Microsoft Dynamics GP (Archived)

Project issue - Error: Fiscal information does not exist for the date range...

(0) Share

Report

Posted on by DavidMO

1,030

My user is getting an error when entering a fee for a project.

1.) Cards, Project, Project to bring up the "Project Maintenance" screen, they then select the project.

2.) Click on the "Fees" button.

3.) Then they add an existing "Fee ID" to the bottom of the "Project and Services Fees" List.

4.) When they then click on the "Frequency" arrow, they get the following error...

“Fiscal information does not exist for the date range. The fiscal year must exist

in order to create the periodic records.”

What date is GP checking before opening the Fee Schedule screen? Where is it located?

We are on GP 2010 sp1.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

DavidMO 1,030 on at

Like (0)

Report

Well, I must say I read a GP product suggestion online (from 2007) and missed the significance the first time around. I kept looking at the end date since it was so far in the future.

It IS the beginning date that caused this error.

To fix this go into SQL table PA01201 and fix the Project's begin date

Was this reply helpful? Yes No
DavidMO 1,030 on at

Like (0)

Report

Well, I have a group of users that keep creating this error. I have mapped out 243 places in the PA tables where beginning and ending dates might be stuck.

Does anyone have a longer term solution for this?

I am still trying to identify where they are typing these in wrong, but the speculation is that the users are typing in dates in an international format while GP takes the date as mm/dd/yyyy.

Were are on 2010 R2 now.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi, we have encountered this and fixed this in the table PA01201 and PA01101. We only have one project under that contract. However, it reverted back to the invalid end date. How did you manage to resolve this? Thanks..

Was this reply helpful? Yes No
Suggested answer

DavidMO 1,030 on at

Like (0)

Report

I used a SQL script (Find columns where a particular value is present) to search all PA tables for that specfic bad date value. I then searched those tables for the date, project, etc. to isolate the related records. Then I updated them.

I was doing these fixes too often, so I also wrote a GP plug-in to block Project dates more than 7 years back and 7 years forward.

I also posted a product suggestion to Microsoft.

*************************************

From the last time the date issue occurrend, I found these fields/tables. Sometimes there are more.

Select 11, PABEndDate, * FROM PA01100 WHERE PABEndDate = '7/9/2013'

Select 12, PA_Actual_End_Date, * FROM PA01101 WHERE PA_Actual_End_Date = '7/9/2013'

Select 15, PABEndDate, * FROM PA01101 WHERE PABEndDate = '7/9/2013'

Select 18, PA_Actual_End_Date, * FROM PA01201 WHERE PA_Actual_End_Date = '7/9/2013'

Select 21, PABEndDate, * FROM PA01201 WHERE PABEndDate = '7/9/2013'

Select 26, PA_Actual_End_Date, * FROM PA01301 WHERE PA_Actual_End_Date = '7/9/2013'

Select 33, PAUEndDate, * FROM PA01301 WHERE PAUEndDate = '7/9/2013'

Select 50, PAEnDate, * FROM PA02101 WHERE PAEnDate = '7/9/2013'

Select 177, receiptdate, * FROM PA31102 WHERE receiptdate = '7/9/2013'

Was this reply helpful? Yes No
Eric Wild II on at

Like (0)

Report

I Ran PA Recreate Periodic and PA Reconcile Periodic and it fixed this problem!

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Eric, I think it is a version issue - back when this error was reported, the Reconcile you talk about running may not have been cleaning up the files as well.

I know that currently with GP2013 and GP2015 we have relied on this to fix the fiscal error a number of times

Was this reply helpful? Yes No
Eric Wild II on at

Like (0)

Report

You are right, I am on an early version of GP 10.0.

Was this reply helpful? Yes No