It is possible to predetermine the points debt rules as a means of automating the debit of points. These debit rules concern the contracts with points.

Two main rules exist for points debits :

  • The contractual debt of points :This rule is used to debit a fixed number of points, whatever the service carried out and the time passed on the customer account.
  • Complementary debit of points :This rule is used to debit points as a function of the nature of the services carried out on the customer account.

It is possible to combine a contractual rule with a complementary rule.

The points debit rules can be viewed from the following objects :

  • Customers
  • Skills
  • Products

The non cross referenced rules can be saved directly in each of these three objects via the Functions menu.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

 

Header

The points debit rules can be defined at several possible levels :

  • General level :If none of the fields is entered.
  • Customer level :The debit rule is applied for the single customer entered.
  • Installed base level:The debit rule is applied for the single installed base entered.
  •  Skills group level : The debit rule is applied for the single skills group entered.
  •  For combinations of these different elements. For example it is possible to imagine a debit rule foe a single skills group for a specified customer.

Zero value taken into account

This field is used to neutralize the return up a rules structure by imposing the taking into account of a zero value at an upper level. This possibility is applied to both contractual debits and complementary.

Customer (field BPR)

This field is used to define a Customer component for a points debit rule.

The fixed debit associated with a rule where only the customer code is entered will also be visible

in the selected customer rule.
Base concerned (field ITMREF)

This field is used to define a Customer base component for a points debit rule.

The fixed debit associated with a rule where only the product code is entered will also be visible

on the selected product record.
Skill group (field PBL)

This field is used to define a Skill component for a points debit rule.

The fixed debit associated with a rule where only the skill code is entered will also be visible

in the selected skill record.
field PBLCLA
Standard debit (field SGLNBRPIT)

The fixed debit is applied when a service request is entered for a customer having a

contract with points.

This debit is applied independently of the time and resources devoted to the processing of the request.
Taking into account null value (field NULPIO)

This option is used to block moving back up the structure for the debit of points rule during the analysis of the

coverage of a service request.

In other words, it is used to constrain the system to adopting a null debit if

a rule having this option is encountered.

Tab Debits

The complementary rule are determined in the Debits tab.

The consumed products are entered defining the complementary points debit rule. A points debit rule is used to fix the number of points debited by the consumption of a product as a function of a unit of measure. It is necessary to enter the Debited points, All the and Units fields.

The Zero value taken into account field is also taken into account in the points debit rule line.

Grid Supplementary debits

Product consumed (field ITM)

The additional debits that are used to adjust the points debits conforming to the time and resources

devoted to the resolution of a service request.

These particular rules can be distinguished for each type of consumption thanks to their activity code.
Points debited (field NBRPIT)

This field is used to indicate the number of points debited by this additional rule.
all the (field DEBFRY)

This field is used to indicate the coefficient applied between the evaluation unit for the consumption and the

selected point debit.
Unit (field DEBFRYBAS)

This field is used to indicate the unit that is used to value the additional debit rule in face of the

different consumptions recorded.
Taking into account null value (field NULPIOVAL)

This option is used to block moving back up the structure for the debit of points rule during the analysis of the

coverage of a service request.

In other words, it is used to constrain the system to adopting a null debit if

a rule having this option is encountered.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation