Search Results gmf_burden_association




Overview
Explore in AI Chat

Overview

The GMF_BURDEN_ASSOCIATION table is a core data structure within Oracle E-Business Suite (EBS) Process Manufacturing Financials (GMF) module, specifically for Oracle Process Manufacturing (OPM) Costing. Its primary function is to store the definitions for percentage burden associations. In OPM Costing, a burden is an indirect cost, such as overhead, that is applied to the cost of a manufactured item. This table enables the system to associate a specific burden cost element with a source cost component and analysis code, and allocate it to a target cost component and analysis code based on a defined percentage. This mechanism is essential for accurate product cost calculation and absorption of overhead expenses in a process manufacturing environment, supporting both release 12.1.1 and 12.2.2 of Oracle EBS.

Key Information Stored

The table's design centers on linking source and target cost elements with a burden. The primary identifier is the system-generated BURDEN_ASSOCIATION_ID. The core logical data consists of two key pairs and a burden reference. The SOURCE_CMPNTCLS_ID and SOURCE_ANALYSIS_CODE identify the cost component class and analysis code from which the burden calculation originates. Conversely, the TARGET_CMPNTCLS_ID and TARGET_ANALYSIS_CODE identify the component class and analysis code to which the burden cost will be allocated. The BURDEN_ID is a foreign key to GMF_BURDEN_CODES, specifying which burden cost element is being applied. The table likely includes additional columns for the association percentage, effective dates, and control attributes to manage the lifecycle and validity of each burden association rule.

Common Use Cases and Queries

The primary use case is the configuration and maintenance of burden cost allocation rules during cost setup and the subsequent runtime calculation of item costs. A typical reporting query would join this table to its related master tables to produce a human-readable list of all active burden associations. For example:

  • Listing All Burden Associations: A common SQL pattern selects from GMF_BURDEN_ASSOCIATION (GBA), joining to CM_CMPT_MST_B for component class descriptions and GMF_BURDEN_CODES for the burden name, filtering on effective dates to show current rules.
  • Cost Rollup and Simulation: During a cost rollup, the costing engine queries this table to determine which burden costs, and at what percentages, should be applied to specific cost components of an item, directly impacting the final calculated standard cost.
  • Audit and Analysis: Analysts may query the table to understand overhead cost structures, validate costing setups, or troubleshoot discrepancies in reported product costs by tracing the burden associations applied.

Related Objects

The GMF_BURDEN_ASSOCIATION table is centrally connected to several key master tables via foreign key relationships, as documented in the ETRM metadata. These relationships ensure referential integrity and define the valid domain of values for its key columns.

  • GMF_BURDEN_CODES: Joined via BURDEN_ID. This table stores the definition of the burden cost elements themselves.
  • CM_CMPT_MST_B: Joined twice: once via SOURCE_CMPNTCLS_ID and once via TARGET_CMPNTCLS_ID. This table defines valid cost component classes.
  • CM_ALYS_MST: Joined twice: once via SOURCE_ANALYSIS_CODE and once via TARGET_ANALYSIS_CODE. This table defines valid cost analysis codes.

These relationships form the foundation for any query or process that needs to resolve the IDs stored in GMF_BURDEN_ASSOCIATION into their meaningful business descriptions.