Microsoft Project Server(MPS) Sample Integration … Project Server(MPS) Sample Integration...

How-To Guide

SAP Enterprise Project Connection 2.0 SP02 (Patch05 & UP)

Document Version: 1.0 – 2014-04-28

CUSTOMER

Microsoft Project Server(MPS) Sample Integration Solution(SIS) Default Business Rules, Mappings and Configuration

2 Error! Reference source not found.

CUSTOMER

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when they

are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,

names of variables and parameters, source text, and names of installation, upgrade and

database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they

appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

Error! Reference source not found.

CUSTOMER

© 2013 SAP AG or an SAP affiliate company. All rights reserved. 3

Document History

Version Date Change

1.0 2014-04-28 Original Document


CUSTOMER


Table of Contents

1 Introduction ...................................................................................................................................................... 5 1.1 SAP EPC SIS Disclaimer ......................................................................................................................................... 5 1.2 Intended Audience .................................................................................................................................................. 5 1.3 Additional Documentation...................................................................................................................................... 5 1.4 Prerequisites ............................................................................................................................................................ 6 1.5 Overview of SAP EPC Transactions ....................................................................................................................... 6 1.6 Transfer Projects transaction configuration ........................................................................................................ 7

2 SAP PS to Microsoft Project Server ................................................................................................................. 8 2.1 Preparation .............................................................................................................................................................. 8 2.2 Workflow .................................................................................................................................................................. 9 2.3 Object Mappings ..................................................................................................................................................... 9 2.4 SAP Project Definition Field Mappings ................................................................................................................ 10 2.5 SAP WBS Element Field Mappings ....................................................................................................................... 11 2.6 SAP Network Field Mappings ................................................................................................................................ 13 2.7 SAP Network Activity Field Mappings .................................................................................................................. 15 2.8 SAP Activity Element Field Mappings .................................................................................................................. 17 2.9 SAP Work Center–Resource Field Mappings ...................................................................................................... 19 2.10 SAP Work Center-Assignment Field Mappings .................................................................................................. 20 2.11 SAP Relationship Field Mappings ......................................................................................................................... 21 2.12 Milestone ................................................................................................................................................................ 22

2.12.1 SAP WBS Element Milestone Field Mappings .................................................................................... 22 2.12.2 SAP Activity Milestone Field Mappings .............................................................................................. 24

2.13 SAP Material component Field Mappings ........................................................................................................... 25

3 Microsoft Project Server to SAP PS ............................................................................................................... 27 3.1 Workflow ................................................................................................................................................................ 27 3.2 Object Mappings ................................................................................................................................................... 28 3.3 MPS Project Field Mapping .................................................................................................................................. 28 3.4 MPS Summary Task – WBS Element Field Mapping ......................................................................................... 29

3.4.1 MPS Summary Task – SAP WBS Element Hierarchy Field Mapping .............................................. 30 3.5 MPS Task – Network Field Mapping .................................................................................................................... 30 3.6 MPS Task – Network Activity Field Mapping ....................................................................................................... 31 3.7 MPS Task to Activity Element Field Mapping ..................................................................................................... 33 3.8 MPS Dependency to SAP Relationship Field Mappings .................................................................................... 35 3.9 Milestone Task ....................................................................................................................................................... 36

3.9.1 Milestone Task to WBS Milestone Field Mapping .............................................................................. 36 3.9.2 Milestone Task to Activity Milestone Field Mapping ......................................................................... 37

4 Limitations and Restrictions ..........................................................................................................................39


CUSTOMER


1 Introduction

SAP Enterprise Project Connection (EPC) 2.0 SP02 Patch05 and subsequent releases includes Sample Integration

Solution (SIS) for Microsoft Project Server (MPS) that demonstrates data synchronization between the SAP ERP and

Microsoft Project Server. SAP EPC SIS allows you to integrate project related data from SAP Project System (PS) to

Microsoft Project Server and from Microsoft Project Server to SAP Project System. The aim of SAP EPC SIS is to

provide ideas, ready to use mappings and business rules to the developer for developing the real live integration

scenario based on customer’s specific integration requirement.

This document provides the mappings and business rules of the SAP EPC SIS for MPS.

1.1 SAP EPC SIS Disclaimer

You must review the SAP Enterprise Project Connection (EPC) Sample Integration Solution (SIS) Terms of Use and

Disclaimer. This disclaimer can be found either in SAP Note 1994073.

1.2 Intended Audience

This document’s target audience includes the following SAP EPC user roles:

o Planner

Responsible for creating and maintaining work orders in Plant Maintenance or projects in Project System

o Scheduler

Responsible for creating and maintaining project schedules in a project management system

o Executive

Responsible for operational, maintenance, or resource efficiencies and effectiveness

1.3 Additional Documentation

SAP EPC also includes the following documentation that is available at http://help.sap.com and then SAP Business

Suite → SAP Product Lifecycle Management → SAP Enterprise Project Connection 2.0.

o SAP Enterprise Project Connection Solution Operations Guide

For the product administrator, this document describes how to configure the application and the tasks

necessary to support SAP EPC users.

o SAP Enterprise Project Connection Installation Guide

For the network administrator, this document contains information about how to install and configure SAP

Enterprise Project Connection.

o SAP Enterprise Project Connection Application Help


CUSTOMER


For the network administrator or user, this document describes the basic functionality of SAP Enterprise

Project Connection.

o SAP Enterprise Project Connection Security Guide

For the network administrator, this document describes the security settings of SAP Enterprise Project

Connection.

1.4 Prerequisites

Sample Integration Solution (SIS) for Microsoft Project Server (MPS) has explicit dependency on the following SAP

EPC component release and any subsequent releases of these components:

1. SAP EPC Java component:

a. SAP ENTERPRISE PROJ CONN J 2.0

i. SAP ENTERPRISE PROJ CONN J 2.0 SP02 Patch 05 and up

b. EPCCTC 2.0

i. EPCCTC 2.0 SP02 Patch 01 and up

2. SAP EPC ABAP Add-on component:

a. SAP ENTERPRISE PROJ CON 2.0 60

i. SAP Note 2007441 - Using Customizing tables /SEPC/XFER_PR_T and

/SEPXFER_OR_T without implementing BADIs

1.5 Overview of SAP EPC Transactions

From the SAP Easy Access menu, users can access SAP EPC transactions. These transactions are located in the

Enterprise Project Connection folder of the Cross-Application Components.

The following transactions are part of SAP Enterprise Project Connection:

1. /SEPC/XFER_PROJECT – Transfer Projects.

The Transfer Projects transaction transfer data between SAP ERP and EPPM and have similar modes in which

to transfer the data. However, these transactions have different selection criteria for SAP ERP data and the

transfer types.

o Note: This transaction by default uses workflow that integrates data between SAP and Oracle Primavera

EPPM system. To use SAP EPC SIS for MPS, go to the section of “Transfer Projects transaction

configuration”

2. /SEPC/XFER_RESULTS – Display Transfer Results.

The Display Transfer Results transaction displays the past results of transactions for orders or projects

within a specified data range for the current user.

3. /SEPC/XFER_ALL_RES – Display Transfer Results ADMIN.

The Display Transfer Results ADMIN transaction displays the past results of transactions for orders or

projects within a specified data range for all users.


CUSTOMER


If you do not have access to one of these transactions, contact your SAP ERP administrator. You may need to have a

role or authorization added to your user profile.

1.6 Transfer Projects transaction configuration

/SEPC/XFER_PROJECT – Transfer Projects. This transaction by default uses workflow that integrates data between

SAP and Oracle Primavera EPPM system.

To use SAP EPC SIS for MPS, implement the following SAP Note:

Refer SAP Note 2007441 - Using Customizing tables /SEPC/XFER_PR_T and /SEPXFER_OR_T without

implementing BADIs.

Add two new Transfer Type entries using transaction: “SM30” -> Table/View text: “/SEPC/XFER_PR_T” ->

“Maintain” ->” New Entries“ screen as mentioned in the above SAP Note documentation,.

1. Example of New Entry for SAP to MPS data transfer:

i. Language: “EN” or any other SAP EPC supported language

ii. Explanation: “SAP to MPS Project Transfer” or any other descriptive text.

iii. Worklfow Name: SAPS_to_MPS (Case-sensitive)

2. Example of New Entry for MPS to SAP data transfer:

i. Language: “EN” or any other SAP EPC supported language

ii. Explanation: “MPS to SAP Project Transfer” or any other descriptive text.

iii. Worklfow Name: MPS_to_SAPPS (Case-sensitive)


CUSTOMER


2 SAP PS to Microsoft Project Server

Microsoft Project Server and the Project System do not contain the same objects. In the Project System, for example,

there are two structures for planning projects, work breakdown structures and networks. In Microsoft Project Server

there is only one structure. It does not recognize work breakdown structures as independent objects. Summary Tasks

are used in Microsoft Project Server to give projects a hierarchical structure. Similarly there is no such object as a

network in Microsoft Project Server. As a result of these differences, it is necessary to map project objects from one

program to the other. This is referred to as a Mapping.

2.1 Preparation

SIS requires following Enterprise Project Custom Fields in Microsoft Project Server. These custom fields should be

setup prior to execution of SAP to MPS data synchronization workflow.

o List of required Enterprise Project Custom Fields with type “text”:

1. SAP Project Last Transfer Date

2. SAP Project Profile

3. SAP Project Plant

4. SAP Network Profile

o List of required Enterprise Task Custom Fields with type “text”:

1. SAP Activity Element

2. SAP Description

3. SAP Object

4. SAP Activity

5. SAP Network

6. SAP Control Key

7. SAP Transfer

8. SAP WBS Element

9. SAP Plant

10. SAP Network Profile

11. SAP MRP Controller

12. SAP Network Type

13. SAP System Status

14. SAP User Status

15. SAP Component

16. SAP Component Item Number

17. SAP Component Item Text

18. SAP Milestone Usage


CUSTOMER


2.2 Workflow

SAP EPC SIS includes workflow that includes multiple synchronization steps to transfer the data from SAP to MPS.

This work flow consists of a series of steps which represents a particular part of business process.

Highlights of SAP EPC SIS SAP PS to MPS workflow:

1. Reads SAP PS Project related data from SAP using SAP PS standard BAPIs

2. Synchronizes SAP Work Centers and Components used in the requested project to Microsoft Project

Server Enterprise Resources if missing.

3. Reads Microsoft Project Server Project, Resource and Custom Field data.

4. Maps, applies business rules to SAP PS and MPS Project data and outputs Microsoft Project Data

Set xml.

5. Sends Project data Set to Microsoft Project Server for writing.

Workflow Name: SAPPS_to_MPS

Workflow File: sapps_saptomps-operations.xml

List of BAPIs used in SAP to MPS synchronization workflow:

1. BAPI_PROJECT_GETINFO – Retrieves SAP Project data

2. BAPI_NETWORK_GETINFO – Retrieves Network & Activity data

3. BAPI_BUS2002_GET_STATUS – Retrieves System and User status of each Activity for the given Network

4. BAPI_BUS2054_GET_STATUS – Retrieves WBS Element User and System Status.

2.3 Object Mappings

Object Mapping from SAP Project System to Microsoft Project Server

No SAP Project System Microsoft Project Server

1 Project Definition Project Information

2 WBS Element Summary Task

3 Network Task

4 WBS Milestone Milestone Task

5 Activity Task

6 Activity with Work Center Resource

7 Activity with Work Center Assignment

8 Relationship Dependency

9 Activity Element Task

10 Activity Element with Work Center Resource

11 Activity Element with Work Center Assignment

12 Activity Milestone Milestone Task


CUSTOMER


No SAP Project System Microsoft Project Server

13 Material Component Resource

14 Material Component Assignment

2.4 SAP Project Definition Field Mappings

The project information in Microsoft Project Server is the nearest equivalent to a project definition in SAP PS.

Pre-requisite: SIS requires following Enterprise Project Custom Fields in Microsoft Project Server:

List of required Enterprise Project Custom Fields:

o SAP Project Last Transfer Date

o SAP Project Profile

o SAP Project Plant

o SAP Network Profile

No SAP PS MPS Condition if any

1 - PROJ_UID o Mandatory Field.

o UID is globally unique identifier. If

project is new then use temporary

UID.

2 PROJECT_DEFINITION PROJ_NAME Mandatory Field for Project creation.

3 - PROJ_TYPE o Set to "0"

o '0' represents Regular project

o Mandatory Field for Project

creation.

4 RESPONSIBLE_NO PROJ_PROP_MANAGER Set during Project Creation

5 DESCRIPTION PROJ_PROP_TITLE Set during Project Creation

6 START PROJ_OPT_DEF_START_TIME Set during Project Creation

7 - PROJ_OPT_DEF_TASK_TYPE o Set to "1" during Project Creation

o "1" represents "Fixed Duration"

Task Type in MPS

8 - PROJ_INFO_SCHED_FROM o Set to "true" ,

o "true" = Project is set to schedule

from start (SFS)

9 START PROJ_INFO_START_DATE Set during Project Creation

10 - PROJ_NEW_TASKS_ARE_MAN o Set to "false" which represents

SAP MPS

PROJECT PROJECT


CUSTOMER



UAL

"Auto Schedule"

o This flag controls the default task

scheduling behavior. If task

scheduling flag TASK_IS_MANUAL

is not set then it will use this project

level flag to control the

scheduling behavior of the new

tasks.

o NOTE: If task scheduling is set to

"Manual" then MPS may throw

ProjectScheduling Exception like

“Microsoft.Office.Project.Schedulin

g. SchedulingException: Cannot

extend beyond minimum date" due

to inability to resolve scheduling

conflict.

11 - Project Custom Field:

SAP Project Last Transfer Date

o Set to current system Date-Time.

o Updated during each transfer

12 PROJECT_PROFILE Project Custom Field:

SAP Project Profile

Set during Project Creation

13 PLANT Project Custom Field:

SAP Project Plant


14 NETWORK_PROFILE Project Custom Field:

SAP Network Profile


2.5 SAP WBS Element Field Mappings

Microsoft Project Server does not have WBS elements. WBS Elements are mapped as summary tasks in Microsoft

Project Server. If a WBS element does not have any subordinate (child) objects, for example, activities, milestones or

subordinate WBS elements, it becomes a task in Microsoft Project Server. In Microsoft Project Server, a summary

task must have subordinate tasks.

As a summary task in Microsoft Project Server, a WBS element only summarizes its subordinate tasks. It cannot have

dates of its own. The dates that appear on the summary task bar are the overall dates of the subordinate tasks. This

means that the start date of the summary task is the earliest start date of the subordinate tasks and the finish date is

the latest finish date.

Pre-requisite: SIS requires following Enterprise Task Custom Fields in Microsoft Project Server:

List of required Enterprise Task Custom Fields:

o SAP Description

o SAP Object

o SAP Transfer

o SAP System Status

o SAP User Status


CUSTOMER



1 - PROJ_UID Mandatory Field. PROJ_UID of Project

2 - TASK_UID o Mandatory Field.

o If task is new then generated UID is

used.

o For existing task, TASK_UID from

the MPS data is used.

3 WBS_ELEMENT TASK_NAME Mandatory Field during task creation

4 - TASK_TYPE o Set to “1” during task creation.

o Value “1” represents “Fixed

Duration” - The duration of the

task remains constant, regardless

of the number of resources

(Assignment Units) assigned or

the amount of work.

o Mandatory Field during task

creation

5 - TASK_IS_MILESTONE Set to “false”

6 - TASK_LOCKDOWN_BY_MANAGE

R

Set to “false”

7 - TASK_IS_EFFORT_DRIVEN Set to “false”

8 WBS_HIERARCHIE :

UP/DOWN/LEFT/RIGHT

TASK_OUTLINE_LEVEL TASK_OUTLINE_LEVEL controls

hierarchy of the task in MPS. Value of

this field is calculated from

E_WBS_HIERARCHIE_TABLE/[UP/DO

WN/LEFT/RIGHT]

9 WBS_BASIC_DURATION TASK_DUR

10 - TASK_DUR_FMT o Set to “7”.

o Value “7” represents “Day” unit.

11 WBS_BASIC_START_DATE TASK_START_DATE

12 WBS_BASIC_FINISH_DATE TASK_FINISH_DATE

13 WBS_ACTUAL_START_DATE TASK_ACT_START

14 WBS_ACTUAL_FINISH_DATE TASK_ACT_FINISH

15 DESCRIPTION Task Custom Field:

SAP Description

16 - Task Custom Field:

SAP Object

o Set to “WBS_ELEMENT”.

o Mandatory Field.

SAP MPS

Summary Task WBS Element


CUSTOMER



17 SYSTEM_STATUS Task Custom Field:

SAP System Status

18 USER_STATUS Task Custom Field:

SAP User Status


SAP Transfer

o Set to “Yes”.

o Mandatory Field.

2.6 SAP Network Field Mappings

When synchronizing SAP WBS elements, Microsoft Project Server does not distinguish between work breakdown

structures and networks. There is no such object as a network in Microsoft Project Server. Consequently the network

header does not appear in Microsoft Project Server. The network number is used to identify individual network

activities. The network header is mapped to the MPS task.

NOTE: When you synchronize a SAP Project containing a network with no activities, the network is not transferred. If

you want to transfer that network you must assign at least one activity to the network in SAP.



o SAP Description

o SAP Object

o SAP Control Key

o SAP Network

o SAP WBS Element

o SAP Plant

o SAP Network Profile

o SAP MRP Controller

o SAP Network Type

o SAP Transfer

o SAP User Status

No. SAP PS MPS Condition if any




used.

o For existing task, TASK_UID from the

SAP MPS

Task Network


CUSTOMER



MPS data is used.

3 NETWORK TASK_NAME Mandatory Field during task creation

5 Parent WBS_ELEMENT

Outline Level +1

TASK_OUTLINE_LEVEL Incremented Parent WBS Element Object

Outline Level by one to create as a child

Task.


o Value “1” represents “Fixed Duration”

- The duration of the task remains

constant, regardless of the number of

resources (Assignment Units)

assigned or the amount of work.

o Mandatory Field during task creation

7 - TASK_IS_MILESTONE Set to “false” during task creation

8 - TASK_LOCKDOWN_BY_MANAGER Set to “false” during task creation

- TASK_FIXED_COST_ACCRUAL o Set to “3” during task creation

o Value 3 represents Pro-rated

(default); costs accrue as work is

scheduled to occur and as actual

work is reported

9 START_DATE TASK_START_DATE Populated if Actuals date not exist.

10 FINISH_DATE TASK_FINISH_DATE Populated if Actuals date not exist.

11 ACTUAL_START_DATE TASK_ACT_START

12 ACTUAL_RELEASE_DATE TASK_ACT_FINISH

13 SHORT_TEXT Task Custom Field:

SAP Description


SAP Object

o Set to “NETWORK”.

o Mandatory Field

15 NETWORK_TYPE Task Custom Field:

SAP Control Key

16 NETWORK Task Custom Field:

SAP Network

17 WBS_ELEMENT Task Custom Field:

SAP WBS Element

18 PLANT Task Custom Field:

SAP Plant

19 PROFILE Task Custom Field:

SAP Network Profile

20 MRP_CONTROLLER Task Custom Field:

SAP MRP Controller

21 NETWORK_TYPE Task Custom Field:


CUSTOMER



SAP Network Type


SAP Transfer

o Set to “Yes”

o Mandatory Field

2.7 SAP Network Activity Field Mappings

SAP Network Activities are mapped directly as tasks in Microsoft Project Server. Microsoft Project Server itself does

not differentiate between different types of activity. However the control key for a task/activity appears in the task

custom fields.



o SAP Description

o SAP Object

o SAP System Status

o SAP User Status

o SAP Activity

o SAP Network

o SAP Control Key

o SAP WBS Element

o SAP Plant

o SAP Transfer

o SAP Transfer





used.


MPS data is used.

3 NETWORK-ACTIVITY TASK_NAME o Mandatory Field.

o Maps to two fields i.e. <NETWORK>-

<ACTIVITY>.

o Separated by “-“separator.


Outline Level +1



SAP MPS

Task Activity


CUSTOMER



Task.


o Value “1” represents “Fixed Duration”

- The duration of the task remains






8 - TASK_LOCKDOWN_BY_MAN

AGER

Set to “false” during task creation

9 - TASK_FIXED_COST_ACCRUA

L

o Set to “3” during task creation



scheduled to occur and as

actual work is reported

10 DURATION_NORMAL TASK_DUR Maps to DURATION_NORMAL for

“internal” and “cost” type of SAP

Activities.

11 PLND_DELRY TASK_DUR Maps to PLND_DELRY for “service” and

“external” type of SAP Activities.

12 TASK_DUR_FMT = 7 o Set to “7”.

o Value “7” represents “Day” unit.


14 ACTUAL_FINISH_DATE TASK_ACT_FINISH

15 CONSTRAINT_TYPE_START TASK_CONSTRAINT_TYPE o Maps if Start Constraint exists in SAP

Activity.

SAP Constraint = MPS Constraint:

o Must start on(1)=Must start on(2)

o Cannot start before(2)=Start no

earlier than(4)

o Cannot start later(3)=Start no later

than(5)

o Start from resource planning(4)=As

soon as possible(0)

16 CONSTRAINT_START_DATE TASK_CONTRAINT_DATE

17 CONSTRAINT_TYPE_FINISH TASK_CONSTRAINT_TYPE o Maps if Finish Constraint exists in

SAP Activity.

SAP Constraint = MPS Constraint:

o Must finish on(1)=Must finish on(3)

o Cannot finish before(2)= Finish no

earlier than(6)

o Cannot finish later(3)= Finish no later

than(7)


CUSTOMER



o Finish from resource planning(4)=As

late as possible(1)

18 CONSTRAINT_FINISH_DATE TASK_CONTRAINT_DATE

19 CONSTRAINT_FINISH_DATE TASK_DEADLINE Maps to Finish Constraint date if no

actuals date exist.

20 EARLY_START_DATE TASK_START_DATE Maps of no actuals date exist.

21 PLANNED_COST TASK_COST Maps if SAP Activity type equals to

“Cost”, or “External” or “Service”


SAP Description


SAP Object

o Set to “ACTIVITY”.

o Mandatory Field.

23 ACTIVITY Task Custom Field:

SAP Activity


SAP Network

25 CONTROL_KEY Task Custom Field:

SAP Control Key


SAP Transfer

o Set to “Yes”.

o Mandatory Field.

27 SYSTEM_STATUS Task Custom Field:

SAP System Status

28 USER_STATUS Task Custom Field:

SAP User Status


SAP WBS Element

30 PLANT Task Custom Field:

SAP Plant

2.8 SAP Activity Element Field Mappings

Microsoft Project Server does not have any objects that are hierarchically subordinate to tasks. You can only

represent activity elements in Microsoft Project Server as a task. If the activity element has a plant, work center and

activity type then the plant-work center-activity type are created as a resource for the task.



o SAP Object


CUSTOMER


o SAP Description

o SAP Activity Element

o SAP Activity

o SAP Network

o SAP Transfer

o SAP Control Key





used.


MPS data is used.

3 NETWORK-ACTIVITY-

ELEMENT

TASK_NAME o Mandatory Field.

o Maps to three fields i.e. <NETWORK>-

<ACTIVITY>-<ELEMENT>

o Separated by “-“separator.


Outline Level +1



Task.


o Value “1” represents “Fixed Duration” -

The duration of the task remains






7 - TASK_LOCKDOWN_BY_MANA

GER


8 - TASK_FIXED_COST_ACCRUA

L


o Value 3 represents Pro-rated (default);

costs accrue as work is scheduled to

occur and as actual work is reported


10 ACTUAL_FINISH_DATE TASK_ACT_FINISH

11 EARLY_START_DATE TASK_START_DATE Maps if actuals date not exist.

SAP MPS

Task Activity Element


CUSTOMER




SAP Object

Set to “ACTIVITY_ELEMENT”

Mandatory Field

13 ELEMENT Task Custom Field:

SAP Activity Element


SAP Activity


SAP Network


SAP Transfer

o Set to “Yes”.

o Mandatory Field.

17 CONTROL_KEY Task Custom Field:

SAP Control Key


SAP Description

2.9 SAP Work Center–Resource Field Mappings

In SAP PS Work Center can be assigned at Activity or Activity Element level for “internal” type of Activities. Microsoft

Project Server does not use Work Center object in the same way as in the SAP system. However it does have

resources for a project, which can be planned. The plant, the work center and Activity Type values are combined to

depict the resource in MPS and assigned to the task as an assignment with capacity planning and actuals work data.

NOTE: SAP Work Center assigned at SAP Activity and SAP Activity Element having type ”internal” with Plant and

Activity Type data will be transferred as MPS Resource during this work flow.

SAP Work Center to MPS Resource

No. SAP MPS Condition if any

1 - RES_UID o Mandatory Field.

o For new resources generated UID is

used.

2 - RES_TYPE o Set to “20”

o Value “20” represents Generic

Labor type of resource in MPS.

3 PLANT-WORK_CNTR-

ACTTYPE

RES_NAME Maps to three fields separated by “-“ i.e.

<PLANT>-<WORK_CNTR>-

SAP MPS

Resource Work Center


CUSTOMER



<ACTTYPE>

4 PLANT-WORK_CNTR-

ACTTYPE

RES_EXTERNAL_ID Same as RES_NAME mapping

5 - RES_IS_TEAM Set to “false”

2.10 SAP Work Center-Assignment Field Mappings

In SAP PS Work Center can be assigned at Activity or Activity Element level for “internal” type of Activities. Microsoft

Project Server does not use Work Center object in the same way as in the SAP system. However it does have

resources for a project, which can be planned. The plant, the work center and Activity Type values are combined to

depict the resource in MPS and assigned to the task as an assignment with capacity planning and actuals work data.



o SAP Object

o SAP Activity

o SAP Network

o SAP Transfer



2 - TASK_UID Mandatory Field. TASK_UID of Task

3 - ASSN_UID o Mandatory Field.

o If Assignment is new then generated UID

is used.

o For existing Assignment, TASK_UID from

the MPS data is used.

4 - RES_UID Mandatory Field. RES_UID of Resource

5 - WASSN_LOCKDOWN_BY_MAN

AGER

o Mandatory Field.

o Set to “False”

6 - ASSN_UNIT o Set to “10000”

o Value 10000 equals to 100% capacity of

resource. Assuming a resource's Max

SAP MPS

Assignment Activity with Work Center


CUSTOMER



Units value is 100 percent.

7 WORK_ACTUAL ASSN_ACT_WORK

8 WORK_ACTIVITY ASSN_WORK If Actuals work exist then it is mapped as

actuals work WORK_ACTUAL otherwise it is

mapped as WORK_ACTIVITY

9 ACTUAL_START_DATE ASSN_ACT_START

10 ACTUAL_FINISH_DATE ASSN_ACT_FINISH


SAP Object

o Set To “ACTIVITY_RESOURCE” for Work

Center assigned at SAP Activity level

o Or set To “ELEMENT_RESOURCE” for

Work Center assigned at SAP Activity

Element level.

o Mandatory Field.


SAP Activity


SAP Network


SAP Transfer

o Set to “Yes”.

o Mandatory Field.

2.11 SAP Relationship Field Mappings

Since relationships are common to both the Project System and Microsoft Project Server, there are no difficulties

mapping them. The four types of relationship: Finish-Start (FS), Start-Start (SS), Finish-Finish (FF), and Start-Finish

(SF) are used in both programs. You can also transfer time intervals. In Microsoft Project Server these intervals are

only expressed in absolute units, that is days or weeks and so on.

In SAP PS it is possible to have more than one relationship between two activities, as long as the relationships are of a

different type. This is not possible in Microsoft Project Server. Therefore only one relationship is transferred.

You can use the Predecessors and Successors fields in Microsoft Project Server to display the task to which a task is

linked. If the relationship is not an FS relationship (default value), the relationship type is displayed. Any time interval

between the two tasks is also displayed. Here the tasks are referred to by their ID, which is the line number in the

project.

In Microsoft Project Server a task that must start or finish before another task can begin is called a predecessor task.

A task that depends on the start or finish of a preceding task is called a successor task.

SAP MPS

Dependency Relationship


CUSTOMER



1 - LINK_UID o Mandatory Field.

o If Relationship is new then generated UID is used.

o For existing Relationship, TASK_UID from the

MPS data is used.


3 - LINK_PRED_UID Mandatory Field. TASK_UID of Predecessor Task

4 - LINK_SUCC_UID Mandatory Field. TASK_UID of Successor Task

5 RELATION_TYPE LINK_TYPE o 0 represents FinishFinish (FF)

o 1 represents FinishStart (FS)

o 2 represents StartFinish (SF)

o 3 represents StartStart (SS)

6 DURATION_RELATION LINK_LAG Duration is stored as a number representing one tenth

of a minute. For example, duration of 100 indicates 10

minutes.

7 - LINK_LAG_FMT o Set to “5”

o 5 represents “HOURS”

2.12 Milestone

SAP EPC SIS supports both WBS element milestones and activity milestones. They are both represented as milestone

tasks under a WBS summary task in Microsoft Project Server.

2.12.1 SAP WBS Element Milestone Field Mappings

This is shown as a task with duration of zero days for which the Mark task as milestone indicator is set. It is

distinguished from an activity milestone by the entry in the “SAP Object” Enterprise Task Custom Field. Value of “SAP

Object” task custom field for WBS Milestone is “WBS_MILESTONE”.



o SAP Description

o SAP Object

o SAP WBS Element

o SAP Milestone Usage

o SAP Transfer


CUSTOMER





3 MILESTONE_NUMBER TASK_NAME Mandatory Field.


Outline Level +1



Task.


o Value “1” represents “Fixed Duration” -

The duration of the task remains


resources (Assignment Units) assigned

or the amount of work.


6 - TASK_IS_MILESTONE Set to “true” during task creation

7 - TASK_LOCKDOWN_BY_MA

NAGER


8 - TASK_FIXED_COST_ACCRU

AL


o Value 3 represents Pro-rated (default);

costs accrue as work is scheduled to

occur and as actual work is reported

9 - TASK_DUR Set to “0”, Since it is milestone task, The

duration of this task is 0.

10 - TASK_DUR_FMT o Set to “7”

o 7 represents “Day”

11 SCHED_MILESTONE_DATE

_BASIC

TASK_START_DATE

12 ACTUAL_ DATE TASK_ACT_START

13 ACTUAL_ DATE TASK_ACT_FINISH

14 FIXED_MILESTONE_DATE_

BASIC

TASK_CONSTRAINT_DATE


SAP Description


SAP Object

o Set to WBS_MILESTONE

o Mandatory Field


SAP WBS Element

SAP MPS

Milestone Task WBS Milestone


CUSTOMER



18 MILESTONE_USAGE Task Custom Field:

SAP Milestone Usage

19 -

Task Custom Field:

SAP Transfer

o Set to “Yes”

o Mandatory Field

2.12.2 SAP Activity Milestone Field Mappings

This is shown as a task with duration of 0 days for which the Mark task as milestone indicator is set. It is distinguished

from an activity milestone by the entry in the “SAP Object” Enterprise Task Custom Field. Value of “SAP Object” task

custom field for WBS Milestone is “ACTIVITY_MILESTONE”.

.



o SAP Description

o SAP Object

o SAP Activity

o SAP Network


o SAP Transfer


1 - PROJ_UID Mandatory Field. PROJ_UID of

Project


3 MILESTONE_NUMBER TASK_NAME Mandatory Field.

4 Parent WBS_ELEMENT Outline

Level +1

TASK_OUTLINE_LEVEL Incremented Parent WBS Element

Object Outline Level by one to create

as a child Task.


o Value “1” represents “Fixed

Duration” - The duration of the

task remains constant,

regardless of the number of



SAP MPS

Milestone Task Activity Milestone


CUSTOMER



o Mandatory Field during task

creation

6 - TASK_IS_MILESTONE Set to “true” during task creation

- TASK_LOCKDOWN_BY_

MANAGER


- TASK_FIXED_COST_AC

CRUAL




scheduled to occur and as

actual work is reported

- TASK_DUR Set to “0”, Since it is milestone task,

The duration of this task is 0.

7 SCHED_MILESTONE_DATE_BASIC TASK_START_DATE

8 ACTUAL_ DATE TASK_ACT_START

9 ACTUAL_ DATE TASK_ACT_FINISH


SAP Description


SAP Object

o Set to “ACTIVITY_MILESTONE”

o Mandatory Field


SAP Activity


SAP Network

14 MILESTONE_USAGE Task Custom Field:

SAP Milestone Usage


SAP Transfer

o Set to “Yes”

o Mandatory Field

2.13 SAP Material component Field Mappings

Microsoft Project does not have any objects that are hierarchically subordinate to tasks. You can only represent

Material Components in Microsoft Project as different resources for a task. If task has multiple material components

then only material components that have a unique material are transferred to Microsoft Project.



o SAP Component

o SAP Component Item Number

o SAP Component Item Text

o SAP Description


CUSTOMER


o SAP Object

o SAP Activity

o SAP Network




3 - ASSN_UID o Mandatory Field.

o If Assignment is new then generated

UID is used.

o For existing Assignment, TASK_UID

from the MPS data is used.

4 - RES_UID Mandatory Field. RES_UID of Material

Resource

5 - WASSN_LOCKDOWN_BY_MANAGER o Set to “false”

6 WORK_ACTIVITY ASSN_WORK Work is stored as thousandths of a

minute. For example, 10 minutes is

represented as 10000

7 COMPONENT Task Custom Field:

SAP Component

8 ITEM_NUMBER Task Custom Field:

SAP Component Item Number

9 ITEM_TEXT Task Custom Field:

SAP Component Item Text

10 MATL_DESC Task Custom Field:

SAP Description


SAP Object

o Set to “MATERIAL”

o Mandatory Field


SAP Activity


SAP Network

SAP MPS

Assignment SAP Material


CUSTOMER


3 Microsoft Project Server to SAP PS

This is the more complex of the two mapping scenarios. This is because the Microsoft Project Server objects must

have a particular format to be mapped successfully to the Project System. Objects created in Microsoft Project Server

have to fulfill certain criteria before they can be transferred to the Project System. Also, Scheduling in Microsoft

Project Server and the Project System differs in detail. This can cause unexpected scheduling results when

transferring dates related between the two programs.

3.1 Workflow

SAP EPC SIS includes workflow that includes multiple synchronization steps to transfer the data from MPS to SAP.

This work flow consists of a series of steps which represents a particular part of business process.

Highlights of SAP EPC SIS SAP PS to MPS workflow:

1. Reads Microsoft Project Server Project, Resource and Custom Field data.

2. Reads SAP PS Project related data from SAP using SAP PS standard BAPIs

3. Maps, applies business rules to SAP PS and MPS Project data and outputs xml request in

BAPI_PROJECT_MAINTAIN schema.

4. Sends Project data in BAPI_PROJECT_MAINTAIN request xml format to SAP for writing.

Workflow Name: MPS_to_ SAPPS

Workflow File: sapps_mpstosap-operations.xml

List of BAPIs used in SAP to MPS synchronization workflow:

1. SAP PS BAPIs used for reading data from SAP PS:

a. BAPI_PROJECT_GETINFO – Retrieves SAP Project data

b. BAPI_NETWORK_GETINFO – Retrieves Network & Activity data

c. BAPI_BUS2002_GET_STATUS – Retrieves System and User status of each Activity for the given

Network

d. BAPI_BUS2054_GET_STATUS – Retrieves WBS Element User and System Status.

2. SAP PS BAPI used for writing Project data to SAP PS

a. BAPI_PROJECT_MAINTAIN – Writes data to SAP PS


CUSTOMER


3.2 Object Mappings

Object Mapping from Microsoft Project Server to SAP Project System

No Microsoft Project Server SAP Project System

1 Project Information Project Definition

2 Summary Task WBS Element

3 Task Network

4 Milestone Task WBS Milestone

5 Task Activity

7 Assignment Work Center at Activity

8 Dependency Relationship

9 Task Activity Element

11 Assignment Work Center at Activity Element

12 Milestone Task Activity Milestone

3.3 MPS Project Field Mapping

Project in SAP PS maps to the Project properties in Microsoft Project Server. SAP EPC SIS supports both Project

creation and update in SAP PS from MPS.

Transferring a new project from Microsoft Project Server to the SAP Project System, SAP EPC checks whether the

project exists in the SAP Project System or not. If the project does not exist in the SAP Project System, SAP EPC

creates a new project as a copy of the project in Microsoft Project Server. If the project already exists in the SAP

Project System, SAP EPC compares the structure of the Project System Project to the corresponding Project

structure in Microsoft Project Server. If there is a difference, SAP EPC creates or updates data in the SAP Project

System if SAP Transfer custom field value in Microsoft Project Server is not “No”.

For a new Project transfer to SAP Project System, enter a project definition and the project profile. The other fields can

be left blank because this information is already contained in the project profile, which has been defined in

Customizing for the SAP Project System, along with the network profile.

Pre-requisite: SIS requires following Enterprise Project Custom Fields in Microsoft Project Server:

List of required Enterprise Project Custom Fields:

o SAP Project Profile – If you are transferring a new Project from MPS to SAP i.e. Project Creation in SAP.

For updating an existing Project this field is not required.

MPS SAP

Project Project


CUSTOMER


SAP Fields mentioned in the mappings below belongs to I_PROJECT_DEFINITION and I_PROJECT_DEFINITION_UPD

input in the BAPI_PROJECT MAINTAIN BAPI request.

No MPS SAP PS Condition if any

1 PROJ_NAME PROJECT_DEFINITION

2 PROJ_PROP_TITLE DESCRIPTION This field is updatable.

3 Project Custom Field:

SAP Project Profile

PROJECT_PROFILE Required only for creating new Project

in SAP PS

4 PROJ_INFO_START_DATE START This field is updatable.

5 PROJ_INFO_FINISH_DATE FINISH This field is updatable.

3.4 MPS Summary Task – WBS Element Field Mapping

WBS elements as such do not exist in Microsoft Project Server. SAP EPC SIS maps MPS summary tasks to WBS

elements in SAP PS. For a task to be a summary task, it must have subordinate tasks.



o SAP Description

o SAP Object with value=”WBS_ELEMENT”

o SAP Transfer

SAP Fields mentioned in the mappings below belongs to I_WBS_ELEMENT_TABLE and

I_WBS_ELEMENT_TABLE_UPDATE tables in BAPI_PROJECT MAINTAIN BAPI request.

No. MPS SAP PS Condition if any

1 TASK_NAME WBS_ELEMENT Max length supported is 24

characters. Accepts alphanumeric

entries. Value of this object must be

unique in the Project structure.


3 Task Custom Field:

SAP Description

DESCRIPTION This field is updatable.

4 TASK_NAME SHORT_ID

MPS SAP

Summary Task WBS Element


CUSTOMER


No. MPS SAP PS Condition if any

5 TASK_START_DATE WBS_BASIC_START_DATE This field is updatable.

6 TASK_FINISH_DATE WBS_BASIC_FINISH_DATE This field is updatable.

3.4.1 MPS Summary Task – SAP WBS Element Hierarchy Field Mapping

No. MPS SAP PS Condition If any

1 TASK_NAME WBS_ELEMENT


3 TASK_OUTLINE_LEVEL + 1 UP Parent WBS – One level Up.

4 TASK_OUTLINE_LEVEL - 1 DOWN Child WBS – One level Down.

5 TASK_OUTLINE_LEVEL LEFT Same level sibling WBS – Same level Up.

6 TASK_OUTLINE_LEVEL RIGHT Same level sibling WBS – Same level Down.

3.5 MPS Task – Network Field Mapping

The network number is used to identify individual network activities. There is no such object as a network in Microsoft

Project Server. To capture network header information, it is mapped to the MPS task.



o SAP Object with value=”NETWORK”

o SAP Description

o SAP Network Type – Optional for new network creation only.

o SAP Plant – Optional for new network creation only.

o SAP MRP Controller – Optional for new network creation only.

o SAP Transfer

SAP Fields mentioned in the mappings below belongs to I_NETWORK and I_NETWORK_UPDATE tables in

BAPI_PROJECT MAINTAIN BAPI request.

MPS SAP

Task Network


CUSTOMER



1 TASK_NAME NETWORK Max length supported is 12 characters.

Accepts numeric entries. Value of this

object must be unique in the Project

structure.

2 Task Custom Field :

SAP Description

SHORT_TEXT This field is updatable.



SAP Network Type

NETWORK_TYPE Used only during new Network creation.

Optional - This filed can be left blank or

might be required. This depends on your

configuration/customization of SAP PS.

5 TASK_NAME from

TASK_PARENT_UID

(Parent Summary

Task Name)

WBS_ELEMENT MPS Parent Summary Task which maps to

SAP WBS Element


SAP Plant

PLANT Used only during new Network creation.





SAP MRP Controller

MRP_CONTROLLER Used only during new Network creation.





SAP Network Profile

PROFILE Used only during new Network creation.




9 TASK_FINISH_DATE FINISH_DATE This field is updatable.

10 TASK_START_DATE START_DATE This field is updatable.

3.6 MPS Task – Network Activity Field Mapping

Tasks in Microsoft Project Server are the equivalent of activities in the SAP Project System. Since an activity number

in SAP PS can have up to four characters, you can only use this number of characters in Microsoft Project Server.



o SAP Object with value=”ACTIVITY”

o SAP Description

o SAP Control Key – Required for new Activity creation only.

o SAP Plant – Optional for new Activity creation only.


CUSTOMER


o SAP Transfer

List of required Enterprise Assignment Custom Fields:

o SAP Object with value=”ACTIVITY_RESOURCE”

SAP Fields mentioned in the mappings below belongs to I_ACTIVITY and I_ACTIVITY_UPDATE tables in



1. PROJ_NAME PROJECT_DEFINITION

2. TASK_NAME NETWORK o MPS Task maps to two SAP fields i.e.

<NETWORK>-<ACTIVITY>.

o Gets network number from text

before '-'.

o 12 characters long. Numeric entry.

3. TASK_NAME ACTIVITY o MPS Task maps to two SAP fields i.e.


o Gets Activity number from text after '-

'.

o 4 characters long. Numeric entry

only.

4. Task Custom Field :

SAP Control Key

CONTROL_KEY o Control Key is required field for

creating new task in SAP o if getting invalid/null control key from

MPS then map it to the default value from configuration file - mpsconfiguration.xml


SAP Description


6. TASK_NAME from

TASK_PARENT_UID

(Parent Summary Task Name)

WBS_ELEMENT MPS Parent Summary Task which maps

to SAP WBS Element

7. TASK_CONSTRAINT_TYPE CONSTRAINT_TYPE_START This field is updatable.

8. TASK_CONSTRAINT_DATE CONSTRAINT_START_DATE This field is updatable.

9. TASK_CONSTRAINT_TYPE CONSTRAINT_TYPE_FINISH This field is updatable.

10. TASK_FINISH_DATE CONSTRAINT_FINISH_DATE This field is updatable.

11. TASK_WORK WORK_ACTIVITY This field is updatable.

12. - UN_WORK Set to “H”

13. - UN_WORK_ISO Set to “HUR”

MPS SAP

Task Activity


CUSTOMER



14. RES_NAME from

Assignment RES_ID

(Selects from the first MPS

Assignment with Task Custom

Field “SAP Object” with

value="ACTIVITY_RESOURCE”

i.e. labor resource (work center)

assigned to the task.)

WORK_CNTR o MPS RES_NAME maps to three SAP

fields i.e. <PLANT>-< WORK_CNTR

>-< ACTTYPE>.

o Gets Work Center value after ‘-‘.

o 4 characters long.

15. RES_NAME ACTTYPE o MPS RES_NAME maps to three SAP


>-< ACTTYPE>.

o Gets ACTVTYPE value after ‘-‘.


16. RES_NAME PLANT o Gets from MPS Assignment i.e.

resource (work center) assigned for

the task.

o MPS RES_NAME maps to three SAP


>-< ACTTYPE>.



17. Task Custom Field”

SAP Plant

PLANT If no Resource Assignment exist for the

task them PLANT maps to the task

custom field.

3.7 MPS Task to Activity Element Field Mapping

Microsoft Project Server does not have any objects that are hierarchically subordinate to tasks. You can only

represent activity elements in Microsoft Project Server as a task. If the activity element has a plant, work center and

activity type then the plant-work center-activity type are created as a resource for the task.



o SAP Object with value=”ACTIVITY_ELEMENT”

o SAP Description

o SAP Transfer

o SAP Control Key – Required for new Activity Element creation only.

List of required Enterprise Assignment Custom Fields:

o SAP Object with value=”ELEMENT_RESOURCE”


CUSTOMER


SAP Fields mentioned in the mappings below belongs to I_ACTIVITY and I_ACTIVITY_UPDATE tables in


No MPS SAP Condition if any

1. TASK_NAME NETWORK o MPS Task maps to two SAP fields

i.e. <NETWORK>-<ACTIVITY>-

<ELEMENT>.

o Gets network number from text

before '-'.


2. TASK_NAME ACTIVITY o MPS Task maps to two SAP fields


<ELEMENT>.

o Gets Activity number from text

after '-'.


only.

3. TASK_NAME ELEMENT o MPS Task maps to two SAP fields


<ELEMENT>.

o Gets Element value from text

before '-'.


only.

4. Task Custom Field:

SAP Control Key

CONTROL_KEY o Maps to task Custom Field in MPS. o Required field for creating new

Element in SAP. o If getting invalid/null control key

from MPS then map it to the default value from configuration file - mpsconfiguration.xml.


SAP Description


6. RES_NAME from

Assignment RES_ID

(Selects from the first MPS

Assignment with Task Custom

Field “SAP Object” with

value="ELEMENT_RESOURCE”

i.e. labor resource (work center)

assigned to the task.)

WORK_CNTR o MPS RES_NAME maps to three

SAP fields i.e. <PLANT>-<

WORK_CNTR >-< ACTTYPE>.

o Gets Work Center value after ‘-‘.


7. RES_NAME ACTTYPE o MPS RES_NAME maps to three





MPS SAP

Task Activity Element


CUSTOMER


No MPS SAP Condition if any

8. RES_NAME PLANT o Gets from MPS Assignment i.e.

resource (work center) assigned

for the task.

o MPS RES_NAME maps to three






SAP Plant

PLANT If no Resource Assignment exist for

the task them PLANT maps to the task

custom field.

10. ASSN_WORK WORK_ACTIVITY

11 - UN_WORK Set to “STD”

12 - UN_WORK_ISO Set to “HR”

3.8 MPS Dependency to SAP Relationship Field Mappings

Since relationships are common to both the SAP Project System and Microsoft Project Server, there are no difficulties

mapping them. The four types of relationship (Finish-Start (FS), Start-Start (SS), Finish-Finish (FF), and Start-Finish

(SF)) are used in both programs. You can also transfer time intervals, expressed either in absolute values or as a

percentage of one of the two activities. You can use the Predecessors and Successors fields in Microsoft Project to

display the task to which a task is linked. If the relationship is not a FS relationship (default value), the relationship type

is displayed. Any time interval between the two tasks is also displayed. Here the tasks are referred to by their ID, which

is the line number in the project.

In Microsoft Project a task that must start or finish before another task can begin is called a predecessor task. A task

that depends on the start or finish of a preceding task is called a successor task.

SAP Fields mentioned in the mappings below belongs to I_RELATION and I_RELATION_UPDATE tables in



1 LINK_PRED_UID NETWORK_PREDECESSOR o MPS Task maps to two SAP fields i.e.


o Gets network number from text before '-'.


2 LINK_PRED_UID ACTIVITY_PREDECESSOR o MPS Task maps to two SAP fields i.e.


o Gets Activity number from text after '-'.

MPS SAP

Dependency Relationship


CUSTOMER



o 4 characters long. Numeric entry only.

3 LINK_SUCC_UID NETWORK_SUCCESSOR o MPS Task maps to two SAP fields i.e.


o Gets network number from text before '-'.


4 LINK_SUCC_UID ACTIVITY_SUCCESSOR o MPS Task maps to two SAP fields i.e.


o Gets Activity number from text after '-'.

o 4 characters long. Numeric entry only.

5 LINK_TYPE RELATION_TYPE o 0 represents FinishFinish (FF)

o 1 represents FinishStart (FS)

o 2 represents StartFinish (SF)

3 represents StartStart (SS)

6 LINK_LAG DURATION_RELATION LINK_LAG stored in TenthOfMinute in MPS

converted to Hours.

This field is updatable.

7 - DURATION_RELATION_UNIT Set to “STD”

8 - DURATION_RELATION_UNIT_ISO Set to “HUR”

3.9 Milestone Task

Milestones in Microsoft Project Server are defined as tasks with duration of 0 days. They have the Mark task as

milestone indicator set. Milestones in Microsoft Project do not have the same functionality as milestones in the SAP

Project System. Therefore you will in general have to edit the milestones in the Project System, before you can use

them.

3.9.1 Milestone Task to WBS Milestone Field Mapping

This is shown as a task with duration of zero days for which the Mark task as milestone indicator is set. It is

distinguished from an activity milestone by the entry in the “SAP Object” Enterprise Task Custom Field. Value of “SAP

Object” task custom field for WBS Milestone is “WBS_MILESTONE”.



o SAP Description

o SAP Object : value = ”WBS_MILESTONE”


o SAP Transfer


CUSTOMER


SAP Fields mentioned in the mappings below belongs to I_WBS_MILESTONE_TABLE and

I_WBS_MILESTONE_TABLE_UPDATE tables in BAPI_PROJECT MAINTAIN BAPI request.


1. TASK_NAME MILESTONE_NUMBER 12 character long numeric number.

2. TASK_NAME from

TASK_PARENT_UID

(Parent Summary Task

Name)

WBS_ELEMENT Mandatory Field

MPS Parent Summary Task which maps to

SAP WBS Element


SAP Milestone Usage

MILESTONE_USAGE Optional. Used during Milestone creation.


SAP Description


5. TASK_ACT_START ACTUAL_DATE This field is updatable.

6. TASK_START_DATE FIXED_MILESTONE_DATE_BAS

IC


3.9.2 Milestone Task to Activity Milestone Field Mapping

These are transferred to the Project System as activity milestones. This is shown as a task with duration of 0 days for

which the Mark task as milestone indicator is set. It is distinguished from an activity milestone by the entry in the “SAP

Object” Enterprise Task Custom Field. Value of “SAP Object” task custom field for WBS Milestone is

“ACTIVITY_MILESTONE”.

.



o SAP Description

o SAP Object: value = “ACTIVITY_MIELSTONE”


o SAP Transfer

SAP Fields mentioned in the mappings below belongs to I_ACTIVITY_MILESTONE and

I_ACTIVITY_MILESTONE_UPDATE tables in BAPI_PROJECT MAINTAIN BAPI request.

MPS SAP

Milestone Task WBS Milestone

MPS SAP

Milestone Task Activity Milestone


CUSTOMER



1 TASK_NAME MILESTONE_NUMBER 12 character long numeric number.


SAP Network

NETWORK Mandatory Field


SAP Activity

ACTIVITY Mandatory Field

4 Task Custom Field : SAP Milestone

Usage

MILESTONE_USAGE Optional. Used during Milestone creation.

5 Task Custom Field : SAP

Description


6 TASK_ACT_START ACTUAL_DATE This field is updatable.

7 TASK_START_DATE FIXED_MILESTONE_DAT

E_BASIC



CUSTOMER


4 Limitations and Restrictions

1. There are some basic business and scheduling rules of Microsoft Project Server which cannot be manipulated, like

scheduling of task dates based on constraint types, duration and so on. Attempt to force value into the fields may

result in the error returned from the MS Project Server PSI.

2. In Microsoft Project Server, Milestones can be linked to other milestones. In SAP PS, milestones can only be

assigned to a WBS Element or a Network Activity. This might cause a difference in scheduling since the milestone

relationship is taken into account while scheduling in MS Project Server but not in SAP PS.

3. After transferring a project from SAP PS to Microsoft Project Server, a single WBS element, single network or

single activity cannot be transferred back using MPS to SAP PS workflow. The whole project should be transferred

back to SAP PS. However, selective task transfer can be accomplished using "SAP Transfer" enterprise task

custom field. Set value of this field to “No” (case-sensitive) to restrict the transfer of the task object. If "SAP

Transfer" value is 'Yes' or blank (null) then the object will be transferred to the SAP PS system.

4. Activity or Activity elements that do not have either plant/work center/activity type assigned will not be transfer

to MS Project Server as Assignment. Plant, Work Center and Activity Type fields are all part of the compound key

used to uniquely identify the enterprise Resource object in the Microsoft Project Server.

5. It is strongly recommended not to transfer the same project concurrently from SAP to Microsoft Project Server

with either request initiated from the same client or from the multiple clients. During processing of the project

data, SAP EPC follows execution sequence of the methods required by the Microsoft Project Server Interface PSI

which includes the project check out, publish, check-in etc. SAP EPC cannot write the project data to MPS if the

project is already checked-out by individual user or if it is already in process by SAP EPC concurrent thread.

6. While transferring the project to/from MS Project Server, make sure that project is published and checked-in.

7. SAP EPC can only work with the checked-in published Microsoft Project. Attempt to transfer checked-out project

will lead to an error during transfer.

8. Project transfer may fail due to network/machine failure, data related issues or due to business and scheduling

rules of the MS Project Server/SAPPS system. In some cases SAP EPC might fail to publish/check-in the project

in Microsoft Project Server. Due to the fact that failed job may block subsequent jobs, go to the Project Server

Web Access site to force check-in of the project manually.

9. SAP EPC SIS does not support transfer of calendar object right now. Make sure you synchronized calendar in SAP

PS and in MS Project Server manually.

10. Data creation in SAP depends on the project profile and other SAP PS configuration. This configuration controls

the default and required fields for creation of objects in SAP. Data transfer to SAP from MS Project Server might

fail if required data is not provided based on your SAP PS configuration.

www.sap.com/contactsap

Material Number


No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software

vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated

companies (“SAP Group”) for informational purposes only, without

representation or warranty of any kind, and SAP Group shall not be

liable for errors or omissions with respect to the materials. The only

warranties for SAP Group products and services are those that are

set forth in the express warranty statements accompanying such

products and services, if any. Nothing herein should be construed as

constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of

SAP AG in Germany and other countries. Please see

www.sap.com/corporate-en/legal/copyright/index.epx#trademark

for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

Date post:	15-Mar-2018
Category:	Documents
Upload:	truonglien
View:	292 times
Download:	13 times

Microsoft Project Server(MPS) Sample Integration … Project Server(MPS) Sample Integration...

Documents