Results for “differences_account”

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

Overview

CE_SYSTEM_PARAMETERS_MRC_V is a multi-reporting-currency (MRC) view in the APPS schema, owned by Oracle Cash Management (CE). It presents the cash management system parameters as configured for each set of books, exposing both the primary configuration columns and the reporting-currency context through SET_OF_BOOKS_ID. The view is a retrofitted MRC object: its naming convention and the SET_OF_BOOKS_ID projection reflect Oracle's transition from the older multi-organization/multi-currency architecture toward the Ledger and Secondary Ledger model in Release 12. In practice, the view behaves as the MRC-aware read layer over the Cash Management system parameters, allowing reporting and integration components to retrieve parameter settings in the correct set-of-books context.

Its role is primarily reporting and integration: concurrent programs, reconciliation logic, bank statement processing, and open interface handling use these parameters to determine behavior such as cleared-item display, matching order, and voided payment visibility.

Underlying Base Objects

The view is defined over a single documented base object, CE_SYSTEM_PARAMETERS (accessed through a synonym), which stores one parameter row per cash management configuration. CE_SYSTEM_PARAMETERS_MRC_V exists as a compatibility/MRC view that projects Set of Books context onto those rows. The view text selects SET_OF_BOOKS_ID and the CE_SYSTEM_PARAMETERS columns, aliasing the base row as CE, and includes the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus the fifteen ATTRIBUTE flex columns.

The View Text also shows that the MRC view maps the current base columns to legacy MRC-style names. For example, AMOUNT_TOLERANCE_OLD, PERCENT_TOLERANCE_OLD, RECEIVABLES_TRX_ID_OLD, DIFFERENCES_ACCOUNT_OLD, ORG_ID_OLD, and a series of matching and handling flags (_OLD) are projected. Crucially for identity purposes, SHOW_VOID_PAYMENT_FLAG appears in the view text without the _OLD suffix, indicating it is a current, actively referenced parameter rather than a legacy retained column.

Key Columns

• SET_OF_BOOKS_ID — the set of books / ledger context for the parameter row; the MRC discriminator column reported first in the view.
• CASHBOOK_BEGIN_DATE — start date governing cashbook and reconciliation processing.
• SHOW_CLEARED_FLAG — controls whether cleared transactions are displayed.
• SHOW_VOID_PAYMENT_FLAG — controls whether voided payments are visible in Cash Management inquiry and reconciliation screens. This is the column users most frequently search for in this view.
• LINES_PER_COMMIT — batch commit size for processing interfaces, affecting performance and throughput.
• INTERFACE_PURGE_FLAG / INTERFACE_ARCHIVE_FLAG — govern purge and archive behavior for cash management interfaces.
• LINE_AUTOCREATION_FLAG — enables automatic creation of bank statement lines.
• AP_MATCHING_ORDER / AR_MATCHING_ORDER — determine the matching sequence for Payables and Receivables transactions.
• FLOAT_HANDLING_FLAG — behaviour for float status handling.
• ENABLE_OPEN_INTERFACE_FLAG, OPEN_INTERFACE_FLOAT_STATUS, OPEN_INTERFACE_CLEAR_STATUS, OPEN_INTERFACE_MATCHING_CODE — configuration of the open interface processing path.
• EXCHANGE_RATE_TYPE / EXCHANGE_RATE_DATE — default rate type and rate date conventions for currency conversion.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY — descriptive flexfield storage.

Common Use Cases and Queries

Typical use cases include verifying whether voided payments are displayed for a given configuration, auditing parameter differences across sets of books, and supporting reporting that must be resolved against Cash Management settings.

To find the voided payment setting across sets of books:

• SELECT set_of_books_id, show_void_payment_flag, show_cleared_flag FROM apps.ce_system_parameters_mrc_v ORDER BY set_of_books_id;

To inspect the full active parameter row for one set of books:

• SELECT set_of_books_id, cashbook_begin_date, show_void_payment_flag, lines_per_commit, ap_matching_order, ar_matching_order, exchange_rate_type FROM apps.ce_system_parameters_mrc_v WHERE set_of_books_id = :p_sob_id;

To confirm the parameter source and view definition at the database level:

• SELECT text FROM dba_views WHERE view_name = 'CE_SYSTEM_PARAMETERS_MRC_V';

Because the view is documented as retrofitted and MRC-based, queries should filter or join on SET_OF_BOOKS_ID to obtain the correct context and should not assume a single global parameter row.