Search Results ap_step_id

Overview

AMW_AP_STEPS_TL is the translation table for Audit Steps within the Oracle E-Business Suite Internal Controls Manager (ICM) module, identified by the product code AMW. It stores the language-dependent NAME and DESCRIPTION attributes for each audit step defined in the base AMW_AP_STEPS_B table. The "_TL" suffix follows the standard Oracle EBS multilingual convention, where the base ("_B") table holds language-independent columns and the translation table holds one row per installed language.

The ETRM metadata records that this object is obsolete and is not implemented in the reference database. Its presence in the data dictionary reflects the historical footprint of the ICM application, which was deprecated in favor of the GRC (Governance, Risk, and Compliance) product family. In Oracle EBS 12.1.1 and 12.2.2, AMW objects may still exist in upgraded instances, but they are inactive and generally void of data.

From a Data Vault modeling perspective (heuristic classification), this object is a satellite. It carries descriptive, language-scoped attributes (name and description) attached to the audit step hub identified by AP_STEP_ID, with LANGUAGE acting as a qualifier that produces multiple descriptive rows per hub key. The standalone classification reflects that the table participates only through its owning entity rather than bridging two independent business keys.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• AP_STEP_ID — The surrogate primary key component identifying the audit step. It is a foreign-key-linked identifier to the base audit step entity and, combined with LANGUAGE, forms the composite primary key AMW_AP_STEPS_TL_PK.
• LANGUAGE — The language code (for example, US for American English) qualifying the translation row. This is the second component of the composite primary key.
• NAME — The language-specific display name of the audit step. This is the primary business attribute surfaced to users in forms and reports.
• DESCRIPTION — The language-specific narrative description of the audit step, used in documentation and review workflows.
• SOURCE_LANGUAGE and SOURCE_LANG — Track the language of the source row from which a translation was derived, supporting the Oracle translation lifecycle. Note that both variants appear in the documented schema, which is common in legacy EBS translation tables.
• SECURITY_GROUP_ID — A foreign key referencing FND_SECURITY_GROUPS, enforcing data security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified each translation row, and when.

The unique index AMW_AP_STEP_TL_U1 on (AP_STEP_ID, LANGUAGE) is the business-key candidate, identical in composition to the primary key and guaranteeing one translation per step per language.

Common Use Cases and Queries

In active ICM implementations, the primary use case is joining the translation table to the base table to retrieve a step's name and description in the session's language. A representative pattern follows:

• Retrieve step details in a specific language:

  SELECT b.ap_step_id,
         t.name,
         t.description
  FROM   amw_ap_steps_b b,
         amw_ap_steps_tl t
  WHERE  b.ap_step_id = t.ap_step_id
  AND    t.language = USERENV('LANG');
  

• Identify steps missing translations for a required language by comparing against FND_LANGUAGES.
• Audit translation completeness across languages by grouping on LANGUAGE and counting rows per AP_STEP_ID.
• Extract bilingual listings for regulatory reporting where step names must be presented in the operating language.

Because the table is documented as not implemented, these queries are chiefly relevant during migration, archiving, or forensic analysis of legacy ICM data before or after upgrading to GRC.

Related Objects

• AMW_AP_STEPS_B — The base table holding language-independent audit step columns; joined on AP_STEP_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, providing the security partitioning context.
• FND_LANGUAGES — Provides valid values for LANGUAGE and SOURCE_LANGUAGE.
• FND_APPLICATION — Maps the AMW product code to the ICM application registration.
• ICM audit procedure and audit plan entities that consume audit steps through AP_STEP_ID.
• Oracle GRC successor tables, which superseded the AMW schema during the ICM-to-GRC transition.