Results for “edi_location_code”

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

Overview

The APPS.CLN_RN_UTIL_TO_ROLE_CUSTOMER_V view is a database object within the Oracle E-Business Suite (EBS) Supply Chain Trading Connector for RosettaNet (CLN) module. Its documented purpose is to retrieve "To Role Customer" information for RosettaNet outbound XGMs (eXtensible Markup Language Gateway messages). In RosettaNet B2B integration, outbound business documents require identification of the receiving trading partner ("To Role") and its associated party and location context. This view serves as a utility lookup that consolidates customer party, party site, and EDI location code data into a single row-per-party-site structure, enabling the trading connector to populate outbound message headers and partner identification segments accurately.

The object is owned by the APPS schema and holds a status of VALID in the documented environment. It exists as a read-only view intended for internal use by the RosettaNet processing logic, but it is also queryable for diagnostic and reporting purposes.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS-owned synonyms into the Oracle Trading Community Architecture (TCA) or "HZ" schema:

• HZ_CUST_ACCT_SITES_ALL — the customer account site table, aliased as HCAS. It supplies the EDI location code used for partner identification.
• HZ_PARTY_SITES — the party site table, aliased as HPS. It links a party to a physical or logical site and provides the PARTY_SITE_ID.
• HZ_PARTIES — the master party table, aliased as HP. It provides the PARTY_ID and PARTY_NAME.

The joins are driven by HP.PARTY_ID = HPS.PARTY_ID and HCAS.PARTY_SITE_ID = HPS.PARTY_SITE_ID. This effectively returns one row per customer account site, enriched with the owning party's name and identifier. The view does not filter on account status or site status, so callers must apply their own selection criteria.

Key Columns

The documented column list defines seven output columns:

• TP_ID — maps to HP.PARTY_ID, the unique trading partner (party) identifier.
• TP_SITE_ID — maps to HPS.PARTY_SITE_ID, the site identifier for the party.
• CONTACT_NAME, CONTACT_EMAIL, CONTACT_TELEPHONE, CONTACT_FAX — these are defined as NULL placeholders in the view text. They reserve positional slots for contact information that is not sourced through this view, indicating the columns exist for interface compatibility rather than data delivery.
• EDI_LOCATION_CODE — maps to HCAS.ECE_TP_LOCATION_CODE, the trading partner location code used in RosettaNet and EDI partner identification.

Common Use Cases and Queries

Typical usage includes diagnosing which customer site maps to a given RosettaNet partner, verifying that EDI location codes are populated before an outbound message is generated, and validating party-to-site relationships for trading partner setup. A representative query confirming the columns and lookup behavior follows:

• SELECT TP_ID, TP_SITE_ID, PARTY_NAME, EDI_LOCATION_CODE FROM APPS.CLN_RN_UTIL_TO_ROLE_CUSTOMER_V WHERE EDI_LOCATION_CODE = :location_code;
• SELECT TP_ID, TP_SITE_ID, PARTY_NAME FROM APPS.CLN_RN_UTIL_TO_ROLE_CUSTOMER_V WHERE PARTY_NAME LIKE :partner_name;

Because the view exposes no contact data, it should not be used where contact-level detail is required; those columns will always return NULL.