Search Results po_lines_interface_u1

Overview

PO.PO_LINES_INTERFACE is the open interface table in the Oracle Purchasing (PO) schema that stages purchase order line and shipment information for processing by the Purchasing Documents Open Interface (PDOI) program. In Oracle EBS 12.1.1 and 12.2.2, external systems, legacy conversions, and custom concurrent programs populate this table, and PDOI subsequently validates the rows, derives or defaults additional attributes, creates the resulting standard purchase orders, blanket purchase agreements, contracts, and catalog quotations, and writes any validation failures to PO_INTERFACE_ERRORS. The table is owned by the PO schema, carries FND Design Data reference PO.PO_LINES_INTERFACE, has status VALID, and resides in the APPS_TS_INTERFACE tablespace with a PCTFREE of 10.

The object participates in several business entity categories, including PO_STANDARD_PURCHASE_ORDER, PO_BLANKET_PURCHASE_AGREEMENT, PO_CONTRACT_PURCHASE_AGREEMENT, PO_PRICE_BREAKS, and the global blanket and contract agreement categories. From a Data Vault modeling perspective, the metadata's heuristic classification is standalone, suggesting the table behaves primarily as an independent staging structure rather than as a classic hub, link, or satellite. In practice it resembles a transient staging satellite keyed on INTERFACE_LINE_ID, with INTERFACE_HEADER_ID linking line rows to their header context in PO_HEADERS_INTERFACE.

Key Information Stored

The table contains 256 documented columns. The most operationally significant are summarized below.

• INTERFACE_LINE_ID — the mandatory surrogate primary key and interface line unique identifier. It is enforced by the unique index PO_LINES_INTERFACE_U1, which the user's search term (po_lines_interface_u1) refers to directly. This is the only documented uniqueness constraint and therefore the sole business-key candidate.
• INTERFACE_HEADER_ID — mandatory foreign reference to the corresponding header row, forming the parent-child relationship between interface headers and lines.
• ACTION — indicates whether the row is a New or Add operation.
• LINE_NUM — the document line number assigned to the resulting purchase order line.
• LINE_TYPE and LINE_TYPE_ID — distinguish Goods, Services, and other line categories; LINE_TYPE_ID references PO_LINE_TYPES_B.
• ITEM, ITEM_ID, and ITEM_REVISION — the inventory item identity and revision.
• CATEGORY and CATEGORY_ID — purchasing category assignment.
• UOM_CODE, QUANTITY, and UNIT_PRICE — core pricing and quantity values used to build the line.
• SHIPMENT_NUM and SHIPMENT_TYPE — shipment-level attributes written alongside the line.
• REQUISITION_LINE_ID and PO_LINE_ID — source requisition reference and the target PO line identifier after processing.
• PROCESSING_ID — the run identifier that groups interface rows belonging to a single PDOI execution.
• REQUEST_ID, PROGRAM_ID, and LAST_UPDATE_DATE — the standard concurrent program and audit stamp columns.

Foreign keys documented for this table include PO_RELEASE_ID to PO_RELEASES_ALL, LINE_TYPE_ID to PO_LINE_TYPES_B, UN_NUMBER_ID to PO_UN_NUMBERS_B, HAZARD_CLASS_ID to PO_HAZARD_CLASSES_B, and AUCTION_HEADER_ID to PON_AUCTION_HEADERS_ALL.

Common Use Cases and Queries

The primary use case is bulk loading purchase order lines for PDOI. A typical load inserts one row per line/shipment, assigns INTERFACE_LINE_ID from a sequence, sets INTERFACE_HEADER_ID to the already-loaded header, and then submits the PDOI concurrent program. Common reporting and troubleshooting queries include:

• Retrieving all lines for a specific interface header: SELECT interface_line_id, line_num, item, quantity, unit_price FROM po.po_lines_interface WHERE interface_header_id = :header_id ORDER BY line_num;
• Isolating rows from a specific PDOI run: SELECT * FROM po.po_lines_interface WHERE processing_id = :processing_id;
• Verifying a unique line identifier before update: SELECT * FROM po.po_lines_interface WHERE interface_line_id = :line_id;
• Joining back to the header interface to confirm grouping: SELECT l.interface_line_id, l.line_num, h.interface_header_id FROM po.po_lines_interface l JOIN po.po_headers_interface h ON l.interface_header_id = h.interface_header_id;

Typical scenarios include legacy PO conversion, inbound integration from external procurement systems, and mass creation of blanket agreements or catalog quotations where price break and contract line attributes are supplied. The non-unique indexes N2 through N8 support filtering by header/line type, line number, requisition line, auction identifiers, category, PO line, and processing run.

Related Objects

The following objects are most directly associated with PO_LINES_INTERFACE:

• PO.PO_INTERFACE_ERRORS — receives validation error messages generated by PDOI for each failing row.
• PO.PO_LINE_TYPES_B — referenced by LINE_TYPE_ID and supplies valid line type values.
• PO.PO_RELEASES_ALL — referenced by PO_RELEASE_ID for release-level line handling.
• PO.PO_UN_NUMBERS_B — referenced by UN_NUMBER_ID for hazardous material identification.
• PO.PO_HAZARD_CLASSES_B — referenced by HAZARD_CLASS_ID for hazard classification.
• PON.PON_AUCTION_HEADERS_ALL — referenced by AUCTION_HEADER_ID for sourcing/auction-related lines.
• PO.PO_HEADERS_INTERFACE — the header-level companion table joined on INTERFACE_HEADER_ID.

Together these objects form the complete PDOI staging and validation framework that converts interface data into live purchasing documents.