Results for “operation_code”

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

Overview

The view EDW_POA_LN_TYPE_A_LTC_IV belongs to the Oracle E-Business Suite product family known as POA — Purchasing Intelligence. This module, which is now designated Obsolete, was originally delivered as part of Oracle's Enterprise Data Warehouse (EDW) and Business Intelligence infrastructure for procurement analytics. The IV suffix in the object name follows the EDW convention for an "interface view" or derived staging view used by extraction, transformation, and load routines to publish dimension and lookup data from the source EBS instance into the purchasing data warehouse.

In role and purpose, EDW_POA_LN_TYPE_A_LTC_IV presents a read-only projection over line type reference data. It is not a transactional object; rather, it exposes a set of key and descriptive attributes that downstream reports, materialized views, and ETL packages consume. Because POA is obsolete in the 12.1.1 and 12.2.2 releases, this view is not seeded or implemented in a standard database. The ETRM entry explicitly states "Not implemented in this database," confirming that on current deployments the definition exists only as documentation and would raise an ORA-00942 if referenced without custom creation.

Underlying Base Objects

The view is defined over a single base object, EDW_POA_LN_TYPE_A_LTC, which supplies the physical columns exposed through the SELECT list. The dependency is direct and uncomplicated, consisting of column mapping plus one literal expression, with a ROWID pseudo-column added for EDW change-tracking purposes. No joins, unions, aggregations, or filter predicates are present in the documented view text, and the ETRM metadata records no additional referenced base objects beyond this one table.

The base table name embeds several naming clues: POA (Purchasing Intelligence), LN_TYPE (line type), A (the "A" or active/base variant common in EDW staging), and LTC (likely a line type code or lookup characteristic). The view therefore acts as a thin interface layer over that table's contents.

Key Columns

• ROW_ID — Maps the table ROWID, providing a stable physical row identifier used by EDW incremental loads and change detection.
• ALL_PK — The all-primary-key column. This is the column matched by the user's search term "all_pk" and typically holds a concatenated or composite key representing the full unique identity of a line type record.
• NAME — The descriptive name of the line type, used as the display attribute in warehouse dimensions.
• ALL_PK_KEY — A key variant, generally the surrogate or foreign key referencing the ALL_PK value in related EDW entities, enabling joins across the warehouse schema.
• OPERATION_CODE — Emitted as a single space literal (' '), it is a placeholder column reserved for ETL change-data-capture signaling.

Common Use Cases and Queries

Typical consumption is from ETL jobs and analytical reports requiring line type lookups for purchasing facts. A representative query selecting the primary-key and name attributes would be:

• SELECT ALL_PK, ALL_PK_KEY, NAME FROM EDW_POA_LN_TYPE_A_LTC_IV;
• SELECT ROW_ID, ALL_PK, NAME FROM EDW_POA_LN_TYPE_A_LTC_IV WHERE ALL_PK = :p_key;

Practitioners should verify whether the underlying table has been created in the target instance before relying on this view, given its obsolete and unimplemented status.