Search Results original_amount




Overview
Explore in AI Chat

Overview

XTR_PARCEL_SPLITS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered against the XTR – Treasury product. It exposes the parcel split structure used by Treasury to break a single deal into resalable or allocatable parcels, together with the financial attributes that describe each parcel. Because the view is defined as a simple projection over the base entity without joins, filtering, or aggregation, it behaves as a stable, denormalized read interface for the parcel split data.

In EBS 12.1.1 and 12.2.2 the view is registered as VALID, which confirms that its definition resolves cleanly against the synonym through which the base object is referenced. Its principal role is to support reporting, inquiry screens, and integration extracts that must read parcel data without touching the underlying transactional table directly. Notably, the view exposes ORIGINAL_AMOUNT, the column most frequently associated with the search term "original_amount."

Underlying Base Objects

The view is defined exclusively over XTR_PARCEL_SPLITS, referenced in the view text through a synonym. No additional tables, lookup views, or inline functions participate in the definition, so the view introduces no join cardinality risk and no row multiplication.

  • XTR_PARCEL_SPLITS – the single documented base object; holds one row per parcel split within a Treasury deal.
  • APPS.XTR_PARCEL_SPLITS – the synonym-resolved object name recorded in the ETRM metadata.

Because the SELECT list names every documented column explicitly and contains no WHERE clause, the view is a direct 1:1 projection. Row counts and commit-time visibility are therefore identical to the base table, and any DML or concurrent program operating on XTR_PARCEL_SPLITS is immediately reflected in the view.

Key Columns

The column set describes the identity of each parcel, its financial content, and its selection or sale status:

Common Use Cases and Queries

The view is typically used to report parcel composition, reconcile original amounts against current balances, and feed downstream resale or settlement processes.

  • Retrieving the original amount for a specific parcel split.
  • Identifying parcels still available for resale.
  • Comparing original versus remaining parcel value.
  • Extracting parcel data for integration or audit reconciliation.

Sample queries:

SELECT deal_no, parcel_split_no, original_amount FROM xtr_parcel_splits_v WHERE deal_no = :deal_no;

SELECT deal_no, parcel_split_no, face_value_amount, original_amount, parcel_remaining, consideration FROM xtr_parcel_splits_v WHERE available_for_resale = 'Y' ORDER BY deal_no, parcel_split_no;

SELECT deal_no, SUM(original_amount) original_total, SUM(consideration) current_total FROM xtr_parcel_splits_v GROUP BY deal_no;

Because the view is unfiltered, production queries should always constrain DEAL_NO or STATUS_CODE to avoid full scans of the parcel split table.