Use this transaction to import customer production sequence schedules into your Oracle Release Management system. Using the Release Management Demand Processor, you can import customer production sequence schedules into your Oracle Order Management and Oracle Planning systems.
Prerequisite Setup in Oracle Release Management
The Demand Processor verifies schedule data based on the e-Commerce Gateway Trading Partner Setup in conjunction with Oracle Release Management Processing Rules.
For more details on Oracle Release Management Setup steps, refer to:
Oracle Release Management Implementation Manual Oracle Release Management User's Guide
Prerequisites in Oracle e-Commerce Gateway
• Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
7-24 Oracle e-Commerce Gateway User's Guide
• Define the ECE: Inbound file path profile option. See: e-Commerce Gateway Profile Options, Oracle e-Commerce Gateway Implementation Manual.
• Define trading partner relationships and enable EDI transactions for the trading partner. See: Defining Trading Partner Data, page 3-4.
• Define code conversions. See: Defining Code Conversion Categories, page 4-7, Assigning Categories, page 4-8, and Defining Code Conversion Values, page 4-14. • Customize interface data file layout, if necessary. See: Changing the Interface Data
File Record Layout, page 5-1.
To run the Production Sequence Schedule Inbound Program:
This transaction may be submitted under either the e-Commerce Gateway Responsibility or the Release Management Responsibility.
From the e-Commerce Gateway Responsibility:
1. Navigate to the Run e-Commerce Inbound Process window: • Process > Import Program
• In the Submit a New Request window, select Single Request to submit an individual request.
2. In the Name field of the Run e-Commerce Inbound Process window, select IN: Planning Sequence (830, DELFOR) from the LOV.
3. The Parameters window will open. Enter the following parameters as necessary: • Inbound File Path: Enter the inbound file path or accept the default.
• Inbound File Name: Enter the inbound file name or accept the default. • Map Code: (Required) Enter the Map Code for this file: RLM_PSQI_FF. • Debug Mode: Set the debug mode to report on debug information. Debug
information is written to the concurrent manager log file:
OFF: No debug information is generated.
LOW: Summary debug information is written to the concurrent manager log
file.
MEDIUM: Medium level debug information is written to the concurrent
manager log file.
HIGH: High level debug information is written to the concurrent manager log
Inbound Transactions 7-25 • Execute DSP Flag:
Select Yes to initiate the Demand Processor.
Select No if you do not want to initiate the Demand Processor. • Issue Warning for Dropped Parts:
• Data File Characterset: Defaults to thte characterset defined in the database. Accept this value or select from the list of values.
Note: If the selected data file characterset is different from the database characterset, then the generic inbound program will perform a characterset conversion on the data in the data file. This conversion is done to the database characterset. If the conversion is failed, a 'Lossy Conversion' error will be raised. Transactions without Lossy Conversion errors in the same file will continue processing unless they have other types of errors. Use the View Staged Documents window to identify the transaction errors due to Lossy Conversion. The document status is set to 'SKIPPED' and the Line that caused this conversion error has the status 'Invalid characters detected during Characterset Conversion'.
4. Enter any Schedule or Completion Options for the request.
5. Choose Submit and make a note of the Request ID returned.
From the Release Management Responsibility:
1. Select Process Inbound Transactions
2. In the Submit a New Request window, select Single Request to submit an individual request.
3. In the Submit Request window, select EDI Inbound Transactions.
4. The Parameters window will open. Enter the following parameters as necessary: • Inbound File Path: Enter the inbound file path or accept the default.
• Inbound File Name: Enter the inbound file name or accept the default. • Transaction Type: Enter the Transaction Type: PSQI
7-26 Oracle e-Commerce Gateway User's Guide
• Debug Mode: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:
OFF: No debug information is generated.
LOW: Summary debug information is written to the concurrent manager log
file.
MEDIUM: Medium level debug information is written to the concurrent
manager log file.
HIGH: High level debug information is written to the concurrent manager log
file. (This option generates much information.) • Execute DSP Flag:
Select Yes to initiate the Demand Processor.
Select No if you do not want to initiate the Demand Processor. • Issue Warning for Dropped Parts:
5. Enter any Schedule or Completion Options for the request.
6. Choose Submit and make a note of the Request ID returned.
Automating the Production Sequence 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.
Note: For additional information, see:
Viewing the Status of Concurrent Programs, page 9-6
Oracle e-Commerce Gateway Implementation Manual
Planning/Material Release Schedule Inbound, Oracle e-Commerce
Gateway Implementation Manual
Submitting a Request, Oracle Applications User's Guide
Oracle Release Management Implementation Manual Oracle Release Management User's Guide
Inbound Transactions 7-27