Results for “application_status”

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

Overview

AR_INTERIM_CR_LINES_V is an Oracle E-Business Suite Receivables (AR) view owned by the APPS schema. Its name and definition indicate that it exposes the line-level detail of interim cash receipts — the temporary receipt records held in the AR_INTERIM_CASH_RECEIPTS and AR_INTERIM_CASH_RECEIPT_LINES tables prior to posting through the Receivables posting and AutoAccounting process. ETRM documents the object specifically as "(Release 115 Only)," meaning it is a legacy construct whose lineage traces back to Release 11.5 and which remains valid in the 12.1.1 and 12.2.2 application schemas largely for backward compatibility.

The view joins header-level interim receipt attributes (amount, receipt date, currency, receipt method, GL date, status) to their associated lines (payment amount, discount taken, due date, payment schedule, transaction reference). It also denormalizes descriptive context from the trading community model — pay-from customer name and account number, sold-to customer name and account number, and billing location. In reporting and integration terms, it supplies a flat, query-friendly projection of data that would otherwise require joining multiple interim and customer tables, which is the primary reason the name "ar_interim_cash_receipt_lines" is issued as a search term. Unreleased or unposted receipts are inherently transient, so the view is most useful for operational reporting, reconciliation diagnostics, custom concurrent programs, and conversion interfaces.

Underlying Base Objects

The documented referenced objects span several functional pillars. The core interim tables are referenced through AR_INTERIM_CASH_RECEIPTS and AR_INTERIM_CASH_RECEIPT_LINES, with column aliases ICR and ICRL in the view text. Supporting Receivables objects include AR_BATCHES (for BATCH_NAME), AR_PAYMENT_SCHEDULES (payment schedule linkage), AR_RECEIPT_METHODS (TYPE_NAME), AR_RECEIVABLE_APPLICATIONS, AR_CONS_INV (billing number, CONS_BILLING_NUMBER), and RA_CUSTOMER_TRX plus RA_CUST_TRX_TYPES. Trading community data is drawn from HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, and HZ_CUSTOMER_PROFILES. Banking context comes from CE_BANK_ACCOUNTS and CE_BANK_ACCT_USES for remit-to bank account use.

The view also references infrastructure packages — ARPT_SQL_FUNC_UTIL, ARP_DEDUCTION, FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS — along with the RA_TERMS synonym. The presence of MO_GLOBAL and security-related packages reflects Multi-Org and access-control filtering, while the package references indicate that portions of the view logic are encapsulated rather than expressed as plain SQL joins.

Key Columns

• CASH_RECEIPT_ID / CASH_RECEIPT_LINE_ID — Identifiers linking the projected row back to the interim receipt header and line.
• PAYMENT_AMOUNT / DISCOUNT_TAKEN — Line-level monetary values applied against the referenced transaction.
• DUE_DATE, PAYMENT_SCHEDULE_ID, CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID — Linkage from the receipt line to the installment and transaction line being paid.
• BATCH_ID / BATCH_NAME — The receipt batch the interim record belongs to.
• AMOUNT, RECEIPT_DATE, RECEIPT_NUMBER, CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE — Header-level receipt attributes, including currency conversion details.
• GL_DATE / GL_POSTED_DATE — Accounting date and posting date for the receipt.
• STATUS — Interim receipt status used to distinguish unposted from processed records.
• PAY_FROM_CUSTOMER, SOLD_TO_CUSTOMER, PAY_CUSTOMER_NAME, PAY_CUSTOMER_NUMBER, SOLD_CUSTOMER_NAME, SOLD_CUSTOMER_NUMBER, BILLING_LOCATION — Customer identification and address context.
• RECEIPT_METHOD_ID / TYPE_NAME, REMIT_BANK_ACCT_USE_ID, CUSTOMER_BANK_ACCOUNT_ID — Payment method and banking attributes.
• DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE — Document sequencing information.
• TRX_NUMBER, BILLING_NUMBER, USSGL_TRANSACTION_CODE, SPECIAL_TYPE — Transaction and accounting classification references.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, PROGRAM_ID, REQUEST_ID — Audit and who-columns for traceability.

Common Use Cases and Queries

Typical scenarios include identifying open interim receipts awaiting posting, reconciling batch totals against expected receipt amounts, validating customer and currency assignment during receipt import, and extracting receipt-line detail for downstream data warehouse feeds. The STATUS, GL_DATE, and GL_POSTED_DATE columns are the usual filters for locating unposted receipts.

A representative query selecting unposted interim receipt lines with customer context:

• SELECT cash_receipt_id, cash_receipt_line_id, receipt_number, receipt_date, amount, payment_amount, discount_taken, currency_code, status, batch_name, pay_customer_name, sold_customer_name, trx_number FROM ar_interim_cr_lines_v WHERE status = 'UNPOSTED' ORDER BY receipt_date, receipt_number;

A second pattern aggregates line amounts by receipt batch to verify batch control totals:

• SELECT batch_id, batch_name, receipt_number, SUM(payment_amount) line_total, SUM(discount_taken) discount_total FROM ar_interim_cr_lines_v GROUP BY batch_id, batch_name, receipt_number ORDER BY batch_name;

Because the object is documented as Release 115 only, developers should confirm availability and column behavior in the specific 12.1.1 or 12.2.2 instance before embedding it in production integrations, and should prefer supported public APIs for write operations rather than attempting DML through the view.