Search Results autocreated_from_system

Overview

APPS.CSI_SYSTEMS_V is an Oracle EBS service module view that exposes customer-installed system (CSI) records in a denormalized, reporting-friendly form. It sits in the Install Base (CSI) schema family and consolidates system header attributes with related Trading Community Architecture (TCA) party, account, site, location, and lookup information. Its purpose is to provide a single queryable surface for installed system data without requiring the caller to join the CSI system table to multiple TCA tables manually. The view is commonly consumed by Install Base reports, service contract generation, depot repair lookups, and integration interfaces that extract installed asset context for downstream systems. It is available in both EBS 12.1.1 and 12.2.2, with the documented metadata corresponding to 12.2.2.

Underlying Base Objects

The view is defined over the following documented base objects:

• CSI_SYSTEMS_VL — the underlying multi-language installed system entity aliased as S; supplies the core system header columns.
• CSI_LOOKUPS — aliased as LK; resolves the SYSTEM_TYPE_CODE into a user-facing SYSTEM_TYPE meaning.
• HR_OPERATING_UNITS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES — supply customer, party, account number, ship-to, bill-to, and address attributes.

Because several TCA objects are joined, the view effectively represents a curated projection of system plus party/account context rather than a raw table read.

Key Columns

The view exposes identifiers and TCA enrichment alongside configuration and audit fields. Notable columns include:

• SYSTEM_ID, SYSTEM_NUMBER, NAME, DESCRIPTION — system identity; description is truncated to 240 characters.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_PARTY_NUMBER, CUSTOMER_NUMBER — customer/account context.
• SYSTEM_TYPE_CODE, SYSTEM_TYPE, CONFIG_SYSTEM_TYPE — classification, with SYSTEM_TYPE decoded from lookups.
• PARENT_SYSTEM_ID — hierarchical grouping of systems.
• INSTALL_SITE_USE_ID, SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID — site-use references.
• TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID, BILL_TO_CONTACT_ID, SHIP_TO_CONTACT_ID — contact roles.
• START_DATE_ACTIVE, END_DATE_ACTIVE, COTERMINATE_DAY_MONTH — lifecycle and cotermination.
• AUTOCREATED_FROM_SYSTEM — maps the base column AUTOCREATED_FROM_SYSTEM_ID, identifying the parent system from which the record was automatically created.
• SHIP_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER, SHIP_TO_CUSTOMER_NUMBER, SHIP_TO_SITE_NUMBER, SHIP_TO_LOCATION_ID — ship-to enrichment.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT, OBJECT_VERSION_NUMBER — DFF and concurrency columns.

Common Use Cases and Queries

Typical scenarios include listing installed systems for a customer, tracing auto-created systems back to their origin, and joining systems to service contracts. The AUTOCREATED_FROM_SYSTEM column is the key for the user's search, representing the source system from which a record was generated.

• Find auto-created systems and their source:

  SELECT system_id, system_number, name, autocreated_from_system
  FROM   apps.csi_systems_v
  WHERE  autocreated_from_system IS NOT NULL;

• List active systems for a customer:

  SELECT system_id, system_number, customer_name, system_type
  FROM   apps.csi_systems_v
  WHERE  customer_number = :p_account
  AND    SYSDATE BETWEEN NVL(start_date_active,SYSDATE)
                     AND NVL(end_date_active,SYSDATE+1);

• Ship-to reporting:

  SELECT system_id, name, ship_to_customer, ship_to_site_number
  FROM   apps.csi_systems_v
  WHERE  ship_to_customer_id IS NOT NULL;

All queries should be executed against the APPS schema with appropriate Install Base responsibilities and row-level security consideration.