Purchasing
Table
Or View: Table
Important
columns:
PO_LINE_ID :
Document line unique identifier
PO_HEADER_ID : Document header unique identifier. (References PO_HEADERS_ALL.po_header_id.)
LINE_TYPE_ID : Line type unique identifier (References PO_LINE_TYPES_B.line_type_id.)
LINE_NUM : Line number
ITEM_ID : Item unique identifier. (References MTL_SYSTEM_ITEMS_B.inventory_item_id.)
CLOSED_FLAG : Indicates whether the line is closed or not
ORG_ID : Operating unit unique identifier
PO_HEADER_ID : Document header unique identifier. (References PO_HEADERS_ALL.po_header_id.)
LINE_TYPE_ID : Line type unique identifier (References PO_LINE_TYPES_B.line_type_id.)
LINE_NUM : Line number
ITEM_ID : Item unique identifier. (References MTL_SYSTEM_ITEMS_B.inventory_item_id.)
CLOSED_FLAG : Indicates whether the line is closed or not
ORG_ID : Operating unit unique identifier
Description:
PO_LINES_ALL
stores current information about each purchase order line. You need
one row for each line you attach to a document. There are five
document types that use lines:
- RFQs
- Quotations
- Standard purchase orders
- Blanket purchase orders
- Planned purchase orders
Each row includes
the line number, the item number and category, unit, price, tax
information, matching information, and quantity ordered for the line.
Oracle Purchasing uses this information to record and update item and
price information for purchase orders, quotations, and RFQs.
PO_LINE_ID is the
unique system-generated line number invisible to the user. LINE_NUM
is the number of the line on the purchase order.
Oracle Purchasing
uses CONTRACT_ID to reference a contract purchase order from a
standard purchase order line. Oracle Purchasing uses
ALLOW_PRICE_OVERRIDE_FLAG, COMMITTED_AMOUNT, QUANTITY_COMMITTED,
MIN_RELEASE_AMOUNT only for blanket and planned purchase order lines.
The QUANTITY field
stores the total quantity of all purchase order shipment lines (found
in PO_LINE_LOCATIONS_ALL)
No comments:
Post a Comment