Search Results amw_process_objectives_b




Overview
Explore in AI Chat

Overview

AMW_PROCESS_OBJECTIVES_B is the base table that stores the non-translatable attributes of Process Objectives within the Oracle E-Business Suite Internal Controls Manager (AMW) module. In ETRM terms, a "process objective" is a control-oriented statement describing what a business process is intended to achieve; the AMW module uses these objectives as anchor points for risk assessment, control association, and compliance monitoring across an organization's process hierarchy. The table was introduced in the 12.1.1 code line and continues to be referenced in 12.2.2, though the product documentation explicitly flags the module as Obsolete, meaning it is retained for backward compatibility and historical data rather than for new functional deployments.

The ETRM metadata for this object describes it as a base table for non-translatable attributes, which implies the existence of a companion _TL table (for translated name/description fields). From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone, suggesting that AMW_PROCESS_OBJECTIVES_B most closely resembles a hub-and-satellite combination collapsed into a single physical table. The presence of descriptive attributes (attribute1–attribute15, start/end dates, objective type) alongside the primary key makes it effectively a satellite sitting on the PROCESS_OBJECTIVE_ID hub.

Key Information Stored

The table exposes 28 documented columns in the 12.1.1 physical schema, owned by the AMW schema. The most significant columns are:

The unique index AMW_PROCESS_OBJECTIVES_B_U1 is defined on PROCESS_OBJECTIVE_ID, which mirrors the primary key rather than defining a separate business key. No independent business-key candidate is documented; in practice the human-readable objective name resides in the companion translation table.

Common Use Cases and Queries

Typical usage centers on internal audit and compliance dashboards. Analysts join AMW_PROCESS_OBJECTIVES_B to its translation table and to the association tables to reconstruct the objective-to-risk-to-control map. A representative query:

SELECT po.PROCESS_OBJECTIVE_ID,
       po.OBJECTIVE_TYPE,
       po.START_DATE,
       po.END_DATE
FROM   AMW.AMW_PROCESS_OBJECTIVES_B po
WHERE  po.SECURITY_GROUP_ID = :p_security_group_id
  AND  TRUNC(SYSDATE) BETWEEN po.START_DATE AND NVL(po.END_DATE, SYSDATE);

Other scenarios include extracting new or changed objectives since the last ETL run using LAST_UPDATE_DATE, reconciling objective counts per OBJECTIVE_TYPE for management reporting, and auditing access by grouping through SECURITY_GROUP_ID. Because the module is obsolete, most production queries today are read-only reporting and historical migration extracts rather than transactional operations.

Related Objects

The foreign-key relationships documented in the ETRM metadata show this table as a parent to three dependent tables and a child of one:

These relationships confirm that AMW_PROCESS_OBJECTIVES_B functions as the central hub for the AMW objective model, with downstream links driving the risk-and-control association graph used across the Internal Controls Manager module.