RSB4HTRF - any log table available that store the errors or logs

[former_member367612]

Hello all,

i am working on a B4HANA migration project where i am using an in place conversion option to migrate the dataflows in the system. when i execute the tcode RSB4HTRF it generates a task log with errors. i wanted to know if there are any statistic or log tables where these logs are stored . Second thing is the objects listed in the error log are not related to the scope that i have defined and in some cases the Objects do not exist in the system at all like in my case in have a list of infopackages displayed as errors and it is not present in the system. so would like to know if anyone has an idea on how these objects are being picked up and is there any way to get rid of them from the tool since they are not related to my scope.

thanks.

[former_member254739]

hi ,

You can also check the logs in SLG1 with the below selections or with the transaction code as RSB4HTRF.

Object________________ RSD (BW Data Basis)Subobject_____________MIGRATION (Heterogeneous System Migration)

Best Regards

Bhavani

[Former Member]

Hello Saleha,

If I understand the question correctly you receive an error while executing task list SAP_BW4_TRANSFER_INPLACE.

A task list execution generates a task list run with a name like: SAP_BW4_TRANSFER_INPLACE_20180718065827195. You can look the past executions up (with their logs) in transaction STC02 (either by the exact task list run's name or by the executing user for example).

Regarding your second question about the scope: if you select an object to be transferred, at least the dependent objects must be transferred also (you have to option to choose "minimal scope" to limit this).

There is a detailed example in the Conversion Guide under the part: "4.7.2 Perform a Scope Transfer", you can find the documentation here:

https://help.sap.com/doc/c3f4454877614bc7b9e85ae1f9d1d2c7/1.0/en-US/SAP_BW4HANA_10_Conversion_Guide....

Regarding the infopackages which do not exist in the system but end up in the scope: it's hard to tell at the moment what causes this. 🙂 This might be something that has to be looked at in the system (if the scope transfer documentation about dependencies above does not answer the question).

Best Regards,
Szabolcs Cseh
SAP Product Support