Search Results ec_execution_utils




Overview

EC_EXECUTION_UTILS is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Execution layer of the E-Commerce Gateway (EC/ECE) product family and forms part of the application's technical infrastructure rather than a business-facing API. Its primary function is to support the runtime execution of the E-Commerce Gateway inbound processing model by dynamically loading mapping definitions, assigning values to interface columns, and invoking the stored procedures registered against a given transaction. It works alongside the sibling package EC_UTILS and the ECE_* interface packages to move data through the staging, mapping, and application stages of the interface cycle.

Key Procedures and Functions

The documented package exposes three procedures and functions:

  • RUNPROC — Executes a stored procedure dynamically. It is the central routine that takes a registered procedure name from the mapping metadata and invokes it at runtime, allowing the E-Commerce Gateway to drive user-defined or seeded logic without hard-coded calls.
  • ASSIGN_VALUES — Assigns values to interface columns during record processing. This routine resolves the source-to-target relationships defined in the mapping tables and populates the staging structure consumed by downstream interface programs.
  • LOAD_MAPPINGS — Loads mapping definitions into memory or into working structures so that they can be referenced efficiently during a batch execution. It reads the mapping metadata and prepares the runtime context used by RUNPROC and ASSIGN_VALUES.

No parameter lists are documented in the ETRM metadata, and none should be assumed.

Tables Accessed

The package body references a defined set of ECE configuration and staging tables through APPS synonyms:

It also depends on the standard PL/SQL packages DBMS_DESCRIBE, DBMS_SQL, DBMS_UTILITY, and PLITBLM, and on EC_DEBUG and ECE_ERROR_HANDLING_PVT for diagnostics and error capture.

Usage Notes

EC_EXECUTION_UTILS is not an end-user API and is not typically invoked from a form. It is called internally by E-Commerce Gateway processing packages during inbound interface execution, and it is referenced by three other database objects. Customizations that extend ECE mapping behavior — for example adding a new procedure mapping or a column rule — will be exercised through this package without directly calling it. Developers debugging inbound interfaces may trace its activity through EC_DEBUG output, and any modification to ECE_PROCEDURE_MAPPINGS, ECE_COLUMN_RULES, or the interface table/column definitions will directly affect its behavior. Because the package is not referenced by any external object outside the APPS schema, it should be treated as internal implementation and not as a supported integration point.