Search Results amw_process_organization




Overview
Explore in AI Chat

Overview

The AMW_PROCESS_ORGANIZATION table belongs to the AMW (Internal Controls Manager) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the association between processes and organizations, effectively acting as the intersection entity that links a defined process to one or more organization units within the enterprise governance framework. This association model supports the Internal Controls Manager's requirement to track which processes apply to which organizations, together with certification, audit, and approval metadata.

The product is marked as obsolete in the ETRM documentation, and the table is recorded as not implemented in the documented database. Consequently, AMW_PROCESS_ORGANIZATION should be treated as a legacy or dormant object in current EBS environments, though the schema definition remains documented for reference and historical analysis.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table references HR_ALL_ORGANIZATION_UNITS via ORGANIZATION_ID and FND_SECURITY_GROUPS via SECURITY_GROUP_ID, while carrying its own descriptive and state-tracking attributes such as status flags, dates, and counts. This pattern is consistent with a satellite attached to a process-organization relationship hub or link, rather than a pure hub defining core business keys.

Key Information Stored

The table contains 63 documented columns. Among the most significant are:

Business-key uniqueness is enforced through indexes U1 (PROCESS_ORG_REV_ID), U2 (PROCESS_ID, ORGANIZATION_ID, REVISION_NUMBER), U4 (PROCESS_ORGANIZATION_ID, REVISION_NUMBER), and U5 (ORGANIZATION_ID, PROCESS_ID, END_DATE, DELETION_DATE, APPROVAL_DATE, APPROVAL_END_DATE). These indexes reveal that the natural key combines process, organization, and revision context.

Common Use Cases and Queries

Typical usage centers on process-to-organization reporting and certification status tracking. A common query retrieves all processes associated with a given organization:

  • Join AMW_PROCESS_ORGANIZATION to HR_ALL_ORGANIZATION_UNITS on ORGANIZATION_ID to resolve organization names.
  • Filter by APPROVAL_STATUS or CERTIFICATION_STATUS to isolate processes pending certification or approval.
  • Use START_DATE and END_DATE to obtain the active association as of a reporting date.
  • Aggregate RISK_COUNT and CONTROL_COUNT by PROCESS_CATEGORY_CODE to summarize exposure across organizations.
  • Join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to enforce multi-organization access control in custom reports.

A representative pattern selects PROCESS_ID, ORGANIZATION_ID, REVISION_NUMBER, APPROVAL_STATUS, CERTIFICATION_STATUS, and START_DATE, filtered by SECURITY_GROUP_ID and restricted to records where END_DATE IS NULL for current associations.

Related Objects

The most significant related objects, based on documented foreign keys and relationship data, are:

  • HR_ALL_ORGANIZATION_UNITS — joined on AMW_PROCESS_ORGANIZATION.ORGANIZATION_ID; the primary organization dimension.
  • FND_SECURITY_GROUPS — joined on AMW_PROCESS_ORGANIZATION.SECURITY_GROUP_ID; controls access to records across organizations.
  • AMW_PROCESSES (process definition table referenced by PROCESS_ID) — the parent process catalog.
  • AMW_PROCESS_REVISIONS (referenced association via RL_PROCESS_REV_ID) — revision-level process metadata.
  • AMW_RISKS and AMW_CONTROLS — related risk and control entities whose counts are summarized in RISK_COUNT and CONTROL_COUNT.
  • FND_FLEX_VALUES — resolves ATTRIBUTE flexfield values and PROCESS_CATEGORY_CODE lookups.
  • FND_USER — resolves PROCESS_OWNER_ID, APPLICATION_OWNER_ID, and FINANCE_OWNER_ID to user identities.

Because the table is documented as obsolete and not implemented, integrators should verify actual presence in the target instance before building dependencies against it.