Results for “cost_layer_id”

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

Overview

The APPS.CSTFV_PAC_QUANTITY_LAYERS view exposes the layer quantity of an inventory item broken out by PAC period and cost group. It is part of the Periodic Average Costing (PAC) feature set that is associated with the Bills of Material product family in Oracle E-Business Suite. In release 12.1.1 and 12.2.2, Periodic Average Costing allows organizations to compute item costs using an average over a defined costing period rather than a perpetual, transaction-by-transaction basis. This view is the reporting and integration surface for the quantity layer records that PAC maintains during that process.

The view is defined with the WITH READ ONLY clause, which prevents DML against it. It is intended purely for query and extraction, making it safe for use in custom reports, concurrent programs, and downstream integrations. Its purpose is to resolve the raw foreign-key identifiers held on the quantity layer table into meaningful business values such as the PAC period name, cost group name, and item context, so that users and applications can report on layer quantities without joining the base tables themselves.

Underlying Base Objects

According to the ETRM metadata, the view is defined over four objects, all referenced through APPS synonyms:

• CST_PAC_QUANTITY_LAYERS — the driving table (aliased CPQL), holding the actual quantity layer rows keyed by QUANTITY_LAYER_ID and COST_LAYER_ID.
• CST_PAC_PERIODS — the period definition table (aliased CPP), joined on PAC_PERIOD_ID to supply PERIOD_NAME.
• CST_COST_GROUPS — the cost group table (aliased CCG), joined on COST_GROUP_ID and filtered by COST_GROUP_TYPE = 2 to supply organization and cost group context.
• MTL_SYSTEM_ITEMS — the item master (aliased SY), joined to validate the organization and inventory item combination.

The joins are inner joins across all four tables, with a security predicate embedded as a bind-style constraint on CCG.ORGANIZATION_ID. This means only rows where the cost group, period, and item relationships are all valid will be returned.

Key Columns

• QUANTITY_LAYER_ID / COST_LAYER_ID — composite primary key identifying each quantity layer row.
• PAC_PERIOD_ID — the period identifier; this is the column the user searched for under the prompt "pac_period_name".
• CPP.PERIOD_NAME — surfaced in the ETRM column list as PAC_PERIOD_NAME, this is the human-readable PAC period name corresponding to PAC_PERIOD_ID.
• COST_GROUP_ID and CCG.COST_GROUP (COST_GROUP_NAME) — identifes the cost group the layer belongs to.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — identify the item and inventory organization for the layer.
• LAYER_QUANTITY and BEGIN_LAYER_QUANTITY — the ending and beginning quantities of the layer for the period, the core measures of the view.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard WHO audit columns.

Common Use Cases and Queries

The most frequent use case is reporting layer quantities by PAC period name, which is why searches for "pac_period_name" resolve to this view. A sample query illustrates this:

• SELECT pac_period_name, cost_group_name, inventory_item_id, layer_quantity, begin_layer_quantity FROM apps.cstfv_pac_quantity_layers WHERE pac_period_name = :p_period ORDER BY cost_group_name, inventory_item_id;

Other scenarios include reconciling beginning and ending layer balances for a period, comparing layer quantities across cost groups, and feeding periodic average cost data into external reporting or reconciliation workflows. Because the view is read only and already resolves the key foreign keys, it is the preferred access point for ad hoc cost analysis in both 12.1.1 and 12.2.2.