Search Results ec_copy_external_levels

Overview

EC_MAPPING_UTILS is a PL/SQL utility package owned by APPS that supports the mapping and transformation infrastructure of Oracle E-Business Suite's E-Commerce Gateway (EC) module. Its principal business function is to manage the metadata that governs how inbound and outbound EDI transactions are mapped between interface tables and the ECE_MAPPINGS configuration repository. The package provides helper functions that resolve mapping identifiers and codes, and a broad set of procedures that copy, upgrade, and delete mapping-related configuration such as column rules, process rules, level matrices, and interface columns. A recurring theme in the package is the upgrade path from legacy mapping structures to newer ones, evidenced by the parallel "_UPG" and "_MAIN" tables and the numerous upgrade-flagged functions. The package is internally significant in the EBS code base, with the ETRM metadata indicating it is referenced by 13 other packages.

Key Procedures and Functions

The package exposes lookup functions that translate between the surrogate and business keys used throughout the mapping model. EC_GET_MAP_ID resolves a map code to its numeric map identifier, while EC_GET_MAP_CODE performs the inverse. EC_GET_UPGRADE_MAP_ID and EC_GET_MAIN_MAP_ID return the upgrade and main (base) map identifiers respectively, supporting the parallel upgrade data structures. EC_GET_TRANS_UPGRADE_STATUS returns the upgrade status for a transaction type, with an overload accepting an explicit map identifier, allowing callers to determine whether a given transaction's mapping has completed upgrade.

The EC_COPY_* family performs the bulk of the package's work. EC_COPY_MAP_DATA_BY_MAPCODE, EC_COPY_MAP_DATA_BY_MAPID, and EC_COPY_MAP_DATA_BY_TRANS each orchestrate copying a full mapping definition using a different lookup key. The remaining copy procedures target finer-grained structures: EC_COPY_COLUMN_RULES, EC_COPY_PROCESS_RULES, EC_COPY_DYNAMIC_ACTIONS, EC_COPY_EXTERNAL_LEVELS, EC_COPY_INTERFACE_COLUMNS, EC_COPY_INTERFACE_TABLES, EC_COPY_LEVEL_MATRICES, and EC_COPY_MAPPINGS. The upgrade procedures EC_UPGRADE_COLUMN_RULES, EC_UPGRADE_LAYOUT, and EC_UPGRADE_PROCESS_RULES migrate existing configuration into the upgrade tables, while EC_DELETE_COLUMN_RULES removes column-rule definitions for a given map. The package is documented with 34 procedures and functions in total in the 12.2.2 ETRM registry.

Tables Accessed

All tables are accessed through APPS synonyms. ECE_MAPPINGS and its parallel ECE_MAPPINGS_UPG hold the core mapping definitions that the lookup and copy routines operate against. ECE_INTERFACE_TABLES and ECE_INTERFACE_COLUMNS (with the upgrade counterparts ECE_INTERFACE_TBLS_UPG and ECE_INTERFACE_COLS_UPG) describe the interface-table structure that mappings target. Column-level rules reside in ECE_COLUMN_RULES and ECE_COLUMN_RULES_UPG. Level configuration is stored in ECE_LEVEL_MATRICES and ECE_LEVEL_MATRICES_UPG, and external levels in ECE_EXTERNAL_LEVELS and ECE_EXTERNAL_LEVELS_UPG. Process logic is captured in ECE_PROCESS_RULES and ECE_PROCEDURE_MAPPINGS. The sequence ECE_INTERFACE_COLUMN_ID_S supplies interface column identifiers. The package both reads (for lookup and validation) and writes (during copy, upgrade, and delete operations) these tables.

Usage Notes

Because this package is a utility rather than a user-facing API, it is rarely invoked directly by end users. It is typically called from EBS setup forms and concurrent programs that configure or migrate mapping data, from the internal upgrade routines that convert legacy mappings to the upgraded structures, and from other PL/SQL packages — a dependency reflected in the 13 referencing packages documented in ETRM. Custom code should never construct parallel mapping logic manually; instead it should call the appropriate EC_COPY_* or EC_GET_* routine to preserve consistency between main and upgrade tables. The "BY_MAPCODE" variant is the conventional entry point when a caller knows the business map code rather than the numeric identifier, for example during configuration cloning or environment migration.