Search Results exception_present_flag

Overview

The table AMW.AMW_PROCESS_ORG_RELATIONS is an Oracle E-Business Suite (EBS) application table owned by the AMW schema (Oracle Process Manufacturing / Manufacturing Execution System component). According to its FND Design Data registration, the object is classified as VALID and resides in the APPS_TS_TX_DATA tablespace. Its documented purpose is to hold the process hierarchy in organizations — that is, the parent/child relationships between manufacturing processes as scoped to a specific inventory organization.

Each row represents a single directed relationship between a parent process and a child process within an organization, with an associated relation instance identifier. Because the table stores link-like relational associations (parent-to-child) rather than descriptive attributes of a single entity, its heuristic Data Vault classification as a standalone object — effectively functioning as a link between parent and child process entities — is a reasonable modeling suggestion. The EXCEPTION_PRESENT_FLAG column, which drove the user's search, is a descriptive attribute carried on that link rather than on either endpoint process.

Key Information Stored

The table contains twelve documented columns. The most operationally significant are:

• ORGANIZATION_ID – the inventory organization context for the hierarchy; a core business key discriminator.
• PARENT_PROCESS_ID – identifier of the parent process in the relationship.
• CHILD_PROCESS_ID – identifier of the child process in the relationship.
• INSTANCE_ID – the relation instance identifier, a surrogate-style key distinguishing one relation occurrence from another.
• EXCEPTION_PRESENT_FLAG (VARCHAR2) – flag indicating whether an exception exists on this relation; the column most commonly queried by users investigating manufacturing exceptions.
• OBJECT_VERSION_NUMBER – used for optimistic locking, protecting concurrent updates to relation rows.
• SECURITY_GROUP_ID – supports hosted (multi-tenant) environments and is the only documented foreign key, referencing FND_SECURITY_GROUPS.
• WHO columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard audit trail information.

No primary-key unique index is documented for this object; the natural business key is the combination of ORGANIZATION_ID, PARENT_PROCESS_ID, and CHILD_PROCESS_ID, while INSTANCE_ID behaves as a surrogate relation key.

Common Use Cases and Queries

The primary use case is traversing or reporting on the process hierarchy per organization, and specifically isolating relations marked by an exception.

• Find exceptions in an organization:
  SELECT ORGANIZATION_ID, PARENT_PROCESS_ID, CHILD_PROCESS_ID, INSTANCE_ID
FROM AMW.AMW_PROCESS_ORG_RELATIONS
WHERE EXCEPTION_PRESENT_FLAG = 'Y' AND ORGANIZATION_ID = :org_id;
• Enumerate the children of a given parent process:
  SELECT CHILD_PROCESS_ID FROM AMW.AMW_PROCESS_ORG_RELATIONS
WHERE PARENT_PROCESS_ID = :parent_id AND ORGANIZATION_ID = :org_id;
• Audit recently changed relations using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Reporting: join to process definition tables to produce hierarchy reports and exception dashboards.

Related Objects

Per the documented dependencies, AMW_PROCESS_ORG_RELATIONS does not reference any other database object, and it is referenced by the APPS synonym AMW_PROCESS_ORG_RELATIONS. The single documented foreign key joins SECURITY_GROUP_ID to FND_SECURITY_GROUPS. In practice, the parent and child process identifiers are meaningful only when joined to the process definition entities they represent, and ORGANIZATION_ID resolves to the organization definition table. Where exception values are stored as lookup codes, they may be validated against Oracle EBS lookup types. These join paths — FND_SECURITY_GROUPS, the process definitions, and the organization table — constitute the principal related objects for query and reporting purposes.