How to ignore reference internal order from service contract in service order?

[tprekel]

Hello everyone,

we are using Service Contracts and Service Orders in S/4HANA Service OP.

When we create a Service Order in reference to a Service Contract the internal order of Service Contract is also used for our Service Order. We would like to have the scenario that a new internal order is created for each Service Order. So I'd assume we just have to do some configuration here:

Setting "Reference Usage" to "Ignore" for CRM Transaction SRVO should do the job but it's still copying the internal order of the leading Service Contract.

Do you have any ideas where we made a missconfiguration? Or is it simply not possible to create new internal orders for Service Orders if they are referencing a Service Contract?

Thanks in advance for your assistance. Maybe silvia.ventura is able to help?

Best regards

Thomas

[Silvia_Ventura · Accepted solution]

Hello Thomas,

I was checking internally your requirement in my S/4HANA system. It didn't work either...I mean, I had the same idea than you : field REFERENCE should be used for getting different internal orders from source (e.g. srv.contrract) and target (e.g. srv.order).

So I contacted with my colleague in development support and he explained that you and me are right BUT the feature wasn't developed in the old CRM and you have to apply note 3213190 in S/4HANA.

Please apply this note and let us know the result.

Best regards

[tprekel · Accepted solution]

Hello Silvia,

thanks a lot! I will try to implement your recommended solution and let you know if it worked.

Best regards

[Silvia_Ventura]

Hello Thomas

really I didn't check it. My internal test systems are very restrictive with the application of notes. I don't know what to say,..create a ticket and I'll try to check it.

Best regards

Silvia

[tprekel]

Hello Silvia,

I understand. Thanks a lot! I will analyse some more and then eventually create a Ticket.

Best regards and have a nice weekend!

Thomas

[tprekel]

Hello silvia.ventura,

we implemented the recommended note but unfortunately it doesn't quite work for us. It seems like the CO scenario determination is not happening due to missing "created_at" date in "ls_orderadm_h" structure:

"ls_servicechar-handing_over_date" based on "created_at" date is used later on as variable to check for validity in CO scenarios:

Now due to the dates being zero, none of the customized CO scenarios - which would lead to "ignore" referenced CRM transaction - is being used. Does the note work in your system?

Again thank you a lot and best regards!

Thomas