Search Results control_ap_id




Overview
Explore in AI Chat

Overview

The AMW_CONTROL_AP table resides in the AMW schema, which is owned by the Oracle Internal Controls Manager (ICM) product family. In Oracle E-Business Suite 12.1.1 and 12.2.2, the AMW schema was created to support audit, compliance, and internal control management functionality, including the definition of controls, audit procedures, and their associations. The table AMW_CONTROL_AP is documented in the ETRM metadata as "No longer in use," indicating that it is a legacy or deprecated object retained in the schema for backward compatibility, historical data preservation, or upgrade purposes, but no longer actively written to or referenced by current application logic.

From a heuristic Data Vault modeling perspective, the table is classified as standalone, meaning it does not participate in foreign-key relationships within the documented schema. This suggests it functions conceptually as a hub-like or reference entity keyed by a single surrogate identifier, rather than as a link table or a descriptive satellite.

Key Information Stored

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

  • CONTROL_AP_ID — the surrogate primary key, defined by constraint AMW_CONTROL_AP_PK and reinforced by the unique index AMW_CONTROL_AP_U1. This column uniquely identifies each row.
  • CONTROL_ID — a reference to a control definition, presumably linking this record to a control record in a related control-master table.
  • AUDIT_PROCEDURE_ID — a reference to an audit procedure, suggesting this table captured associations between controls and audit procedures.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, used for extensible, client-specific attributes.
  • SECURITY_GROUP_ID — the multi-org/style security grouping identifier used across EBS for data partitioning.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework (OAF) and BC4J to manage concurrent updates.
  • Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard "Who" columns tracking row creation and modification.

The unique index AMW_CONTROL_AP_U1 on CONTROL_AP_ID confirms the surrogate key is also a business-key candidate, though no separate natural business key is documented.

Common Use Cases and Queries

Because the table is marked "No longer in use," production usage is primarily historical. Typical scenarios include:

  • Data migration and upgrade verification — confirming that legacy control-to-audit-procedure associations were migrated to successor tables during an EBS upgrade.
  • Historical reporting — extracting legacy associations for audit trails or compliance evidence predating the deprecation.
  • Archival and purging — identifying residual rows prior to schema cleanup.

A representative query to inspect residual records is:

SELECT control_ap_id, control_id, audit_procedure_id, creation_date
FROM amw.amw_control_ap
WHERE security_group_id = :sgid;

Reporting joins would typically key off CONTROL_ID and AUDIT_PROCEDURE_ID, though the standalone Data Vault classification implies no enforced FK relationships remain.

Related Objects

Given the standalone classification, no formal foreign keys are documented. Conceptually related objects in the AMW schema include:

  • Control master table — joined via CONTROL_ID, holding control definitions.
  • Audit procedure table — joined via AUDIT_PROCEDURE_ID, holding procedure definitions.
  • AMW_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for data partitioning.
  • Successor association tables in current ICM releases that replaced AMW_CONTROL_AP.
  • FND_ATTACHED_DOCUMENTS and other standard EBS reference tables indirectly linked through flexfield attributes.

Developers should verify current equivalents against the active ICM data model before relying on this deprecated object.