Results for “ship_to_customer_number”

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

Overview

AR_TRX_REP_ITF_V is a reporting interface view owned by the APPS schema in Oracle E-Business Suite Receivables. It exists to flatten the transaction reporting staging table, AR_TRANSACTIONS_REP_ITF, and to join it to the surrounding Receivables and Trading Community reference data required by standard AR reporting output. The view is not a transactional entity in its own right; it is a denormalized presentation layer that supplies descriptive attributes — customer names and numbers, site locations, transaction type and class, payment terms and methods, accounting flexfield descriptions, document sequencing, and reporting currency amounts — for rows staged in the interface table.

Its primary consumers are concurrent reporting programs and custom extracts that need transaction-level receivables data without reimplementing the same multi-way joins. Because bill-to and ship-to attributes are resolved here through HZ_PARTIES, HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL, the view eliminates the most common source of duplicated logic in AR reporting: party name resolution and phonetic key derivation for organization-type customers.

Underlying Base Objects

The documented base objects are AR_TRANSACTIONS_REP_ITF, RA_CUST_TRX_TYPES_ALL, RA_TERMS, AR_RECEIPT_METHODS, RA_BATCHES_ALL, RA_BATCH_SOURCES_ALL, FND_DOCUMENT_SEQUENCES, HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, and the ARPT_SQL_FUNC_UTIL utility package.

• AR_TRANSACTIONS_REP_ITF is the driving table, aliased RX in the view text. All ROWID, REQUEST_ID, audit columns, currency amounts and account fields originate here.
• RA_CUST_TRX_TYPES_ALL supplies TRX_TYPE, while ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING converts the type into the INV/CM transaction class.
• HZ_PARTIES, HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL resolve the bill-to and ship-to party, account number and site location.
• RA_TERMS, AR_RECEIPT_METHODS, FND_DOCUMENT_SEQUENCES, RA_BATCHES_ALL and RA_BATCH_SOURCES_ALL provide payment terms, payment method, document sequence and batch context.

All are referenced in the ETRM metadata as synonyms under APPS, consistent with the view being granted to reporting responsibility users rather than to the base schemas.

Key Columns

The columns most frequently referenced are described below.

• BILL_TO_CUSTOMER_NAME — SUBSTRB(BILL_TO_PARTY.PARTY_NAME, 1, 50). The 50-byte truncation is important: very long party names are silently truncated in the reporting extract.
• BILL_TO_CUSTOMER_NAME_PHONETIC — populated only where the bill-to party is of type ORGANIZATION; otherwise the DECODE returns NULL. It is intended for fuzzy name searching.
• BILL_TO_CUSTOMER_NUMBER and BILL_TO_CUSTOMER_SITE — the account number and site location from HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL.
• SHIP_TO_CUSTOMER_NAME, SHIP_TO_CUSTOMER_NUMBER, SHIP_TO_CUSTOMER_SITE — the parallel ship-to attributes, resolved independently of bill-to.
• TRX_NUMBER, TRX_DATE, TRX_DUE_DATE, TRX_CURRENCY, TRX_AMOUNT, TRX_ACCTD_AMOUNT, EXCHANGE_RATE, EXCHANGE_DATE and EXCHANGE_TYPE — the transaction header and amount context.
• TRX_CLASS and TRX_TYPE — derived and looked-up values for classification.
• PAYMENT_TERMS, PAYMENT_METHOD, DOC_SEQUENCE_NAME, DOC_SEQUENCE_VALUE, TAX_CALCULATION_LEVEL, RECEIVABLES_GL_DATE and REC_ACCOUNT with its description/balance columns — reporting enrichments.

Common Use Cases and Queries

The view is typically queried as part of the AR transaction reporting flow, or directly for ad hoc extracts. A typical requirement is locating all staged transactions for a specific customer by bill-to name:

SELECT TRX_NUMBER, TRX_DATE, TRX_CLASS, TRX_TYPE,
       BILL_TO_CUSTOMER_NAME, BILL_TO_CUSTOMER_NUMBER,
       SHIP_TO_CUSTOMER_NAME, TRX_CURRENCY, TRX_AMOUNT
FROM   APPS.AR_TRX_REP_ITF_V
WHERE  BILL_TO_CUSTOMER_NAME LIKE 'ACME%'
AND    TRX_DATE BETWEEN :p_from_date AND :p_to_date;

Because ROW_ID and REQUEST_ID are exposed, the view also supports drill-down or reconciliation between a report request and its staged rows, and it can be joined back to AR_TRANSACTIONS_REP_ITF for additional attributes not surfaced in this view. When filtering on customer names, note that only the first 50 bytes are available and that phonetic matching is restricted to organization parties.