Go to Options:

Tick this checkboxes:

Go to Options:
Tick this checkboxes:
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:
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:
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:
Regedit:
Hive: HKEY_CURRENT_USER
KeyPath: Software\SAP\SAPGUI Front\SAP Frontend Server\LocalData\
Value Name: FieldLenHistoryOn
Value Type: REG_DWORD
Value Data: 000000FF (255)
Action: Replace
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.
Profile Name | Description |
SAP_2SL_TO_3SL | 2 System Landscape to 3 System Landscape Converter |
SAP_CLIENT_BACKUP | Client Backup including Temporary Data |
SAP_INITIAL_CLIENT | Provisioning of Users and Customizing |
SAP_TENANT_MOVE | All Tables incl. Temporary Data and Change Docs |
SAP_ALL | All Client-Specific Data w/o Change Documents |
SAP_APPL | Customizing and Application Data w/o Change Docs |
SAP_APPX | SAP_APPL w/o Authorization Profiles and Roles |
SAP_CUST | Customizing |
SAP_CUSV | Customizing and User Variants |
SAP_CUSX | Customizing w/o Authorization Profiles and Roles |
SAP_PROF | Only Authorization Profiles and Roles |
SAP_RECO | Recovery (Only if Source Client = Target Client) |
SAP_RMBC | Customizing, Users and Cross-Client Customizing |
SAP_RMPA | SAP_ALL with Cross-Client Customizing |
SAP_RMPC | Customizing Including Cross-Client Customizing |
SAP_UCSV | Customizing, User Master Records and User Variants |
SAP_UCUS | Customizing and User Master Records |
SAP_UONL | User Without Authorization Profiles and Roles |
SAP_USER | User Master Records and Authorization Profiles |