Search Results gme_validate_flex_fld_pvt




Overview
Explore in AI Chat

Overview

GME_VALIDATE_FLEX_FLD_PVT is a private (PVT) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Process Manufacturing (GME) product family and provides the validation and defaulting engine that governs flexible-field (descriptive flexfield) values captured against process manufacturing entities such as batches, batch steps, step activities, step resources, material details, process parameters, and resource transactions.

In Oracle EBS, descriptive flexfields allow customers to add attribute columns to standard GME tables without modifying the underlying data model. Before such attribute values can be persisted, they must be validated against the flexfield definition — checking value-set membership, required flags, security rules, and cross-field dependencies. GME_VALIDATE_FLEX_FLD_PVT encapsulates this logic in one centralized package so that every process manufacturing program that writes flexfield data applies identical validation semantics. The package name carries the classification suffix PVT, indicating it is an internal implementation package intended for use by GME APIs and forms rather than a public integration interface. Its dependencies confirm this role: it references FND_FLEX_APIS, FND_FLEX_DESCVAL, FND_MSG_PUB, FND_API, and FND_PROFILE for flexfield and message infrastructure, together with the GME batch, material, parameter, and resource tables.

Key Procedures and Functions

The ETRM documentation records fourteen documented program units in this package body. They divide naturally into two families: validation routines and creation/defaulting routines.

The naming symmetry (a VALIDATE_ and a CREATE_ variant for each entity) reflects a consistent pattern of cross-validating input and then materializing the flexfield row once validation succeeds.

Tables Accessed

Validation and creation routines operate directly on the GME transactional tables, using APPS synonyms resolved through the GME_*_DBL dependent packages:

Reference is made to the RDBMS STANDARD package and to FND_FLEX_APIS, FND_FLEX_DESCVAL, FND_MSG_PUB, and FND_PROFILE for flexfield resolution, message stack handling, and profile option evaluation.

Usage Notes

GME_VALIDATE_FLEX_FLD_PVT is an internal API. It is documented as not being referenced by any database object in the ETRM dependency report, yet the metadata notes it is referenced by ten other packages and it invokes itself recursively for nested structures — indicating use by sibling GME public APIs rather than direct invocation from SQL.

Typical invocation paths include process manufacturing forms (batch maintenance, step and resource entry, material detail maintenance) and concurrent programs or public GME APIs that create or update batch, material, parameter, and resource transaction data. Customizations should not call this package directly; instead, callers should route through the corresponding public GME API, which in turn delegates flexfield validation and creation here. Because the package depends on FND_MSG_PUB and FND_API, error conditions are surfaced through the standard EBS message stack and API return-status conventions. Behavior is identical across Oracle EBS 12.1.1 and 12.2.2; the 12.2.2 ETRM metadata confirms the package remains status VALID in the APPS schema.