Search Results revert_finalization

Overview

GMF_VIB is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Value In Batch (VIB) layer infrastructure within Oracle Process Manufacturing (OPM). The package exists to reconcile, calculate, and finalize the relationship between batch requirements and the cost layers maintained by the OPM costing engine. In the context of GMF_LAYERS and GMF_INCOMING_MATERIAL_LAYERS, GMF_VIB acts as a bridging layer that translates production batch demand into layer-aware requirement records.

In Oracle EBS 12.1.1 and 12.2.2, the package maintains status standards through a dependency on FND_API, ensuring consistent error handling and API conventions across the OPM stack. It is classified as OTHER under API classification, indicating that it is an internal utility rather than a public integration surface. Business users indirectly benefit through accurate backflush, material allocation, and cost layer consumption reporting for process manufacturing batches.

Key Procedures and Functions

• CREATE_BATCH_REQUIREMENTS — Populates persistent batch requirement records that describe the materials and quantities needed by a batch.
• UPDATE_BATCH_REQUIREMENTS — Modifies existing batch requirement records when quantities, statuses, or layer linkages change.
• DELETE_BATCH_REQUIREMENTS — Removes batch requirement records that are no longer valid, typically after rollback or re-planning.
• CREATE_TEMP_BATCH_REQUIREMENTS — Builds temporary requirement rows used during intermediate VIB calculation before finalization.
• CREATE_VIB_DETAILS — Generates Value In Batch detail records, tying batch material consumption to specific cost layers.
• FINALIZE_VIB_DETAILS — Commits the VIB detail set, locking in layer consumption for the batch.
• REVERT_FINALIZATION — Reverses a previously finalized VIB detail set, restoring prior layer state.
• ALLOCATE_INGREDIENTS — Distributes ingredient quantities across applicable layers, driving the allocation logic used by the VIB engine.

Tables Accessed

GMF_VIB reads and writes a focused set of OPM tables through APPS synonyms. It references GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ITEMS, GME_BATCH_STEP_RESOURCES, and GME_BATCH_STEP_DEPENDENCIES to establish batch structure and the sequencing context required for layer allocation. Material and resource activity is captured through GME_MATERIAL_DETAILS, GME_RESOURCE_TXNS, and GME_TRANSACTION_PAIRS. The layer infrastructure is serviced via GMF_INCOMING_MATERIAL_LAYERS, GMF_OUTGOING_MATERIAL_LAYERS, GMF_LAYERS, GMF_LAYER_ID_S, GMF_BATCH_REQUIREMENTS, GMF_BATCH_REQUIREMENTS_GTMP, and GMF_BATCH_VIB_DETAILS. Additionally, CR_RSRC_MST_B is referenced to resolve resource master data.

Usage Notes

GMF_VIB is not invoked directly by end users. It is referenced by eight sibling packages, including GME_API_MAIN, GME_CLOSE_BATCH_PVT, GME_RELEASE_BATCH_PVT, GME_UNRELEASE_BATCH_PVT, GME_REOPEN_BATCH_PVT, GME_DELETE_BATCH_STEP_PVT, GME_RESOURCE_ENGINE_PVT, and GMF_LAYERS itself. This dependency pattern indicates that batch lifecycle events — release, un-release, close, reopen, and batch step deletion — trigger the procedures within GMF_VIB, most notably the requirement and VIB detail routines. Because GMF_VIB also depends on GMF_LAYERS, recursion-style calls are possible when layer recalculations intersect with batch requirement regeneration. Customizations should treat GMF_VIB as an internal API: direct invocation risks corrupting VIB detail balances and layer consumption. Integration should occur through the higher-level GME_* batch APIs, with GMF_VIB remaining a controlled internal engine.