A day in the life of an Oracle Applications Consultant

Thursday, April 07, 2005

FSG YTD-Actual Problem and Resolution

This post contains the solution for a small problem we encountered when trying to produce an FSG report.

When trying to produce an FSG report in ADI the other day we noticed a problem with the YTD-Actual column in the report. We wanted to print the report as at December 2005 (i.e. the last month of the year) so that we could see what the budget figures looked like. When trying to print the report in this fashion the YTD-Actual column for Dec 2005 was displaying zero values even though we knew there should be data in the report. We tried printing the report from within General Ledger but still the same result, zero values in the YTD-Actual Column. We knew that there should be values in this column as January and February had already been closed and most of the entries for March had been processed. Even when performing a drill down to the detail in the General Ledger we could see that there were values present.

The problem was a simple one which we found the resolution for buried in point 30 of Metalink Note:108236.1 entitled FSG Functional FAQ. The solution suggested that in order for the YTD-Actual data to display in the report you should ensure that the GL periods upon which you were reporting should be open or closed. In our instance the periods from April to December were still Future Enterable and hence we resolved the problem by opening these periods and immediately closing them so that they now had a status of closed. Once this simple task had been performed we were able to see data in our report.