The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help
.
. 
Master Data Adjustment
Information- Master data can still be adjusted after its creation. Some typical application cases and suitable workflows are described below.
- The changing of master data requires access rights to the modules of the PM administration role.
Adjust Last Name (e.g. After Marriage, Divorce)
Example- An employee marries or gets divorced. Her/his last name must therefore be changed.
Employee Changes Department
Example- An employee is employed in and planned for another department.
- Open the Resource Structure module.
- Click on the name of the resource.
- Adjust the Name of the parent resource field as required.
- Adjust the Resource structure code field.
- Save.
- When the department is changed, the possible change of the default cost type and of the default cost center of the resource is to be bared in mind as well as the impact this has on the cost type and cost center of the planning records in existing projects.
- The availability data of the parent resources is updated automatically.
ID Change
From DB 39.5.12
Example
- After name change or due to incorrect assignment, an identity change may be necessary.
- NEW Open Change Person ID
- Enter the new person ID in the New ID field.
- Now, you have the option to
- either carry out the ID change immediately
- To do so, click on the Assign Stakeholder button.
- or have a preview displayed first and then carry out the change.
- To do so, click on the Preview button.
- All data tables of the PLANTA project database are displayed, and the number of records to be changed in the respective table is displayed opposite of each table.
- After you have checked the preview in the preview field, click on the Start ID change button.
- To do so, click on the Preview button.
- either carry out the ID change immediately
- Subsequently, the list of data tables is displayed again with a specification of the number of changed records per table.
- The ID (code) of the person is changed in both the master data and all person assignments of the entire PLANTA project database.
- The auto commit to the database is automatically switched on and off during the change process.
- The change is visible in other modules, e.g. Resources.
Up to DB 39.5.12
Example
- After name change or due to incorrect assignment, an identity change may be necessary.
- Open Resource ID Change
- Enter the new person ID in the New resource field.
- Now, you have the option to
- either carry out the ID change immediately
- To do so, click on the Assign Stakeholder button.
- or have a preview displayed first and then carry out the change.
- To do so, click on the Preview button.
- All data tables of the PLANTA project database are displayed, and the number of records to be changed in the respective table is displayed opposite of each table.
- After you have checked the preview in the preview field, click on the Start button.
- To do so, click on the Preview button.
- either carry out the ID change immediately
- Subsequently, the list of data tables is displayed again with a specification of the number of changed records per table.
- The ID (code) of the resource is changed in both the master data and all resource assignments of the entire PLANTA project database.
- The auto commit to the database is automatically switched on and off during the change process.
- The change is visible in other modules, e.g. Resources.
Employee Leaves the Company
Example- Employee leaves the company
- The person, the person properties, and the respective resource are to be archived (by setting the Leaving date/Left on date). Caution: Do not delete!
- If the person or the resource itself is deleted, both the planning (remaining data) as well as reports and evaluations are falsified since they no longer contain actual data.
- The user of the respective person can be deleted if required. This has no impact on the reporting system in PLANTA project.
- If the person or the resource itself is deleted, both the planning (remaining data) as well as reports and evaluations are falsified since they no longer contain actual data.
- The remaining planning of the employee resource is to be checked and the effort is possibly to be replanned.
From DB 39.5.11
- In the Persons module:
- Enter the leaving date in the Leaving date field on top level. This is automatically inherited by all person attributes as well as by the Left on field in the Resource Data Sheet.
- Empty the Start period and End period fields in the Resource Data Sheet module additionally.
- Save.
- Result: the person and the respective resource are archived. The resource is no longer displayed in any of the resource listboxes and cannot be used for new resource planning.
- In the Resource Planning module:
- Check the resource planning and replan the remaining effort if necessary.
Up to DB 39.5.11
- Enter the leaving date in the Leaving date field on top level.
- Enter the leaving date in the to field of the user.
- Enter the leaving date in the to field of the stakeholder.
- Enter the leaving date in the to field of the person resource.
- Save.
- Result: the person and the respective resource are archived.
- Enter the leaving date in the Left on field of the stakeholder.
- Empty the Start period and End period fields.
- Save.
- Result: the resource is archived. The resource will thus no no longer be displayed in any of the resource listboxes and cannot be used for new resource planning.
- Check the resource planning and replan the remaining effort if necessary.
- From the leave date on, employees who have left the company are no longer considered in further planning and no longer displayed in different modules.
| See also: Master Data Entry |
 |
|
