Search Results trx_class_code

Overview

The ICX_AR_RECEIVABLE_APPL_V view belongs to the ICX — Oracle iProcurement product family within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its stated purpose is to expose Cash and Credit Memo applications Accounting Information for receivable applications. In practice, the view is derived from the Receivables applications window used by the Oracle Receipt Workbench, providing a formatted, user-facing projection of payment application records tied to cash receipts and credit memo activity.

The view is not implemented in the database documented in the ETRM metadata; the underlying view text references AR_RECEIVABLE_APPLICATIONS_V and selects from a Receipt Workbench perspective. This means the object is primarily a reporting/inquiry construct rather than a transactional table. Its role is to surface amounts applied, discount taken (earned and unearned), remaining amounts due, customer and location descriptors, and receipt identifiers in a single, readable record for downstream UI or integration use.

Underlying Base Objects

The ETRM metadata documents no referenced base objects explicitly for ICX_AR_RECEIVABLE_APPL_V. However, the view text embedded in the metadata indicates it is built on the Receivables applications family. Key source structures implied by the SELECT include:

• AR_RECEIVABLE_APPLICATIONS (aliased as APP) — the driving applications table holding CASH_RECEIPT_ID, AMOUNT_APPLIED, APPLY_DATE, and GL dates.
• AR_PAYMENT_SCHEDULES (aliased PS_INV) — supplying TRX_NUMBER, INVOICE_CURRENCY_CODE, AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, and TERMS_SEQUENCE_NUMBER.
• AR_CASH_RECEIPTS (aliased CR) — providing RECEIPT_NUMBER.
• HZ_CUST_ACCOUNTS / Customers (aliased CUST) — CUSTOMER_NAME and CUSTOMER_NUMBER.
• HZ_LOCATIONS / Site Uses (aliased SU) — LOCATION.
• FND_LOOKUPS (aliased L_ACC and L_CLASS) — decode values for the meaning of application class and transaction class.
• FND_CURRENCY — SAFE_GET_FORMAT_MASK for currency-aware formatting of numeric columns.

Because the documented view metadata lists no base objects, EBS administrators should validate actual dependencies against the deployed AR schema in their instance.

Key Columns

• ROW_ID — ROWID of the underlying application record.
• CASH_RECEIPT_ID — Identifier linking the application to its cash receipt.
• TRX_NUMBER — Transaction number or lookup meaning when the application is against a receipt (-1 schedule).
• TRX_CLASS_NAME — Class of the applied transaction (e.g., invoice, credit memo).
• AMOUNT_APPLIED — Amount applied, formatted per invoice currency.
• DISCOUNT — Sum of EARNED_DISCOUNT_TAKEN and UNEARNED_DISCOUNT_TAKEN, which is directly relevant to the search term discounts_unearned.
• APPLY_DATE, GL_DATE, GL_POSTED_DATE, REVERSAL_GL_DATE — Application and accounting dates.
• AMOUNT_DUE_ORIGINAL and AMOUNT_DUE_REMAINING — Original and remaining amounts on the schedule.
• CUSTOMER_NAME, CUSTOMER_NUMBER, LOCATION_NAME — Customer and site descriptors.
• RECEIPT_NUMBER — User-visible receipt identifier.
• INSTALLMENT — Terms sequence number for the payment schedule.

Common Use Cases and Queries

Typical scenarios include reconciling applied receipts, analyzing discount activity (including unearned discount), and providing inquiry data to iProcurement or Receipt Workbench-style screens.

Sample query isolating unearned discount exposure:

• SELECT customer_name, trx_number, amount_applied, discount, apply_date FROM icx_ar_receivable_appl_v WHERE discount > 0 ORDER BY apply_date DESC;

Sample query for remaining balances on invoices with applications:

• SELECT customer_number, trx_number, amount_due_original, amount_due_remaining, receipt_number FROM icx_ar_receivable_appl_v WHERE amount_due_remaining > 0;

Because the view is documented as not implemented in the reference database, confirm object validity and column availability in the target instance before relying on these statements.