Search Results xtr_reconciliation_process_v




Overview
Explore in AI Chat

Overview

XTR_RECONCILIATION_PROCESS_V is a Treasury (XTR) module database view owned by the APPS schema. It exposes configuration data that governs how the Treasury reconciliation process is executed, including the sequence in which reconciliation steps run, the verification method applied, and the pass code assigned to reconciled records. In Oracle EBS 12.1.1 and 12.2.2, Treasury uses reconciliation to match internal transaction records (for example, cash management, deal, or interest rate entries) against external statements and bank feeds. The rules that drive that matching are not hard-coded; they are stored as data and read at runtime.

This view is the primary read interface to that configuration. Because it is a view rather than a table, it is intended to be queried for reporting, validation, and integration purposes, while updates are directed to the underlying base object. Its PROCESS_TYPE column is frequently the target of inquiries, as it identifies which reconciliation method or process category a given configuration row applies to. In practice, the view serves as a reference source for functional consultants auditing reconciliation setup, for technical developers building custom reconciliation logic, and for DBA scripts validating that the correct process types have been configured.

Underlying Base Objects

The view is defined over a single documented base object:

  • XTR_RECONCILIATION_PROCESS — the base table (accessed via a synonym) that physically stores the reconciliation process configuration.

The view text is a straightforward projection, selecting each column from the base table without joins, filters, or aggregation:

Because the mapping is one-to-one, the view introduces no derived values or business logic of its own. It functions as a stable, read-only access path to the configuration table, shielding consumers from direct table dependencies and providing a consistent name for reporting and integration. Any change made to the base table is immediately visible through the view.

Key Columns

  • SEQUENCE_ORDER — the execution order in which this reconciliation process entry is evaluated relative to others.
  • VERIFICATION_METHOD — the method used to verify or match records during reconciliation.
  • RECONCILED_PASS_CODE — the pass code assigned to records that successfully reconcile under this process.
  • PROCESS_TYPE — identifies the category or type of reconciliation process this row configures; this is the column most commonly used as a selection filter.
  • DAYS_ADJUSTMENT — the number of days by which dates are shifted during reconciliation (for example, to accommodate value-date versus posting-date differences).
  • ALLOW_HOLIDAYS_YN — flag indicating whether holidays are permitted when calculating adjustment dates.
  • GENERATE_REPORT_YN — flag controlling whether a reconciliation report is produced for this process configuration.

Common Use Cases and Queries

Typical use cases include auditing which process types are configured, retrieving the sequence and verification method for a given process type, and driving custom reporting or interfaces that must respect the configured reconciliation rules.

List all configured reconciliation processes in execution order:

SELECT process_type,
       sequence_order,
       verification_method,
       reconciled_pass_code,
       days_adjustment,
       allow_holidays_yn,
       generate_report_yn
FROM   apps.xtr_reconciliation_process_v
ORDER BY sequence_order;

Retrieve configuration for a specific process type:

SELECT process_type, sequence_order, verification_method
FROM   apps.xtr_reconciliation_process_v
WHERE  process_type = :p_process_type
ORDER BY sequence_order;

Identify processes that generate reports and permit holidays:

SELECT process_type, sequence_order, days_adjustment
FROM   apps.xtr_reconciliation_process_v
WHERE  generate_report_yn = 'Y'
AND    allow_holidays_yn = 'Y';

Because the view exposes the base table without filters, a query against it returns the full configuration set, and the PROCESS_TYPE predicate is the most effective way to narrow results.