Results for “fm_fmct_cls”

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

Overview

FM_FMCT_CLS is a table owned by the GMD schema within Oracle EBS Process Manufacturing Product Development. It is documented as storing formula control classes, and the ETRM metadata carries the explicit annotation -NOT USED-. This designation indicates that the table survives as a legacy or reserved structure in the 12.1.1 / 12.2.2 data model, but is not actively populated or referenced by current application logic for formula control processing. Its presence is primarily significant for schema completeness, foreign key integrity, and impact analysis rather than for day-to-day functional use.

From a Data Vault modeling perspective, the mined heuristic classifies this object as hub-leaning. This suggests that FM_FMCT_CLS functions as a reference or lookup entity that defines the set of control class values, keyed by a stable business identifier. Its role in the surrounding model is that of a parent or target table for foreign keys originating in formula master tables.

Key Information Stored

The documented physical schema lists 10 columns. The most significant are:

• FMCONTROL_CLASS — The primary key column and the single business-key candidate, enforced through the unique index FM_FMCT_CLS_PK. It holds the code that identifies a formula control class.
• FMCONTROL_CLASS_DESC — The descriptive text associated with each control class code, used for display and reporting.
• TEXT_CODE — A foreign key to FM_TEXT_HDR, linking the class to text or note records maintained in the text header table.
• TRANS_CNT — A transaction count column, typical of Oracle's multi-organization and concurrency control patterns.
• DELETE_MARK — The standard soft-delete indicator used throughout Oracle EBS to flag logically removed rows.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard Oracle Applications audit columns that record who created and last modified each row and when.

The primary key is a single-column surrogate on FMCONTROL_CLASS, which also serves as the business key. There is no composite key or separate sequence-derived identifier documented.

Common Use Cases and Queries

Because the table is annotated -NOT USED-, practical usage is limited. Primary scenarios are archeological and structural:

• Impact analysis — Determining which formula tables would be affected if the control class concept were reactivated or retired.
• Data migration and conversion — Validating legacy data extracted from earlier releases where formula control classes may have been populated.
• Referential integrity auditing — Verifying that no orphaned values exist in the referencing formula tables.

A representative audit query:

• SELECT fm.FORMULA_ID, fm.FMCONTROL_CLASS FROM FM_FORM_MST fm LEFT JOIN FM_FMCT_CLS c ON fm.FMCONTROL_CLASS = c.FMCONTROL_CLASS WHERE c.FMCONTROL_CLASS IS NULL;

Reporting use cases center on listing defined control classes and their descriptions, joined to FM_TEXT_HDR via TEXT_CODE when explanatory text is required.

Related Objects

FM_FMCT_CLS participates in a small set of documented relationships:

• FM_TEXT_HDR — Referenced by FM_FMCT_CLS.TEXT_CODE; provides text and note content for each class.
• FM_FORM_MST_B — References FM_FMCT_CLS via the FMCONTROL_CLASS column.
• FM_FORM_MST — References FM_FMCT_CLS via FMCONTROL_CLASS; the principal formula master table.
• LM_FORM_MST — References FM_FMCT_CLS via FMCONTROL_CLASS in the laboratory management context.

These relationships establish FM_FMCT_CLS as a lookup hub for formula control classification across formulation and laboratory master data, even though the class itself is not currently put to functional use.