Search Results ce_bank_stmt_map_line




Overview
Explore in AI Chat

Overview

CE_BANK_STMT_MAP_LINE is a Cash Management (CE) schema table in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that stores the individual mapping definitions used to translate a bank's proprietary statement file layout into Oracle's standard bank statement interface format. Each row represents one source column or field of an inbound bank statement file and describes how that field should be interpreted, positioned, and formatted when loaded into the CE_BANK_STMT_INTERFACE staging structures. The parent table, CE_BANK_STMT_INT_MAP, holds the header-level definition for a named statement mapping, while CE_BANK_STMT_MAP_LINE holds the child-level detail required to parse each line of the incoming file.

The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. In modeling terms, this object behaves like a satellite attached to the CE_BANK_STMT_INT_MAP hub/link structure, since it enriches the parent mapping definition with descriptive attributes and is joined to its parent through MAP_ID. The table is considered a modeling suggestion only; the physical schema is a conventional relational child table.

Key Information Stored

The table contains 30 documented columns. The most business-relevant include:

  • MAP_LINE_ID — Surrogate primary key, uniquely identifying each mapping line. Enforced by the CE_BANK_STMT_MAP_LINE_PK constraint.
  • MAP_ID — Foreign key to CE_BANK_STMT_INT_MAP; ties each line to its parent mapping definition.
  • COLUMN_NAME — Name of the target interface column (for example, the destination field in the bank statement interface).
  • REC_ID_NO — Record identifier number used to distinguish record types within the parsed file.
  • POSITION — Ordinal position or offset of the field within the source record, driving positional parsing logic.
  • FORMAT — Format mask applied when interpreting the source field.
  • INCLUDE_FORMAT_IND — Indicator controlling whether the format specification is applied during parsing.
  • CONCATENATE_FORMAT_FLAG — Flag governing concatenation behavior for composite fields.
  • ZD_EDITION_NAME — Editioning column introduced under Edition-Based Redefinition in 12.2; combined with MAP_LINE_ID it forms the unique index CE_BANK_STMT_MAP_LINE_U1.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns provided for extensibility.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle WHO audit columns.

The business-key candidate is the unique index CE_BANK_STMT_MAP_LINE_U1, spanning MAP_LINE_ID and ZD_EDITION_NAME. MAP_LINE_ID serves as the surrogate identity, while MAP_ID provides the parent linkage.

Common Use Cases and Queries

Typical uses include auditing how incoming bank statement formats are configured, verifying that each parent mapping has complete field definitions, and generating reports of mapping coverage before file loading. Administrators frequently query this table when troubleshooting failed statement loads, since an incorrect POSITION or FORMAT value causes parsing errors. A common retrieval pattern below lists all mapping lines for a given parent:

  • SELECT MAP_LINE_ID, COLUMN_NAME, POSITION, FORMAT FROM CE_BANK_STMT_MAP_LINE WHERE MAP_ID = :map_id ORDER BY POSITION;
  • Joining to the parent: SELECT m.MAP_NAME, l.COLUMN_NAME, l.POSITION FROM CE_BANK_STMT_INT_MAP m, CE_BANK_STMT_MAP_LINE l WHERE m.MAP_ID = l.MAP_ID;
  • Duplicate-position validation: group by MAP_ID and POSITION to detect overlapping or missing field offsets.

Related Objects

The principal related object is the parent CE_BANK_STMT_INT_MAP, joined through CE_BANK_STMT_MAP_LINE.MAP_ID. Coverage and control consistencies are maintained via the CE_BANK_STMT_MAP_LINE_PK and CE_BANK_STMT_MAP_LINE_U1 indexes. Related Cash Management objects encountered alongside this table include the bank statement interface tables and mapping views used by the Bank Statement Reconciliation and Cash Management statement load programs. The standard WHO audit columns also relate logically to FND_USER via CREATED_BY and LAST_UPDATED_BY.