Search Results txn_cur_code_fk_key




Overview
Explore in AI Chat

Overview

POA_EDW_ALINES_F_IV is a database view historically shipped with Oracle Purchasing Intelligence (POA), the predecessor of the Oracle Procurement and Spend Analytics family of E-Business Suite applications. It is a "F_IV" family object, indicating that it exposes the interface-level or incremental-version projection of purchasing agreement lines destined for an Enterprise Data Warehouse (EDW) fact table. In Oracle EBS 12.1.1 and 12.2.2 the object is documented as obsolete, and the ETRM metadata explicitly records that it is not implemented in this database. Consequently, the view should be treated as a legacy reference for upgrade and migration analysis rather than a run-time reporting source.

Its role was to normalize purchasing document line attributes — agreement identifiers, pricing, quantities, supplier and site references, currency and UOM conversions — into the standardized, surrogate-keyed column set expected by the Purchasing Intelligence star schema. The column names carrying the _FK_KEY suffix are the EDW foreign keys that resolve to the intelligence dimension tables, which is why almost every descriptive column is paired with a numeric key rather than a raw value.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, but the view SQL terminates in FROM POA ..., indicating that the FROM clause resolves to a POA-owned source object (typically a staging or interface table such as the agreement-lines extract used by the EDW load). The projection is a flat, single-row-per-line result: no joins appear in the documented text, so all denormalization was performed upstream. The ROWID ROW_ID in the first position provides a row locator for incremental extract/change-capture handling.

Because the object is not implemented in the current database, DBAs should verify existence with ALL_VIEWS or ALL_OBJECTS before referencing it, and expect it to be absent in a clean 12.1.1 or 12.2.2 installation where POA is not licensed or has been superseded.

Key Columns

Common Use Cases and Queries

Legacy reports built on this view were primarily price-comparison and agreement-compliance extracts. A representative query retrieving negotiated versus market pricing by item:

SELECT item_id, item_description, unit_price_t, market_price_t,
  txn_cur_code_fk_key
FROM poa_edw_alines_f_iv
WHERE agree_ln_inst_pk = :p_agreement_line_id;

Other practical scenarios include reconciliation of extracted agreement lines against PO_LINE_ID in the base purchasing tables, verification of quantity consumption by comparing QTY_AGREED_T with QTY_RELEASED_T, and auditing currency conversion coverage through the TXN_CUR_RATE_FK_KEY dimension link. Because the view is documented as not implemented and obsolete in 12.1.1/12.2.2, any such query should first confirm object existence; where it is absent, the equivalent purchasing agreement line data must be sourced from the current Procurement and Spend Analytics views or directly from the purchasing tables.