Results for “cst_cost_groups_v”

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

Overview

CST_COST_GROUPS_V is an APPS-owned database view in Oracle E-Business Suite 12.1.1 and 12.2.2, registered as a VALID object under the Bills of Material (BOM) product family. It is defined directly over the CST_COST_GROUPS base table and is documented as "based on CST_COST_GROUPS table." The view presents cost group definitions in a denormalized, reporting-friendly form, enriching the raw cost group rows with legal entity and organization name information sourced from Oracle Legal Entity (XLE) and Human Resources organization tables. Its role is primarily to support read-only reporting, concurrent program lookups, and integration queries where cost group context—particularly the Project Accounting (PAC) costing model—must be presented alongside descriptive organization and legal entity attributes. The view text carries an explicit comment that it was modified for PAC in release 11.5, and its design reflects the union of two cost group types: PROJECT cost groups (COST_GROUP_TYPE = 1) and ORG cost groups used for PAC (COST_GROUP_TYPE = 2), the latter joined to XLE to resolve legal entity data.

Underlying Base Objects

The view is defined as an outer-join query across three documented base objects:

• CST_COST_GROUPS (SYNONYM) — the driving table, supplying all cost group attributes including COST_GROUP_ID, COST_GROUP, ORGANIZATION_ID, COST_GROUP_TYPE, and the DFF attribute columns.
• XLE_ENTITY_PROFILES (SYNONYM) — outer-joined on CG.LEGAL_ENTITY = XEP.LEGAL_ENTITY_ID to resolve the legal entity name for ORG-type cost groups.
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — outer-joined on CG.ORGANIZATION_ID = HAOUT1.ORGANIZATION_ID, filtered by the session language, to provide the organization name.

The join conditions use the Oracle (+) outer-join syntax, so rows in CST_COST_GROUPS without a matching legal entity or organization are still returned, with NULL names. The view therefore remains a 1:1 projection of CST_COST_GROUPS rows, with no row multiplication under normal master data conditions.

Key Columns

• ROW_ID — the CST_COST_GROUPS ROWID, useful for row-level addressing.
• COST_GROUP_ID / COST_GROUP — the primary key and user-facing name of the cost group.
• ORGANIZATION_ID — the inventory organization the cost group belongs to; NULL identifies a non-organization (project) cost group.
• MULTI_ORG_FLAG — derived via DECODE(NVL(ORGANIZATION_ID,-1), -1, 1, 2). A value of 1 indicates the record is not organization-specific (project cost group, the default multi-org context), while 2 indicates an organization-specific cost group. This is the column most directly relevant to multi-org searches, as it classifies each row’s organizational scope.
• COST_GROUP_TYPE — NVL(CG.COST_GROUP_TYPE,1); 1 = project cost group, 2 = org cost group used for PAC.
• LEGAL_ENTITY / LEGAL_ENTITY_NAME — the legal entity ID and resolved name for ORG cost groups.
• ORGANIZATION_NAME — the translated organization name for ORG cost groups.
• DESCRIPTION, DISABLE_DATE — descriptive text and effective end date.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — descriptive flexfield columns.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include validating which cost groups are organization-specific versus shared, resolving legal entity and organization names for PAC reporting, and driving multi-organization aware LOVs. A representative query listing all cost groups with their multi-org classification is:

• SELECT cost_group_id, cost_group, organization_id, multi_org_flag, organization_name, legal_entity_name FROM apps.cst_cost_groups_v ORDER BY cost_group;
• To restrict to organization-specific (PAC) cost groups: SELECT cost_group_id, cost_group, organization_name FROM apps.cst_cost_groups_v WHERE multi_org_flag = 2;
• To isolate project cost groups not tied to an organization: SELECT cost_group_id, cost_group FROM apps.cst_cost_groups_v WHERE multi_org_flag = 1;
• To resolve names for a specific legal entity: SELECT cost_group, organization_name FROM apps.cst_cost_groups_v WHERE legal_entity_name = :p_legal_entity;

Because the view applies an outer join and language filter, queries should not assume organization or legal entity names are always populated; NULL handling is required when the source organization or legal entity reference is missing.