Skip to Content
author's profile photo Former Member
0
Former Member

WBS element exceed error

Posted on Nov 27, 2007 at 05:18 AM 63 Views

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.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 27, 2007 at 08:03 AM
    0

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 27, 2007 at 03:52 PM
    0

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • Richard Feco
      Nov 27, 2007 at 07:03 PM

      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!

  • author's profile photo Richard Feco
    Richard Feco
    Posted on Nov 27, 2007 at 06:53 PM
    0

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 28, 2007 at 01:25 AM
    0

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member
      Dec 03, 2007 at 05:56 PM

      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

    Comment on This Answer

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.