SAP: Digitally Signed SAP Note Support

As per SAP Blog, Jan 2020 onward download & upload process of SAP note from SNOTE transaction will stop until unless SNOTE is enabled in ABAP systems to with Digitally signed SAP Notes.

This is the secure method to download the SAP notes & all SAP note will get download only as SAR files.

Below are the SAP note which is helpful for Configuring the same.

Enable Note Assistant (SNOTE) for downloading and uploading digitally signed SAP Notes,
please implement SAP Notes 2408073, 2546220 and 2508268.

2576306 – Transport-Based Correction Instruction (TCI), it contains the SAP Notes 2408073, 2546220 and 2508268. If the SNOTE in your ABAP system is already enabled for TCI, It is recommended to implement only TCI SAP Note 2576306 instead of applying the above individual SAP Notes.

You can download the instructions from Support Portal with Subject – SAP Note Transport-Based Correction Instructions.

SAP: What is SAPCPE & Usage of SAPCPE

SAPCPE is an program which exists in your Kernel folder. it helps to copy kernel binaries from one location to another exe location.

Whenever we run the “STARTSAP” command, SAPCPE copy or verify the kernel binaries from “CDEXE” location to Instance/exe. it depends whether how much instances you have including ASCS/SCS, ERS & Gateway.

When we perform Kernel Upgrade activity we update the kernel patch level on “CDEXE” location & rest other location are having the old version of kernel. if we want to update the kernel patch level in Instance EXE before starting the system then we can perform the same via SAPCPE manually.

For doing this, we need to find the respective instance profile & run the below command.

Example –

sapcpe pf=/usr/sap//SYS/profile/Instance_Profile

Once you trigger the above command it copies the required binaries from CDEXE location to respective profile instance directory/exe & update the kernel.

How it Works Internally

There are some LST files exists in the kernel directory(CDEXE) where it read the LST file to copy the same. we have separate LST file for Instance, ERS, ASCS/SCS & Gateways. These LST files are mentioned in the respective profiles.

For Example –

sapcpe pf=/usr/sap//SYS/profile/Instance_Profile

When you run the above command SAPCPE read the Instance_Profile & find out the LST file mentioned in profile & based on this LST file, it transfer the respective binaries only from CDEXE to Instance Directory/exe.

The same procedure also happen when you trigger the STARTSAP.

I hope this clarifies the SAPCPE usage.

SAP – IGS failing with RFC External Failure

Recently we have faced issue where IGS stopped working after BW system restart. As our BW system is connected to Portal & it’s throwing error while generating reports.

We have checked that IGS RFC is working fine in SM59 – TCP/IP but when we run the report in SA38 – GRAPHICS_IGS_ADMIN. it’s failing with error “RFC_EXTERNAL_FAILURE”.

By going through the multiple log files, we identify that it’s failing as IGS is not able to bind the DEFAULT Port.

Port 4NN01 and 4NN02 where NN is the instance number

Due to this it’s not connecting to IGS server. We followed SAP note – 2719952 to resolve the issue.

We change the IGS default port to customize & restart the system.

Example as below –

igs/listener/http = 40085
igs/mux/port = 40005
igs/pw/1 = 40006,7
igs/pw/2 = 40008,9

By changing above now IGS is listening to different Port & RFC & Reports are working fine.
Hope this Helps.

SAP : JAVA Transport failing with Internal Server Error HTTP Code 500

Recently we are facing a issue where all BPM transport import is failing in PO JAVA system with below error –

WS Execution Error in CDTDEPLOY_DI (cx_ai_system_fault)
SOAP:1007 SRT: Unsupported xstream found: (HTTP Code 500 : Internal Server Error)
Error when processing Web Service Call

Connectivity for PO Java system is as below –

Solution Manager ——–> NWDS ———> SAP PO (JAVA)

Transport import from Solution Manager (CTS+)

The above transport is failing on Pre Prod system but it’s successfully completing in QA system so with same configuration & same NWDS system.

We followed SAP note – 1139406 but it didn’t help us there was no configuration change in the system because it’s deploying successfully in QA. We did restart PO multiple times but that also not help us.

we again trigger the transport & saw the below error in Developer Trace while transport is running.

ClientServerException exception:Write object <> failed! Caused by: lock 14051311214586500000pwdf5674……………….18228850,J2EE_CONFIGURATION_MANAGER,22352127/cb1c722f/30c4e431/18064/2dca72/6f336575/573c0b09/abe4c6a3/8f4414e3…]; it is in use by another owner. The lock collision occurred with user .

There is an standard SAP note for the same issue – 2023974 – Write object failed – Cannot lock as it is in use by another owner.

We followed the SAP note as it’s saying to delete the JAVA locks from PO system & re import, after deleting locks from PO system we again restart the PO & NWDS system again & then import the same, now this time it’s successfully imported in the system.

Reference note for JAVA system performance
2579836 – AS Java system has performance problem – FCAException – Best practices and tuning recommendations

SAP:Cannot import instance profile via RZ10


Recently after system we are facing below issue while importing the Instance Profile from SAP in RZ10 Tcode.

While multiple restart & also changed the profile authorization to 777 that also doesn’t work.

There is an SAP Note – 2157878 which describe the solution for this error, however in our case that we need to change profile parameter in START profile(if start profile is separate then Instance) & also change the entry in /usr/sap/sapservices file.

Correct Entry

Adjust /usr/sap/sapservices, change /sapmnt//profile/ to /usr/sap//SYS/profile/

After updating above 2 entries & then restart the application server by killing the SAPSTARSRV process, that resolve the issue & we are able to import the profile in RZ10 successfully.

Hope this Helps.


Recently after BDLS we have seen in our BW system that some of the logical system entries in table – RSLOGSYSDEST didn’t change to QAS/Pre Prod & still pointing to production.

BW team was facing some issue & request us to change the table entries manually to QAS/Pre Prod.

As we have already closed the client to – No changes allowed, it’s not allowing us to change directly in table from SE16.

we have found another way to change the same from SE37 – Execute Function.


This Function will update the table as per our requirement by giving the new value.

SAP SM13 Update Mechanism for V2 Updates

Recently we have faced a big issue in our ECC System where all V2/V3 updates get stuck in SM13 & not processing further.

All update are in the condition of Collective Run –

SM13 -> V2 -> Update Modules: MCEX_UPDATE_03 Collective Run Initial

Manually Reprocessing is also not helping us.

We have raised High Severity call to SAP & SAP provide us to run the report “RMCSV3VB”. we ran the report once & all stuck V2/V3 updates get cleared from SM13 & place in SM58 for further processing but the problem is new updates are still not processing from SM13.

We have discussed the same to SAP & SAP suggest to schedule this report to run as per your requirement for processing updates & they also confirm that there is no harm while running this report in the system.

Please make sure to run & schedule this report from SM36 via BATCH user (full authorization). This Job will complete it in some seconds but this will trigger any BG process to trigger the updates.

Reference Blog –

BDLS Conversion failed for some tables

Recently while working on System Refresh for Global Batch Trade system, we have observed that even though BDLS completed successfully but still it skipped some of the important tables of the system & due to this, it’s impacting the functionality of GBT.

we are not able to assign QAS logical system on Tcode – /GBT/LOGSYS_CONFIG & it’s throwing dump “Duplicate entry”. we found that we have PRD logical system entry in table – MDG_BUS_SYS_TECH (even BDLS completed successfully earlier for respective logical system).

Tables –

There is on SAP Note 1637676 – (BDLS Manual correction required or Manual Conversion required) which is helpful to understand the scenario & take corrective actions.

Table – COMC_PR_LOGSYS has multiple entries (PRD & QAS) both & there is no way to delete the PRD entry from the table. The alternate method to remove the entry is from SPRO.

SPRO – Cross Application Components – SAP Product – Basic Settings – Define Output Format and Storage Format of Product IDs

Edit the above field after opening the client & remove the PRD logical entry, close the client.

Inform Functional Team to perform their functional tests.


SPOOL INTERNAL ERROR is very common in SAP landscape. whenever spool reaches to their limit so it’s start failing the jobs & prints & due to this everything get stopped in SAP system.

SAP is having a default limit of 32000 spool in SAP system as per SAP Note 48284.

You need to check the limit by logging into 000 client – SNRO – Object – SPO_NUM & check interval.

if there is an heavy usage of SPOOL in your organization. you can use 2 things to resolve the issue.

1. Schedule daily cleanup job (RSPO1041) in the system with variant value less then 7 days.
2. Increase the limit of spool count from 32000 to 60000.

if you system is having this issue & you are not able to run the report in background, then delete the old spool in DIALOG mode for temporary cleanup via SPAD. once it’s clean then you can schedule the job again with change variant.

SAP – Enable TLS in SAP ABAP & JAVA Application Servers

Enabling TLS & SSL protocol in SAP ABAP & JAVA Application Servers.

Follow below SAP notes –

2384243 – NetWeaver Application Server: How to configure strict TLS 1.2
510007 – Setting up SSL on Application Server ABAP
2110020 – Enabling TLS or disabling SSLv3 protocol versions on SAP WebDispatcher, or SAP WebAS (AS ABAP 6xx, 7xx or AS Java >= 710)

There are other blog also which are explaining of this process but the above SAP notes are sufficient to complete the process.