How To Fix K6035 - No data slice exists for the data to be updated.


SAP Error Message - Details

  • Message type: E = Error

  • Message class: K6 - EC-EIS/EC-BP data basis: Data entry and collection

  • Message number: 035

  • Message text: No data slice exists for the data to be updated.

  • Show details Hide details
  • What causes this issue?

    The system settings do not contain a data slice that determines, for
    the selected data, whether an update is allowed.

    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?

    Change either your entries or the selection criteria for the locked
    <DS:CHAP.SIMG_CMMENUOKCMSL>data slice</>.

    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 K6035 - No data slice exists for the data to be updated. ?

    The SAP error message K6035 ("No data slice exists for the data to be updated") typically occurs in the context of SAP Controlling (CO) when you are trying to update or post data to a CO object (like a cost center, internal order, etc.) but the system cannot find a corresponding data slice for the specified period or object.

    Causes:

    1. Missing Data Slice: The most common cause is that there is no data slice available for the specified period. This can happen if the data has not been initialized or if the period is closed.
    2. Incorrect Period: The period you are trying to post to may not be open for posting in the controlling area.
    3. Configuration Issues: There may be configuration issues in the controlling area or the specific CO object you are working with.
    4. Authorization Issues: Sometimes, the user may not have the necessary authorizations to access or update the data slice.

    Solutions:

    1. Check Data Initialization: Ensure that the data slice for the relevant period has been initialized. You may need to run the initialization process for the CO object.
    2. Open Period: Verify that the period you are trying to post to is open for posting. You can check this in the controlling area settings.
    3. Review Configuration: Check the configuration settings for the controlling area and the specific CO object to ensure everything is set up correctly.
    4. Authorization Check: Ensure that the user has the necessary authorizations to perform the action. You may need to consult with your SAP security team.
    5. Transaction Codes: Use transaction codes like KSB1 (for cost centers) or KOB1 (for internal orders) to check if the data exists for the specified period and object.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes in SAP CO, such as KSB1, KOB1, and KSV5, to analyze and troubleshoot the data.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
    • Documentation: Review SAP documentation for Controlling to understand how data slices work and how to manage them effectively.

    If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or refer to SAP's official support channels 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