Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE (Application Component) Germany⤷
P01C (Package) HR Customizing: Germany
IMG Activity
| ID | OHADBECK0 | Special Features of Statements |
| Transaction Code | S_AHR_61006590 | IMG Activity: OHADBECK0 |
| Created on | 19981221 | |
| Customizing Attributes | OHADBECK0 | Special Features of Statements |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADBECK0 |
Special features of statements
- Manual fields
- Printing the payroll results
- Statement wage types
- Other payments: tax-free and subject to tax
- Unpaid absences
- Regular gross tax amount
- Constants
- Time data
- Leave data
- Fictitious net calculation
- Fictitious net calculation from the master data
- Fictitious net calculation from the payroll results
- Non-recurring payments less than 300DM
- Flat-rate remuneration to be taxed
- Direct net deduction- direct insurance
Employee association contributions - CS - Consideration of SPF
- Controlling printing of table using rules
The examples in this unit refer to setting up forms with the help of the form editor. Of course, these can be copied to maintenance using views.
1.) Manual fields
For statements it is necessary to be able to enter certain data manually. For example, if this data is not available in the system. The capacity to enter data manually can be accessed in two different ways.
- Purely manual fields
Fields whose contents are not held by the system can be brought onto the statement in the partial object single fields by entering `MAN´in the table field and ´´in the field table field. A field to be maintained manually will be created.
If a fixed text is stored in the partial object background for this area then this can be overwritten. This entry also enables you to overwrite texts that have been entered.
- Fields that can be overwritten
If the information held in the system is not quite definite and you would like to make it so that it can be overwritten on printing, you can do so by entering conversion 99 in the conversion field (partial object individual fields and rules). The value found in the system will then be displayed, but can be corrected manually.
2.) Printing the payroll results
The individual wage types (from results table RT for payroll results) are totaled in a statement wage type and stored in internal tables. The following apply
- BRT - monthly values
- BCRT - total for the statements period
- LRT - values from the last months statement
- LCRT - can only be used if the statement has statement
type F:
the total for the current year is stored in table BCRT
the total for last year is stored in table LCRT
3.) Statement wage types
There are four possibilities for coding a statement wage type.
- Wage types are summarized into one statement wage type
Every wage type entered is included either positively or negatively in the statement wage type, as specified by the mathematical sign.
Example
Statement wage type LFL1. Further regular benefits are coded.
Cumulation identifier: LFL1
The addends are
Table Identifier Long text Mathematical sign
--------- ------------- -------- ---------------
RT /358 ER-HI allowance +
RT /359 ER-HI allowance priv.supplement +
RT /368 ER-PI allowance +
RT /369 ER allowance, fixed-term LI +
RT /378 ER allowance UI +
RT /3Q8 ER allowance NI +
RT /3Q9 ER allowance NI priv.supplement +
- Wage types that are set up in the assign wage types for form printing step, are included in a cumulation wage type.
Entries have to be made in the adapt control parameters and assign wage types for form printing steps. The relation between entries is as follows:
- Adapt control parameters:
An Evaluation class is assigned to the statement in field B evaluation class.
Classes 06-10 are reserved for statements. Evaluation classes 06 to 08 are used by SAP, 09 and 10 are available to you as a customer.
- Assign wage types for form printing:
The wage types requested are maintained in this evaluation class with a specification and then are summarized to certain groups.
In this case 01 means non-recurring payment, 09 employment tax, 10 church tax, and so on.
- Cumulation identifiers:
By entering **xx in the identifier field, only the wage types that are coded in the evaluation class (specified in adjust control parameters) with xx are accessed.
Example
In the statement for sick/injured/transition payment, gross pay should be identified without non-recurring payments. The technical wage type total gross amount (/101) influences the statement wage type BRUG (total gross amount) positively and the non-recurring payments are deducted.
- Adapt control parameters step
Statement number 14
B Evaluation Class 08 - Assign wage types for form printing step
Wage types M110 (vacation allowance) and M120 (holiday pay) and M150 (13th month's salary) are coded in evaluation class "08" using 01.
- Cumulation identifier:BRUG
Table Identifier Mathematical sign
------- ------------- ------------
RT /101 +
RT **01 -
- The entry in Customizing triggers an internal calculation of the statement wage type
An internal calculation of this wage type is triggered by the same entries in the identifier fields for cumulation identifiers and addends.
Such wage types are, for example ABZ1, NET1 and NET2.
Example
Cumulation identifier: NET1
Table Identifier Mathematical sign
------- ------------- ------------
Dummy NET1
Pay attention to the fact that in some cases the coding of more statement wage types is necessary for internal calculation.
Example
- The agreed gross BRU1 must be coded for the fictitious net amount NET1.
- The wage types BRUG, BRU2, BRU6, PVKZ and SVTG must be coded for the fictitious net amount NET2.
- Unpaid absences are coded by the processing class absences and absence evaluation rule.
The entry in the identifier field consists of the following:
- Position 1-2: Processing class absences
- Position 3-4 : Absence evaluation class
Example
Cumulation identifier: UBAW
Table Identifier Mathematical sign
------- ------------- ------------
UBAW 0302
Processing class absences 03 means health cure
Absence valuation class 02 means illness/health cure
For more information see Special features of statements -> Unpaid absences .
Special statement output wage types
There are a multitude of statement wage types for the many various standard forms.
There are statement wage types with a fixed wage type name, that are accessed in the report and others whose name is selected freely. Wage types with fixed names are listed and explained in the following. For the meaning of the statement wage types whose mames have been selected freely, see the wage type text.
Fixed statement wage types
Statement wage types of variants 1 and 2
- BAK1 Employee association gross from master data (see Notional Net Calculation)
- BAK2 Employee association gross from payroll (see Notional Net Calculation)
- BRUA Gross remuneration from the master data
This cumulation wage type is required in the training statement and its subsequent statement to code the agreed gross remuneration from the master data. Wage types coded with BRUA are determined from infotype 8 or 14 (if paid monthly). The payments are placed in internal table BRT; however this is not done monthly, rather only when the payment has actually changed. - BRUG total gross amount (see fictitious net calculation)
- BRU1 Agreed gross pay (s. fictitious net calculation)
The wage types entered in the basic pay and re
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHADBECK0 | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHADBECK0 | 0 | HLA0003772 | Statements |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19981221 |
| SAP Release Created in |
