on 09-25-2012 5:57 AM
hi
all,we have budget check at pr level
i want to remove now,our budget are yearly specific
i want to know there is there any impact
john
Hi John,
Hope you got answer to your query from above post.
But my take is that why do you want to remove budget check at PR level.
You can postpone the budget check to PO level but it wont reduce your problem of budget exceed(for which you want to remove budget check as I guess, correct me if I am wrong). You will have to face budget exceed error at next level ultimately. Scene might be more complex there.
So be careful.
Regards,
Pranav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
Gokul has already suggested in his post above for your doubts.
The only effect will be that system wont give you budget exceeded error for your PR commitment (nor it will check budget at PR stage).
However, your PR commitment would eat out your allocated/available budget.
And if you don't want system to eat out budget at PR level then implement SAP note 955106 & 955107 that what Gokul has suggested.
For rest of the things system will behave as it was behaving before.
hope it is clear to you know.
NOTE: If you are not sure then you may check the behavior of the system in your testing server and yourself analyze if the system is behaving properly.
All the Best.
Regards
Ankur
Hi guys
i remove the PR document check in the spro for availability check
however i couldn't make availability zero it is asking for some numeric value
when i am making PR it does not check the availability budget,but its making commitment document
what does it mean the budget consumed or not,bcz i am interested in budget consumed for me its ok if it is making commitment document but budget should not be commitment as earlier while the pr level check is there.
Hi John,
I hope you have checked SAP notes 955106 & 955107.
If you have made settings for not allowing budget check @PR level then system would not give "Budget Exceeded......" error at PR though it would consume the budget and show it as commitment in S_ALR_87013558 report.
However, if you want that system should neither check budget @PR level not it should consume budget @PR level then in this case you have to implement SAP note 955106 & 955107.
Hope it is clear to you now.
Regards
Ankur
i have seen 955106 is implemented not 955107.
i gone through both the notes 955107 is how to dlete the commitmnet documents automatically created.
it speaks about some devlopment
while 955106 implement that the requirement is not to consume the budget let the system create the commitment document.
should i implement 955107 or 0955106 is enough for not consuming budget
pls suggest
Hi John,
I don't think its happening because you have disabled the budget check at PR. The value type for PR is 21 and that for PO is 22.
As far as i feel, the note 955106 would disable budget check for PR based on value type. Why don't you try to check this out with a new test case? I mean test this with a new project in your test system.
Regards,
Gokul
Hi John,
SAP creates notes considering many aspects and not what an individual requires. Besides, implementing a note and then manually reverting a correction is a normal process followed by many.
As far as your question, "why sap did not give to choose if at all it gives two correction" goes...please ask SAP about it and i hope you get a fitting reply.
And who told you we should not do anything manually? I guess someone is misguiding you. Please go ahead with the suggestions posted above and i assure you there wont be any issues. Else, raise this with SAP.
Best Regards,
Gokul
hi
all
we have applied the budget check removal notes
Now the commitment on no mere on PR hence forth.
what happen to the earlier commitment siting on the Pr
i just test some old pr in devlopement they have commitment document but when i change either value or quantity and then save and then check no commitment document found
my query is how to return the siting commitment to budget from the PR
The standard way of reducing value and quantity will still work on earlier PR before budget check removal?
i executed but the assigned value remains the same the assigned value should increase
actually what happened in client site the earlier pr before budget check removal have commitmnets so the budget get reduced since now no ore commitment on PR after check removal client wants that commitment of PR should reduce and budget avalable should be more .
Hi John,
OSS 1307755 has 2 solutions, I think you need the second one
The attachments contain two modifications (number of correction instructions):
Are you sure you have implemented correction 1086521 instead of 1086520?
Regars,
Sara
error is not in reporting the query is fundamental
if i applied both the note then earlier commitment will delete and the assigned value will decrease equally due to commitment or simply delete the commitment on pr?
Requirement is it should delete the commitment and budget available should increase so that customer can take the benefit of budget check removal at Pr stage.
Hi John,
After OSS note implementation :
To delete previous commitment documents :RKANBU01
To delete the amount from the assigned value in Budget : CJBN
To fix the reports CJEN
It is not possible that the commitment document has been deleted and it is taking as budget consumed after CJBN execution.
Are you sure that it is taking the commitment and not the plan cost?
Go to CJ31 for your project --> extras --> Availability Control --> and check the entries that impact in budget consumed. ( check the value type, value on the right of the year...) which value type do you see.. 21?
Simply Remove your tolerance limit for PR as 00:Purchase Req. in sap standard in OPSC tcode.
then check after Reconstruct availability CO for project & Reconstruct project info database via CJBN and CJEN tcodes
Budget check only in those case where we assigned to any account like Q/P/N.in manual PR via ME51n
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 John,
Try what Ankur has mentioned in his post above and see if it helps.
In addition to this, do you never want the system to check the budget for PR in the future? Do you mean that except PR you want the system to check budget from the PO onwards? Please clarify.
If the answer to the first question is yes i would suggest you to check if notes 955106 and 955107 are implemented in your system. If these notes are implemented PR commitment will not be taken into account during availability control.
As far as i know there wont be any negative impact on the system. Only thing is budget check wont happen at the PR level and you can create a PR for any amount irrespective of the budget assigned.
Hope its clear.
Regards,
Gokul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I had the same requirement some time ago. If you change your tolerance limit for PR you will have a problem in your system because when you create a PO related to the PR there won't be AVAC.
You have 2 options :
1) Don't generate controlling document for PR ( then you won't have commitment) --> but you lost this information from controlling reports.
2) Implement changes in OSSnote 955107 : This was my solution, with this you can display PR costs in reportsbut it doesn't take account in the availability control
I hope this can be useful.
Sara
Hi John,
In tolerance group (maintained under tolerance limits settings) remove the activity group 00: Purchase requisition -> CJEN->CJBN and check.
Impact: System won't give the budget exceeded error at PR commitment level.
NOTE: Search more about it in the forum. there are so many threads for the same requirement.
Regards
Ankur
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
9 | |
9 | |
5 | |
4 | |
3 | |
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.