Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix FKKBIX673 - Exception reason &1 is not supported


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FKKBIX - Conv.Inv.: Billing (Invoice Preprocessing)

  • Message number: 673

  • Message text: Exception reason &1 is not supported

  • Show details Hide details
  • What causes this issue?

    <DS:DE.BITEXCREASON_KK>Exception reason</> &v1& is not supported for
    excepting billable items in event <DS:FU.FKK_SAMPLE_TFK8101EV_05>05</>
    or <DS:FU.FKK_SAMPLE_TFK8101EV_10>10</>.

    System Response

    Processing of the source transaction is canceled.

    How to fix this error?

    Check whether:
    The exception reason is valid only for a certain <DS:DE.BITSTATGRP_KK>
    status group</>
    The status group is allowed for the event
    In event 05, only exception reasons for the following status groups are
    allowed:
    <LS>' ' </> (All)
    <LS>R </>(Raw data)
    In event 10, only exception reasons for the following status groups are
    allowed:
    <LS>' ' </> (All)
    <LS>B </>(Billable)
    The selected exception reason has to allow that the billable items can
    be restored. Check the <DS:DE.BITEXCTYPE_KK>exception type</> in the
    settings for the exception reason.

    Procedure for System Administrators

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FKKBIX673 - Exception reason &1 is not supported ?

    The SAP error message FKKBIX673, which states "Exception reason &1 is not supported," typically occurs in the context of the SAP Financial Accounting (FI) module, particularly when dealing with the posting of documents or during the execution of certain financial transactions. This error indicates that the exception reason specified in the transaction is not recognized or supported by the system.

    Cause:

    1. Invalid Exception Reason: The exception reason provided in the transaction does not exist in the system or is not configured correctly.
    2. Configuration Issues: The exception reasons may not be properly set up in the system configuration, leading to unsupported entries.
    3. Version Compatibility: The error may arise if there are discrepancies between the version of the SAP system and the configuration settings.
    4. Data Entry Errors: Users may inadvertently enter incorrect values or codes that do not correspond to valid exception reasons.

    Solution:

    1. Check Exception Reason: Verify the exception reason being used in the transaction. Ensure that it is a valid and supported reason in the system.
    2. Configuration Review: Review the configuration settings for exception reasons in the SAP system. This can typically be done in the SPRO transaction under Financial Accounting settings.
    3. Consult Documentation: Refer to SAP documentation or help files to understand the valid exception reasons and their configurations.
    4. User Training: Ensure that users are trained on the correct codes and values to use when entering data in the system.
    5. System Update: If the issue is related to version compatibility, consider updating the system or applying relevant patches that may resolve the issue.
    6. Contact SAP Support: If the problem persists after checking the above points, it may be necessary to contact SAP support for further assistance.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes that may be involved in the process, such as FB01 (Post Document), FB50 (G/L Account Document), etc.
    • SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or workarounds.
    • Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.

    By following these steps, you should be able to identify the cause of the FKKBIX673 error and implement a suitable solution.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


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 simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant