Results for “amw_fin_stmnt_b”

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

Overview

AMW_FIN_STMNT_B is a table within the Oracle Internal Controls Manager (ICM) module, delivered under the AMW product short name. Its documented purpose is to store the list of financial statements that have been imported into Oracle ICM. In the Oracle EBS 12.1.1 and 12.2.2 release streams, ICM forms part of the governance, risk, and compliance toolset used to manage financial reporting controls and certification cycles. The table therefore acts as the master registry of statement definitions consumed by downstream ICM logic, including statement line item assembly and the security-based access controls applied to financial reporting structures.

The ETRM documentation marks this object as "Not implemented in this database," meaning the object may be absent from a given environment depending on whether ICM has been licensed, installed, and configured there. The AMW module itself is flagged as obsolete in the metadata, so deployments should be validated against the module installation status before relying on the object.

From a dimensional modeling perspective, the mined relationship data classifies this table as hub-leaning. This is a heuristic suggestion rather than a delivered design: the table carries a composite business key and is referenced by a dependent child, which are characteristic traits of a hub entity in a Data Vault style model. Analysts building conformed reporting layers may treat it as such, while recognizing that Oracle's native schema is a conventional relational design rather than a formal Data Vault implementation.

Key Information Stored

The physical schema documents 26 columns. The most operationally significant are:

• STATEMENT_GROUP_ID and FINANCIAL_STATEMENT_ID — the two-part composite identifier that forms the business key. Both are also members of the primary key constraint AMW_FIN_STMNT_B_PK and of the unique index AMW_FIN_STMNT_B_U1. Because the unique index mirrors their combination, they are the sole documented business-key candidates; there is no separate surrogate column generated by a sequence.
• END_DATE — the effective or termination date associated with the statement record, typically used to determine the active period of a statement definition.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, which scopes the statement to a functional security group and drives row-level access filtering.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column used to detect concurrent update conflicts.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO columns capturing audit trail information for insertion and modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the flexfield-style descriptive attribute columns reserved for client-specific or localization extensions.

Common Use Cases and Queries

The principal application scenario is reporting and reconciliation of imported financial statements. A typical query joins the statement header to its line items through both key columns:

• List all statements with their line items: join AMW_FIN_STMNT_B to AMW_FIN_STMNT_ITEMS_B on STATEMENT_GROUP_ID and FINANCIAL_STATEMENT_ID.
• Security-scoped lookup: filter by SECURITY_GROUP_ID to restrict results to the security groups visible to the current responsibility.
• Active statement selection: constrain by END_DATE to isolate statements still in effect.
• Change auditing: use the WHO columns to identify statements modified since a given date, or to generate an audit trail of who imported the statement.
• Migration and validation extracts: select the business key along with ATTRIBUTE_CATEGORY to verify that descriptive flexfield data was populated during import.

Because the module is obsolete, extraction logic built against this table should be treated as legacy and validated carefully during upgrades or when migrating compliance data to successor applications.

Related Objects

The FK metadata identifies a small dependency cluster around this object:

• AMW_FIN_STMNT_ITEMS_B — the most significant dependent table. It references this table through STATEMENT_GROUP_ID and FINANCIAL_STATEMENT_ID, holding the individual line items that compose each financial statement.
• FND_SECURITY_GROUPS — referenced by AMW_FIN_STMNT_B.SECURITY_GROUP_ID, supplying the security group definitions that govern visibility of the statement.
• AMW_FIN_STMNT_B_PK and AMW_FIN_STMNT_B_U1 — the primary key and unique index that enforce uniqueness of the composite business key and underpin all joins to child tables.

No additional views, PL/SQL APIs, or concurrent programs are documented in the supplied metadata; consumers should verify against the ICM data dictionary in the target environment before building interfaces.