Copying general task list onto the service order by selecting service product

[Former Member]

Hello fellow PLMers,

I have a question that I could not quite resolve with my colleagues so here I am hoping that the SAP PLM community can help me out:

When raising a service order through IW31, the user would like to have a general task list determined and copied into the order when they select a given "service product" material. The service product material is usually selected by picking the relevant service contract item that the material is sitting on. Of course, the mapping between the service product material and the desired general task list is maintained through table entries in OISD.

It works perfectly fine but only in full work order view. As soon as I try to do this in "basic order" view, I get an error which says:

IWO_BAPI134: General maintenance task list for service product xxx cannot be integrated.

I read up on it and it seems that anytime a service order is created programmatically through the BAPI_ALM_ORDER_MAINTAIN this error will happen. So, I suppose it means that whenever service orders are created through "basic order" view, the BAPI will be utilised - hence the issue.

I looked on SAP OSS for any OSS notes regarding this. I could find one:

OSS note # 967472 BAPI: Maintenance task lists are not included

But I'm not 100% sure if that's the note is relevant to my issue.

Any help or guidance will be greatly appreciated.

Thanks in advance,

Roman.

[Former Member]

Dear Roman Feigin,

I am facing the same issue in SAP CS. Have you already found a solution ? Or do you have any advice ?

Thanks in advance.

br/ole

[Former Member]

Hello Ole,

This is going back a while ago! Two large SAP implementations ago, to be precise .

To answer your question - we ended up going with "standard work order view" instead of the "basic view" and to simplify the service order header screen we added config to hide a whole lot of fields (see transaction OIAY and OIAN)

I never really followed up with SAP to see if there's been a solution to this issue.

The only other option I can think of is to develop "task list copy" logic in ABAP and include it into the "Save work order" user exit...  In our case, the project was already running over budget and we had to switch to "standard work order view" and hide the irrelevant service order header fields instead.

Hope this helps.

Regards,

Roman.