Search Results applied_transaction_number




Overview
Explore in AI Chat

Overview

APPS.ARFV_CREDIT_MEMO_APPLICATIONS is a reporting view in the Oracle E-Business Suite Receivables (AR) module that exposes credit memo application activity. It presents the linkage between a credit memo (a credit transaction) and the transactions against which it has been applied, including the amount applied, tax, freight, and receivables charges components. The view carries an internal-only designation: Oracle Corporation does not support direct access to this object except through standard Oracle Applications programs. External reporting or integration against this object is therefore undertaken at the customer's own risk and must remain read-only in practice, since the object is a view rather than a maintainable entity.

The view is registered with FND Design Data AR.ARFV_CREDIT_MEMO_APPLICATIONS, has a status of VALID, and is owned by the APPS schema. Its view type is Internal. It is principally intended to support credit memo application inquiries and reporting that require both transaction-level and line-level application detail alongside descriptive flexfield context.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms:

AR_RECEIVABLE_APPLICATIONS supplies the core application facts, including the receivable application identifier, applied amounts, apply date, and the corresponding applied payment schedule. AR_PAYMENT_SCHEDULES provides the due-date and scheduling context that allows the view to derive fields such as DAYS_LATE. RA_CUSTOMER_TRX supplies credit transaction header attributes such as CREDIT_TRANSACTION_NUMBER and CREDIT_TRANSACTION_DATE, while RA_CUSTOMER_TRX_LINES contributes line-level application information and TRANSACTION_LINE_ID, TRANSACTION_LINE_NUMBER, and associated line amounts. HR_ALL_ORGANIZATION_UNITS resolves the operating unit description exposed as OPERATING_UNIT and supports the ORG_ID column.

Key Columns

The view exposes primary keys and identifiers (RECEIVABLE_APPLICATION_ID, CUSTOMER_TRX_ID, TRANSACTION_LINE_ID, APPLIED_PAYMENT_SCHEDULE_ID) plus transactional amounts (AMOUNT_APPLIED, AMOUNT_APPLIED_BASE, ALLOCATED_RECEIPT_AMOUNT_BASE, LINE_AMOUNT_APPLIED, TAX_AMOUNT_APPLIED, FREIGHT_AMOUNT_APPLIED, RECEIVABLES_CHARGES_APPLIED).

For users searching on "applied_transaction_number", the column APPLIED_TRANSACTION_NUMBER (VARCHAR2(30)) is the transaction number of the transaction to which the credit memo was applied — frequently the invoice or debit memo that the credit offsets. It sits alongside CREDIT_TRANSACTION_NUMBER (the credit memo's own number) and TRANSACTION_LINE_NUMBER, enabling a full picture of which credit was applied to which transaction and line. Applying date is held in APPLY_DATE, and REASON_CODE captures the credit reason. Descriptor flexfield context is exposed through _DF:APP_INFO and _DF:GLOBAL_FLEX, while standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) are also present.

Common Use Cases and Queries

Typical uses include credit memo application analysis, unapplied versus applied reconciliation, and line-level credit reporting. A query matching the user's search term would be:

  • SELECT CREDIT_TRANSACTION_NUMBER, APPLIED_TRANSACTION_NUMBER, TRANSACTION_LINE_NUMBER, AMOUNT_APPLIED, APPLY_DATE FROM APPS.ARFV_CREDIT_MEMO_APPLICATIONS WHERE APPLIED_TRANSACTION_NUMBER = :transaction_number;
  • Summing applied credit by operating unit: SELECT OPERATING_UNIT, SUM(AMOUNT_APPLIED) FROM APPS.ARFV_CREDIT_MEMO_APPLICATIONS GROUP BY OPERATING_UNIT;
  • Aggregating tax, freight, and charges applied against a given customer transaction using CUSTOMER_TRX_ID.

Because the object is internal and read-only, queries should be restricted to reporting and should not assume supportability. Data is filtered implicitly by ORG_ID within a multi-org context.