Results for “as_ref_rstrctn_map_b”

8 results




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

Overview

AS_REF_RSTRCTN_MAP_B is a table in the Oracle E-Business Suite Sales Foundation (AS) product family. According to the ETRM metadata, its documented description is "No Longer Used." This designation indicates that the object is a legacy or deprecated structure retained in the data model for historical continuity rather than for active functional processing. In Oracle EBS 12.1.1 and 12.2.2, Sales Foundation provides shared reference and setup infrastructure consumed by Oracle Order Management, Oracle Advanced Pricing, and related application modules; legacy objects such as this one are frequently encountered by administrators and developers auditing the schema.

The metadata explicitly states that the table is "Not implemented in this database." In practice, this means the physical table may be absent, empty, or retained only as a stub within a given environment. Its presence in data dictionaries and ETRM documentation should not be interpreted as evidence of active configuration.

Applying the heuristic Data Vault classification supplied in the metadata, the table is characterized as hub-leaning. This classification is a modeling suggestion: the table holds the RSTRCTN_MAP_ID identifier at its center, and both AS_REF_RESTRICTIONS and AS_REF_RSTRCTN_MAP_TL reference that identifier as a foreign key. This hub-like pattern is typical of a master identifier table in a normalized reference-data model, where the hub supplies the durable key and dependent objects carry descriptive or transactional attributes. Because the table is deprecated, the classification is historical rather than operational.

Key Information Stored

The documented metadata identifies only a single column explicitly, so the description of stored content is necessarily narrow:

  • RSTRCTN_MAP_ID — The primary key of the table, defined by the constraint AS_REF_RSTRCTN_MAP_B_PK. It is a surrogate identifier for a restriction map record. Because no unique business-key index is documented in the supplied metadata, no alternate natural key can be confirmed.

The naming convention common to Sales Foundation reference tables suggests column families that would ordinarily accompany such a primary key, such as the restriction map name, seed data flag, creation and update audit columns, and an active or enabled status indicator. However, none of these are present in the ETRM excerpt. Consultants should not assume their existence without verifying against the actual data dictionary view ALL_TAB_COLUMNS in the target environment.

Common Use Cases and Queries

Given the "No Longer Used" status, practical use cases are limited to schema auditing, impact analysis, and upgrade assessment rather than functional reporting. Typical investigative queries include:

  • Confirming physical presence: query ALL_TABLES and ALL_TAB_COLUMNS for OWNER = 'AS' and TABLE_NAME = 'AS_REF_RSTRCTN_MAP_B'.
  • Checking for residual data: SELECT COUNT(*) FROM AS.AS_REF_RSTRCTN_MAP_B; where the table exists.
  • Identifying dependent objects: query ALL_CONSTRAINTS and ALL_CONS_COLUMNS for constraints referencing AS_REF_RSTRCTN_MAP_B.
  • Assessing orphan relationships to AS_REF_RESTRICTIONS and AS_REF_RSTRCTN_MAP_TL during migration or purging exercises.

No supported functional flow should be built on this table. Any custom code or report that references it should be reviewed for removal or replacement with the current restriction-mapping mechanism documented for the installed release.

Related Objects

The metadata documents two foreign-key relationships in which other tables reference this one on RSTRCTN_MAP_ID:

  • AS_REF_RESTRICTIONS — Column RSTRCTN_MAP_ID references AS_REF_RSTRCTN_MAP_B. This table appears to hold restriction definitions associated with a given restriction map.
  • AS_REF_RSTRCTN_MAP_TL — Column RSTRCTN_MAP_ID references AS_REF_RSTRCTN_MAP_B. The TL suffix designates a translated or language-specific table, consistent with Oracle's MLS pattern, carrying the language-dependent attributes of the same logical record.

These two objects constitute the documented dependency set. Because both are also Sales Foundation reference structures, they share the legacy character of the parent table. Consultants should treat the trio as a single deprecated cluster and verify current status in each environment before relying on any of them for reporting or integration.