How To Fix SCTS_HDI702 - HDI object is checked out in SAP Web IDE (see long text)


SAP Error Message - Details

  • Message type: E = Error

  • Message class: SCTS_HDI - Messages for CTS HDI API

  • Message number: 702

  • Message text: HDI object is checked out in SAP Web IDE (see long text)

  • Show details Hide details
  • What causes this issue?

    The HDI object is currently checked out in ABAP Development Tools (ADT)
    for editing in SAP Web IDE for SAP HANA.

    System Response

    The system displays an error message. However, you can edit the HDI
    object. Be aware that if you change the object here, and it was also
    changed in SAP Web IDE, parallel changes and hence conflicts occur.

    How to fix this error?

    We recommend that you check the state of the object in ADT before you
    edit it here. To avoid conflicts, the state in ADT should be <LS>In Sync
    </>. If necessary, contact the user who checked out the HDI object in
    ADT for editing in SAP Web IDE, or ask the user to check in the current
    changes so that your changes here will be based on the latest version of
    the object.
    If you edit the HDI object now and save your changes, the following
    situations can occur:
    If the object is checked out to SAP Web IDE and was not yet modified
    there, but it is edited here and deployed using HTA for HDI -
    Deployment, the state in ADT will be <LS>Modified in ABAP</>. The user
    who checked out the object to SAP Web IDE should check out the object
    again as soon as possible after the deployment using HTA for HDI -
    Deployment. If you have permission to check out the object using ADT,
    you might also do this yourself.
    If the object is checked out to SAP Web IDE and was modified there, and
    it is edited here and deployed using HTA for HDI - Deployment, the state
    in ADT will be <LS>Conflict</>. This state will prevent check in,
    because this can lead to a downgrade. In this case, the only option to
    solve the conflict is <LS>check out</> in ADT. During check out, a copy
    of the SAP Web IDE object version is created as a backup file (.bck),
    and the version created in the Editor for HDI Objects will replace the
    previous version that was edited in SAP Web IDE. The user who checked
    out the object to SAP Web IDE can then compare the backup file with the
    checked-out file and manually merge the two versions. Afterwards, the
    object can be checked in again. Do not forget to delete the backup file
    after merging the two versions.
    If the object is checked out to SAP Web IDE and was deleted there, and
    it is edited here and deployed using HTA for HDI - Deployment, the state
    in ADT will be <LS>Modified in ABAP</>. The user who checked out the
    object to SAP Web IDE must recreate the file with same name again (an
    empty file is sufficient), and then check out the ABAP version of the
    object to SAP Web IDE. This will create a backup file as described in
    the previous point. If you want the deletion of the object to be the
    final version of the object, you must delete the object again in SAP Web
    IDE and build this change. If you want to keep the checked-out object
    version from ABAP, you don?t need to do anything. In any case, do not
    forget to delete the backup file when you are sure you no longer need
    it.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message SCTS_HDI702 - HDI object is checked out in SAP Web IDE (see long text) ?

    The SAP error message SCTS_HDI702 indicates that an HDI (HANA Deployment Infrastructure) object is checked out in the SAP Web IDE. This typically occurs when a developer has checked out an object for editing, and another user or process is attempting to perform an action on that object, such as deploying or modifying it.

    Cause:

    1. Checked Out State: The object is currently checked out by another user or process, which prevents other users from making changes to it.
    2. Session Timeout: If a user has checked out an object and their session times out without checking it back in, the object remains checked out.
    3. Concurrent Access: Multiple users trying to access the same HDI object simultaneously can lead to this error.

    Solution:

    1. Check In the Object: If you have access to the SAP Web IDE, check in the object that is currently checked out. This will release the lock and allow other users to access it.
    2. Contact the User: If you know who has checked out the object, you can contact them to check it back in.
    3. Force Check In: If the user who checked out the object is unavailable, you may need to use administrative tools or commands to force the check-in of the object. This typically requires appropriate permissions.
    4. Wait and Retry: If the object is checked out temporarily, you may need to wait until the user checks it back in and then retry your operation.

    Related Information:

    • SAP Web IDE: This is the development environment where HDI objects are created and managed. Understanding how to navigate and use this tool is essential for managing HDI objects effectively.
    • HDI Objects: These are database artifacts managed by the HANA Deployment Infrastructure, which includes tables, views, procedures, and more.
    • Version Control: Familiarize yourself with version control practices in SAP Web IDE to avoid conflicts and manage object states effectively.
    • Documentation: Refer to the official SAP documentation for more details on HDI and the specific error messages related to it.

    If the problem persists after trying the above solutions, consider reaching out to your SAP support team 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