Results for “cln_rn_util_from_role_v”

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

Overview

The CLN_RN_UTIL_FROM_ROLE_V view is a utility database object owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the CLN product family, officially designated as the Supply Chain Trading Connector for RosettaNet. As its name implies, this view is not intended for general-purpose reporting, but rather serves as a specialized helper for RosettaNet integration processing. Specifically, its documented purpose is to retrieve "From Role" information for outbound RosettaNet XML Gateway Messages (XGMs). In RosettaNet Business-to-Business (B2B) transactions, the "From Role" identifies the sending partner's organizational identity, which typically includes the trading partner's name, location code, and contact details necessary to populate the header and routing segments of an outbound PIP (Partner Interface Process) document. Because this view normalizes data from HR and general ledger-adjacent location tables, it allows the RosettaNet connector to construct a consistent partner profile without requiring the integration user to directly join multiple HR tables.

Underlying Base Objects

The view is defined over two primary underlying objects, as documented in the ETRM metadata. The first is HR_ALL_ORGANIZATION_UNITS_VL, which is a base view in the Human Resources module that stores the valid, translated organization definitions, including the organization name and its associated location ID. The second object is HR_LOCATIONS_ALL, which contains address and telecommunications details for physical locations. The join condition explicitly links these two objects on the LOCATION_ID column, ensuring that the organizational unit is paired with its correct physical address and phone information. A critical implementation detail is that CLN_RN_UTIL_FROM_ROLE_V references HR_ALL_ORGANIZATION_UNITS_VL directly, making it a dependent object in the HR schema hierarchy. In the context of the user's search for "hr_all_organization_units_vl," this view demonstrates a common integration pattern where the HR organization view is joined to a location table to produce a flattened, integration-ready dataset. The view acts as a bridge, abstracting the complexity of the HR data model into a single row representing the "From" party for a transaction.

Key Columns

The view exposes six columns, each mapped from its source objects. ORGANIZATION_ID is sourced from HR_ALL_ORGANIZATION_UNITS_VL and uniquely identifies the sending organization within the EBS instance. NAME, also from the organization view, is the translated organization name used as the partner identifier. The CONTACT_NAME column is interestingly hardcoded as NULL in the view definition, meaning the display name of the partner is not derived from a person record but relies solely on the organization name. The CONTACT_TELEPHONE and CONTACT_FAX columns are populated from LOC.TELEPHONE_NUMBER_1 and LOC.TELEPHONE_NUMBER_2 respectively, providing the voice and fax contact numbers for the partner location. The final column, EDI_LOCATION_CODE, maps to LOC.ECE_TP_LOCATION_CODE, which is the critical EDI/XML location identifier used by the RosettaNet gateway to route the outbound message to the correct trading partner endpoint. Notably, the column list in the metadata includes ORG_ID, CONTACT_EMAIL, and CONTACT_FAX, which correspond to the aliased output columns expected by the RosettaNet mapping utility, even though the view text reveals CONTACT_NAME is null and CONTACT_EMAIL may be mapped elsewhere or null depending on the actual runtime definition.

Common Use Cases and Queries

This view is primarily queried by the RosettaNet outbound processing logic to determine the sender details when generating an XML message. A developer or integration consultant might query this view directly to validate the partner setup or to troubleshoot why a specific outbound transaction is failing due to an invalid location code. For example, the following query retrieves the From Role information for a specific organization:

• SELECT organization_id, name, edi_location_code FROM apps.cln_rn_util_from_role_v WHERE organization_id = 204;
• SELECT name, contact_telephone, edi_location_code FROM apps.cln_rn_util_from_role_v WHERE edi_location_code IS NOT NULL;

Because the view conflates the organization name with the location telephone numbers, it is useful for generating a quick partner profile report. However, since CONTACT_NAME is hardcoded as NULL, any use case requiring a specific contact person's name must be handled by a custom query against HR_LOCATIONS_ALL or HR_ALL_ORGANIZATION_UNITS_VL rather than relying on this utility view. In summary, CLN_RN_UTIL_FROM_ROLE_V is a targeted, RosettaNet-specific helper that flattens HR organization and location data for the outbound XML gateway.