Search Results bill_address1

Overview

CS_CP_SYSTEMS_MAINT_V is a Service (CS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose the system details of a product recorded in Oracle Installed Base, consolidating the header attributes of an installed system with the party and address context associated with its ship-to, install, and bill-to roles. The view is used primarily for reporting, service contract administration, and integration endpoints that require a denormalized, read-only projection of installed system data rather than direct navigation of the base Installed Base tables.

Because the view joins customer, party, and location entities from the Trading Community Architecture (TCA) model, it returns ready-to-consume descriptive fields such as party names, party types, and address elements alongside the system identifiers. This makes it suitable for maintenance-oriented screens and correspondence generation where both the system and its responsible parties must be presented together.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, CS_CP_SYSTEMS_MAINT_V is defined over the following base objects, all referenced through APPS synonyms:

• CS_SYSTEMS — the Installed Base system header, supplying ROW_ID, SYSTEM_ID, SYSTEM_TYPE_CODE, SERIAL_NUMBER, PARENT_SYSTEM_ID, configuration type, descriptive flexfield columns (ATTRIBUTE1–15, CONTEXT), and contact/site references.
• HZ_CUST_ACCOUNTS — the customer account, used to resolve the owning customer.
• HZ_PARTIES — the party records for customer, ship-to, install, and bill-to roles (aliased HZPTY1, HZPTY2, HZPTY3, and the customer party).
• HZ_PARTY_SITES — links parties to locations for each role.
• HZ_CUST_ACCT_SITES_ALL — customer account site usages referenced by the site use identifiers on CS_SYSTEMS.
• HZ_LOCATIONS — address data (ADDRESS1–ADDRESS4, DESCRIPTION) for ship-to, install, and bill-to locations.

The view is a direct projection driven by CS_SYSTEMS, enriched by repeated outer or inner joins to the TCA tables for each distinct party-role combination.

Key Columns

• ROW_ID, SYSTEM_ID — primary identifiers of the Installed Base system record.
• CUSTOMER_ID, CUSTOMER_NAME — owning customer account and its resolved party name.
• SYSTEM_TYPE_CODE, SERIAL_NUMBER, PARENT_SYSTEM_ID, CONFIG_SYSTEM_TYPE, NAME, DESCRIPTION — system identity and hierarchy attributes.
• INSTALL_SITE_USE_ID, SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID — site use references for the three address roles.
• TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID, BILL_TO_CONTACT_ID, SHIP_TO_CONTACT_ID — contact assignments.
• START_DATE_ACTIVE, END_DATE_ACTIVE, COTERMINATE_DAY_MONTH — lifecycle and cotermination data.
• SHIP_ADDRESS1–SHIP_ADDRESS4, INSTALL_ADDRESS1–INSTALL_ADDRESS4, BILL_ADDRESS1 — role-specific address elements derived from HZ_LOCATIONS.
• SHIP_PARTY_NAME, INSTALL_PARTY_NAME, BILL_PARTY_NAME and their party type/person name columns — role-specific party detail.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — descriptive flexfield content.

Note that the documentation excerpt exposes BILL_ADDRESS1 but does not list further bill address columns; the ship and install roles expose ADDRESS1 through ADDRESS4. Consumers searching for "bill_address4" should therefore validate at runtime whether that column exists in their instance, since the documented column list terminates at BILL_ADDRESS1. In practice, extending the pattern used for SHIP_ADDRESS4 and INSTALL_ADDRESS4 suggests HZLOC3.ADDRESS4, but this is not confirmed by the ETRM excerpt.

Common Use Cases and Queries

Typical scenarios include installed base reporting by customer, service contract sourcing, and address validation for field service dispatch. A representative query follows:

• Listing systems with ship and install addresses for a customer:
  SELECT system_id, serial_number, customer_name, ship_address1, install_address1
  FROM apps.cs_cp_systems_maint_v
  WHERE customer_id = :p_customer_id;
• Identifying active systems by type:
  SELECT system_id, name, system_type_code, start_date_active
  FROM apps.cs_cp_systems_maint_v
  WHERE system_type_code = :p_type
  AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
• Resolving billing party detail for invoice correspondence:
  SELECT system_id, bill_party_name, bill_party_type, bill_address1
  FROM apps.cs_cp_systems_maint_v
  WHERE system_id = :p_system_id;

Because the view joins multiple TCA tables, queries should always filter on indexed identifiers such as SYSTEM_ID or CUSTOMER_ID to avoid full scans across the party and location joins. Confirm column availability, particularly for bill-to address elements, against the actual view definition in the target instance before deploying dependent code.