Receivables Frequently Asked Questions

Accounts Receivable Topics:

Since Receipt Accounting Date doesn't support Receipt Amount, which measure should I use to get receipt amount by accounting period? Also which measures are recommended for balancing segment?
What is the purpose of AR Unaccounted Transactions functional area?
Why am I missing transactions and receipts related to Multifund Accounting in Receivables subject areas?
Why can’t I use receivables unaccounted transactions?
Why can't I validate data in AR Adjustments and AR Credit Memo Applications for Primary Ledgers?
Why do I not see the Project attributes or the Associated Task attributes for the Project Contract invoices in AR Revenue subject area?
Why do I see unaccounted transactions in AR Transactions and AR Revenue subject areas?
Why is the Credit Memo Applications Amount not populated for certain ledgers?
Why am I missing month-end snapshots from AR Aging and AP Aging? or What frequency should I run the pipeline data extract for Accounts Receivable and Accounts Payable Functional areas?
Why do some of the Aging metrics sow the same value in all Aging buckets?
How do I identify Risk Receipts in the AR Aging subject area? Is it included in the Outstanding calculation?

Since Receipt Accounting Date doesn't support Receipt Amount, which measure should I use to get receipt amount by accounting period? Also which measures are recommended for balancing segment?

For Receipt Accounting Date and Balancing Segment Code, all metrics are supported except Receipts Amount and Average Receipts Amount. While Receipts Amount by Accounting Period isn'te supported, you can query receipts amount by the following two period columns:

Financials - AR Receipts and Applications.Time.Fiscal Period"
Financials - AR Receipts and Applications.Receipt Details.Receipt Date.Receipt Fiscal Period

What is the purpose of AR Unaccounted Transactions functional area?

The AR Unaccounted Transactions functional area brings in AR Transactions, Line, and Distributions data for all completed transactions including unaccounted transactions. The Accounts Receivables subject area only brings in data for accounted transactions.

AR Transactions and AR Revenue have unaccounted transactions and distributions if the AR Unaccounted Transactions functional area is activated and this data is also used to calculate the Transaction Amount and Line Amount in the AR Revenue subject area. Therefore, be sure to activate the AR Unaccounted Transactions functional area after the Accounts Receivables functional area is activated.

Since the AR Unaccounted Transactions functional area has unaccounted transactions, if customers marks a completed transaction as incomplete in Oracle Fusion Cloud Applications and deletes it, this will leave orphan records in Oracle Fusion ERP Analytics which is handled as part of the daily incremental pipeline run. Be sure to reset the functional area in such cases.

Why am I missing transactions and receipts related to Multifund Accounting in Receivables subject areas?

In the Fusion Data Intelligence Accounts Receivables subject areas, Multifund Accounting, Detailed Reeivables Distributions, and MFAR aren't currently supported.

Why can’t I use receivables unaccounted transactions?

All Receivables subject areas except AR Transactions and AR Revenue only support accounted transactions. AR Transactions and AR Revenue subject areas support unaccounted transactions when the AR Unaccounted Transactions functional area is activated.

Why can't I validate data in AR Adjustments and AR Credit Memo Applications for Primary Ledgers?

When you perform data validation on the Adjustments Amount metric in AR Adjustments and the Credit Memo Application Amount metric in AR Credit Memo Applications for non-primary ledgers, the source value is null even though there's a value. These data validations only support primary ledgers.

Why do I not see the Project attributes or the Associated Task attributes for the Project Contract invoices in AR Revenue subject area?

The Fusion Accounts Receivables module stores the Project and Associated Task attributes at the Receivables line level for Project Invoices only if the Invoice Grouping rule on the Contract is set up to group the lines by these attributes. If Project and Associated Task attributes aren't used in the Invoice grouping, these attributes won't be passed to Receivables and won't be available the in AR Revenue subject area either.

Why do I see unaccounted transactions in AR Transactions and AR Revenue subject areas?

The AR Unaccounted Transactions functional area is new in Release 22.R4. When you activate this functional area, the AR Transactions and AR Revenue subject areas show both accounted transactions and unaccounted transactions as long as the transactions are complete and the revenue schedules are generated. Data validations of Total Transaction Amount in AR Transactions and Distribution Amount in AR Revenue fetch both accounted and unaccounted data from the source. If the AR Unaccounted Transactions functional area isn't activated, then there is a mismatch between the source and warehouse since the warehouse only has the accounted transactions.

To work around this issue, set the Accounted Indicator attribute to Yes for the data validation.

Why is the Credit Memo Applications Amount not populated for certain ledgers?

The Credit Memo Applications Amount in the Facts-Ledger Currency folder of the AR Credit Memo Applications subject area is populated only for Primary Ledgers. It's not supported for non-primary ledgers. Application distribution Amount is populated for Primary and non-primary ledgers.

Why am I missing month-end snapshots from AR Aging and AP Aging? or What frequency should I run the pipeline data extract for Accounts Receivable and Accounts Payable Functional areas?

You must schedule pipeline incremental runs for Account Receivable functional areas daily. AR Aging fact tables (included in Accounts Receivables functional areas respectively) are designed for daily incremental runs.

When the incremental run happens after the fiscal month end date, it creates a historical snapshot for the previous month with the month-end data. If the incremental snapshot runs on a weekly basis, and the month-end date falls on a day on which the schedule doesn't run, then the month won't have an accurate month-end snapshot. Creating a snapshot as the last day of an incremental run for the month won't include open transactions that belong to that snapshot. To work around this issue, reset the functional area to build a snapshot that includes the month-end date.

Why do some of the Aging metrics sow the same value in all Aging buckets?

In AR and AP aging, only the below metrics calculate outstanding amounts based on the Aging buckets:

Aging Amount - Invoice Date Basis
Aging Count - Invoice Date Basis
Aging Amount - Schedule Date Basis
Aging Count - Schedule Date Basis

All other Aging metrics aren't designed to work based on the Aging buckets. They should be used for analysis with the other dimensions and attributes in Aging subject area.

How do I identify Risk Receipts in the AR Aging subject area? Is it included in the Outstanding calculation?

AR Aging has a Risk indicator attribute to identify Receipts at Risk. This shows all Receipts that aren't Cleared, Risk Eliminated, or Reversed as Y. The receipt amount of such Receipts is shown as Risk Amount in the Risk Amount metric.

Unapplied, Unidentified, and On-Account Receipts are only included in the Total Outstanding and Aging calculations. Risk Receipts aren't separately included in the Aging calculation.