Results for “po_asl_documents”

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

Overview

PO.PO_ASL_DOCUMENTS is a Purchasing (PO) module table that stores the documents attached to an Approved Supplier List (ASL) entry. In Oracle EBS, the ASL is the master record that authorizes a specific supplier, supplier site, and item combination for sourcing. While the ASL header itself is held in PO_APPROVED_SUPPLIER_LIST, supporting artifacts — quality certifications, audit reports, compliance certificates, drawings, contract references, or other documentary evidence — are captured as individual rows in PO_ASL_DOCUMENTS. Each row links a document header (and optionally a document line) to a specific ASL record scoped by operating unit (organization).

The table resides in the PO schema and is classified as VALID in both EBS 12.1.1 and 12.2.2. From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone. This is a modeling suggestion only: while the object carries a foreign key to PO_APPROVED_SUPPLIER_LIST, the mined FK structure does not point to a broader set of hub entities, so it is treated as an independent structure rather than a classic link table. In practice it behaves as a satellite-style detail table hanging off the ASL hub.

Key Information Stored

The physical schema documents 32 columns. The most business-significant columns are:

• ASL_ID — Foreign key to PO_APPROVED_SUPPLIER_LIST; identifies the owning ASL record. This is the anchor for every document row.
• USING_ORGANIZATION_ID — The operating unit / inventory organization context in which the ASL document is used. Scopes the document to a specific organization.
• DOCUMENT_HEADER_ID — Reference to the document header (typically an attachment record).
• DOCUMENT_LINE_ID — Optional reference to a specific document line.
• DOCUMENT_TYPE_CODE — Classifies the nature of the document attached.
• SEQUENCE_NUM — Ordering sequence for multiple documents on one ASL.
• ORG_ID — Operating unit identifier used for multi-org security (MOAC) filtering.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context that created or updated the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard DFF (Descriptive Flexfield) columns for extensible customer-defined data.

The unique index PO_ASL_DOCUMENTS_U1 is defined on (ASL_ID, USING_ORGANIZATION_ID, DOCUMENT_HEADER_ID), which serves as the business-key candidate ensuring no duplicate document header is attached to the same ASL within the same organization. There is no documented single-column surrogate primary key for this table; the unique index is the closest business-key representation.

Common Use Cases and Queries

Typical use cases include auditing which documents support a given supplier approval, verifying that required certifications exist before sourcing, and reporting on compliance coverage by organization.

A common pattern joins this table to the ASL header and the supplier to list all documents for a supplier item:

• Join PO_ASL_DOCUMENTS d to PO_APPROVED_SUPPLIER_LIST a on d.ASL_ID = a.ASL_ID.
• Filter by d.ORG_ID or d.USING_ORGANIZATION_ID to respect MOAC.
• Use DOCUMENT_TYPE_CODE to isolate, for example, quality certificates.
• Join outward to supplier and item tables (via the ASL) to resolve vendor name and item description.

Count-based queries such as "which ASL records have no attached documents" (NOT EXISTS against PO_ASL_DOCUMENTS) are useful compliance-gap reports. The REQUEST_ID/PROGRAM_ID columns enable traceability back to the concurrent program that inserted the data.

Related Objects

• PO_APPROVED_SUPPLIER_LIST — Parent table; join on PO_ASL_DOCUMENTS.ASL_ID = PO_APPROVED_SUPPLIER_LIST.ASL_ID. This is the documented foreign key relationship.
• PO_ASL_ATTRIBUTES — Stores additional attribute detail for the same ASL records.
• PO_ASL_STATUS_HISTORY — Tracks status changes on ASL entries that these documents support.
• PO_VENDORS / PO_VENDOR_SITES_ALL — Resolved through the ASL to identify the supplier.
• FND_ATTACHED_DOCUMENTS — The functional attachment framework that typically backs DOCUMENT_HEADER_ID references.
• FND_DOCUMENTS / FND_DOCUMENT_ENTITIES — Attachment metadata resolved via the document header id.
• PO_ASL_DOCUMENTS itself participates in DFF storage via ATTRIBUTE1–15 and ATTRIBUTE_CATEGORY, governed by the ASL Documents descriptive flexfield definition.