Search Results amw_key_acc_interface_n1

Overview

AMW.AMW_KEY_ACC_INTERFACE is a transient interface table owned by the AMW (Applications Manager Workbench / Enterprise Transactional Reporting Management) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as the staging area for data uploaded through WebADI (Web Applications Desktop Integrator) for the "Process to Key Account Association" workflow. Rows are written to this table during an upload, validated and processed by a concurrent program, and subsequently consumed or cleared once the association between a process and its key accounts has been persisted to the base transaction tables.

The table resides in the APPS_TS_INTERFACE tablespace, which is characteristic of an interface/staging object rather than a permanent transactional entity. In Data Vault terms, the ETRM metadata classifies this object heuristically as standalone, with no mined foreign-key structure. For modeling purposes, this suggests the table functions as an interface or staging satellite — record-level upload data keyed by a technical surrogate rather than a resolved hub or link. It does not itself participate in referential integrity through enforced FK constraints; associations are resolved at processing time.

Key Information Stored

The table contains 31 documented columns. The most important are:

• KEY_ACC_INTERFACE_ID (NUMBER) — Table primary key and the column referenced by the search term key_acc_interface_id. Enforced through the unique index AMW_KEY_ACC_INTERFACE_U1 and the primary key constraint AMW_KEY_ACC_INTERFACE_PK. Because it is the sole unique index column, it is also the documented business-key candidate, though in practice it is a surrogate identifier assigned during the upload.
• BATCH_ID (NUMBER) — Groups all rows belonging to a single WebADI upload batch. Indexed by AMW_KEY_ACC_INTERFACE_N1 together with CREATED_BY, supporting batch retrieval and user-based filtering.
• PROCESS_ID (NUMBER) — Identifies the AMW process being associated with key accounts.
• FINANCIAL_STATEMENT_ID and FINANCIAL_ITEM_ID (NUMBER) — Identify the financial statement and financial item context for the association.
• NATURAL_ACCOUNT_ID and NATURAL_ACCOUNT_ACC_ID (NUMBER) — Reference the natural account and its associated account definition used as the key account in the upload.
• PROCESSED_FLAG, ERROR_FLAG, and INTERFACE_STATUS — Control columns that drive the interface processor. They indicate whether a row has been processed, whether validation failed, and the current lifecycle state of the record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2(150)) — Descriptive flexfield (DFF) columns, providing 15 open segments plus a structure-defining category column for client-specific extensions.
• Standard WHO columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide audit and ownership metadata on every row.

Common Use Cases and Queries

Typical usage centers on validating upload results, diagnosing failed WebADI loads, and confirming that a batch was fully processed before the data was promoted to the production key-account association tables.

• Reviewing a batch. Retrieve all rows in an upload by batch and user:
  SELECT key_acc_interface_id, process_id, financial_statement_id, financial_item_id, interface_status, processed_flag, error_flag FROM amw.amw_key_acc_interface WHERE batch_id = :p_batch_id ORDER BY key_acc_interface_id;
• Detecting errors. Isolate failed rows before reprocessing:
  SELECT batch_id, process_id, error_flag, interface_status FROM amw.amw_key_acc_interface WHERE error_flag = 'Y' AND processed_flag = 'N';
• Reading DFF content. Reporting on client-defined attribute segments as configured against the ATTRIBUTE_CATEGORY value.
• Audit and activity monitoring. Grouping by BATCH_ID and CREATED_BY (using index N1) to profile upload volume and users.

Because this is an interface table, direct inserts and updates should be avoided outside of the supported WebADI and concurrent processing flows.

Related Objects

The ETRM metadata documents no enforced foreign keys, and the mined relationship classification is standalone. The objects below are therefore implicated by naming, column semantics, and typical AMW processing flow rather than by documented constraints; the join predicates shown are the ones the ETRM profile supports.

• AMW.AMW_PROCESSES — the process master; joined on PROCESS_ID = PROCESS_ID.
• AMW financial statement and financial item masters — joined on FINANCIAL_STATEMENT_ID and FINANCIAL_ITEM_ID respectively.
• Natural account definition tables (GL natural account / account hierarchy objects) — joined on NATURAL_ACCOUNT_ID and NATURAL_ACCOUNT_ACC_ID.
• The WebADI upload definition for the Process-to-Key-Account association, which populates this interface table.
• The concurrent program that processes this interface, which reads rows in processed/error flag state and writes the resolved associations to the base key-account tables.
• Sibling interface table AMW.AMW_INTERFACE (or equivalent AMW staging object), where the same batch processing pattern applies.

All references should be confirmed against the actual AOL registration in the target instance, since interface tables in AMW are commonly customized and their downstream consumers vary by release and patch level.