Search Results check_costing

Overview

The APPS.GMF_SUBLEDGER_PKG package is a Process Manufacturing (OPM) subledger utility within Oracle E-Business Suite. Its role is to support the transfer and reconciliation of manufacturing cost transactions into the General Ledger subledger accounting process. In Oracle Process Manufacturing, shop-floor activity such as batch production, resource consumption, and material issue/return generates cost transactions that must ultimately be posted to the correct accounting periods and ledgers. This package provides the underlying PL/SQL logic that validates costing periods, manages control records, and populates the global cost/subledger data structures required before the accounting transfer can proceed.

The package is owned by the APPS schema and carries an OTHER API classification in the ETRM metadata, meaning it is a supporting internal utility rather than a published extension API. It operates against a mix of OPM-specific tables (GME, GMF, GEM) and shared Oracle Financials and HR tables (GL, FND, HR), reflecting its bridging function between manufacturing cost data and the Financials accounting model. The package is recorded as VALID in the 12.2.2 environment.

Key Procedures and Functions

The documented package exposes nine procedures/functions. Their names and purposes are as follows:

• UPDATE_PROCESS — Coordinates the update portion of the subledger processing flow, applying changes to the relevant cost and period data.
• VALIDATE_PARAMETERS — Performs input validation on the parameters passed into the subledger process before execution proceeds, guarding against invalid period, ledger, or organization context.
• INSERT_CONTROL_RECORD — Inserts a control record used to track and manage the subledger run, supporting restartability and audit of the process.
• CHECK_COSTING — Verifies costing conditions, ensuring that items and transactions are eligible for cost processing before the subledger is updated.
• POPULATE_GLOBAL — Populates global package variables/structures used across the subledger routines within a session.

The remaining four documented procedures complete the operational flow alongside the above (for example, supporting population and update of subledger data), all sharing the same control-record and validation orientation. Parameter lists are not documented in the ETRM extract and are intentionally omitted here.

Tables Accessed

The package references the following tables through APPS synonyms:

• OPM/Costing: GME_BATCH_HEADER and GME_RESOURCE_TXNS (batch and resource transaction source data); GMF_PERIOD_BALANCES and GMF_PERIOD_STATUSES (OPM period balances and open/closed period status); GMF_FISCAL_POLICIES (fiscal calendar policy); CM_MTHD_MST (cost method master); GEM5_REFERENCE_NO_S (reference number sequence).
• General Ledger: GL_LEDGERS, GL_PERIODS, GL_PERIOD_SETS, GL_PERIOD_STATUSES, GL_SUBR_STA — used to resolve ledger, period, and subledger status context for the accounting transfer.
• Application and Logging: FND_APPLICATION and FND_LOG_MESSAGES, supporting application lookup and diagnostic logging.
• HR: HR_ORGANIZATION_INFORMATION, used to resolve organization/operating unit context.

Usage Notes

GMF_SUBLEDGER_PKG is an internal supporting package invoked by Oracle Process Manufacturing cost and subledger processing programs rather than called directly from a form or exposed custom API. It is typically executed as part of the OPM cost transfer / period-close flow, including concurrent programs that move manufacturing costs to the General Ledger subledger. The ETRM metadata records that no other packages reference it (referenced by 0 packages), which indicates it sits near the top of the OPM subledger call stack rather than being a shared dependency. Because it depends on SYS.STANDARD only at the package level, it is light on nested package dependencies, but its table footprint ties it tightly to OPM costing and GL period data. Customizations should avoid calling it directly and instead use supported OPM subledger and cost transfer APIs; any diagnostics should leverage its FND_LOG_MESSAGES output.