Hierarchy

⤷

⤷

Basic Data
Data Element | ABK |
Short Description | Date conversion abbreviation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR2 | |
Data Type | CHAR | Character String |
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 | 10 | Abbrev. |
Medium | 15 | Date abbrev. |
Long | 20 | Date conv.abbrev. |
Heading | 5 | Abbr. |
Supplementary Documentation - ABKND 0001
Use
- Austria
BLANK - Other
1 - Illness
2 - Industrial accident
3 - Accident
4 - Occupational illness
5 - Unpaid leave at cost of employee
6 - Unpaid leave at cost of employer
7 - Unpaid leave at cost of employee/employer
8 - Grace period (Public sector) - Germany: Public sector
- BLANK - Not relevant
- 2 - Industrial accident
- Public sector: Industrial accident, accident en route to work, occupational illness
- 3 - Accident
- Public sector: Ill after sterilization or termination of pregnancy
- 9 - Health spa stay
- Public sector: Action for preventative medical care or rehabilitation
- Netherlands
- BLANK - Not relevant
- 1 - Calculate continued sick pay
- 2 - No continued sick pay, but relevant in calculation of absence period
- Belgium
- BLANK - Not relevant
- X - Enables differentiation between half-day and full-day illness periods
Supplementary Documentation - ABKOART 0100
Use
The "To" cost element defines the upper limit of a cost element interval.
You can also define individual cost elements instead of an interval.
These cost elements are for the condition type you are currently maintaining.
Procedure
Examples
Dependencies
You can assign cost elements only to base condition types.
Supplementary Documentation - ABKOART 3300
Use
Together with the 'To cost element' field you can create a range of cost elements. If you want to define individual cost elements, only enter one cost element in the 'From cost element' field.
The current calculation base comprises the cost elements entered in this way.
Procedure
Examples
Dependencies
You can use both primary and secondary cost elements as the calculation base. If you use secondary cost elements, these must be posted before you calculate the imputed costs.
Imputed cost elements (type 03 cost element % or type 04 target=actual) are ignored when determining the base values (if they are contained in the cost element range entered).
Supplementary Documentation - ABKRS 0001
Definition
The payroll subunit has two functions:
- It selects data from the sequential file for report RPRFIN00. Records for employees in this payroll subunit are selected.
- It determines the posting period automatically if it has not been specified already.
- RPRIRB00 is started from RPRFIN00:
The payroll subunit determined by RPRFIN00 is used to determine the period. Any entry made by the user is ignored. - RPRIRB00 is not started via a different report:
The default value or the user's own entry is used.
Supplementary Documentation - ABKRS 0002
Use
This field defines the payroll accounting area valid for the reference personnel number in the validity period of the current infotype record.
All reference personnel numbers of an employee which are to be accounted simultaneously must have the same payroll accounting area. The reference personnel numbers chosen for the current priority must therefore have the same payroll accounting area.
If this field is empty, the reference personnel number is not assigned to a payroll accounting area in the period specified.
Supplementary Documentation - ABKRS 0003
Use
This field defines the payroll accounting area valid for the reference personnel number in the validity period of the current infotype record.
All reference personnel numbers of an employee which are to be accounted simultaneously must belong to the same payroll accounting area. The reference personnel numbers which you choose from the Reference Personnel Numbers infotype (0031) must belong to the same payroll accounting area.
If this field is empty, the reference personnel number is not assigned to a payroll accounting area in the period specified.
Supplementary Documentation - ABKRS 0004
Use
This field specifies the payroll subunit to which the reference personnel number belongs in the validity period of the previous infotype record.
If the field is empty, the reference personnel number is not assigned to a payroll subunit in the corresponding period.
If a payroll is run for a personnel number together with its reference personnel numbers, the reference personnel numbers assigned to the employee that must be included in the payroll run must all be in the same payroll subunit.
Supplementary Documentation - ABKRS 0005
Use
Payroll subunit: For period
Supplementary Documentation - ABKRS 0006
Use
Payroll subunit: In period
Supplementary Documentation - ABKRS 0007
Use
This entry is used in the Validation data block.
Enter a value in this field if the work file to be processed originates from an evaluation of a periodic payroll run.
If you have maintained the personnel control record for the payroll area (this is MANDATORY in the production system), you can use it to determine the payroll period and payroll year which are written automatically to the next two fields. This allows you to create variants which you can use several times without having to make any changes.
Note: The payroll area, period and year are also used as validation data. If the items in your work file are incompatible with this data, they are ignored. Ignored items are listed separately when you transfer data to FI/CO.
This entry is used in the Special selections from posting data block.
By entering a selection option, you can delimit the payroll areas to be transferred which enables you to divide the posting data into several subsets. To ensure that these subsets can be posted separately, they must not overlap.
Procedure
Examples
Dependencies
History
Last changed by/on | SAP | 19950401 |
SAP Release Created in |