ORACLE PURCHASING TABLES in 11.5.X
segment1 - is the system–assigned number you use to identify
in forms and reports.
Table Name
PO_REQUISITION_HEADERS_ALL :
REQUISITION_HEADER_ID, PREPARER_ID, SEGMENT1, SUMMARY_FLAG,ENABLED_FLAG
This table Stores information about requisition headers.
You need one row for each requisition header you
create. Each row contains the requisition number, preparer,
status, and description,SEGMENT1 is the number you use to identify the
requisition in forms and reports (unique).
PO_REQUISITION_LINES_ALL
REQUISITION_LINE_ID,REQUISITION_HEADER_ID, LINE_NUM,LINE_TYPE_ID,CATEGORY_ID, ITEM_DESCRIPTION,UNIT_MEAS_LOOKUP_CODE,UNIT_PRICE,QUANTITY, DELIVER_TO_LOCATION_ID,TO_PERSON_ID,
SOURCE_TYPE_CODE
stores information about requisition lines. line number,
item number, item category, item description, need–by date, deliver–to
location, item quantities, units, prices, requestor, notes, and suggested
supplier information for the requisition line.
LINE_LOCATION_ID - purchase order shipment line on which you
placed the requisition. it is null if you have not placed the requisition line
on a purchase order.
BLANKET_PO_HEADER_ID and BLANKET_PO_LINE_NUM store the
suggested blanket purchase agreement or catalog quotation line information for
the requisition line.
PARENT_REQ_LINE_ID contains the REQUISITION_LINE_ID from the
original requisition line if you exploded or multi sourced this requisition
line.
PO_HEADERS_ALL
PO_HEADER_ID, AGENT_ID, TYPE_LOOKUP_CODE,SEGMENT1,
SUMMARY_FLAG, ENABLED_FLAG
information for your purchasing documents. There are six
types of documents that use PO_HEADERS_ALL
RFQs, Quotations, Standard purchase orders, Planned purchase
orders, Blanket purchase orders, Contracts can uniquely identify a row in
PO_HEADERS_ALL using SEGMENT1 and TYPE_LOOKUP_CODE or using
PO_HEADER_ID.BLANKET_TOTAL_AMOUNT
For blanket purchase orders or contract purchase orders .if
we use copy document Oracle Purchasing stores the foreign key to your original
RFQ in FROM_HEADER_ID.
PO_LINES_ALL
: PO_LINE_ID, PO_HEADER_ID,
LINE_TYPE_ID,INE_NUM
stores current information about each purchase order
line. CONTRACT_NUM reference a contract
purchase order from a standard purchase order line.
PO_VENDORS
:
VENDOR_ID, VENDOR_NAME, SEGMENT1, SUMMARY_FLAG, ENABLED_FLAG
This table stores Information about your suppliers,
Purchasing, receiving, payment, accounting, tax, classification and general
information.
PO_VENDOR_SITES_ALL
VENDOR_SITE_ID, VENDOR_ID, VENDOR_SITE_CODE
This table stores information about supplier sites , a row
for each supplier site you define
Each row includes the site address, supplier reference,
purchasing, payment, bank, and general information.
Oracle Purchasing uses this information to store supplier
address information.
PO_DISTRIBUTIONS_ALL
PO_DISTRIBUTION_ID, PO_HEADER_ID,
PO_LINE_ID,LINE_LOCATION_ID,
SET_OF_BOOKS_ID,CODE_COMBINATION_ID,QUANTITY_ORDERED, DISTRIBUTION_NUM
This table Contains accounting distribution information for
purchase order shipment line. You need one row for each distribution line you
attach to a purchase order shipment.
There are four types of documents using distributions in
Oracle Purchasing:
Standard Purchase Orders, Planned
Purchase Orders, Planned Purchase Order Releases, Blanket Purchase Order
Releases includes the destination type, requestor ID, quantity ordered and
deliver–to location for the distribution.
PO_RELEASES_ALL
PO_RELEASE_ID,
PO_HEADER_ID, RELEASE_NUM, AGENT_ID, RELEASE_DATE
contains information about blanket and planned purchase
order releases. You need one row for each release you issue for a blanket or
planned purchase order. Each row includes the buyer, date, release status, and
release number. Each release must have at least one purchase order shipment
PO_VENDOR_CONTACTS
VENDOR_CONTACT_ID, VENDOR_SITE_ID
stores information about contacts for a supplier site. You
need one row for each supplier contact you define.
Each row includes the contact name and site.
PO_ACTION_HISTORY
OBJECT_ID, OBJECT_TYPE_CODE, OBJECT_SUB_TYPE_CODE,SEQUENCE_NUM
This table stores Information about the approval and control
history of your purchasing documents. There is one record in this table for
each approval or control action an employee takes on a purchase order, purchase
agreement, release, or requisition.
This table stores object_id -- Document header identifier,
OBJECT_TYPE_CODE --- Document type, OBJECT_SUB_TYPE_CODE
--Document subtype
SEQUENCE_NUM --Sequence of the approval or control action
for a document
PO_REQ_DISTRIBUTIONS_ALL
DISTRIBUTION_ID, REQUISITION_LINE_ID, SET_OF_BOOKS_ID, CODE_COMBINATION_ID,
REQ_LINE_QUANTITY, DISTRIBUTION_NUM
Stores information about the accounting distributions
associated with each requisition line.
PO_LINE_LOCATIONS_ALL
LINE_LOCATION_ID,
LAST_UPDATE_DATE, LAST_UPDATED_BY, PO_HEADER_ID,
PO_LINE_ID, SHIPMENT_TYPE
This table Contains information about purchase order
shipment schedules and blanket agreement price breaks. You need one row for each
schedule or price break you attach to a document line. There are seven types of
documents that use shipment schedules:
RFQs, Quotations, Standard purchase orders, planned purchase
orders, Planned purchase order releases, Blanket purchase orders, Blanket
purchase order releases
Each row includes the location, quantity, and dates for each
shipment schedule. Oracle Purchasing uses this information to record delivery
schedule information for purchase orders, and price break information for
blanket purchase orders, quotations and RFQs.
