Search Results bill_to_ship_from

Overview

APPS.RLM_CUM_SITE_USES_V is a reporting and integration view in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that exposes customer site uses associated with cumulative (CUM) shipping and receiving terms for a given operating unit. The view is defined within the Oracle Receiving / Logistics Management (RLM) schema family, and its defining characteristic is the join to RLM_CUST_SHIPTO_TERMS, which anchors each returned site use to a CUM organization level code. Specifically, the view filters RLM_CUST_SHIPTO_TERMS records to three organization level codes: SHIP_TO_SHIP_FROM, BILL_TO_SHIP_FROM, and DELIVER_TO_SHIP_FROM. This makes the view particularly relevant to processes that depend on CUM management — such as consigned inventory, ship-from/deliver-to trading relationships, and procurement or receiving transactions that must resolve the correct ship-from and deliver-to address pairing. The view joins Trading Community Architecture (TCA) entities to customer site uses, producing a denormalized record that combines address location attributes with the lookup meaning for the site use code.

Underlying Base Objects

The view is defined over six referenced base objects:

• RLM_CUST_SHIPTO_TERMS (synonym) — the driving table, holding CUM organization level codes keyed by ADDRESS_ID and ORG_ID.
• AR_LOOKUPS (view) — supplies the SITE_USE_MEANING for each site use code where LOOKUP_TYPE = 'SITE_USE_CODE'.
• HZ_PARTY_SITES (synonym) — TCA party site records linking a party to a location.
• HZ_LOCATIONS (synonym) — address/location details such as CITY and STATE.
• HZ_CUST_ACCT_SITES_ALL (synonym) — customer account site associations, providing CUST_ACCOUNT_ID and CUST_ACCT_SITE_ID.
• HZ_CUST_SITE_USES_ALL (synonym) — the customer site use records, filtered to STATUS = 'A' (active).

Joins are enforced so that terms.ADDRESS_ID equals ACCT_SITE.CUST_ACCT_SITE_ID, ACCT_SITE.PARTY_SITE_ID equals PARTY_SITE.PARTY_SITE_ID, LOC.LOCATION_ID equals PARTY_SITE.LOCATION_ID, ACCT_SITE.CUST_ACCT_SITE_ID equals CUST_SITE.CUST_ACCT_SITE_ID, and that ORG_ID is consistent across TERMS, ACCT_SITE, and CUST_SITE. This ORG_ID consistency ensures all returned rows are scoped to a single operating unit.

Key Columns

• ROW_ID — the ROWID of the underlying customer site use record, usable as a unique identifier.
• SITE_USE_ID — primary identifier of the customer site use.
• CUST_ACCOUNT_ID / CUST_ACCT_SITE_ID — customer account and account site identifiers from HZ_CUST_ACCT_SITES_ALL.
• LOCATION, CITY, STATE — address attributes derived from HZ_CUST_SITE_USES_ALL.LOCATION and HZ_LOCATIONS.
• SITE_USE_CODE / SITE_USE_MEANING — the site use code and its decoded meaning (e.g., Ship-To, Bill-To, Deliver-To).
• CUM_ORG_LEVEL_CODE — the CUM organization level qualifier (SHIP_TO_SHIP_FROM, BILL_TO_SHIP_FROM, or DELIVER_TO_SHIP_FROM).
• ORG_ID — the operating unit that scopes the record.

Common Use Cases and Queries

A frequent requirement is retrieving the ship-from site associated with a deliver-to relationship, which explains the common search term “deliver_to_ship_from.” The view supports this by exposing records where CUM_ORG_LEVEL_CODE = 'DELIVER_TO_SHIP_FROM'.

• List all active CUM site uses for an operating unit:

SELECT cust_account_id, site_use_code, site_use_meaning, city, state, cum_org_level_code FROM apps.rlm_cum_site_uses_v WHERE org_id = :p_org_id;

• Isolate deliver-to / ship-from relationships:

SELECT site_use_id, cust_acct_site_id, city, state FROM apps.rlm_cum_site_uses_v WHERE cum_org_level_code = 'DELIVER_TO_SHIP_FROM' AND org_id = :p_org_id;

Because the view filters to active site uses and performs the lookup decoding internally, it is well suited for address validation reports, receiving configuration inquiries, and integration extracts that must resolve CUM ship-from and deliver-to designations without manually joining TCA and lookup tables.