Hi Mark,

Unfortunately, I don’t believe it’s possible in our current system design.  The SLA is purely taken from the contract.  It can be set up for a different order type.

Or it can be set up for the Contract Obj. Of Services.

Just FYI, it can be set up based on priority in our newer version (V15).

To load a different SLA depending on the problem code will require customization by IFS. 

Regards,

Susie

Thanks Susie. I suspected that might be the case.

cheers

mark.

Is this UM orders only? IOn PM orders you can have different SLAs based on Request Types - see Customer Contracts - Advanced - Exceptions

Hi Bjørn,

You are correct that you can use Exceptions to manage the SLA based on Request Types but the question was about Problem Codes which does not have functionality to adjust the SLA based on just the problem code.

What the user could consider doing is develop a Process Flow (v15) to find 'mis-matched’ SLA's per what they expect for their problem codes and have that update the customer support or service order priority.  Or if it is event drive (document creation), set the priority just after the document is created.

Otherwise, an escalation rule for v14 probably could also be developed.

As Susie indicated, it would be an RFE to change this in standard or more likely can only be done as a customization.

Actually guys, I think using Request Types will work.
I can create some request types that have the same name as the problem codes i want them associated with, and then, apply those in the Customer Contracts → Exceptions with the appropriate SLA assigned.

The only thing, is it means the user would need to select a Problem Code and a Request type that are the same. But that should be do-able.

Thanks for your suggestions guys.

cheers
Mark.