Results for “amw_ap_tasks_u2”

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

Overview

AMW.AMW_AP_TASKS is a transactional table within the Oracle E-Business Suite Audit Management Workbench (AMW) module. It stores the association between audit procedures and the project tasks that must be performed to satisfy those procedures. Users can attach tasks sourced from project templates to an audit procedure, and this table persists each such association. The task definition itself is not duplicated here; the table holds only the identifiers that point to the authoritative task and project records in the Projects (PA) schema. Task information is stored in PA_TASKS, while the parent project and template information resides in PA_PROJECTS_ALL.

The object is owned by the AMW schema and is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. In the ETRM 12.1.1 documentation the table is reported as VALID with 30 columns. From a Data Vault modeling perspective, the mined relationship structure suggests classifying AMW_AP_TASKS as a link table: it resolves a many-to-many relationship between audit procedures and project tasks, carrying only the foreign keys plus descriptive and WHO audit attributes rather than a durable business entity of its own.

Key Information Stored

The table centers on four business columns that define the association:

• AP_TASK_ID (NUMBER) — the surrogate primary key and audit procedure–task association unique identifier. Backed by unique index AMW_AP_TASKS_U1 and the primary key constraint AMW_AP_TASKS_PK.
• AUDIT_PROCEDURE_ID (NUMBER) — identifies the audit procedure to which tasks are attached.
• TASK_ID (NUMBER) — the task identifier; foreign key referencing TASK_ID in PA_TASKS.
• PROJECT_ID (NUMBER) — the project to which the task belongs; foreign key referencing PROJECT_ID in PA_PROJECTS_ALL.

The combination of AUDIT_PROCEDURE_ID, PROJECT_ID, and TASK_ID forms the business-key candidate enforced by unique index AMW_AP_TASKS_U2, preventing duplicate task assignments to the same procedure within the same project. Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) provide change auditing. Fifteen descriptive flexfield segments (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15, VARCHAR2 150) support client-specific extensions. SECURITY_GROUP_ID (foreign key to FND_SECURITY_GROUPS), OBJECT_VERSION_NUMBER, ORIG_SYSTEM_REFERENCE, REQUESTOR_ID, and SOURCE_CODE support multi-organization security, optimistic locking, and interface/import traceability.

Common Use Cases and Queries

Typical reporting asks which tasks belong to a given audit procedure, and which projects or templates those tasks originated from. A join from AMW_AP_TASKS through PROJECT_ID to PA_PROJECTS_ALL surfaces the project and template context, while joining through TASK_ID to PA_TASKS retrieves the task name and attributes:

• SELECT t.AP_TASK_ID, t.AUDIT_PROCEDURE_ID, t.TASK_ID, t.PROJECT_ID FROM AMW.AMW_AP_TASKS t WHERE t.AUDIT_PROCEDURE_ID = :p_procedure_id;
• SELECT t.AP_TASK_ID, pt.TASK_NAME, pa.PROJECT_NAME FROM AMW.AMW_AP_TASKS t, PA.PA_TASKS pt, PA.PA_PROJECTS_ALL pa WHERE t.TASK_ID = pt.TASK_ID AND t.PROJECT_ID = pa.PROJECT_ID AND t.AUDIT_PROCEDURE_ID = :p_procedure_id;
• Duplicate-detection: SELECT AUDIT_PROCEDURE_ID, PROJECT_ID, TASK_ID, COUNT(*) FROM AMW.AMW_AP_TASKS GROUP BY AUDIT_PROCEDURE_ID, PROJECT_ID, TASK_ID HAVING COUNT(*) > 1;

Because the AMW objects are not exposed through standard Oracle seeds, queries should be written against the AMW schema with the appropriate APPS grants, and security-group predicates (SECURITY_GROUP_ID) should be applied when querying across operating units. The ORIG_SYSTEM_REFERENCE and SOURCE_CODE columns are useful when auditing records created through interface or conversion routines.

Related Objects

• PA.PA_TASKS — referenced via AMW_AP_TASKS.TASK_ID = PA_TASKS.TASK_ID; the authoritative task definition.
• PA.PA_PROJECTS_ALL — referenced via AMW_AP_TASKS.PROJECT_ID = PA_PROJECTS_ALL.PROJECT_ID; holds the project/template header.
• FND_SECURITY_GROUPS — referenced via AMW_AP_TASKS.SECURITY_GROUP_ID; enforces multi-organization access control.
• AMW audit procedure tables — AUDIT_PROCEDURE_ID functionally joins to the AMW procedure definition entity, the parent of each task association.
• AMW_AP_TASKS_U1 / AMW_AP_TASKS_U2 — unique indexes enforcing the surrogate and business keys respectively.