Service Definition, Product Service Definition and Benefit Priorities

Just as benefit specifications are based on a combination of a service definition and a product service definition, benefit priorities can also be based on the combination of a service definition priority and a product service definition priority. But this is not mandatory, benefit priorities can also be based on solely a service definition priority or a product service definition priority.

So dependent on the configured priorities three flavors are automatically created:

• Benefit Priorities based on a service definition and a product service definition priority

• Benefit Priorities based on a service definition priority (and no product service definition priority)

• Benefit Priorities based on a product service definition priority (and no service definition priority)

To clarify this and the (im)possibilities, some examples are given in this document.

Using only Product Service Definition Priorities

Consider the following example containing two product service definition priorities.

Product Service Definition Priorities

Code	Short Code	Display Name	Priority
REGULAR	REGL	Regular Service	3
FEDERAL MANDATE	FMAN	Federal Mandate	2

This results in the generation of two benefit priorities.

Benefit Priorities

Code	Display Name	Priority
FEDERAL MANDATE	Federal Mandate	2999
REGULAR	Regular Service	3999

The value of the benefit priority is calculated as follows:

Product Service Definition Priority * 1000 + Service Definition Priority AND if either priority is missing, use value "999" for that priority

This is why the value of the resulting benefit priority is "2999" and not "2".

Combined Priorities

Using both service definition and product service definition priorities to generate benefit priorities allows for the most fine grained list of benefit priorities, as each possible combination of two priorities results in a benefit priority. Consider the following example containing two product service definition priorities.

Product Service Definition Priorities

Code	Short Code	Display Name	Priority
REGULAR	REGL	Regular Service	3
FEDERAL MANDATE	FMAN	Federal Mandate	2

And two service definition priorities.

Service Definition Priorities

Code	Short Code	Display Name	Priority
DEFAULT	DFLT	Default	5
EXCEPTION	EXCP	Exception	3

These configured (product) service definition priorities result in the generation of the following benefit priorities (ordered from high to low priority).

Benefit Priorities

Code	Display Name	Priority
FMANEXCP	Federal Mandate Exception	2003
FMANDFLT	Federal Mandate Default	2005
FEDERAL MANDATE	Federal Mandate	2999
REGLEXCP	Regular Service Exception	3003
REGLDFLT	Regular Service Default	3005
REGULAR	Regular Service	3999
EXCEPTION	Exception	999003
DEFAULT	Default	999005

For each benefit priority that is based on two priorities the two short codes are used to create the code for the benefit priority. If the benefit priority is only based on a single priority, the code of that priority is used to create the code of the benefit priority.

Incorrect Setup

It is not possible to create a service definition and a product service definition priority with the same code. This will encounter an error when benefit priorities are generated. So the following example must be avoided.

Product Service Definition Priorities

Code	Short Code	Display Name	Priority
REGULAR	REGL	Regular Service	3

And two service definition priorities.

Service Definition Priorities

Code	Short Code	Display Name	Priority
REGULAR	REGL	Regular Service Definition	5

In this situation the system tries to create two benefit priorities with the same code which results in a unique key violation.