Results for “gmf_burden_codes”

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

Overview

GMF_BURDEN_CODES is a Process Manufacturing Financials (GMF) table within the Oracle E-Business Suite entering the OPM Costing subsystem. It serves as the master repository for Percentage Burden Codes, which define indirect cost absorption rules applied to process manufacturing items and resources during cost rollup and cost calculation. Each row represents a discrete burden definition that can subsequently be associated with items, resources, or routings, and assigned percentage rates and priority sequencing through companion tables.

The table resides in the GMF schema, is documented as VALID, and contains 27 columns in the ETRM 12.2.2 physical schema (the same structure applies to 12.1.1, as OPM Costing tables were not materially re-architected between these releases). From a dimensional modeling perspective, the mined foreign-key structure suggests a hub-leaning classification: BURDEN_ID is referenced by three downstream tables (GMF_BURDEN_ASSOCIATION, GMF_BURDEN_PERCENTAGES, and GMF_BURDEN_PRIORITIES) but the table itself carries no foreign keys, making it a candidate hub in a Data Vault model with the dependent tables acting as links or satellites. This is a heuristic suggestion rather than a documented architectural designation.

Key Information Stored

The most operationally significant columns are:

• BURDEN_ID — The surrogate primary key, enforced by GMF_BURDEN_CODES_PK. All downstream references join on this column.
• BURDEN_CODE — The user-visible business key, enforced by the unique index GMF_BURDEN_CODES_U1. This is the value users enter on burden setup forms and reference in costing inquiries.
• BURDEN_DESC — Descriptive text for the burden code, used in reports and lookups.
• BURDEN_LEVEL — Defines the level at which the burden applies within the costing hierarchy.
• BURDEN_BASIS — Specifies the basis against which the burden percentage is calculated.
• ATTRIBUTE_CATEGORY — The descriptive flexfield context discriminator.
• ATTRIBUTE1 through ATTRIBUTE15 — The fifteen descriptive flexfield segments, available for client-specific extensions.
• DELETE_MARK — The OPM-standard soft-delete flag; rows are logically removed rather than physically deleted.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns maintained by the application.

The distinction between BURDEN_ID and BURDEN_CODE matters for integration design: foreign keys elsewhere in the schema reference the surrogate key, while end-user interfaces and data loads typically key on BURDEN_CODE. Any interface that inserts burden records must resolve BURDEN_ID from the sequence or from a lookup on the unique code.

Common Use Cases and Queries

Typical scenarios include validating burden setup before a cost rollup, extracting burden definitions for a costing data warehouse, and reconciling burden associations across items and resources. A basic retrieval of active burden codes follows:

• SELECT burden_id, burden_code, burden_desc, burden_level, burden_basis FROM gmf_burden_codes WHERE delete_mark = 0 ORDER BY burden_code;

To identify codes configured with flexfield values, query on ATTRIBUTE_CATEGORY combined with the relevant ATTRIBUTE segments. To audit recently modified setup, filter on LAST_UPDATE_DATE within a date range. Because three child tables reference BURDEN_ID, a common diagnostic is a left-join anti-pattern query that surfaces burden codes lacking any percentage or association rows — often the root cause when cost rollups fail to apply expected overhead. Reporting extracts for costing analytics typically join GMF_BURDEN_CODES to GMF_BURDEN_PERCENTAGES to present the effective rate per code.

Related Objects

Three documented tables reference GMF_BURDEN_CODES via the BURDEN_ID foreign key and constitute the immediate dependency set:

• GMF_BURDEN_ASSOCIATION (BURDEN_ID → GMF_BURDEN_CODES) — Maps burden codes to the items, resources, or other costing entities they apply to.
• GMF_BURDEN_PERCENTAGES (BURDEN_ID → GMF_BURDEN_CODES) — Stores the percentage rates effective for each burden code, typically across date ranges or cost scenarios.
• GMF_BURDEN_PRIORITIES (BURDEN_ID → GMF_BURDEN_CODES) — Defines the sequence in which multiple burden codes are applied when several overlap on the same basis.

Because GMF_BURDEN_CODES carries no foreign keys of its own, it is a terminal reference table within OPM Costing; all meaningful joins flow outward from BURDEN_ID. Cost rollup and burden calculation logic in OPM Costing reads these four tables together, and any customization or interface touching burden setup must respect the soft-delete convention and the surrogate-key relationships described above.