Results for “line_type_pk”

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

Overview

EDW_POA_LN_TYPE_LCV is a validation view owned by the APPS schema within the Oracle E-Business Suite Purchasing (PO) module. It is classified as a "LCV" object, the naming convention Oracle uses for list-of-values (LOV) validation views, indicating that it exists primarily to drive lookup and selection lists in Oracle Forms, OAF pages, and related reporting or integration layers. The view exposes a set of line type attributes associated with purchasing document lines, including descriptive and control fields such as the line type name, description, order type, outside-operation flag, and inactive date.

Although the object is documented under the PO - Purchasing product, its EDW_ prefix and the presence of a LAST_UPDATE_DATE/CREATION_DATE pair suggest it is used within the Oracle Enterprise Data Warehouse (EDW) or ETRM analytics context, presenting purchasing line type reference data in a denormalized, presentation-ready format. In EBS 12.1.1 and 12.2.2, such views are typically referenced by BI Publisher reports, Oracle Discoverer workbooks, and custom validation code rather than by core transactional forms.

Underlying Base Objects

The ETRM metadata documents the view as having no formally referenced base objects. This is not unusual for ETRM documentation, which often lists only the view text header and column list when the underlying dependencies are undocumented. Based on the column set and naming conventions, the view is defined over the purchasing line type / order type tables (the PO_LINE_TYPES_B/_TL family and related order-type definitions) and is populated via a SELECT statement listing the columns enumerated in the metadata: LINE_TYPE_PK, LAST_UPDATE_DATE, CREATION_DATE, LINE_TYPE_DP, NAME, INSTANCE, DESCRIPTION, ORDER_TYPE, OUTSIDE_OP_FLAG, INACTIVE_DATE, PLTDR_CONTEXT, and USER_ATTRIBUTE1 through USER_ATTRIBUTE5.

The _LCV suffix and the "View Text" placeholder in the documentation confirm it is a stored database view rather than a synonym or table, with status VALID in the APPS schema. Its dependency chain is concealed behind the EDW prefix but functionally maps to Purchasing line type reference data.

Key Columns

• LINE_TYPE_PK — Primary key of the underlying line type record; used as the LOV return value.
• NAME / DESCRIPTION — Human-readable identifiers displayed in list-of-values selections.
• LINE_TYPE_DP — Display value for the line type, commonly concatenated for LOV presentation.
• INSTANCE — Discriminator distinguishing whether the line type applies to purchasing documents, requisitions, or other document classes.
• ORDER_TYPE — Associates the line type with an order-type classification.
• OUTSIDE_OP_FLAG — Indicates whether the line type supports outside processing operations.
• INACTIVE_DATE — Effective end date; NULL indicates an active record, permitting the LOV to filter inactive entries.
• PLTDR_CONTEXT — Descriptive flexfield context identifier carried through for DFF-enabled line types.
• USER_ATTRIBUTE1–5 — DFF attribute columns exposed for descriptive flexfield reporting.
• LAST_UPDATE_DATE / CREATION_DATE — Audit columns supporting incremental extraction and ETL logic.

Common Use Cases and Queries

The view is typically queried to populate drop-down selections or to extract line type reference data into reporting datasets. A representative query restricting to active line types is:

SELECT line_type_pk, name, description, line_type_dp, order_type FROM apps.edw_poa_ln_type_lcv WHERE inactive_date IS NULL ORDER BY name;

For ETL or warehouse loading, the audit columns support delta extraction:

SELECT * FROM apps.edw_poa_ln_type_lcv WHERE last_update_date >= :p_since_date;

Because the metadata documents no base objects, validations against this view in EBS 12.1.1/12.2.2 should be treated as read-only lookups, and any customization should reference the view rather than its presumed underlying tables to preserve upgrade safety.