on 12-30-2013 3:46 PM
During CJ8G one settlement error gets repeated with error msg EBP603 as follows:
Item 001 WBS element W.00000010.001 budget exceeded
Sender: ORD 540000008932
Item 001 WBS element W.00000010.001 budget exceeded
Sender: WBS U.80026507
Item 001 WBS element W.00000010.001 budget exceeded
Sender: WBS U.80010284
We find the same WBS in all the lines. What can cause this same line to reappear again in all lines.
Hi Suman,
I guess this is due to different sender is different.
If you have a single sender, then it will display only one message.
Regards
Terence
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hallo Maria,
the issue is that the error messages does not seem to have any reason at all,
an example would be
Sender: WBS CPX.000XXXXX-F1 | ||
E | BP604 | Item 001 WBS element C14.XXXXX-F2 budget exceeded |
E | BP604 | Item 003 WBS element C14.XXXXX-F2 budget exceeded |
However CPX.000XXXXX-F1 is in no way related to the receiver C14.XXXXX-F2, it is not in the same structure, it has a settlement rule to an AUC and since it does not have any other errors it is expected that settlement would take place.
Hi Suman / Jacob,
There are couple notes available in SAP. Please find below, check and let us know whether this resolves your issue.
1742941 - Unjustified error messages for availability control
1606591 - Unjustified error messages when entering budgets or releases
1464000 - Unjustified error messages of availability control
In case if the above does not solve or not related to your SAP version, you need to raise a OSS note to SAP to resolution.
Regards
Terence
Good Morning Suman,
have you had any joy resolving this as we are having the exact same issue.
During execution of settlement run in background whenever the message BP604 is correctly raised even once this message is repeated over and over again for a single WBS element. This occurs even though the WBS element is only maintained as a settlement receiver once.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Go though any of structure report as cns41 as well and select the fields for budgeting and actual cost and plan cost.
do comparison as below:
Plan Vs Actual
Budget Vs Actual
Report will show if budget exceeded? make adjustment then execute settlement.
Regards,
Sanjeev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Understand your suggestions but my querry is why this error gets repeated for the same WBS in all error lines. This is in almost 50 lines and whatever may be the sender object of the cost the error always shows for the same WBS. Since this a standard program do we still need to look deep into the code?
Hi Suman,
In project hierarchy lower level wbs elements and activities are settled to the respective higher level WBS element. In standard when we execute collective processing of settlement, system considers all the cost objects in the hierarchy which have settlement rule and does the settlement to receiver. In your case the wbs W.00000010.001 is reciver for many lower level objects.that's why same wbs is showing multiple times in the error message with different senders.
Check the budget exceeded issue on the WBS element W.00000010.001 as suggested by Tushar and Sanjeev.
Regards,
Hello Suman,
Go to Budget report S_ALR_87013558 for WBS element W.00000010.001 and check how much is the available amount against Budget.
Check Actual cost and open commitment for this WBS element.
You can check list of open commitment from CJI5 report as well.
Regards
Tushar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.