Search Results ce_ba_signatory_hist_h




Overview
Explore in AI Chat

Overview

The CE_BA_SIGNATORY_HIST_H table is a Cash Management (CE) product table that stores the history information for bank account signatories in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides in the CE schema and is documented as VALID. The table captures the lifecycle of changes to a bank account's authorized signatory records — the individuals empowered to sign or approve transactions against a given bank account — so that prior configurations remain auditable after a signatory is added, modified, or end-dated.

From a heuristic, Data Vault-style modeling perspective, this object is satellite-leaning. It keys on a surrogate identifier and carries descriptive and audit attributes attached to a parent signatory entity rather than representing an independent business concept. Its structure — a primary key surrogate (SIGNATORY_HISTORY_ID) plus foreign key references back to a signatory — is characteristic of a satellite recording historical states of a parent hub or link.

Key Information Stored

The table is documented with 26 columns. The most significant are:

  • SIGNATORY_HISTORY_ID — the surrogate primary key, enforced by constraint CE_BA_SIGNATORY_HIST_H_PK and additionally backed by unique index CE_BA_SIGNATORY_HIST_H_U1. This is the technical identifier for each history row.
  • SIGNATORY_ID — the foreign key linking each history row back to its parent signatory record. This is the principal business-key candidate used to correlate history to the current signatory.
  • APPROVER_PERSON_ID — the person identifier associated with the approval action, resolving to the HR party/person model.
  • ACTION — the type of change recorded (for example, creation, update, or end-date), indicating what happened to the signatory.
  • CURRENT_RECORD_FLAG — marks whether the row represents the currently effective signatory state, enabling point-in-time versus as-is reporting.
  • CREATED_BY, CREATION_DATE — who created the history row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns tracking the most recent modification and session.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, providing extensible, customer-defined context.

Because the table carries both a single-column primary key and a unique index on the same column, it is not a composite business key; the true business correlation relies on SIGNATORY_ID together with the date/flag attributes.

Common Use Cases and Queries

Typical scenarios include historical audit reporting, signatory change tracking, and reconciliation of current versus prior signatory assignments.

  • Retrieve the current effective signatory rows: 
    SELECT SIGNATORY_HISTORY_ID, SIGNATORY_ID, APPROVER_PERSON_ID, ACTION
FROM   CE.CE_BA_SIGNATORY_HIST_H
WHERE  CURRENT_RECORD_FLAG = 'Y';
  • Trace the full change history for a specific signatory: 
    SELECT SIGNATORY_HISTORY_ID, ACTION, CREATION_DATE, LAST_UPDATE_DATE
FROM   CE.CE_BA_SIGNATORY_HIST_H
WHERE  SIGNATORY_ID = :p_signatory_id
ORDER BY CREATION_DATE;
  • Audit who made changes and when, filtered by the audit columns (CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE).
  • Report on approvers using APPROVER_PERSON_ID joined to HR person tables.
  • Expose DFF context via ATTRIBUTE_CATEGORY and the ATTRIBUTE1–ATTRIBUTE15 segments for customer-specific reporting.

Related Objects

The principal relationships documented for this table are:

  • CE_BA_SIGNATORY_HIST_H (self-referencing) — the documented foreign key maps CE_BA_SIGNATORY_HIST_H.SIGNATORY_ID back into the signatory model, tying each history row to its parent entity.
  • Primary key constraint CE_BA_SIGNATORY_HIST_H_PK on SIGNATORY_HISTORY_ID — the integrity anchor for this table.
  • Unique index CE_BA_SIGNATORY_HIST_H_U1 on SIGNATORY_HISTORY_ID — reinforces uniqueness of the surrogate key.

In practice, the signatory history is consumed alongside the current bank account signatory definition in the CE module and the HR person model referenced through APPROVER_PERSON_ID, supporting audit trails and Cash Management bank account configuration reporting.