If you need in SAP to prohibit the transfer of requests from the DEV system further along the transport landscape, you can create a file for this:

The contents of the file will be displayed during the attempt (unsuccessful) to release the request in the development system.

Transaction SE38 > report BTC_MASS_JOB_CHANGE. Firstly, check with Test Mode.

In addition, you can change variant and traget application server for the jobs.

I would like to use, of course, SSO 3 for MacOS, but..

In SAP GUI for JAVA (MacOS), you can create a shortcut and save your login and password.
It’s convenient to drag it into the dock for a quick start:

1. Right-click in the SAP GUI on the desired system > Save Connection Data as Document, save it somewhere
2. Find this file and open it with a text editor
3. Add data to the connection string (enter your user= and pass=):
   conn=/H/hostname.domain.com/S/3200&expert=true&user=ikostylev&pass=MYPASS&clnt=100
4. Save, drag the file to the dock on the right side
   It is not safe to store passwords in clear text, but if you really need to, you can.

For security, encrypt the disk by enabling FileVault.

A story that happened with me once…
After switching from release 46 to release 50, an unpleasant thing was discovered – a strange memory leak, and it happened exclusively on Mondays. The switching would be due to the fact that SP05 uses memory much more economically compared to SP04 (Note 2808956 about the Pool/L/llang/Debuggee problem). The problem occurred on Mondays immediately after running the background job /BDL/TASK_PROCESSOR. This background job is responsible for EWA purposes.

After this background job, the memory of dpserver, xsengine and docstore starts to expand:

The solution was found in note 2955475, it says that you need to update ST-PI, but in fact it was necessary to update both ST-PI and ST-A/PI to the latest version. Which is logical, because these components participate in EWA and work in pairs.

Have you set the table data elements to be output to ALV, but for some reason the old or empty column headers are being output? Database utility didn’t help?
Use one of the following programs to clear the ALV buffer:

• BALVBUFDEL
• BCALV_BUFFER_DELETE
• BCALV_BUFFER_DEL_SHARED

SAP Logon field entry history has a length limit. So, if the input field is 255 characters long, the input history for it will not be saved. By default, history is saved for fields that are 49 characters long. This can be fixed by setting or group policy:

Please keep in mind that you cannot fill a client with profile data, for example, SAP_CUSV (settings and options) and expect that the application data in this client will remain old. No, they’ll just wear out. When copying, you can use copy profiles that simplify selection and combination of the objects to be copied. SAP delivers the following copy profiles in the table below. The customizing and application data is deleted in the target client before copying for all profiles except SAP_USER. This is technically unavoidable.

It is one of the key system performance indicators that can be found in
ST03n transaction > Detailed Analysis > Last Minute’s Load:

Average response Time/Dialog Step (ms) =
Avg. Processing Time + Ø DB Time (ms) + Ø Time/DB Procedure Call (ms) + Average Wait Time per Dialog Step (ms) + Average Roll In Time (ms) + Average Roll Wait Time (ms) + Average Load and Generation Time (ms) + Average Lock Time per Dialog Step (ms)

*Particularly significant components are highlighted in bold