Rhinte30 program

Status to be used for relationships and objects active or planned; only active for integration plan version. Percentage to be used in the relationship. Whether objects and relationships are to be created. Whether old holder relationships are to be delimited if can be decided technically. If and under which name a batch input session is to be created. The integration object types are required for infotype "Organizational Assignment". A program run can take place for one or all object types.

Objects that are missing either in PA or PD can be created immediately. We recommend that you start the report in test mode so you can troubleshoot errors. Written by: Whitaker-Taylor. Subscribe to our blog.

Recent Posts. Recent Popular Categories. When the report is executed, a batch input session is created for personnel numbers that are related with positions in Personnel Planning and Development and that were changed.

Please note the following points regarding the start date of the infotype record update and the validity period of the record from the Personnel Planning perspective. Case 1: Start and end date of the validity period are after the date entered. In this case, a record is created in PA with the same validity period.

There are no changes made on the Personnel Planning side. Case 2: The start date of the validity period lies before the start date entered, and the end date is after it. In this case, a record is created in PA with a start date the same as the start date entered.

The end date of the record is taken over. Browse pages. A t tachments 0 Page History. Jira links. Created by Linna Hao , last modified on Feb 21, Content tree Introduction This report creates a batch input session for specified personnel numbers. Parameter "Start date" Enter the date as of when the changes to infotype records are effective. No labels. Content Tools.