Wednesday, November 23, 2011

PO_LINE_LOCATIONS_ALL

Purchasing
Table Or View: Table

Important columns: 
LINE_LOCATION_ID : Document shipment schedule unique identifier
LAST_UPDATE_DATE : Standard Who column: date when this record was last updated
LAST_UPDATED_BY : Standard Who column: the user who last updated this record. (References FND_USERS.user_id.)
PO_HEADER_ID : Document header unique identifier. (References PO_HEADERS_ALL.po_header_id.). For Release shipments, this references the Unique identifier of Blanket PO
PO_LINE_ID : Document line unique identifier (References PO_LINES_ALL.po_line_id). For Release Shipments, this references the unique line identifier of Blanket PO
QUANTITY :  Quantity ordered or break quantity for blanket purchase orders, RFQs and quotations
QUANTITY_RECEIVED : Quantity received until today
QUANTITY_ACCEPTED : Quantity accepted after inspection, up until today
QUANTITY_REJECTED : Quantity rejected after inspection, up until today
QUANTITY_BILLED :  Quantity invoiced by Oracle Payables, up until today
QUANTITY_CANCELLED : Quantity cancelled
TAXABLE_FLAG : Indicates whether the shipment is taxable
TAX_NAME : Tax code for the shipment (References AP_TAX_CODES_ALL.name)
SHIP_TO_ORGANIZATION_ID : Ship-to organization unique identifier(References HR_ORGANIZATION_UNITS.organization_id)
SHIPMENT_NUM : Shipment line number
SOURCE_SHIPMENT_ID : Unique identifier of the planned purchase order shipment(also stored in PO_LINE_LOCATIONS_ALL) that was referenced when creating this scheduled release shipment
ORG_ID : Operating unit unique identifier(References HR_OPERATING_UNITS.organization_id)

Description: 
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:
  1. RFQs
  2. Quotations
  3. Standard purchase orders
  4. Planned purchase orders
  5. Planned purchase order releases
  6. Blanket purchase orders
  7. 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.

No comments:

Post a Comment

Best Blogger TipsGet Flower Effect