Results for “yield_round_type”

36 results




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

Overview

XTR_A_BOND_ISSUES is a Treasury (XTR) module table within Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the master definition of bond and debenture instruments issued or tracked by the organization. The object was created from the entity "XTR BOND ISSUE" by Oracle on 06-MAY-93, and it remains a VALID dictionary object owned by the XTR schema. In functional terms, the table acts as the instrument-level reference record for debt securities, capturing issuance terms, coupon conventions, day-count and yield calculation rules, rounding behavior, and pricing model configuration that downstream accrual, valuation, and settlement processes consume.

Based on the heuristic Data Vault classification mined from its foreign-key structure, XTR_A_BOND_ISSUES is characterized as standalone. In Data Vault modeling terms this suggests the table behaves as an independent hub or reference construct rather than a pure transaction satellite, since it carries a single outgoing foreign key and is not dependent on a parent transactional link. This classification should be treated as a modeling suggestion rather than a definitive architectural statement.

Key Information Stored

The table comprises 52 documented columns. The most operationally significant are:

The documented FK identifies SECURITY_ID as the sole foreign key, referencing EDR_PSIG_SECURITY. No separate surrogate primary key column is enumerated in the metadata beyond the implicit row identifier; BOND_ISSUE_CODE and SECURITY_ID serve as the principal business-key candidates for uniqueness.

Common Use Cases and Queries

Typical usage centers on instrument reference lookups, coupon schedule derivation, and integration with the security master. Common patterns include:

  • Retrieving issuance terms for a given bond code: SELECT bond_issue_code, coupon_rate, coupon_type, maturity_date FROM xtr_a_bond_issues WHERE bond_issue_code = :code;
  • Joining to the security master to reconcile Treasury instruments with enterprise securities: SELECT b.bond_issue_code, s.security_id FROM xtr_a_bond_issues b JOIN edr_psig_security s ON b.security_id = s.security_id;
  • Listing active instruments by currency and maturity window for cash-flow forecasting: SELECT * FROM xtr_a_bond_issues WHERE currency = :ccy AND maturity_date BETWEEN :from_dt AND :to_dt;
  • Reporting on DFF attributes for regulatory or risk segmentation: SELECT bond_issue_code, attribute1, attribute2 FROM xtr_a_bond_issues;
  • Auditing recently changed instruments: SELECT * FROM xtr_a_bond_issues WHERE updated_on > SYSDATE - 7;

Related Objects

XTR_A_BOND_ISSUES principally references the enterprise security master EDR_PSIG_SECURITY through SECURITY_ID. Downstream, it is consumed by Treasury accrual, coupon schedule, valuation, and settlement processes within the XTR module, which join on BOND_ISSUE_CODE or SECURITY_ID. Related reference data includes currency and day-count definitions (YEAR_BASIS, SETTLEMENT_BASIS), pricing model and market data set configuration, and risk-group reference tables. Standard audit relationships exist with FND_USER via CREATED_BY and UPDATED_BY for who-column resolution. Because the documented metadata lists only one explicit foreign key, any additional dependencies should be confirmed against the actual XTR data model in the target release before being relied upon in production queries.