Creating a Write Variant for HRPD_TMC
The system uses the write program RPTMC_HRPD_TMC_WRI
to select the relationship data that is to be destroyed and transfers it to an archive file temporarily so that it can then use the delete programRPTMC_HRPD_TMC_DEL
to destroy this data.
You can run the program in test mode or productive mode. Irrespective of this, you always need to create a variant for the write program (or select an existing variant). For this purpose, you have the following selection criteria and options available:
Note
Note that the Talent Management data is stored not for the person
(object type P
), but for the person ID
. Therefore, when specifying the selection criteria, you must note a few points, which are described below.
Person ID
If you have activated Concurrent Employment
in your system, several employment contracts and therefore several personnel numbers can be assigned to a person ID in the case of employees in concurrent employment or global employees. You can restrict the selection to the data records that belong to the entered person ID. You use this parameter primarily in test mode.
Personnel Number
You can restrict the selection to the data records that belong to the personnel number entered. You use this parameter primarily in test mode.
Note
Note that if concurrent employment is in use, more than one person may be linked to one person ID. It is therefore possible that you enter a personnel number here and the system automatically determined other people linked to the person ID. During selection, the write program uses these people together with the person you entered.
Archiving Subobject
You enter the archiving subobject that contains the data you want to select.
You can select the following archiving subobjects:
Archiving Subobject | Short Description |
|---|---|
1 |
|
2 |
|
3 |
|
4 |
|
5 |
|
6 |
|
7 |
|
8 |
|
9 |
|
Select Data Until
You use this field to enter the date up until which you want to be able to select the data records. Entry of a date is mandatory. The system selects the data depending on the archiving subobject specified as follows:
For archiving subobjects 2, 7, 8, and 9
The data records of the associated infotypes have an explicit end date. Therefore, the system can use this date as a destruction date. In the case of employees who have not left, the system selects all data records whose end date is on or before this date. In the case of employees who have left, the system selects all data records.
For archiving subobjects 1, 3, 4, 5, and 6
The data records of the infotypes do not have an explicit end date. The data is valid until the high date. Therefore, the system cannot adopt the end date as the destruction date in these cases. Instead, the system uses the leaving date and selects only the employees who have left the company before the selection date.
If you specify January 1 2015 as the selection date, for example, the system selects only the employees who have left before this date. If concurrent employment is in use, more than one person may be linked to one person ID. In this case, a person is only deemed to have left once all other persons linked to the person ID have left.
Country Grouping
The system selects the data on the personnel numbers that belong to the country grouping entered.
Note
The country grouping
(MOLGA
) is linked to the r person
(P
). If you use concurrent employment, there are a few things you need to note during selection. If you specify a country grouping here, all persons linked to a person ID
must corresponding to this MOLGA
. If one or more persons are assigned to a different MOLGA
, the system does not select the person ID
.
Archiving
If you choose this option, only the selected data for which the archivability check could be completed successfully is transferred to archive files.
Note
This setting is only useful if you have assigned the ILM object HRPD_TMC
to the audit area ARCHIVING
for the policy category RST
(Residence Rules
) and to the audit area HCM_DP
(HCM Datenschutz
) for the policy category RTP
(Aufbewahrungsregeln
) (transaction ILMARA
).
Destruction of Data
If you choose this option, only the selected data that may be destroyed according to the rules defined in ILM is transferred to the archive files.
Note
This setting is only useful if you have assigned the ILM object HRPD_TMC
to the audit area HCM_DP
(HCM Data Privacy
) for the policy category RTP
(Retention Rules
) (transaction ILMARA
).
Test Mode
If you select this checkbox, the write program is started in test mode. No archive files are created and no data is deleted from the database. The delete program is not started.
Productive Mode
If you select this checkbox, the write program is started in productive mode and archive files are created for the destruction of data.
Detailed Log
If you select this, with
or without success messages
, a detailed log is output. Use this option only to perform an error analysis in test mode. Since the log is very detailed, you must not use it in productive mode.
Log Output
You specify whether the log is written to the list or to the application log.
Choose application log if you want the log to be written to the application log.
Choose list and application log if you want the log to be available in both locations.
Note on Archiving Session
You enter a short text that describes the content of the archive files of an archiving session.
Start Archive Administration
(transaction SARA
).
Enter the Archiving Object
and choose Write
.
Enter a name for the Variant
and choose Maintain
. The Variants: Screen Assignment
dialog box appears.
Define whether the variant is to apply to all selection screens of the program or to individual selection screens. Choose Continue
.
Enter the selection criteria and choose Attributes
.
Define the variant attributes.
Save the variant.