Results for “ap_terms_bat_pay_terms_v”

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

Overview

The AP_TERMS_BAT_PAY_TERMS_V view is a Payables module database object owned by the APPS schema and registered as status VALID in Oracle E-Business Suite. Its documented purpose is to expose a simplified, effective-dated list of payment terms suitable for batch payment processing and reporting. The ETRM metadata explicitly notes a description of "(Release 10SC Only)," indicating the view originated as a legacy batch payment terms access path and has been carried forward, largely unchanged, into the 12.1.1 and 12.2.2 code lines where it remains a valid dictionary object.

Functionally, the view acts as a pass-through filter over AP_TERMS. Rather than presenting every term definition regardless of status, it returns only those terms whose active date range encompasses the current system date (SYSDATE). This makes it a convenient reporting and integration surface for both custom concurrent programs and external systems that need the set of payment terms currently valid for use in payment batches.

Underlying Base Objects

The view is defined over a single referenced base object: the AP_TERMS synonym in the APPS schema, which resolves to the Payables payment terms table. The documented view text is:

• SELECT NAME TERMS, DESCRIPTION DESCRIPTION, TERM_ID FROM AP_TERMS WHERE SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE - 1) AND NVL(END_DATE_ACTIVE, SYSDATE + 1)

The NVL logic is significant. Where START_DATE_ACTIVE is null, the lower bound defaults to SYSDATE - 1; where END_DATE_ACTIVE is null, the upper bound defaults to SYSDATE + 1. Terms with no effective dates therefore remain visible, while terms whose active window has expired (or has not yet begun) are excluded. Because the predicate is evaluated at query time rather than stored, the view is always self-adjusting to the current date and requires no maintenance.

Key Columns

• TERMS — The payment terms name, aliased from AP_TERMS.NAME. This is the user-facing term identifier used on invoices, payment batches, and supplier records.
• DESCRIPTION — The descriptive text for the terms, aliased from AP_TERMS.DESCRIPTION. Useful for reporting labels and for distinguishing similarly named terms.
• TERM_ID — The unique primary key of the term in AP_TERMS. This is the value to join against foreign-key columns such as AP_INVOICES_ALL.TERMS_ID or AP_SUPPLIERS.TERMS_ID.

Note that only three columns are projected; the effective-date columns, discount attributes, and installment detail held in AP_TERMS (and its related term-line tables) are not exposed through this view.

Common Use Cases and Queries

The view is typically used for term lookups in batch payment validation, custom reports, and integrations that must present only currently active terms. A representative query joins the view to invoices to confirm that each invoice references a term that is currently active:

• SELECT t.TERMS, t.TERM_ID, i.INVOICE_NUM, i.INVOICE_AMOUNT FROM AP_TERMS_BAT_PAY_TERMS_V t, AP_INVOICES_ALL i WHERE i.TERMS_ID = t.TERM_ID ORDER BY t.TERMS;
• SELECT TERMS, DESCRIPTION FROM AP_TERMS_BAT_PAY_TERMS_V ORDER BY TERMS;
• SELECT TERM_ID, TERMS FROM AP_TERMS_BAT_PAY_TERMS_V WHERE UPPER(TERMS) LIKE UPPER(:p_search || '%');

The third pattern supports an LOV-style search driven by user input. Because the view filters by effective dates implicitly, callers do not need to add their own date predicates. Implementers should treat the view as read-only and be aware that its projected surface is intentionally narrow; requirements calling for discount percentages, term lines, or base-amount schedules must query AP_TERMS and its child tables directly rather than extending reliance on this legacy object.