PO_HEADERS_ALL contains header information for your purchasing
documents. You need one row for each document you create. There are six types of documents that use PO_HEADERS_ALL:
â€¢ Standard purchase orders
â€¢ Planned purchase orders
â€¢ Blanket purchase orders
Each row contains buyer information, supplier information, brief notes, foreign currency information, terms and conditions information, and the status of the document.
Oracle Purchasing uses this information to record information that is related to a complete document.
PO_HEADER_ID is the unique systemâ€“generated primary key and is invisible to the user. SEGMENT1 is the systemâ€“assigned number you use to identify the document in forms and reports.
Oracle PurchasingÂ generates SEGMENT1 using the PO_UNIQUE_IDENTIFIER_CONT_ALL table if you choose to let Oracle Purchasing generate document numbers for you. SEGMENT1 is not unique for the entire table.
Different document types can share the same numbers. You can uniquely identify a row in PO_HEADERS_ALL using SEGMENT1 and TYPE_LOOKUP_CODE or using
PO_HEADER_ID. If APPROVED_FLAG is â€™Yâ€™, the purchase order is approved. If your
document type is a blanket purchase order, contract purchase order,RFQ, or quotation, Oracle Purchasing uses START_DATE and END_DATE to store the valid date range for the document. Oracle Purchasing only uses BLANKET_TOTAL_AMOUNT for blanket
purchase orders or contract purchase orders. If you autocreate a quotation from an RFQ using the Copy Document window, Oracle Purchasing stores the foreign key to your original RFQ in FROM_HEADER_ID. Oracle Purchasing also uses
FROM_TYPE_LOOKUP_CODE to indicate that you copied the quotation from an RFQ.