Results for “formula_use”

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

Overview

FM_CONF_TBL is a configuration table owned by the GMD schema (Process Manufacturing Product Development) in Oracle EBS 12.1.1 and 12.2.2. Its documented description states that it governs formula effectivity configuration and controls how formula effectivities are created within the Process Manufacturing suite. The table therefore acts as a rules registry that determines default effectivity behavior, organization-level defaults, and conflict resolution policy when formula versions overlap in time or scope. Because it is consumed by the formula effectivity creation logic, incorrect or missing rows can directly affect which formula version becomes effective for a given organization and usage.

From a Data Vault modeling perspective, the mined relationship structure suggests this table behaves as a link entity: it associates an organization (ORGN_CODE) with a formula usage context (FORMULA_USE) and records the descriptive effectivity behavior, default, and conflict-resolution attributes surrounding that association. This classification is a heuristic modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The table contains 14 documented columns. The most significant include:

• FMCONF_ID — the surrogate primary key, enforced by the FM_CONF_TBL_PK constraint. It uniquely identifies each configuration row and is typically system-generated.
• ORGN_CODE and FORMULA_USE — the business-key candidate pair, enforced by the unique index FM_CONF_TBL_U1. Together they scope a configuration entry to a specific organization and formula usage (for example, a production or costing usage), ensuring one configuration per combination.
• EFF_BEHAV — controls the effectivity behavior applied when formula effectivities are created, driving the versioning rules for formula versions.
• ORGN_DEFAULT — indicates the default organization context applied during effectivity creation.
• CONFLICT_RES — defines the conflict resolution strategy used when overlapping or conflicting formula effectivities are detected.
• TEXT_CODE — foreign key to FM_TEXT_HDR, providing descriptive or instructional text associated with the configuration.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS Who columns supporting auditability and concurrency.
• DELETE_MARK — soft-delete indicator consistent with Oracle Application Object Library conventions.
• TRANS_CNT — transaction counter column typically used for locking or change detection.

Common Use Cases and Queries

Typical usage includes diagnosing why a formula version was not made effective, reviewing organization-level defaults for formula effectivity, and auditing conflict-resolution settings across organizations. A common query retrieves the configuration for a given organization and usage:

• SELECT fmconf_id, orgn_code, formula_use, eff_behav, orgn_default, conflict_res FROM gmd.fm_conf_tbl WHERE orgn_code = :orgn AND formula_use = :use AND NVL(delete_mark,0) = 0;
• Reporting joins to FM_TEXT_HDR to surface the descriptive TEXT_CODE content for each configuration row.
• Validating completeness by comparing the distinct ORGN_CODE set in FM_CONF_TBL against organizations in SY_ORGN_MST to identify missing configurations.

Related Objects

• FM_TEXT_HDR — referenced via FM_CONF_TBL.TEXT_CODE, supplying text header detail.
• SY_ORGN_MST_B — referenced via FM_CONF_TBL.ORGN_CODE, the organization master base table.
• SY_ORGN_MST — referenced via FM_CONF_TBL.ORGN_CODE, the organization master view.
• Formula effectivity creation logic and related FM/GMD formula tables — consume this configuration to determine how effectivity rows are generated.
• FM_CONF_TBL_PK and FM_CONF_TBL_U1 — the primary key and unique business-key indexes enforcing uniqueness of FMCONF_ID and the ORGN_CODE/FORMULA_USE pairing.