OBIA 7963 Clarification of Functionality For Extracting R11 AR Subledger Into DW
(Doc ID 1910900.1)
Last updated on FEBRUARY 06, 2020
Applies to:Siebel Financial Analytics - Version 184.108.40.206 [AN 1900] and later
Information in this document applies to any platform.
There appears to be some inconsistencies in the AR detail,snapshot and aging dashboards defined on top of the OOTB AR extract functionality in Financial Analytics.
In particular, end of month details do not match our AR reports from R11; as well future-posted transactions appear to be assigned to current aging buckets, which differs from our other AR reports.
To best outline the issue:
Situation: AR in Oracle E-Business Suite – from a business process standpoint, users open all periods for a fiscal year (periods based on fiscal calendar month). This allows the business to create AR transactions with a future accounting transaction (sub -ledger and GL posting date). For example, you can create an invoice in AR today with an accounting date > July 31, 2104.
In order for the AR Aging report to properly capture the correct date for which a transaction should be included in a monthly (as of date) view, the report needs to be looking at the accounting date on the AR sub-ledger transactions.
The current AR mapping is referencing the following column (POSTED_ON_DT_WID)
The is is that it is unclear where the date is populated from based on the review of mappings. At an invoice level, the Oracle AR subledger table name that appears to capture the correct accounting transaction date is (apps.ra_cust_trx_gl_dist_all ragl) using the field name (GL_DATE).
This would provide the proper accounting date whether running an AR report within a fiscal period (as of date) or for a period end (where the period end dates are defined).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document