SAP ABAP IMG Activity SIMG_OHP3SXDA (Data Transfer Workbench)
Hierarchy
☛ SAP_HRGXX (Software Component) Sub component SAP_HRGXX of SAP_HR
   ⤷ PE (Application Component) Training and Event Management
     ⤷ PP9C (Package) Training and Event Management - Customizing
IMG Activity
ID SIMG_OHP3SXDA Data Transfer Workbench  
Transaction Code S_AHR_61011940   IMG Activity: SIMG_OHP3SXDA 
Created on 19990204    
Customizing Attributes SIMG_OHP3SXDA   Data Transfer Workbench: Personnel Planning 
Customizing Activity SIMG_OHP3SXDA   Data Transfer Workbench: Personnel Planning 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_OHP3SXDA    

Edit Transfer File

In this section, you can use report "RHMOVE00" to generate a sequential file of your legacy data for further processing by report "RHALTD00". In addition, in this step you can use report "RHMOVE40" to display the generated test file and edit the test data.

Activities

  1. Create your test data in the PD database.
  2. Start report "RHMOVE00" to transfer the data records from the PD database to the sequentiaal file.
  3. Start report "RHMOVE40" to display and, if required, change the data records.

Further notes

For more information, refer to the online documentation of the reports "RHMOVE00" and "RHMOVE40".

Execute data transfer of personal data

In this step, you make the necessary system configurations for changing standard object types and creating new object types.

Caution

You should not create new object types without first consulting SAP.

You can make the following settings:

  • You can specify the relationship proposed as default during the authorization check. For more information, refer to "Structural authorization".
  • You can create and change external object types that are not administered within Personnel Planning, for example, object type 'Person' from Personnel Administration.

    In this case, you must specify the interface program used to access these object types.

  • You can define an object type hierarchy for reporting.
  • If required, you can change the code of a standard object type (for example, "O" for organizational unit, "T" for task).

Example

If you request a report on positions, the system reads objects whose object type is the same as the value of the semantic abbreviation "PLSTE" in the parameter group "OTYPE" - in this case "S".

  • You can maintain the control entries for object-type related transactions.

    For each object-type related transaction (PO** = Menu-guided infotype maintenance), you store the object type edited in the transaction.

Note

You can create two-digit numberical object types in the range "01" to "99".

Activities

  1. Define the mandatory relationship, if required.
  2. Create external object types if required and enter the program used to access these object types.
  3. Define the object type hierarchy for reporting.
  4. Change the code of a standard object type only if you cannot avoid it. When doing so, use the name range reserved for customer-specific entries.
  5. When you have created new object types, change the value of the semantic abbreviation in the parameter group OTYPE for each object type where necessary.

    Similarly, change the value of the semantic abbreviation in the parameter group TCODE for each object-type related transaction.

Business Attributes
ASAP Roadmap ID 254   Transfer Data 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_OHP3SXDA 0 HLA0009703 Training and Event Management 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
DWBDUMMY D - Dummy object SXDA 07770000PH SAPDXfer: Initial Data Transfer Tool Support 
History
Last changed by/on SAP  19990205 
SAP Release Created in