Results for “cst_xla_wip_entity_ref_v”

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

Overview

In Oracle E-Business Suite, CST_XLA_WIP_ENTITY_REF_V is a reporting and integration view owned by the APPS schema. It provides a streamlined projection of work in process (WIP) entity reference data, exposing a concise set of attributes that identify discrete jobs, repetitive schedules, and other WIP entities for use by subledger accounting (XLA), costing, and analytical reporting components. The view is catalogued under the BOM — Bills of Material product in the ETRM documentation for release 12.2.2, where it is recorded as VALID.

Rather than presenting the full breadth of columns held on the underlying WIP entity table, this view intentionally narrows the result set to the fields required to reference and describe a WIP entity. This design makes it a convenient, stable interface for joins against costing and accounting tables, and for reports where only identification and categorization of the WIP entity is required. Its naming convention — the CST (Cost Management) prefix combined with the XLA token — indicates its role as a cost-side reference source consumed by subledger accounting processes.

Underlying Base Objects

The view is defined over a single referenced base object, WIP_ENTITIES (exposed in the APPS schema as a synonym). The documented view text is:

SELECT WIP_ENTITY_ID, WIP_ENTITY_NAME, ENTITY_TYPE, DESCRIPTION FROM WIP_ENTITIES

Because it is a simple projection of one base table with no aggregation, joins, or filtering predicates, the view inherits the row granularity of WIP_ENTITIES directly: one row per WIP entity. This simplicity means the view carries no performance overhead beyond the base table scan and no additional integrity constraints of its own; all validation and referential behaviour derive from WIP_ENTITIES. It is therefore best regarded as a controlled, read-only façade over the entity master rather than a transformation layer.

Key Columns

• WIP_ENTITY_ID — The unique primary key of the WIP entity. This is the value used as a foreign key throughout costing, accounting, and transaction tables (e.g., WIP_TRANSACTIONS style references), making it the principal join column for XLA and report queries.
• WIP_ENTITY_NAME — The user-visible name of the job or schedule, typically the job number or repetitive schedule name.
• ENTITY_TYPE — The internal numeric discriminator that distinguishes entity categories, such as discrete job versus repetitive schedule. This column corresponds to the concept users search for as wip_entity_type. In the view as documented, it is exposed as ENTITY_TYPE.
• WIP_ENTITY_DESCRIPTION — The free-text description attached to the WIP entity. It is sourced from the DESCRIPTION column of WIP_ENTITIES and is aliased as WIP_ENTITY_DESCRIPTION for clarity in reporting contexts.

Note a documented discrepancy worth observing: the view text lists the columns as WIP_ENTITY_ID, WIP_ENTITY_NAME, ENTITY_TYPE, and DESCRIPTION, while the ETRM column listing names them WIP_ENTITY_ID, WIP_ENTITY_NAME, WIP_ENTITY_TYPE, and WIP_ENTITY_DESCRIPTION. Developers should verify the actual column aliases against the deployed view in their specific patch level before hard-coding references.

Common Use Cases and Queries

Typical applications include subledger accounting reference lookups, costing reconciliation reports, and cross-referencing WIP entity identifiers in interface or conversion scripts. A representative query returning entity identification and type is:

SELECT wip_entity_id, wip_entity_name, entity_type, description
FROM apps.cst_xla_wip_entity_ref_v
WHERE entity_type = :entity_type
ORDER BY wip_entity_id;

To resolve the type meaning, join to the WIP entity type lookup table, e.g. WIP_ENTITY_TYPES or MFG_LOOKUPS, on entity_type. For reporting discrete jobs by name:

SELECT wip_entity_name, entity_type, description
FROM apps.cst_xla_wip_entity_ref_v
WHERE wip_entity_name LIKE :job_prefix || '%';

Because the view is a direct projection of WIP_ENTITIES, it should be used where only identification data is needed. Where broader WIP attributes are required, query the base table directly. The view remains a lightweight, reliable reference point for XLA-related integration across both 12.1.1 and 12.2.2.