Search Results pol_global_attribute20

Overview

APPS.AP_PO_LINES_EXTRACT_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. As its name implies, the view exposes purchase order line information in a denormalized, extract-oriented format suitable for downstream consumption by external systems, interfaces, and custom reports. The object is registered in the E-Business Suite Tables and Views Repository (ETRM) under the FND Design Data identifier SQLAP.AP_PO_LINES_EXTRACT_V and carries a status of VALID. Its design centers on surfacing the descriptive flexfield (DFF) columns associated with purchase order lines, including the full AP_PO_LINES_ALL attribute range, in a single flat structure that avoids the joins typically required when querying PO_LINES_ALL directly.

The view is particularly relevant to users searching for "pol_attribute15," since it explicitly exposes the POL_ATTRIBUTE15 column (VARCHAR2(150)), which corresponds to the fifteenth descriptive flexfield segment of the purchase order line. This makes the view a convenient target for extracting flexfield segment values without navigating the attribute category setup that governs the underlying base table.

Underlying Base Objects

Per the documented ETRM metadata for Release 12.2.2, the view is defined over a single referenced base object: PO_LINES_ALL, accessed through a synonym. PO_LINES_ALL is the core transactional table storing purchase order line records in Oracle Purchasing. The view acts as a projection over that table, renaming and re-sequencing its columns into an extract-friendly layout. Because the view is owned by APPS and references PO_LINES_ALL via a synonym, it inherits the standard APPS schema security model: grants and synonyms must be in place for any custom schema to query the view directly. No additional joins to PO_HEADERS_ALL, PO_LINE_LOCATIONS_ALL, or PO_DISTRIBUTIONS_ALL are documented, so the view returns line-level data only and does not include shipment or distribution context.

Key Columns

• PO_LINE_ID — The unique identifier of the purchase order line. This is the primary join key back to PO_LINES_ALL and to related Purchasing tables.
• POL_LINE_TYPE_ID — The line type identifier, typically referencing the purchasing line type lookup.
• POL_LINE_NUM — The line number as displayed on the purchase order.
• POL_ITEM_DESCRIPTION — The item description text (VARCHAR2(240)) associated with the line.
• POL_ATTRIBUTE_CATEGORY — The descriptive flexfield context (attribute category) applied to the line.
• POL_ATTRIBUTE1 … POL_ATTRIBUTE15 — The fifteen descriptive flexfield segments, each VARCHAR2(150). POL_ATTRIBUTE15 is the column of interest for users searching on that term; it holds the value of the fifteenth DFF segment, whose meaning is determined by the attribute category.
• POL_GLOBAL_ATTRIBUTE_CATEGORY and POL_GLOBAL_ATTRIBUTE1 … POL_GLOBAL_ATTRIBUTE20 — The global descriptive flexfield context and its twenty segments (each VARCHAR2(150)), used for global DFF data.
• POL_LINE_REFERENCE_NUM — A VARCHAR2(25) reference number associated with the line.

Common Use Cases and Queries

The view is typically used to extract purchase order line data together with flexfield values for integration with external procurement, analytics, or archival systems. A common query retrieves POL_ATTRIBUTE15 for a specific line or attribute category:

• Flexfield segment reporting: SELECT PO_LINE_ID, POL_LINE_NUM, POL_ATTRIBUTE_CATEGORY, POL_ATTRIBUTE15 FROM APPS.AP_PO_LINES_EXTRACT_V WHERE POL_ATTRIBUTE15 IS NOT NULL;
• Line detail extraction by category: SELECT PO_LINE_ID, POL_LINE_NUM, POL_ITEM_DESCRIPTION, POL_ATTRIBUTE1, POL_ATTRIBUTE15 FROM APPS.AP_PO_LINES_EXTRACT_V WHERE POL_ATTRIBUTE_CATEGORY = :category;
• Global flexfield extraction: SELECT PO_LINE_ID, POL_GLOBAL_ATTRIBUTE_CATEGORY, POL_GLOBAL_ATTRIBUTE1 FROM APPS.AP_PO_LINES_EXTRACT_V WHERE POL_GLOBAL_ATTRIBUTE_CATEGORY IS NOT NULL;
• Join to purchase order headers: join PO_LINE_ID to PO_LINES_ALL and onward to PO_HEADERS_ALL to obtain vendor, order number, and date context not carried by the view itself.

Because the view is a thin projection over PO_LINES_ALL, query performance is governed by the base table's indexes on PO_LINE_ID and its organization-based access paths. Responsibility-based security is not applied within the view, so consumers must enforce any required operating unit or organization filtering in their own SQL.