Search Results bill_postal_code

Overview

CSI_SYSTEMS_V is a seeded, VALID view owned by the APPS schema and delivered as part of the CSI — Install Base product family in Oracle EBS 12.1.1 and 12.2.2. It exposes system-level records from the Install Base, resolving the numerous foreign key identifiers stored on the underlying CSI_SYSTEMS_VL entity into human-readable, denormalized attributes. The view is described in the ETRM as "System Details with foreign key resolutions," which precisely captures its purpose: rather than forcing report authors and integrators to repeatedly join customer, site, contact, and lookup tables, CSI_SYSTEMS_V performs those resolutions once and presents the results in a single queryable structure.

Because the Install Base is the repository of record for customer-owned configurations, systems, and their relationships, this view plays a central role in service, support, and contract reporting. It is frequently consumed by Oracle Service, Oracle Contracts, and Oracle Installed Base integrations, as well as by custom concurrent programs, BI Publisher data templates, and OBIEE/OTBI extracts that require installed-base attributes denormalized for downstream consumption. Practitioners searching on the column name bill_to_contact typically reach this view when attempting to identify the billing contact associated with an installed system — the view surfaces BILL_TO_CONTACT_ID alongside the corresponding bill-to site usage.

Underlying Base Objects

The view is defined over a mix of base entities and resolution sources. The documented referenced objects are CSI_LOOKUPS, CSI_SYSTEMS_VL, HR_OPERATING_UNITS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES.

• CSI_SYSTEMS_VL — the primary driver table, providing the system_id, system_number, system_type_code, parent_system_id, contact references, site use references, and descriptive attributes.
• CSI_LOOKUPS — supplies the MEANING decoding of SYSTEM_TYPE_CODE into the SYSTEM_TYPE display column.
• HR_OPERATING_UNITS — resolves OPERATING_UNIT_ID to the owning operating unit context.
• HZ_PARTIES — resolves CUSTOMER_ID to CUSTOMER_NAME and CUSTOMER_PARTY_NUMBER, and via the ship-to join supplies party attributes for the ship-to party.
• HZ_CUST_ACCOUNTS — provides the ACCOUNT_NUMBER exposed as CUSTOMER_NUMBER.
• HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS — resolve the install, bill-to, and ship-to site identifiers into site numbers and location identifiers.

Key Columns

The projection begins with S.ROWID as ROW_ID and S.SYSTEM_ID as the primary identifier, followed by standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER for optimistic locking.

• Customer attributes: CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_PARTY_NUMBER, CUSTOMER_NUMBER.
• System attributes: SYSTEM_TYPE_CODE and its decoded SYSTEM_TYPE, SYSTEM_NUMBER, PARENT_SYSTEM_ID, CONFIG_SYSTEM_TYPE, NAME, DESCRIPTION (truncated to 240 characters), START_DATE_ACTIVE, END_DATE_ACTIVE, COTERMINATE_DAY_MONTH, AUTOCREATED_FROM_SYSTEM.
• Contact references: TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID, BILL_TO_CONTACT_ID, SHIP_TO_CONTACT_ID. These are the identifiers that answer searches such as "bill_to_contact."
• Site usage references: INSTALL_SITE_USE_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID.
• Ship-to resolution: SHIP_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER, SHIP_TO_CUSTOMER_NUMBER, SHIP_PARTY_TYPE, SHIP_FIRST_NAME, SHIP_LAST_NAME, SHIP_TO_SITE_NUMBER, SHIP_TO_L... (location).
• Descriptive flexfield: ATTRIBUTE1 through ATTRIBUTE15 plus CONTEXT.

Common Use Cases and Queries

A typical customer-facing requirement is to list all installed systems with their billing contact context:

• Installed-base reconciliation reports that compare system records against contract coverage.
• Service dashboards that display bill-to and ship-to party details for each system.
• Data migration and integration extracts feeding external CRM or billing platforms.
• Ad hoc queries locating all systems associated with a given customer party or site use.

Sample query joining contact names via HZ_CONTACT_POINTS or a contacts resolution view:

SELECT system_number, system_type, customer_name,
       bill_to_contact_id, bill_to_site_use_id,
       start_date_active, end_date_active
FROM   apps.csi_systems_v
WHERE  customer_number = :p_account_number
AND    NVL(end_date_active, SYSDATE+1) > SYSDATE;

Because CSI_SYSTEMS_V resolves so many foreign keys, report authors should exercise care with date-effective joins on the HZ tables and with the DESCRIPTION truncation to 240 characters when comparing against source data.