/BKC/SOL21_PBKLON - Clone&Test! - Copy and anonymization of applicant dataTXBHW - Original Tax Base Amount in Local Currency rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
The program 'PB Copy' is used to copy applicant data (all infotypes from table T582A, applicant-dependant clusters of table PCL3, qualifications, appraisals, relationships and optionally the advertsements to which the applicants are assigned) between different SAP HR systems and/or clients.
The tables from which data is to be copied should have the same stucture in the source system and the target system. It is not possible to copy data between different releases.
All personal data of the applicants can be anonymized (scrambled) while being copied (data security aspect).
In order to anonymize the data, a name for an anonymization set must be provided. A set contains all anonymization rules for different tables and their fields. By defining appropriate name conventions the user should make sure that the anonymization sets for the report /BKC/SOL21_ KLON (PA Copy) are separated from the sets for the PB Copy program. We recommend to use the prefix 'PB-..' for the anonymization sets for the PB Copy program.
Anonymization sets can be maintained by the program /BKC/SOL21_ANON. You can jump directly to this program by pressing the button 'Maintain set' in the selection screen.
The option 'Create new apllicant numbers' allows applicant numbers to be copied within the same client.
By entering a target system in the form of an RFC destination applicant data can be transferred to any other SAP HR system.
Alternatively, you can copy the data into a sequential file.
The default directory in which a sequential file will be stored is the usual transport directory. This default can be altered however by changing the parameter DIR_DEFAULT in table /BKC/S21_PARAMS.
Before the data is copied, the existence of the applicant number in the target system is checked. If the applicant number already exists the applicant will not be copy and an error message will be shown. As an alternative, the applicant number may be deleted. This enables repeated testing with the same source data.
Always a check against the table T000 is made to make sure, that the target client is not productive. Into productive clients no data can be transferred!
If the data is stored into a sequential file, the upload can be done using the report /BKC/SOL21_PBKLUP. This should only be done on a system which runs the same SAP-Release as the source system. If the releases differ, the upload could work, but the data may be corrupted.
Another reason for errors could be a difference between source and target system concerning the state of customizing and/or development. If such an error occurs, the affected infotypes (e.g. customer specific infotypes) or clusters should be excluded from the copy.
After the collection of all applicant numbers that should be copied, an additional authorization check can be made in an external program. An example and the needed interface are given in the modulepool /BKC/SOL21_EXTF with the routine CHECK_AUTH. In order to redirect the call to a user-defined routine, an entry in the table /BKC/S21_EXT_F must be made with these values:
|FORMROUTINE||name of an existing routine in this report|
The determination of the target applicant numbers is done in an external routine and can be controlled
by the user. An example and the needed interface are given in modulpool /BKC/SOL21_EXTF with the routine CREATE_NEW_APPNR.
The target of the call is defined by an entry in table /BKC/S21_EXT_F in which the fields must be filled with the following values:
|FORMROUTINE||Name of a Form routine in the above mentioned report|
The table /BKC/S21_PARAMS can be filled with parameters which will control the copy program. The following values are valid for the PA Copy as well as for the PB Copy program:
Default value of the path in which the export files of the copy program should be created. If no value is given or if this parameter is not in the table, then a subdirectory within the standard SAP-transport directory will be proposed. The content of the field is interpreted as a string of characters.
Default value for the determination of the memory size which can be used for SQL-statements. If no value is given for this parameter, the copy program will assume the empirically determined value of '12', the prior standard.
This value of '12' can be decreased if the copy program aborts with an error indicating there it is not enough memory for all the results of a SQL-statement.
The value of MAX_MEMORY modifies the package size used for SELECT-statements. An increase of the value may reduce necessary number of physical read processes and may therefore lead to an increase in performance. These are general responses to memory problems: However, no specific advice can be given because the optimal value of this parameter strongly depends on the hardware used (mainly memory) and on the inter-operation between the SAP-system and database.
Number of lines in WHERE clause for internally generated Select statements. The value '30' has until now produced good results.For more information regarding increasing this value please see the parameter MAX_MEMORY.
The following values are only valid for the PB copy program:
ANON_PB_ALWAYS_SWITCHED_ON If this parameter is filled, then the checkbox 'Anonymize data during the copy' is checked and cannot be changed by the user. This means that a user can not copy any data without scrambling them.
ANON_PB_SET_CANNOT_BE_CHANGED If this parameter is filled, then the name of the anonymization set in the selection screen of the PB copy program cannot be changed.
The button 'Maintain set' will not be shown.
Default value for anonymization set.
The tables from which data should be copied must be identical in both the source and target system. Copying between systems of different releases is not possible.
The same customizing must be present in both the source and target system.
This is particluarly (but not only) concerning the following items:
- Wage types
- Applicant groups / ranges
- Unsollicited application groups
- Applicant action types
- Recruitment instruments
- Document formats for internet applications
The neccessary RFC-destinations must be defined. The "RFC-User" must have the appropriate rights in the target system/client.
The report and all needed function modules must exist in both the source and the target system.
The selection of the applicants is handled through the logical database PAP. By pressing the button 'PAP parameters: ON/OFF" you can show or suppress the additional selection options from the standard PAP selection screen.
Screen: Selection and conversion
INCLUDE /BKC/SOL21_PBKLON_P_ASSTXT OBJECT DOKU ID TX
INCLUDE /BKC/SOL21_PBKLON_P_ZASSNR OBJECT DOKU ID TX
Screen: Data selection
Tables in customer namespace
Screen: Target options
Options for data in target system
Screen: Protocol options
BAL Application Log Documentation ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 9789 Date: 20191021 Time: 164327 sap01-206 ( 39 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.