Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PA-PA (Application Component) Personnel Administration⤷
PBAS (Package) SAP HR Master Data Application Development
Basic Data
| Data Element | STAG_RP |
| Short Description | Specify key date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
Supplementary Documentation - STAG_RP 0000
Use
Determines the key date for evaluation. As Customizing of wage types is based on a time, you must enter a date in this field.
Example
Supplementary Documentation - STAG_RP 0001
Use
In this field, you can determine which day is used as the key date in the individual period.
The following values are allowed:
- F = first
The first day in the period is the key date. - M = middle
The middle day in the period is the key date. The middle day is determined in accordance with the period length. For periods that consist of an odd number of days, the middle day is the key date. If the period consists of an even number of days, the later of the two days in the middle of the period is used as the key date. - L = last
The last day in the period is the key date.
This entry determines the date on which data is read from the database.
Supplementary Documentation - STAG_RP 0002
Use
All changes that occur as of the date specified in this field are marked when displayed/printed with the date of the last change (in the case of lists) and with an exclamation mark in front of the header (in the case of ordinary modules).
Supplementary Documentation - STAG_RP 0003
Use
Table T511K is read using the date specified in this field. This entry is necessary if you start the evaluation independent of the payroll area.
Dependencies
If you enter '0' in the second column of the parameter 'Sort sequence' (start evaluation independent of the payroll area), you must enter a date for this parameter. Table T511K is read using this date.
If you enter a number from 1 to 7 in the second column of the parameter 'Sort sequence', the specification of a date is ignored.
Supplementary Documentation - STAG_RP 0004
Use
Germany only.
Supplementary Documentation - STAG_RP 0005
Use
Germany only.
Supplementary Documentation - STAG_RP 0006
Use
Austria only.
Supplementary Documentation - STAG_RP 0007
Use
The date of issue is the date on which the contribution statement is created.
The date is displayed together with the city.
Dependencies
The following entries are possible:
- No entry - the current date is printed on the statement
- Date - the entered date is printed on the statement
Supplementary Documentation - STAG_RP 0008
Use
Austria only.
Supplementary Documentation - STAG_RP 0009
Use
Tax is calculated according to the tax formula valid on this key date.
Supplementary Documentation - STAG_RP 0010
Use
Germany only.
Supplementary Documentation - STAG_RP 0011
Use
Date of the data carrier run.
Supplementary Documentation - STAG_RP 0012
Description
Validity date for the insurance statement.
This date is used as a PER date for selecting data and performing calculations.
Dependencies
Valid date.
Supplementary Documentation - STAG_RP 0013
Description
Date on which statement was created.
The date on which the statement was created can be found on the top left hand side of the statement. The date is included simply to provide more information; it is not used for selections or calculations.
Dependencies
Valid date.
Supplementary Documentation - STAG_RP 0014
Description
Validity date for the initial payroll run.
Use
This date is used as a PER date for selecting data and performing calculations.
Dependencies
Valid date.
Supplementary Documentation - STAG_RP 0015
Use
Enter the earliest retroactive accounting date for all personnel numbers which require retroactive accounting but cannot automatically be recognized by the system. If an earlier retroactive accounting date is specified in the Payroll Status infotype (0003) due to a change in master data, this date is used.
Employees who have left the company in the current payroll period are not automatically selected for the payroll run if the forced retroactive accounting date is specified. If you should require this, you must set the Earliest MD change field in the Payroll Status infotype (0003).
Examples
The standard pay must be increased retroactively.
Dependencies
Before changing the Earliest MD change field manually, contact your system administrator.
Supplementary Documentation - STAG_RP 0016
Use
Germany only.
Supplementary Documentation - STAG_RP 0017
Use
Germany only.
Supplementary Documentation - STAG_RP 0018
Use
You must explicitly enter a posting date in this field.
An entry in this field is permissible for all work file types.
The following applies to country versions for USA, Canada and Japan:
You must make an entry in this field if the work file to be processed originates from a third-party remittance run.
If you start the Transfer to FI/CO program with a variant, do not make an entry in this field as you must adapt the variant each time you start the program.
Procedure
Examples
Dependencies
Supplementary Documentation - STAG_RP 0019
Use
The paper document created by the Transter to FI/CO report (RPCIPO00) can be interpreted as the document on which the payroll results posting is based.
That is why the system proposes the date on which the FI/CO transfer is started as the document date.
When you start the Transfer to FI/CO program with a variant, you should not enter a value in this parameter because you must then adapt the variant every time you start the program. If you do not enter a value in this parameter when creating a variant, the system uses the current system date.
Procedure
Examples
Dependencies
Supplementary Documentation - STAG_RP 0020
Use
The date of issue is the date on which the contribution statement is created.
Dependencies
The following entries are possible:
- No entry - the current date is printed on the statement
- Date - the entered date is printed on the statement
Supplementary Documentation - STAG_RP 0021
Use
You must enter the key date for your reorganization run in this field. The system reorganizes records which start and end before this date.
Supplementary Documentation - STAG_RP 0022
Use
This field enables you to specify a default value for the document date. The entry can be used as the document date (day on which the original document was created) within the accounting department.
In the standard SAP program, the current date is used as a default. This date can, however, be changed.
Supplementary Documentation - STAG_RP 0023
Use
Document date from business trip
Dependencies
The value of this parameter determines whether the document date is determined on the basis of the trip duration:
- No entry : document date from parameter 'Document date'
- Entry = 'B': start date of business trip as document date
- Entry = 'E': end date of the business trip as document date
Supplementary Documentation - STAG_RP 0024
Definition
The posting date is the date on which the document is entered within the accounting department.
Use
On the basis of the posting date, the fiscal year and period are determined for which the accounts referenced in the document are updated.
With regard to document entry, the permitted posting period is used to check that the specified posting date is allowed.
Note
The posting date can be different from the entry date (day of entry in the system) and the document date (day on which the original document is created).
Supplementary Documentation - STAG_RP 0025
Use
Date of standard pay increase.
Procedure
If no further selections are required, only the date of the standard pay increase must be entered.
Otherwise, only the parameters as of T date should be used (with the exception of the personnel number restriction).
The B input parameter prevents batch input records from being displayed and/or printed online.
- T DATE (MMDDYYYY) => date on which the standard pay increase occurs
Supplementary Documentation - STAG_RP 0026
Use
This date enables you to determine when the new data record you created by batch input becomes valid.
If you do not enter a date, the beginning of the current year is used (determined on the basis of the system date).
Supplementary Documentation - STAG_RP 0027
Use
Date of the last time evaluation run (RPTIME00)
Display on the memo list as information for the payee.
Dependencies
If no entry is made and the time is before 12:00 (system time), the previous day is set, otherwise the current date is set.
Supplementary Documentation - STAG_RP 0028
Use
The date on which the record becomes valid.
It is used to set a time-based limit for data to be displayed.
Supplementary Documentation - STAG_RP 0029
Use
The date on which the record becomes invalid.
It is used to set a time-based limit for data to be displayed.
Supplementary Documentation - STAG_RP 0030
Use
Specify the entry period for the selected persons.
Persons whose entry date is not within the specified period are not selected.
Supplementary Documentation - STAG_RP 0031
Use
Key date for importing basic pay data
This field enables you to specify the key date on which basic pay data is imported. The annual salary is calculated on the basis of basic pay data on the key date, multiplied by the monthly factor for monthly earners. Please note that any salary increases that occur during the course of the year are ignored by this evaluation.
Supplementary Documentation - STAG_RP 0032
Use
Enter the date up to which the system should take requested and compensated leave into account.
Supplementary Documentation - STAG_RP 0033
Use
Enter the date as of which requested leave is counted as leave taken. The default value is the current date.
Supplementary Documentation - STAG_RP 0034
Procedure
Enter the date for which an attendance check is performed.
Supplementary Documentation - STAG_RP 0035
Use
Enter the date up to which the evaluations should be retroactively checked even if the system does not require this entry.
As the system automatically recognizes retroactively accounted data, you normally do not have to enter the date.
Supplementary Documentation - STAG_RP 0036
Use
If you enter a date in this field, a pay scale reclassification will be performed for all employess on this key date.
Procedure
Enter the date on which the pay scale reclassification is to take place.
Examples
Dependencies
Pay scale reclassification is performed only for employees whose subsequent PS group or PS level has been set in the customizing system.
The date of a pay scale increase based on age or seniority prior to the specified key date and the date of the next pay scale increase in the "Basic Pay" infotype (0008) have precedence over the key date.
Supplementary Documentation - STAG_RP 0037
Use
If you enter a date in this field, pay scale reclassification is performed for all employees on the key date specified.
Procedure
If you want to use this type of pay scale reclassification (02), enter the date of the PS reclassification in this field.
Examples
Dependencies
Only those employees who have been assigned a subsequent PS group of level are included in the pay scale reclassification. For more information, please read the Define pay scale reclassification based on hours worked section in the IMG.
A jump due to age or seniority or a jump based on the number of working hours with a reclassification date before the key date or the date of the next increase in the Basic Pay (0008) infotype have priority.
Supplementary Documentation - STAG_RP 0038
Use
The batch input session can be run one day after the keydate, at the earliest. Only a system administrator with LOCK-authorization for the authorization object batch input authorizations can unlock or run a batch input session before the keydate. Entering lock dates is optional. If you do not enter a lock date, then the batch input session can be run immediately.
Procedure
Examples
Dependencies
Supplementary Documentation - STAG_RP 0039
Use
Determines the key date for the report. As Customizing for wage types is time-dependent, you must enter a date in this field.
Supplementary Documentation - STAG_RP 0100
Use
Enter a key date for initial transfer of data to cost allocation. The system selects only records which have not been retrieved and have posting date lower than or equal to this key date.
The system date is used as the default value.
An entry in this field only has an effect on data selection if you have marked the Initial transfer checkbox.
Supplementary Documentation - STAG_RP 0101
Use
The batch input session is locked up to the date specified here.
Supplementary Documentation - STAG_RP 0102
Use
To recreate a batch input session, enter the date and time on which the session was initially created in the Retrieval date and Retrieval time fields respectively.
Supplementary Documentation - STAG_RP 0103
Use
Enter a key date for reorganization of cost allocation data. The system selects only successfully retrieved records whose posting date is lower than or equal to this key date.
The default value is 14 days before the system date.
The entry in this field only has an effect on data selection if you have marked the Reorganize old data checkbox.
Supplementary Documentation - STAG_RP 0104
Use
The system selects only absence/attendance types which are valid on the specified key date.
Further notes
Absence/attendance types are defined in table T554S. Please read the IMG section entitled Define absence types.
Supplementary Documentation - STAG_RP 0105
Use
It has recently become necessary to recalculate SMP in the event of a backdated pay increase.
Procedure
Enter the date as of which the pay increase is to become effective. This is the date as of which the SMP must be recalculated.
Supplementary Documentation - STAG_RP 0106
Use
This date indicates the reporting run which is to be written to the data medium.
All notifications whose run date is higher or identical to the date specified here are taken into account.
Example:
Reason for notification Reporting date
Initial registration 03/31/1996
Annual report 96 01/31/1997
Annual report 97 01/31/1998
Reporting date: 01/31/1997
The annual reports for 1996 and 1997 are written to the data medium.
Procedure
Examples
Dependencies
Supplementary Documentation - STAG_RP 0107
Use
This date is stored in cluster 'ZV' for each notification which is written to the data medium.
If you want to repeat the data medium run, enter the same date in the 'Date of data medium run' field.
Procedure
Examples
Dependencies
Supplementary Documentation - STAG_RP 0108
Definition
Enter the date until which the report should be retroactively accounted.
Procedure
Example
You have changed table entries that are relevant for the evaluation of heavy work at night. These changes are not automatically recognised as changes that are relevant to retroactive accounting. You must therefore enter the date until when retroactive accounting should be performed in the report.
Dependencies
If you have only made changes in the retroactive-accounting-relevant fields, you do not have to enter a date. Changes in retroactive- accounting-relevant fields are automatically recognized by the report.
Supplementary Documentation - STAG_RP 0200
Enter the key date on which the payroll results are to be converted. All payroll records up to the current release will then be entered.
The end date and for-period or date of bonus run are decisive for selection.
Example
1.01.1998 as key date.
January 1998 will then be the first for-period for monthly payroll. For weekly payroll on the other hand, it will be 52/1997.
Supplementary Documentation - STAG_RP 0201
Use
Enter the date on which the completeness check of postings is to be performed.
During this process, all payroll results after the date entered are checked.
Dependencies
Example
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in |
