Results for “interest_action”

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

Overview

XTR_PAYMENT_SCHEDULE_V is a Treasury (XTR) module view owned by the APPS schema in Oracle E-Business Suite. It exposes the payment schedule definitions used by Treasury deal processing, including payment frequency, posting timing, calendar month flags, and default indicators. In both 12.1.1 and 12.2.2, the view is documented as VALID and returns a single row for each payment schedule definition keyed by deal type, product type, deal subtype, and payment schedule code. The view is a reporting and integration vehicle only; it contains no business logic beyond the column projection, so it is safe to query from custom concurrent programs, BI Publisher data templates, and outbound interfaces without risk of modifying Treasury setup data. Because the columns include DEFAULT_YN, administrators and analysts frequently use this view to identify which payment schedule Treasury will apply when a deal is created without an explicit override.

Underlying Base Objects

The view is defined over XTR_PAYMENT_SCHEDULE, exposed to the APPS schema through a synonym. The view text is a straightforward SELECT of every column from that base table, with no joins or filters applied. Consequently, the view inherits the row population, partitioning, and indexing characteristics of XTR_PAYMENT_SCHEDULE directly. There is no aggregation, no decode, and no outer join, which means row counts between the view and the base table are identical. From an ETRM metadata perspective, the referenced base object is documented as XTR_PAYMENT_SCHEDULE (SYNONYM), confirming that the view is a thin presentation layer rather than a denormalized reporting structure.

Key Columns

• DEAL_TYPE, PRODUCT_TYPE, DEAL_SUBTYPE — the classification attributes that scope a payment schedule to a specific class of Treasury instrument.
• PAYMENT_SCHEDULE_CODE — the identifier for the schedule definition; together with the three classification columns it forms the logical key.
• DESCRIPTION — the user-facing name of the payment schedule.
• DEFAULT_YN — indicates whether the schedule is the default for the associated deal type, product type, and subtype combination. This is the column most often referenced in searches.
• PAYMENT_FREQUENCY, POST_MONTHS_FORWARD, POSTING_FREQ, MIN_POSTINGS — control the timing and cadence of cash flows and postings.
• CALC_TYPE, ADJUST_ON_SETTLE, INTEREST_ACTION — determine how interest is calculated and what happens at settlement.
• JAN_YN through DEC_YN — twelve month flags indicating the months in which the schedule is active.
• NEXT_POSTING_DUE — the next scheduled posting date for the schedule definition.

Common Use Cases and Queries

The most frequent requirement is locating the default schedule for a given deal classification. The view lends itself to a simple predicate on DEFAULT_YN:

• SELECT payment_schedule_code, description FROM xtr_payment_schedule_v WHERE default_yn = 'Y' AND deal_type = :deal_type AND product_type = :product_type AND deal_subtype = :deal_subtype;
• Listing every schedule configured for a product: SELECT payment_schedule_code, description, payment_frequency, default_yn FROM xtr_payment_schedule_v WHERE product_type = :product_type ORDER BY default_yn DESC, payment_schedule_code;
• Auditing monthly coverage: SELECT payment_schedule_code, jan_yn, feb_yn, mar_yn, apr_yn FROM xtr_payment_schedule_v;
• Driving an outbound interface: SELECT * FROM xtr_payment_schedule_v WHERE deal_type = :deal_type AND default_yn = 'Y';

Because the view performs no filtering, always constrain queries by deal type, product type, or schedule code to avoid full scans on the underlying synonym.