Results for “document_line_id”

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

Overview

PO_AUTOSOURCE_DOCUMENTS_ALL is a table in the Oracle Purchasing (PO) schema within Oracle E-Business Suite, holding records that associate sourcing rules with specific purchasing documents such as requisitions, quotations, and purchase orders. In ETRM 12.1.1 and 12.2.2 documentation, the object carries a description of "No longer used," indicating that it is a legacy or deprecated table retained for backward compatibility and historical data reference rather than active functional processing. Despite this status, the table remains VALID in the schema and is still defined with a full column set and referential constraints, which means DBAs and technical consultants may encounter it in older customizations, migrations, or archival extracts.

The heuristic Data Vault classification for this object is link, mined from its foreign key structure. This classification suggests modeling the table as a relationship construct that connects sourcing rules, vendors, and purchasing document headers and lines, rather than as a hub of business entities or a satellite of descriptive attributes. The link classification reflects the table's apparent purpose of resolving many-to-many associations between autosource rules and the documents they apply to.

Key Information Stored

The physical schema documents 33 columns. The following are the most significant for understanding row identity and meaning:

• AUTOSOURCE_RULE_ID — foreign key to PO_AUTOSOURCE_RULES, identifying the sourcing rule that qualifies the row.
• VENDOR_ID — foreign key to PO_VENDORS, identifying the supplier associated with the document.
• SEQUENCE_NUM — ordinal value used to order multiple documents for a rule/vendor combination.
• DOCUMENT_TYPE_CODE — code describing the type of purchasing document (for example, requisition, quotation, or purchase order).
• DOCUMENT_HEADER_ID — foreign key to PO_HEADERS_ALL, pointing to the document header.
• DOCUMENT_LINE_ID — foreign key to PO_LINES_ALL, pointing to the specific document line.
• DOC_GENERATION_METHOD — indicates the method by which the associated document was generated.
• ORG_ID — operating unit identifier supporting multi-org partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield segments for extensibility.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns recording the process that last touched the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard who-column audit trail.

The surrogate primary key is PO_AUTOSOURCE_DOCUMENTS_PK on (AUTOSOURCE_RULE_ID, VENDOR_ID, SEQUENCE_NUM). The unique index PO_AUTOSOURCE_DOCUMENTS_U1 extends this business key with ORG_ID, making the operating-unit-aware composite the strongest uniqueness candidate.

Common Use Cases and Queries

Although marked as no longer used, the table surfaces in historical reporting, data migration reconciliations, and archival queries. A typical pattern joins the table to its parent purchasing documents:

• Listing documents associated with a sourcing rule: SELECT * FROM po_autosource_documents_all WHERE autosource_rule_id = :rule_id ORDER BY sequence_num;
• Linking to suppliers and headers: SELECT d.autosource_rule_id, d.vendor_id, h.segment1, h.type_lookup_code FROM po_autosource_documents_all d, po_headers_all h WHERE d.document_header_id = h.po_header_id;
• Auditing by concurrent request: filtering on PROGRAM_ID or REQUEST_ID to trace which process populated or updated rows.
• Validating multi-org extracts by grouping on ORG_ID.

Reporting use cases include historical sourcing-rule traceability, gap analysis when migrating to newer sourcing functionality, and verification that legacy autosource assignments were retained during upgrades.

Related Objects

• PO_AUTOSOURCE_RULES — parent table joined via AUTOSOURCE_RULE_ID.
• PO_VENDORS — supplier master joined via VENDOR_ID.
• PO_HEADERS_ALL — document header joined via DOCUMENT_HEADER_ID.
• PO_LINES_ALL — document line joined via DOCUMENT_LINE_ID.

These relationships confirm the table's role as a link between sourcing rules, vendors, and purchasing documents, and they define the primary join paths for any historical extraction or reconciliation effort.