Results for “bill_to_customer_name”

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

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:

• AR_DOCUMENT_TRANSFERS — the driver for outbound RosettaNet document generation; provides DOCUMENT_TRANSFER_ID.
• RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_TYPES_ALL, RA_SALESREPS_ALL, AR_RECEIPT_METHODS — the Receivables invoice header, lines, transaction type, primary salesrep, and receipt method.
• HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL — the operating unit and its supplier/seller organisation and location details.
• HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES — TCA customer account, account site, site use (restricted to SITE_USE_CODE = 'BILL_TO'), and party name.

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:

• DOCUMENT_TRANSFER_ID — identifier of the outbound transfer record.
• CUSTOMER_TRX_ID — the AR invoice header identifier.
• AMOUNT — a scalar subquery returning SUM(EXTENDED_AMOUNT) from RA_CUSTOMER_TRX_LINES_ALL for the invoice.
• CURRENCY_CODE, TRX_DATE, TRX_NUMBER, TERM_ID — invoice currency, transaction date, transaction number and payment term.
• PO_NUMBER — the purchase order on the invoice, defaulted to 'N/AA' when null.
• DOCUMENT_TYPE and PAYMENT_METHOD — derived from RA_CUST_TRX_TYPES_ALL.TYPE and AR_RECEIPT_METHODS.PAYMENT_TYPE_CODE.
• SUPPLIER_NAME and SUPPLIER_CODE — the operating unit name and the ECE_TP_LOCATION_CODE of the supplier location.
• SALESREP, SALESREP_EMAIL — the primary salesrep's name and e-mail address.
• REFERENCE_NUMBER — concatenation of DOCUMENT_TRANSFER_ID and CUSTOMER_TRX_ID.
• BILL_TO_LOCATION_CODE — the field the user searched for; sourced from HZ_CUST_ACCT_SITES_ALL.ECE_TP_LOCATION_CODE, obtained through the BILL_TO site use (CSU.SITE_USE_ID = H.BILL_TO_SITE_USE_ID, CSU.SITE_USE_CODE = 'BILL_TO').
• CUSTOMER_NAME — party name from HZ_PARTIES.
• ORG_ID — the operating unit identifier carried through for multi-org security.

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.