Results for “cst_cg_wip_acct_classes”

50+ results




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

Overview

The CST_CG_WIP_ACCT_CLASSES table is a Bills of Material (BOM) module object within the Oracle E-Business Suite database, owned by the BOM schema. Its documented purpose is to uniquely identify the WIP accounting class associated with a cost group within each inventory organization. In practice, this table serves as the association bridge that ties the Cost Management construct of a cost group to the discrete Work in Process construct of a WIP accounting class, ensuring that manufacturing transactions posted against a cost group resolve to the correct accounting class for valuation and cost collection purposes.

The primary key, CST_CG_WIP_ACCT_CLASSES_PK, is defined on the composite of COST_GROUP_ID, ORGANIZATION_ID, and CLASS_CODE, which confirms that the granularity of a row is one accounting class per cost group per organization. The metadata additionally documents a unique index, CST_CG_WIP_ACCT_CLASSES_U1, defined on the identical three columns, indicating the business key and the surrogate/composite primary key coincide. From a Data Vault modeling perspective, the heuristic classification is standalone, meaning the table is not documented as a dependent child in a foreign-key-driven relationship chain. A modeling suggestion, therefore, is to treat the three-column key as a natural business key and to consider whether the association is better represented as a link between a cost group hub and a WIP accounting class hub, with the remaining attributes carried as satellite detail.

Key Information Stored

The table documents thirteen physical columns. The most significant are the following:

  • COST_GROUP_ID — Identifier of the cost group. Part of the composite primary key and business key.
  • ORGANIZATION_ID — Inventory organization in which the association is valid. Part of the composite primary key.
  • CLASS_CODE — The WIP accounting class code. Part of the composite primary key and the element that links accounting behavior to the cost group.
  • DISABLE_DATE — The date on which the association becomes inactive, supporting date-effective analysis of accounting class assignments.
  • LAST_UPDATE_DATE — Standard audit column recording the most recent change to the row.
  • LAST_UPDATED_BY — The user or process that performed the most recent update.
  • CREATION_DATE — Timestamp of initial row creation.
  • CREATED_BY — The user or process that created the row.
  • LAST_UPDATE_LOGIN — The login identifier associated with the last update.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the request and program responsible for the last change, enabling audit and troubleshooting of batch processes.

The surrogate primary key is the three-column composite rather than a single generated identifier; the unique index matches it exactly, so no separate business-key candidate exists beyond the primary key.

Common Use Cases and Queries

Typical usage centers on verifying which WIP accounting class applies to a cost group in a given organization, and on identifying associations that have been disabled. A common pattern joins the table to organization and cost group metadata to produce a current-state listing:

  • Determine the active accounting class for a cost group: select CLASS_CODE where COST_GROUP_ID, ORGANIZATION_ID match and DISABLE_DATE is null.
  • Audit historical assignments using DISABLE_DATE ranges.
  • Trace which concurrent program introduced changes using REQUEST_ID and PROGRAM_ID.
  • Validate configuration completeness before opening WIP periods, ensuring every cost group has a valid class.
  • Reconcile cost group setup against WIP accounting class definitions during period-close.

Related Objects

Because the metadata classifies this object as standalone, direct foreign-key relationships are not documented. Related objects are therefore inferred from the semantic dependencies implied by the key columns: