Settlement Calendar

Use

The settlement calendar enables you to enter and store important settlement data for equipment on different levels per day or period of time. It consists of the following functions:

Integration

You have to release all the entries in the settlement calendar after you have entered them. Entries in the settlement calendar will not be taken into account in the Generation of SD Orders until they have been released.

Prerequisites

You can make settings in Customizing to control the following:

  • which settlement and activity type is taken into account in the settlement calendar

  • whether the settlement calendar or the document activity and settlement type is dominant (Customizing for Start of the navigation path Equipment and Tools Management (ETM) Next navigation step Operations and Functions Next navigation step Settlement Next navigation step Settlement Calendar End of the navigation path )

  • which access sequences the system uses (Customizing for Start of the navigation path Equipment and Tools Management (ETM) Next navigation step Operations and Functions Next navigation step Settlement Next navigation step Pricing End of the navigation path ).

Features

Users should make entries in the settlement calendar. Releasing entries has a major impact on the generation of SD orders. The release acts as a type of control mechanism and should be carried out by an authorized person.

The settlement calendar is only of relevance for shipping documents and not for PBE documents.

Example 1

Equipment is in operation on usage site A from 12.01. – 12.30. No work is done on usage site A on 12.12. due to severe weather conditions. So that this can be taken into account in settlement, the appropriate activity type for bad weather is set on usage site level for this site and on this date.

Result in settlement: the activity type for bad weather is used in settlement for all equipment on this usage site and on this date Equipment is split into several SD items in ETM Settlement . Different settlement condition records can be used depending on the activity and settlement type. You can define these using condition techniques in the SD module.

Example 2

The whole company is shut down from December 24 th until January 3 rd . If you want this to be taken into account in settlement, you must make appropriate settings on the highest access level (company code).

Result in settlement: all equipment on all usage sites in this company code is settled with activity and settlement type “shutdown” from 12.24. – 01.03.

Example Example

The following hierarchical levels have been defined:

End of the example.

  • Debited company code – debited business area – recipient – equipment (most exact setting)

  • Debited company code – debited business area – recipient – equipment type

  • Debited company code – debited business area – recipient

  • Debited company code – debited business area

  • Debited company code (least exact setting)