Release 12.1
Part Number E12952-03
Contents
Previous
Next
| Oracle e-Commerce Gateway User's Guide Release 12.1 Part Number E12952-03 | Contents | Previous | Next |
This chapter covers the following topics:
Use this transaction to import customer purchase orders and grocery purchase orders into your Oracle Order Management system.
Note: Grocery purchase orders allows you to create sales orders in the Order Management system and support various functions including the import of price adjustments, pricing attributes, sales credits, reservations, action requests, and customer creation. Lot and serial number information can also be imported for return lines. The Inbound Grocery Purchase Order (875/ORDERS) concurrent program reads the data from views, which is filtered by operating unit, on the open interface tables.
Using the Order Management Order Import Open Interface, you can import a high-volume of purchase orders and grocery purchase orders, complete with all the standard online purchase order entry features, including customer item to supplier item cross-referencing.
The required Order Management setup steps are the same whether the order is entered online or through Order Import. The following is a sample list of the Order Management setup steps needed to process orders through the e-Commerce Gateway or online.
Define Customers and Customer Sites in Order Management/Oracle Receivables.
Define Order Types in Order Management.
Define items and appropriate customer items in Oracle Inventory.
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
Define trading partner relationships and enable EDI transactions for the trading partner. See: Defining Trading Partner Data.
To run the Purchase Order Inbound program
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.
In the Name field of the Run e-Commerce Inbound Process window, select one of the following names from the list of values:
IN: Purchase Orders (850/ORDERS)
IN: Grocery Purchase Orders (875/ORDERS)
IN: OPM Purchase Order (850/ORDERS)
For IN: Purchase Orders (850/ORDERS) and IN: Grocery Purchase Orders (875/ORDERS), enter the following parameters as necessary in the Parameters window:
File Path: (for IN: Purchase Orders (850/ORDERS) only) Enter the file path or accept the default.
File Name: Enter the inbound data file or accept the default.
Debug Mode: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:
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 much information.)
Run Import (Required)
Select Yes to initiate the Order Management Order Import Open Interface Import program using the default parameter values.
Enter No to cancel the Order Management Order Import Open Interface.
Order Import Instances: Enter an appropriate order import instance or accept the default.
Map Code: (Required) The default map code is EC_POI_FF.
Data File Characterset: Defaults to the 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'.
For IN: OPM Purchase Order (850/ORDERS), enter the following parameters as necessary:
Inbound Datafile Name: Enter the inbound data file or accept the default.
Execute Open Interface Flag: (Required)
Select Yes to initiate the Order Management Order Import Open Interface Import program using the default parameter values.
Select No to cancel the Order Management Order Import Open Interface.
Map Code: (Required) The default map code is EC_GPOI_FF.
Debug Mode: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:
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 much information.)
Enter the Schedule and Completion Options as desired.
Choose Submit and make a note of the Request ID returned.
Note: For additional information, see:
Oracle e-Commerce Gateway Implementation Manual
Inbound Purchase Order, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Viewing the Status of Concurrent Programs
Use this transaction to import customer purchase order changes into your Oracle Order Management system. Using the Order Management Order Import Open Interface, you can import purchase orders with all standard online purchase order entry features, including the customer item to supplier item cross-referencing.
The required Order Management setup steps are the same whether the order is entered on-line or through Order Import. The following is a sample list of the Order Management setup steps to process orders through the e-Commerce Gateway or entered on-line.
Define Customers and Customer Sites in Order Management/Oracle Receivables.
Define Order Types in Order Management.
Define items and appropriate customer items in Oracle Inventory.
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
Define trading partner relationships and enable EDI transactions for the trading partner. See: Defining Trading Partner Data.
To run the Purchase Order Change Inbound program
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Purchase Order Changes (860/ORDCHG) from the LOV.
The Parameters window opens. Enter the following parameters as necessary:
File Path: Enter the file path or accept the default.
File Name: Enter the inbound data file or accept the default.
Debug Mode: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:
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 much information.)
Run Import (Required)
Select Yes to initiate the Order Management Order Import Open Interface Import program using the default parameter values.
Enter No to cancel the Order Management Order Import Open Interface.
Order Import Instances: Enter an appropriate order import instance or accept the default.
Map Code: (Required) Select map code from the LOV.
Data File Characterset: Defaults to the 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'.
Enter the Schedule and Completion Options for the request.
Choose Submit and make a note of the Request ID returned.
Note: For additional information, see:
Oracle e-Commerce Gateway Implementation Manual
Inbound Purchase Order Changes, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Viewing the Status of Concurrent Programs
Use this transaction to import supplier invoices into your Oracle Payables system for manual or electronic payment. Using the Payables Open Interface, you can accomplish high-volume invoice import complete with all standard online invoice entry features, including purchase order matching, invoice approval, and invoice batch processing.
You can optionally set up an Invoice Hold Reason unique to this transaction. All invoices being imported into Payables may be placed on hold using the unique Invoice Hold Reason. This may be useful during implementation of a new trading partner to separate electronic invoices from other invoices in your Payables system. To define an invoice hold reason, use the Invoice Approvals window.
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Invoice (810/INVOIC) from the LOV.
The Parameters window will open. Enter the following parameters as necessary:
Inbound Datafile Name: Enter the inbound data file or accept the default.
Execute Open Interface? (Required)
Select Yes to initiate the Payables Open Interface Import program using the default parameter values.
Enter No if you do not want to initiate the Payables Open Interface.
Payables: Batch Name: If you are using batch control, enter a name to be assigned to the batch of invoices to be imported.
Payables: Hold Code: Enter an Invoice Hold Reason if you want to place all invoices to be imported on hold for review or audit purposes.
Payables: Hold Reason: Accept default Hold Reason Description or overwrite the default.
Payables: GL Date: Enter GL date in an open period to be applied to imported invoices.
Payables: Purge: (Required) Enter Yes if you wish to delete the invoice data from the Payables Open Interface tables after the data has been imported into Oracle Payables.
Summarize Report: Enter Yes to submit the Payables Invoice Import Report in summary. Enter No to submit the report in detail.
Map Code: (Required) Enter the appropriate map code.
Debug Mode for INI: 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.)
Data File Characterset: Defaults to the 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'.
Enter Schedule and Completion Options for the request.
Choose Submit and make a note of the Request ID returned.
Note: For additional information, see:
Oracle e-Commerce Gateway Implementation Manual
Inbound Invoice, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Viewing the Status of Concurrent Programs
Use this transaction to import supplier catalogs into your Purchasing system as Catalog Quotes. This supports catalog lookup and purchase order placement. During the import process, supplier sourcing rules may be added to Oracle Purchasing, and the Oracle Inventory item master may be updated with catalog item changes or new catalog items.
Allow updating of item description in Purchasing Options.
Allow the updating of item status codes at the site level. Set the INV: Default Item Status profile to Active.
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Price Catalog (832/PRICAT) from the LOV.
The Parameters window will open. Enter the following parameters as necessary:
Inbound Datafile Name: Enter the inbound data file or accept the default.
Execute Open Interface? (Required)
Select Yes to initiate the Purchasing Open Interface Import program using the default parameter values.
Enter No if you do not want to initiate the Purchasing Open Interface.
Default Buyer: (Required) Enter the default buyer name for the Price/Sales Catalog or Response to RFQ.
Document Type: Valid options are Blanket and Quotation. The option of Blanket directs Purchasing to create a Blanket Agreement for the document to be imported. The option of Quotations directs Purchasing to create a Catalog Quotation for the document to be imported.
Document Sub Type: Used with document type of ”Quotation” to indicate a document sub type of “Catalog Quotation” for the Price/Sales Catalog or Response to RFQ to be imported. The document sub type of “Bid Quotation” is invalid for the transaction.
Create or Update Items: Used with the Price/Sales Catalog or Response to RFQ to indicate whether you wish to update the item master with catalog item changes or add catalog items to the item master.
Create Sourcing Rules: Indicate Yes or No on whether supplier sourcing rules should be created automatically during the Price/Sales Catalog and Response to RFQ import process.
Approval Status: Enter desired status of Approved or Incomplete for Blanket Agreement and Quotation created by Purchasing for the Price/Sales Catalog or Response to RFQ to be imported.
Release Generation Method: Used when Document Type is set to Blanket and Create Sourcing Rules is set to Yes. Select from the following three blanket release methods:
Automatic Release: allows Purchasing to automatically generate approved blanket releases for items that are autosourced to a single supplier.
Automatic Release with Review: allows Purchasing to automatically generate releases and forwards them for approval.
Release using Autocreate: allows you to use the Purchasing Autocreate function to convert purchase requisitions into blanket releases for blanket purchase orders.
Map Code: (Required) Enter the appropriate map code.
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.)
Data File Characterset: Defaults to the 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'.
Enter any Schedule and Completion options for the request.
Choose Submit and make a note of the Request ID returned.
Note: For additional information, see:
Inbound Price / Sales Catalog, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Viewing the Status of Concurrent Programs
Use this transaction to import supplier responses to your request for quotes into your Purchasing system to support the procurement process.
Allow updating of item description in Purchasing Options.
Allow the updating of item status codes at the site level. Set the INV: Default Item Status profile to Active.
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Response to RFQ (843/QUOTES) from the LOV.
The Parameters window will open. Enter the following parameters as necessary:
Inbound Datafile Name: Enter the inbound data file or accept the default.
Execute Open Interface? (Required)
Enter Y to initiate the Purchasing Document Open Interface program using the default parameter values.
Enter N if you do not to initiate Purchasing Document Open Interface.
Default Buyer: (Required) Enter the default buyer name for the Response to RFQ.
Document Type: Valid options are Blanket and Quotation. The option of Blanket directs Purchasing to create a Blanket Agreement for the document to be imported. The option of Quotations directs Purchasing to create a Catalog Quotation for the document to be imported.
Document Sub Type: Used with document type of ”Quotation” to indicate a document sub type of “Catalog Quotation” for the Price/Sales Catalog or Response to RFQ to be imported. The document sub type of “Bid Quotation” is invalid for the transaction.
Create or Update Items: Used with the Price/Sales Catalog or Response to RFQ to indicate whether you wish to update the item master with catalog item changes or add catalog items to the item master.
Create Sourcing Rules: Indicate Yes or No on whether vendor sourcing rules should be created automatically during the Price/Sales Catalog and Response to RFQ import process.
Approval Status: Enter desired status of Approved or Incomplete for Blanket Agreement and Quotation created by Purchasing for the Price/Sales Catalog or Response to RFQ to be imported.
Release Generation Method: Used when Document Type is set to Blanket and Create Sourcing Rules is set to Yes. Select from the following three blanket release methods:
Automatic Release: allows Purchasing to automatically generate approved blanket releases for items that are autosourced to a single supplier.
Automatic Release with Review: allows Purchasing to automatically generate releases and forwards them for approval.
Release using Autocreate: allows you to use the Purchasing Autocreate function to convert purchase requisitions into blanket releases for blanket purchase orders.
Map Code: (Required) Enter the appropriate map code.
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.)
Data File Characterset: Defaults to the 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'.
Enter any Schedule and Completion Options for the request.
Choose Submit and make a note of the Request ID returned.
Note: For additional information, see:
Inbound Response to Request for Quote, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Viewing the Status of Concurrent Programs
Use this transaction to import supplier ship notices into your Purchasing system as a pre-receipt. The electronic ship notice provides a shipment identifier to facilitate the receipt of the physical goods.
In the Receiving Options window, set the ASN Control to Name/Reject/Warning to indicate treatment of the inbound ASN as if the Purchase Order shipment exists.
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Ship Notice/Manifest (856/DESADV) from the LOV.
The Parameters window will open. Enter the following parameters as necessary:
Inbound Datafile Name: Enter the inbound data file or accept the default.
Execute Open Interface? (Required)
Select Yes to initiate the Receiving Open Interface program immediately. There are no program parameters.
Enter No if you do not want to initiate the Receiving Open Interface program in Purchasing.
Map Code: (Required) Enter the appropriate map code.
Debug Mode for ASNI? 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.)
Data File Characterset: Defaults to the 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'.
Enter any Schedule and Completion Options for the request.
Choose Submit and make a note of the Request ID returned.
Note: For additional information, see:
Inbound Ship Notice / Manifest, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Viewing the Status of Concurrent Programs
Use this transaction to import supplier ship notices and invoices into your Purchasing and Payables system as a pre-receipt and unapproved invoice.
Similar to the Ship Notice/Manifest transaction, the electronic ship notice provides a shipment identifier to facilitate the receipt of the physical goods and the creation of the unapproved invoice in a single EDI transaction.
In the Receiving Options window, set the ASN Control to Name/Reject/Warning to indicate treatment of the inbound ASN as if the Purchase Order shipment exists.
Set the RCV: Show ASN Matched POs profile option to Yes or No. A value of Yes indicates the original Purchase Order Shipment line is displayed in the Find Expected Receipts in addition to the ASN Shipment line.
Supplier site must be defined as a ”Pay on Receipt” site.
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Shipment and Billing Notice (857) from the LOV.
The Parameters window will open. Enter the following parameters as necessary:
Inbound Datafile Name: Enter the inbound data file or accept the default.
Execute Open Interface? (Required)
Select Yes to initiate the Receiving Open Interface immediately. There are no program parameters.
Enter No if you do not want to initiate the Receiving Open Interface program in Purchasing.
Map Code: (Required) Enter the appropriate map code.
Debug Mode for SBNI? 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.)
Data File Characterset: Defaults to the 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'.
Enter any Schedule and Completion Options for the request..
Choose Submit and make a note of the Request ID returned.
Note: For additional information, see:
Inbound Shipping and Billing Notice, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Viewing the Status of Concurrent Programs
Use this transaction to import customer planning schedules into your Oracle Release Management system. Using the Release Management Demand Processor, you can import customer planning schedules into your Oracle Order Management and Oracle Planning systems.
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
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
This transaction can be submitted under either the e-Commerce Gateway Responsibility or the Release Management Responsibility.
From the e-Commerce Gateway Responsibility:
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Planning Sequence (830, DELFOR) from the LOV.
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_SPSI_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 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:
Enter any Schedule or Completion Options for the request..
Choose Submit and make a note of the Request ID returned.
From the Release Management Responsibility:
Select Process Inbound Transactions.
In the Submit a New Request window, select Single Request to submit an individual request.
In the Submit Request window select EDI Inbound Transactions.
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: SPSI
Map Code: (Required) Enter the Map Code for this file: RLM_SPSI_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 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:
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'.
Enter any Schedule or Completion Options for the request..
Choose Submit and make a note of the Request ID returned.
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
Oracle e-Commerce Gateway Implementation Manual
Planning/Material Release Schedule Inbound, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Oracle Release Management Implementation Manual
Oracle Release Management User's Guide
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.
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
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
This transaction may be submitted under either the e-Commerce Gateway Responsibility or the Release Management Responsibility.
From the e-Commerce Gateway Responsibility
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Planning Sequence (830, DELFOR) from the LOV.
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 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:
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'.
Enter any Schedule or Completion Options for the request.
Choose Submit and make a note of the Request ID returned.
From the Release Management Responsibility
Select Process Inbound Transactions
In the Submit a New Request window, select Single Request to submit an individual request.
In the Submit Request window, select EDI Inbound Transactions.
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
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 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:
Enter any Schedule or Completion Options for the request.
Choose Submit and make a note of the Request ID returned.
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
Oracle e-Commerce Gateway Implementation Manual
Planning/Material Release Schedule Inbound, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Oracle Release Management Implementation Manual
Oracle Release Management User's Guide
Use this transaction to import customer shipping schedules into your Oracle Release Management system. Using the Release Management Demand Processor, you can import customer shipping schedules into your Oracle Order Management and Oracle Planning systems.
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
Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
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.
Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.
Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.
This transaction can be submitted under either the e-Commerce Gateway Responsibility or the Release Management Responsibility.
From the EC Gateway Responsibility
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.
In the Name field of the Run e-Commerce Inbound Process window, select IN: Planning Sequence (830, DELFOR) from the LOV.
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_SSSI_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 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:
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'.
Enter Schedule and Completion Options for the request as necessary.
Choose Submit and make a note of the Request ID returned.
From the Release Management Responsibility
Select Process Inbound Transactions.
In the Submit a New Request window, select Single Request to submit an individual request.
In the Submit Request window, select EDI Inbound Transactions.
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: SSSI
Map Code: (Required) Enter the Map Code for this file: RLM_SSSI_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 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:
Enter any Schedule and Completion Options for the request.
Choose Submit and make a note of the Request ID returned.
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
Oracle e-Commerce Gateway Implementation Manual
Planning/Material Release Schedule Inbound, Oracle e-Commerce Gateway Implementation Manual
Submitting a Request, Oracle E-Business Suite User's Guide
Oracle Release Management Implementation Manual
Oracle Release Management User's Guide
Copyright © 1996, 2009, Oracle and/or its affiliates. All rights reserved.