Results for “control_dr_line_count”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CE_STATEMENT_HEADERS_V is an Oracle E-Business Suite view owned by the APPS schema within the Cash Management (CE) product family. It presents a denormalized, reporting-oriented projection of bank statement headers, joining statement header records to their corresponding bank account and bank branch attributes so that a single query can return statement-level data enriched with bank master information. The view is documented in ETRM as retrofitted, indicating it was introduced or re-pointed during an upgrade cycle to preserve backward compatibility for dependent forms, reports, and interfaces. In Oracle EBS 12.1.1 and 12.2.2, it is most commonly consumed by Cash Management reconciliation pages, bank statement inquiry reports, and custom integrations that import or validate statement headers.

Underlying Base Objects

The documented base objects referenced by the view are CE_BANK_ACCTS_GT_V (a view), CE_BANK_BRANCHES_V (a view), and CE_STATEMENT_HEADERS (exposed through a synonym). The view text confirms these relationships: statement header columns are sourced from the CE_STATEMENT_HEADERS alias SH, bank account attributes from the bank account view aliased BA, and bank branch attributes from the bank branch view aliased BB. Salient source columns include BA.BANK_ACCOUNT_NAME, BA.BANK_ACCOUNT_NUM, BA.CURRENCY_CODE, BA.MULTI_CURRENCY_ALLOWED_FLAG (aliased to MULTI_CURRENCY_FLAG), BA.ASSET_CODE_COMBINATION_ID, and BB.BANK_NAME and BB.BANK_BRANCH_NAME. Because the view derives from other views, its column set and column order are dictated by the underlying bank account and branch view definitions rather than by a single base table.

Key Columns

• ROW_ID — SH.ROWID; a unique row identifier for the statement header.
• BANK_ACCOUNT_ID / BANK_ACCOUNT_NAME / BANK_ACCOUNT_NUM — identify the bank account against which the statement was loaded.
• MULTI_CURRENCY_FLAG — aliased from BA.MULTI_CURRENCY_ALLOWED_FLAG; this is the column returned when users search for "multi_currency_flag," indicating whether the bank account permits transactions in multiple currencies.
• TRX_CURRENCY_TYPE — hard-coded as NULL in the view text.
• STATEMENT_HEADER_ID / STATEMENT_NUMBER / STATEMENT_DATE — core statement identification.
• CONTROL_BEGIN_BALANCE, CONTROL_END_BALANCE, CONTROL_TOTAL_DR, CONTROL_TOTAL_CR — statement control totals used for reconciliation validation.
• CONTROL_DR_LINE_COUNT / CONTROL_CR_LINE_COUNT — expected debit and credit line counts.
• AUTO_LOADED_FLAG, STATEMENT_COMPLETE_FLAG, GL_DATE — statement processing status and accounting date.
• CASHFLOW_BALANCE, INT_CALC_BALANCE, ONE_DAY_FLOAT, TWO_DAY_FLOAT — float and cash position metrics.
• ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE columns — descriptive flexfield and global descriptive flexfield segments.
• DOC_SEQUENCE_ID / DOC_SEQUENCE_VALUE, CHECK_DIGITS — document sequencing and validation data.

Common Use Cases and Queries

The view is typically used to drive bank statement inquiry screens, reconciliation utilities, and custom reporting where both statement totals and bank account context are required in one pass. A representative query retrieves open statements and their multi-currency capability:

• SELECT statement_number, statement_date, bank_account_num, currency_code, multi_currency_flag, control_end_balance, statement_complete_flag FROM ce_statement_headers_v WHERE bank_account_id = :p_bank_account_id ORDER BY statement_date DESC;
• SELECT statement_number, gl_date, cashflow_balance, one_day_float, two_day_float FROM ce_statement_headers_v WHERE auto_loaded_flag = 'Y' AND statement_complete_flag = 'N';
• SELECT bank_name, bank_branch_name, statement_number, control_total_dr, control_total_cr FROM ce_statement_headers_v WHERE statement_number = :p_statement_number;

Because MULTI_CURRENCY_FLAG is sourced from the bank account view, joins back to CE_BANK_ACCOUNTS or CE_STATEMENT_HEADERS using STATEMENT_HEADER_ID or BANK_ACCOUNT_ID are common when additional attributes are needed. Reports should always filter by bank account or statement number to avoid full scans, and integrations should treat TRX_CURRENCY_TYPE as non-populated since the view returns NULL for that column.