2. Microsoft Office Project Solution Starter Overview SAP-CO/PS Integration David Ducolon Program Manager Project Microsoft Corporation

3. What You will Learn The solution starter architecture The functional design when interfacing with SAP CO and PS What data will be exchanged What limitations exist The functional procedure calls and class hierarchy

4. The Architecture File Drop

5. The Architecture

6. Functional Design Integration with SAP CO 1:1 relationship between projects and internal orders (IO) IO is stored as an enterprise project text field IO is stored as an enterprise project text field Tasks are not created from SAP for CO

7. Functional Design Integration with SAP PS 1:M relationship between internal orders (IO) and project tasks IO is stored as an enterprise task text field IO is stored as an enterprise task text field Tasks ARE created from SAP in the hierarchy represented in SAP PS

8. What Data is Exchanged? Complex Data Types The following data types are used in the definition for a project to be created from SAP exported data: Project definition data CO internal order data WBS element data WBS hierarchy data

9. Data interface Field Matrix Project definition data Input dataMS Project fieldComment Project IDNot mappedThe internal SAP ID is not necessary DescriptionProject nameThe name of the project. A “.Published” is concatenated when the project is created in MS Project Server. Start dateProject start Responsible No Enterprise Project Text n The text field to be used can be dynamically assigned at the administration area of the connector. Plant IDEnterprise Project Text n The text field to be used can be dynamically assigned at the administration area of the connector.

10. Data interface Field Matrix CO internal order data Input dataMS Project fieldComment Order IDEnterprise Task Text n/ Enterprise Project Text n The Ent. Project Text Field is used for an export from SAP CO, the Ent. Task Text Field is used for an export from SAP PS Order nameNot mapped Plant IDNot mapped WBS Element IDEnterprise Task Text n Responsible person Not mapped Start dateNot mappedDefined by the Project or WBS element definition

11. Data interface Field Matrix WBS Element data Input dataMS Project fieldComment WBS Element ID Enterprise Task Text n The text field to be used can be dynamically assigned at the administration area of the connector. Element description Task name Start dateStartNew Tasks in MS Project are created with the constraint “Start no earlier than”. Finish dateFinish

12. Class Structure

13. Data Interface Project Data Service Extended Custom extensions Fully customizable Coded in C#.NET Logging to system logs MethodsProjectCreateSAPGetActualsSAP

14. Export From Project Server Process Query parameters PeriodStart: Start date of the period for which actuals are exported (Format: YYYYMMDD). PeriodFinish: Finish date of the period for which actuals are exported (Format: YYYYMMDD). Check if a SAP CO number exists for a task, If not, check the SAP CO number from the summary task of this task is assigned and so on. The overall project is the top level summary task Projects which have no SAP CO number are deleted Results: GetActualsSAP_YYYYMMDD.xml

15. Limitations No process enforcement ProjectSAP Data rich but limited to extremely standard fields Does not address timesheet adjustments AssignmentGets Does not read MSP_WEB_WORK_ADJUSTED Must be filtered

16. Summary Prescriptive Architecture Best Practices for ERP Integration Foundation upon which you can build your specific solution Many uses Timesheet interface Project/Task Update

17. © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.