Search Results validate_flex_step_resources

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. It provides the internal infrastructure for validating and populating descriptive flexfield (DFF) attribute columns on the principal Process Manufacturing transactional entities: batch headers, batch steps, step activities, step resources, material details, resource transactions, and process parameters. The package shields calling APIs from the mechanics of resolving flexfield definitions and applying the appropriate validation rules to user-entered attribute values before persistence.

The package header declares several global variables that govern flexfield context resolution at runtime, including pkg_application_short_name, pkg_application_id, pkg_flex_field_name, pkg_flex_enabled, pkg_context_column_name, and pkg_context_required. These are used to identify the owning application and target flexfield, determine whether the flexfield is enabled, and establish whether a context segment is mandatory. The package carries an early header revision (120.3, dated 2006) and was extended over time by targeted bug fixes and feature changes, notably enhancements tracked under Bug#3406639 and Bug#5078853.

Key Procedures and Functions

The package exposes paired validation and creation routines for each supported entity. The validation routines accept an inbound row record and return an updated record along with a return status indicator, signalling success or failure of flexfield validation.

• VALIDATE_FLEX_BATCH_HEADER — validates flexfield attributes on a batch header record.
• VALIDATE_FLEX_BATCH_STEP — validates flexfield attributes on a batch step record.
• VALIDATE_FLEX_STEP_ACTIVITIES — validates flexfield attributes on a step activity record.
• VALIDATE_FLEX_STEP_RESOURCES — validates flexfield attributes on a step resource record.
• VALIDATE_RSRC_TXN_FLEX — validates flexfield attributes on a resource transaction record.
• VALIDATE_FLEX_MATERIAL_DETAILS — validates flexfield attributes on a material detail record; rewritten under Bug#5078853.
• VALIDATE_FLEX_PROCESS_PARAM — validates flexfield attributes on a process parameter record. This is the procedure referenced by the search term validate_flex_process_param. It accepts a process parameter record and a validation directive (p_validate_flexfields), added 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 — companion routines that build the flexfield attribute payload for each corresponding entity prior to insert or update.

Tables Accessed

The package references the following tables through APPS synonyms:

• FND_APPLICATION — resolves the application short name and application identifier used to locate the correct flexfield definition.
• GME_BATCH_HEADER — source and target of batch header flexfield validation.
• GME_BATCH_STEPS — source and target of batch step flexfield validation.
• GME_BATCH_STEP_ACTIVITIES — step activity records subject to flexfield validation.
• GME_BATCH_STEP_RESOURCES — step resource records subject to flexfield validation.
• GME_MATERIAL_DETAILS — material detail records subject to flexfield validation.
• GME_PROCESS_PARAMETERS — process parameter records, the entity handled by VALIDATE_FLEX_PROCESS_PARAM.
• GME_RESOURCE_TXNS — resource transaction records subject to flexfield validation.

Usage Notes

GME_VALIDATE_FLEX_FLD_PVT is classified as a private package and is not intended for direct invocation from forms or concurrent programs. It is referenced by approximately ten other packages, which are the public API layer that Process Manufacturing forms, concurrent programs, and external integrations call. Typical callers are the batch, material, resource transaction, and process parameter public APIs, which delegate flexfield handling to this package during record validation and creation.

Custom code should not call this package directly, because its signature and behaviour are subject to change without notice. Developers requiring flexfield validation for OPM entities should invoke the corresponding public API instead. The presence of IN OUT NOCOPY record parameters means callers must supply the full entity row; the package mutates flexfield attribute columns in place and reports outcome through the return status parameter.