Search Results construct_function

Overview

EGO_FUNCTIONS_BULKLOAD_PVT is a private PL/SQL package in the APPS schema that supports the bulk import of user-defined function metadata into the Oracle E-Business Suite extensibility framework (Ego). Functions in Ego represent named, externally callable business operations exposed through the Metadata Manager, and this package provides the programmatic machinery required to load those definitions and their associated parameters from interface staging tables into the production metadata repository in high-volume batches. Because it is classified as a PVT (private) API, it is not intended as a public integration surface; it exists to service the bulk loading routines owned by the Ego Metadata Manager product, including the closely related EGO_METADATA_BULKLOAD_PVT package.

The package mirrors the general bulk-loading pattern used throughout Ego: incoming records are first inserted into interface tables, validated and enriched, then transacted into base tables. EGO_FUNCTIONS_BULKLOAD_PVT handles the function header and function parameter portions of this pipeline, delegating shared orchestration to EGO_METADATA_BULKLOAD_PVT and calling cross-cutting services in EGO_METADATA_PUB and FND_API.

Key Procedures and Functions

The package exposes sixteen documented procedures organized around three logical phases.

• Header import and initialization: IMPORT_FUNCTIONS_INTF, INITIALIZE_FUNCTIONS, DELETE_PROCESSED_FUNCTIONS, and UPDATE_INTFC_FUNCTIONS manage the movement of function rows into the interface structures and their subsequent cleanup.
• Header processing: CONSTRUCT_FUNCTION, VALIDATE_FUNCTION, TRANSACT_FUNCTION, PROCESS_FUNCTIONS, and BULK_VALIDATE_FUNCTIONS construct the in-memory function definition, apply validation rules, and write validated rows to the base tables in set-based fashion.
• Parameter processing: INITIALIZE_FUNC_PARAMS, CONSTRUCT_FUNC_PARAM, VALIDATE_FUNC_PARAM, TRANSACT_FUNC_PARAM, PROCESS_FUNC_PARAMS, UPDATE_INTFC_FUNC_PARAMS, and BULK_VALIDATE_FUNC_PARAMS perform the equivalent lifecycle for function parameter records.

The parallel naming of header and parameter routines reflects the package's design intent: each entity passes through an initialize, construct, validate, transact, and bulk-validate sequence. EGO_FUNCTIONS_BULKLOAD_PVT itself references its own procedures recursively (for example, bulk-validate routines calling the single-record validators), and it is consumed by EGO_METADATA_BULKLOAD_PVT and EGO_ICC_BULKLOAD_PVT.

Tables Accessed

The package reads and writes interface tables EGO_FUNCTIONS_INTERFACE and EGO_FUNC_PARAMS_INTERFACE as the staging ground for inbound data. Validated functions are committed to the base tables EGO_FUNCTIONS_B, EGO_FUNCTIONS_S, and EGO_FUNCTIONS_TL, while parameters are committed to EGO_FUNC_PARAMS_B, EGO_FUNC_PARAMS_S, and EGO_FUNC_PARAMS_TL. Supporting metadata includes EGO_ACTIONS_B and EGO_ACTION_DISPLAYS_B (actions and their UI presentations), and EGO_MAPPINGS_B (mapping rules associated with functions).

Reference and utility tables include FND_LANGUAGES (for translated TL rows), FND_LOOKUP_VALUES (validating coded values), FND_NEW_MESSAGES (message text resolution), and MTL_INTERFACE_ERRORS (capturing row-level load errors so that failed records can be diagnosed in the standard interface error framework).

Usage Notes

EGO_FUNCTIONS_BULKLOAD_PVT is invoked indirectly rather than by end users. It is called from the Ego Metadata Manager bulk-loading concurrent programs and from EGO_METADATA_BULKLOAD_PVT and EGO_ICC_BULKLOAD_PVT during full or incremental metadata uploads. It is also a dependency of itself through internal recursion in the bulk-validate paths. Because the object is a private package, direct calls from custom code are not supported; integrations should target the published EGO_METADATA_PUB APIs or the documented interface tables. In Oracle EBS 12.1.1 and 12.2.2 environments the package is expected to appear as VALID in the APPS schema, and any INVALID status indicates a dependency or compilation issue in the Ego metadata stack that should be resolved before bulk metadata loading is attempted.