Results for “techinical_contact_id”

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

Overview

APPS.CSI_CP_SYSTEMS_ALL_B_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes customer product system records maintained by the Enterprise Installation Standards and Telecommunications Management (EBS) / Customer Product (CSI) module. The view presents the base system definition rows held in the CSI_SYSTEMS_B table, formatting them for consumption by interfaces, concurrent programs, and downstream integration points that need a stable, read-only projection of installed system data.

The view exists in the "ALL" naming family, which in EBS typically signals an org-stripped or cross-organization read model. Consistent with this, the view text explicitly defines the last projected column as NULL ORG_ID rather than deriving the value from the underlying table, indicating that the view deliberately suppresses multi-org partitioning in favor of a single, unified result set. Because it is a "_V" view defined over a "_B" (base) table, it functions as the base-layer projection prior to translation handling; there is no associated "_TL" joining logic applied here.

The most notable structural characteristic, and the artifact returned by the search term "techinical_contact_id," is that the underlying column TECHNICAL_CONTACT_ID is exposed under the aliased name TECHINICAL_CONTACT_ID. This misspelling—dropping the second "c" in "TECHNICAL"—is present in the view definition itself. Consumers must therefore reference the misspelled alias, not the correctly spelled underlying column name, when querying the view.

Underlying Base Objects

The view is defined over a single referenced base object, CSI_SYSTEMS_B, which the ETRM documentation lists as a synonym. The query aliases that object as CSB and performs a straightforward column-for-column projection with no joins, filters, aggregations, or functions applied. Every column in the view maps one-to-one to a column of the same or similar name in CSI_SYSTEMS_B, with three naming transformations worth noting: SYSTEM_NUMBER is projected as SERIAL_NUMBER, TECHNICAL_CONTACT_ID is projected as the misspelled TECHINICAL_CONTACT_ID, and ORG_ID is supplied as a literal NULL rather than sourced from the base table.

Key Columns

• SYSTEM_ID — Primary identifier of the installed system record.
• SERIAL_NUMBER — Derived from SYSTEM_NUMBER; the manufacturer or system serial reference.
• CUSTOMER_ID — Owning customer of the system.
• SYSTEM_TYPE_CODE / CONFIG_SYSTEM_TYPE — Classification of the system and its configuration type.
• PARENT_SYSTEM_ID / AUTOCREATED_FROM_SYSTEM_ID — Hierarchical and provenance relationships between systems.
• TECHINICAL_CONTACT_ID — Technical contact party for the system (note the documented misspelling).
• SERVICE_ADMIN_CONTACT_ID, BILL_TO_CONTACT_ID, SHIP_TO_CONTACT_ID — Administrative and transactional contacts.
• INSTALL_SITE_USE_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID — Site-use references for the corresponding locations.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating of the system record.
• ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — Descriptive flexfield columns.
• OBJECT_VERSION_NUMBER — Optimistic locking version, consistent with the 12.2.x object model.
• ORG_ID — Always NULL in this view.

Common Use Cases and Queries

Typical usage includes extracting installed base details for service contracts, asset tracking, and telemetry integrations. To retrieve systems with their technical contacts, the misspelled alias must be used:

• SELECT system_id, serial_number, customer_id, techinical_contact_id FROM apps.csi_cp_systems_all_b_v WHERE customer_id = :p_customer_id;
• SELECT system_id, serial_number, start_date_active, end_date_active FROM apps.csi_cp_systems_all_b_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• SELECT system_id, parent_system_id FROM apps.csi_cp_systems_all_b_v WHERE parent_system_id IS NOT NULL;

Because the view applies no filters and returns ORG_ID as NULL, queries relying on organization security must supply their own org context or join to the underlying CSI_SYSTEMS_B table directly.