Results for “op_ctrd_cls”

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

Overview

OP_CTRD_CLS is a GML (Process Manufacturing Logistics) reference table that stores Customer Trade Classes. Customer trade classes are classification codes used to group customers by trade category — for example, wholesale, retail, distributor, or export categories — so that pricing, promotion, and logistics rules can be applied consistently to a defined customer segment rather than to individual customer records. The table resides in the GML schema, carries a VALID status in the ETRM 12.2.2 documentation set, and is fully supported in both Oracle EBS 12.1.1 and 12.2.2 environments where Process Manufacturing Logistics is licensed.

From a dimensional modeling perspective, the mined heuristic classification places OP_CTRD_CLS as hub-leaning. In Data Vault terms, this suggests the table behaves primarily as a hub: it holds a stable business key (CUSTTRADE_CLASS) around which descriptive attributes and downstream references accumulate, rather than acting as a link (many-to-many association) or a pure satellite (descriptive history). Its foreign key into OP_TEXT_HDR supports the hub interpretation by attaching reusable text, rather than splitting the entity across associative tables.

Key Information Stored

The documented physical schema defines 10 columns. The primary key, OP_CTRD_CLS_PK, is defined on CUSTTRADE_CLASS, and the same column is also the single unique index and therefore the business-key candidate. This is an unusual but convenient case where the surrogate and business key coincide: CUSTTRADE_CLASS serves as both the join key and the human-readable identifier.

• CUSTTRADE_CLASS — the trade class code and primary key; the value referenced by all dependent tables.
• CUSTTRADE_CLASS_DESC — the descriptive name of the trade class, used in list-of-values (LOV) displays and reports.
• TEXT_CODE — foreign key to OP_TEXT_HDR, linking the trade class to an extended text header for long descriptions or notes.
• TRANS_CNT — a transaction/usage counter, commonly used for concurrency or record-use tracking in OPM tables.
• DELETE_MARK — soft-delete indicator; records are logically disabled rather than physically removed.
• CREATION_DATE, CREATED_BY — audit columns recording initial insert.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns recording the most recent change and the login/user session responsible.

The table functions as a stable, low-volume reference or "hub" of trade class definitions, with audit and soft-delete columns layered on top of the core key and description.

Common Use Cases and Queries

Typical usage involves populating LOVs, resolving trade class descriptions in customer and pricing reports, and validating that customer assignments reference active (non-deleted) trade classes. A standard lookup query is:

• SELECT CUSTTRADE_CLASS, CUSTTRADE_CLASS_DESC FROM GML.OP_CTRD_CLS WHERE DELETE_MARK = 0 ORDER BY CUSTTRADE_CLASS;
• Joining to extended text: SELECT c.CUSTTRADE_CLASS, c.CUSTTRADE_CLASS_DESC, t.TEXT_CODE FROM GML.OP_CTRD_CLS c, GML.OP_TEXT_HDR t WHERE c.TEXT_CODE = t.TEXT_CODE;
• Counting customers per trade class by joining to OP_CUST_MST: SELECT cl.CUSTTRADE_CLASS, cl.CUSTTRADE_CLASS_DESC, COUNT(*) FROM GML.OP_CTRD_CLS cl, GML.OP_CUST_MST cm WHERE cl.CUSTTRADE_CLASS = cm.CUSTTRADE_CLASS GROUP BY cl.CUSTTRADE_CLASS, cl.CUSTTRADE_CLASS_DESC;

These patterns support trade class usage audits, orphaned-reference detection (trade classes referenced by customers but soft-deleted here), and pricing/promotion rule configuration reporting.

Related Objects

The FK metadata establishes clear relationships. OP_CTRD_CLS.TEXT_CODE references OP_TEXT_HDR, pulling in extended descriptive text. In the reverse direction, three tables depend on this table:

• OP_CUST_MST_OPM.CUSTTRADE_CLASS — the OPM customer master reference to the trade class.
• OP_CUST_MST.CUSTTRADE_CLASS — the customer master reference to the trade class.
• OP_PRSL_HDR.CUSTTRADE_CLASS — the price list header reference, indicating trade classes participate in pricing rule scoping.

Together these confirm OP_CTRD_CLS as a shared reference hub consumed by customer and pricing modules, with OP_TEXT_HDR supplying its extended text. Any change to a trade class definition therefore propagates in meaning across customer masters and price lists, making controlled maintenance of this table important for data integrity.