Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PY-XX (Application Component) Payroll: General Parts⤷
PCAL (Package) SAP HR Payroll Application Development
Basic Data
| Data Element | AVER_UNIT |
| Short Description | Time unit for average periods |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AVER_UNIT | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 9 | Time unit |
| Medium | 11 | Time unit |
| Long | 20 | Time unit for period |
| Heading | 0 |
Documentation
Definition
Use
You can choose one of the following time units for the average periods in your system:
- Calendar month
You can perform average calculation on the basis of calendar months even if you use payroll periods in your system that do not correspond to calendar months (for example, weekly periods or monthly periods that do not start on the first day in a month). With this, the system always goes off the last day in the calendar month. The settings in customizing determine which calendar month is relevant (see Dependencies):
- If you want to take the current payroll period into consideration, the system goes off the last day in the current period. It adds on a day and then searches for the last day in the calendar month that comes before this day. If, for example, the current payroll period ends on June 15th, the system goes to June 16 and from there goes back to May 31. If the current payroll period ends on June 30th, the system goes to July 1st and then back to June 30th.
- If you do not want to take the current payroll period into consideration, the system goes off the first day in the current payroll period. It then searches for the last day of the calendar month that comes before this day.
The system uses the last day calculated in this way to continue to go back in intervals of calendar months.
- Calendar Weeks According to Feature LDAYW
In feature LDAYW (Determine Last Day of Week), you set the day on which a calendar week ends in your system. In the standard system, this feature is set so that a calendar week in the USA ends on a Saturday, and on a Sunday in all other countries.
Depending on your customizing settings, (see Dependencies) the system either uses the last working day before the current payroll period, or the last working day in the current payroll period. The system searches for the USA, for example.
- if you want to take the current payroll period into account, which is a Saturday that falls in the current payroll period
- if you do not want to take the current payroll period into account, which is a Saturday that falls before the current payroll period
The system uses the last day of the calendar week to work backwards in weekly intervals.
- Floating Months
If you want to use payroll periods that do not correspond to calendar months, you can use so-called floating months for the average calculation. In this case, the system works as follows:
- It uses the last day of either the current or previous payroll period, depending on your customizing settings (see Dependencies).
- The system goes back to the month in which the current (or previous) payroll period falls. It uses the date of the last day of the current (or previous) payroll period, and adds 1. For example, if the system starts on April 7, it will work backwards to March 8.
- From this point, the system continues to work backwards in monthly. intervals. For example, starting on March 7, it will continue to work backwards to February 8, and from February 7 to January 8, and so on.
If the last day of the current (or previous) payroll period is the 28th of the month or later, the system does not work backwards to the previous month, but to the beginning of the same month (in other words, the first of this month). Otherwise, the different lengths of calendar months would present problems for the system.
Dependencies
The time unit for average periods cannot be identical to the time unit used for payroll periods in your system.
In customizing for averages, under Create Calculation Rules for Averages, the Also take current period into account field specifies whether or not the current period is included in the average calculation.
Example
You use weekly payroll periods in your system. The current payroll period is from Tuesday June 21 to Monday June 27. You want to perform average calculation over three average periods. The current period should not be taken into account in the average calculation. Depending on the time unit that you enter in this field, the system uses different periods for the average calculation:
Calendar month: March, April and May
Calendar Weeks According to Feature LDAYW:
- USA: Sunday, May 29, to Saturday, June 18
- Other countries: Monday, May 30 to Sunday, June 19
Floating months: March 21 to June 20
If you specify that the current payroll period is to be taken into account in the average calculation, the period for the average calculation is different for calendar weeks and floating months:
Calendar Weeks According to Feature LDAYW:
- USA: Sunday June 5 to Saturday June 25
- Other countries: Monday June 6 to Saturday June 26
Floating months: March 28 to June 27
Supplementary Documentation - AVER_UNIT 0001
Use
Please specify the time unit to be used when splitting the relevant periods.
Procedure
Examples
Dependencies
Supplementary Documentation - AVER_UNIT 0002
Use
Please specify the time unit to be used when splitting the maximum number of periods.
Procedure
Examples
Dependencies
The time unit must be identical to the time unit used in the relevant periods.
History
| Last changed by/on | SAP | 19980505 |
| SAP Release Created in |
