3780283 - cannot set abap breakpoints or debug in non-development client (authorization error s_develop); cross-client debugging not possible; s/4hana cloud public edition

• Breakpoints set in the abap development tools (adt) project for the development client do not stop when running objects in a different client (for example, client 100).
• When trying to Toggle ABAP Breakpoint directly in the non-development client adt project, activation is blocked with error: "You are not authorized to change (Authorization Object S_DEVELOP)"
• Users cannot debug abap cloud repository objects in the non-development client until appropriate authorizations are in place.
• In a related scenario, a generated pdf form output was empty (0kb), and debugging of the form logic was needed but not possible due to the above.

• Product: SAP S/4HANA Cloud Public Edition
• Installation and infrastructure for ABAP tools in Eclipse

1. Develop abap cloud objects in adt while connected to the development client.
2. Run or test the deployed object in a different (non-development) client, such as client 100.
3. Observe that breakpoints set in the development client do not stop for processing in the other client.
4. Create an adt project that logs on to the non-development client and attempt to toggle a breakpoint.
5. Receive authorization error "Object could not be locked Reason: You are not authorized to change (Authorization object S_DEVELOP)".

• Cross-client debugging is not supported; a process running in one client cannot be stopped by a breakpoint set from a different client.
• Users in the non-development client were missing the required supporter authorizations to log on with adt and set/debug breakpoints (authorization object S_DEVELOP and related support permissions).

1. In the target (non-development) client, create a custom supporter role based on role template SAP_BR_APPL_SUP_ENG_DEV_SUP. Do not use the template directly; copy it to a Z-role and adjust as needed.
2. Assign this custom supporter role to the users who must debug in that client.
3. Have each user create a separate adt project that logs on directly to the target client using their user for that client.
4. Set and use breakpoints within the adt project connected to the target client. Do not attempt cross-client debugging.
5. If authorization errors persist after role assignment, wait briefly to allow buffers to refresh, then restart the adt project connection and try again.

adt, abap, breakpoint, s_develop, authorization error, object could not be locked, 您無權更改, cannot set breakpoint, debug non-development client, client 100, cross-client debugging, supporter role, sap_br_appl_sup_eng_dev_sup, eclipse, public cloud , KBA , BC-DWB-AIE , Installation and infrastructure for ABAP tools in Eclipse , Problem