Search Results po_line_locations_all

The PO_LINE_LOCATIONS_ALL table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical entity within the Purchasing module, serving as the foundation for tracking shipment and delivery details associated with purchase order lines. This table stores information about scheduled shipments, quantities, pricing, and receiving details, ensuring accurate procurement execution. Below is a detailed analysis of its structure, key columns, relationships, and functional significance.

Table Overview

PO_LINE_LOCATIONS_ALL is part of the PO schema and acts as a child table to PO_LINES_ALL. Each record represents a shipment schedule for a specific purchase order line, enabling organizations to manage multiple deliveries for a single line item. The table is multi-org enabled, as indicated by the _ALL suffix, meaning it stores data across operating units while enforcing data security via ORG_ID.

Key Columns and Descriptions

• LINE_LOCATION_ID: Primary key, uniquely identifying each shipment line.
• PO_LINE_ID: Foreign key linking to PO_LINES_ALL, associating the shipment with a specific PO line.
• SHIPMENT_TYPE: Indicates whether the shipment is "Standard," "Blanket," or "Planned."
• QUANTITY: Ordered quantity for the shipment.
• QUANTITY_RECEIVED: Tracks received quantities against the shipment.
• QUANTITY_BILLED: Records invoiced quantities for matching with AP invoices.
• SHIP_TO_ORGANIZATION_ID: Identifies the inventory organization receiving the shipment.
• SHIP_TO_LOCATION_ID: Physical delivery location, tied to HR_LOCATIONS_ALL.
• NEED_BY_DATE: Expected delivery date for the shipment.
• PROMISED_DATE: Vendor-committed delivery date.
• PRICE_OVERRIDE: Allows deviation from the unit price defined in PO_LINES_ALL.
• TAXABLE_FLAG: Determines if the shipment is subject to tax.
• CLOSED_CODE: Status of the shipment (e.g., "OPEN," "CLOSED," "CANCELLED").

Functional Significance

The table plays a pivotal role in procurement workflows:

1. Shipment Scheduling: Enables splitting a single PO line into multiple deliveries with distinct dates, quantities, or destinations.
2. Receiving: Integrates with the RCV_TRANSACTIONS table to update QUANTITY_RECEIVED upon goods receipt.
3. Invoice Matching: Provides data for three-way matching (PO, receipt, invoice) in Accounts Payable.
4. Reporting: Supports analytics on delivery performance, vendor compliance, and procurement cycle times.

Relationships with Other Tables

• PO_LINES_ALL: Parent table via PO_LINE_ID.
• PO_HEADERS_ALL: Indirect relationship through PO_LINES_ALL.PO_HEADER_ID.
• RCV_SHIPMENT_LINES: Ties shipment details to receiving transactions.
• AP_INVOICE_LINES: Links to invoiced quantities via PO_DISTRIBUTIONS_ALL.

Technical Considerations

In EBS 12.2.2, the table benefits from Online Patching (ADOP) compatibility, ensuring uninterrupted operations during patches. Indexes such as PO_LINE_LOCATIONS_N1 (PO_LINE_ID) and PO_LINE_LOCATIONS_U1 (LINE_LOCATION_ID) optimize query performance. Customizations often extend the table via descriptive flexfields (DFFs) to capture organization-specific attributes.

Conclusion

PO_LINE_LOCATIONS_ALL is indispensable for granular procurement control, bridging purchase orders, logistics, and financial accountability. Its design reflects Oracle EBS's emphasis on flexibility, auditability, and integration across supply chain and financial modules. Understanding this table is essential for troubleshooting, custom reporting, and enhancing procurement automation.