Description
If you have chosen indirect valuation of basic pay, only the valuationfor the specified date (or a substitute date) is displayed. Indirectlyvaluated wage types for basic pay are flagged as 'I'. This suffices inmost cases. However, sometimes a history of standard pay increases isrequired. This can be displayed with the 'List' function.
Report RPITRF00 satisfies this requirement by creating records forstandard pay increases which can be stored on the database.
Report description
------------------
Report RPITRF00 reads the basic pay and checks whether table 510D (dyn.standard pay increase) contains a valid entry for the report period.The entries in 510D contain variants for pay increases which areprogrammed in this report.
If the existing standard pay increase variants do not suffice, you mustmodify this report and follow this up for each new release.
Table T510D allows you to increase indirectly (in T510) and directlyvaluated basic pay wage types which begin before a key date, and endthereafter, to create records as batch inputs.
The list shows indirectly and directly valuated wage types, and logsall records which begin or end after the key date, together with theirpayment types.
The list contains notes which can assist you in processing.
Special case: A standard pay increase can become valid on the key
date of a pay scale reclassification. Since a pay
scale reclassification (with RPITUM00) takes place
before a standard pay increase, report RPITRF00 queries
event pay scale reclassification.
If this special case should occur, the existing
record is updated.
Explanation of notes
--------------------
- 'New record (basic pay) created'
The imported record complies with the selection criteria.
- 'Record (basic pay) already exists and is unchanged -> no batchinput'
A record already exists for the key date and there is no difference
between the basic pay in this record and that of the existing one -
the existing record therefore does not need to be modified.
- 'Existing record (basic pay) modified'
A record already exists for the key date. The basic pay of the
new record differs from that of the existing record - a batch
input record is created if 'B-INPUT' is set.
- 'Preceding record (basic pay) identical -> no batch input!'
The basic pay of the new record is identical to that of
the preceding record. A new record is therefore not required.
- 'Record (basic pay) only with directly valuated wage types'
This record contains only directly valuated wage types.
- 'Record (basic pay) was changed in spite of a pay scale
reclassification'.
A pay scale reclassification and standard pay increase occur on
the same key date (see 'Special case' documentation).
- 'Records (basic pay) available for the future'
Basic pay records (0008) have already been created for a
future date.
A batch input session cannot be created for future records!
- Valuation notes
'direct' = wage type is valuated directly (entered manually)
'indirect' = wage type is valuated indirectly
'indirect/ = wage type which is intended for indirect
direct' valuation has been overwritten manually.
The report then uses the manual entry.
SAP tables used
---------------
The operative table 510D (dynamic standard pay increase), and those
listed below are used in report RPITRF00.
- T510E (dynamic standard pay increase I)
This table is required if an employee is valuated
according to a PS classification which differs from
the one specified in his/her basic pay record.
- T539J (basic wage types, percentage valuation, reference wage types)
This table is used when a standard pay increase variant
is based on more than one reference wage type.
The different standard pay increase variants for directly valuated wagetypes are defined in table 510D.
Table 510 (pay scale groups) is used for indirect valuation.
Also pay attention to the following tables:
- T511 (Wage type features)
defines indirect wage types
- T512T (Wage type long texts)
are written in the log
- T503 (Employee group/subgroup)
defines the pay scale indicator for table 510
- T538D (Units of time/measurement)
The SAP standard entries ('Int.key' field values =
'Input text' field) are required for importing batch
input files.
- T529A (Events)
You can define your own event if you do not want
to use the standard event '16' and event reasons '01'
(pay scale reclassification) and '02' (standard pay increase).
You should, however, always use an infogroup which contains
infotype 0008 (Basic Pay) and the COP operation
(e.g. infogroup 81). Enter user-defined events/reasons
using the report parameters 'Event for pay scale
reclassification' and 'Event for standard pay increase'.
Implementing standard pay increases
--------------------------------
1. Maintain table 510. (Indirect valuation of pay scale groups)
2. Maintain table T510D. (Dynamic standard pay increase)
3. Maintain table 510E. (Dynamic standard pay increase I)
4. Maintain table 539J. (Reference wage types for standard pay
increase.
5. Start the report with the desired criteria in the online mode.
Batch input records are stored in a batch input session if
'B-INPUT' is set). The report creates an online list with
error messages which can be used for preliminary checks.
6. After you have checked the online list, you can import
the batch input session using transaction SM35.
For more information on standard pay increases, read the IMG sectionentitled Standard pay increase.

Note
Personnel numbers are listed in ascending order.
BEGIN OF UPDATE
Country grouping parameter
WAGE TYPE MODIFIER

Definition
The country grouping is used to display the long texts for wage typesin table 512T.

Dependencies
The valid country modifiers are stored in table 500L.