Last year SAP advised its customers to enable the SNOTE in the ABAP systems for digitally signed notes and change the connectivity methods of SAP systems with SAP support backbone which included the below: For systems with releases SAP_BASIS 740 and above, the HTTPs connections had to be created in the systems to replace the RFC connectivity. For systems with releases SAP_BASIS 700 to 731, SAP advised to continue using the normal SAPOSS related RFCs by replacing the user with

SAP Solution manager work modes are being used frequently by the SAP administrators and SAP Solman consultants to suspend the monitoring alerts of the monitored systems for any maintenance tasks or setting up the daily monitoring hours of the system. SAP has redesigned the IT calendar work center with the easy interface in the latest SPS of the Solution manager 7.2 to create the work modes of multiple systems in a click and easily manage them without the hassle of selecting t

This is the most common error while performing the SAP system copy running on DB2 database. Sample Error: ERROR 2020-10-13 17:58:57.336 (root/sapinst) id=syslib.process.childApplication.notAccessed errno=FSL-04008 Unable to access application /db2/db2<sid>/sqllib/adm/db2set. A file or directory in the path name does not exist. ERROR 2020-10-13 17:58:57.348 (root/sapinst) id=modlib.jslib.caughtException errno=MUT-03025 Caught ::ESyException in module call: At line 1121 file /b

Permanent Fix for very high priority vulnerability in SAP JAVA systems

SAP has finally announced the extension of mainstream maintenance on February 4, 2020 for their widely used SAP Business Suite 7 software until the end of 2027 free of charge to its customers. This is the good news for various organisations who are running the SAP ERP software as they get additional 2 years of mainstream maintenance support for the existing SAP ERP software and can get more time to focus and plan for the S/4 HANA migration strategy and planning. SAP Applicati

If you support a customer who has implemented the transport strategy using Change Request Management in SAP Solution Manager, you might have faced issues while moving the Change documents from one state to next state. In urgent scenarios, you might have to import the transport requests in test or prod systems manually and then would have changed the CD status manually later on. Sometimes this is straightforward but sometimes this can be really complex. I have resolved various

There could be multiple scenarios in SAP CHARM where you would need to manually move the transports in the SAP systems due to various issues in CHARM change documents. If there is a requirement to create a transport request in the development system directly or modify a transport request, you might come across the below error while saving the transport request in development system. You cannot assign any requests to project Message no. CTSPRJ043 Diagnosis You want to create a

Starting from Jan 1 2020, SAP has implemented the new Support Backbone infrastructure and hence, your ABAP systems must be prepared to get connected with the new SAP support backbone. This is required for at least downloading the digitally signed SAP notes in the ABAP systems and maintaining the connectivity related to Early Watch reports of your SAP systems. Pre-requisites and Preparation 1. Prepare ABAP systems SNOTE for Digitally Signed SAP Notes Below is the step-by-step

Recently, we got an issue in our SAP system where the SAP standard job SAP_PERIODIC_ORACLE_SNAPSHOT was failing every hour with system dump DBIF_RSQL_SQL_ERROR. The dump had the database error text as Database error text........: "ORA-01115: IO error reading block from file (block # )#ORA-01110: data file 30: '/oracle/<SID>/sapdata1/sr3_23/sr3.data23'#ORA-27072: File I/O error#Solaris-AMD64 Error: 5: I/O error#Additional information: 4#Additional We suspended the SAP job SAP_

SAP schedules minimal maintenance activities on the backbone systems which may result in the unavailability of the SAP support portal services, One support Launchpad ,SAP service marketplace etc. Generally, SAP broadcasts a user message on the portal advising the users about the current maintenance activity in progress which might impact the users while accessing the support portal for searching SAP notes, opening the OSS connections, registering SAP licenses etc. It gets rea

Purpose The purpose of writing this blog is to provide screen by screen procedure of enabling the long running job alerts through SAP solution manager 7.2. You can setup the alerts for long running jobs ( for example, running more than 2 hours) in sm37 of managed system. There are sometimes requirements from the customers to enable these alerts for the critical jobs monitoring , when they would like to take some actions if there are delays in the completion of specific jobs (

Purpose The purpose of writing this blog is to provide screen by screen procedure of the sapjvm patch update using the SUM (Software Update Manager) tool. SAP has now replaced all the deployment tools for java based systems with one standard tool which is SUM to update the patches. If you want to switch to sapjvm 4.1 from vendor jdk using sapjvm switch tool, please refer to below blog Sapjvm 4.1 switch procedure Check Existing sapjvm build version and compatibility 1434916-

Purpose SAP has issued a recent security advisory mail to the customers in May 2019 with subject line " SAP Security Advisory – Patch Your SAP Landscape and Ensure Secure Configuration" to remind the customers of implementing the gateway and message server security recommendations already provided by SAP long time ago. You can check the advisory at below URL SAP security advisory notice The purpose of writing this blog is to provide the list of tasks that need to be performed

Step by step guide to enable the digitally signed notes downloads and TCI in SNOTE for SAP support backbone changes