Results for “amw_fin_items_key_acc”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AMW_FIN_ITEMS_KEY_ACC table is a core configuration and mapping object within the Oracle Internal Controls Manager (ICM) module, owned by the AMW schema. Its documented purpose is to hold information on Key Accounts that are mapped to a Financial Item for reporting purposes in Oracle ICM. In practice, this table acts as the associative bridge that ties a natural account segment value to a financial statement line item, scoped by a statement group, account group, and financial statement. This allows ICM to aggregate underlying account balances into the financial statement reporting hierarchy used for certification, disclosure, and sign-off workflows.

The table is a standard EBS transactional configuration table rather than a transactional fact table. It carries the full complement of EBS "WHO" audit columns and a set of 15 generic ATTRIBUTE columns supporting descriptive flexfield (DFF) extensibility. The metadata classifies this object heuristically as standalone under a Data Vault lens; from a modeling perspective, it is best treated as a link entity that resolves a many-to-many relationship between key accounts and financial items, rather than a hub or satellite. This classification is a modeling suggestion derived from the foreign key structure, not a documented Oracle attribute.

Key Information Stored

The table is defined with 28 columns. The most significant are the composite key components and the mapping columns:

• STATEMENT_GROUP_ID – Identifier for the statement group that scopes the mapping.
• ACCOUNT_GROUP_ID – Identifier for the account group within the statement group.
• FINANCIAL_STATEMENT_ID – The financial statement to which the key account is reported.
• FINANCIAL_ITEM_ID – The financial item (line item) that the key account maps to for reporting.
• NATURAL_ACCOUNT_ID – The natural account segment value being mapped into the reporting hierarchy.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, controlling row-level access.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the EBS framework for concurrent update control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY – Standard EBS audit (WHO) columns.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 – Descriptive flexfield storage for client-specific extensions.

The surrogate primary key is AMW_FIN_ITEMS_KEY_ACC_PK, composed of (STATEMENT_GROUP_ID, ACCOUNT_GROUP_ID, FINANCIAL_STATEMENT_ID, FINANCIAL_ITEM_ID, NATURAL_ACCOUNT_ID). A unique index, AMW_FIN_ITEMS_KEY_ACC_U1, mirrors the same five columns and functions as the business-key candidate, ensuring no duplicate mapping of a natural account to a financial item within its group context.

Common Use Cases and Queries

Typical usage centers on resolving which financial statement items a given natural account rolls into, and validating that every required account is mapped. Reporting queries commonly join this table to financial statement and financial item metadata to produce mapping coverage reports used before certification cycles.

A representative pattern retrieves all financial items associated with a statement group:

• SELECT financial_item_id, natural_account_id FROM amw.amw_fin_items_key_acc WHERE statement_group_id = :p_group AND security_group_id = :p_sec;
• Join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to enforce access restrictions in custom reports.
• Group by FINANCIAL_ITEM_ID to count key accounts per financial item and detect under-mapped line items.

Related Objects

• FND_SECURITY_GROUPS – referenced via SECURITY_GROUP_ID; governs row-level security.
• The ICM financial statement, financial item, statement group, account group, and natural account definition tables referenced by the corresponding *_ID columns.
• ICM reporting and certification views that aggregate this mapping for sign-off.

Because the metadata classifies the object as standalone, dependent views and APIs are typically resolved through the AMW module rather than direct foreign keys; administrators should consult the ICM data model for the exact parent definition tables in their instance.