Search Results ce_bank_stmt_map_hdr_u1

Overview

The CE.CE_BANK_STMT_MAP_HDR table is a Cash Management (CE) configuration table that stores bank statement mapping information for the CE_STATEMENT_HEADERS_INT_ALL interface table. It is owned by the CE schema and registered in FND Design Data as CE.CE_BANK_STMT_MAP_HDR. The mapping rules held in this table are defined by users in the Bank Statement Mapping Setup window, and they drive the transformation of raw bank file data into the standardized column structure expected by the bank statement interface.

From a Data Vault modeling perspective, the documented FK structure suggests this object is satellite-leaning. Its primary relationship points outward to CE_BANK_STMT_INT_MAP via MAP_ID, indicating that CE_BANK_STMT_MAP_HDR functions as a descriptive satellite of an integration mapping parent rather than as an independent hub. Practitioners designing warehouse or staging models around this table should treat it accordingly.

Key Information Stored

The table is stored in the APPS_TS_TX_DATA tablespace (PCT Free 10) and contains 30 documented columns. The most significant are:

• MAP_HEADER_ID (NUMBER(15), mandatory) — the surrogate primary key, enforced by CE_BANK_STMT_MAP_HDR_PK and also covered by the unique index CE_BANK_STMT_MAP_HDR_U1 (MAP_HEADER_ID, ZD_EDITION_NAME).
• MAP_ID (NUMBER(15)) — the mapping rule identifier; foreign key to CE_BANK_STMT_INT_MAP.
• COLUMN_NAME (VARCHAR2(50)) — the target column name being populated.
• REC_ID_NO (VARCHAR2(30)) — the record identifier number used to locate the correct record within the bank file.
• POSITION (NUMBER) — the position of the data within the bank file record.
• FORMAT (VARCHAR2(150)) — the predefined format applied to the target data.
• INCLUDE_FORMAT_IND (VARCHAR2) — flag ('Y'/'N') indicating whether format conversion applies.
• CONCATENATE_FORMAT_FLAG — controls concatenation behavior during mapping.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield structure and segment columns for extensibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns.
• ZD_EDITION_NAME — the editioning column used for EBR-enabled schemas in 12.2.x.

Common Use Cases and Queries

Typical usage centers on troubleshooting and validating bank statement mapping configurations. Common queries include retrieving all mapping lines for a given rule, or identifying the positional/format definition applied to a specific target column:

• SELECT * FROM ce_bank_stmt_map_hdr WHERE map_id = :p_map_id ORDER BY position;
• SELECT column_name, rec_id_no, position, format, include_format_ind FROM ce_bank_stmt_map_hdr WHERE map_header_id = :p_id;
• Join to CE_BANK_STMT_INT_MAP to reconcile active mapping sets against loaded statement lines.

Reporting scenarios include auditing which mapping rules populate which interface columns, verifying flexfield attribute assignments in customizations, and confirming edition scoping (ZD_EDITION_NAME) in multi-edition deployments.

Related Objects

• CE.CE_BANK_STMT_INT_MAP — parent mapping definition; join on CE_BANK_STMT_MAP_HDR.MAP_ID = CE_BANK_STMT_INT_MAP.MAP_ID.
• CE.CE_STATEMENT_HEADERS_INT_ALL — the interface table that consumes the mapping output defined here.
• CE_BANK_STMT_MAP_HDR_PK — primary key constraint on MAP_HEADER_ID.
• CE_BANK_STMT_MAP_HDR_U1 — unique index (MAP_HEADER_ID, ZD_EDITION_NAME), the business-key candidate.

Together these objects form the bank statement mapping and loading pipeline in Cash Management, with CE_BANK_STMT_MAP_HDR acting as the descriptive detail layer beneath the mapping header.