Search Results ap_payment_terms




Overview
Explore in AI Chat

Overview

APPS.OKE_TERM_VALUES_V is a reporting and integration view in Oracle E-Business Suite (documented at 12.2.2, valid for 12.1.1 as well) that presents a consolidated, uniform listing of the various "term" definitions used across Oracle EBS modules. Rather than forcing downstream consumers—such as Oracle Contracts, Order Management, or custom integrations—to query each source table individually, the view unions terms originating from Oracle Payables, Oracle Receivables, Oracle Inventory/Shipping, and Oracle Contracts lookups into a single homogeneous column structure. Each row is tagged with a term code that identifies the originating family of terms (for example, AP_PAYMENT_TERMS, RA_PAYMENT_TERMS, IB_SHIPPING_METHOD), together with a numeric or coded identifier, a name, a description, effective dates, an enabled flag, and a computed "active" indicator.

This view is a key data source for payment term picklists and shipped-term lookup functionality embedded in the Order Capture / Oracle Contracts (OKE) framework. When a user searches for "ap_payment_terms," the view is typically the object reached through the Contracts term template or the payment-term list of values logic, where multiple module-specific term sources must be presented together in a single LOV.

Underlying Base Objects

The ETRM metadata documents the following referenced objects, all accessed by the APPS schema:

The view is a pure UNION ALL of these sources; no joins occur across branches. Column positions in every SELECT branch are aligned so that a single record shape is produced.

Key Columns

The view exposes ten positional columns, best understood by their meaning per branch:

  • Term Code (col 1) — discriminator naming the source family: 'AP_PAYMENT_TERMS', 'RA_PAYMENT_TERMS', 'IB_SHIPPING_METHOD', or the term code from OKE_TERMS_B for lookup-based rows.
  • Term ID / Org ID (col 2) — TO_CHAR of TERM_ID for AP/RA terms, ORGANIZATION_ID for shipping methods, or LOOKUP_CODE for lookup rows.
  • Freight Code (col 3) — populated ('N/A' or the freight code) mainly for the shipping-method branch.
  • Name (col 4) — the term or freight name, description, or lookup meaning.
  • Description (col 5) — the term description.
  • Start Date / End Date (cols 6, 7) — effective date range where maintained.
  • Enabled Flag (col 8) — populated mainly from the lookup branch's ENABLED_FLAG.
  • Active (col 9) — a computed flag returning 'N' if SYSDATE precedes the start date or exceeds the end date, otherwise 'Y' (or the enabled flag for lookups).
  • Org Code (col 10) — MTL_PARAMETERS.ORGANIZATION_CODE for the shipping branch, else NULL.

Common Use Cases and Queries

Typical use cases include building unified payment and shipping term lists of values, validating that a term is active on a given date, and auditing term definitions across modules.

  • List Payables terms: SELECT * FROM APPS.OKE_TERM_VALUES_V WHERE term_code = 'AP_PAYMENT_TERMS';
  • Find active terms only: SELECT term_name, description FROM APPS.OKE_TERM_VALUES_V WHERE active = 'Y';
  • Locate a specific term by name: SELECT term_id, term_name FROM APPS.OKE_TERM_VALUES_V WHERE term_name = 'IMMEDIATE';
  • Inspect shipping methods: SELECT org_code, freight_code, description FROM APPS.OKE_TERM_VALUES_V WHERE term_code = 'IB_SHIPPING_METHOD';

Because the view enforces lookup security group restrictions via FND_GLOBAL, results respect the security context of the querying responsibility when lookup-based terms are retrieved.