Search Results amw_nonstandard_variations_b




Overview

The AMW_NONSTANDARD_VARIATIONS_B table is a core repository within the Oracle E-Business Suite Internal Controls Manager (AMW) module. It stores the details of non-standard process variations — that is, documented deviations between a standard process definition and an alternative ("non-standard") process version that an organization has adopted to accommodate regulatory, operational, or jurisdictional requirements. Internal Controls Manager relies on these records to preserve the audit lineage of every approved variation, ensuring that control testing, remediation tracking, and certification activities remain traceable to the baseline standard process.

From a Data Vault modeling perspective, the mined heuristic classification for this object is standalone. This is a modeling suggestion rather than a strict declaration: the table carries its own unique business key and only a single outbound foreign key (to FND_SECURITY_GROUPS), so it does not naturally decompose into a hub-and-link pair with satellite attributes. It is best treated as a self-contained entity table whose surrogate key anchors the variation definition.

Key Information Stored

The physical schema documents 16 columns, of which the following carry the substantive business meaning:

  • VARIATION_ROW_ID — the surrogate primary key and the business-key candidate, enforced by unique index AMW_NONSTANDARD_VARIATIONS_U1. Every downstream reference to a non-standard variation resolves through this identifier.
  • STD_PROCESS_ID and STD_PROCESS_REV_NUM — identify the baseline standard process and the specific revision against which the variation is measured.
  • NON_STD_PROCESS_ID and NON_STD_PROCESS_REV_NUM — identify the adopted non-standard process and its revision, forming the counterpart to the standard pair above.
  • STD_CHILD_ID and NON_STD_CHILD_ID — link the parent process definitions to their respective child sub-processes, enabling variation tracking at sub-process granularity rather than only at the top level.
  • START_DATE and END_DATE — define the effective period during which the variation is valid. The END_DATE value is meaningful for historical reporting, allowing point-in-time reconstruction of which variations were active.
  • SECURITY_GROUP_ID — the sole documented foreign key, referencing FND_SECURITY_GROUPS. It enforces multi-tenant data segregation so that variation records are visible only to the appropriate security group.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework (OAF) and Forms layers to prevent concurrent-update loss.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard Oracle EBS audit columns, supporting WHO-column auditing and reconciliation.

Common Use Cases and Queries

Typical usage centers on audit and compliance reporting: reconciling standard versus non-standard process coverage, identifying variations active during a given certification period, and verifying that a specific security group has visibility into the correct subset of variations. A representative query joins the effective-date window and security predicate:

  • SELECT v.VARIATION_ROW_ID, v.STD_PROCESS_ID, v.NON_STD_PROCESS_ID, v.START_DATE, v.END_DATE FROM AMW.AMW_NONSTANDARD_VARIATIONS_B v WHERE v.SECURITY_GROUP_ID = :p_security_group AND SYSDATE BETWEEN v.START_DATE AND NVL(v.END_DATE, SYSDATE);
  • A revision-comparison query filters on STD_PROCESS_REV_NUM <> NON_STD_PROCESS_REV_NUM to isolate variations where the standard and non-standard processes are on different revision levels.
  • A child-level drilldown joins on STD_CHILD_ID / NON_STD_CHILD_ID to report which sub-processes account for the greatest number of deviations.

Related Objects

  • FND_SECURITY_GROUPS — referenced by AMW_NONSTANDARD_VARIATIONS_B.SECURITY_GROUP_ID; the only documented foreign-key relationship and the determinant of row-level visibility.
  • AMW_NONSTANDARD_VARIATIONS_TL — the translation (MLS) table conventionally paired with the _B base table, carrying language-specific descriptive text keyed on VARIATION_ROW_ID.
  • AMW_STANDARD_PROCESSES_B — the standard process definition referenced through STD_PROCESS_ID and STD_PROCESS_REV_NUM.
  • AMW_STANDARD_PROCESS_CHILDREN — the child sub-process source resolved through STD_CHILD_ID.
  • AMW_PROCESSES_B — the general process master that supplies the non-standard process identity via NON_STD_PROCESS_ID.
  • AMW_PROCESS_CHILDREN — the child source resolved through NON_STD_CHILD_ID.

These joins collectively reconstruct the complete standard-versus-non-standard comparison path that Internal Controls Manager presents to compliance officers.