08-24-2012 7:24 AM
Hi:
In FM Closing operations i am trying to set year wise setting for sender and received budget type as shown in figure and i am getting this error. The error disappears if remove year from it.
Message no. 00058
Regards
08-24-2012 7:48 AM
Hi Atif
Make necessary settings in SPRO path: Activate Budget Carryforward for Commitment
after that you can maintain entries in 'path Define Budget Entry Documents for Commitment Carryforward'
Let me know still if the issue persists
Regards
Rao
08-24-2012 8:03 AM
Dear Rao:
Before configuring ABP i want to know its relevancy with commitments carry forward and residual budget carry forward. Does configuring ABP impacts carry forward of these in any way ? I am unable to get this idea.
Regards
08-24-2012 9:01 AM
Hi Atif,
The two settings:
Activate Budget Carryforward for Commitment
Define Budget Entry Documents for Commitment Carryforward
are related to commitment carry-forward, not to residual budget (which is better to be called 'carry-over' by the way, as for SAP standard term). You have to set both of these two functions, if you want to proceed with carry-forward of your commitments.
Regards,
Eli
08-24-2012 9:11 AM
Hi Eli:
I have set the following settings in ABP with exception of derivation strategy ( don't know what needs to be defined in it or what will be its use for carrying forward commitment items) but still i am facing the same error as indicated in my 1st post.
08-24-2012 9:38 AM
Hi Atif
First maintain relevat settings in IMG path: Activate Budget Carryforward for Commitment, Define Budget Entry Documents for Commitment Carryforward.
After that go to IMG path 'Set Up Automatic Budget Postings After Fiscal Year Change' enter your FM Area, Fiscal Year and active status then save it.
After that click on define header attributes then enter budget process, version and document type.
If you process like this u may not get any error.
Check it once again let me know.
Regards
Rao
08-24-2012 9:55 AM
Hi Atif,
Why ABP???? You don't have to do it. This is completely separate action and for common, standard carry-forward of commitments is not relevant.
Regards,
Eli