method not defined for object

[Former Member]

Hello,

When I look into one of the standard tasks in my wf, this message appears:

"Method 'POPUPCONTABLE' is not defined for object type 'ZBUS2081'"

This problem happens in Test (Quality - QAS) environment, but not in Development (DEV). So I have activated and generated the object type in DEV and then generated again the whole wf, and included it all into a transport request.

After the requests were released and imported in QAS these modifications apparently did not take place, and the method is still unrecognized for that object.

How could I make sure that this change will be included in the requests? And, is this approach right (activating the object type)?

Appreciate your suggestions,

Best regards,

Ivson

Note: There are other/similar methods in that object type, in the same wf, that work ok.

[pokrakam · Accepted solution]

Hi Ivson,

Two ideas:

- Check that the status of your method is either 'Implemented' or 'Released'.

- Can you see the method if you look at the object in SWO1 in QA? Also, sometimes it helps to manually activate it in QA (won't work from the front screen of SWO1, go into the object display itself then hit generate).

Oh, and come out of any transactions before trying anything after any transports/changes.

Cheers,

Mike

[Former Member · Accepted solution]

Thanks,

I've activated the object directly in Test and it has worked (although we have no authorization to modify in Test, it has accepted that modification in particular).

Anyway, I still wonder why things didn't change the first time. Maybe I am not including changes correctly in the requests.

Best regards,

Ivson

[morten_nielsen]

Hi

To me it sounds like you haven't got the delegation from ZBUS2081 to BUS2081 transported. Have you checked this on test (In SWO1 under Settings delegation).

I'm without SAP Access, so I'm not sure, but if I remember this correctly this is placed in a customizing, and not in a development request.

Regards

Morten Nielsen

[Former Member]

Hi,

I've checked both in Test and Development where you said (swo1, Settings, Delegation) and there are no elements at all. Does this really mean that the delegation of the object we use (zbus2081) has not been transported? is it necessary to include it?

Thanks

[pokrakam]

Hi Ivson,

The transport system can be a bit flaky, though to be fair it can get quite complex. What it tries to do in the case of interdependent objects is to attempt activation of one thing, then reactivate the other and go back and reactivate any failed ones.

There are a few notes on OSS regarding transports and you'll see a few recommendations to simply retransport things if they failed. One way to minimize problems is to transport objects and code first, then workflows, then customizing.

As to delegation, you said 'other attributes work' so I assumed you'd delegated. What you should be doing is creating a delegation from BUS2081 to ZBUS2081. This is effectively the reverse of inheritance and makes all your additional components in the Z-object available as part of the BUS...-obj. In your workflows you should then ONLY work with BUS2081.

Cheers,

Mike

[Former Member]

Thank you,

I suppose the object type zbus2081 was inherited from bus2081 (i didn't create it). How can I find out?

And in case I want to delegate zbus2081 to bus2081, what steps should I follow? So far, besides the transport problems, it is working fine with zbus2081.

Kind regards

Ivson

[pokrakam]

ZBUS2081 -> header data -> Supertype will show where it's inherited from.

The problem with using ZBUS... is that a lot of standard stuff uses BUS... BOR is not polymorphic, so you cannot bind one object type to another. In other words if your element is ZBUS you cannot use a task based on BUS - you need to create your own.

Delegation is done from the front screen of SWO1 - Settings->Delegate.

Cheers,

Mike

[Former Member]

Hi Ivson,

Instead of current existing method, try creating another method e.g. POPUPCONTABLENEW and then check if it works.

Regds,

Akshay Bhagwat