Results for “csi_systems_b”

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

Overview

CSI_SYSTEMS_B is the base table for System Details within the Oracle E-Business Suite Install Base (CSI) product module. It stores the master definition of a "system," a logical grouping of customer-configurable items that are treated as a single serviceable entity. In the Install Base model, individual instances are recorded in CSI_ITEM_INSTANCES, while CSI_SYSTEMS_B provides the higher-level container that binds those instances to a customer, a set of contacts, and ship-to, bill-to, and install-site addresses. The table is owned by the CSI schema and is documented as a VALID object in both Oracle EBS 12.1.1 and 12.2.2.

In heuristic Data Vault terms, the foreign-key topology of this table is satellite-leaning. It carries a single-column surrogate primary key (SYSTEM_ID), descriptive and state-like attributes such as SYSTEM_TYPE_CODE, SYSTEM_NUMBER, and START_DATE_ACTIVE/END_DATE_ACTIVE, plus several role-based references to HZ_PARTIES and customer account tables. This profile is consistent with a satellite surrounding one or more hub or link structures, so a Data Vault modeler would typically treat CSI_SYSTEMS_B as a descriptive satellite rather than a true business hub, even though it functions as the primary system-of-record table inside EBS itself.

The physical schema contains 46 columns, and the primary key is enforced by CSI_SYSTEMS_B_PK on SYSTEM_ID. A unique index, CSI_SYSTEMS_B_U01, also exists on SYSTEM_ID, which is the closest documented business-key candidate.

Key Information Stored

The most significant columns and their roles are:

• SYSTEM_ID — surrogate primary key (CSI_SYSTEMS_B_PK); the value propagated into CSI_ITEM_INSTANCES.SYSTEM_ID, CSI_SYSTEMS_H.SYSTEM_ID, CSI_T_TXN_LINE_DETAILS.CSI_SYSTEM_ID, and CS_INCIDENTS_ALL_B.SYSTEM_ID.
• SYSTEM_NUMBER — the user-facing system identifier; the natural counterpart to the surrogate key.
• SYSTEM_TYPE_CODE — classifies the system (for example, a configuration versus a standalone grouping).
• CONFIG_SYSTEM_TYPE — further distinguishes the configuration/system category.
• CUSTOMER_ID — the owning customer account, referencing HZ_CUST_ACCOUNTS.
• PARENT_SYSTEM_ID — a self-referencing FK that supports system hierarchies.
• AUTOCREATED_FROM_SYSTEM_ID — a second self-referencing FK recording the system from which this record was automatically generated.
• SHIP_TO_CONTACT_ID, BILL_TO_CONTACT_ID, TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID — four role-based contact references to HZ_PARTIES.
• SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID — address references to HZ_CUST_SITE_USES_ALL.
• INSTALL_SITE_USE_ID — installation site, referencing HZ_PARTY_SITES.
• START_DATE_ACTIVE, END_DATE_ACTIVE — the effective dating window for the system record.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS and governs multi-organization data access.
• OPERATING_UNIT_ID, MIGRATED_FLAG, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — organizational context, migration state, and concurrent-program audit information.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard EBS who-columns and optimistic locking.
ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the standard DFF extensibility block.

Common Use Cases and Queries

Typical use cases include reporting on customer-owned systems, resolving all instances that belong to a system, tracing system hierarchies, and joining system records to service incidents. A representative query lists active systems with their customer and primary contacts:

SELECT s.system_id, s.system_number, s.system_type_code,
a.account_number, p.party_name
FROM csi_systems_b s, hz_cust_accounts a, hz_parties p
WHERE s.customer_id = a.cust_account_id
AND s.technical_contact_id = p.party_id
AND TRUNC(SYSDATE) BETWEEN s.start_date_active
AND NVL(s.end_date_active, TRUNC(SYSDATE));

To explode a system into its instances, join CSI_ITEM_INSTANCES on SYSTEM_ID. To traverse hierarchy, self-join CSI_SYSTEMS_B on PARENT_SYSTEM_ID. To report incidents per system, join CS_INCIDENTS_ALL_B on SYSTEM_ID. Because the table also feeds CSI_T_TXN_LINE_DETAILS, it is frequently used in transaction and move-order reconciliation reporting. Always constrain by SECURITY_GROUP_ID or OPERATING_UNIT_ID where multi-org access is enabled.

Related Objects

• CSI_ITEM_INSTANCES — child table; joins on CSI_ITEM_INSTANCES.SYSTEM_ID = CSI_SYSTEMS_B.SYSTEM_ID, the primary mechanism for expanding a system into its component items.
• CSI_SYSTEMS_H — history table; joins on CSI_SYSTEMS_H.SYSTEM_ID = CSI_SYSTEMS_B.SYSTEM_ID for audit and change tracking.
• CSI_T_TXN_LINE_DETAILS — transaction line detail; joins on CSI_T_TXN_LINE_DETAILS.CSI_SYSTEM_ID = CSI_SYSTEMS_B.SYSTEM_ID.
• CS_INCIDENTS_ALL_B — service incident base table; joins on CS_INCIDENTS_ALL_B.SYSTEM_ID = CSI_SYSTEMS_B.SYSTEM_ID.
• HZ_CUST_ACCOUNTS — referenced via CUSTOMER_ID for the owning account.
• HZ_PARTIES — referenced four times, through SHIP_TO_CONTACT_ID, BILL_TO_CONTACT_ID, TECHNICAL_CONTACT_ID, and SERVICE_ADMIN_CONTACT_ID.
• HZ_CUST_SITE_USES_ALL — referenced via SHIP_TO_SITE_USE_ID and BILL_TO_SITE_USE_ID.
• HZ_PARTY_SITES — referenced via INSTALL_SITE_USE_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security.