Service Contracts

• Company (field CPY)

This field contains the company code that manages the contract.

• Site (field SALFCY)

This field contains the site code which carries out the contract management.

• Reference (field CONNUM)

This field is by default associated with an automatically functioning sequence number counter. Consequently, the user should not normally concern him/herself with its contents.

By default, the service contract code will be composed of a sequence number of 15 characters generated in an automatic fashion.

• Customer (field CONBPC)

This field contains the customer code who is in receipt of the contract.

• Currency (field CUR)

This field is used to define the currency to be applied to all the financial fields in a service contract.

This same currency is also used to value the minimum and maximum threshold for the

financial coverages.

• Contact (relationship) (field CONCCN)

This field contains the name of the contact with whom the different contract negotiations are carried out.

• field CONCCNCLA

• Description (field CONNAM)

This field is used to enter a text to help identify and understand the principal characteristics of the contract.

• field CONTYP

The statistics groups are used in the statistical processings as well as selection criteria in many programs.
There is a maximum of five statistical groups, and their number as well as their title can be set up when installing the software.

• Category (field CONCAT)

This essential field is used to determine the functional category for the service contract.

This field is the support for the activation of certain functionalities such as the management of points,

the re-evaluation of contracts, invoicing....

• All skills (field EVRPBL)

This field is used to determine the access to the descriptive grid of skill coverage.

If this field is ticked, the grid cannot be accessed because all the skills described in the application are taken into account in accordance with the contract. It is therefore of no use to enter them one by one.

If this field is not ticked, only the skills entered in the Skills covered grid are taken into account.

Warning: In this function, the level of the skills group covered is entered. This signifies that when a skills group is entered, all the sister groups are taken into account by the contract.

If this field is not ticked and no skills group is entered, the contract will be almost unusable. No customer problem will be able to be taken into account by this contract.

• All installed base products (field EVRMAC)

This field determines the access to the customer base coverages definition.

It is not applied to contracts with points.

If this field is ticked, the customer base management function is inaccessible.

It signifies that the contract applies to all the products ordered by the customer.

In this way a sort of super contract is obtained.

If this field is not ticked, the contract can then contain coverage rules based on :

1/ The particular customer base records.

2/ A group of customer base records defined for a reference product.

3/ A group of customer base records defined for a commercial group.

These coverages can be sorted by restrictions in terms of components, consumed items,

labor and trip expenses.

• Priority to installed base (field CRSCOVSAM)

This option is of use only in warranty and maintenance contracts for which a coverage type Customer base

(and not the type All the base) has been defined.

It is used to totally automate the definition of the cross referenced coverages (Base + Skill) on the basis of all

the coverages of the type Customer Base.

If this option is active, any creation, modification or deletion of a Customer base coverage is immediately

copied to all the different corresponding cross-referenced coverages.

• Signed by (field SALREP)

This field contains the code for the sales representative that has negotiated either the service contact subscription or

the order for a product covered by the service contract.

• Source (field CONORI)

• Document no. (field CONORIVCR)

When the number of the document is indicated (other than that of the contract), a contextual menu "Document detail" is used to view the

characteristics of the document in question.

• Line (field CONORIVCRL)

• field RSITXT

• Contract template (field CONCOT)

This field is used to facilitate the manual creation of a contract by the use of a template designed to qualify the

principal information that makes up the contract.

The selected template MUST conform with the service contract category currently being created.

In addition, the available contract template selection window only displays the templates

corresponding to the category entered in the contract.

• field CONCOTNAM

• Subscription date (field SIUDAT)

This field contains the subscription date of the contract. It is entered once and for all.

• Renewal frequency (field REWFRY)

This field represents the contract duration.

For the contracts with tacit renewal, this is the frequency on which the contract will be automatically renewed.

For the contracts that have no tacit renewal agreement, it is the frequency on which the contract should be renegotiated by the two parties.

• Unit (field REWFRYBAS)

• Start date (field CONSTRDAT)

This field contains either a date that is identical to the subscription date (throughout the first period) or the date of the last renewal.

• End date (field CONENDDAT)

This date indicates either the date on which the contract will automatically be renewed where there is tacit renewal agreement or the date from which the contract will no longer be valid.

• Automatic renewal (field CONREW)

This field only concerns contract with points.

This field specifics whether the contract will be subject to an automatic renewal at the end of its term.

This essentially signifies that will in this case be no break in the invoicing chain

that will continue to be executed at the desired frequency.

When this is not the case will be the object of a re-negotiation in order to allow the continuation of its

invoicing cycle.

• Annual royalty base (field CONAMT)

This field does not concern the warranty contracts.

This field contains the price for a contract with points. In fact, the contract with points is the object of a single and total

invoicing.

This field contains the calculation basis for the invoiceable open items in the maintenance contracts.

• field CONCUR3

• field REWWRN

• Points credit (field PITCDT)

This field concerns only contracts with points.

It is used to define the total number of points given to the customer for the contract.

• Revaluation frequency (field RVAFRY)

This field is used to enter the frequency on which the annual fee basis for the maintenance contract

must be re-evaluated.

• Unit (field RVAFRYBAS)

• Revaluation method (field RVAMET)

The maintenance contracts can be re-evaluated in two different fashions.

1 - The Post-re-evaluation presents the advantage of always calculating the amount of the next open item in a contract.

However, the basis of the annual fee basis is always moved by a period with respect to the actual value

of the support index for this re-evaluation.

2 - The Pre-re-evaluation offers the advantage of calculating the annual fee that is the exact reflection of the development

of the index used. However, apart from the first open item in the contract, this method does not make it

possible to know the amount of the open items in advance.

• Help for revaluation (field RVASSP)

The re-evaluations can be calculated by using one of the two supports :

1 - It is possible to choose an index that will serve as a basis of the periodic fluctuations to be applied to the

annual fee basis for a contract.

2 - The use of a Mathematic formula option is used to manage all the other re-evaluation methods.

In fact, each formula provides an entry point where the application field is potentially unlimited.

• Index (field CONBASIDX)

This field is used to enter the index that should be used at each re-evaluation of the contract. A re-evaluation is realized by comparing the index value used during the last re-evaluation and the last value saved in the system for this index.

• Last value used (field LASVALIDX)

This field indicates what is the index value used at the time of the last contract re-evaluation. The Date field indicates the date for the index value.

• Date (field LASIDXDAT)

• Formula (field CONBASFOR)

This field is used to select the entry point that will be used for the contract re-evaluation calculation.

If the selected formula contains the code A1, the entry point will be : RVACON_A1.

This entry point is called from the TRTCRMPE process.

• Date of last revaluation (field RVADAT)

This field contains the date on which the contract has been re-evaluated for the last time.

• Advance notice of cancellation (field RSILTI)

As a function of the activity sectors, this field can have the following meanings :

1/ The number of days preceding the end of the contract before which a customer termination request can be accepted.

2/ The number of days during which the contract continues to be applied after receipt of a customer termination.

In all cases, the termination is a manual operation that must be carried out directly in a contract record.

• Unit (field RSILTIBAS)

• Points tolerance (%) (field PITTOL)

This information involves only contracts with points.

It offers a mechanism that is used to consume the contracts with points

In fact, with regard to the potential complexity of the rules for the debiting of points, the probability of consuming

exactly the number of points allowed in the contract is very low.

Taking as an example benefiting from a contract of 100 points with a debit rule of 30 points

by service request.

The fourth call by this customer will close by issuing a quote related to the subscription to a new contract when

at the same time the customer still benefits from a contract of 10 points.

If this same contract benefits from a points tolerance of 20%, the fourth call will normally be honored and the

contract will automatically be closed at the end of the service request process.

• Frequency (field INVFRY)

This field indicates the frequency on which the customer will receive the invoices related to the receipt of services covered by their contract. This field is also used to determine what part of the annual charge is to be posted to the invoice.

• Unit (field INVFRYBAS)

• Method (field INVMET)

The management of the service contracts allows two different invoicing methods.

1 - Pre-invoicing makes it possible to invoice the contracts before the customer has had any benefit.

2 - Post-invoicing is used to invoice the contracts after the customer has benefited from it.

• Increase/Decrease coefficient (field INVFRYCOE)

Certain operations increase the open item amount when they are applied over the long term. The coefficient field is used to define the size of this increase or decrease should it be required.

• Advance notice (field INVLTI)

This field is used to define the notice from which a contract open item to be invoice will appear in the invoicing tools. From this moment, the invoice will be generated and sent to the customer.

The notice represents the number of days that precede the term for an invoicing open item.

• Unit (field INVLTIBAS)

• Payment term (field PTE)

This field is used to enter the assigned payment conditions for the payment of the contract open items.
Only a discount code consistent with the legislation and company group of the document site can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Litigation code (field ACPDPTCOD)

This field is used to enter the dispute codes that trigger the management of a customer problem if the payment has not been done on time in respect to the contract due dates.

For instance, a customer's payment is two month late in respect to the contract due date. Moreover, this customer has declare a dispute with their supplier. When the customer call the customer support in order to solve a problem on one of the materials, the customer will benefit from the service if the dispute code of the due date corresponds to one of the codes mentioned on the maintenance contract.

• Dimension type (field DIE)

• Description (field NAMDIE)

• Dimension (field CCE)

• Bill-to customer (field CONBPCINV)

The bill-to customer code initialized by default with the bill-to customer code associated with the customer indicated in the

subscription.

• Pay-by (field CONBPCPYR)

Paying customer code.

It is initialized by default with the paying customer code associated with the customer indicated in the

subscription.

• Group customer (field CONBPCGRU)

Group customer code

It is initialized by default with the group customer code associated with the customer indicated in the service contract

subscription.

• Project (field CONPJT)

This field is used to indicate any project at the origin of the service contract

subscription.

• Rate type (field CONCHGTYP)

• Invoicing product (field ITMREF)

This field is indispensable once the service contract must be the object of invoicing.

It contains the product code that will be transferred to the invoice line corresponding to the service contract open

.

This field is initialized by default with the value in the service contract template used

or else with the contents of the DEFCONITM setup.

• Price type (field CONPRITYP)

• Sales unit (field SAU)

• Tax rule (field CONVACBPR)

This information is used to indicate the tax rule for the document. This code is controlled in the tax rule table and is initialized by the corresponding code in the BP record. It can be modified.
This information is mandatory and remains accessible provided the delivery has not been confirmed.
Only a tax rule with a legislation and group that are consistent with those of the document can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Entity/Use (field SSTENTCOD)

• No. (field NOLIG)

• Description (field SHO)

• % or amount (field INVDTAAMT)

The values relate to the invoicing footer. This information can come directly from the parameters of the elements of the invoice footer or from the record of the customer involved.
 Please refer to the documentation on the invoicing elements for further details.
The values of the footer elements can be modified. The Tax excl. and Tax incl. amounts are directly impacted by these values.
Specificities linked to the inter-company functionality
If the order has been generated from an inter-company or inter-site purchase order, and the inter-company parameters specify that the invoicing elements come from the Purchasing module, the latter will be initialized with the values entered on the purchase order of origin.

• field INVDTATYP

• Curr. (field WWCUR)

• SST tax code (field SFISSTCOD)

Enter the code to use in order to override the default SST tax code from the product or invoice element. This tax code is recognized by Sage Sales Tax and is used to identify line types for tax purposes. This field is available only if the LTA - Local taxing activity code is activated, and the USATAX - Tax system use parameter is set to Yes.

For invoicing elements designated as the SST document discount for a company, you cannot remove the SST tax code value on the document.

• Points available (field PITRER)

The points used correspond to the points assigned to a non resolved service request.

If the service request is deleted, the points used are then returned to circulation.

The points consumed corresponding to the points assigned to a closed service request.

The remaining points field calculates the balance of point that are neither in use nor consumed.

• Points consumed (field PITCSM)

• Remaining points (field PITBLC)

• Next invoice issue date (field NEXSHIINV)

This field displays the date from which the invoice corresponding to the next open item

in the service contract can be generated.

• Next invoice date (field NEXINVDAT)

This field displays the invoice date for the next open item in the service contract.

• Next inv. amount excluding tax (field NEXINVAMT)

This field displays the ex-tax amount for the next invoice only if the contract has not been subject to a revaluation

or else it is re-evaluated according to the post reevaluation method.

In the case of contracts with pre-re-evaluation, only the amount of the first open item can be viewed in

this field. The amount for all the other later open items is never displayed because it is unknown.

• field CONCUR4

• field NEXAMTCMT

• Date (field INVDAT)

• Amount - tax (field INVAMT)

• Document no. (field INVVCR)

• Date (field DUDDAT)

• Amount + tax (field DUDAMT)

• Dispute (field DUDDPTCOD)

• Open item no. (field DUDNUM)

• Date (field PAYDAT)

• Amount + tax (field PAYAMT)

• Payment no. (field PAYNUM)

• Open item no. (field PAYDUDLIG)

• Start (field AMTSTR)

• End (field AMTEND)

• Amount (field AMT)

• Start (field REWSTR)

• End (field REWEND)

• Cancelled contract (field RSIFLG)

This tick box is used to terminate a contract.

The termination of a contract leads to its disappearance from the invoicing cycle

and all the renewal tools.

The contract disappears from the left list of active contracts and becomes available only

from the terminated or closed contracts left list.

• Termination reason (field RSIREN)

This field is used to indicate any reason invoked by the customer to demand the termination of their contract.

• Closed contract (field FDDFLG)

This option leads to the same consequences as a termination with respect to the mechanisms for the invoicing

and renewal.

Nevertheless, the closure in general results from an action internal to the organization rather than a

customer request.

• Closed by (field FDDUSR)

This field is used to indicate the employee that has instigated the closure of the service contract.

• field FDDUSRCLA

• Date of the event (field RSIDAT)

This field is loaded with the current date when the field "Contract terminated" or "Contract closed" is ticked.

The user is free to enter the actual date of the termination on the part of the customer or else the closure date by the employee.