Search Results ap_terms




Overview
Explore in AI Chat

Overview

APBV_AP_PAYMENT_TERMS is a read-only view in the APPS schema that exposes payment term definitions maintained in Oracle Payables. It is a database view rather than a base table, meaning it carries no independent storage and reflects the current state of its single source object at query time. The view is defined with the WITH READ ONLY clause, so it can be queried or joined but cannot be used as the target of DML operations. Its purpose in Oracle EBS 12.1.1 and 12.2.2 is to provide a stable, security-consistent read interface to payment term configuration for reporting, integration, and diagnostic queries, without exposing the full column set of the underlying table.

Because the object is owned by APPS and is read-only, it is typically consumed by custom reports, extracts, and interface programs that need to resolve a payment term identifier or name without touching the base table directly. The documented metadata classifies it under ETRM 12.2.2 with the referenced base object AP_TERMS, exposed through a synonym.

Underlying Base Objects

The view is defined over a single documented base object: AP_TERMS, referenced via synonym. Its view text is a straightforward projection:

No joins, aggregations, or filters are applied. Consequently, the view returns one row per payment term row in AP_TERMS, preserving the table's cardinality. There is no MTI (multiple table insert) behavior, no organization security predicate, and no function-based derivation. Any change committed in AP_TERMS is immediately visible through the view, which makes it unsuitable as a point-in-time snapshot but appropriate for real-time lookups.

Key Columns

  • TERM_ID — Primary identifier for the payment term. This is the value stored on AP invoices, suppliers, and purchasing documents when a term is assigned.
  • NAME — User-visible payment term name, such as "Immediate" or "Net 30." This is the value most frequently used in joins to invoice headers for reporting.
  • DUE_CUTOFF_DAY — The day of the month on which due-date calculation is cut off, relevant for terms with multiple installments.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — Effective date range governing when the term may be selected. END_DATE_ACTIVE null generally indicates an open-ended term.
  • RANK — Ordering rank used when presenting or prioritizing terms.
  • DESCRIPTION — Free-text description of the term.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns identifying who created or last modified the term and when.

Common Use Cases and Queries

Typical scenarios include validating that a payment term referenced by an interface staging record exists and is active, listing terms for a value-set or LOV-style extract, and resolving a term name to its TERM_ID during invoice import processing. A basic listing of currently effective terms:

  • SELECT term_id, name, due_cutoff_day, start_date_active, end_date_active FROM apps.apbv_ap_payment_terms WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE)) ORDER BY rank, name;

Joining to invoice headers to report terms in use:

  • SELECT ah.invoice_num, pt.name AS payment_term, ah.invoice_date FROM apps.ap_invoices_all ah, apps.apbv_ap_payment_terms pt WHERE ah.terms_id = pt.term_id AND ah.org_id = :org_id;

Because the view is read-only and mirrors AP_TERMS exactly, no DML, no row-level security, and no archival behavior should be assumed. It is best treated as a convenience projection for read-only integration and reporting.