Hello all,
this is the reply from SAP. We've disabled the BADI and then the issue was solved:
Dear customer,
the system disables the menu link to FD33 from classic credit
management because it thinks that the new FSCM Credit Management is
active.
We have made a check which disables the classic credit management for
the case that our product is active. With implementing the BADI
UKM_FILL you made the system think that you use FSCM Credit Management.
According to the documentation of your implementation ZUKM_CREDENTIALS
from your credentials project you would like send some credit vector
information.
I do not exactly know why this implementation has been made but as a
side effect it deactivates some credit management functionalities.
So one option would be to deactivate the BADI. For the case you need
this implementation there would be a possibility to modify our function
module checking for any active implementation. But I cannot predict all
side effects of using this implementation in parallel with classic
credit management functionality.
In function module UKM_IS_ACTIVE you will find a call to form routine
CHECK_ACTIVE_BADI. This check comes back with an active flag.
In the form routine you will see why. The main check is made against
BADI UKM_R3_ACTIVATE. But for compatibility reasons we do a check for
UKM_FILL as well. Unfortunately I cannot change this coding in standard
for you for the case that any customer who makes an update from a lower
release where this BADI has been used to activate FSCM functionality.
But this would be the point to manipulate the check to get classic
credit management functionality back.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.