How To Fix KY347 - An exception already exists for column &1


SAP Error Message - Details

  • Message type: E = Error

  • Message class: KY - Messages for SAP-EIS: Presentation

  • Message number: 347

  • Message text: An exception already exists for column &1

  • Show details Hide details
  • What causes this issue?

    You cannot create an exception for this column because an exception
    already exists.

    System Response

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

    How to fix this error?

    If you wish to change the existing exception, choose 'Change
    exception'.
    If you really want to create a new exception, you should note that you
    can create only one exception per area of validity. If you have already
    created an exception for column &V1&, you can create further exceptions
    with reference to &V1&, however only based on certain cells.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message KY347 - An exception already exists for column &1 ?

    The SAP error message KY347, which states "An exception already exists for column &1," typically occurs in the context of SAP Controlling (CO) when you are trying to create or modify a report or a planning layout that involves exceptions for specific columns. This error indicates that there is an attempt to define an exception for a column that has already been defined.

    Cause:

    The primary cause of this error is that the system has detected that an exception for the specified column (denoted by &1) is already defined in the report or layout you are working with. This can happen if:

    • You are trying to add a new exception for a column that already has an existing exception.
    • There is a duplicate entry in the configuration of exceptions for that column.

    Solution:

    To resolve the KY347 error, you can follow these steps:

    1. Check Existing Exceptions:

      • Go to the report or planning layout where the error occurred.
      • Review the existing exceptions for the specified column to see if there is already an exception defined.
    2. Modify or Remove Duplicates:

      • If you find that an exception already exists for the column, you can either modify the existing exception to meet your requirements or remove it if it is not needed.
      • Ensure that you are not trying to create a new exception with the same criteria as an existing one.
    3. Adjust Report Layout:

      • If you are working with a report layout, consider adjusting the layout to avoid conflicts with existing exceptions.
    4. Consult Documentation:

      • Refer to SAP documentation or help resources for more detailed guidance on managing exceptions in reports and layouts.
    5. Testing:

      • After making the necessary changes, test the report or layout again to ensure that the error has been resolved.

    Related Information:

    • Transaction Codes: You may be using transaction codes like KSB1 (Cost Centers: Actual Line Items) or KSBP (Cost Centers: Plan Line Items) when encountering this error.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
    • User Roles: Ensure that you have the appropriate permissions to modify reports and layouts in SAP CO.

    If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.

    • 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 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