Search Results salesrep_email




Overview
Explore in AI Chat

Overview

The CLN_3C3_INVOICE_V view is an APPS-owned database object within the Oracle E-Business Suite, belonging to the CLN product family — Supply Chain Trading Connector for RosettaNet. Its documented purpose is to present a consolidated, integration-ready projection of accounts receivable invoice data used to generate the outbound 3C3 (Invoice Notification) RosettaNet business message. The view flattens and joins data from Receivables, Human Resources, and Trading Community Architecture (TCA) tables into a single row per invoice document transfer, so that the RosettaNet connector can emit a fully populated 3C3 payload without executing the join and aggregation logic at runtime.

Because the view is validated and exposed in the APPS schema in both EBS 12.1.1 and 12.2.2, it can be queried directly by integration code, concurrent programs, and reporting tools. A user searching for bill_to_location_code will usually be investigating how the outbound 3C3 interface derives the buyer/ship-to location identifier for a RosettaNet trading partner.

Underlying Base Objects

The view is defined over a set of synonym-modelled base objects spanning three modules:

Joins are keyed on CUSTOMER_TRX_ID (between the transfer record and the invoice header) and on ORG_ID throughout, ensuring all lookups are restricted to the invoice's operating unit. Outer joins (+) are applied to AR_RECEIPT_METHODS, HR_LOCATIONS_ALL and RA_SALESREPS_ALL so that invoices lacking a receipt method, location or salesrep are still returned.

Key Columns

The view exposes the following principal attributes:

Common Use Cases and Queries

Typical usage centres on confirming the outbound payload content and troubleshooting missing or incorrect location codes for RosettaNet trading partners. The query below lists invoices flagged for 3C3 generation together with their bill-to location codes:

  • SELECT trx_number, customer_name, bill_to_location_code, currency_code, amount FROM apps.cln_3c3_invoice_v WHERE org_id = :org_id;
  • SELECT trx_number, supplier_code, bill_to_location_code FROM apps.cln_3c3_invoice_v WHERE document_transfer_id = :transfer_id; — inspect a single transfer record.
  • SELECT COUNT(*) FROM apps.cln_3c3_invoice_v WHERE bill_to_location_code IS NULL; — detect invoices whose bill-to site has no ECE trading partner location code assigned.

Because BILL_TO_LOCATION_CODE originates in HZ_CUST_ACCT_SITES_ALL.ECE_TP_LOCATION_CODE, a null result generally indicates the account site has not been configured with a trading partner location code, which must be corrected in TCA before the 3C3 message can be successfully generated.