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

When you export a report from SAP to MS Excel this error may occur. New MS Office update prevents running unsigned VBA scripts.

You need to upload new templates to SAP. The problem is that SAP uses several templates for different cases. I found it for Report Writer and EHS Excel. The notes mentioned below might help you. You just need to download these new templates and upload them according to the notes information. In addition, you need to download new SAP certificates for digitally signed VBA scripts. It’s needed to upload to each workstation in Trusted Publishers. Group policy can be used to automate it.

Transaction OAOR:
Class name: REPORTWRITER
Class type:OT
https://me.sap.com/notes/1992004
https://me.sap.com/notes/0003261967

Class name:EHSEXCEL
Class type: OT
https://me.sap.com/notes/2594418
https://me.sap.com/notes/3247649

G5S-API(maj): Miscellaneous failure
GSS-API(min): A2210223:Server does not trust my certificate path
target='p:CN=<SID>, OU=SAP-HEC, O= SAP SE, C=DE*
Error in SNC
Do you want to see the detailed error description?

There is an SAP note for this problem, but it didn’t help me:
https://userapps.support.sap.com/sap/support/knowledge/en/2516117

The resolution was simple, I checked my SPN records by typing the command:
setspn -L SSO-ABAP-<SID>

And I got an expected error:

FindDomainForAccount: Call to DsGetDcNameWithAccountW failed with return value 0x00000525. Could not find account SSO-ABAP-<SID>.

The answer is: Check your technical account that is used for SAP Kerberos SSO. It might be locked in MS Active Directory.

In my case, this account was simply locked by AD security script.

Ensure you didn’t check the box “Save output as file”, thinking it sends a copy to a file. In fact, it redirects all printing to a file, despite the fact you are able to see in the Windows print spooler: “Printed successfully”.

By the way, with the release of 7.6 SAPPDRPRINT is no longer needed, it became a part of SAPSPRINT with the new engine ASPOSE PDF.

Continue reading »

Problem:
No memory on the host. You can’t even reboot the host due to a lack of memory.

Solution:

Trigger OOM-killer by executing these commands:

echo 1 > /proc/sys/kernel/sysrq
echo f > /proc/sysrq-trigger
echo 0 > /proc/sys/kernel/sysrq

Yes, it’s bad, but sometimes you don’t have a choice…