Ansicht
Dokumentation
CPRO_MSP_INT_GEN - Integration with Microsoft Project
General Data in Customer Master SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
This process describes the integration between Microsoft Project (MSP) and SAP Portfolio and Project Management.
You can import data from XML files with MSP format and export data to XML files with MSP format as required.
Event though the MSP integration does not use Integrated Office Suites (IOS), the MSP versions supported are the same as for IOS. For more information about supported MSP versions, see SAP note 892638.
To enable the integration, you must fulfill the following conditions.
- An item that is not linked to any project in the base project system (Microsoft Project, External Project Management System, SAP PS) exists in SAP Portfolio and Project Management.
- A Project Management project (referred as Operational Project) exists that is attached to the item.
- Basic configuration steps have been carried out in Customizing for SAP Portfolio and Project Management.
You can import an MSP file to Project Management. When you transfer the project data it becomes operational data in projects in Project Management. When an import takes place, a link is temporarily created between the MSP file and the project to which you are importing the data. The system creates a simulation with the version 0Import.
The project information stored in the MSP file can be imported to Project Management as a project header. If you want to create a Project Management project with a certain project type, enter the correct project type in the CATEGORY field in MSP. For a list of the project types that are available in Project Management, see Customizing for Project Management under Structure -> Define Project Types.
To create a phase in a Project Management project from MSP, you have to mark a task in MSP as a phase. To do this, choose the enterprise text field TEXT20 for the task in MSP and add the required Project Management phase type. For a list of the phase types that are available in Project Management, see Customizing for Project Management Implementation Guide under Structure -> Define Phase Types. Only tasks that are at root level (level 1) can be marked as phases.
When an import takes place, the tasks in Project Management are created below a certain phase, provided that the task is marked as a phase at the highest level in MSP. If the tasks at the highest level in MSP are not marked as phases, the tasks are created below the task hierarchy phase in Project Management. This phase contains all tasks at the top level that are not marked as phases or checklists as well as all subtasks of the phase in MSP.
To create a checklist from MSP in a Project Management project, you have to mark a task as a checklist in MSP. To do this, choose the enterprise text field TEXT21 for the task in MSP and add a checklist type. For a list of the checklist types that are available in Project Management, see Customizing for Project Managementunder Structure -> Define Checklist Types.
Only tasks at the top level or tasks at the first level below a phase can be marked as checklists.
All subtasks of a task at the first level that are marked as checklists are automatically created as checklist items in Project Management. It is not possible to explicitly specify a task as a checklist item. All tasks below a checklist item are automatically created as subtasks below the checklist item.
Predecessors that you enter for tasks in MSP become relationships when they are transferred to Project Management. The relationships are created with exactly the same link type as in MSP. The lag between two tasks in MSP is also transferred to the Project Management project and stored in days.
Resources that you created in MSP are transferred to Project Management as roles.
Note: A resource in MSP corresponds to a role in Project Management while a team member linked to a resource in MSP corresponds to a resource in Project Management.
To be able to import resources defined in MSP as assignments of resources to roles in Project Management, you have to have entered the personnel number of the person in MSP; enter the personnel number in the Codefield.
Each personnel number in MSP must have a corresponding business partner in Project Management. The team member whose personnel number in MSP is linked to a resource, is linked to the role as a resource in Project Management.
Note: Each role is staffed with a maximum of one resource after the project import.
You can import the assignment of roles to tasks in MSP to Project Management 1:1.
When a Project Management project is exported, a new MSP file is created with the required data. The data is exported exactly the same way as it is imported:
The project definition is exported to MS Project as project data.
- The phases are exported as tasks which are marked as phases.
- The tasks below a phase are exported as subtasks of the task marked as a phase
- Checklists are exported as tasks that are marked as a checklist
- Checklist items and subtasks of checklist items are exported as subtasks of the task marked as a checklist
- Roles are exported as resources and filled with the personnel number.
Tasks are assigned the start and finish date of the superior task. MSP controls how this data is transferred to superior tasks. Therefore, the data of the tasks in MSP may differ from that in Project Management.
Any modifications or additions to the assignment table in Customizing for Project Management may lead to inconsistencies.
A Project Management project can be exported any number of times. Each time the project is exported, a new project is created in MSP.
If you have imported projects to Project Management, you can update the projects by reconciling them.
CL_GUI_FRONTEND_SERVICES - Frontend Services ROGBILLS - Synchronize billing plans
This documentation is copyright by SAP AG.
Length: 6752 Date: 20240606 Time: 033049 sap01-206 ( 133 ms )
