Results for “cp_phase_code”

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

Overview

CST_COST_UPDATES_V is a single-organization reporting view owned by the APPS schema in Oracle E-Business Suite. It exposes the cost update records stored in the Cost Management (CST) module while resolving the foreign key identifiers into their user-facing descriptions, meanings, and concatenated values. The view is cataloged under the BOM – Bills of Material product family but is consumed primarily by Cost Management, Inventory, and Manufacturing reporting flows.

Its principal role is to present a denormalized, readable projection of the CST_COST_UPDATES table. Rather than requiring report authors to join cost types, category sets, flexfields, lookup codes, and concurrent request tables manually, the view performs that work natively. Each row represents one cost update transaction, together with the descriptive context required to interpret it — cost type name, item range, category, adjustment account, and the status of the concurrent request that processed the update.

The version is time-zone aware: the update date is passed through FND_DATE.ADJUST_DATETIME using the server and client time zone codes from FND_TIMEZONES. This makes the view suitable for end-user reporting where local time presentation is expected.

Underlying Base Objects

The view is defined over a mixture of base tables and supporting objects. The primary driving object is CST_COST_UPDATES (accessed via synonym), which supplies the cost update transaction row. CST_COST_TYPES supplies the cost type description through a non-outer join on COST_TYPE_ID. FND_CONCURRENT_REQUESTS is joined with an outer join to expose the request completion text and the phase and status codes associated with the update process.

Translation and lookup objects are joined with outer joins so that missing values do not suppress the transaction row. These include MTL_CATEGORY_SETS_TL for the category set name, MFG_LOOKUPS for the update option and item range meanings, and FND_LOOKUPS for the concurrent request phase code (CP_PHASE_CODE) and status code (CP_STATUS_CODE). Item and category context is supplied by MTL_ITEM_FLEXFIELDS and MTL_CATEGORIES_KFV, while GL_CODE_COMBINATIONS resolves the inventory adjustment account. Package calls to FND_DATE, FND_GLOBAL, and FND_TIMEZONES handle date conversion and session context.

Key Columns

• COST_UPDATE_ID — primary identifier for the cost update transaction.
• UPDATE_DATE — transaction date adjusted to the client time zone.
• STATUS — status of the cost update record.
• ORGANIZATION_ID, COST_TYPE_ID, COST_TYPE — the organization and cost type being updated.
• SNAPSHOT_SAVED_FLAG — indicates whether a cost snapshot was persisted.
• SINGLE_ITEM, ITEM_RANGE_LOW, ITEM_RANGE_HIGH — scope of items affected.
• CATEGORY_ID, CATEGORY_SET_ID, CATEGORY_SET_NAME, CONCATENATED_SEGMENTS — category and category set context.
• INV_ADJUSTMENT_ACCOUNT, CODE_COMBINATION_ID — adjustment account and its GL code combination.
• REQUEST_ID, COMPLETION_TEXT, and the phase and status meanings — concurrent request processing detail.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID.

Common Use Cases and Queries

The view is typically queried to audit cost update activity, confirm completion of cost rollups, or reconcile adjustment accounts. A common pattern filters by organization and cost type, then orders by update date:

SELECT cost_update_id, update_date, cost_type, status, completion_text
FROM apps.cst_cost_updates_v
WHERE organization_id = :org_id
ORDER BY update_date DESC;

Because CP_STATUS_CODE and CP_PHASE_CODE are resolved through FND_LOOKUPS, the view is frequently used to report on request status without joining the lookup tables directly. Analysts also use it to identify updates that affect a single item versus a range, and to inspect the adjustment account associated with a cost change before posting to the general ledger.