Vendor Aging Report with Large Data Volume in Microsoft D365 F&SC
Deepak Singh
163
Table of Contents
Introduction
There is a thrilling announcement that Microsoft has launched a new functionality for Vendor Aging reports having large data volume in July 2023, now customers will get rid of session time out.
The vendor aging report can time out due to large data volume. This feature provides an alternative way to let customers export results from the vendor aging report. Customers will be able to do reporting based on the exported data, and this assures business continuity.
Problem Statement
Many times businesses face issues of time out in Microsoft D365 F&SC while running Vendor aging reports with large volumes of data. This causes a problem in business continuity and business loss since the customer is not able to fetch the report and is unable to track the Vendor aging and make payment timely.
In the Feature management workspace, enable the Vendor aging data storage feature:
(D) Batch job will run and Number of aging lines (in our case it was 97 same as at the time of creating Vendor aging data storage in Accounts payable module) will be generated
Thank you
Feature Details
When you run the vendor aging data storage process to export the vendor aging report, the results can go to an external system using our data management framework. This feature provides an efficient way to report on data when there are large volumes of it.Configuration and Process
1. Enable the vendor aging data storage feature
In the Feature management workspace, enable the Vendor aging data storage feature:
2. Run the vendor aging data storage process
(A) Go to Accounts payable > Inquiries and reports > Vendor aging data storage.
(B) then click on new and in the name provide process name and fill other parameters as required
and Click OK to run the batch job.
Note: Transaction details are always included, and the processing is always done in a batch job.
(C) After Clicking OK, batch job will run
(D) Refresh the Vendor aging data storage page to see the batch name, batch runtime, and processing status. When the batch job is completed, the Processing status field is set to Ended, and the Number of aging lines field is set. If the batch job is recurring, the Processing status field is set to Waiting.
Record the Execution name which is batch name as per below screenshot. It will be used as a filter while extracting vendor aging reports from Data Management Framework.
In our case it is "All vendor aging-2023-09-23T18:57:21"
3. Use of Data Management Framework for exporting the Vendor Aging
(A) Go to Data Management > click on Export
(B) Apply filter for which batch job (execution name) aging report will be generated
(C) Now Click EXPORT to generate the Aging report
(D) Batch job will run and Number of aging lines (in our case it was 97 same as at the time of creating Vendor aging data storage in Accounts payable module) will be generated
(E) Report will be downloaded and can be shared or used for business purpose.
As per below screenshot Vendor Aging will be downloaded based on aging period definition of 30 day, 60 days and 90 days and yellow highlighted is related to vendor information.
Important Note:
If "Vendor aging data storage" entity is not visible then
Go to Data management > Framework parameter > Entity Setting > Refresh entity List, it will update/refresh all the entity in the system.
Happy Learning 🙂
*This post is locked for comments