Results for “cr_rsrc_cls”

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

Overview

CR_RSRC_CLS is a reference (lookup) table within the Oracle EBS Process Manufacturing Process Planning module (GMP). Its documented description is simply "Resource class," indicating that each row represents a distinct classification category for manufacturing resources — the equipment, machines, production lines, and labor entities that process planning schedules and capacity calculations rely upon. Resource classes allow planners to group resources that share similar characteristics, such as capacity units, scheduling behavior, or costing treatment, so that routing and capacity logic can be applied consistently across a family of resources rather than managed resource-by-resource.

The ETRM metadata classifies this object heuristically as satellite-leaning under a Data Vault modeling interpretation. In practice this means CR_RSRC_CLS behaves like a descriptive attribute set attached to a business key (the resource class code) rather than an independent hub of a transactional relationship. It carries two characteristics typical of a satellite: a single natural business key constrained by its primary key, and a foreign key to a text/description header (CR_TEXT_HDR) that supplies language-dependent descriptive content. The ETRM record notes the object is "Not implemented in this database," which is expected for a large multi-module EBS instance — Process Manufacturing tables exist only where the GMP product family has actually been installed and configured.

Key Information Stored

The documented metadata exposes a deliberately narrow column set, and the table should be treated as a thin code-and-description reference. The most significant attributes are:

• RESOURCE_CLASS — the sole primary key column and the business key of the table. It holds the alphanumeric code that uniquely identifies each resource class within the Process Manufacturing implementation. Every reference from other objects resolves to this value.
• TEXT_CODE — the foreign key to CR_TEXT_HDR, providing the translatable name or description associated with the resource class. This indirection lets the same class code display descriptive text in multiple installed languages without duplicating the class row.

Because the primary key (CR_RSRC_CLS_PK) is defined on RESOURCE_CLASS, that single column is both the surrogate-style identifier used by joins and the natural business-key candidate; no separate unique index beyond the PK is documented. Consumers should not assume the presence of additional descriptive, enabled-flag, or audit columns unless they are confirmed in the actual installed schema — the ETRM excerpt deliberately limits itself to the key and the text reference.

Common Use Cases and Queries

The principal use case is validation and enrichment of resource master data. When reporting on production resources, a planner joins CR_RSRC_CLS to resolve class codes into descriptive labels, and to group capacity or utilization metrics by class. A second use case is data-quality auditing: identifying resource master rows whose RESOURCE_CLASS value has no matching definition in CR_RSRC_CLS, which would indicate an orphaned or invalid assignment.

Representative SQL patterns supported by the documented structure include:

• Enumerating all defined classes: SELECT RESOURCE_CLASS, TEXT_CODE FROM CR_RSRC_CLS ORDER BY RESOURCE_CLASS;
• Resolving descriptions through the text header: SELECT c.RESOURCE_CLASS, h.TEXT FROM CR_RSRC_CLS c, CR_TEXT_HDR h WHERE c.TEXT_CODE = h.TEXT_CODE; (adjust the CR_TEXT_HDR column names to the installed schema).
• Counting resources per class: SELECT c.RESOURCE_CLASS, COUNT(*) FROM CR_RSRC_CLS c, CR_RSRC_MST m WHERE m.RESOURCE_CLASS = c.RESOURCE_CLASS GROUP BY c.RESOURCE_CLASS;
• Detecting unclassified resources: a left outer join from CR_RSRC_MST to CR_RSRC_CLS where the class key is null.

These queries are read-only reporting constructs and are safe against the reference table; the table is typically maintained through the Process Manufacturing resource setup forms rather than by direct DML.

Related Objects

The FK metadata identifies a compact but well-defined neighborhood around CR_RSRC_CLS:

• CR_RSRC_MST — the resource master table. It carries the column RESOURCE_CLASS as a foreign key referencing CR_RSRC_CLS.RESOURCE_CLASS. This is the dominant relationship: every production resource is assigned to exactly one class.
• CR_TEXT_HDR — the text header table referenced by CR_RSRC_CLS.TEXT_CODE, supplying translated descriptive text for each class.

Beyond the documented foreign keys, the resource class value propagates indirectly into capacity, scheduling, and routing objects that consume CR_RSRC_MST, making CR_RSRC_CLS a foundational reference for GMP process planning reporting even though it holds very few columns. Any view or concurrent program that reports on resource utilization, capacity loading, or resource grouping will typically traverse CR_RSRC_MST and then resolve the class through this table.