Search Results gmf_batch_validations




Overview
Explore in AI Chat

Overview

GMF_BATCH_VALIDATIONS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Process Manufacturing (OPM) product family, where the GMF and GME prefixes denote objects associated with Oracle Process Manufacturing Financials and Manufacturing Execution respectively. The package encapsulates business logic used to validate batch-related transactions before they are processed, cancelled, or posted within the OPM environment. In EBS 12.1.1 and 12.2.2, packages of this class act as server-side validation layers that enforce data integrity rules governing production batches, resource transactions, and their downstream financial or inventory implications.

According to the documented metadata, GMF_BATCH_VALIDATIONS is classified as an "OTHER" API, meaning it is not part of a formal public API set such as the PL/SQL APIs published for external integration. It is referenced internally by the GME_API_PUB package, indicating its role as a supporting validation utility consumed by higher-level manufacturing APIs.

Key Procedures and Functions

The ETRM documentation identifies a single documented procedure within the package:

  • CHECK_CANCEL_BATCH — This routine performs validation logic that determines whether a manufacturing batch may be cancelled. In the OPM model, a batch can only be cancelled if it satisfies a series of business conditions, such as the absence of posted resource transactions, adherence to open or otherwise eligible fiscal periods, and consistency with calendar and period-status rules. The procedure evaluates these conditions and returns a validation result that callers use to permit or block the cancellation attempt.

The metadata lists no other documented procedures or functions. No parameter lists are published in the available documentation, and none are inferred here.

Tables Accessed

The package references the following tables through APPS synonyms, each serving a specific validation purpose:

  • GME_BATCH_HEADER — Holds the primary batch header record; the procedure checks batch existence, status, and attributes to determine cancellation eligibility.
  • GME_RESOURCE_TXNS — Records resource transactions charged to batches; the validation ensures no such transactions are posted for the batch being cancelled.
  • GMF_CALENDAR_ASSIGNMENTS — Associates calendars with organizations or accounting entities, providing the reference for period determination.
  • GMF_FISCAL_POLICIES — Defines fiscal policy configuration that governs how accounting periods are established.
  • GMF_PERIOD_STATUSES — Stores the open/closed status of accounting periods, which the validation consults to confirm the affected periods permit cancellation.
  • MTL_MATERIAL_TRANSACTIONS — Inventory transaction records; the validation confirms whether material movements have been posted for the batch before allowing cancellation.

Usage Notes

GMF_BATCH_VALIDATIONS is invoked internally rather than exposed as a public API. Its documented caller is GME_API_PUB, the public API package for process manufacturing execution functions. Invocation typically occurs when a user cancels a batch through the OPM Batch Maintenance forms or when a programmatic cancellation request is submitted through GME_API_PUB. The CHECK_CANCEL_BATCH routine functions as a guard: prior to the actual cancellation, callers execute the validation to prevent data corruption that would arise from cancelling a batch with posted financial or inventory activity, or from operating against closed fiscal periods. Because it reuses the same validation package across both online form flows and programmatic interfaces, GMF_BATCH_VALIDATIONS enforces consistent cancellation rules throughout the OPM application. Customizations should avoid modifying the package directly and should instead rely on the GME_API_PUB entry points to preserve upgrade safety.