Search Results sign_off_status_code

Overview

APPS.AMW_AUDIT_PROJECTS_V is a valid, internal Oracle E-Business Suite view owned by the APPS schema. It exposes audit project information maintained within the Oracle Audit Management Workbench (AMW) module, presenting a denormalized, joined representation of audit engagement records alongside their associated Oracle Projects (PA) project definitions. The view carries the FND Design Data identifier AMW.AMW_AUDIT_PROJECTS_V and is registered as an internal view type, meaning it is intended for use by standard Oracle Applications programs rather than for direct customer access. Oracle Corporation explicitly does not support direct reading of applications data through this object outside of standard application code paths.

Because the view consolidates project identity, status, manager assignment, engagement type, sign-off tracking, and scope-change indicators into a single queryable structure, it serves as a reporting and integration bridge between AMW audit engagements and the Oracle Projects foundation. Users searching for scope_changed_flag will find that column in this view, representing whether the audit project scope has been modified from its original definition.

Underlying Base Objects

The view is defined over the following documented base objects:

• AMW_AUDIT_PROJECTS and AMW_AUDIT_PROJECTS_TL — the audit project header and translated attributes tables that drive most descriptive columns.
• PA_PROJECTS_ALL — the Oracle Projects table supplying project number, name, description, and project status.
• PER_ALL_PEOPLE_F — the HR person table used to resolve the audit manager person identifier and name.
• AMW_LOOKUPS, AMW_WORK_CATEGORIES_B, and AMW_WORK_TYPES_B — work types, categories, and lookup values supporting engagement classification.
• PA_PROJECT_PARTIES_UTILS — a utility package referenced in the view definition, typically to retrieve project party and role information.
• AMW_AUDIT_PROJECT — the underlying AMW audit project entity referenced in the dependency chain.

The join between AMW audit tables and PA_PROJECTS_ALL links audit engagements to the project structure that governs their execution, while PER_ALL_PEOPLE_F resolves audit manager identities. The presence of ORG_ID confirms the view is operating-unit (multi-org) aware, with project data filtered by operating unit context.

Key Columns

Important columns exposed include:

• AUDIT_PROJECT_ID and PA_PROJECT_ID — the AMW audit project identifier and the corresponding Oracle Projects project identifier.
• PROJECT_NUMBER, PROJECT_NAME, and DESCRIPTION — core project identification attributes.
• PROJECT_STATUS_CODE / PROJECT_STATUS_NAME — the project status from Oracle Projects.
• AUDIT_MANAGER_PERSON_ID / AUDIT_MANAGER_NAME — the assigned audit manager.
• AUDIT_PROJECT_STATUS — the audit-specific status of the engagement.
• START_DATE, COMPLETION_DATE, and CREATION_DATE — temporal landmarks.
• TEMPLATE_FLAG and CREATED_FROM_PROJECT_ID — indicate whether the record is a reusable template and its source project.
• ENGAGEMENT_TYPE_ID — classifies the engagement via AMW work types.
• SCOPE_CHANGED_FLAG — indicates whether the audit scope has been altered from the original.
• SOURCE_CODE — origin of the audit project record.
• SIGN_OFF_STATUS_CODE, SIGN_OFF_STATUS_MEANING, and SIGN_OFF_REQUIRED_FLAG — sign-off workflow state.
• ORG_ID — operating unit identifier.

Common Use Cases and Queries

Typical usage involves reporting on audit engagement status, tracking scope changes, and auditing sign-off compliance. A representative query retrieving scope-changed engagements follows:

• SELECT PROJECT_NUMBER, PROJECT_NAME, AUDIT_MANAGER_NAME, SCOPE_CHANGED_FLAG, AUDIT_PROJECT_STATUS FROM APPS.AMW_AUDIT_PROJECTS_V WHERE SCOPE_CHANGED_FLAG = 'Y' AND ORG_ID = :org_id;

Additional scenarios include identifying projects pending sign-off (SIGN_OFF_REQUIRED_FLAG = 'Y' with an unresolved SIGN_OFF_STATUS_CODE), isolating template projects (TEMPLATE_FLAG = 'Y'), and analyzing engagements by role or manager using the joined person data. Because the view is unsupported for direct access, these patterns should generally be embedded within or derived from standard Oracle Applications programs rather than executed standalone in production.