Reactivaton of user exits

43 Views

We have an instance when enhancement COOPA_01 was inactive in both our

Test box (SI4) and Production box (SP1) while it's activated in the

Development box (SD2). In the past, this enhancement was activated when

user exit

EXIT_SAPLRKIO_001 (Include ZXAUFU01) was developed, activated and sent

from SD2 to SI4 (then to SP1).

Recently, we got an issue when an IO logic encoded in the said include

was not being read upon (in SI4 and SP1). After debugging, it was found

out that the reason why the processing isn't passing through the

intended IO logic is because it was inactive in the SI4 and SP1 boxes.

Here are my questions:

1. Do we have any ways on how we could track the deactivation and/or

reactivation activities of user exits/enhancements?

2. What are the possible reasons why a user exit is getting deactivated

in certain boxes/clients (For ex. in SI4 and SP1. Why in SD2, it's

activated?)

3. Does"Reactivating User exit" a transportable activity or it's client

specific one?

4. Are there any ways on how to prevent the deactivation of enhancement

COOPA_01 in all clients?

The information that will be provided, will be used, to prevent issues

caused by enhancements getting deactivated, in the future.

Thank you very much for your help!

Best Regards,

JP