Results for “fm_oprn_cls”

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

Overview

FM_OPRN_CLS is a reference and grouping table within the Oracle E-Business Suite process manufacturing domain, owned by the GMD (Process Manufacturing Product Development) module. Its documented description identifies it as a "Formula operation class" used to group operations. In practical terms, the table acts as a classification or lookup entity that organizes formula operations into logical categories, allowing process manufacturers to maintain consistent grouping of operations used in recipes, formulas, and routings. Because operations are central to how process manufacturing models production steps, the operation class provides a reusable taxonomy that downstream master data can reference.

The metadata notes that this object is "Not implemented in this database" and that a heuristic Data Vault classification of satellite-leaning has been mined from the foreign key structure. This suggests that, as a modeling suggestion, FM_OPRN_CLS behaves more like a descriptive satellite supporting a parent business concept than a pure hub or link. Its single-column primary key and its role as a code-driven lookup reinforce this interpretation.

Key Information Stored

The documented structure is compact. Its most significant elements are:

• OPRN_CLASS — the primary key column and business identifier for each formula operation class. Defined by the primary key constraint FM_OPRN_CLS_PK (OPRN_CLASS), this column holds the code value that uniquely identifies a class and is the value referenced by dependent operation master records.
• TEXT_CODE — a foreign key column referencing FM_TEXT_HDR. This links the operation class to the shared text header structure, enabling descriptive or multilingual text to be associated with the class rather than storing long descriptions directly in this table.

The documented metadata does not enumerate additional descriptive columns such as names or dates. Based on the pattern of EBS lookup tables, any supplemental attributes would typically be limited to descriptive text obtained via TEXT_CODE and standard audit or translation handling. The surrogate versus business-key distinction is effectively collapsed here: OPRN_CLASS is both the primary key and the business-key candidate, since it is the only column documented within FM_OPRN_CLS_PK.

Common Use Cases and Queries

The primary use case is validating and enumerating the set of operation classes available for grouping formula operations. A typical query retrieving a class together with its descriptive text header is:

• SELECT c.oprn_class, h.text_code FROM fm_oprn_cls c, fm_text_hdr h WHERE c.text_code = h.text_code;
• Reporting on which operation classes are actually in use: SELECT m.oprn_class, COUNT(*) FROM fm_oprn_mst m GROUP BY m.oprn_class;
• Detecting orphaned classes not referenced by any operation master: an outer join between FM_OPRN_CLS and FM_OPRN_MST on OPRN_CLASS filtered where the master key is null.

Because the table is documented as not implemented in the reference database, developers should confirm object existence and usage in the target instance before relying on it in extracts or interfaces. Where present, it is primarily consumed for reference and grouping rather than transactional processing.

Related Objects

Two documented foreign key relationships define its immediate context:

• FM_TEXT_HDR — the parent of FM_OPRN_CLS.TEXT_CODE, supplying text header and description data.
• FM_OPRN_MST — the operation master table, which references FM_OPRN_CLS through FM_OPRN_MST.OPRN_CLASS. This is the principal dependent object, as operations are grouped by the class defined here.

Beyond these documented relationships, formula and routing tables within GMD that consume operation master records transitively depend on the operation class for grouping and classification logic. Any validation or list-of-values that restricts operation classes ultimately resolves to FM_OPRN_CLS.