Ansicht
Dokumentation
Import and Export from or to MS Project and XML (Enhanced) ( RELNPPM_50_PRO_IMP_EXP )
General Material Data ABAP Short ReferenceThis documentation is copyright by SAP AG.
Short text
Import and Export from or to MS Project and XML (Enhanced)
Use
As of SAP Portfolio and Project Management 5.0, the import and export functions that are available on portfolio level and on project level have been consolidated. The same user interface is now used when starting the import or export from the item and from the project.
The authorization concept has been aligned, as follows:
- For export at project level, at least write authorization for all project elements is required.
- For import at project level, at least administration authorization instead of write authorization for all project elements is required.
- For export at portfolio level, at least write authorization for all project elements is required, and write authorization for the portfolio item is required.
- For import at portfolio level, at least write authorization for all project elements is required, and administration authorization for the portfolio item is required.
You can now start import and export from the Versionswork center directly.
Functional Enhancements for XML and Microsoft Project
During import, you can decide which data is to be imported. You have the following options:
- Structure Only
- Structure and Resources
- Structure, Resources, and Resource Assignments
The system creates a log of all imports and exports. The log contains, for example, the date of the import or export, the user who performed the import or export, and additional information, such as warning and error messages. You can access the log directly during import or export. You can view earlier versions of the log in the log table in the import/export UI.
During import, either a new simulation is created or the operational project is updated. This is decided either by the user during import or via Customizing for the project.
The last imported file is stored in the document management of Project Management. The file can be viewed by choosing the link on the Additional Data tab in the Detail sub view of the project.
When changing the project during import, the changes are logged in the change documents of the project (in case change documents are activated).
When creating a new project by importing, the system automatically generates the project number if this is not provided in the import file.
Microsoft Project-Specific Enhancements
You can now export and import fields of the project definition.
When you add tasks or checklists to the project in MSP and import the project again, the sequence of the tasks remains the same as in MSP. The sequence of tasks and checklists also remains the same during export.
In MSP, it is possible to define lags in relationships with a percentage value. Example: Task 1 (duration 10 days) and Task 2 (duration 1 day) have a finish-start relationship. You maintain a lag of 50% in MSP. During import, 50% of the duration of the predecessor is used as lag in the relationship (5 days).
When exporting the project for the fields Phase Type, Checklist Type, Process, Priority, Duration, Severity, and Currency value list descriptions are created.
Technical Adjustments
As of SAP Portfolio and Project Management 5.0, the import and export UI in both Project Management and Portfolio Management uses the Web Dynpro ABAP OfficeControl UI element for Microsoft Project Integration. Since rendered pages are normally displayed in a Web browser connected to the Internet in Web Dynpro, security aspects must be considered for UI elements like OfficeControl.
The following security measures therefore exist for OfficeControl:
- OfficeControl only communicates with authorized servers.
- Data can only be stored in authorized directories.
- Data can only be read from authorized directories.
The authorized servers and directories are listed in a whitelist (an administrator stores this information locally using transactions WDR_ACF_WLIST and ACF_WHITELIST_SETUP). If requests for access to directories or communication with servers are sent using HTTP or HTTPS, the control first checks whether this is allowed. It then compares the directories or servers in question with the data in the local whitelist file. It only executes the relevant methods if the authorization is set in the white list.
The whitelist certificate needs to be installed locally on each end-user PC to perform the Project Import and Export. The whitelist certificate can be generated using transaction WDR_ACF_GEN_CERT. To install the whitelist certificate, go to transaction ACF_WHITELIST_SETUP and click Install Certificate.
For more information, see Customizing for SAP NetWeaver under Application Server -> Web Dynpro ABAP -> Set Up Whitelist for Active Controlsand Activate Whitelist for Active Controls.
Effects on Existing Data
Effects on Data Transfer
Prerequisites
Import and export from or to MS Project is only supported when either Internet Explorer or NWBC for Desktop (with Browser rendering from Internet Explorer) are used. It is not supported for Firefox, for example. For more information, see SAP note 1402912.
If the browser does not support ActiveX, the system issues a warning message and the application Microsoft Project is not available in the Application dropdown box.
Effects on Customizing
The Customizing for import and export has been consolidated and moved to SAP Portfolio and Project Management -> Common Functions -> Import and Export of Project Data.
Further Information
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 7200 Date: 20240523 Time: 055645 sap01-206 ( 123 ms )
