Search Results apbv_ap_payment_terms




Overview
Explore in AI Chat

Overview

APBV_AP_PAYMENT_TERMS is a business view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Payables (AP) product. It is classified as a "Business view," meaning it is intended for consumption by reports, integrations, and external interfaces rather than as a transactional base table. The view presents a simplified, read-only projection of Oracle Payables payment terms, exposing the descriptive and control attributes of each term definition without requiring the caller to understand the full AP_TERMS table structure.

Because the view is defined with the WITH READ ONLY clause, it cannot be used for DML operations. Consumers can only query it, which reinforces its role as a reporting and integration surface. This is significant in Oracle EBS 12.1.1 and 12.2.2, where direct DML against AP_TERMS is already governed by application logic and validation; the read-only constraint makes the view safe to expose to downstream systems such as data warehouses, BI Publisher reports, and extract programs.

Underlying Base Objects

The view is defined exclusively over AP_TERMS, referenced through its APPS synonym. The view text is:

AP_TERMS is the master table that stores payment term definitions, including their names, due cutoff logic, effective dating, and ranking. APBV_AP_PAYMENT_TERMS does not join to any additional objects; it is a one-to-one, column-aliased projection of AP_TERMS. As a result, row counts and filtering behavior in the view match the parent table exactly, subject to the standard APPS schema access privileges required to query it.

Key Columns

  • PAYMENT_TERM_ID (aliased from TERM_ID) — The unique primary key identifying each payment term. This is the value stored on invoices, suppliers, and other Payables entities that reference a term.
  • PAYMENT_TERM_NAME (aliased from NAME) — The user-visible name of the payment term, such as "Net 30" or "Immediate." This is the attribute most commonly searched for by users and reporting tools.
  • DUE_CUTOFF_DAY — The day of the month used to determine due date cutoff behavior for terms that calculate due dates relative to a cutoff point.
  • START_EFFECTIVE_DATE / END_EFFECTIVE_DATE (aliased from START_DATE_ACTIVE / END_DATE_ACTIVE) — The active date range during which the term is valid. A null end date generally indicates the term is currently active.
  • RANK — A numeric ordering attribute used to prioritize or sequence payment terms, particularly in selection or defaulting scenarios.
  • DESCRIPTION — Free-form text describing the payment term.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard Oracle EBS audit columns tracking who created and last modified each row, and when.

Common Use Cases and Queries

The view is typically used to resolve payment term names for display in reports where only the term identifier is otherwise available, and to drive validation or lookup lists in integrations. A common pattern is joining PAYMENT_TERM_ID from an invoice or supplier record back to this view to obtain the readable PAYMENT_TERM_NAME.

Example query returning active terms ordered by rank:

  • SELECT PAYMENT_TERM_ID, PAYMENT_TERM_NAME, DUE_CUTOFF_DAY FROM APBV_AP_PAYMENT_TERMS WHERE (END_EFFECTIVE_DATE IS NULL OR END_EFFECTIVE_DATE >= SYSDATE) ORDER BY RANK;

Example lookup by name, matching the common "payment_term_name" search pattern:

  • SELECT PAYMENT_TERM_ID, PAYMENT_TERM_NAME, START_EFFECTIVE_DATE, END_EFFECTIVE_DATE FROM APBV_AP_PAYMENT_TERMS WHERE PAYMENT_TERM_NAME = :p_term_name;

Because all columns are read-only, the view is well suited for BI Publisher data models, Oracle Reports, and extract-to-flat-file programs. When integrating, note that effective dating must be applied explicitly through START_EFFECTIVE_DATE and END_EFFECTIVE_DATE; the view does not filter inactive terms on its own.