Results for “cr_rsrc_cls_b”

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

Overview

CR_RSRC_CLS_B is the resource class base table within the Oracle EBS Process Manufacturing Process Planning (GMP) module. It defines the master list of resource classes — the highest-level grouping construct used to categorize manufacturing resources such as equipment, labor, and production lines. Resource classes provide a reusable classification layer above the individual resource level, enabling planners to roll up capacity, cost, and usage information across families of similar resources rather than maintaining that detail for each resource independently.

The table resides in the GMP schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its structure follows the standard Oracle "base" table convention (the _B suffix), indicating a companion translation or view layer may exist for descriptive attributes. From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. This suggestion reflects the fact that CR_RSRC_CLS_B holds mostly descriptive and audit attributes keyed by a single business identifier, rather than acting as a pure join or transaction link. In practice, however, it functions as a reference or hub-like master within the GMP planning model, since downstream resource records depend on it for their classification.

Key Information Stored

The table carries ten documented columns. The primary key, enforced by the unique index CR_RSRC_CLS_B_PK, is RESOURCE_CLASS. This column is the business-key candidate — a short, user-defined code that uniquely identifies each resource class throughout the application. It is the value referenced by child tables and is the natural identifier used in queries and interfaces.

Descriptive content centers on RESOURCE_CLASS_DESC, which stores the human-readable name or description associated with the code. The TEXT_CODE column holds a reference into the shared text header table, allowing long or multi-line descriptive notes to be attached to the class without storing them in the base row. Standard Oracle audit columns — CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — capture who created and last modified each record and when. TRANS_CNT supports Oracle's transaction-count concurrency control, and DELETE_MARK implements soft deletion, allowing a class to be logically retired without physically removing the row or orphaning historical references. Together these columns make the table both a business reference and an audit-tracked entity.

Common Use Cases and Queries

Typical use cases include validating resource class setup, generating planning reports grouped by class, and extracting reference data for integration or migration. Because RESOURCE_CLASS is the join key in CR_RSRC_MST_B, a common query resolves class descriptions for resource master rows:

• SELECT m.RESOURCE_CLASS, c.RESOURCE_CLASS_DESC FROM CR_RSRC_MST_B m JOIN CR_RSRC_CLS_B c ON m.RESOURCE_CLASS = c.RESOURCE_CLASS;
• Reporting active classes only: SELECT RESOURCE_CLASS, RESOURCE_CLASS_DESC FROM CR_RSRC_CLS_B WHERE DELETE_MARK = 0;
• Retrieving attached notes: join TEXT_CODE to CR_TEXT_HDR to pull descriptive text for a class.
• Audit review: filter on LAST_UPDATE_DATE or CREATED_BY to identify recently changed or newly added classes.
• Integration extracts: select the code and description pairs for loading into external planning or MES systems.

Always filter DELETE_MARK = 0 in operational queries and use RESOURCE_CLASS as the stable key rather than row ordering.

Related Objects

The relationship data identifies two documented joins. The most significant is CR_RSRC_MST_B, the resource master table, which references this table via RESOURCE_CLASS; every resource master row depends on a valid class definition here. The second relationship is to CR_TEXT_HDR through TEXT_CODE, providing the text-header link for long descriptions. Standard Oracle EBS companion objects — including the _TL translation or descriptive view layer following the _B convention, and GMP planning forms and concurrent programs that populate and consume resource classes — complete the dependency chain. Because CR_RSRC_MST_B is the primary dependent, any modification or deletion of a resource class must be validated against referencing resource master records to avoid invalid or orphaned resource definitions.