Results for “as_ref_restrictions”

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

Overview

AS_REF_RESTRICTIONS is a legacy table within the AS (Sales Foundation) product family of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases at the schema level but flagged in ETRM documentation as "No Longer Used." The object was originally conceived to store restriction records that governed how deliverable items, references, and restriction maps related to one another during the order-to-cash lifecycle — a pattern consistent with Sales Foundation's historical role in defining mandatory and optional document references, deliverables, and business rules applied to sales orders and their lines.

Within a Data Vault modeling view (heuristic classification mined from the foreign key structure), AS_REF_RESTRICTIONS is best classified as a link table. Its three outgoing foreign keys to AS_REF_RSTRCTN_MAP_B, AS_REF_DELIVERABLES, and HZ_REFERENCES indicate it functions as an associative junction, capturing relationships between a restriction map, a deliverable, and a reference record rather than describing a standalone business entity.

Key Information Stored

The documented structure is intentionally narrow, reflecting the associative nature of the table:

• RESTRICTION_ID — Surrogate primary key defined by constraint AS_REF_RESTRICTION_PK. This is the only column explicitly named in the documented primary key definition and serves as the unique row identifier without business meaning.
• RSTRCTN_MAP_ID — Foreign key to AS_REF_RSTRCTN_MAP_B. Links each restriction row to its governing restriction map entry, which defines the rule context.
• DELIVERABLE_ID — Foreign key to AS_REF_DELIVERABLES. Associates the restriction with a specific deliverable record from the Sales Foundation deliverable catalog.
• REFERENCE_ID — Foreign key to HZ_REFERENCES. Connects the restriction to the TCA/HZ party or reference record to which the rule applies.

Although the ETRM excerpt does not enumerate additional descriptive columns (for example attribute flags or effective dates), the FK trio above constitutes the entirety of the documented business-key candidates. Because no unique index on the combination of RSTRCTN_MAP_ID, DELIVERABLE_ID, and REFERENCE_ID is recorded, and because the table is described as "Not implemented in this database," developers should not assume enforcement of uniqueness on the natural key in any given environment. In most 12.1.1 and 12.2.2 instances the physical table is either absent or empty.

Common Use Cases and Queries

Because AS_REF_RESTRICTIONS is documented as no longer used and not implemented, direct queries against it in a live environment typically return no rows or raise ORA-00942. Practical uses therefore fall into three categories: schema archaeology, migration analysis, and reverse engineering of legacy restriction rules.

A typical investigative query joins all three parent tables:

• SELECT r.RESTRICTION_ID, r.RSTRCTN_MAP_ID, r.DELIVERABLE_ID, r.REFERENCE_ID FROM AS_REF_RESTRICTIONS r; — establishes whether the table is populated.
• SELECT r.RESTRICTION_ID, m.MAP_NAME, d.DELIVERABLE_NAME FROM AS_REF_RESTRICTIONS r, AS_REF_RSTRCTN_MAP_B m, AS_REF_DELIVERABLES d WHERE r.RSTRCTN_MAP_ID = m.MAP_ID AND r.DELIVERABLE_ID = d.DELIVERABLE_ID; — reconstructs the restriction context where data exists.
• SELECT r.RESTRICTION_ID, ref.REFERENCE_ID, ref.REFERENCE_TYPE FROM AS_REF_RESTRICTIONS r, HZ_REFERENCES ref WHERE r.REFERENCE_ID = ref.REFERENCE_ID; — surfaces the TCA reference linkage.

Reporting scenarios include impact analysis prior to upgrades, discovery of orphaned references during data cleansing, and documentation of deprecated Sales Foundation configuration. Because the descriptions in ETRM are sparse, any reconstruction should be treated as indicative rather than authoritative.

Related Objects

The following objects are documented as directly related through the FK/PK structure:

• AS_REF_RSTRCTN_MAP_B — Parent table reached via RESTRICTION_ID's sibling key RSTRCTN_MAP_ID; it defines the restriction map itself. Note the "_B" suffix, indicating a base (non-translated) table, which typically pairs with a "_TL" translation table.
• AS_REF_DELIVERABLES — Parent table of DELIVERABLE_ID; holds the deliverable definitions referenced by the restrictions.
• HZ_REFERENCES — TCA reference table joined via REFERENCE_ID; represents the customer, contact, or document reference affected by the restriction.

No views, PL/SQL APIs, or concurrent programs are documented in the ETRM excerpt as depending on AS_REF_RESTRICTIONS, consistent with its deprecated status. Developers extending Sales Foundation functionality in 12.1.1 or 12.2.2 should treat any dependency on this table as non-supported and migrate logic to currently maintained AS_REF_RSTRCTN_MAP_B-driven configuration.