Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix SCPR359 - Complete activation not possible because of system settings


SAP Error Message - Details

  • Message type: E = Error

  • Message class: SCPR - BC Sets

  • Message number: 359

  • Message text: Complete activation not possible because of system settings

  • Show details Hide details
  • What causes this issue?

    You want to activate one or more BC Sets, but system settings, e.g.
    system and client changeability, prevent the activation of some or all
    of the customizing objects which were specified in the BC Sets.

    System Response

    The data assigned to these objects is not activated.

    How to fix this error?

    Check which BC Sets and customizing objects are affected. In a dialog
    activation (transaction SCPR20), the BC Sets and customizing objects
    affected are specified in the activation log and the detail display in
    the Activation Selection screen. To create an activation log for a
    dialog activation, end the activation with the creation of a log. The
    system creates an activation log automatically for background
    activation. You can also call the activation log later.
    Change the system settings. You can then activate the objects.

    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 SCPR359 - Complete activation not possible because of system settings ?

    The SAP error message SCPR359 indicates that a complete activation of a transport request or a change is not possible due to certain system settings. This error typically arises in the context of the SAP Change and Transport System (CTS) when there are issues with the configuration or settings of the system that prevent the activation of objects.

    Causes:

    1. Transport Layer Configuration: The transport layer may not be correctly configured for the system. This can happen if the transport layer is not assigned to the correct system or if there are inconsistencies in the transport routes.

    2. System Settings: Certain system settings may prevent the activation of changes. This could include settings related to the transport directory, transport routes, or system authorizations.

    3. Missing Authorizations: The user attempting to perform the activation may not have the necessary authorizations to activate the changes.

    4. Transport Request Status: The transport request may be in a status that does not allow for activation, such as being in a "modification" state or not being released.

    5. Dependencies: There may be dependencies on other objects or transport requests that have not been activated or are in an inconsistent state.

    Solutions:

    1. Check Transport Layer: Verify that the transport layer is correctly configured. You can do this by checking the transport routes in transaction STMS and ensuring that the transport layer is assigned correctly.

    2. Review System Settings: Check the system settings related to the transport directory and ensure that they are correctly configured. You can use transaction RZ10 to check profile parameters.

    3. User Authorizations: Ensure that the user has the necessary authorizations to perform the activation. You can check the user's roles and authorizations in transaction SU01.

    4. Transport Request Status: Check the status of the transport request in transaction SE09 or SE10. If the request is not released, release it and try the activation again.

    5. Check Dependencies: Review any dependencies that may exist for the objects being activated. Ensure that all required objects are in the correct state and have been activated.

    6. System Logs: Check the system logs for any additional error messages or warnings that may provide more context about the issue. You can use transaction SM21 to view the system log.

    7. Consult SAP Notes: Look for relevant SAP Notes that may address this specific error message. SAP Notes often provide solutions or workarounds for known issues.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as STMS (Transport Management System), SE09/SE10 (Transport Organizer), and SU01 (User Maintenance).
    • SAP Documentation: Refer to the official SAP documentation for detailed information on the Change and Transport System and troubleshooting transport-related issues.
    • SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered similar issues.

    If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or consult SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


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