Search Results cs_ra_addr_install_rg_v

Overview

CS_RA_ADDR_INSTALL_RG_V is a reporting view shipped within the Oracle E-Business Suite Service (CS) module. Its name reflects its purpose: it joins party address, site use, customer, and lookup data to present a denormalized, report-ready address record. The suffix "RG" indicates it is associated with the Service module's report generation layer, historically tied to depot repair and field service address reporting. The ETRM metadata classifies the object as "Retrofitted," meaning it was carried forward from an earlier release lineage rather than newly designed in the 12.1.1 or 12.2.2 code lines. In both releases the view definition itself is unchanged, though the surrounding AR and RA table structures it consumes have evolved. Notably, the metadata states "Not implemented in this database," indicating the view is seeded as a scripted object but is not instantiated in every environment. Its role is confined to read-only reporting and integration extracts; no application logic, concurrent program, or form depends on it for transactional processing.

Underlying Base Objects

The view is defined over four documented base objects:

• RA_ADDRESSES (aliased A) — the party address repository, supplying ADDRESS1 through ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY, and CUSTOMER_ID.
• RA_SITE_USES (aliased SU) — site use assignments, supplying SITE_USE_ID, ADDRESS_ID, and the LOCATION column exposed as INSTALL_LOCATION.
• AR_LOOKUPS (aliased LU) — the lookup repository, supplying the MEANING column exposed as ADDRESS_USAGE from LOOKUP_TYPE = 'SITE_USE_CODE'.
• RA_CUSTOMERS (aliased CUST) — the customer registry, supplying CUSTOMER_NAME and CUSTOMER_NUMBER.

The joins are equi-joins on CUSTOMER_ID, ADDRESS_ID, and LOOKUP_CODE. Filters restrict output to active records: CUST.STATUS = 'A' and A.STATUS = 'A'. The ETRM metadata notes that no base objects are separately documented for the 12.2.2 representation, so the view text above is the authoritative structural reference.

Key Columns

• INSTALL_LOCATION — the site use location identifier, historically an installation or service site reference.
• SITE_USE_ID — unique identifier of the site use record; useful as a join key back to RA_SITE_USES.
• ADDRESS_USAGE — decoded site use meaning (for example, Bill-To, Ship-To, or Install-At).
• CUSTOMER_NAME / CUSTOMER_NUMBER — party identity attributes from RA_CUSTOMERS.
• ADDRESS_LINE_1 / ADDRESS_LINE_2 — concatenated address segments; each uses DECODE to suppress dangling delimiters when a component is null.
• CITY_STATE_ZIP — a SUBSTR-limited (1 to 240 characters) composite for label printing and single-line display.
• ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY — the untransformed discrete address attributes for sorting, filtering, or structured output.
• FULL_ADDRESS — the complete formatted address, also truncated at 240 characters.

Common Use Cases and Queries

Typical consumers are customer-facing address extracts, service site rosters, and integration feeds that require a flattened address string. A representative query filters by usage type:

SELECT CUSTOMER_NUMBER, CUSTOMER_NAME, ADDRESS_USAGE, FULL_ADDRESS FROM CS_RA_ADDR_INSTALL_RG_V WHERE ADDRESS_USAGE = 'Ship-To' ORDER BY CUSTOMER_NAME;

Because the view already enforces active-status filtering, callers should not re-apply status predicates against the base tables. Environments where the object is not implemented must substitute an equivalent ad hoc join or deploy the shipped script before use. The 240-character truncation on CITY_STATE_ZIP and FULL_ADDRESS should be considered when addresses may exceed that limit; the discrete columns remain available for full-fidelity output.