Results for “amw_ap_steps_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMW_AP_STEPS_VL is a bilingual (translated) reporting view within the Oracle E-Business Suite module AMW — Internal Controls Manager. The "_VL" suffix denotes a view that joins a base (non-translated) table to its translation table and filters the translation rows by the session language, thereby returning descriptive text in the user's language while exposing the full set of transactional and descriptive columns of the underlying entity. In this case, the view presents information about the audit steps that are associated with audit procedures. Audit steps represent the discrete, ordered activities executed to satisfy an audit procedure; the view therefore serves as the canonical read-only source for step sequences, sample sizes, revision ranges, and the multilingual name and description of each step.

As documented in the ETRM metadata for release 12.2.2 (and applicable to 12.1.1), the object is listed under the AMW product with the notation that the product is obsolete and that the view is not implemented in this database. The absence of referenced base objects and an owner entry in the documented metadata reinforces that AMW is a retired module. Consequently, AMW_AP_STEPS_VL should be treated as a legacy metadata artifact rather than a view guaranteed to be present in a given 12.1.1 or 12.2.2 instance. Where AMW data is retained for historical reporting, the view provides a convenient, language-aware projection suitable for reports, extracts, and integration queries.

Underlying Base Objects

The view text resolves to two base objects: AMW_AP_STEPS_B (the base table holding transactional attributes) and AMW_AP_STEPS_TL (the translation table holding NAME and DESCRIPTION). The join predicate is B.AP_STEP_ID = TL.AP_STEP_ID, restricted by TL.LANGUAGE = USERENV('LANG'), which returns the translation row matching the language of the current database session. The SELECT list is composed of all principal columns from the _B table plus NAME and DESCRIPTION from the _TL table. Unlike many EBS _VL views, no separate AMW_AP_STEPS_VL entity is materialized; the documented ETRM metadata records no referenced base objects and no owner, reflecting the view's obsolete status.

Key Columns

• ROW_ID — the ROWID of the base table row; useful for ad hoc row identification.
• AUDIT_PROCEDURE_ID — foreign reference to the parent audit procedure to which the step belongs.
• AP_STEP_ID — primary identifier of the audit step and the join key to the translation table.
• SEQNUM / CSEQNUM — sequence values establishing the ordering of steps within a procedure.
• SAMPLESIZE — the sample size defined for the audit step's testing.
• FROM_REV_NUM / TO_REV_NUM — the revision range over which the step applies.
• NAME / DESCRIPTION — language-specific descriptive text sourced from AMW_AP_STEPS_TL.
• OBJECT_VERSION_NUMBER — optimistic locking/versioning column.
• SECURITY_GROUP_ID — the security grouping used for multi-tenant or organizational data partitioning.
• ORIG_SYSTEM_REFERENCE / REQUESTOR_ID — provenance and responsibility identifiers.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS auditing columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — flexfield-style descriptive attributes available for customer extensions.

Common Use Cases and Queries

The primary use case is the retrieval of ordered audit steps for a procedure in the user's session language. Typical reporting patterns include listing steps, review of sample sizes, and revision-based filtering.

Listing all steps for a given procedure in sequence:

SELECT ap_step_id, seqnum, name, description, samplesize
FROM   amw_ap_steps_vl
WHERE  audit_procedure_id = :p_procedure_id
ORDER  BY seqnum;

Extracting steps valid within a revision range:

SELECT ap_step_id, name, from_rev_num, to_rev_num
FROM   amw_ap_steps_vl
WHERE  audit_procedure_id = :p_procedure_id
AND    :p_rev_num BETWEEN from_rev_num AND to_rev_num;

Because AMW is obsolete, any remaining rows are usually accessed for historical or migration reporting. Confirm the object's existence and its base tables in the target instance before deploying queries dependent on it.