Search Results ce_bank_stmt_map_hdr




Overview
Explore in AI Chat

Overview

CE_BANK_STMT_MAP_HDR is a Cash Management (CE) configuration table that stores bank statement mapping definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the header-level mapping rules used by the Bank Statement Reconciliation and Cash Management statement import processes to translate incoming bank statement data into the internal transaction and reconciliation structures of Oracle Cash Management. Each row represents a mapping header that governs how a specific bank statement interface layout is interpreted.

The table belongs to the CE schema and is implemented as a standard EBS transactional table with the usual WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus a set of descriptive flexfield columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15). Its documented primary key is CE_BANK_STMT_MAP_HDR_PK on MAP_HEADER_ID, and a unique business-key index, CE_BANK_STMT_MAP_HDR_U1, exists on (MAP_HEADER_ID, ZD_EDITION_NAME). From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning: the mapping header carries descriptive, context-dependent attributes that depend on the associated mapping definition, rather than acting as an independent business hub.

Key Information Stored

The columns that carry the substantive meaning of a mapping header are the following:

  • MAP_HEADER_ID — the surrogate primary key of the table and the value exposed by CE_BANK_STMT_MAP_HDR_PK. It uniquely identifies each mapping header record.
  • MAP_ID — the foreign key to CE_BANK_STMT_INT_MAP, linking the header to the statement interface mapping definition it belongs to.
  • COLUMN_NAME — the bank statement interface column being mapped.
  • REC_ID_NO — the record identifier associated with the mapped column, used to distinguish mapping entries across source records.
  • POSITION — the ordinal position of the mapped column within the statement layout.
  • FORMAT — the display or conversion format applied to the mapped value.
  • INCLUDE_FORMAT_IND — an indicator controlling whether the FORMAT value is applied.
  • CONCATENATE_FORMAT_FLAG — a flag governing whether formatted values are concatenated during mapping.
  • ATTRIBUTE_CATEGORY / ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments available for customer-specific extensions.
  • ZD_EDITION_NAME — the editioning column used by the EBS 12.2 Online Patching (ADOP) architecture; combined with MAP_HEADER_ID it forms the unique business-key index CE_BANK_STMT_MAP_HDR_U1.

The distinction between MAP_HEADER_ID and MAP_ID is important: MAP_HEADER_ID is the surrogate key of the header row itself, whereas MAP_ID is a foreign key referencing the broader mapping definition in CE_BANK_STMT_INT_MAP.

Common Use Cases and Queries

Typical use cases include verifying statement mapping configuration before running Bank Statement Interface imports, diagnosing reconciliation failures caused by incorrect mapping, and building reporting extracts of mapping definitions.

  • Retrieving all mapping headers for a given mapping definition:
    SELECT map_header_id, map_id, column_name, position FROM ce.ce_bank_stmt_map_hdr WHERE map_id = :p_map_id ORDER BY position;
  • Locating a header by its surrogate key:
    SELECT * FROM ce.ce_bank_stmt_map_hdr WHERE map_header_id = :p_header_id;
  • Retrieving mapping headers joined to their interface mapping definition:
    SELECT h.map_header_id, h.column_name, i.* FROM ce.ce_bank_stmt_map_hdr h JOIN ce.ce_bank_stmt_int_map i ON h.map_id = i.map_id;
  • Auditing recently modified mappings:
    SELECT map_header_id, last_updated_by, last_update_date FROM ce.ce_bank_stmt_map_hdr WHERE last_update_date > SYSDATE - 30;

Querying with ZD_EDITION_NAME in the predicate is advisable in 12.2.x patched environments to ensure the correct edition of the row is returned.

Related Objects

  • CE_BANK_STMT_INT_MAP — the parent mapping definition referenced by CE_BANK_STMT_MAP_HDR.MAP_ID; the central join to understanding mapping context.
  • CE_BANK_STMT_MAP_HDR_PK — the primary key constraint on MAP_HEADER_ID enforcing uniqueness of each mapping header.
  • CE_BANK_STMT_MAP_HDR_U1 — the unique index on (MAP_HEADER_ID, ZD_EDITION_NAME) supporting edition-aware access.
  • CE_BANK_STATEMENTS / CE_STATEMENT_HEADERS — statement records whose import relies on mapping headers for correct interpretation.
  • CE_BANK_STMT_INT_MAP-related interface tables in the CE schema that consume the mapping definitions during statement loading.

Because the documented FK metadata lists only MAP_ID → CE_BANK_STMT_INT_MAP, the above related objects should be treated as the primary documented dependencies, supplemented by the surrounding Cash Management statement-processing objects.