Search Results lp_attribute_category




Overview
Explore in AI Chat

Overview

APPS.ECE_POCO_LINES_V is a denormalized reporting and integration view within the Oracle E-Business Suite E-Commerce Gateway (ECE) module. Its name follows the ECE convention of "POCO" (Purchase Order Change Order) plus a "_V" suffix indicating it is a view. The view consolidates purchase order line detail with header context, item definitions, hazard class information, UN number data, and system parameter defaults, producing a single wide row per purchase order line suitable for outbound procurement document extraction and interface processing.

In ETRM it is classified under the APPS schema and is commonly referenced by reports, custom concurrent programs, and interface tables that feed the ECE outbound 850/860 (Purchase Order / PO Change) document generation logic. Because ECE extracts flat records into interface tables before transforming them into EDI or XML, a single view that surfaces both PO-line attributes and their associated item and hazard descriptors greatly simplifies the extraction query used by such programs.

Underlying Base Objects

The view is documented as being defined over the following APPS synonyms: FINANCIALS_SYSTEM_PARAMETERS, MTL_SYSTEM_ITEMS_B, PO_HAZARD_CLASSES_B, PO_HAZARD_CLASSES_TL, PO_HEADERS, PO_HEADERS_ALL, PO_LINES, PO_LINES_ALL, PO_LINE_LOCATIONS, PO_LINE_TYPES, PO_RELEASES, PO_UN_NUMBERS_B, and PO_UN_NUMBERS_TL. These are references (synonyms) pointing to the underlying base tables owned by the relevant product schemas.

The principal line data is sourced from PO_LINES / PO_LINES_ALL. Header context (PO_NUMBER, vendor quote number, order type) comes from PO_HEADERS and PO_HEADERS_ALL, while the line's ship-to / ordering configuration is derived from PO_LINE_LOCATIONS. Item master attributes—specifically the descriptive flexfield (DFF) columns exposed as LP_ATTRIBUTE_CATEGORY, LP_ATTRIBUTE1 … LP_ATTRIBUTE15—are pulled from MTL_SYSTEM_ITEMS_B. Human-readable hazard descriptions are joined via PO_HAZARD_CLASSES_B/TL, and UN number information is joined via PO_UN_NUMBERS_B/TL. FINANCIALS_SYSTEM_PARAMETERS supplies default/system-level context, and PO_LINE_TYPES contributes ORDER_TYPE_LOOKUP_CODE.

Key Columns

Common Use Cases and Queries

The most frequent use of this view is to extract PO line detail for ECE outbound purchase order and purchase order change document generation. It also serves as a convenient ad-hoc query source when both line-level and item-level context are needed in one result set, and it is frequently used by reports resolving item descriptive flexfields (MTL_SYSTEM_ITEMS_B) alongside PO line details. Because the DFF columns are exposed with distinct prefixes, the view is particularly useful when reporting needs both the PO_LINES DFF values (POL_ATTRIBUTE*) and the item master DFF values (LP_ATTRIBUTE*).

Example query—retrieve PO lines including item-level DFF values:

  • SELECT po_number, line_num, item_id, item_description, lp_attribute_category, lp_attribute1, lp_attribute2, quantity, unit_price, uom_code FROM apps.ece_poco_lines_v WHERE po_number = :p_po_number ORDER BY line_num;

Example query—locate lines where a specific item flexfield is populated:

  • SELECT po_number, line_num, item_id, lp_attribute1 FROM apps.ece_poco_lines_v WHERE lp_attribute1 IS NOT NULL AND cancel_flag = 'N';

Because the view joins many large tables, always restrict results with the leading PO_NUMBER, ITEM_ID, or a date/status predicate to avoid full-table scans, and confirm the current DFF definition in the relevant flexfield registration before relying on LP_ATTRIBUTE1 semantics.