Search Results ap_map_codes

Overview

The AP_MAP_CODES table is a core data dictionary table within the Oracle E-Business Suite Payables (AP) module, specifically designed as a QuickCode Map. It functions as a centralized repository for defining and storing mapping relationships between different sets of lookup codes. Its primary role is to facilitate data translation and integration by providing a configurable mechanism to link a source code (FROM_LOOKUP_CODE) from one domain to a corresponding target within the application. This enables consistent code conversion across interfaces, reports, and transactional processes, such as mapping external supplier codes to internal item categories or standardizing accounting flexfield values during invoice import.

Key Information Stored

The table's structure is purpose-built for defining mapping pairs. The critical columns, which also form the composite primary key, are MAP_TYPE_CODE and FROM_LOOKUP_CODE. The MAP_TYPE_CODE identifies the specific mapping rule or context to which a set of code pairs belongs, such as 'ACCOUNTING_FLEXFIELD' or 'SUPPLIER_CATEGORY'. This column is a foreign key to the AP_MAP_TYPES_B table, which defines and describes these mapping types. The FROM_LOOKUP_CODE stores the source or input code that requires translation. While the provided ETRM excerpt does not list all columns, a typical implementation includes a corresponding TO_LOOKUP_CODE column to store the target or output code, and potentially columns for effective dates, descriptions, and enabled flags to control the mapping's validity and usage.

Common Use Cases and Queries

A primary use case is the transformation of data during the Payables Open Interface (AP_INVOICES_INTERFACE) process, where external invoice data is mapped to internal EBS values. For example, a legacy system's expense type code can be mapped to an EBS account code combination. Common reporting queries involve joining this table to AP_MAP_TYPES_B to list all active mappings for a specific type. A fundamental query pattern is:

• SELECT map.map_type_code, map.from_lookup_code, map.to_lookup_code FROM ap_map_codes map, ap_map_types_b type WHERE map.map_type_code = type.map_type_code AND type.user_map_type_name = '&MAP_TYPE_NAME' AND NVL(map.enabled_flag, 'Y') = 'Y';

Technical consultants also query this table to troubleshoot data conversion errors in interfaces or to verify the setup for a new mapping rule before deployment.

Related Objects

AP_MAP_CODES has a direct and documented dependency on the AP_MAP_TYPES_B table, which serves as the master definition for all mapping types available in the system. The relationship is enforced by a foreign key constraint where AP_MAP_CODES.MAP_TYPE_CODE references AP_MAP_TYPES_B. This ensures referential integrity, meaning a mapping code cannot exist without a valid, predefined mapping type. While the provided metadata does not list objects that reference AP_MAP_CODES, it is intrinsically linked to interface and conversion logic within Payables, potentially referenced by public APIs, concurrent programs, and PL/SQL packages responsible for data validation and transformation, such as those underlying the Payables Open Interface.