Search Results ap_attribute15

Overview

AMW.AMW_AP_INTERFACE is a VALID interface table owned by the AMW (Audit Management Workbench) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Audit Procedure upload data originating from WebADI (Web Applications Desktop Integrator). Rows represent staged Audit Procedure header and step information that is validated and processed into the application's base audit procedure tables. The table resides in the APPS_TS_INTERFACE tablespace with PCT_FREE 10, and is registered in FND Design Data as AMW.AMW_AP_INTERFACE.

Because the table holds staged, transient data awaiting validation and processing, and because no foreign keys exist from this table outward, the heuristic Data Vault classification is standalone. As a modeling suggestion, it is best treated as an interface staging construct rather than a true hub, link, or satellite; its greatest affinity is toward a satellite-style record capturing description and WHO audit attributes, but the dominant purpose is inbound data loading, not enterprise data warehousing.

Key Information Stored

The documented metadata lists 40 columns. The most significant are:

• AP_INTERFACE_ID (NUMBER) — the table primary key and the column backing the unique index AMW_AP_INTERFACE_U1, the business-key candidate.
• BATCH_ID (NUMBER) — groups rows into a single upload batch; indexed non-uniquely via AMW_AP_INTERFACE_N1 (BATCH_ID, CREATED_BY).
• AP_NAME (VARCHAR2 240) — Audit Procedure Name.
• AP_DESCRIPTION (VARCHAR2 4000) — Audit Procedure Description.
• AP_APPROVAL_STATUS_CODE (VARCHAR2 30) — approval status lookup code for the procedure.
• AP_END_DATE (DATE) — Audit Procedure end date.
• REVISE_AP_FLAG — indicates whether an existing Audit Procedure is being revised or updated.
• CONTROL_NAME (NUMBER) — the associated control selected from an LoV.
• AP_STEP_NAME (VARCHAR2 240) and AP_STEP_DESCRIPTION (VARCHAR2 4000) — step-level detail.
• AP_STEP_SAMPLESIZE (NUMBER) — sample size for the step.
• AP_STEP_SEQNUM (NUMBER) — Audit Procedure step sequence number, the column referenced in the user's search; a second column, AP_STEP_SEQNUM2, also exists.
• ERROR_FLAG, INTERFACE_STATUS (VARCHAR2 2000), and PROCESS_FLAG — row-level processing and error indicators.

Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and a descriptive flexfield block (AP_ATTRIBUTE_CATEGORY plus AP_ATTRIBUTE1 through AP_ATTRIBUTE15) complete the row. Additional descriptive columns include DESIGN_EFFECTIVENESS, OP_EFFECTIVENESS, and CLASSIFICATION.

Common Use Cases and Queries

Primary usage is monitoring and troubleshooting WebADI uploads. Operators inspect batches for failures before or after concurrent processing validation:

• List unprocessed rows: SELECT AP_INTERFACE_ID, AP_NAME, AP_STEP_SEQNUM, INTERFACE_STATUS FROM AMW.AMW_AP_INTERFACE WHERE PROCESS_FLAG IS NULL;
• Find errored rows: filter on ERROR_FLAG or INTERFACE_STATUS where values indicate rejection.
• Reconcile by batch: SELECT BATCH_ID, COUNT(*) FROM AMW.AMW_AP_INTERFACE GROUP BY BATCH_ID;
• Audit step ordering: order by AP_STEP_SEQNUM to confirm sequence integrity before upload.

Reporting use cases include tracking revise-versus-new loads via REVISE_AP_FLAG and verifying approval status distribution across uploads.

Related Objects

• AMW_AUDIT_PROCEDURE_INTERFACE — references this table via the FK column AP_INTERFACE_ID, carrying the step-level interface rows keyed to the header staged here.
• AMW_AP_INTERFACE_U1 — unique index on AP_INTERFACE_ID; the business-key candidate.
• AMW_AP_INTERFACE_N1 — non-unique index on (BATCH_ID, CREATED_BY) supporting batch lookups.
• The WebADI desktop integration uploader and the concurrent program that validates and promotes staged Audit Procedure data into the AMW base tables.
• FND lookup objects resolving AP_APPROVAL_STATUS_CODE and the AP_ATTRIBUTE_CATEGORY descriptive flexfield definition.