Enhanced Retrofit: CSOL Lock exists but critical retrofit still available

[Former Member]

Hello experts,

I am having some trouble with retrofit.

I have implemented this functionality on SolMan 7.1 SP13, and created a test landscape.

I created a change doc and made a new customizing entry.

No conflict detected : Critical retrofit is working very well

Now I want to test the BC-Set.

I modify my previous entry in a new change document.

CSOL pops ups, I ignore

I check in /TMWFLOW/LOCKMON

There is an entry for my document:

When changing the status on my change document, I have to ignore the DGP checks.

So everything is fine.

But when I start the retrofit, critical retrofit is still available:

This shouldn't be the case. So, of course, if I try the "Transfer with BC Set", it's not working. Critical Retrofit works despite the conflict !

I have checked if the BC-Sets are created at release, they are not:

And here is the log when I try to do the "Transfer with BC-Sets" Action:

Do you have an idea of what is wrong? I don't think it's an authorization issue. I have a sap all on all involved systems.

Regards,

Roger Tchalla

[rishav54 · Accepted solution]

Hi,

Ensure that user creating the BCset is having Utilities (M)->User settings ->Maint. Transaction->Deletion Functionality is Switch On

Please check if the objects are supported by BC set or not in tcode /nSOBJ

Also please check the user maintained in TMW rfc destination.

Thanks

Rishav

[Former Member]

Thanks to a colleague, I found what was wrong:

And as Rishav said, the user maintained in the RFC of my Retrofit system did indeed not have the rights in SolMan for RFC Access.

So, I had no lock entries in SolMan for my retrofit system. Hence, no BC-SET created.