Results for “amw_process”

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

Overview

AMW_PROCESS is a core table within the Oracle E-Business Suite Internal Controls Manager (AMW) module. It stores the master definition of business processes that are subject to internal control, risk assessment, and certification activities. Each row represents a versioned process record, capturing descriptive attributes, ownership assignments, approval and certification statuses, and aggregate counts of associated controls and risks. The table resides in the AMW schema and contains 56 documented columns in the ETRM 12.1.1 schema, with the same structure carried forward in 12.2.2.

From a dimensional modeling perspective, the documented foreign key relationship to FND_SECURITY_GROUPS and the standalone composition of the object suggest classifying AMW_PROCESS as a satellite entity in Data Vault terms, keyed by a process hub. Because it carries the descriptive and status attributes of a process revision rather than representing a pure intersection of two entities, it is best modeled as an attribute-bearing satellite attached to a process business key, with the security group acting as a referencing hub.

Key Information Stored

The table is structured around a surrogate primary key and three unique business-key candidates documented as unique indexes.

• PROCESS_REV_ID — surrogate identifier for the process revision; enforced by unique index AMW_PROCESS_U1 and functioning as the primary key.
• PROCESS_ID and REVISION_NUMBER — joint business key (unique index AMW_PROCESS_U2) linking a process to a specific revision.
• PROCESS_CODE and REVISION_NUMBER — alternative user-facing business key (unique index AMW_PROCESS_U3).
• NAME and PROCESS_TYPE — descriptive identity and classification of the process.
• PROCESS_CATEGORY and CLASSIFICATION — grouping and control-relevant classification metadata.
• PROCESS_OWNER_ID, FINANCE_OWNER_ID, and APPLICATION_OWNER_ID — ownership assignments referencing persons or parties.
• APPROVAL_STATUS, APPROVAL_DATE, APPROVAL_END_DATE — approval lifecycle tracking.
• CERTIFICATION_STATUS — certification state of the process revision.
• SIGNIFICANT_PROCESS_FLAG, STANDARD_PROCESS_FLAG, STANDARD_VARIATION — flags driving scoping and standardization logic.
• CONTROL_COUNT, RISK_COUNT, CONTROL_COUNT_LATEST, RISK_COUNT_LATEST — aggregate counts of associated controls and risks.
• START_DATE, END_DATE, DELETION_DATE — effective dating and logical deletion.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS enforcing row-level security.
• OBJECT_VERSION_NUMBER — optimistic locking for concurrent updates.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the 15 ATTRIBUTE flex columns for extensibility.

Common Use Cases and Queries

AMW_PROCESS is queried extensively by internal control dashboards, certification workflows, and audit reporting. A typical query retrieves the latest approved revision of each process for a given security group:

• Listing significant processes by owner: SELECT PROCESS_CODE, NAME FROM AMW_PROCESS WHERE SIGNIFICANT_PROCESS_FLAG = 'Y' AND PROCESS_OWNER_ID = :owner AND SECURITY_GROUP_ID = :sg
• Retrieving the current revision: SELECT * FROM AMW_PROCESS WHERE PROCESS_ID = :id ORDER BY REVISION_NUMBER DESC
• Approval backlog reporting: SELECT PROCESS_CODE, APPROVAL_STATUS FROM AMW_PROCESS WHERE APPROVAL_STATUS <> 'APPROVED'
• Control/risk coverage summaries using CONTROL_COUNT_LATEST and RISK_COUNT_LATEST.

These patterns support SOX scoping, process owner attestation, and management reporting on control coverage.

Related Objects

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to enforce row-level security.
• AMW control and risk association tables — joined via PROCESS_ID or PROCESS_REV_ID to populate CONTROL_COUNT and RISK_COUNT.
• AMW process certification and approval history tables — keyed by PROCESS_REV_ID.
• FND_USER — referenced indirectly through PROCESS_OWNER_ID, FINANCE_OWNER_ID, and APPLICATION_OWNER_ID for owner display.
• AMW_ORGANIZATION / AMW_ORG assignments — joined via PROCESS_ID to derive ORG_COUNT.

These relationships establish AMW_PROCESS as the anchoring entity for internal control modeling in the AMW schema.