Design issue in Reports based on Subledger Transactions showing Accounting information
Hello Enginatics Team,
I found a design issue in Reports based on Subledger Transactions showing Accounting information. For example “INV Material Account Distribution Detail”. The Accounting information are picked from the Distributions Tables of the SL Transactions, but since R12 Subledger Accounting is processed through the SLA Tables, where the SLA Rule customizations are applied to generate the “true accounting information into GL” the SL Distribution Tables are not showing the “Accounting Truth” anymore.
Example: we have SLA Rules defined to adjust the accounting for COGS to values picked from the Customer and Items into the Accounting FlexField for the Journals created. In the “INV Material Account Distribution Detail” Report the Debit COGS Accounting for a specific Transaction No is shown as 640101.0000.THP.9600.CN.E.104.SC.000000.0.0.ECN
But in the SLA Journal Line Tables the query result for the same
Transaction No gives the result:
660247.P091.THP.5166.CN.A.104.SC.000000.0.0.ECN this is the true
Accounting information transferred to GL.
I am afraid it needs a redesign for all Blitz Reports based on Source SL Transactions with accounting information, because they do not use SLA Tables to pick up the accounting information. Of course the SLA Tables are filled after “Create Accounting” in the Subledgers had been run. So it should be clear that Accounting information can only be shown in SL Reports after Create Accounting had been run.
3 replies
I think it would be a good idea to extend the Subledger Reports with Accounting information with an additional column showing the final SLA accounts once generated. That would be very helpful because SLA modification is a common feature used by many customers, I assume.
To be honest I expected that Oracle Development would have extended the Standard Reports in the same way, as SLA modification was introduced as powerful feature by Oracle and the Subledger Reports with Accounting details are recommended to reconcile Subledger with General Ledger. But this is nothing you have impact on.
I guess when you would extend the Subledger with Accounting details Blitz Reports with this additional piece of information you would make a lot of customers more happy with the Blitz reports then they already are J
Please let me know if you could manage this.
Many thanks
I have extended the “INV Material Account Distribution Detail” Blitz report to include the SLA Account and Account Description and SLA Entered/Accounted amounts. The updated version can be downloaded from the Enginatics library (https://www.enginatics.com/reports/inv-material-account-distribution-detail/) and imported into your instances.
Due to resource constraints, we will review and update any additional reports on a customer driven basis so we can prioritize our workload. Please let me know if you come across any other reports that are causing immediate concerns and I will add them to my task list to modify.
With the introduction of the SLA module, Oracle’s approach has been to retain the Inventory Reports as running based on the Inventory Accounting setups, and for the users to use the Ledger based reports for the SLA Accounting.
The “INV Material Account Distribution Detail”‘ Blitz report is an implementation of the Oracle Standard report of the same name, and as per MOS Note 781015.1, this report is not intended to look at the SLA tables.
I can extend the report to show the final SLA Accounts once generated, but as we have users using the report as a replacement for the standard report, I could not redesign it in such a way that it no longer works as per the standard report.
In regards to available Blitz reports that include the SLA Accounting, you can look to use the GL Account Analysis or GL Account Analysis (Distributions) reports with a Journal Source of Cost Management to review the journals generated from SLA along with the details of the originating Inventory Transactions.
- You must be logged in to reply to this post.
Sign in with LinkedIn or Google to take part.