Search Results ec_get_map_code

Overview

The APPS.EC_MAPPING_UTILS package is a utility package within the Oracle E-Business Suite E-Commerce Gateway (EC) module. Its principal business function is to manage the definition, retrieval, duplication, and upgrade of transaction mapping metadata used by E-Commerce Gateway interfaces. E-Commerce Gateway relies on mapping definitions to translate application data into the flat-file and EDI structures required for inbound and outbound business transactions such as purchase orders, invoices, and advance ship notices. The package provides a programmatic layer over the underlying ECE_% configuration tables, allowing mapping identifiers and codes to be resolved, entire mapping layouts to be copied, and upgrade-related structures to be reconciled between older and newer representations of the same mapping.

The package is owned by APPS and is classified as an OTHER API object rather than a public, supported interface. It contains 34 documented procedures and functions and is referenced by 13 other packages, indicating that it acts as a shared internal service used broadly across the E-Commerce Gateway codebase.

Key Procedures and Functions

The documented routines divide into several functional groups.

• Identifier resolution: EC_GET_MAP_ID returns the internal map identifier for a supplied map code, while EC_GET_MAP_CODE performs the inverse lookup, returning the map code associated with a given map identifier. Both accept an optional upgrade flag. Related helpers EC_GET_UPGRADE_MAP_ID and EC_GET_MAIN_MAP_ID resolve the upgrade and main map identifiers respectively.
• Upgrade status: The two overloaded forms of EC_GET_TRANS_UPGRADE_STATUS return the upgrade status for a transaction type, either scoped by map identifier or evaluated on transaction type alone.
• Upgrade operations: EC_UPGRADE_COLUMN_RULES, EC_UPGRADE_LAYOUT, and EC_UPGRADE_PROCESS_RULES migrate and reconcile column rules, mapping layout definitions, and process rules into their upgraded counterparts.
• Copy operations: A broad family of routines duplicates mapping data. These include EC_COPY_COLUMN_RULES, EC_COPY_DYNAMIC_ACTIONS, EC_COPY_EXTERNAL_LEVELS, EC_COPY_INTERFACE_COLUMNS, EC_COPY_INTERFACE_TABLES, EC_COPY_LEVEL_MATRICES, EC_COPY_MAPPINGS, and EC_COPY_PROCESS_RULES. Higher-level entry points EC_COPY_MAP_DATA_BY_MAPCODE, EC_COPY_MAP_DATA_BY_MAPID, and EC_COPY_MAP_DATA_BY_TRANS copy a complete mapping definition using a map code, a map identifier, or a transaction type and map type as the selection key.
• Deletion: EC_DELETE_COLUMN_RULES removes column rules associated with a map identifier.

Tables Accessed

The package reads and writes the core E-Commerce Gateway mapping tables through APPS synonyms. ECE_MAPPINGS and its upgrade companion ECE_MAPPINGS_UPG store the mapping headers keyed by map code and map type. ECE_INTERFACE_TABLES, ECE_INTERFACE_COLUMNS, and the upgrade tables ECE_INTERFACE_TBLS_UPG and ECE_INTERFACE_COLS_UPG define the interface table and column structures that mappings populate; ECE_INTERFACE_COLUMN_ID_S supplies sequence-generated column identifiers. ECE_COLUMN_RULES and ECE_COLUMN_RULES_UPG hold the column-level transformation rules. ECE_EXTERNAL_LEVELS and ECE_EXTERNAL_LEVELS_UPG, together with ECE_LEVEL_MATRICES and ECE_LEVEL_MATRICES_UPG, define hierarchical level structures. ECE_PROCESS_RULES and ECE_PROCEDURE_MAPPINGS capture process rule and procedure mapping definitions. Access to these tables supports both routine runtime resolution (identifier and status lookups) and administrative copy or upgrade activity.

Usage Notes

EC_MAPPING_UTILS is an internal utility package and is not intended for direct invocation by customer extensions. It is typically called from E-Commerce Gateway forms, concurrent programs, and the other EC packages that reference it, particularly during mapping setup maintenance and during the upgrade path that reconciles legacy and current mapping structures. The map code and map identifier lookups (EC_GET_MAP_CODE in particular) are commonly used as convenience resolution calls wherever a routine receives one key form but requires the other. Because the package performs DML against configuration tables in its copy, upgrade, and delete routines, callers must ensure appropriate transaction control and commit handling. The package header reflects a relatively stable implementation, with the source revision dated 2005, and it remains valid across both the 12.1.1 and 12.2.2 releases. Custom code should treat these routines as unsupported and rely on them only where no supported alternative exists.