Results for “ap_map_types_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_MAP_TYPES_TL is the translation (language) table for AP_MAP_TYPES_B within the Oracle E-Business Suite Payables (AP) module. The "_TL" suffix denotes that the table stores multilingual, descriptive attributes — specifically translated "meaning" and "description" text — for the rows defined in the base table. The base table AP_MAP_TYPES_B stores the language-independent, functional definition of a map type (such as code, enabled flag, and other operational attributes), while AP_MAP_TYPES_TL holds the human-readable, language-specific labels presented to users. In Oracle EBS 12.1.1 and 12.2.2, all translatable reference and setup entities follow this base/translation (B/TL) pattern, and AP_MAP_TYPES_TL is the translation counterpart for the Payables map type lookup.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. The foreign key to AP_MAP_TYPES_B on MAP_TYPE_CODE indicates that AP_MAP_TYPES_TL hangs off the map type hub (represented by the base table), making it a dependent satellite of descriptive, language-qualified attributes. It does not serve as a link or independent hub.

Key Information Stored

The documented physical schema contains 10 columns. The most significant are described below; the surrogate/business identifiers and the language-qualified descriptive attributes are central.

• MAP_TYPE_CODE — The business key linking each translation row to its parent row in AP_MAP_TYPES_B via the documented foreign key AP_MAP_TYPES_TL.MAP_TYPE_CODE → AP_MAP_TYPES_B. It identifies the map type being described.
• LANGUAGE — The language code (for example, US or an installed language) for which the following descriptive text is valid. LANGUAGE is a mandatory component of both the primary key and the business key.
• MEANING — The translatable, user-visible name of the map type, rendered in the specified LANGUAGE. This is the value presented in Payables application forms and list-of-values.
• DESCRIPTION — The translatable descriptive text providing additional detail about the map type.
• SOURCE_LANG — The language in which the row was originally authored, used by the translation framework to track the seed language.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS "WHO" auditing columns recording the user and timestamps of row creation and last modification.

The primary key is AP_MAP_TYPES_TL_PK, composed of (MAP_TYPE_CODE, LANGUAGE). A separate unique index, AP_MAP_TYPES_TL_U1, also spans (MAP_TYPE_CODE, LANGUAGE), confirming these two columns are the business-key candidates that jointly guarantee one translation row per map type per language.

Common Use Cases and Queries

The principal use of AP_MAP_TYPES_TL is to resolve a map type code into a language-specific label for display and reporting. A typical query joins the translation table to the base table and filters by LANGUAGE:

• Label resolution: SELECT b.map_type_code, tl.meaning, tl.description FROM ap_map_types_b b, ap_map_types_tl tl WHERE b.map_type_code = tl.map_type_code AND tl.language = USERENV('LANG');
• Coverage audit: identifying map types that lack a translation row for a given language by outer-joining AP_MAP_TYPES_TL to AP_MAP_TYPES_B.
• Reporting: embedding the meaningful name (rather than the raw code) into Payables map-type reports and concurrent program outputs.
• Data validation: confirming that the primary key combination of MAP_TYPE_CODE and LANGUAGE is unique before migration or data-load activities in 12.1.1 or 12.2.2.

Related Objects

The most significant related objects, based on the documented relationship data and the standard B/TL pattern, are:

• AP_MAP_TYPES_B — The base table holding language-independent map type definitions; related through MAP_TYPE_CODE (AP_MAP_TYPES_TL.MAP_TYPE_CODE → AP_MAP_TYPES_B). This is the primary parent of the translation table.
• AP_MAP_TYPES_TL_PK — The primary key constraint enforcing uniqueness on (MAP_TYPE_CODE, LANGUAGE).
• AP_MAP_TYPES_TL_U1 — The unique business-key index on (MAP_TYPE_CODE, LANGUAGE).
• AP_MAP_TYPES_VL / AP_MAP_TYPES_V — Commonly used translated views that join the base and translation tables to expose a single language-specific row, a standard companion object in the EBS B/TL pattern.
• Payables lookup and mapping setup components — Application forms and setup pages that consume the meaning and description values for display and selection.

Because AP_MAP_TYPES_TL stores only descriptive text, it is referenced primarily for read-only display and reporting rather than transactional processing, and any direct maintenance should be coordinated with the corresponding AP_MAP_TYPES_B row to preserve referential integrity.