Results for “cust_class”

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

Overview

OP_CUST_CLS is a reference (lookup) table owned by the GML schema within the Process Manufacturing Logistics (OPM) product family. It stores the definitions of general customer classes, which serve as a classification mechanism for organizing customers in Oracle EBS Process Manufacturing. Each row represents one distinct customer class code that can be assigned to customer records for use in pricing, reporting, credit control, order processing, and other downstream logistics functions. The table is a foundational master-level object in the OPM customer data model; it does not store transactional data but rather the controlled vocabulary of class codes that other OPM tables reference through foreign keys.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure identifies OP_CUST_CLS as hub-leaning. This suggests that, when modeled in a Data Vault, the table would most naturally map to a hub (with CUST_CLASS as the business key) rather than a link or satellite. The short, stable list of class codes with limited descriptive attributes supports this interpretation.

Key Information Stored

The documented physical schema for OP_CUST_CLS (ETRM 12.2.2) contains 10 columns. The most significant are:

• CUST_CLASS — The primary key column and the business identifier for each customer class. It is a text/code value that uniquely identifies a class and is the column referenced by all foreign keys pointing to this table. The unique index OP_CUST_CLS_PK enforces uniqueness on this single column.
• CUST_CLASS_DESC — The descriptive name or long description associated with the class code, used for display in user interfaces and reports.
• TEXT_CODE — A foreign-key reference to OP_TEXT_HDR, linking the class to a text header record. This enables extended free-form notes or documentation to be attached to the class via the OPM text framework.
• TRANS_CNT — A transaction count column, typically used by the OPM concurrent/audit framework to track record activity.
• DELETE_MARK — The standard soft-delete flag (0 = active, 1 = logically deleted), used throughout OPM instead of physical row removal.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard WHO columns capturing audit and user information.

The surrogate primary key is enforced by OP_CUST_CLS_PK on CUST_CLASS; no separate system-generated numeric key is documented, making CUST_CLASS both the business key and the effective primary key.

Common Use Cases and Queries

Customer classes drive segmentation and defaulting logic across OPM order entry, pricing, and credit management. Typical reporting and integration scenarios include:

• Populating a list of valid customer classes for a concurrent program or DFF (descriptive flexfield) value set.
• Enriching customer records with their class description for analytical reporting.
• Verifying that every customer references a valid (non-deleted) class before migration or data cleanup.

A common join pattern enriches OP_CUST_MST (Operational/Standalone customer master) with class descriptions:

SELECT m.customer_number, m.customer_name, c.cust_class, c.cust_class_desc
FROM   op_cust_mst m, op_cust_cls c
WHERE  m.cust_class = c.cust_class
AND    c.delete_mark = 0;

A validation query to detect orphaned customer classes would identify customers pointing to nonexistent or deleted classes:

SELECT cust_class FROM op_cust_mst
WHERE  cust_class NOT IN (SELECT cust_class FROM op_cust_cls WHERE delete_mark = 0);

A simple lookup for a value set or LOV:

SELECT cust_class, cust_class_desc FROM op_cust_cls
WHERE  delete_mark = 0 ORDER BY cust_class;

Related Objects

The following objects are documented as directly related to OP_CUST_CLS through foreign-key relationships:

• OP_CUST_MST — The primary customer master table for OPM. Its CUST_CLASS column references OP_CUST_CLS.CUST_CLASS. This is the most significant dependent object, since every customer record is classified through this relationship.
• OP_CUST_MST_OPM — An OPM-specific customer master variant whose CUST_CLASS column also references OP_CUST_CLS.CUST_CLASS.
• OP_TEXT_HDR — The text header table referenced by OP_CUST_CLS.TEXT_CODE. This is the only outbound foreign key from OP_CUST_CLS, providing the mechanism for attaching extended textual content to a customer class.

Because OP_CUST_CLS is a foundational lookup, reporting joins typically traverse from OP_CUST_MST or OP_CUST_MST_OPM into this table to resolve class codes into descriptions, and from OP_CUST_CLS into OP_TEXT_HDR where textual annotations are required. No OPM public API is documented for maintaining this table; it is typically populated and maintained through OPM setup forms or direct data seeding during implementation.