Search Results month_booked_fk_key

Overview

The view EDW_CST_COGS_F_IV is an Oracle EBS Inventory (INV) reporting object that exposes cost-of-goods-sold (COGS) fact data in a denormalized, star-schema-oriented form intended for the Enterprise Data Warehouse (EDW). The suffix "IV" designates it as an "inventory view" variant, and the "F" notation identifies it as a fact-style extract. It surfaces transactional COGS amounts expressed in both transactional currency (COGS_T) and reporting/functional currency (COGS_G), together with a broad set of foreign-key surrogate references that map the fact row to conformed EDW dimensions.

In the context of Oracle EBS 12.1.1 and 12.2.2, this object is a warehouse-facing artifact rather than a transactional application view. It is typically created by the EBS data extraction and transformation layer that populates the EDW, allowing BI and reporting tools to join COGS facts against shared dimension tables. The metadata notes "Not implemented in this database," meaning the view is delivered as part of the EDW integration objects and exists only in environments where the warehouse schema has been deployed. Because the columns are surrogate-key driven, the view is optimized for dimensional modelling rather than for online transaction processing.

Underlying Base Objects

Per the documented metadata, the only referenced base object is the table EDW_CST_COGS_F. The view is a thin projection: it selects all significant columns from that table and appends a single derived column, ' ' OPERATION_CODE — a constant blank string used as a placeholder for the warehouse's change-data-capture or slowly-changing-dimension operation indicator. No joins, aggregations, or filters are applied, so the view is effectively a renamed and slightly extended interface over the base fact table. The documented referenced base objects list is otherwise empty, confirming that EDW_CST_COGS_F is the sole source.

Key Columns

• ROW_ID — the physical ROWID of the underlying row, retained for warehouse housekeeping.
• COGS_PK / COGS_PK_KEY — the primary key and its surrogate key form for the COGS fact record.
• COGS_T / COGS_G — COGS value in transaction and functional (reporting) currency respectively.
• RMA_VALUE_T / RMA_VALUE_G, RMA_QTY_B, SHIPPED_QTY_B — return and shipment value/quantity measures.
• PROMISE_LEAD_TIME, REQUEST_LEAD_TIME, ORDER_LEAD_TIME — fulfillment timing measures with early/late counts and values.
• TRX_CURRENCY_FK_KEY — the surrogate foreign key to the transaction currency dimension; the column named in the user's search and central to any currency-aware reporting query.
• Dimensional FK columns such as ORDER_CATEGORY_FK_KEY, INV_ORG_FK_KEY, ITEM_ORG_FK_KEY, LOCATOR_FK_KEY, CUSTOMER_FK_KEY, SHIP_TO_SITE_FK_KEY, BILL_TO_SITE_FK_KEY, TRX_DATE_FK_KEY, and OPERATING_UNIT_FK_KEY.
• Persistent item attributes: LOT, REVISION, SERIAL_NUMBER, WAYBILL_NUMBER.
• USER_ATTRIBUTE1–15 and USER_MEASURE1–5 — extensibility placeholders.
• LAST_UPDATE_DATE, CREATION_DATE — audit columns.
• OPERATION_CODE — constant blank placeholder added by the view.

Common Use Cases and Queries

The most common scenario is currency-aware COGS analysis, which is why TRX_CURRENCY_FK_KEY was the search term. A typical query joins the view to the currency dimension to report COGS by transactional currency and period:

• Reporting COGS by inventory organization, customer, and transaction currency for a fiscal period.
• Reconciling transactional-currency COGS (COGS_T) against functional-currency COGS (COGS_G) during period close.
• Measuring fulfillment performance via lead-time and early/late shipment counts and values.
• Feeding a star-schema fact load where the FK columns resolve to conformed dimensions.

Illustrative SQL:

• SELECT COGS_PK, INV_ORG_FK_KEY, TRX_CURRENCY_FK_KEY, COGS_T, COGS_G FROM EDW_CST_COGS_F_IV WHERE TRX_CURRENCY_FK_KEY = :p_currency_fk;
• SELECT TRX_CURRENCY_FK_KEY, SUM(COGS_G) FROM EDW_CST_COGS_F_IV GROUP BY TRX_CURRENCY_FK_KEY;

Because no joins are embedded in the view, all dimension resolution is performed by the calling query, giving the warehouse full control over join paths and aggregation grain.