Search Results amw_prcdr_apprv_status
Overview
APPS.AMW_EXPORT_AP_V is a reporting and integration view within the Oracle E-Business Suite Audit Management module (AMW). It presents audit procedure definitions together with their revision, approval, step, and control-association details in a denormalized, export-oriented format. The view is designed to feed downstream reporting tools, extract processes, and interfaces that require a consolidated picture of approved audit procedures rather than the normalized transactional tables.
The user search term amw_prcdr_apprv_status corresponds directly to the lookup type referenced in the view definition. The view resolves the procedure approval status by decoding the APPROVAL_STATUS code against AMW_LOOKUPS where LOOKUP_TYPE='AMW_PRCDR_APPRV_STATUS', returning the human-readable meaning. This is central to the view's purpose: only procedures whose approval status is not Pending or Rejected are surfaced, ensuring the export represents actionable, approved content.
Underlying Base Objects
The view is defined over the following AMW base tables, joined in a single, distinct SELECT (with a UNION ALL branch in the full definition):
- AMW_AUDIT_PROCEDURES_B and AMW_AUDIT_PROCEDURES_TL — the audit procedure header and its translated name/description.
- AMW_AP_STEPS_B and AMW_AP_STEPS_TL — procedure steps and their translated descriptions.
- AMW_AP_ASSOCIATIONS — links procedures to associated objects such as controls.
- AMW_CONTROLS_B and AMW_CONTROLS_TL — control definitions and translated names.
- AMW_LOOKUPS — value set supplying the approval status meaning.
- AMW_OBJ_CLASSIFICATION_V — supplies the classification (work type) name for the procedure.
The ETRM metadata documents no referenced base objects for this view, so the join relationships above are derived from the view text itself. Notably, the language columns are constrained using USERENV('LANG'), and the step relationship is a revision-range join (audit_procedure_rev_num >= from_rev_num and < NVL(to_rev_num, rev_num+1)), which makes the view revision-aware.
Key Columns
- APID / APRID / APRNM — audit procedure ID, revision ID, and revision number.
- APAPP — approval status meaning resolved via the
AMW_PRCDR_APPRV_STATUSlookup. - APCAF / APLRF — current approved flag and latest revision flag; only the latest revision (
LATEST_REVISION_FLAG='Y') is returned. - APEND / APAPDT — procedure end date and approval date.
- APNM / APDS — translated procedure name and description.
- CNM / ADE / AOE — control name and design/operational effectiveness indicators.
- STPNM / STPNUM / STDSC / STSS — step name, sequence number, description, and sample size.
- APCLASS — classification work type name for the procedure.
- party_id — a constant
-100, used as a placeholder for export/party context.
Common Use Cases and Queries
Typical uses include extracting the approved audit procedure catalog, auditing control-to-procedure coverage, and driving step-level test reporting. A representative query:
SELECT APID, APRNM, APNM, APAPP, CNM, STPNM FROM APPS.AMW_EXPORT_AP_V WHERE APAPP = 'Approved';SELECT APID, APCLASS, COUNT(STPNUM) FROM APPS.AMW_EXPORT_AP_V GROUP BY APID, APCLASS;
Because the view filters out Pending and Rejected statuses and restricts results to the latest revision with current approvals, it is well suited to reconciliation and downstream integration where only effective, approved audit procedures should appear.
-
Lookup Type: AMW_PRCDR_APPRV_STATUS
12.1.1
product: AMW - Internal Controls Manager , meaning: AMW Procedure Approval Status ,
-
Lookup Type: AMW_PRCDR_APPRV_STATUS
12.2.2
product: AMW - Internal Controls Manager (Obsolete) , meaning: AMW Procedure Approval Status ,
-
VIEW: APPS.AMW_EXPORT_AP_V
12.1.1
-
View: AMW_EXPORT_AP_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AMW.AMW_EXPORT_AP_V, object_name:AMW_EXPORT_AP_V, status:VALID, product: AMW - Internal Controls Manager , implementation_dba_data: APPS.AMW_EXPORT_AP_V ,
-
View: AMW_EXPORT_AP_V
12.2.2
product: AMW - Internal Controls Manager (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 FND Design Data
12.2.2