Search Results amw_control_ap_u1

Overview

AMW.AMW_CONTROL_AP is a table in the Oracle E-Business Suite Application Management (AMW) schema. In the context of Oracle EBS 12.1.1 and 12.2.2, the AMW schema historically supported application monitoring and control utilities — including features associated with Application Management Pack, Auditor, and related control/audit framework components. AMW_CONTROL_AP serves as a control association table that records relationships between control definitions (CONTROL_ID) and audit procedures (AUDIT_PROCEDURE_ID), along with descriptive flexfield segments and standard WHO/audit columns.

The ETRM metadata classifies this object as standalone under the heuristic Data Vault model, meaning no foreign-key dependencies were mined from the physical schema. From a modeling standpoint, this suggests AMW_CONTROL_AP could be treated as a satellite-like holding table rather than a true hub or link, since the documented relationship data reveals no enforced FK constraints linking it to other objects. The table is documented as VALID and carries 26 columns, with all columns explicitly annotated "No Longer Used" except the two descriptive flexfield segments ATTRIBUTE1 and ATTRIBUTE2, and the CONTROL_AP_ID itself. This annotation strongly implies the table exists primarily for backward compatibility with earlier releases of the AMW control framework.

Key Information Stored

The table is organized around a single surrogate primary key and a unique business-key index:

• CONTROL_AP_ID (NUMBER) — Surrogate primary key, enforced by AMW_CONTROL_AP_PK and also indexed by the unique index AMW_CONTROL_AP_U1 in the APPS_TS_TX_IDX tablespace. This is the column most frequently referenced in searches such as "amw_control_ap_u1".
• CONTROL_ID (NUMBER) — Reference to the parent control definition; documented but flagged as no longer used.
• AUDIT_PROCEDURE_ID (NUMBER) — Reference to an associated audit procedure; also flagged as no longer used.
• ATTRIBUTE1, ATTRIBUTE2 (VARCHAR2(150)) — Descriptive flexfield (DFF) segments; these remain active in the documented schema and are the primary extensibility points.
• ATTRIBUTE_CATEGORY (VARCHAR2(30)) — DFF context/context-value discriminator, flagged as no longer used.
• ATTRIBUTE3 through ATTRIBUTE15 (VARCHAR2(150)) — Additional DFF placeholders, all flagged "No Longer Used".
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO columns for auditing row changes; no longer actively populated.
• SECURITY_GROUP_ID (NUMBER) — Multi-org/security grouping discriminator, flagged as no longer used.
• OBJECT_VERSION_NUMBER (NUMBER) — Optimistic locking column, flagged as no longer used.

The metadata does not attribute business meaning to CONTROL_ID or AUDIT_PROCEDURE_ID beyond their names, so any joins to control or audit-procedure master tables should be validated against the actual runtime schema rather than assumed from the physical documentation.

Common Use Cases and Queries

Because every legacy column is annotated "No Longer Used," the primary practical value of AMW_CONTROL_AP is (a) schema compatibility for upgrades, and (b) DFF-based extension of the control association model through ATTRIBUTE1 and ATTRIBUTE2. Typical queries include:

• Looking up an association row by its unique key: SELECT * FROM AMW.AMW_CONTROL_AP WHERE CONTROL_AP_ID = :id;
• Querying by DFF context: SELECT CONTROL_AP_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2 FROM AMW.AMW_CONTROL_AP WHERE ATTRIBUTE_CATEGORY = :ctx;
• Diagnostic scans during upgrade or patching, verifying the unique index AMW_CONTROL_AP_U1 is intact: SELECT index_name, uniqueness, tablespace_name FROM all_indexes WHERE table_name = 'AMW_CONTROL_AP';

Reporting against this table is generally limited to audit-trail or lineage exercises rather than functional business reporting, since the transactional content is deprecated.

Related Objects

The supplied metadata classifies AMW_CONTROL_AP as standalone with no mined foreign keys, so dependencies are inferred by naming conventions rather than enforced constraints. Relevant objects typically include:

• AMW_CONTROL_AP_PK — Primary-key constraint on CONTROL_AP_ID.
• AMW_CONTROL_AP_U1 — Unique index on CONTROL_AP_ID in APPS_TS_TX_IDX; the object most often referenced in the user's search term.
• AMW_CONTROL — Presumed master control table, joined via CONTROL_ID.
• AMW_AUDIT_PROCEDURES — Presumed audit-procedure master, joined via AUDIT_PROCEDURE_ID.
• FND Descriptive Flexfield definitions — Registered against AMW_CONTROL_AP for ATTRIBUTE1/ATTRIBUTE2 context handling.
• FND_APPLICATION / FND_TABLES — Metadata registrations that describe AMW_CONTROL_AP within the applications data dictionary.

Because none of these joins are documented as enforced FKs, implementers should confirm actual relationships in the target environment before relying on them for integration or reporting logic.