Search Results ce_200_groups_v




Overview
Explore in AI Chat

Overview

CE_200_GROUPS_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose the available Oracle Payables (AP) and Oracle Payments (IBY) payment groups that are eligible for reconciliation within Cash Management. The view functions as a reconciliation-facing layer that presents payment instruction batches — logically grouped as "groups" — together with their associated internal bank account, bank, branch, payment date, currency, and legal entity context. Rather than storing data, it derives its rows entirely from underlying transactional and setup objects, returning a denormalized result set suitable for reporting, LOV queries, and integration with bank statement reconciliation flows. Because the row source is filtered to include only payment instructions with a populated logical group reference, the view is intentionally scoped to payment groupings that participate in the reconciliation process.

Underlying Base Objects

The view is defined over several documented objects, joined to produce a single reconciliation-oriented row set:

  • IBY_PAY_INSTRUCTIONS_ALL (synonym) — the payment instruction header, supplying payment date, currency, organization, and instruction identifiers.
  • IBY_PAYMENTS_ALL (synonym) — the payment records linked to instructions; the join requires a non-null LOGICAL_GROUP_REFERENCE, which drives the group-level orientation of the view.
  • CE_BANK_ACCTS_GT_V (view) — provides internal bank account details, including account number, currency, and account owner organization.
  • HZ_PARTIES (synonym) — joined twice to resolve the bank party name and the bank branch party name.
  • GL_SETS_OF_BOOKS (view) — supplies the functional (set of books) currency used to classify each payment as FUNCTIONAL, BANK, or FOREIGN.
  • CE_SYSTEM_PARAMETERS (synonym) — Links the legal entity to the appropriate set of books via LEGAL_ENTITY_ID and SET_OF_BOOKS_ID.
  • CE_LOOKUPS (view) — Restricts the results to the PAYMENT batch type lookup, validating the instruction as a payment grouping.

The joins enforce that only bank accounts tied to a legal entity matching the system parameters, with valid party resolution and a populated logical group reference, are returned.

Key Columns

The view exposes a numbered projection of columns. Notable entries include:

  • BANK_ACCOUNT_ID / BANK_ACCOUNT_NAME / BANK_ACCOUNT_NUM — Internal bank account identity for the payment group.
  • PAYMENT_INSTRUCTION_ID — Identifier of the payment instruction (also output as a TO_CHAR string in several positions for display and filtering).
  • LOOKUP_CODE / MEANING — The batch type code and its translated meaning, sourced from CE_LOOKUPS.
  • PAYMENT_DATE / PAYMENT_CURRENCY_CODE — Timing and currency of the payment instruction.
  • Currency classification — A DECODE comparing payment currency to the functional currency and bank account currency, yielding FUNCTIONAL, BANK, or FOREIGN.
  • ORG_ID-derived columns — DECODE logic separating OPERATING_UNIT and LEGAL_ENTITY organization identifiers.
  • Bank and branch party names — Resolved from HZ_PARTIES for identification.
  • LOGICAL_GROUP_REFERENCE — The grouping key that qualifies records for reconciliation.

Numerous NULL placeholders are included to align the view's column count with downstream consumers, and standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) are carried through.

Common Use Cases and Queries

Typical usage involves locating reconcilable payment groups by bank account or date range, and joining back to Cash Management reconciliation entities. A representative query:

  • SELECT bank_account_id, bank_account_name, payment_instruction_id, payment_date, payment_currency_code FROM ce_200_groups_v WHERE bank_account_id = :p_bank_account_id AND payment_date BETWEEN :p_from AND :p_to;

Additional scenarios include filtering by currency classification for foreign-currency reconciliation review, resolving the legal entity grouping for multi-org reporting, and presenting the view as a value set for payment group selection in Cash Management reconciliation pages. Because the view pre-joins lookup, party, and set-of-books data, it reduces the need for callers to replicate these joins manually.