Search Results remit_batch_media_reference

Overview

The AR_REMITTED_RECEIPTS_FORMAT_V view is an Oracle Receivables (AR) reporting object owned by the APPS schema. As its description states, it "holds general information of remitted receipts being formatted for reporting purpose." In practical terms, the view assembles the data elements required to render a remittance or deposit report — the receipt header, customer identity, receipt method, remittance bank, and batch information — into a single denormalized result set. It is a reporting convenience view rather than a transactional entity; it exposes no columns that are not already derivable from its base tables.

The view is relevant in both Oracle EBS 12.1.1 and 12.2.2. In 12.2.2 the object remains VALID and is defined over the multi-org and subledger accounting infrastructure (MO_GLOBAL, XTR_USER_ACCESS, FND_GLOBAL), meaning its results are subject to the standard operating unit and security context established at runtime. Reports and concurrent programs that consume this view therefore rely on the caller's FND_GLOBAL session context being correctly initialized.

Underlying Base Objects

The view joins a substantial set of AR and shared Receivables/IBY objects. The principal base objects, as documented in ETRM 12.2.2, include:

• AR_CASH_RECEIPTS — the primary receipt record, supplying receipt number, currency, amount, factor discount, receipt and deposit dates, exchange rate, customer receipt reference, and the remit bank account use identifier.
• AR_RECEIPT_METHODS — supplies the receipt method, printed name, and payment channel code.
• AR_CASH_RECEIPT_HISTORY (aliased twice as CRH and CRHPRV) — used to constrain the receipt history state and provide prior-state logic.
• AR_PAYMENT_SCHEDULES, AR_BATCHES, and AR_LOOKUPS (twice, for the YES/NO and batch media lookups) — provide due dates, batch identity/date/media reference, and lookup meanings.
• HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_SITE_USES — supply the customer name, account number, and site location.
• IBY_TRXN_EXTENSIONS_V — resolves instrument type to a customer bank account number or credit card number.
• CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES, CE_BANK_BRANCHES_V (twice) — provide remittance bank, branch, and account details.
• FND_GLOBAL, FND_PROFILE, FND_ACCESS_CONTROL_UTIL, MO_GLOBAL, XTR_USER_ACCESS, and IBY_FNDCPT_TRXN_PUB — supporting packages for org context, access control, and payment instrument resolution.

Several columns (CUSTOMER_BANK_NAME, CUSTOMER_BANK_BRANCH_NAME, CUSTOMER_BANK_BRANCH_NUMBER, CUSTOMER_BANK_ACCOUNT_NAME, CUSTOMER_BANK_ACCOUNT_ID) are explicitly defined as NULL placeholders so that downstream report layouts can reference a consistent column structure.

Key Columns

• RECEIPT_NUMBER, CURRENCY_CODE, AMOUNT, FACTOR_DISCOUNT_AMOUNT — core receipt identification and value.
• RECEIPT_DATE, DEPOSIT_DATE, DUE_DATE — the due date uses NVL(PS.DUE_DATE, CR.DEPOSIT_DATE) to guarantee a non-null reporting value.
• PRINTED_NAME, MEANING (receipt method), PAYMENT_CHANNEL_CODE — receipt method attributes.
• PARTY_NAME, ACCOUNT_NUMBER, LOCATION — customer identity; PARTY_NAME is truncated with SUBSTRB(...,1,50).
• CUSTOMER_BANK_ACCOUNT_NUMBER — decoded from IBY.INSTRUMENT_TYPE (BANKACCOUNT → ACCOUNT_NUMBER, CREDITCARD → CARD_NUMBER).
• REMIT_BANK_NAME, REMIT_BANK_BRANCH_NAME, REMIT_BANK_BRANCH_NUMBER, REMIT_BANK_ACCOUNT_NAME, REMIT_BANK_ACCOUNT_NUMBER — the remittance bank details.
• BATCH_NAME (B.NAME), BATCH_DATE, BATCH_ID, MEDIA_REFERENCE — remittance batch context.
• CASH_RECEIPT_ID, CUST_ACCOUNT_ID, REMIT_BANK_ACCOUNT_ID, PAYMENT_TRXN_EXTENSION_ID — primary and foreign keys for drill-down or linkage.

Common Use Cases and Queries

Typical consumers are custom remittance reports, reconciliation extracts, and integration feeds requiring receipt-to-customer-to-bank relationships in one row. Because the view applies batch-level factor logic (REMIT_METHOD_CODE = 'FACTORING' drives the YES/NO lookup branch), it is suited to factoring and standard remittance reporting alike.

A simple filtered query:

• SELECT RECEIPT_NUMBER, CURRENCY_CODE, AMOUNT, RECEIPT_DATE, REMIT_BANK_NAME, REMIT_BANK_ACCOUNT_NUMBER, BATCH_NAME, BATCH_DATE FROM AR_REMITTED_RECEIPTS_FORMAT_V WHERE RECEIPT_DATE BETWEEN :p_from AND :p_to;
• SELECT CUST_ACCOUNT_ID, PARTY_NAME, ACCOUNT_NUMBER, SUM(AMOUNT) FROM AR_REMITTED_RECEIPTS_FORMAT_V GROUP BY CUST_ACCOUNT_ID, PARTY_NAME, ACCOUNT_NUMBER;
• SELECT CASH_RECEIPT_ID, RECEIPT_NUMBER, BATCH_ID, PAYMENT_CHANNEL_CODE FROM AR_REMITTED_RECEIPTS_FORMAT_V WHERE BATCH_ID = :p_batch_id;

Reports should always initialize the operating unit context (via FND_GLOBAL / MO_GLOBAL) before querying, and should not assume the NULL placeholder customer bank columns carry data.