Search Results xtr_payment_schedule




Overview
Explore in AI Chat

Overview

The XTR_PAYMENT_SCHEDULE table is a core reference data object within the Oracle E-Business Suite Treasury (XTR) module, specifically for versions 12.1.1 and 12.2.2. It functions as a master repository for defining and storing valid payment schedule templates applicable to retail term money deals. These deals are financial instruments where a principal amount is placed or borrowed for a fixed term, with a predefined schedule for interest payments and principal repayment. The table's primary role is to enforce data integrity and provide a centralized definition of payment frequencies (e.g., monthly, quarterly, bullet) and structures, which are then linked to individual treasury deals. This ensures standardization and consistency in cash flow calculations and payment processing across all term money transactions.

Key Information Stored

The table's structure is defined by a composite primary key, which uniquely identifies each valid payment schedule. The key columns are DEAL_SUBTYPE, PRODUCT_TYPE, and PAYMENT_SCHEDULE_CODE. These columns work in conjunction to categorize the financial product and specify the exact schedule code applicable. While the provided metadata does not list all columns, the table typically stores descriptive information about the schedule, such as a name or description for the PAYMENT_SCHEDULE_CODE. It may also contain attributes defining the calculation basis (e.g., actual/360, 30/360) and timing rules for payments. The table's design ensures that a payment schedule is explicitly valid for a specific combination of deal subtype and product type, providing granular control over deal configuration.

Common Use Cases and Queries

The primary use case is the validation and defaulting of payment terms during the entry of a new retail term money deal in the XTR module. When a user creates a deal, the application references this table to present a valid list of payment schedules based on the selected DEAL_SUBTYPE and PRODUCT_TYPE. For reporting and operational analysis, common queries involve joining this table to the transactional deal table. A fundamental SQL pattern is to retrieve all deals using a specific payment schedule:

  • SELECT d.deal_number, d.start_date, p.payment_schedule_code FROM xtr_deals d, xtr_payment_schedule p WHERE d.deal_subtype = p.deal_subtype AND d.product_type = p.product_type AND d.payment_schedule_code = p.payment_schedule_code AND p.payment_schedule_code = 'QUARTERLY';

Administrators may also query the table to audit or maintain the list of available schedule codes for various products.

Related Objects

The most critical relationship for the XTR_PAYMENT_SCHEDULE table is its parent-child link with the XTR_DEALS table. As documented, a foreign key constraint exists where the columns XTR_DEALS.DEAL_SUBTYPE, XTR_DEALS.PRODUCT_TYPE, and XTR_DEALS.PAYMENT_SCHEDULE_CODE reference the primary key of XTR_PAYMENT_SCHEDULE. This enforces referential integrity, ensuring every deal's payment schedule is defined in the master schedule table. The table is also intrinsically related to the cash flow engine and interest calculation routines within the XTR module, which consume the schedule definitions to generate projected payment amounts and dates. While not explicitly listed, other reference tables for product types (XTR_PRODUCT_TYPES) and deal subtypes likely provide the context for the code values used in this table's key columns.