Search Results non_std_process_rev_num

Overview

AMW.AMW_NONSTANDARD_VARIATIONS_B is a transaction data table in the Oracle E-Business Suite Applications (AMW) schema that stores details of non-standard process variations. Its documented purpose is to record the mapping between a standard process (and its revision and child component) and the corresponding non-standard process (and its revision and child component), along with the effective date range during which the variation is active. The table is created under the FND Design Data definition AMW.AMW_NONSTANDARD_VARIATIONS_B, resides in the APPS_TS_TX_DATA tablespace, and is marked VALID in both Oracle EBS 12.1.1 and 12.2.2.

The object has a documented physical schema of 16 columns. Heuristic Data Vault classification derived from the foreign-key structure identifies this table as standalone. From a modeling perspective, it is best treated as a satellite of the standard/non-standard process relationship, since it carries descriptive and effective-dating attributes (START_DATE, END_DATE) keyed by a surrogate identifier rather than acting as an independent hub or a pure associative link. It has no child tables reported as dependent on it, which reinforces its role as a leaf-level attribute store.

Key Information Stored

The surrogate primary key is VARIATION_ROW_ID, a NUMBER column that stores the variation identifier and is enforced by the unique index AMW_NONSTANDARD_VARIATIONS_U1. In this schema the unique index is the documented business-key candidate, though the column itself is a system-generated surrogate.

• VARIATION_ROW_ID — unique variation identifier (unique index U1); the primary access path for single-row retrieval.
• STD_PROCESS_ID — the standard process identifier being varied.
• STD_PROCESS_REV_NUM — the revision number of the standard process; this is the column referenced in the user's search and appears as the second column of the non-unique composite index N1.
• NON_STD_PROCESS_ID — the non-standard (replacement) process identifier.
• NON_STD_PROCESS_REV_NUM — the revision number of the non-standard process.
• STD_CHILD_ID — the standard child component affected by the variation.
• NON_STD_CHILD_ID — the non-standard child component substituted in the variation.
• START_DATE / END_DATE — the effective date range over which the variation applies, supporting date-effective querying.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to prevent lost updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns.
• SECURITY_GROUP_ID — used in hosted (multi-tenant) environments.

Common Use Cases and Queries

The composite non-unique index AMW_NONSTANDARD_VARIATIONS_N1 covers STD_PROCESS_ID, STD_PROCESS_REV_NUM, NON_STD_PROCESS_ID, NON_STD_PROCESS_REV_NUM, STD_CHILD_ID, and NON_STD_CHILD_ID, making it the primary driver for lookups that resolve a standard process/revision to its non-standard counterpart. A typical query returns all active variations for a given standard process revision on a specific date:

SELECT variation_row_id, std_process_id, std_process_rev_num, non_std_process_id, non_std_process_rev_num, std_child_id, non_std_child_id, start_date, end_date FROM amw.amw_nonstandard_variations_b WHERE std_process_id = :p_process_id AND std_process_rev_num = :p_rev_num AND :p_as_of_date BETWEEN start_date AND NVL(end_date, :p_as_of_date) ORDER BY start_date;

Reporting scenarios include auditing which non-standard children were substituted for standard children within a manufacturing or process window, reconciling revisions used in production runs, and generating date-effective histories of variation changes. Because the table is standalone, joins in reporting are limited to the FND_SECURITY_GROUPS foreign key on SECURITY_GROUP_ID for hosted-environment filtering.

Related Objects

The documented FK data identifies one referenced object:

• FND_SECURITY_GROUPS — joined on AMW_NONSTANDARD_VARIATIONS_B.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID, used in hosted environments to scope rows.

Beyond the documented FK, schema usage implies that STD_PROCESS_ID, STD_PROCESS_REV_NUM, NON_STD_PROCESS_ID, and NON_STD_PROCESS_REV_NUM reference the corresponding process definition and revision entities, and STD_CHILD_ID / NON_STD_CHILD_ID reference child component definitions. The table does not reference any other object per the dependency report, and no dependent views or tables are documented.