Project Schedule Import using MS Project file
Project schedule import using MS Project
- Project Schedule import with BOQ linking
1. Import BOQ in Project WBS form and Create WBS Activities accordingly
2. To import schedule of the same, Create an MS Project file and add custom columns as shown in the attachment
3. In the Activity Code column mention WBS activity Code generated in ERP in front of relevant tasks and mention task weightage in the Activity Code Percentage
(You can mention the Activity ids also instead of Code so ERP will auto fetch Codes on that basis)
4. This will create Project schedule separate BOQ activities that can be managed in detail task wise
5. To import schedule go to MSP Integration Page available in the left menu
6. Select Project Name, Sub Project, and Select Import type as Project Schedule
7. Upload MSP file to be imported
8. In ERP once the file is uploaded can be checked for further details by clicking view MSP data, in View MSP Data system will check for incorrect format or data, and then only Integrate Button will be enabled. Click on Integrate MSP data then system will import that file in ERP
9. Once the import completes system will pop the message and the same data will be available in the Project Schedule form and Project Schedule Bar Chart
10. According to this, it will also generate Project Bar Chart for WBS activities
- Project Schedule import without BOQ linking
1. To Import Project Schedule without linking of the WBS activities create the file as shown below where no any other custom columns required to add in MSP file
2. Rest follow the same process to import the file from MSP Integration
3. In This process WBS activities and Project Schedule will remain seperate and there will be no linking in between.
o MSP Import DOs and Don’ts ·
DOs
i. All Activities should be properly grouped
ii. Dependencies are Properly mentioned
iii. Task Mode (Auto, Manual) should be the same for all activities
iv. While entering Lag period Unit should be days for all tasks
v. If Calendar Setting is there in MSP then the same should be entered in ERP ·
Don’ts
i. Don’t keep different modes for tasks, it should be either Auto-Schedule or Manual Schedule
ii. Don’t put Start date manually if dependency is mentioned as ERP will not consider that dependency if Manual Start date is there
iii. Lag unit should not be different than days
iv. Actual Strat and Actual End date should not be there in the MSP file
v. If Activity Codes are entered then Percentages in front of them should be mentioned for all Activities
vi. Tasks Schedule end date should not be edited manually. It should come according to task duration only
vii. Special Characters as '-', ' ' (space), ':', should be avoid while mentioned in task name
Notes
i. If there Actual Start Date and Actual End Date is defined in MSP file for any task then in ERP it will fetch in Manual Start Date and Manual End Date and predecessors in MSP file for that task will not be considered and entred in ERP
ii. While doing an import from MSP to ERP we have taken Unique Id from MSP into consideration as Task id of ERP and on that basis Predecessors are also assigned
iii. In the case of 'Project Schedule import with BOQ linking' in WBS Activity duration days will be zero but the Schedule Start and End date will get calculated as per the Schedule defined in the Project schedule form. It will take the Minimum start date and Maximum end date from the list of tasks where that Activity is linked.