Search Results audit_project_status

Overview

AMW_AUDIT_PROJECTS_VL is a multilingual (VL) view owned by the APPS schema within the Oracle E-Business Suite Internal Controls Manager (AMW) product. It presents audit project header information by joining the audit project base table to its translation table, resolving the descriptive attributes NAME and DESCRIPTION into the session's runtime language. Audit projects in AMW represent the controlled engagements through which an organization records, tracks, and signs off on internal control and compliance activities, so this view acts as the primary read interface for audit project data used by AMW forms, concurrent programs, and reporting layers.

The VL suffix indicates that the view is language-aware: it filters the translation table on TL.LANGUAGE = USERENV('LANG') so that consumers see only the localized name and description matching their current language setting. Because the view consolidates transactional header columns with translated descriptive columns, it is the preferred object for reporting and integration interfaces, removing the need for callers to write their own join to the _TL table.

Underlying Base Objects

The view is defined over two underlying objects:

• AMW_AUDIT_PROJECTS — the base table holding transactional audit project data such as identifiers, dates, flags, DFF attributes, the audit manager, and status columns.
• AMW_AUDIT_PROJECTS_TL — the translation table holding the language-specific NAME and DESCRIPTION, keyed by AUDIT_PROJECT_ID and LANGUAGE.

The defining SQL selects all base-table columns from AMW_AUDIT_PROJECTS (aliased B) and joins to AMW_AUDIT_PROJECTS_TL (aliased TL) on B.AUDIT_PROJECT_ID = TL.AUDIT_PROJECT_ID, with the language predicate TL.LANGUAGE = USERENV('LANG'). The join is effectively one-to-one within a language. No additional base objects are documented in the ETRM metadata for this view.

Key Columns

• AUDIT_PROJECT_ID — primary key of the audit project; the join key between the base and translation tables.
• PROJECT_ID — reference to the associated Oracle Projects project, linking the audit engagement to project accounting.
• CREATED_FROM_PROJECT_ID — the source project from which this audit project was generated, supporting audit project creation by copy or template instantiation.
• TEMPLATE_FLAG — indicates whether the record functions as a reusable template rather than an active audit project.
• PROJECT_NUMBER, START_DATE, COMPLETION_DATE — identification and lifecycle dates for the engagement.
• PHASE, ENGAGEMENT_TYPE_ID — the audit phase and the engagement type classifying the project.
• AUDIT_MANAGER_PERSON_ID — the person designated as audit manager.
• AUDIT_PROJECT_STATUS, SIGN_OFF_STATUS, SIGN_OFF_REQUIRED_FLAG, SCOPE_CHANGED_FLAG — control and workflow state indicators.
• NAME, DESCRIPTION — language-resolved descriptive attributes from the translation table.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments.
• OBJECT_VERSION_NUMBER, SECURITY_GROUP_ID — concurrency control and multi-organization security columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried for audit project listings, status dashboards, and integration extracts. A representative query retrieving projects created from a specific source project is:

SELECT audit_project_id, project_number, name, project_id, start_date, audit_project_status
FROM   apps.amw_audit_projects_vl
WHERE  created_from_project_id = :p_source_project_id
  AND  template_flag = 'N';

Other frequent patterns include listing active engagements by status, joining PROJECT_ID to Oracle Projects tables for financial reconciliation, filtering on ENGAGEMENT_TYPE_ID for type-specific reporting, and consuming NAME/DESCRIPTION directly in reports where no manual translation join is desired. Because the language predicate is embedded, no additional LANGUAGE filter is required by the caller.