Oracle A75089-02 Manual De Usuario

Running the Purchase Order Outbound (POO) Extract Program

 

Outbound Transactions

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. 

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: 

 on page 8-20.

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, Release 
11i.

❏ Define the ECE: Output file path profile option.  See: e-Commerce Gateway 

Profile Options, Oracle e-Commerce Gateway Implementation Manual, Release 11i.

❏ Define trading partner relationships and enable EDI transactions for the trading 

partner.  See: 

This transaction is not used to convey PO change or 

acknowledgment information.