Search Results engagement_type_id




Overview
Explore in AI Chat

Overview

APPS.AMW_PROJECT_LISTS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered in the application design layer as AMW.AMW_PROJECT_LISTS_V. It exposes a denormalized, read-oriented projection of audit project data maintained by the Oracle Audit Management (AMW) module and correlates that data with project records owned by Oracle Projects. Within EBS 12.1.1 and 12.2.2, the view functions as a reporting and integration surface: it flattens multilingual project names, status lookups, manager identities, and engagement classification attributes into a single row per audit project, sparing downstream consumers from reconstructing the joins themselves.

The view carries a prominent Oracle warning that it is for internal use only and is not supported for direct customer access except through standard Oracle Applications programs. This reflects a general EBS principle: seeded views may be restructured or dropped during patch application, and their column semantics are governed by the owning module rather than by a published interface contract. Nevertheless, the object is widely encountered in custom reports, extracts, and diagnostic queries where consumers accept the stability risk in exchange for convenience.

Underlying Base Objects

Per the ETRM dependency listing, AMW_PROJECT_LISTS_V is defined over the following objects:

No dependent database objects reference the view, confirming it is a terminal, leaf-level object in the dependency graph.

Key Columns

  • AUDIT_PROJECT_ID — primary identifier of the audit project; the view's unique key.
  • PA_PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, DESCRIPTION — the corresponding Oracle Projects identity and descriptive attributes.
  • PROJECT_STATUS_CODE / PROJECT_STATUS_NAME — the Projects status and its translated display name.
  • AUDIT_MANAGER_PERSON_ID / AUDIT_MANAGER_NAME — the engagement manager and resolved full name.
  • AUDIT_PROJECT_STATUS — the AMW-level lifecycle status, distinct from the Oracle Projects status.
  • START_DATE, COMPLETION_DATE — engagement scheduling dates.
  • TEMPLATE_FLAG, CREATED_FROM_PROJECT_ID, SOURCE_CODE — origin and template indicators for the audit project.
  • ENGAGEMENT_TYPE_ID — the classification of the audit engagement, derived from project type configuration. This is the column most frequently used to distinguish engagement categories in reporting and integrations.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit stamp columns.

Common Use Cases and Queries

The most common scenario is filtering audit projects by engagement classification, which is why "engagement_type_id" surfaces as a frequent search term:

  • Engagement-type reporting: SELECT PROJECT_NUMBER, PROJECT_NAME, AUDIT_MANAGER_NAME, ENGAGEMENT_TYPE_ID FROM APPS.AMW_PROJECT_LISTS_V WHERE ENGAGEMENT_TYPE_ID = :p_type AND TEMPLATE_FLAG = 'N';
  • Active engagement dashboard: filter on AUDIT_PROJECT_STATUS and COMPLETION_DATE to list in-flight audits.
  • Integration extracts: joining PA_PROJECT_ID back to PA_PROJECTS_ALL or cost/effort facts for reconciliation.

Because the view is unsupported for direct access, production integrations should generally replicate its logic against the documented base tables, using the view definition as a reference template.