Knowledge Management for Purchase Order conversion 11.5.10

1. Responsibility / Navigation / Module
Purchasing US Super User / Purchase Orders / Purchase Orders

2. Conversion Approach / Reference Documents
Interface Tables / Oracle Manufacturing APIs and Open Interfaces

3. Application Setup Requirements
Buyer must be set up so that Po’s can be approved.

4. Assumptions / Prerequisites / Validations
Items, Suppliers, Organizations, Locations, Supplier Sites, Operating Unit, Buyers mapping must be available / Required Columns Validations.

5. Base Tables Effected
PO_HEADERS_ALL
PO_LINES_ALL
PO_LINE_LOCATIONS_ALL
PO_DISTRIBUTIONS_ALL

6. Interface Tables / APIs
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE

7. Navigation of Import Program & Parameters
Two Different Import Programs are used based on the Po Type.

i. Incase of ‘Standard Purchase Orders’, the Import Program used is ‘Import Standard Purchase Orders’.
Navigation:
Purchasing US Super User => Purchase Orders => Reports => Run => Import Standard Purchase Orders.
Parameters:
Default Buyer (Optional)
Create or Update Item (Required)
Approval Status (Required)
Batch Id (Optional)

ii. Incase of ‘Blanket Purchase Agreements ‘, the Import Program used is ‘Import Price Catalogs’.
Navigation:
Purchasing US Super User => Purchase Orders => Reports => Run => Import Price Catalogs.
Parameters:
Default Buyer (Optional)
Document Type (Required)
Document Sub Type (Optional)
Create or Update Item (Required)
Create Sourcing Rules (Required)
Approval Status (Required)
Release Generation Method (Optional)
Batch Id (Optional)

8. Import Errors
PO_INTERFACE_ERRORS