Results for “xtr_accepted_bids_v”

4 results




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

Overview

XTR_ACCEPTED_BIDS_V is a treasury-module (XTR) database view shipped with Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. It presents accepted bid information captured against treasury term actions, exposing retail rate-adjustment activity and mass rate-update (auction/bid) activity through a single unified result set. Because it is a view rather than a base table, it holds no data of its own; it is a read-only projection over the transaction tables that store term action records.

The view exists primarily for reporting and integration purposes. It enables inquiries, extracts, and downstream interfaces to retrieve accepted bid details — effective dates, new interest rates, deal references, and payment schedule codes — without requiring the consuming program to replicate the UNION logic separating retail adjustments from mass rate updates internally.

Underlying Base Objects

The view text references a single documented base object: XTR_TERM_ACTIONS. It is constructed as a UNION ALL of two SELECT statements issued against that table:

  • The first branch selects records where NVL(MASS_RATE_UPDATE, 'N') = 'N', labelled with the literal CALL_FROM value 'RETAIL'.
  • The second branch selects DISTINCT records where NVL(MASS_RATE_UPDATE, 'N') = 'Y' and NEW_INTEREST_RATE IS NOT NULL, labelled 'RATE'.

This union explains the 'CALL_FROM' discriminator column, which identifies whether a given row originated from retail term-action processing or from a mass rate update. Additional lookups such as deal, payment schedule, and rate references are resolved by the application layer rather than documented within the view text. No other base objects are documented in the ETRM metadata.

Key Columns

  • EFFECTIVE_DATE — Derived as NVL(INCREASE_EFFECTIVE_FROM_DATE, NVL(FROM_START_DATE, EFFECTIVE_FROM_DATE)) in the retail branch; the raw EFFECTIVE_FROM_DATE in the rate branch. This is the date from which the accepted bid's rate or payment adjustment takes effect.
  • PAYMENT_SCHEDULE_CODE — Identifies the payment schedule associated with the term action.
  • CREATED_ON — The timestamp when the underlying term action record was created. This is the column commonly used to determine when a bid or rate update was captured in the system, and it is frequently the target of user searches and date-range filters.
  • DEAL_NO — The deal number for retail rows; the rate-update branch returns the constant 0.
  • PRINCIPAL_ADJUST — The principal adjustment for retail rows; the rate-update branch returns the constant 0.
  • NEW_INTEREST_RATE — The new rate applied by the accepted bid or rate update; the rate branch filters on this column being non-null.
  • CALL_FROM — Literal discriminator: 'RETAIL' or 'RATE'.

Common Use Cases and Queries

The most frequent query pattern filters by creation timestamp, since users commonly track activity by the date it was recorded.

  • Retrieve recent accepted retail and rate bids: SELECT EFFECTIVE_DATE, CREATED_ON, PAYMENT_SCHEDULE_CODE, DEAL_NO, NEW_INTEREST_RATE, CALL_FROM FROM XTR_ACCEPTED_BIDS_V WHERE CREATED_ON >= SYSDATE - 30 ORDER BY CREATED_ON DESC;
  • Isolate rate-update activity only: SELECT DEAL_NO, NEW_INTEREST_RATE, CREATED_ON FROM XTR_ACCEPTED_BIDS_V WHERE CALL_FROM = 'RATE';
  • Identify deals with principal adjustments: SELECT DEAL_NO, PRINCIPAL_ADJUST, EFFECTIVE_DATE FROM XTR_ACCEPTED_BIDS_V WHERE PRINCIPAL_ADJUST <> 0;

Typical consumers include treasury reporting extracts, audit reconciliations of accepted bids, and interface programs feeding downstream pricing or payment systems. Note that the metadata records this view as "Not implemented in this database," so availability should be confirmed against each target instance before reliance.