Results for “addr1_addr2”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_RA_ADDR_LOC_RG_V is a Service (CS) module reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that consolidates customer product locations drawn from the Receivables address and site-use foundation. The view exposes active customer addresses together with their associated site-use codes and translated usage meanings, producing a flattened, query-friendly record set for reporting and integration purposes. In the context of a search for "service now curr location," this object is relevant because it represents the canonical list of a customer's active installed-at or ship-to locations that a service application (for example, a field service or support ticketing system synchronized with Service) would resolve to the "current location" for a customer product.

Rather than requiring a caller to join RA_ADDRESSES, RA_SITE_USES, AR_LOOKUPS, and RA_CUSTOMERS manually, the view pre-joins these objects and restricts rows to active records only. The ETRM metadata notes that the view is "Not implemented in this database," meaning the definition is documented but the object itself is not deployed in the reference instance queried; the SQL text and column list remain authoritative for environments where it is present.

Underlying Base Objects

The view text references four base objects in the Oracle Receivables schema hierarchy:

• RA_ADDRESSES (aliased A) — supplies street address components and links to the customer via CUSTOMER_ID.
• RA_SITE_USES (aliased SU) — supplies the site-use (usage) information and the ADDRESS_ID and SITE_USE_ID keys.
• AR_LOOKUPS (aliased LU) — resolves the SITE_USE_CODE to a user-friendly MEANING under LOOKUP_TYPE = 'SITE_USE_CODE'.
• RA_CUSTOMERS (aliased CUST) — supplies the customer name and number and links to the address via CUSTOMER_ID.

The join conditions require RA_CUSTOMERS.CUSTOMER_ID = RA_ADDRESSES.CUSTOMER_ID, RA_SITE_USES.ADDRESS_ID = RA_ADDRESSES.ADDRESS_ID, and RA_SITE_USES.SITE_USE_CODE = AR_LOOKUPS.LOOKUP_CODE. The ETRM metadata lists no separate referenced base objects beyond these. All three principal entities are filtered to STATUS = 'A' (active), so only active customers, active addresses, and active site uses are returned.

Key Columns

• LOCATION — sourced from RA_SITE_USES.LOCATION; the location identifier used in Receivables and referenced by downstream service processes.
• SITE_USE_ID — the unique key of the site use, commonly used as the foreign key in service transaction tables.
• SITE_USE_CODE / USAGE — the raw code and its AR_LOOKUPS meaning (for example, SHIP_TO, BILL_TO, INSTALL_AT).
• CUSTOMER, CUSTOMER_NUMBER, CUSTOMER_ID — customer name, account number, and surrogate key from RA_CUSTOMERS.
• ADDRESS_ID — the Receivables address key.
• ADDR1_ADDR2, ADDR3_ADDR4 — concatenated address lines for single-field display.
• CITY_STATE_CODE_CTRY — a SUBSTR-truncated (240 characters) composite of city, state, postal code, and country, suitable for address blocks on reports.
• ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY — individual address attributes for structured output.

Common Use Cases and Queries

The view is typically used to list active locations for a customer or to resolve the correct site-use for a service subscription. A representative query filters by customer and usage:

• List all active ship-to locations for a given customer number.
• Resolve the current service/install location for a customer product record.
• Populate a location picker in an external service management system.

SELECT LOCATION, SITE_USE_ID, USAGE, CUSTOMER_NUMBER,
       CITY_STATE_CODE_CTRY
FROM   CS_RA_ADDR_LOC_RG_V
WHERE  CUSTOMER_NUMBER = :customer_number
AND    SITE_USE_CODE IN ('SHIP_TO','INSTALL_AT');

Because the view already restricts to active statuses and strips inactive lookups, it is safe to use in integration extracts without additional status predicates, though callers should still scope queries by CUSTOMER_ID or SITE_USE_ID for performance.