Results for “rstrctn_map_id”

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

Overview

AS_REF_RSTRCTN_MAP_TL is a table within the AS (Sales Foundation) product family of Oracle E-Business Suite. The ETRM documentation designates this object with the description "No Longer Used," and the metadata explicitly records it as "Not implemented in this database." This designation is significant for both functional and technical audiences: the table is a legacy artifact retained in the data model dictionary of older EBS releases but absent from active runtime schemas in the referenced 12.1.1 and 12.2.2 environments.

Conceptually, the table represents the translation layer for a restriction mapping entity. The "_TL" suffix follows the standard EBS multilingual naming convention, indicating a translation table that stores language-dependent descriptive attributes keyed to a base table. The corresponding base entity is AS_REF_RSTRCTN_MAP_B, which would hold the language-independent definition rows. Together these form a reference-mapping construct presumably used by Sales Foundation to associate customer, site, or order-reference attributes with restriction or eligibility rules.

From a heuristic Data Vault classification standpoint, the metadata's FK structure — a single foreign key from the translation table back to its base table — suggests a satellite-leaning model. In Data Vault terms, the base table behaves as a hub or link holding the durable business key, while AS_REF_RSTRCTN_MAP_TL functions as a multi-active satellite capturing language-specific descriptive context. This classification should be treated as a modeling suggestion rather than an authoritative schema designation.

Key Information Stored

Because the object is documented as not implemented, the column list is inferred from the primary key and unique index metadata rather than from a live data dictionary extract. The most important columns are:

• RSTRCTN_MAP_ID — Surrogate identifier for the restriction map. This is the join column linking the translation row to its parent base row in AS_REF_RSTRCTN_MAP_B.
• LANGUAGE — The language code identifying the translation locale of the row. Together with RSTRCTN_MAP_ID it forms the composite primary key.
• RESTRICTION — A descriptive attribute appearing as part of the unique key definition, likely holding the translated restriction text or name.

Two key constraints are documented. The primary key AS_REF_RSTRCTN_MAP_TL_PK is defined on (RSTRCTN_MAP_ID, LANGUAGE), establishing the row-level uniqueness of each translation. Separately, the unique index AS_REF_RSTRCTN_MAP_TL_UK is documented with the same leading columns plus RESTRICTION — this is the unique key referenced by the search term "as_ref_rstrctn_map_tl_uk." That the UK includes RESTRICTION suggests the design intended to prevent duplicate translated restriction values for a given map and language. The distinction between the surrogate PK (ID plus language) and this business-key candidate (ID, language, and text) is important when reconstructing historical queries or validating migrated data.

Common Use Cases and Queries

In active EBS environments running 12.1.1 or 12.2.2, direct querying of this table will typically fail because it is not created in the database. Application code paths that once referenced it have been retired or redirected to successor tables. Nonetheless, the following patterns remain useful for archaeology, migration validation, and impact analysis.

• Existence check: Query ALL_TABLES or USER_TABLES filtered on TABLE_NAME = 'AS_REF_RSTRCTN_MAP_TL' to confirm the table's absence in a target instance.
• Parent-child join reconstruction: A representative join would be SELECT b.RSTRCTN_MAP_ID, t.LANGUAGE, t.RESTRICTION FROM AS_REF_RSTRCTN_MAP_B b, AS_REF_RSTRCTN_MAP_TL t WHERE b.RSTRCTN_MAP_ID = t.RSTRCTN_MAP_ID AND t.LANGUAGE = USERENV('LANG'), illustrating how multilingual resolution was intended to work.
• Constraint discovery: Query ALL_CONSTRAINTS and ALL_INDEXES on the name pattern AS_REF_RSTRCTN_MAP_TL% to locate the PK and UK definitions in environments where they persist.
• Migration mapping: During upgrades from earlier releases, teams compile column inventories by parsing the DDL stored in FND_ tables or by scanning DBA_TAB_COLUMNS snapshots retained from the source instance.

Reporting use cases are limited given the retirement status, but historical reconciliation of restriction assignments across releases may still require reconstructing the translation semantics from surviving documentation.

Related Objects

Only one foreign key relationship is documented for this object, but surrounding reference objects are relevant for a complete picture.

• AS_REF_RSTRCTN_MAP_B — The base (non-translated) table. Joined via AS_REF_RSTRCTN_MAP_TL.RSTRCTN_MAP_ID = AS_REF_RSTRCTN_MAP_B.RSTRCTN_MAP_ID. This is the primary dependency and the parent of all translation rows.
• AS_REF_RSTRCTN_MAP_TL_PK — The primary key constraint on (RSTRCTN_MAP_ID, LANGUAGE).
• AS_REF_RSTRCTN_MAP_TL_UK — The unique index on (RSTRCTN_MAP_ID, LANGUAGE, RESTRICTION), referenced directly by user searches.
• FND_LANGUAGES — The standard EBS language reference, conceptually joined on LANGUAGE to resolve locale descriptions.
• FND_TABLES / FND_COLUMNS — Application Object Library metadata tables that would retain registration entries for this object.
• AS_REF_RSTRCTN_MAP_TL_S — A sequence, if historically defined, typically siblings base ID generation.

Any downstream view or concurrent program that previously referenced this translation table should be treated as a candidate for deprecation review.