Search Results burden_code

Overview

The GMF_BURDEN_CODES table is a core data repository within the Oracle Process Manufacturing Financials (GMF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the master definition table for percentage-based burden codes used in the Oracle Process Manufacturing (OPM) Costing system. In manufacturing cost accounting, a burden code represents an indirect cost—such as overhead, utilities, or administrative expenses—that is applied to production costs as a percentage. This table stores the unique identifiers and codes for these burdens, serving as the authoritative source referenced by transactional and calculation tables throughout the costing lifecycle.

Key Information Stored

The table's structure is designed to ensure unique identification and reference of each burden code. The primary columns, as indicated by the documented primary and unique keys, are BURDEN_ID and BURDEN_CODE. The BURDEN_ID is the system-generated primary key (GMF_BURDEN_CODES_PK), a numeric identifier used for all internal foreign key relationships with associated tables. The BURDEN_CODE (enforced by the GMF_BURDEN_CODES_U1 unique key) is the user-defined alphanumeric code, such as 'OVH_ADMIN' or 'UTIL_PLANT', that identifies the burden in application forms and reports. While the provided metadata does not list all columns, typical supplementary columns would include descriptive fields (e.g., DESCRIPTION), enabled flags, and standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY).

Common Use Cases and Queries

This table is central to configuring and analyzing manufacturing overhead costs. Key use cases include setting up the burden structure for a new product line, validating burden codes assigned to cost components, and troubleshooting cost calculation errors. Common reporting needs involve listing all active burden codes or analyzing the definition of a specific code used in a cost simulation. A typical query to retrieve all burden codes would be:

• SELECT burden_id, burden_code, description, enabled_flag FROM gmf_burden_codes WHERE enabled_flag = 'Y' ORDER BY burden_code;

For integration or data validation, a join to the related percentages table is frequent:

• SELECT bc.burden_code, bp.cost_type_id, bp.percentage FROM gmf_burden_codes bc, gmf_burden_percentages bp WHERE bc.burden_id = bp.burden_id;

Related Objects

The GMF_BURDEN_CODES table has defined relationships with several key transactional tables, as per the provided foreign key metadata. The BURDEN_ID column is referenced by:

• GMF_BURDEN_ASSOCIATION: Links burden codes to specific inventory items or categories.
• GMF_BURDEN_PERCENTAGES: Stores the actual percentage rate applied for a given burden code and cost type.
• GMF_BURDEN_PRIORITIES: Defines the order of application when multiple burdens are assigned.

This relational structure ensures that the master definition in GMF_BURDEN_CODES governs how burdens are associated, calculated, and sequenced during the OPM cost rollup and settlement processes.