WBS element exceed error

[Former Member]

hi:

We are using SRM5.0 with ECS.I transfer PR into srm with plan driven procurement.

When I creat a PO for this PR and check it, the error message occurs,says item 001 wbs element *** exceed budget, I could not save the PO but hold it,so I think this error message was not the one from R/3.I am just wondering ,what budget does the system check?

Hope some could help me.Tks.

[Former Member]

Hi Richard:

Thank you for your reply,So SRM check the R/3 data while creating the PO,but I checked the R/3, it does not exceed budget.And I created a PO from this PR in R/3,this error message did not occur.Could you tell me why?Tks

[richard_feco]

Usually, 99% of this issues can be solved when you read and understand the SRM budget check note 520717 and read as well the related notes esp. regarding the CO-report RKACSHOW -- here you see and understand, how and where the budget data are stored on CO-tables and how the AVAC - availibility control works.

You can debug as well -- out of the BBP_PD-Form PROCDOC_CROSS_CHECKS the FM BBP_PD_COMMITMENT_FILL_ITAB is called. Here the data are mapped into backend structures in way ERP-backend requires it. Before the RFC-call is made please look up how exactly the structures are filled. This is something you need to understand whether there are some special tolerance-limits maintained on the CO side. You'll find these AVAC-tolerance limits in the CO-IO resp. WBS customizing (ask a CO-friend if you don't find it right away;). There you see exactly the tolerance linked to certain document type etc.

You can debug as well from the RFC call on -- once you're on the ERP side set a breakpoint at FM RWIN_CHECK -- here all check for Accounting are loaded. One of these checks refers to CO-AVAC. It is something like K_...BUDGET... or K_...OPEN_ITEM or K_...AVC....You have to look up yourself as this is just too long ago.

Cheers,

Richard

[Former Member]

Pan

Budget check can happen at the time of creating a PR or PO depending on the settings in ECC (target group in tolerance limits). I guess in your case it's been set to check budgets at PR stage itself and hence the error.

If the requirement is to issue a warning alone (not error) it can be done again under this node i.e., Availability control action (1-Warning)

Regards

Sreenivas

[richard_feco]

sorry guys, but what is posted above -- diplomatically, I would say filter&forget unrelevant...

What you see is budget exceeded problem coming from the ERP -- no user budget etc. is related. As well you have to look at the details before you decide that there's an issue with the CO availability control...

To understand what happens you need to understand the logic of how the budget is checked -- from SRM we just simulate posting of commitment. The logic how this is done is explained in note No. 520717 + related notes. You need to add the value from your SRM PO to what is the current budget/commitment/actual in this same moment. As well you can adjust the availibility control for logistic types in the backend e.g. you can set up tolerance values for PREQ to 150% and then warning and for PO 100% and error message. This might explain why you get differences for PO/PREQ in the backend.

Richard

[Former Member]

Hi

<u>Please go through the SAP OSS Notes as well -></u>

Note 183159 Investment support and budget monitoring

Note 668240 FAQ 2: Hierarchy reports

Note 783161 Availablty contrl only chcks with increase of assigned value

Note 139569 Availab.control: Status ISBD / AVAC not deactivated

<u>Incase this does not help, please create a Customer OSS Message with SAP for faster processing of your problem.</u>

Do keep me updated.

Regards

- Atul

[richard_feco]

Atul,

I wonder that you propose to open an OSS message in case your posting does not explain the situation correctly.

I don't care if it's part of the etiquette officially , but this is a free forum and pointing people to open an OSS call based upon your decision is really bad style. Maybe you do not remember -- quality is more of value than quantity!

[Former Member]

Hello,

Budget can be set in SRM through

PPOMA_BBP> extended attributes>PO value limits-->User Budget

this value can be set at various dept levels where you want.

But if you have budget control activated for the plant (which you have at ex attribute --> location) in ECC FI then also you will get errors of budget.

your FI guy can tell you better.

So check both the points

BR

Dinesh