Search Results fin_stmt_cert_id

Overview

AMW.AMW_FIN_PROC_CERT_RELAN is a relational intersection table within the Oracle E-Business Suite Application Management Workspace (AMW) schema. It captures the association between financial statement certifications and the individual process certifications that substantiate them. In practice, each financial statement certification may be supported by one or more process certifications, and this table records that many-to-many linkage. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and it is marked VALID in the ETRM repository for both 12.1.1 and 12.2.2.

From a modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. Because the table stores the intersection of two certification entities and carries its own surrogate identifier, it can reasonably be treated as a link-style construct joining a financial statement certification to a process certification. Standard Who columns and an OBJECT_VERSION_NUMBER column are present, consistent with an OAF-managed entity in Oracle EBS.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• FIN_PROC_CERT_ID — NUMBER. The entity identifier for this relationship record, and the column targeted by the unique index AMW_FIN_PROC_CERT_RELAN_U1. This column is the term the user searched for and serves as the surrogate primary key for the relation row.
• FIN_STMT_CERT_ID — NUMBER. Identifies the financial statement certification being supported.
• PROC_CERT_ID — NUMBER. Identifies the process certification contributing to the statement certification.
• END_DATE — DATE. The end date for the business certification relation, allowing the association to be terminated without physical deletion.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns recording audit authorship and timestamps.
• SECURITY_GROUP_ID — NUMBER. Standard column used for row-level security group partitioning; the documented FK links this column to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — NUMBER. Standard column used for optimistic locking by the OAF framework.

The second unique index, AMW_FIN_PROC_CERT_RELAN_U2, spans FIN_STMT_CERT_ID and PROC_CERT_ID, confirming that the pairing of a statement certification and a process certification must be unique. Both unique indexes reside in the APPS_TS_TX_IDX tablespace.

Common Use Cases and Queries

Typical usage centers on certification reporting and completeness checks for financial and process compliance cycles. A common pattern resolves all process certifications supporting a given financial statement certification:

• SELECT FIN_PROC_CERT_ID, FIN_STMT_CERT_ID, PROC_CERT_ID FROM AMW.AMW_FIN_PROC_CERT_RELAN WHERE FIN_STMT_CERT_ID = :stmt_cert_id AND (END_DATE IS NULL OR END_DATE > SYSDATE);
• Joining to financial statement and process certification header tables on FIN_STMT_CERT_ID and PROC_CERT_ID respectively to produce a certification hierarchy report.
• Auditing active versus expired relations using END_DATE to determine which process certifications still support a statement certification.
• Validating data integrity by confirming each (FIN_STMT_CERT_ID, PROC_CERT_ID) pair appears only once, per the U2 unique index.

Because the table carries Who columns and OBJECT_VERSION_NUMBER, most runtime maintenance occurs through the AMW OAF application rather than direct DML, but direct SQL is appropriate for read-only reporting and reconciliation.

Related Objects

The documented dependency information indicates that AMW_FIN_PROC_CERT_RELAN does not reference any database object through declared foreign keys other than the SECURITY_GROUP_ID link to FND_SECURITY_GROUPS. It is referenced by the APPS synonym AMW_FIN_PROC_CERT_RELAN, which is the standard EBS pattern allowing application code to query the table without schema qualification. In practice, reporting joins this table to the financial statement certification and process certification entities identified by FIN_STMT_CERT_ID and PROC_CERT_ID, along with FND_SECURITY_GROUPS for security-group resolution. Analysts should treat the two unique indexes as the authoritative business-key constraints when designing reconciliation queries.