Results for “payment_name”

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

Overview

AR_CUSTOMER_ALT_NAMES_V is a vital reporting and integration view within the Oracle E-Business Suite (EBS) Receivables (AR) module, specifically designed to manage alternate customer names used for lockbox name matching. In Oracle EBS 12.1.1 and 12.2.2, the lockbox process automatically applies receipts to customer accounts based on data transmitted by banks. However, banks often transmit customer names that differ from the standard legal entity names stored in the core HZ_PARTIES table. This view provides the necessary bridge, exposing alternate names, or aliases, that the system can use to correctly identify and match customers during the lockbox import process. For technical consultants and developers, this view is critical for troubleshooting lockbox failures, auditing alternate name configurations, and building custom reporting on customer aliases and their associated payment terms, ensuring accurate cash application and reducing manual intervention.

Underlying Base Objects

This view is constructed over several key base objects in the APPS schema, primarily joining the AR_CUSTOMER_ALT_NAMES table with master data from the Trading Community Architecture (TCA) and Receivables setup tables. The primary table is AR_CUSTOMER_ALT_NAMES (AL), which stores the actual alternate name strings. This is joined to HZ_CUST_ACCOUNTS (CUST_ACCT) to link the alternate name to a specific customer account, and then to HZ_PARTIES (PARTY) to retrieve the main party name and phonetic organization name. The view also employs outer joins to HZ_CUST_SITE_USES_ALL (RS) to associate the alternate name with a specific bill-to site use, and to RA_TERMS (RT) to capture payment term information. This structure allows the view to present a comprehensive picture of a customer's alternate name in the context of their account, site, and payment terms.

Key Columns

The view exposes a range of columns essential for identification and reporting. The most direct column is ALT_NAME, which holds the alternate name string. This is tied to ALT_NAME_ID, the primary key of the underlying record. Customer identification is provided through CUST_ACCOUNT_ID, ACCOUNT_NUMBER, and CUSTOMER_NAME, linking the alias to a specific account. Notably, the PAYMENT_NAME column is a critical field, likely derived from the customer's primary name or account name, used in payment matching logic. The phonetic representation of an organization's name is exposed as CUSTOMER_NAME_PHONETIC, which aids in matching names that sound similar but are spelled differently. Site-specific data is available via SITE_USE_ID and BILL_TO_LOCATION, while payment terms are represented by TERM_ID and the term name from RA_TERMS. Standard audit columns (CREATED_BY, CREATION_DATE, etc.) and ORG_ID for multi-org filtering are also included.

Common Use Cases and Queries

Technical consultants frequently query this view to diagnose lockbox issues where receipts are unapplied due to name mismatches. It is also used to generate reports of all configured alternate names for data governance. A common query retrieves all alternate names for a specific customer account:

• SELECT alt_name, customer_name, payment_name, bill_to_location FROM ar_customer_alt_names_v WHERE account_number = '12345';

To identify which alternate names are associated with a specific payment term for a multi-org setup, a query such as the following is used:

• SELECT alt_name, customer_name, term_id FROM ar_customer_alt_names_v WHERE org_id = 101 AND term_id IS NOT NULL;

Developers building custom lockbox interfaces may use the view to validate incoming names against the ALT_NAME and CUSTOMER_NAME_PHONETIC columns to improve hit rates. Furthermore, a query can list all aliases that lack an associated site use, which might indicate incomplete configuration:

• SELECT alt_name, customer_name FROM ar_customer_alt_names_v WHERE site_use_id IS NULL;