Use this transaction to procure goods and services from suppliers. Approved purchase orders (POs), including standard POs, planned orders, planned releases, blanket purchase agreement, and blanket releases can be extracted.
Note: This transaction is not used to convey PO change or acknowledgment information.
The Outbound Purchase Order transaction includes procurement card information in the interface data file. This includes credit card type, credit card number, and expiration date.
You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels.
Use Purchasing to convert purchase requisitions to POs or to create new POs, planned orders, blanket purchase agreements or blanket releases. Use Purchasing to approve POs before transmitting them to your supplier.
You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels. See: Attachments.
Prior to approving any purchase orders, make sure that the Approve On option is set to Archive for all document types. Do this from Purchasing by navigating to Setup > Purchasing > Document Types.
Create the outbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
Define the ECE: Output 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.
Note: Both the outbound Purchase Order and Purchase Order Change Request transactions allow attachments. See: Attachments.
Navigate to the Run e-Commerce Outbound Process window:
Process > Extract 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 Outbound Process window, select OUT: Purchase Order (850/ORDERS) from the LOV.
Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.
The Parameters window will open. Enter the following parameters as necessary:
Output File Name: Enter an output file name or accept the default.
PO Number From: Enter the PO number from which to extract transactions.
PO Number To: Enter the PO number to which to extract transactions.
Creation Date From: Enter the creation date from which to extract transactions.
Creation Date To: Enter the creation date to which to extract transactions.
PO Type: Enter the PO type: Blanket PO, Blanket Release, Planned PO, or Standard PO.
Supplier Name: Enter the supplier name.
Supplier Site Code: Enter the supplier site code.
Debug Mode for POO: 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.)
Enter any Schedule or Completion Options for the request.
Choose Submit and make a note of the Request ID returned.
Additional Information: For additional information, see:
Outbound Purchase Order, Oracle e-Commerce Gateway Implementation Manuali
Submitting a Request, Oracle Applications User's Guide