Results for “ar_br_assignments_v”

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

Overview

AR_BR_ASSIGNMENTS_V is an APPS-owned, VALID view in the Oracle E-Business Suite Receivables (AR) module. It exposes the relationship between a customer transaction line and a reference customer transaction line created through the Bills Receivable (BR) assignment process, enriching that relationship with transaction, payment schedule, customer, transaction type, receipt method, site, consolidated billing, and descriptive flexfield (DFF) context. The view is used primarily for reporting and integration scenarios where the assignment of an invoice line to a Bills Receivable document must be examined together with its originating customer, transaction type, and payment terms.

Because the underlying data spans transactional tables such as RA_CUSTOMER_TRX_LINES and RA_CUSTOMER_TRX, as well as reference and lookup data held in HZ_PARTIES, HZ_CUST_ACCOUNTS, and AR_LOOKUPS, AR_BR_ASSIGNMENTS_V provides a denormalized, report-ready projection. Its design supports BI Publisher reports, custom concurrent programs, and downstream integrations that need a single query surface rather than multiple joins across AR and HZ.

Underlying Base Objects

The ETRM 12.2.2 documentation lists the following referenced base objects: AR_CONS_INV_ALL, AR_LOOKUPS, AR_PAYMENT_SCHEDULES, AR_RECEIPT_METHODS, FND_GLOBAL, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES, IBY_FNDCPT_TRXN_PUB, IBY_TRXN_EXTENSIONS_V, RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, and RA_CUST_TRX_TYPES.

The core driving object is RA_CUSTOMER_TRX_LINES (aliased LINES), which supplies the assignment row identity, the transaction line ID, the customer transaction ID, the BR reference transaction and payment schedule IDs, and the extended amounts in both entered and accounted currency. RA_CUSTOMER_TRX (TRX) contributes the transaction number, document sequence value, transaction date, comments, purchase order, and bill-to site use. AR_PAYMENT_SCHEDULES (PAYS) provides currency, original and remaining amounts due, accounted remaining amount, due date, exchange rate, terms sequence, and the consolidated invoice ID.

Customer context is drawn from HZ_PARTIES (PARTY) and HZ_CUST_ACCOUNTS (CUST_ACCT), which supply the party name, fiscal code, account number, customer class, and category code. AR_LOOKUPS is joined twice: once for the CUSTOMER_CATEGORY lookup type and once for INV/CM, mapping codes to their descriptive meanings. RA_CUST_TRX_TYPES provides the transaction type name, type, and lookup meaning, while AR_RECEIPT_METHODS supplies the receipt method name and ID. AR_CONS_INV_ALL and the IBY objects complete the join set for consolidated billing and payment extension data. Note the outer-join hint on the CUSTOMER_CATEGORY lookup, which preserves rows even when no lookup meaning exists for the party category code.

Key Columns

• Assignment identifiers: CUSTOMER_TRX_LINE_ID, CUSTOMER_TRX_ID, BR_REF_CUSTOMER_TRX_ID, BR_REF_PAYMENT_SCHEDULE_ID — link the invoice line to its Bills Receivable reference.
• Amounts: EXTENDED_AMOUNT and EXTENDED_ACCTD_AMOUNT on the line; AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, and ACCTD_AMOUNT_DUE_REMAINING on the schedule.
• Transaction context: TRX_NUMBER, DOC_SEQUENCE_VALUE, TRX_DATE, COMMENTS, PURCHASE_ORDER.
• Customer context: PARTY_NAME (substr 50), JGZZ_FISCAL_CODE, ACCOUNT_NUMBER, CUSTOMER_CLASS_CODE, CATEGORY_CODE, plus the CUSTOMER_CATEGORY lookup MEANING that answers the common search term "customer_category".
• Type and method: transaction type NAME, TYPE, and INV/CM lookup MEANING; receipt method NAME and RECEIPT_METHOD_ID.
• Billing and DFF: CONS_BILLING_NUMBER, CONS_INV_ID, and ATTRIBUTE_CATEGORY through ATTRIBUTE15.

Common Use Cases and Queries

Typical uses include reconciling BR assignments to their source invoices, reporting amounts due and remaining by customer category, and feeding downstream integrations the assignment lineage with DFF context.

Selecting assignment details filtered by customer category:

• SELECT customer_trx_id, trx_number, account_number, party_name, meaning, extended_amount FROM ar_br_assignments_v WHERE meaning = '&category';
• SELECT trx_number, trx_date, amount_due_remaining, due_date, receipt_method_id FROM ar_br_assignments_v WHERE customer_trx_line_id = :line_id;
• SELECT br_ref_customer_trx_id, br_ref_payment_schedule_id, attribute1, attribute2 FROM ar_br_assignments_v WHERE cons_inv_id IS NOT NULL;