SAP:Cannot import instance profile via RZ10

Hello,

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
DIR_PROFILE = $(DIR_INSTALL)$(DIR_SEP)profile

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.

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

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 S4HANA – Define Background Job – Job Repository

Hi All,

Recently while working on Background Job Management for SAP Netweaver 751 for S4HANA, we discovered that there is a small change in Background Job Scheduling via SM36- Job Repository (Technical Job Repository) or SJOBREPO Tx.

The change is if you have scheduled any background job via Job Repository then you only can change the status (Scheduled/Remove) of that particular job from Job Repository only.

for Example – SAP_REORG_APPLJOBS – if you have activated this job via Job Repository then making changes of this job directly in SM37 will not work, like variant change, release to schedule status or remove. if you perform any action directly in SM37 then this change happen for the time but again after some minute the job will reappear with the release status as it’s still active in Job Repository.

if you change the variant directly in SM37 then there will be 2 job will appear, 1 is with New Variant & 2 is old default variant.

The last option for stopping this job permanently via SM36 – Job Repository – Select the Job & Click Deactivate Technical Job Definition Locally.

Once you perform this action the default job will stop permanently in the system. if you have created any modified job in the system (new variant) that job will run as per their scheduled time.

SAP SUM Error: Unable to find delivery event

Hi All,

Recently while patching & migration to HANA of Solution Manager 7.2, we have faced the below error in Configuration Phase –

Error in PREP_EXTENSION/CPK_INCLUSION

To Fix this issue, please follow below steps –

1. Please check the error – Unable to find delivery event XXXX XXXXXXXXXXX
2. Login into the system – SE16 – CWBCMPNT – Package – XXXX (Find the Component)
3. Once component is identified then login into SAP Launchpad & search for any note related to the component with respective system release.
4. Download the SAP note via SNOTE (No need to implement the note)
5. Repeat the SUM Phase

Please follow this SAP Note for more details – 2527823 – Error in CPK_INCLUSION during SUM: Unable to find delivery event