Results for “csi_system_type”

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

Overview

XNC_SYSTEMS_PO_RG_V is a reporting view historically shipped with the Oracle E-Business Suite module XNC — Sales for Communications, a vertical application that has since been classified as obsolete. The view exposes the system name and related attributes of pending orders associated with a given party and customer account. In the EBS 12.1.1 and 12.2.2 release streams, this object is retained only for backward compatibility; ETRM documentation explicitly records its implementation status as "Not implemented in this database," and no base objects are formally documented for the view metadata record.

Functionally, the view serves as a denormalized join layer that combines telecommunication system instance data (held in the CSI transaction systems table) with trading partner and customer account information from the Oracle Trading Community Architecture (TCA) model. By doing so, it allows a party or account to be associated with the serialized systems or services they have ordered, together with a decoded system type and a free-text description. This pattern was typical of XNC reporting, where order fulfillment data had to be flattened for use in concurrent programs, Oracle Reports outputs, and OBIEE or Discoverer style reporting layers.

Underlying Base Objects

The view is defined over four documented objects:

• CSI_T_TXN_SYSTEMS CSTTS — the transaction systems table, providing the system identifier, name, number, description, type code, and the customer identifier used for the joins.
• HZ_CUST_ACCOUNTS HCA — the TCA customer account table, supplying the account number, customer account identifier, and party identifier.
• HZ_PARTIES HP — the TCA party table, supplying the party name of the owning entity.
• FND_LOOKUP_VALUES CLK — the standard EBS lookup table, used here to decode CSI_SYSTEM_TYPE lookup codes into a meaningful system type.

The joins follow the TCA model: CSTTS.CUSTOMER_ID equals HCA.CUST_ACCOUNT_ID, and HCA.PARTY_ID equals HP.PARTY_ID. The lookup join to FND_LOOKUP_VALUES is written as an outer join (the (+) operator), constrained to LOOKUP_TYPE = 'CSI_SYSTEM_TYPE', the session language via USERENV('LANG'), and VIEW_APPLICATION_ID = 542. Because the lookup is outer-joined, systems with an unmapped type code still return rows, with a null system type. This predates the ANSI join syntax and reflects the legacy Oracle join convention used throughout 11i/12.x views.

Key Columns

• SYSTEM_ID — the transaction system identifier (CSTTS.TRANSACTION_SYSTEM_ID).
• SYSTEM_NAME — the name of the system instance.
• SERIAL_NUMBER — the system number as held in CSTTS.SYSTEM_NUMBER.
• PARTY_NAME — the name of the owning party from HZ_PARTIES.
• ACCOUNT_NUMBER — the customer account number from HZ_CUST_ACCOUNTS.
• SYSTEM_DESCRIPTION — the descriptive text recorded against the system. This is the column most frequently targeted by users searching for "system_description."
• SYSTEM_TYPE — the decoded lookup meaning for the system type code.
• CUSTOMER_ID / CUST_ACCOUNT_ID / PARTY_ID — the three link keys enabling joins back to order, account, or party queries.

Common Use Cases and Queries

Typical usage is limited to backward-compatible reporting against legacy XNC data. A common requirement is retrieving the description of pending systems for a given party and account:

• Producing a listing of all systems with their serial number, type, and description for an account, for use in customer-facing fulfillment reports.
• Diagnosing missing or unmapped system type codes by selecting rows where SYSTEM_TYPE is null.
• Joining to order tables via CUSTOMER_ID or CUST_ACCOUNT_ID to correlate systems with pending order lines.

A sample query follows:

SELECT system_name, serial_number, party_name, account_number, system_description, system_type
FROM xnc_systems_po_rg_v
WHERE account_number = :p_account_number
ORDER BY system_name;

Because the view is documented as not implemented and the XNC module is obsolete in 12.1.1 and 12.2.2, customers should confirm the object exists in their database and migrate such reporting to supported CSI or TCA views where possible.