Results for “primary_uom_code”

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

Overview

OKX_BUS_PROCESSES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, documented under the OKX – Contracts Integration product. Its stated purpose is to expose transaction groups, presented as business processes drawn from the Contracts Integration foundation. In the EBS 12.1.1 and 12.2.2 environments, this view serves as a simplified, read-only projection over the CS_BUSINESS_PROCESSES base object, presenting a consolidated set of attributes suitable for concurrent programs, LOVs, and inquiry screens without requiring callers to join or transform the underlying table directly.

Because the OKX module governs contracts integration and the interchange of transactional data between EBS and external or downstream systems, views such as this one act as controlled interfaces. They shield consumers from base-table column changes and encapsulate derived logic, notably the STATUS computation, so that application logic and reports remain stable across releases.

Underlying Base Objects

The documented view text selects exclusively from CS_BUSINESS_PROCESSES, referenced in the metadata as a synonym. The view definition aliases that object as BP and derives every exposed column from it:

• BUSINESS_PROCESS_ID is renamed to ID1, establishing the primary identifier for each transaction group.
• NAME and DESCRIPTION are passed through unchanged from the base object.
• START_DATE_ACTIVE and END_DATE_ACTIVE are surfaced directly.
• STATUS is not stored on the base object; it is calculated by the view.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, and PRIMARY_UOM_CODE are emitted as fixed NULL values.

The presence of the constant '#' as ID2 and the three NULL columns indicates the view is designed to conform to a common reporting or interface structure—likely a flexible value-set or multi-source inquiry framework—where homogeneous column layouts are required across heterogeneous sources.

Key Columns

• ID1 – The business process identifier (BUSINESS_PROCESS_ID), used as the unique key for the transaction group.
• ID2 – A literal '#' placeholder, retained for structural conformance rather than data content.
• NAME – The business process name, typically the user-facing label for the transaction group.
• DESCRIPTION – Free-text description of the process.
• STATUS – Derived as 'A' (active) or 'I' (inactive) using nested DECODE/SIGN logic against SYSDATE, START_DATE_ACTIVE, and END_DATE_ACTIVE. A record is inactive when the current date precedes the start date or exceeds the end date; otherwise it is active.
• START_DATE_ACTIVE / END_DATE_ACTIVE – The effective date range governing the STATUS evaluation.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, PRIMARY_UOM_CODE – Always NULL; present only to satisfy a uniform column contract.

Common Use Cases and Queries

Typical uses include populating LOVs for transaction group selection, filtering active processes for integration runs, and driving inquiry forms in the Contracts Integration module. A straightforward listing of active processes can be produced with:

• SELECT name, description, start_date_active, end_date_active FROM okx_bus_processes_v WHERE status = 'A' ORDER BY name;
• SELECT id1, name FROM okx_bus_processes_v WHERE status = 'A'; — for LOV or validation-driven lookups.
• SELECT name FROM okx_bus_processes_v WHERE SYSDATE BETWEEN start_date_active AND end_date_active; — to reconcile the derived STATUS against explicit date logic.

Because STATUS is date-sensitive, results change automatically over time without data modification, making the view well suited for scheduling and eligibility checks in Contracts Integration processing.