Search Results ap_map_types_b




Overview
Explore in AI Chat

Overview

The AP_MAP_TYPES_B table is a core reference table within the Oracle E-Business Suite Payables (AP) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master definition table for mapping rule types, which are foundational for automating the classification and assignment of transaction data. These mapping rules are critical for processes like corporate card transaction reconciliation, where incoming expense data from card providers must be systematically mapped to internal EBS entities such as expense report templates, expense types, and accounting codes. The table stores the unique codes and base attributes for each type of mapping rule, enabling a structured and configurable data transformation layer within Payables.

Key Information Stored

While the provided metadata does not list all columns, the structure centers on the primary key and associated descriptive data. The most critical column is MAP_TYPE_CODE, which is the table's primary key (AP_MAP_TYPES_B_PK). This column holds the unique identifier for a specific category of mapping rule, such as 'CARD_EXP_TYPE' for expense type mapping or 'COUNTRY' for country-specific mappings. Other columns, typically inferred from standard EBS table design, would include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY for auditing. The user-facing name and description for each MAP_TYPE_CODE are stored in the related translation table, AP_MAP_TYPES_TL.

Common Use Cases and Queries

This table is primarily accessed during the setup and maintenance of corporate card programs and the processing of card transactions. Administrators define mapping types to categorize different rules. Common reporting and validation queries involve joining with dependent tables to ensure rule integrity. A fundamental query retrieves all defined mapping rule types:

  • SELECT map_type_code FROM ap_map_types_b WHERE enabled_flag = 'Y' ORDER BY map_type_code;

Another critical use case is troubleshooting mapping failures. A developer might join AP_MAP_TYPES_B to AP_MAP_CODES to analyze all active mapping rules of a specific type:

  • SELECT mt.map_type_code, mc.map_code, mc.meaning FROM ap_map_types_b mt, ap_map_codes mc WHERE mt.map_type_code = mc.map_type_code AND mt.map_type_code = 'CARD_EXP_TYPE';

Related Objects

AP_MAP_TYPES_B has defined foreign key relationships with several key Payables tables, as documented in the metadata:

  • AP_CARD_PROGRAMS_ALL: This table references AP_MAP_TYPES_B twice. The column CARD_EXP_TYPE_MAP_TYPE_CODE links to a mapping type for expense categories, and COUNTRY_MAP_TYPE_CODE links to a mapping type for country-specific rules.
  • AP_MAP_CODES: This child table stores the individual mapping rules (values and targets) for each MAP_TYPE_CODE defined in AP_MAP_TYPES_B. The foreign key is on AP_MAP_CODES.MAP_TYPE_CODE.
  • AP_MAP_TYPES_TL: This is the translation table that provides the language-specific name and description for each MAP_TYPE_CODE, joined on the MAP_TYPE_CODE column.