Activation Error

[former_member355261]

Hello,

I copied some transport resuests from one SAP system to another, but when trying to activate some of the objects I get the following error message:

I guess the problem is in the BADI implementation OT_DESC_CHECK_MOA.

But now, whatever I want to do I always have this error message appearing (when trying to delete the BADI Implementation or to create a transport request or activating an object or anything).

I always get this error message.

Please help me solve this problem.

Thanks in advance.

[Former Member]

Hi,

First create the TYPE "ZYBCTR_RELEASE"  as the dump says.

Not sure it is a structure/Table Type/Data element. You can check that by going to SE38 and paste the program name "ZCL_IM...======CP" ( As shown in Short text in the dump ) and then do a syntax check via CTRL + F2.

In the error double click and it should take you to the line where the issue is.

Then you should be able to delete/re-transport/use assuming you don't have further syntax issues.

R

[former_member355261]

Hi,

After doing the syntax check, I got the same error message : Type "ZYBCTR_RELEASE" is unknown.

And when trying to activate the object ZYBCTR_RELEASE, I'm prompted for a transport request and when trying to create one I get the error message again.

Please tell me what to do in order to fix this issue.

[Former Member]

In which system you are trying to Activate the Z object? Is it Dev/Sandbox/ QA / Production?

And what message you are getting when you try to create the transport?

[former_member355261]

In the DEV system.

I get the same error message when I try to create the request.

[Former Member]

I am sorry but it is not possible to get the same error while trying to activate/Create ZYBCTR_RELEASE type. How you are activating it? SE11?

Incase it ask for a transport request, you have to create a new transport request and use it. I would not suggest using Local Object as it would then be non transportable.

[former_member355261]

I'm activating it through SE11 normally using th activation button or by pressing Ctrl+F3, and I get then the short dump.

When it asks for a transport request I create a new one but when I validate the creation I get the same short dump again.

[Former Member]

Based on the info on the dump, the type ZYBCTR_RELEASE is missing in the system. It could have probably been in a different transport. Try creating the type in the system where you are copying the transport and assign it to the same TR (if possible) and then try activating the object again.

V.

[former_member355261]

The object "ZYBCTR_RELEASE" exists in the system but is inactive, and when trying to activate it, I'm prompted for a transport request and when trying to create one I get the error message again.

[ThangaPrakash]

Hello Occoro,

You are using which Component version of SAP? I couldn't find the badi which you mentioned in my system.

Regards,

TP

[former_member355261]

Hello,

It's the BADI CTS_REQUEST_CHECK.

[Former Member]

Occoro,

I am guessing there is some sought of dependency. Did you try activating all the objects concerned in one go. If there are dependencies activating all the objects together should work.

V.

[former_member355261]

I tried to activate all the objects in my worklist in one go, but I'm still getting the same short dump

[ThangaPrakash]

Hello Occoro,

Try deactivating the BADI implementation and then delete it from the system.

Regards,

TP

[former_member355261]

Hi,

I can't deactivate the BADI implementation because I get the same error message again.

[Former Member]

Hi Occoro,

First Comment the code of your BADI Implementation. Then activate the BADI Implementation.

Also just do a where used list to find the places where the table is used.

After commenting the places of usage, now activate the table in SE11.

If you are facing the issue in activating try to activate through SE14.

Once the table is in active state, then uncomment the code of the BADI and activate the same.

Hope it might resolve your issues.

Regards,

Vinay Mutt

[former_member355261]

I found the solution for my problem.

I used SAPLINK to re-import the object in the target system, but I made it local so I could activate it and solve the problem.