Results for “po_asl_documents_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO.PO_ASL_DOCUMENTS is a transactional table in the Oracle Purchasing (PO) schema that stores sourcing references between approved supplier list entries and the supply agreements, blanket agreements, and catalog quotations that qualify a given supplier-item combination. Each row links a record in PO_APPROVED_SUPPLIER_LIST to a specific sourcing document, capturing the rank and type of that document so the sourcing engine can determine preferred sources during requisition, sourcing, and auto-sourcing operations. The table is owned by PO and resides in the APPS_TS_TX_DATA tablespace with PCT Free 10. It is flagged as VALID and is registered under FND Design Data as PO.PO_ASL_DOCUMENTS. Its columns follow the standard EBS pattern, including WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), a REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE concurrent request set, an ORG_ID multi-org column, and sixteen descriptive flexfield segments (ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE16). From a Data Vault modeling perspective, the metadata's heuristic classification for this object is standalone, meaning it is not decomposed into hub, link, or satellite constructs by the mining rules, though functionally its ASL_ID foreign key to PO_APPROVED_SUPPLIER_LIST suggests a natural link-and-attribute role between the ASL hub and referenced documents.

Key Information Stored

The most important columns include:

• ASL_ID — the unique identifier of the parent PO_APPROVED_SUPPLIER_LIST row; this is the primary foreign key relationship documented for the table.
• USING_ORGANIZATION_ID — the ship-to organization that uses this sourcing record.
• DOCUMENT_HEADER_ID — the header identifier of the referenced agreement or quotation.
• DOCUMENT_LINE_ID — the specific line within the referenced document, when applicable.
• DOCUMENT_TYPE_CODE — a VARCHAR2(25) value identifying the nature of the referenced sourcing document (for example, blanket, contract, or quotation).
• SEQUENCE_NUM — establishes the ranking or priority of the document for the supplier-item pairing.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard WHO audit columns.
• ORG_ID — the operating unit context for multi-org security.

The unique index PO_ASL_DOCUMENTS_U1 on (ASL_ID, USING_ORGANIZATION_ID, DOCUMENT_HEADER_ID) is the documented business-key candidate, enforcing that a given ASL entry cannot reference the same document header more than once per using organization. The table does not define a separate single-column surrogate primary key in the documented metadata; the composite unique index functions as the effective business key.

Common Use Cases and Queries

Typical scenarios include identifying all sourcing documents attached to a supplier-item ASL entry, ranking those documents for auto-sourcing, and reproducing the source selection behind a purchase order. Example queries:

• List all documents for an ASL entry: SELECT DOCUMENT_TYPE_CODE, DOCUMENT_HEADER_ID, SEQUENCE_NUM FROM PO.PO_ASL_DOCUMENTS WHERE ASL_ID = :p_asl_id ORDER BY SEQUENCE_NUM;
• Find ASL entries sourcing from a specific agreement: SELECT ASL_ID, USING_ORGANIZATION_ID FROM PO.PO_ASL_DOCUMENTS WHERE DOCUMENT_HEADER_ID = :p_header_id;
• Multi-org scoped reporting: filter by ORG_ID and USING_ORGANIZATION_ID to align with operating unit security.

These patterns are commonly used in sourcing diagnostics, approved supplier list reports, and custom reconciliation of blanket and catalog quoting behavior.

Related Objects

• PO.PO_APPROVED_SUPPLIER_LIST — the parent table referenced via ASL_ID; the core join for supplier-item sourcing.
• PO.PO_HEADERS_ALL — the header table implied by DOCUMENT_HEADER_ID for agreements and quotations.
• PO.PO_LINES_ALL — source lines referenced by DOCUMENT_LINE_ID.
• PO_ASL_DOCUMENTS_U1 — the unique index enforcing the composite business key.
• FND_USER — join via LAST_UPDATED_BY and CREATED_BY for audit attribution.