How To Fix AP173 - Measures for app. request already budgeted, or avail. control active


SAP Error Message - Details

  • Message type: E = Error

  • Message class: AP - Investment program messages

  • Message number: 173

  • Message text: Measures for app. request already budgeted, or avail. control active

  • Show details Hide details
  • What causes this issue?

    You tried to attach appropriation request &V1& to a program position.
    As a result, the measures (orders or WBS elements) that are assigned to
    the appropriation request are then indirectly assigned (subordinately)
    to the program position. The settings for this program position specify
    that all measures that are assigned to it receive their budget solely
    from this program position during budget distribution.
    However, at least one of the measures (orders or WBS elements)
    belonging to the appropriation request you are trying to attach already
    has a budget. The budget it has received does <ZH>not</> come from an
    investment program. Or, availability control is still active for at
    least one of the orders or WBS elements belonging to the apppropriation
    request.

    System Response

    In order to avoid inconsistencies, the system does not attach the
    appropriation request to the investment program position.

    How to fix this error?

    First reduce to zero all currently existing budget amounts on the
    orders or WBS elements belonging to appropriation request &V1& (for
    example, using budget returns). And, if necessary, deactivate
    availability control for the orders and WBS elements.
    Then you can attach the appropriation request to the program position,
    and distribute the budget amounts from the program position to the
    orders or WBS elements belonging to appropriation request &V1&.
    following text copied in part from message AP102
    If you want to avoid deactivating availability control for the measures
    assigned to the appropriation request, there is another option. You can
    remove 'budgeted' status on these measures (transaction OK12 for
    orders, OPSX for WBS elements).
    To be able to remove 'budgeted' status, you have to reduce the current
    overall and annual budget on the measures to zero, and - very important
    - you have to use the <ZH>same</> business transaction (original,
    supplement, return ... ) as was used for entering the original budget!
    If the current overall and annual budgets already consist of more than
    one business transaction, then you have to remove each of the budgets
    separately according to the business transaction used. (In order to
    avoid temporary inconsistencies, you should also ideally do this in the
    reverse order to that in which the budget was posted.)
    <ZH>Example</>
    You create a current overall budget on an order assigned to an
    appropriation request as follows:
    RESET N1.
    Original budget 1000
    Supplement 200
    Return 50
    To remove 'budgeted' status from the order, it is not enough to enter a
    return of 1150, for example, even though this would reduce the current
    overall budget to zero.
    Instead you have to reduce the current overall budget to zero in the
    following sequence:
    RESET N1.
    Return 50-
    Supplement 200-
    Set original budget of 1000 to 0.
    You can only remove 'budgeted' status on the order (transaction OK12)
    after following these steps.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message AP173 - Measures for app. request already budgeted, or avail. control active ?

    The SAP error message AP173 ("Measures for app. request already budgeted, or avail. control active") typically occurs in the context of budget management and availability control in SAP. This error indicates that the system has detected that the budget for a particular application request has already been allocated or that availability control is active, preventing further budget allocation or changes.

    Causes:

    1. Budget Already Allocated: The application request you are trying to process has already been budgeted, meaning that the funds have already been committed or reserved for that request.
    2. Availability Control Active: The availability control settings are active for the relevant budget, which means that the system is enforcing budget limits and checks.
    3. Incorrect Configuration: There may be configuration issues in the budget management settings or availability control settings that are causing the error.
    4. Multiple Requests: If multiple requests are being processed simultaneously, it may lead to conflicts in budget allocation.

    Solutions:

    1. Check Budget Status: Verify the status of the budget for the application request. Ensure that the budget has not already been fully allocated or committed.
    2. Review Availability Control Settings: Check the availability control settings in the configuration to ensure they are set up correctly. You may need to adjust the settings if they are too restrictive.
    3. Release Budget: If the budget has been allocated but is no longer needed, consider releasing it or adjusting the budget to allow for the new request.
    4. Consult with Finance Team: If you are unsure about the budget status or availability control settings, consult with your finance or budgeting team for clarification and assistance.
    5. Transaction Codes: Use transaction codes like FMBB (Budgeting) or FMAVCR01 (Availability Control) to analyze and manage budget allocations.
    6. Check for Errors in Previous Transactions: Sometimes, previous transactions may not have been processed correctly, leading to inconsistencies. Review any related transactions for errors.

    Related Information:

    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
    • Documentation: Review SAP documentation on budget management and availability control for a better understanding of how these processes work.
    • User Forums: Engage with SAP user forums or communities where other users may have encountered similar issues and can provide insights or solutions.

    By following these steps, you should be able to identify the cause of the AP173 error and take appropriate action to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker