Oracle A75089-02 - Manual (Page 93)

Running the Planning Schedule Inbound (SPSI) Program
Inbound Transactions 7-15
7. In the Execute DSP flag field:
Select Yes to initiate the Demand Processor.
Select No if you do not want to initiate the Demand Processor.
8. Enter the Transaction Type: SPSI
9. Enter the Map Code for this file: RLM_SPSI_FF
10. Select the Debug Mode: 0, 1, 2, or 3
Set the Debug Mode to report on debug information for troubleshooting. Debug
information is written to the concurrent manager log file:
The Debug Mode is set using a number.
0 = OFF: No debug information is generated.
1 = LOW: Summary debug information is written to the concurrent manager
log file.
2 = MEDIUM: Medium level debug information is written to the concurrent
manager log file.
3 = HIGH: High level debug information is written to the concurrent manager
log file. (This option generates an abundance of information.)
11. When finished, choose OK in the Parameters window.
12. Choose Submit and make a note of the Request ID returned. Select the Process
Import Program.
Automating the Planning Schedule Inbound Program
The steps for receiving inbound EDI demand schedule transactions in Oracle
e-Commerce Gateway and loading them from Oracle e-Commerce Gateway to
Oracle Release Management can be automated.
For details on how to automate the process, see: Process Automation, Using
e-Commerce Gateway for Inbound Demand, Oracle Release Management
Implementation Manual, Release 11i.
See Also
Viewing the Status of Concurrent Programs on page 9-7
Oracle e-Commerce Gateway Implementation Manual, Release 11i