Search Results acceptor_code




Overview
Explore in AI Chat

Overview

XTR_ACCEPTOR_CODES_V is a dictionary view in the Oracle E-Business Suite Treasury (XTR) module. Its name associates it with the acceptor_code attribute found in Treasury deal records, and its definition confirms that it serves as a distinct-value lookup over that attribute rather than a full listing of deals. The view returns the unique set of acceptor codes that appear on current, buy-side, non-interest-bearing deals.

In Oracle EBS 12.1.1 and 12.2.2, the view is typically consumed by Treasury inquiry screens, value-list (LOV) queries, and downstream reporting where a picklist of valid or previously used acceptor codes is required without exposing the entire deal population. Because the view is a reporting abstraction, it does not carry its own storage; it inherits the security and partitioning characteristics of the underlying deal view.

The ETRM documentation records this object as "Not implemented in this database," meaning that in the reference environment used to generate the ETRM metadata, the view was not compiled or deployed. Nonetheless, the documented view text provides an authoritative definition for environments in which it is present.

Underlying Base Objects

The documented view text references a single source object:

The ETRM metadata for XTR_ACCEPTOR_CODES_V lists no separately documented base tables. In practice, XTR_DEALS_V is itself a view over the Treasury deal tables (such as XTR_DEALS and its associated party/company detail tables), so XTR_ACCEPTOR_CODES_V is a second-level view built on top of that abstraction. The DISTINCT operator collapses duplicate acceptor codes arising from multiple qualifying deals into a single row per code.

Because the filter conditions reference DEAL_TYPE, DEAL_SUBTYPE, and STATUS_CODE on XTR_DEALS_V, the view inherits any row-level security or organizational access controls implemented on that underlying view. No joins, unions, or aggregate functions beyond DISTINCT are documented, so the view's performance profile is essentially that of a distinct scan over the qualifying slice of XTR_DEALS_V.

Key Columns

  • ACCEPTOR_CODE — the sole column exposed by the view. It is the acceptor code carried on qualifying Treasury deals, representing the party or counterparty designated as acceptor for the instrument. In Treasury usage, the acceptor is commonly the party accepting a bill of exchange or similar obligation, and the code is the internal identifier for that party.

The selection is constrained by three predicates applied in the view definition:

  • DEAL_TYPE = 'NI' — restricts to a specific deal type classification used within Treasury.
  • DEAL_SUBTYPE = 'BUY' — restricts to the buy subtype.
  • STATUS_CODE = 'CURRENT' — restricts to deals that are currently active rather than cancelled, matured, or otherwise closed.

Common Use Cases and Queries

The principal use case is populating an LOV or inquiry parameter with the acceptor codes actually in use on current buy-side NI deals, so that users select a code that yields at least one matching transaction. A second use case is validation: confirming that a code entered on a new deal already exists elsewhere, or auditing which acceptor codes have fallen out of use.

Typical queries include:

  • SELECT acceptor_code FROM xtr_acceptor_codes_v ORDER BY acceptor_code;
  • SELECT COUNT(*) FROM xtr_acceptor_codes_v; — to size the distinct code population.
  • SELECT d.deal_number, d.acceptor_code FROM xtr_deals_v d WHERE d.acceptor_code IN (SELECT acceptor_code FROM xtr_acceptor_codes_v) AND d.status_code = 'CURRENT'; — to list current deals by acceptor.

Because the view returns only distinct codes, it should not be used to count deals or to retrieve deal-level attributes; those requirements belong to XTR_DEALS_V directly.