Search Results create_flex_batch_header

Overview

APPS.GME_VALIDATE_FLEX_FLD_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Process Manufacturing (OPM/GME) product family. Its purpose is to centralize the validation and population of descriptive flexfield (DFF) data associated with the core Process Manufacturing transactional entities — batch headers, batch steps, step activities, step resources, material details, resource transactions, and process parameters. Because these entities each expose flexfield-enabled columns, the package isolates the logic required to read the enabled flexfield structure, evaluate whether context columns are required, and validate or default the corresponding flex values before a transaction is written.

The package takes its configuration from package-level globals such as the application short name, application ID, flexfield name, flex-enabled flag, context column name, and context-required flag, all initialized with wildcard defaults and populated at runtime. The header comment identifies the revision as 120.3 and notes that the initial validation routines were introduced under enhancement request BUG#3406639.

Key Procedures and Functions

• VALIDATE_FLEX_BATCH_HEADER — validates flexfield values on a GME_BATCH_HEADER record, returning the corrected record and a return status.
• VALIDATE_FLEX_BATCH_STEP — validates flexfield values on a GME_BATCH_STEPS record.
• VALIDATE_FLEX_STEP_ACTIVITIES — validates flexfield values on a GME_BATCH_STEP_ACTIVITIES record.
• VALIDATE_FLEX_STEP_RESOURCES — validates flexfield values on a GME_BATCH_STEP_RESOURCES record.
• VALIDATE_RSRC_TXN_FLEX — validates flexfield values on a GME_RESOURCE_TXNS record; added by Punit Kumar.
• VALIDATE_FLEX_MATERIAL_DETAILS — validates flexfield values on a GME_MATERIAL_DETAILS record; rewritten under BUG#5078853.
• VALIDATE_FLEX_PROCESS_PARAM — validates flexfield values on a GME_PROCESS_PARAMETERS record; extended by Nsinha to accept a parameter controlling flexfield validation as part of the GME_Process_Parameter_APIs_TD work.
• CREATE_FLEX_BATCH_HEADER, CREATE_FLEX_MATERIAL_DETAILS, CREATE_FLEX_BATCH_STEP, CREATE_FLEX_STEP_ACTIVITIES, CREATE_FLEX_STEP_RESOURCES, CREATE_FLEX_PROCESS_PARAM, CREATE_FLEX_RESOURCE_TXNS — the CREATE counterparts that populate or default flexfield values for newly created records before persistence.

Tables Accessed

• FND_APPLICATION — used to resolve the application short name and application ID that identify the flexfield definition to be validated.
• GME_BATCH_HEADER — batch-level header flexfield storage.
• GME_BATCH_STEPS — batch step flexfield storage.
• GME_BATCH_STEP_ACTIVITIES — step activity flexfield storage.
• GME_BATCH_STEP_RESOURCES — step resource flexfield storage.
• GME_MATERIAL_DETAILS — material detail flexfield storage.
• GME_PROCESS_PARAMETERS — process parameter flexfield storage.
• GME_RESOURCE_TXNS — resource transaction flexfield storage.

These tables are referenced through APPS synonyms; the package reads their flexfield attribute columns and returns validated values in the corresponding record structures.

Usage Notes

As a PVT package, GME_VALIDATE_FLEX_FLD_PVT is not a public API and should not normally be called directly by customer extensions. It is invoked internally by the Process Manufacturing transaction APIs, including the GME_Process_Parameter_APIs family, and is referenced by ten other packages according to the documented metadata. Validation occurs during both create and update flows for the affected entities, ensuring that descriptive flexfield values satisfy the application's flexfield rules before the record reaches the database.

Custom code should prefer the public OPM APIs, which in turn call this package. When the metadata does not fully describe parameter signatures, developers should inspect the package specification in the EBS instance rather than assume a calling convention.