Search Results ce_bank_statement_loader




Overview
Explore in AI Chat

Overview

CE_BANK_STATEMENT_LOADER is an Oracle Applications (APPS) PL/SQL package that supports the bank statement import process in Oracle Cash Management. Its principal business function is to read externally supplied bank statement data — typically flat files, EDIFACT-formatted files, or staged records — and load that data into the Cash Management statement interface tables for subsequent validation, formatting, and transfer into the core statement tables. The package therefore sits at the front end of the bank reconciliation data pipeline, translating heterogeneous source formats into the canonical interface structures that Cash Management recognizes.

The package is registered in the ETRM repository with owner APPS and status VALID. It is classified as an API of type OTHER, indicating it is an internal processing package rather than a published public API intended for direct call by external integrators. In the ETRM dependency listing the package references APPS.CE_STATEMENT_LINES and the SYS.STANDARD schema, confirming that it ultimately writes statement line records and relies on standard PL/SQL constructs. It is referenced by no other packages, so its role is confined to the load stage rather than being reused by downstream logic.

Key Procedures and Functions

The documented interface of the package exposes six procedures and functions:

  • SPEC_REVISION — Returns the revision identifier of the package specification, providing version traceability for the API surface.
  • BODY_REVISION — Returns the revision identifier of the package body, allowing the implementation version to be queried independently of the specification.
  • LOAD_BANK_STATEMENT — The primary driver procedure. It orchestrates reading of the source statement data and populating the Cash Management statement interface tables, forming the core of the load operation.
  • FIND_FORMATTED_STRING — A helper used to locate and extract a formatted string within the incoming source record, supporting field-level parsing of variable-format statement files.
  • IS_NUMERIC — A validation utility that determines whether a given value is numeric, enabling the loader to identify and correctly interpret numeric fields such as amounts.
  • COVERT_AMT_EDIFACT — A conversion routine (the name reflects a documented spelling variant of "convert") that translates EDIFACT-encoded amount representations into standard numeric values recognized by Cash Management.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

  • CE_STATEMENT_LINES_INTERFACE — the principal staging area into which parsed statement lines are loaded.
  • CE_STATEMENT_HEADERS_INT — holds statement header information accompanying the lines.
  • CE_STMT_INT_TMP — a temporary working table used during the load and transformation steps.
  • CE_STATEMENT_LINES — the core statement lines table, the eventual destination referenced in the dependency information.
  • CE_BANK_ACCOUNTS — provides bank account context to associate statements with the correct internal account.
  • CE_BANK_STMT_MAP_HDR and CE_BANK_STMT_MAP_LINE — the bank statement mapping header and line definitions that dictate how source fields are mapped to interface columns.
  • CE_SQLLDR_ERRORS — captures errors arising from SQL*Loader-based ingestion of source files.
  • FND_CURRENCIES — used to validate and resolve currency codes on statement amounts.
  • DUAL — used for scalar evaluations and revision queries.

Usage Notes

CE_BANK_STATEMENT_LOADER is invoked as part of the standard Cash Management bank statement import flow, typically driven by the Bank Statement Import concurrent program rather than called directly from a form. Because it is classified as OTHER and referenced by no other packages, it should be treated as an internal component; customizations should not depend on its signature across releases. The presence of EDIFACT conversion and formatted-string parsing logic indicates that the package supports the bank statement mapping feature, in which a flexible mapping definition translates customer-specific file layouts into interface records. The revision functions support version checking during diagnostics, and the SQL*Loader error table reference confirms that file-based ingestion errors are surfaced for review. Any invocation should ensure that mapping definitions and bank account records exist before loading, since the package consults CE_BANK_STMT_MAP_HDR, CE_BANK_STMT_MAP_LINE, and CE_BANK_ACCOUNTS to resolve those relationships.