P&L Statement Budget Report can only use budget scenerio for current year??

[Former Member]

I have a customer running SAP 2007 PL 42. They have 2 budget scenerios set up. 2009 Main and 2010 Main. I have checked and the 2009 Main is set for the period 2009 and 2010 Main is set for 2010. Even if we select a date (upper right corner date) that is for 2009, we can still only select the 2010 Main scenerio. What could be preventing SAP from showing the 2009 Main budget scenerio even when the date is for that period?

[jitin_chawla · Accepted solution]

Hi,

The issue mentioned seems to be similar to Note No. : 1260823.

Please check.

Kind Regards,

Jitin

SAP Business One Product Support

[Former Member]

Is there a work around for this issue?

[jitin_chawla]

Hi,

I am afraid there is no workaround other than that as the same is a bug which was fixed in PL46.

Regards,

Jitin

SAP Business One Forum Team

[Former Member]

Jitin,

Thank you.

Pat

Edited by: Pat Frohlich on Jun 15, 2009 3:11 PM

[former_member325312]

even iam facing the same prolem could anyone help me out

thanks and regards

giri prakash

[Former Member]

That is right based on the note.

Thanks,

Gordon

[Former Member]

I just tested on PL 47 and am getting the same issue. Can anyone verify that this has, in fact, been corrected in PL 46 and higher? Actually, I can't even change the date (located in the upper right corner) of the report. On this version it only shows '2008' even though periods are set up through 2010. Where does it get that 'date' from??...(it is not showing how the posting periods are set up)

Edited by: Pat Frohlich on Jun 15, 2009 2:18 PM

[Former Member]

Never mind. It is correct in PL 47. I was only getting one date because I hadn't created other scenerios that had data in them. Thank you.

[Former Member]

Jitin,

Yes I think this is the same issue. They can't print using a prior period Budget scenerio. From what I understand from your message, this has been corrected in PL 46???

[jitin_chawla]

Hi,

The issue was a bug which is reportedly fixed in 2007A PL46.

You can test in the Test Enviorment on copy of the database, if it works.

Regards,

Jitin

SAP Business One Forum Team