Results for “xtr_payment_schedule”

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

Overview

XTR_PAYMENT_SCHEDULE is a Treasury (XTR) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores payment schedule definitions for retail term money deals. Each row represents a named schedule template that controls how interest and principal postings are generated for a given combination of deal type, product type, and deal subtype. Rather than a transactional ledger, this is a reference and setup object: it dictates posting frequency, permitted posting months, calculation behavior, and interest handling rules that downstream deal processing relies upon.

The table is owned by the XTR schema and is documented with 26 columns. Its primary key is XTR_PAYMENT_SCHEDULE_PK, defined over the composite of DEAL_SUBTYPE, PRODUCT_TYPE, and PAYMENT_SCHEDULE_CODE. From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning: the natural business key (the composite primary key) identifies a durable, non-transactional concept, while descriptive attributes such as frequency, calculation type, and month flags behave like satellite attributes that could be split into a separate satellite in a Data Vault design. In practice, this table functions as a lookup master referenced by deal records.

Key Information Stored

The most significant columns fall into three groups:

• Key and classification columns: DEAL_TYPE, PRODUCT_TYPE, DEAL_SUBTYPE, and PAYMENT_SCHEDULE_CODE. Together with the composite primary key, these form the business-key candidates that uniquely identify a schedule. PAYMENT_SCHEDULE_CODE is the user-facing identifier, while the other three establish the deal context in which the schedule applies.
• Behavioral control columns: PAYMENT_FREQUENCY and POSTING_FREQ define how often postings occur; POST_MONTHS_FORWARD determines the forward posting horizon; MIN_POSTINGS sets the minimum number of postings; NEXT_POSTING_DUE indicates the next scheduled posting date; and CALC_TYPE governs the calculation method used for interest.
• Descriptive and eligibility columns: DESCRIPTION, DEFAULT_YN (marking a schedule as the default for its deal context), ADJUST_ON_SETTLE, INTEREST_ACTION, plus twelve monthly flags JAN_YN through DEC_YN that declare which calendar months permit postings.

The surrogate primary key XTR_PAYMENT_SCHEDULE_PK is derived from the composite business key rather than an independent sequence, so no separate surrogate identifier exists beyond the natural composite key. Unique index concerns center on the DEAL_SUBTYPE / PRODUCT_TYPE / PAYMENT_SCHEDULE_CODE combination.

Common Use Cases and Queries

Typical scenarios include validating that a deal references a valid schedule, retrieving the default schedule for a product configuration, and reporting posting frequencies and monthly eligibility for audit or reconciliation. A representative pattern joins the schedule to deal records:

SELECT p.PAYMENT_SCHEDULE_CODE, p.DESCRIPTION, p.PAYMENT_FREQUENCY
FROM   XTR.XTR_PAYMENT_SCHEDULE p, XTR.XTR_DEALS d
WHERE  d.DEAL_SUBTYPE = p.DEAL_SUBTYPE
  AND  d.PRODUCT_TYPE = p.PRODUCT_TYPE
  AND  d.PAYMENT_SCHEDULE_CODE = p.PAYMENT_SCHEDULE_CODE;

Configuration reporting commonly filters on DEFAULT_YN = 'Y' to identify default templates, or inspects the JAN_YN through DEC_YN flags to confirm that a schedule avoids disallowed posting months. Analysts frequently aggregate by PRODUCT_TYPE to summarize how many schedules exist per product line.

Related Objects

• XTR_DEALS — the principal consumer. Deal rows reference this table through DEAL_SUBTYPE, PRODUCT_TYPE, and PAYMENT_SCHEDULE_CODE, forming the documented foreign key relationship.
• XTR_DEALS.DEAL_SUBTYPE — the foreign key column cited in the ETRM relationship metadata linking deals to schedule definitions.
• Other Treasury setup objects related by DEAL_TYPE and PRODUCT_TYPE context, which provide the classification values consumed by schedules and deals alike.
• Downstream posting and interest-calculation processes that read PAYMENT_FREQUENCY, CALC_TYPE, and NEXT_POSTING_DUE to generate scheduled transactions.

Because the documented relationships are narrow, the XTR_DEALS join is the primary integration point for querying and reporting against this table.