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.