What are the main tables associated with Purchase Order?
There are four main tables associated with Purchase Order.
1. PO_HEADERS_ALL
2. PO_LINES_ALL
3. PO_LINE_LOCATIONS_ALL
4. PO_DISTRIBUTIONS_ALL
1. It contains the Header information for the Purchasing
documents. We require one row for each document we create.
Six types of documents that use PO_HEADERS_ALL are
a. RFQ
b. Quotation
c. Standard PO
d. Planned PO
e. Blanket PO
f. Contracts
Important data that are populated in this table are
- Buyer Information
- Supplier Information
- Brief Notes
- Terms and Conditions
- Status of the document
Important columns: PO_HEADER_ID
1. It stores information about each PO lines. We need one row for each line we attach to a document.
Each row includes
a. LINE NUMBER
b. ITEM NUMBER
c. UNIT
d. PRICE
e. U.O.M
f. QUANTITY
2. It contains the information about PO shipment schedules and Blanket Agreement Price Breaks.
We need one row for each schedule or price break we attach to a document
Each row includes
- Destination Type
- Requestor Id
- Quantity Ordered and Delivered to Destination
- If the distribution corresponds to a Blanket PO release, PO_RELEASE_ID column identifies this release
- We enter distribution information in distribution window accessible through PO window
THE PURCHASE ORDER
The CLOSED_CODE column exists in the following three tables
1. PO_HEADERS_ALL
2. PO_LINES_ALL
3. PO_LINE_LOCATIONS_ALL
IMPORTANT COLUMNS OF PURCHASING TABLES
PO_HEADERS_ALL
PO_LINES_ALL
PO_LINE_LOCATIONS_ALL
PO_HEADER_ID
SEGMENT1
VENDOR_ID
VENDOR_SITE_ID
SHIP_TO_LOCATION_ID
CURRENCY_CODE
CLOSED CODE
1. OPEN
2. CLOSED
3. FINALLY CLOSED
4. HOLD
5. FREEZE
PO_LINE_ID
CATEGORY_ID
ITEM_ID
PO_HEADER_ID
QUANTITY
CLOSED_CODE
1. OPEN
2. CLOSED
LINE_LOCATION_ID
SHIP_TO_LOCATION_ID
PO_HEADER_ID
PO_LINE_ID
QUANTITY_RECEIVED
QUANTITY_ACCEPTED
QUANTITY_REJECTED
CLOSED_CODE
1. OPEN
2. CLOSED FOR INVOICE
3. CLOSED FOR RECEIVING
4. FINALLY CLOSED
What are the different Purchasing modes in Receiving?
There are three modes
1. ONLINE
2. IMMEDIATE
3. BATCH
1. ONLINE: Receipts are processed Online. If there are any errors, they are shown on the FORM itself, and don’t let you IGNORE and PROCEED.
2. IMMEDIATE: Receipts are processed immediately, but no errors are shown. Errors are recorded in REC_TRANSACTION_INTERFACE table.
3. BATCH: Receipts are processed in batch, but no errors are shown. Errors are recorded in REC_TRANSACTION_INTERFACE table.
Note: In all the above two cases, it requires Receiving
Transaction Processor to be run periodically.
When you SAVE a Received Data in FORM, which tables are UPDATED?
- RCV_SHIPMENT_HEADERS: It contains SUPPLIER shipment header data like Shipment Date, Supplier Name
- RCV_TRANSACTIONS_INTERFACE: It contains RECEIVED data like Item Name, Quantity, and Receiving location
- RCV_SHIPMENT_LINES
- MTL_MATERIAL_TRANSACTIONS_TEMP
- PO_LINE_LOCATIONS_ALL
- PO_DISTRIBUTIONS_ALL
- Purchase Order Receipts
- Internal Requisition Receipts
- Inventory Inter-Org Transfer Receipts
- Customer Return Receipts {/slide}
What are the different types of Receiving Routing?}
- Standard Receipt
- Inspection Required
- Direct Delivery
RECEIVING OPEN INTERFACE
- ROI is a gateway to IMPORT data from Oracle as well as Non-Oracle applications.
- The Receipts done through ROI should be processed in Batch mode only.
- In ROI, the table which are updated are
- 1. RCV_HEADER_INTERFACE
- 2. RCV_TRANSACTION_INTERFACE
- Receipts can be done by Direct Delivery or by two steps namely RECEIVED and DELIVER.
- This can be determined through AUTO_TRANSACT_CODE_FLAG.
- If the value is DELIVERED, the system does a direct delivery into Sub-Inventory and if the value is RECEIVED, the system only receives the material and the delivery is done by the Receiving Transaction Form.
- RCV_HEADERS_INTERFACE
- RCV_TRANSACTIONS_INTERFACE
- RCV_SHIPMENT_HEADERS
- HEADER_INTERFACE_ID
- GROUP_ID
- RECEIPT_SOURCE_CODE
- PROCESSING_STATUS_CODE
- TRANSACTION_TYPE
- ASN_TYPE
- INTERFACE_TRANSACTION_ID
- GROUP_ID
- PROCESSING_STATUS_CODE
- TRANSACTION_STATUS_CODE
- PROCESSING_MODE_CODE
- HEADER-INTERFACE_ID
- ASN_STATUS
- ASN_TYPE
- EDI_CONTROL_NUM
- Transactions with LOT controls
- Ø Transactions with SERIAL controls
- Ø Internal Transfer & Sales order
- Ø Un-Ordered Receipts
Through which you will be able to see ERROR reports
in ROI?
Receiving Interface Errors Report Data can be loaded into ROI either through flat files or direct SELECT statement. You can see details of errors from PO_INTERFACE_ERRORS table by joining with RCV_TRANSACTIONS_INTERFACE table using Interface_id.
