Search Results bill_state

Overview

CS_SYSTEMS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the Service (CS) product family. It presents a denormalized, reporting-friendly projection of the CS_SYSTEMS entity — the master record of a customer's installed system or asset — enriched with descriptive attributes resolved from Oracle Trading Community Architecture (TCA) and Oracle Service lookup tables. Where the underlying CS_SYSTEMS table stores only numeric foreign keys for customer, contact, and site references, CS_SYSTEMS_V resolves those keys into human-readable party names, account numbers, addresses, and lookup meanings, which makes it suitable for operational reporting, Oracle Discoverer or BI Publisher queries, and inbound/outbound integration extracts. The view is documented as VALID in ETRM 12.2.2 and is available in both 12.1.1 and 12.2.2.

Underlying Base Objects

Per the documented ETRM metadata, CS_SYSTEMS_V is defined over the following base objects:

• CS_SYSTEMS (synonym) — the primary driving table, supplying system identity, serial number, system type, active dates, parent system, technical and service admin contacts, install site, bill-to and ship-to references, descriptive flexfield columns, and ORG_ID.
• CS_LOOKUPS (view) — joined to translate SYSTEM_TYPE_CODE into its display MEANING.
• HZ_PARTIES (synonym) — joined multiple times to resolve customer party names for the customer, ship-to, and install parties.
• HZ_CUST_ACCOUNTS (synonym) — supplies the CUSTOMER_NUMBER (account number).
• HZ_CUST_ACCT_SITES_ALL and HZ_PARTY_SITES (synonyms) — resolve site-use references to party sites.
• HZ_LOCATIONS (synonym) — supplies address elements (address1–4, city, state, postal code, country) for the ship-to location.
• FND_GLOBAL (package) — referenced for session context, notably ORG_ID resolution under Multi-Org Access Control.

Key Columns

• ROW_ID, SYSTEM_ID — primary identifier of the system record.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER — the owning customer resolved from HZ_PARTIES and HZ_CUST_ACCOUNTS.
• SYSTEM_TYPE_CODE, SYSTEM_TYPE — coded value and its lookup meaning.
• SERIAL_NUMBER, NAME, DESCRIPTION — system identification attributes; DESCRIPTION is truncated to 240 characters.
• PARENT_SYSTEM_ID, CONFIG_SYSTEM_TYPE — hierarchy and configuration classification.
• TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID — support contacts.
• INSTALL_SITE_USE_ID plus INSTALL_CUSTOMER/INSTALL_PARTY_TYPE columns.
• BILL_TO_CONTACT_ID, BILL_TO_SITE_USE_ID — the bill-to contact and site-use references sought by users searching for bill_to_contact.
• SHIP_TO_CONTACT_ID, SHIP_TO_SITE_USE_ID and the SHIP_TO_* address columns.
• START_DATE_ACTIVE, END_DATE_ACTIVE, COTERMINATE_DAY_MONTH — lifecycle dates.
• ATTRIBUTE1–15, CONTEXT — descriptive flexfield columns.
• ORG_ID — operating unit for multi-org security.

Common Use Cases and Queries

The view is most often queried to list installed systems per customer with resolved addresses, or to locate contact assignments for billing and shipping. A typical query filtering on the bill-to contact is:

• SELECT system_id, name, serial_number, customer_name, customer_number, bill_to_contact_id, bill_to_site_use_id FROM cs_systems_v WHERE org_id = :p_org_id AND bill_to_contact_id IS NOT NULL;
• Installed base reporting by customer and address: SELECT customer_name, name, serial_number, ship_to_address1, ship_to_location, system_type FROM cs_systems_v WHERE customer_number = :p_account;
• Active-system extract for integration: SELECT system_id, serial_number, system_type_code, start_date_active, end_date_active FROM cs_systems_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

Because ORG_ID is exposed, queries should always constrain it in multi-org environments. Consumers should note the DESCRIPTION truncation and treat the view as read-only.