How To Fix FMCU105 - Column number &1 has already been used for entry columns


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FMCU - Customizing for budgeting in FM

  • Message number: 105

  • Message text: Column number &1 has already been used for entry columns

  • Show details Hide details
  • What causes this issue?

    Column number &1 has already been used in the <LS>Entry Columns
    </>view. For a given layout variant and tabstrip, the column numbers
    defined in <LS>Display Columns </>and <LS>Entry Columns</> must be
    unique.

    System Response

    The system cannot save the settings, and will prevent you from leaving
    the current view before the error is corrected.

    How to fix this error?

    Select the line containing the wrong column number and delete it.

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

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FMCU105 - Column number &1 has already been used for entry columns ?

    The SAP error message FMCU105 indicates that there is a conflict in the configuration of your financial management or controlling module, specifically related to the use of column numbers in a report or layout. The message states that a specific column number has already been assigned for entry columns, which means that the system is unable to process the request due to this duplication.

    Cause:

    1. Duplicate Column Assignment: The most common cause of this error is that the same column number has been assigned to multiple entry fields in a report or layout configuration.
    2. Incorrect Configuration: There may be an error in the configuration settings where the column numbers are not unique.
    3. Data Entry Error: During the setup of the report or layout, a user may have inadvertently assigned the same column number to different fields.

    Solution:

    1. Check Column Assignments: Review the configuration of the report or layout where the error occurred. Ensure that each entry column has a unique column number.
    2. Modify Configuration: If you find duplicate column numbers, modify the configuration to assign unique numbers to each entry column.
    3. Test Changes: After making changes, test the report or layout to ensure that the error no longer occurs.
    4. Consult Documentation: If you are unsure about how to change the configuration, refer to SAP documentation or help resources for guidance on setting up entry columns correctly.

    Related Information:

    • Transaction Codes: Depending on the module you are working with, you may need to use specific transaction codes to access the configuration settings (e.g., FSE1, FSE2 for financial statements).
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional context or solutions.
    • User Roles and Permissions: Ensure that you have the necessary permissions to make changes to the report or layout configuration.
    • Testing Environment: If possible, make changes in a testing environment before applying them to the production system to avoid disruptions.

    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