Results for “po_lines_all_ext_b_archive”

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

Overview

The PO_LINES_ALL_EXT_B_ARCHIVE table in the PO (Purchasing) schema stores archived user-defined attribute (UDA) data associated with purchase document lines, covering purchase orders and purchase agreements. It is a companion archive to the transient base table PO_LINES_ALL_EXT_B, which holds the descriptive flexfield and extensibility attribute values captured against line-level records during the document lifecycle. When a purchase document is archived through the standard Purchasing archival process, its associated UDA lines are migrated into this table so that the historical attribute snapshot remains queryable without inflating the active transaction tables.

From a data modeling perspective, the metadata's heuristic Data Vault classification is standalone. This reflects the fact that the table carries its own composite primary key (EXTENSION_ID, REVISION_NUM) and a single documented foreign key relationship, rather than participating in a dense hub-and-link network. Practitioners following a Data Vault approach may therefore treat this object as a satellite-like entity, keyed by its extension identifier and revision, with attributes describing the archived extensibility payload. Because the table is populated only by archival activity, it is read-only in normal application use.

Key Information Stored

The table contains 108 documented columns in the 12.2.2 physical schema. The most operationally significant are:

• EXTENSION_ID — Component of the composite primary key PO_LINES_ALL_EXT_B_ARCH_PK; the surrogate identifier linking the archived attribute row back to its originating extension record.
• REVISION_NUM — Second component of the primary key; distinguishes successive revisions of the same extension, supporting audit trails of attribute changes.
• PO_LINE_ID — The business foreign key pointing to the purchase document line (PO_LINES_ALL) whose attributes were archived. This is the primary join path for line-level reporting.
• ATTR_GROUP_ID — Identifies the attribute group or context under which the UDA values were captured.
• DATA_LEVEL_ID — Indicates the data level at which attributes were defined.
• UDA_TEMPLATE_ID — References the extensibility template that governed the attribute set.
• PK1_VALUE through PK5_VALUE — Business key value segments used to resolve the archived attribute record against its source context.
• C_EXT_ATTR1 through C_EXT_ATTR40 — Forty character-mode extensibility attribute columns holding archived alphanumeric UDA values.
• N_EXT_ATTR1 through N_EXT_ATTR20 — Twenty numeric UDA columns for archived numeric values.
• D_EXT_ATTR1 through D_EXT_ATTR10 — Ten date-mode UDA columns.
• UOM_EXT_ATTR1 through UOM_EXT_ATTR20 — Twenty UOM-qualified numeric attribute columns for values expressed with a unit of measure.
• DRAFT_ID — Foreign key to PO_DRAFTS, the sole documented FK relationship, tying the archived row to a draft document context.
• LATEST_EXTERNAL_FLAG — Indicates whether the archived row represents the most recent externally visible revision.
• Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical usage centers on historical reporting and audit reconciliation of descriptive flexfield values that are no longer present in the active base table. A common pattern joins the archive to PO_LINES_ALL on PO_LINE_ID to reconstruct the attribute state of a line at archive time:

• Attribute history for a specific line: SELECT a.po_line_id, a.revision_num, a.c_ext_attr1, a.c_ext_attr2, a.n_ext_attr1 FROM po.po_lines_all_ext_b_archive a WHERE a.po_line_id = :line_id ORDER BY a.revision_num;
• Draft-linked archive extraction: join to PO_DRAFTS on DRAFT_ID to report attributes belonging to a draft workflow.
• Template-driven reporting: filter by UDA_TEMPLATE_ID or ATTR_GROUP_ID to isolate attributes belonging to a specific extensibility configuration.
• Latest-revision filtering: restrict to rows where LATEST_EXTERNAL_FLAG identifies the current external snapshot, avoiding duplication across REVISION_NUM values.
• Data migration and reconciliation: compare archived UDA payloads against the live PO_LINES_ALL_EXT_B rows during upgrades from 12.1.1 to 12.2.2, since extensibility structures and archive behavior differ between these releases.

Because the table is archival, queries should generally be read-only, and reporting extracts should filter on CREATION_DATE or LAST_UPDATE_DATE to bound scan ranges.

Related Objects

• PO_LINES_ALL_EXT_B — The active base table from which archived rows are sourced; shares the same extensibility column layout.
• PO_LINES_ALL — The purchase document line master, joined via PO_LINE_ID.
• PO_DRAFTS — Referenced by the documented foreign key PO_LINES_ALL_EXT_B_ARCHIVE.DRAFT_ID.
• PO_HEADERS_ALL — Parent header context reachable through the line relationship.
• PO_LINES_ALL_EXT_A and related extension tables — Sibling extensibility tables covering other attribute segments.
• FND_DESCR_FLEX_COLUMN_USAGES / FND_FLEX_VALUES — Flexfield metadata used to translate C_EXT_ATTR and N_EXT_ATTR columns into user-recognizable segment labels.
• PO_ARCHIVE APIs and concurrent programs — The archival processes responsible for populating this table.