Results for “config_system_type”

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

Overview

OKX_SYSTEMS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product family. It exposes customer product "systems" — the installed configurations that service contracts reference — in a denormalized, integration-friendly form. The view is documented as VALID in both EBS 12.1.1 and 12.2.2 and is described in the ETRM metadata as "Systems for customer products."

Its principal role is to present system records together with their translatable descriptive attributes and a computed lifecycle status, so that downstream contract, service, and fulfillment processes can consume a single, stable row per system without joining the base tables themselves. Because the view is registered under the OKX module, it functions as a contracts-integration access point over the Customer Care (CS) system entities rather than as a standalone transactional object. Notably, the view synthesizes rows only from the base systems tables and deliberately returns NULL for inventory-related attributes, reflecting an integration contract rather than a full item-mastered representation.

Underlying Base Objects

The documented base objects referenced by OKX_SYSTEMS_V are CS_SYSTEMS_ALL_B and CS_SYSTEMS_ALL_TL, accessed through synonyms in the APPS schema. CS_SYSTEMS_ALL_B is the multilingual base table holding the system header attributes (identifier, customer, installed-site references, serial number, active dates, organization, and type codes). CS_SYSTEMS_ALL_TL is the translation table holding language-specific NAME and DESCRIPTION values. The join is on SYSTEM_ID, constrained by T.LANGUAGE = USERENV('LANG') so that each query returns the descriptive text in the session's current language. This B/TL pairing is the standard Oracle Applications multilingual pattern, and the view inherits the _ALL org-striping semantics of the base table through the ORG_ID column it exposes.

Key Columns

The view selects a fixed column list covering identity, relationship, and status attributes. Relevant columns include:

• SYSTEM_ID / ID1 — the system identifier, aliased to ID1; a literal '#' is returned as ID2.
• CUSTOMER_ID — the owning customer or party.
• NAME / DESCRIPTION — translatable text sourced from CS_SYSTEMS_ALL_TL.
• SERIAL_NUMBER — the system serial reference.
• SYSTEM_TYPE_CODE — the classification code for the system type, the column most commonly used to filter systems by category.
• CONFIG_SYSTEM_TYPE and PARENT_SYSTEM_ID — support hierarchical config and parent/child system structures.
• INSTALL_SITE_USE_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID — site-use references for installation, billing, and shipping.
• START_DATE_ACTIVE, END_DATE_ACTIVE, COTERMINATE_DAY_MONTH — lifecycle and cotermination attributes.
• ORG_ID — operating unit context.
• STATUS — a derived value computed with nested DECODE/SIGN logic comparing TRUNC(SYSDATE) against the active dates: 'I' (inactive/future) when the current date precedes the start date or exceeds the end date, otherwise 'A' (active).
• INVENTORY_ITEM_ID, ORGANIZATION_ID, PRIMARY_UOM_CODE — returned as NULL, indicating these item attributes are out of scope for this view.

Common Use Cases and Queries

Typical use is contract-integration reporting: retrieving active systems for a customer, filtering by type code, or listing systems with their current status and site references. Because the view resolves translatable text automatically, it suits concurrent-program extracts and interface queries that run under a specific language session.

For example, to list all active systems of a given type for a customer:

• SELECT system_id ID1, customer_id, name, serial_number, system_type_code, status FROM okx_systems_v WHERE customer_id = :p_customer_id AND system_type_code = :p_type_code AND status = 'A';

Alternatively, to enumerate the distinct system type codes in use:

• SELECT DISTINCT system_type_code FROM okx_systems_v ORDER BY system_type_code;

Queries joining on ID1 should apply the ORG_ID predicate where multi-org access is in force, since the view carries the operating unit column but does not enforce client-side org security on its own.