Search Results po_lines_all_ext_b




Overview
Explore in AI Chat

Overview

PO_LINES_ALL_EXT_B is a Purchasing (PO) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas, owned by the PO schema. It stores user-defined attribute (UDA) data associated with purchase document lines, covering purchase orders, purchase agreements, quotations, and RFQs. In EBS, the "EXT" naming convention denotes extensibility storage, and this table provides the physical persistence for descriptive flexfield (DFF) and UDA values that purchasing professionals enter against line-level transactions without requiring schema modifications. Its status is VALID in the data dictionary.

The ETRM metadata classifies this object heuristically as standalone under its Data Vault modelling suggestion. This reflects the fact that the table carries a foreign key to PO_DRAFTS via DRAFT_ID but otherwise participates in relatively few enforced referential constraints; a Data Vault model would therefore likely treat it as a satellite or standalone descriptive structure rather than a true hub or link. Practitioners should treat this classification as a modelling hint, not a functional limitation.

Key Information Stored

The table contains 106 documented columns. The most structurally significant are:

  • EXTENSION_ID — the surrogate identifier for each UDA record, functioning as the primary key for individual extension rows.
  • PO_LINE_ID — the business-key candidate linking the extension record to its parent purchase document line; this is the principal join column to PO_LINES_ALL.
  • ATTR_GROUP_ID — identifies the attribute group (context) to which the UDA values belong, mapping back to descriptive flexfield context definitions.
  • DATA_LEVEL_ID — indicates the level at which the UDA data applies within the document hierarchy.
  • PK1_VALUE through PK5_VALUE — reserved key segments used by the flexfield infrastructure to qualify the extension record.
  • C_EXT_ATTR1 to C_EXT_ATTR40 — forty character-format UDA columns holding alphanumeric descriptive flexfield values.
  • N_EXT_ATTR1 to N_EXT_ATTR20 — twenty numeric-format UDA columns.
  • UOM_EXT_ATTR1 to UOM_EXT_ATTR20 — twenty columns storing unit-of-measure-associated attribute values.
  • D_EXT_ATTR1 to D_EXT_ATTR10 — ten date-format UDA columns.
  • UDA_TEMPLATE_ID — references the template that governs which attributes are active for the record.
  • DRAFT_ID — foreign key to PO_DRAFTS, used in the draft/change-management workflow.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who-column auditability.

The surrogate key is EXTENSION_ID; PO_LINE_ID combined with ATTR_GROUP_ID serves as the practical business-key candidate for locating a specific line's UDA set.

Common Use Cases and Queries

Because UDA values are stored generically rather than as named columns, reporting typically joins this table back to PO_LINES_ALL and PO_HEADERS_ALL to translate EXTENSION_ID values into readable business context. A representative pattern retrieves all character attributes for a given purchase order line:

  • Join PO_LINES_ALL_EXT_B to PO_LINES_ALL on PO_LINE_ID to associate UDA values with line numbers and items.
  • Join further to PO_HEADERS_ALL on PO_HEADER_ID to report UDA data by supplier, document type, and operating unit.
  • Filter on ATTR_GROUP_ID or UDA_TEMPLATE_ID to isolate a specific flexfield context rather than returning all 106 columns.
  • Use DRAFT_ID to reconcile UDA values captured in draft purchase orders against their finalised versions.

Typical scenarios include audits of negotiated terms captured as UDA values, supplier performance extracts, and migration scripts that populate descriptive flexfield data during implementations.

Related Objects

  • PO_DRAFTS — referenced via PO_LINES_ALL_EXT_B.DRAFT_ID; supports the draft document workflow.
  • PO_LINES_ALL — the parent line table joined on PO_LINE_ID.
  • PO_HEADERS_ALL — provides document-level context for line extensions.
  • PO_LINE_LOCATIONS_ALL — shipment and distribution detail often reported alongside line UDAs.
  • FND_DESCR_FLEX_CONTEXTS and the PO descriptive flexfield definitions — supply the ATTR_GROUP_ID context mapping.

When the metadata does not document an index explicitly, consultants should confirm indexing on PO_LINE_ID before writing high-volume extracts.