How To Fix KEO406 - Company code &1 is not assigned to a controlling area


SAP Error Message - Details

  • Message type: E = Error

  • Message class: KEO - Enterprise Organization

  • Message number: 406

  • Message text: Company code &1 is not assigned to a controlling area

  • Show details Hide details
  • What causes this issue?

    Company code &V1& is not assigned to a controlling area.

    System Response

    You can only add company codes to the enterprise organization if these
    company codes are assigned to a controlling area.

    How to fix this error?

    Either enter a different company code or assign the company code &V1&
    to a controlling area.

    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 KEO406 - Company code &1 is not assigned to a controlling area ?

    The SAP error message KEO406 indicates that a specific company code is not assigned to a controlling area. This is a common issue encountered in SAP when trying to perform activities related to controlling (CO) that require a valid assignment between company codes and controlling areas.

    Cause:

    The error occurs when:

    1. The company code you are trying to use is not linked to any controlling area in the system.
    2. The controlling area is not properly configured to include the company code.
    3. There may be a mismatch in the configuration settings or data entry errors.

    Solution:

    To resolve the KEO406 error, follow these steps:

    1. Check Company Code Assignment:

      • Go to the SAP transaction code OB62 (or navigate through the menu: SPRO > Enterprise Structure > Assignment > Financial Accounting > Assign Company Code to Controlling Area).
      • Verify if the company code in question is assigned to the appropriate controlling area.
    2. Assign Company Code to Controlling Area:

      • If the company code is not assigned, you can assign it by selecting the appropriate controlling area and adding the company code.
      • Ensure that the controlling area is set up correctly and that it matches the requirements for the company code.
    3. Check Configuration:

      • Ensure that the controlling area and company code are configured correctly in terms of currency, fiscal year variant, and other relevant settings.
      • Make sure that the controlling area is not set to a different type that would prevent the assignment.
    4. Review User Authorizations:

      • Ensure that the user has the necessary authorizations to view and modify the assignments between company codes and controlling areas.
    5. Consult Documentation:

      • If you are unsure about the configuration, refer to SAP documentation or consult with your SAP Basis or FI/CO consultant for guidance.

    Related Information:

    • Transaction Codes:

      • OB62: Assign Company Code to Controlling Area
      • OKKP: Maintain Controlling Area
      • SPRO: Access the SAP Reference IMG for configuration settings.
    • SAP Notes:

      • Check for any relevant SAP Notes that might address specific issues or bugs related to this error message.
    • Testing:

      • After making the necessary changes, test the functionality again to ensure that the error is resolved.

    By following these steps, you should be able to resolve the KEO406 error and ensure that your company code is properly assigned to a controlling area in SAP.

    • 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
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author