If you are new here, you may want to subscribe to the following feeds Oracle Purchasing (PO) key table - po_lines_all (2)
Written by Nilesh JethwaPO_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_NUM 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).
Posted in ERP Tables |
3 Comments to “Oracle Purchasing (PO) key table - po_lines_all (2)”
Leave a Comment
Free Dashboards and KPI examples
August 4th, 2007 at 7:55 am
hi Nilesh,
your blog is a good and informative one. can you inform me about ‘po_line_locations_all’ table. what other tables it is linked to and what information does it store.
thanks,
Omair
August 13th, 2007 at 5:06 pm
Hi Omair,
Here is some info you needed…..
PO_LINE_LOCATIONS_ALL 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.
PO_RELEASE_ID applies only to blanket purchase order release
shipments. PO_RELEASE_ID identifies the release on which you
placed this shipment.
SOURCE_SHIPMENT_ID applies only to planned purchase order
release shipments. It identifies the planned purchase order shipment
you chose to release from.
PRICE_OVERRIDE always equals the purchase order line price for
standard purchase order shipments. For blanket and planned purchase
orders, PRICE_OVERRIDE depends on the values of the
ALLOW_PRICE_OVERRIDE_FLAG and NOT_TO_EXCEED_PRICE in
the corresponding row in PO_LINES_ALL:
• If ALLOW_PRICE_OVERRIDE_FLAG is ‘N’, then
PRICE_OVERRIDE equals UNIT_PRICE in PO_LINES_ALL.
• If ALLOW_PRICE_OVERRIDE_FLAG is ‘Y’, the
PRICE_OVERRIDE can take any value that is smaller than
NOT_TO_EXCEED_PRICE in PO_LINES_ALL.
The QUANTITY field corresponds to the total quantity ordered on all
purchase order distribution lines (found in
PO_DISTRIBUTIONS_ALL).
Oracle Purchasing automatically updates QUANTITY_RECEIVED,
QUANTITY_ACCEPTED, and QUANTITY_REJECTED when you
receive, return, or inspect goods or services. Oracle Payables
automatically updates QUANTITY_BILLED when you match an
invoice with a purchase order shipment. Oracle Purchasing
automatically updates QUANTITY_CANCELLED when you cancel a
purchase order shipment.
Oracle Purchasing sets APPROVED_FLAG to ‘Y’ when you approve
the corresponding purchase order if there are no problems associated
with the shipment and its related distributions.
Oracle Purchasing sets ENCUMBERED_FLAG to ‘Y’ and enters the
ENCUMBERED_DATE when you approve a purchase order if you use
encumbrance.
May 5th, 2008 at 2:16 am
nice one