Results for “cln_procat_customer_v”

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

Overview

CLN_PROCAT_CUSTOMER_V is an Oracle E-Business Suite (EBS) seeded view owned by the APPS schema and registered as VALID in ETRM for both 12.1.1 and 12.2.2. It belongs to the CLN — Supply Chain Trading Connector for RosettaNet product, the module that implements RosettaNet Partner Interface Processes (PIPs) between trading partners. The documented purpose of the view is to expose "the recipient of the price list." It resolves the customer/partner identity associated with the outbound RosettaNet price catalogue (PRCAT) process, returning the party name, party identifier, party site identifier, and the external partner index value that is transmitted in RosettaNet XML messages. Because the view abstracts a multi-table join across ECX and HZ entities, it is used by trading-connector logic and by reporting or troubleshooting queries that need to determine, for a given outbound price-list sync, which customer receives the document.

Underlying Base Objects

ETRM documents the following referenced base objects (resolved through synonyms in APPS):

• ECX_TRANSACTIONS — the EDI/XML transaction header that records the transaction type (CLN) and subtype (SYNCCTLGO).
• ECX_EXT_PROCESSES — the external process record linking each transaction to its processing definition; the view restricts to DIRECTION = 'OUT'.
• ECX_TP_HEADERS — trading partner header, supplying TP_HEADER_ID and PARTY_ID for the partner.
• ECX_TP_DETAILS — trading partner detail lines, supplying PARTY_SITE_ID and EXTERNAL_TP_LOCATION_CODE (the partner index).
• HZ_PARTIES — the Trading Community Architecture party master, supplying PARTY_NAME.

The view text joins ECX_TP_HEADERS to ECX_TP_DETAILS on TP_HEADER_ID, to HZ_PARTIES on PARTY_ID, and to ECX_EXT_PROCESSES on EXT_PROCESS_ID; ECX_EXT_PROCESSES is further linked to ECX_TRANSACTIONS on TRANSACTION_ID. The predicate restricts results to RosettaNet CLN price-list-control outbound transactions.

Key Columns

• PARTY_NAME — the trading partner name from HZ_PARTIES, identifying the recipient of the price list.
• PARTY_ID — the internal TCA party identifier of the recipient.
• PARTY_SITE_ID — the party site identifier from ECX_TP_DETAILS, pinpointing the specific partner location.
• CUSTOMER_PARTNRIDX — the external partner location code (EXTERNAL_TP_LOCATION_CODE), the value exchanged in the RosettaNet message that identifies the customer trading partner.

Common Use Cases and Queries

The view is typically queried to confirm which customer is associated with outbound CLN price-list processing, to validate partner configuration, or to reconcile the partner index transmitted against TCA setup. A representative query:

• SELECT party_name, party_id, party_site_id, customer_partnridx FROM apps.cln_procat_customer_v;
• Joining the view to ECX_TRANSACTIONS to correlate the recipient with a specific transaction identifier.
• Filtering by CUSTOMER_PARTNRIDX to verify a partner's external location code against expected RosettaNet configuration.

Because ECX_TRANSACTIONS underpins the view, queries originating from a search on "ecx_transactions" should be aware that the view only returns transactions meeting the CLN/SYNCCTLGO/OUT criteria; other transaction types must be queried directly against the base tables.