Results for “source_analysis_code”

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

Overview

GMF_BURDEN_ASSOCIATION is a table in the GMF schema (Process Manufacturing Financials) that stores Percentage Burden Associations used by OPM Costing. It defines how burden rates — captured in GMF_BURDEN_CODES — are applied to source and target cost component classes and analysis codes. Burden associations determine which cost components absorb burden, at what percentage, and against which analytical basis, forming the ruleset that drives burden absorption during cost rollup and cost calculation.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a link table. It resolves a many-to-many relationship between burden definitions and cost component/analysis combinations, and its business identity is derived entirely from the participating keys rather than from any descriptive attribute of its own.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• BURDEN_ASSOCIATION_ID — the surrogate primary key (GMF_BURDEN_ASSOCIATION_PK), populated from a sequence. It carries no business meaning and should be used only for row-level reference and joins to child or audit structures.
• SOURCE_CMPNTCLS_ID — the source cost component class. Part of the business-key candidate GMF_BURDEN_ASSOCIATION_U1 and a foreign key to CM_CMPT_MST_B. This is the column most frequently used as a search predicate when tracing which component classes are burdened.
• SOURCE_ANALYSIS_CODE#1 — the source analysis code, the second component of the unique business key and a foreign key to CM_ALYS_MST.
• BURDEN_ID — the burden code applied, the third component of GMF_BURDEN_ASSOCIATION_U1 and a foreign key to GMF_BURDEN_CODES. Together with the two source columns above, it defines uniqueness: one burden per source component class and analysis code.
• TARGET_CMPNTCLS_ID — the cost component class that receives the burden, a foreign key to CM_CMPT_MST_B.
• TARGET_ANALYSIS_CODE#1 — the target analysis code, a foreign key to CM_ALYS_MST.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — plus DELETE_MARK for logical deletion.

The distinction between the surrogate key and the composite unique index matters: BURDEN_ASSOCIATION_ID provides the physical row identifier, while SOURCE_CMPNTCLS_ID, SOURCE_ANALYSIS_CODE#1, and BURDEN_ID constitute the true business key that prevents duplicate percentage burden associations.

Common Use Cases and Queries

Typical reporting scenarios include identifying all burdens assigned to a given component class, auditing which source-to-target pairings exist for a burden code, and validating that every burdened component has a corresponding target. A representative query joins the association to its lookup tables:

• Locate associations by source component class:
  SELECT a.burden_association_id, b.burden_code, a.source_analysis_code#1, a.target_cmpntcls_id
FROM gmf_burden_association a, gmf_burden_codes b
WHERE a.burden_id = b.burden_id AND a.source_cmpntcls_id = :cmpntcls_id;
• Resolve component class descriptions by joining CM_CMPT_MST_B on both SOURCE_CMPNTCLS_ID and TARGET_CMPNTCLS_ID.
• Detect orphaned or inactive rules using DELETE_MARK = 0 filters combined with EXISTS clauses against GMF_BURDEN_CODES.
• Cost-rollup diagnostics that reconcile total applied burden against expected percentages defined here.

Related Objects

• GMF_BURDEN_CODES — joined via BURDEN_ID; master definition of the burden percentage and basis.
• CM_CMPT_MST_B — referenced twice, through SOURCE_CMPNTCLS_ID and TARGET_CMPNTCLS_ID, supplying cost component class names.
• CM_ALYS_MST — referenced twice, through SOURCE_ANALYSIS_CODE#1 and TARGET_ANALYSIS_CODE#1, supplying analysis code definitions.
• GMF_BURDEN_ASSOCIATION_PK / _U1 — the unique indexes enforcing identity and preventing duplicate associations.