Search Results sign_off_status

Overview

APPS.AMW_AUDIT_PROJECTS_VL is a multi-lingual (language-resolved) view owned by the APPS schema in Oracle E-Business Suite. It is registered under the FND Design Data repository as AMW.AMW_AUDIT_PROJECTS_VL and carries a status of VALID. The view presents audit project records maintained by the Oracle Audit Management application (the AMW product family) and exposes a denormalized projection that combines audit-project identity, project linkage, descriptive flexfield segments, and lifecycle attributes such as scope-change indicators and template flags.

The "_VL" suffix indicates that the view resolves translated columns through the language of the current session, following the standard EBS multilingual-view convention. For report developers and integrators who search on terms such as "sign_off_status," this view is typically reached through the audit project entity, which is the parent context for audit results, findings, and sign-off records. Sign-off status in the ETRM audit model is normally tracked on child audit entities rather than on the project header itself, so AMW_AUDIT_PROJECTS_VL is usually joined to those child objects rather than queried in isolation.

Underlying Base Objects

The documented ETRM metadata for this view does not enumerate specific referenced base tables. By naming convention and product design, AMW_AUDIT_PROJECTS_VL is defined over the audit projects base entity (typified by a _B or _TL table pair) in the AMW schema family, where the _B table holds language-independent columns and the _TL table holds translatable columns. This view exposes the language-resolved result. Columns such as AUDIT_PROJECT_ID, PROJECT_ID, and CREATED_FROM_PROJECT_ID are foreign keys pointing to the audit project, the Oracle Projects project, and any source template project respectively. Because the metadata lists no documented base objects, dependency analysis should be performed directly against the data dictionary (ALL_VIEWS / ALL_DEPENDENCIES) in the target environment.

Key Columns

• AUDIT_PROJECT_ID — Primary audit project identifier; the join key to audit sign-off, result, and finding entities.
• PROJECT_ID — Links the audit project to the associated Oracle Projects project record.
• PROJECT_NUMBER — User-facing project number (up to 25 characters).
• SCOPE_CHANGED_FLAG — Indicates whether the project scope has been modified since creation.
• TEMPLATE_FLAG — Distinguishes template audit projects from operative ones.
• CREATED_FROM_PROJECT_ID — The source project from which this record was derived or cloned.
• START_DATE and COMPLETION_DATE — Lifecycle dates for the audit project.
• PHASE — Current project phase (30 characters).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield structure and segment columns for client-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns.
• OBJECT_VERSION_NUMBER — Concurrency-control column used by the framework for row locking.
• SECURITY_GROUP_ID — Reserved for hosted/multi-tenant environments.

Common Use Cases and Queries

The view is most often queried to enumerate audit projects and their status context, then joined to sign-off and finding tables to report on closure progress. Typical pattern:

• Listing all active audit projects with their Oracle Projects linkage.
• Filtering template projects out of operational reporting via TEMPLATE_FLAG.
• Identifying projects whose scope was modified using SCOPE_CHANGED_FLAG.
• Driving sign-off status reports by joining to the audit sign-off child entity using AUDIT_PROJECT_ID.

Sample query:

• SELECT aap.audit_project_id, aap.project_number, aap.start_date, aap.completion_date, aap.phase, aap.scope_changed_flag
• FROM apps.amw_audit_projects_vl aap
• WHERE aap.template_flag = 'N'
• AND NVL(aap.completion_date, SYSDATE) >= SYSDATE - 90
• ORDER BY aap.start_date DESC;

To surface sign-off status, join to the audit sign-off object on AUDIT_PROJECT_ID. Confirm the sign-off table name in the environment, as the view metadata does not document this relationship directly.