SAP – RSLOGSYSDEST Table update

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.

RSAR_UPDATE_RSLOGSYSDEST

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 –

https://wiki.scn.sap.com/wiki/display/BI/SM13+and+update+mechanism+overview

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 –
MDG_BUS_SYS_TECH
COMC_PR_LOGSYS

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.

SAP : SPOOL_INTERNAL_ERROR

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.

SAP Diagnostics Agent disconnect from Solution Manager 7.2

if you are facing issue where all DIA agents are getting disconnected from Solution Manager 7.2 due to error “Exception occurred” or “Processing RMI-P4 request failed. There are no resources to handle the request”. This means there are no more P4 threads are free to handle the request.

This issue is usually occurred in big landscape where more then 600-700 DIA agents are there.

P4 thread usage can be monitor via below method –

telnet localhost 5instance_number08
add p4
p4info

If the displayed value of the “Thread usage” stays at 100% for several minutes so there is an requirement to adjust/increase the threads/queue.

P4 Thread & Queue request size can be calculate as per below Blog –

https://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+7.2+Troubleshooting#DiagnosticsAgent7.2Troubleshooting-scalability

Section – Connectivity Instability in Huge Landscapes – Quick Sizer Tool

There is an attached excel document which give you the correct parameters details as per DIA agents numbers.update the same in your landscape & restart the Java Instance.

References –

https://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+7.2+Troubleshooting#DiagnosticsAgent7.2Troubleshooting-scalability

SAP Note – 2370752 – Diagnostics Agents do not connect to SAP Solution Manager 7.2 due to error in the Default Trace ”Processing RMI-P4 request failed. There are no resources to handle the request.”

SAP also recommend to update the LM-SERVICE patch to latest one to avoid the disconnection issue & also implement Lightweight Ping note as below –

2599110 – Lightweight Ping

2574270 – LM-SERVICE 7.20 SP06 Patch 2

2599110 – LM Service Patch Update

SAP – Unable to create new native thread

Whenever you face this issue in ABAP or JAVA system where your system is not starting up & dumping out by error “unable to create new native thread”.

Please crosscheck the below OS values, this should be set to high/unlimited.

My Suggestion is below –

For Linux – limits or csh -c limits

maxproc – unlimited
descriptors – 65536
stacksize – 32768

after changing these values restart the application server & check.

for More information, follow below SAP notes –

1827960 – Adjusting operating system limits for SAP instances
1847508 – Unable to create new native threadVersion 5 from 26.09.2018 in Eng
1496410 – Red Hat Enterprise Linux 6.x: Installation and Upgrade

How to boost Android Performance

Some months before I have purchased Samsung mobile with 3 GB RAM, initially it was working good as expected but after some time it’s start lagging & responding very slow. I tried uninstalling application & daily cleaning up the memory but that is also not helpful.

Then I start digging some of the options & found below 3 options in “Developer Tools” in Android that can be disable to boost up the speed.

Goto — Settings —- Developer Options (if it’s not enable then there are lot of videos / blogs for the same or easy way to enable “Tap 7 times on your Build Version” under details & option will be now visible.)

Please Note – Don’t Play with Developer options, it may damage your phone. Better to hide the same again after doing above steps.

After disabling above 3 options start using your phone normally & now you can see performance the mobile is now change & responding quickly as new 🙂

SAP – RSTBPDEL – Delete Table Logs

Hi All,

RSTBPDEL is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). This report deletes change documents from the table log database. if you are facing issue while deleting the table logs (job completed successfully but no reduction in DB or table logs) as per SAP note – 2388295 – RSTBPDEL | Delete logs periodically.

SAP released another note for resolving this issue – 2634844 – Deletion program RSTBPDEL not deleting data of table logs.

This note need to implement via SNOTE in all the impacted systems & this will also introduce a new authorization object. Once SAP note has been implemented re trigger the job again & see the difference now.

SAP S4 HANA 1809 Release

SAP has released the S4HANA 1809 for their customers.

There are many blogs which are explaining the features of new version.

The best thing what I have seen is from SAP is the tutorial Library & repository for 1809 version. it’s very much beneficial for new & existing S4 HANA users as it’s providing the examples of multiple technical & functional activities.

Click below for access the URL

https://education.hana.ondemand.com/education/pub/s4/index.html#group!GR_D80CA75852B82A9D”>https://education.hana.ondemand.com/education/pub/s4/index.html#group!GR_D80CA75852B82A9D