Results for “b_status”

50+ results




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

Overview

OKX_PAYABLES_TERMS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite. It belongs to the OKX product family, which handles Contracts Integration, and its documented purpose is to expose supplier payment term definitions in a normalized form suitable for consumption by Oracle Contracts and related integration flows. The view is marked VALID, indicating that its underlying dependency chain resolves cleanly in both Oracle EBS 12.1.1 and 12.2.2 environments. Its role is to translate the multilingual, flag-based payment terms data held in Oracle Payables into a language-filtered result set with a simplified status indicator, avoiding the need for downstream code or reports to interpret the Y/N enabled flag directly.

Underlying Base Objects

The view is defined over a single documented base object: AP_TERMS_TL, referenced in the APPS schema through a synonym. AP_TERMS_TL is the translatable (TL) table that stores payment term names and descriptions in each installed language, keyed by TERM_ID and LANGUAGE. Because it is a TL table, the view applies a language filter using USERENV('LANG') so that each session returns term text in its own language. The view does not join to AP_TERMS_B; instead it relies on the TL table alone, since the columns required for integration—name, description, active dates, and enabled status—reside in the TL structure. No additional base tables are documented for this view.

Key Columns

The view exposes the following columns:

  • NAME — the payment term name in the session language, taken from AP_TERMS_TL.NAME.
  • DESCRIPTION — the descriptive text for the payment term in the session language.
  • START_DATE_ACTIVE — the date from which the payment term becomes usable.
  • END_DATE_ACTIVE — the date on which the payment term ceases to be usable.
  • B_STATUS — the raw ENABLED_FLAG value ('Y' or 'N') from AP_TERMS_TL, preserved for consumers that require the underlying flag.
  • STATUS — a decoded value derived via DECODE(PT.ENABLED_FLAG, 'Y', 'A', 'I'), mapping an enabled term to 'A' (Active) and any other value to 'I' (Inactive).

Internally the view also projects ID1 (TERM_ID) and a literal '#' as ID2, which are used by the OKX integration framework for keying and lookup purposes rather than for direct user reporting.

Common Use Cases and Queries

Typical scenarios include validating which payment terms are available for contract or supplier integration, synchronizing term definitions into external systems, and generating reports on active versus inactive terms. Because the view filters on the session language, queries return text consistent with the user's environment.

A basic listing of active payment terms:

  • SELECT name, description, start_date_active, end_date_active FROM apps.okx_payables_terms_v WHERE status = 'A';

Identifying terms that have been disabled for integration purposes:

  • SELECT name, b_status FROM apps.okx_payables_terms_v WHERE b_status = 'N';

Filtering by an effective date window for point-in-time validation:

  • SELECT name, start_date_active, end_date_active FROM apps.okx_payables_terms_v WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Because the view is a thin projection over AP_TERMS_TL, query performance is generally efficient, and users should be aware that results are constrained by the session language and by the enabled flag as recorded in Oracle Payables.