Search Results validate_validity_id_from_pub

Overview

The APPS.GME_REROUTE_BATCH_PVT package is a private (PVT-classified) PL/SQL API within Oracle EBS Process Manufacturing (OPM/GME). Its primary business function is to re-route a production batch to a different routing or recipe validity, thereby rebuilding the associated batch step structure, activities, charges, resources, and material requirements for that batch. In process manufacturing, a batch is executed against a routing derived from a recipe. When a batch must be reassigned to an alternate routing — for example, when a recipe version changes, when a validity rule is superseded, or when production engineering redirects a batch mid-cycle — this package performs the necessary deconstruction and reconstruction of the batch's step-level detail.

The package is classified as PVT, meaning it is intended for internal consumption by the OPM application rather than as a public integration API. The public-facing entry points are the higher-level packages that call into it.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents four procedures/functions within this package:

• REROUTE_BATCH — The core driver procedure. It performs the actual re-routing of a batch to a new validity/routing, orchestrating the deletion of existing step structures and the regeneration of steps against the new routing.
• VALIDATE_VALIDITY_ID_FROM_PUB — A validation routine invoked when the request originates from the public API layer. It confirms that the supplied recipe validity identifier is valid before the re-route proceeds.
• VALIDATE_VALIDITY_ID — The internal validation counterpart that verifies a validity rule identifier exists and is applicable to the target batch/recipe context.
• DELETE_ALL_STEPS — Removes all existing batch step records (steps, activities, charges, dependencies, items, and resources) associated with the batch prior to rebuilding them under the new routing.

Parameter lists are not enumerated in the metadata; only the names and intended purposes of these units are documented.

Tables Accessed

The package reads and writes a substantial set of OPM tables via APPS synonyms, reflecting the breadth of a batch's step hierarchy:

• GME_BATCH_HEADER — the batch master record whose routing is being changed.
• GMD_RECIPES and GMD_RECIPE_VALIDITY_RULES — source recipe and validity rules that define the target routing.
• FM_FORM_MST, FM_MATL_DTL, FM_ROUT_HDR — formula, material detail, and routing header information used to derive step content.
• GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_CHARGES, GME_BATCH_STEP_DEPENDENCIES, GME_BATCH_STEP_ITEMS, GME_BATCH_STEP_RESOURCES — the step-level child tables that are deleted and regenerated.
• GME_MATERIAL_DETAILS, GME_PROCESS_PARAMETERS, GME_RESOURCE_TXNS — material, parameter, and resource transaction detail supporting the re-routed batch.

The dependency on FND_API indicates the package returns standard Oracle API status codes (success/error/expected-error) and uses the FND message stack for error reporting.

Usage Notes

Because GME_REROUTE_BATCH_PVT is a private package, it is not intended for direct invocation by customers or external integrations. The metadata shows it is referenced by GME_API_MAIN and GME_API_PUB, which are the public OPM batch APIs. Callers should invoke the public API layer, which in turn validates the request via VALIDATE_VALIDITY_ID_FROM_PUB before delegating to REROUTE_BATCH. Typical invocation paths include OPM batch maintenance forms and concurrent programs that regenerate batch routing, as well as any custom code that legitimately calls the public GME API. Direct calls to this PVT package risk bypassing validation and should be avoided. The package is VALID and available in both EBS 12.1.1 and 12.2.2.