Results for “autocreated_from_system_id”

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

Overview

The view APPS.CSI_CP_SYSTEMS_ALL_B_V is a backward-compatibility object shipped with the Oracle Install Base (CSI) module. It exists to preserve the naming convention and column interface used by earlier releases of the E-Business Suite, allowing customizations, reports, and integrations written against the legacy "CP Systems" view name to continue functioning after the underlying data model was consolidated onto the CS_SYSTEMS_ALL_B base table schema. In Oracle EBS 12.1.1 and 12.2.2 the view is owned by APPS, is registered as a VALID database object, and is defined with a straightforward projection of columns from CSI_SYSTEMS_B (referenced through the CSI_SYSTEMS_B synonym). Because it is a simple, non-joined view it adds no filtering or business logic of its own; it is a pure interface shim over the Install Base "systems" entity, which models customer system (asset group) records maintained under the Service/Install Base responsibility.

Underlying Base Objects

Per the documented view text, the definition selects from CSI_SYSTEMS_B CSB, with the referenced base object listed in the metadata as the CSI_SYSTEMS_B synonym (aliased through the base table CS_SYSTEMS_ALL_B, as noted in the description). The view performs no joins — it is a single-table projection — and it emits a literal NULL ORG_ID in place of any organization identifier. This confirms it is a base-table (non-translated, non-operating-unit-secured) view intended to satisfy legacy column expectations rather than to represent multi-org access. All documented columns map one-to-one onto columns of the underlying systems base table.

Key Columns

• SYSTEM_ID — Primary identifier of the system (asset group) record.
• CUSTOMER_ID — Customer/party that owns the installed system.
• SYSTEM_TYPE_CODE, CONFIG_SYSTEM_TYPE — Classification of the system record and its configuration type.
• SERIAL_NUMBER — Exposed from the base column SYSTEM_NUMBER; this is the alias most relevant to install-base external naming.
• PARENT_SYSTEM_ID, AUTOCREATED_FROM_SYSTEM_ID — Self-referencing relationships defining hierarchies and autocreation lineage.
• INSTALL_SITE_USE_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID — Site-use references for installation, billing, and shipping addresses.
• BILL_TO_CONTACT_ID — Contact associated with the bill-to site for the system. This is the column matched by the user's search term "bill_to_contact_id" and is exposed directly from CSB.BILL_TO_CONTACT_ID.
• SHIP_TO_CONTACT_ID, TECHINICAL_CONTACT_ID (sic — note the documented misspelling in the view text, aliased internally as TECHNICAL_CONTACT_ID), SERVICE_ADMIN_CONTACT_ID — Contact roles for shipping, technical, and service administration.
• START_DATE_ACTIVE, END_DATE_ACTIVE, COTERMINATE_DAY_MONTH — Effective-dating and cotermination attributes.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — DFF (descriptive flexfield) columns.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO/audit columns.
• ORG_ID — Always NULL in this view (not sourced from the base table).

Common Use Cases and Queries

The view is typically used when a legacy report or interface expects the CP Systems interface. A representative lookup by bill-to contact is:

• SELECT system_id, serial_number, customer_id, bill_to_contact_id, bill_to_site_use_id FROM csi_cp_systems_all_b_v WHERE bill_to_contact_id = :contact_id;
• Joining to HZ_CUST_ACCOUNTS/HZ_PARTIES on customer_id to resolve customer names.
• Joining to HZ_CUST_ACCT_SITES_ALL and site-use tables via bill_to_site_use_id for address detail.
• Reporting active systems using START_DATE_ACTIVE/END_DATE_ACTIVE predicates.

Because the view exposes no ORG_ID value and applies no security predicates, callers requiring operating-unit or MOAC enforcement should query the underlying CS_SYSTEMS_ALL_B/CSI_SYSTEMS_B objects directly rather than relying on this compatibility view.