Automatic
Creation of Employee Requirements Records (Splits) 
Use
When planning employee resources, you can split operations and generate capacity loads for individual people. This information - known as capacity requirements records (= splits) can be:
- Entered manually on the requirements assignment screen of the required operation
- Created automatically by the system
The automatic function enables you to save time on recurring planning situations of this type by using partner functions. You do not need to enter the distribution of work manually for each operation; the system does this for you. When you save, it creates requirements records for the desired employees. It thereby divides the work equally between the specified people using the partner functions. If you do not want the work to be divided in this way, you must change it manually.
If you enter employee requirements records manually for certain operations when the order is created, these are not overwritten by the automatic function when you save.
The automatic creation of employee requirements records is only executed by the system when an order is created or for newly created operations. It is not executed again for changes. For example, if you delete all the requirements records for an operation in the requirements assignment screen in change mode and save the order, the system does not create any new requirements records. If you want to use employee requirements records again in this situation, you must enter them manually.
Changes to partner information in the order also do not have any effect on an order already saved. For example, if you add another role "Employee responsible" for an order in change mode and save, the system does not change the requirements records already created. If you need another employee requirements record for an operation in this situation, you must enter it manually.
Effects on Customizing
- In the Customizing for Plant Maintenance and Customer Service, you must assign a partner determination procedure that enables partner functions, which have partner type "Person" (for example, "Employee responsible"), to the required order type. One of these partner functions must be entered in the field for the automatic generation of splits, (Split gen. ). Only this partner function is considered when the employee requirements records are created automatically.
- The partner functions of type "Person" must refer to personnel master records in Personnel Management.
Check whether the Customizing settings for the definition of the partner determination procedure and its assignment to the order type correspond to your requirements. Make changes as required.