How-To Guide
SAP Enterprise Project Connection 3.0 (Patch04 and UP)
Document Version: 3.0 – 2016-09-01
SAP Project System (PS) - Oracle Primavera P6 EPPM
Sample Integration Solution (SIS)
Default Business Rules, Mappings and Configuration
CUSTOMER
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.
EXAM PLE
Keys on the keyboard, for example, F 2 or E N T E R .
Document History
Version
Date
Change
1.0
2013-06-14
Original Document
2.0
2013-07-15
Removed P6 EPPM configuration details – moved to an SAP Note
3.0
2016-10-07
SAP EPC 3.0 Patch04 SIS Changes
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
3
Table of Contents
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
Introduction ............................................................................................................................................... 6
SAP EPC SIS Disclaimer ......................................................................................................................................... 6
Intended Audience .................................................................................................................................................. 6
Additional Documentation ...................................................................................................................................... 6
Key Concepts of Data Integration .......................................................................................................................... 7
Prerequisites ............................................................................................................................................................ 7
Overview of SAP EPC Transactions ....................................................................................................................... 7
SAP Project System (PS) and Oracle Primavera P6 EPPM Objects................................................................... 8
2
2.1
SAP Project System (PS) to Oracle Primavera P6 EPPM............................................................................ 9
Preparation .............................................................................................................................................................. 9
2.1.1
Primavera Global Data Creation ............................................................................................................ 9
Workflow................................................................................................................................................................. 10
Object Mappings..................................................................................................................................................... 11
SAP Project Field Mappings ................................................................................................................................. 12
SAP WBS Mappings .............................................................................................................................................. 13
SAP Network Mappings ........................................................................................................................................ 15
SAP Activity Mappings .......................................................................................................................................... 16
Milestone Mappings .............................................................................................................................................. 18
2.8.1
SAP WBS Milestone Mappings ............................................................................................................ 18
2.8.2
SAP Activity Milestone Mappings........................................................................................................20
Resource Mappings............................................................................................................................................... 21
2.9.1
SAP Work Center Mappings................................................................................................................. 21
2.9.2
SAP Material Component Mappings ................................................................................................... 22
Assignment Mappings........................................................................................................................................... 22
2.10.1
SAP Activity: Work Center - Assignment Mappings .......................................................................... 22
2.10.2
SAP Activity Element: Work Center - Assignment Mappings ........................................................... 24
2.10.3
SAP Material Component - Assignment Mappings ........................................................................... 25
Expense Mappings ................................................................................................................................................ 26
2.11.1
SAP Activity: Cost, Service, External - Expense Mappings ............................................................... 26
2.11.2
SAP Activity Element: Cost, Service, External - Expense Mappings ................................................ 27
2.11.3
SAP Material Component - Expense Mappings ................................................................................. 28
SAP Relationship Mapping ................................................................................................................................... 29
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
2.12
3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
Oracle Primavera P6 EPPM to SAP Project System (PS)........................................................................... 31
Workflow................................................................................................................................................................. 31
Object Mappings.................................................................................................................................................... 32
SAP Project Mappings .......................................................................................................................................... 33
SAP WBS Mappings .............................................................................................................................................. 33
SAP WBS Hierarchy Mappings............................................................................................................................. 35
SAP Network Activity Mappings .......................................................................................................................... 36
SAP Activity Element Mappings ........................................................................................................................... 38
SAP Relationship Mappings..................................................................................................................................40
SAP Milestone Mappings ...................................................................................................................................... 41
3.9.1
SAP WBS Milestone Mappings ............................................................................................................ 41
3.9.2
SAP Activity Milestone Mapping.......................................................................................................... 42
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 4
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
5
1 Introduction
SAP Enterprise Project Connection (EPC) 3.0 release includes Sample Integration Solution (SIS) for Oracle Primavera P6 EPPM
that demonstrates data synchronization between the SAP Project System(PS) and Oracle Primavera P6 EPPM. SAP EPC SIS
allows you to integrate Project related data from SAP Project System to Oracle Primavera P6 EPPM and from Oracle Primavera P6
EPPM 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 Oracle Primavera P6 EPPM.
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 is located 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 Projects in the SAP 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/epc30 and then SAP Business Suite →
SAP Product Lifecycle Management → SAP Enterprise Project Connection 3.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
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.
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 6
1.4 Key Concepts of Data Integration
The following list explains how disparate systems and their objects are associated in the SAP EPC solution:
o
Object Correspondence (Mappings)
The high-level mapping between business objects for supported end-point systems. For example, Activity Element Object in SAP PS
maps to Resource Assignment in Primavera, Work Center object of SAP PS maps to Resource (Labor) in Primavera.
o
System of Record
Identified on the Objects Correspondence. The system of record identifies the system that owns the object. Ownership can be very
important in establishing business rules and system behavior. When objects differ in SAP and Primavera, the system of record helps
to identify which object is the authoritative data source.
By default, for SAP EPC, the system of record for most objects is SAP ERP.
o
Object Identity
To know whether to create or update an object in SAP or Primavera, SAP EPC must first be able to determine if the object exists in
the target system. If it does not exist, the object is created, and if it does exist, the object is updated. To determine object identity,
objects use key fields that have the same values in both systems. The key attributes establish identity for the objects and cannot be
changed without affecting the integration behavior established by SAP EPC. For a key to be established between two systems, the
key must satisfy both the equality and uniqueness tests. In many cases, SAP EPC makes use of compound keys to make sure that
uniqueness is correctly established.
o
Field-Level Mappings
The Field-Level Mappings describe the set of data that comprises an object by identifying what fields SAP EPC will modify during data
transfers. Different fields are populated if the object is being created or updated. Mappings can be affected by business rules;
therefore, all mappings are not applicable for all object creations or updates. Field-level mappings may differ from transfer to transfer.
o
Business Rules
Business Rules identify how and when to modify the target system. Object correspondence and object identity are not sufficient;
they can only deliver an understanding of what the same object looks like in the source and target systems.
1.5
Prerequisites
Sample Integration Solution (SIS) for Oracle Primavera P6 EPPM 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 3.0
i. SAP ENTERPRISE PROJ CONN J 3.0 SP00 Patch04 and up
b.
EPCCTC 3.0
i. EPCCTC 33.0 SP00000and up
2.
SAP EPC ABAP Add-on component:
a.
1.6
SAP ENTERPRISE PROJ CON 3.0
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.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
7
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.
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.
If you do not have access to any of above transactions, contact your SAP ERP administrator. A new role or authorization is added to
your user profile
1.7 SAP Project System (PS) and Oracle Primavera P6 EPPM Objects
Oracle Primavera P6 EPPM and SAP Project System do not contain the same objects. SAP Project System has Projects, Network,
Work Centers, Activities, Elements, Milestones, and Components etc. In Oracle Primavera P6 EPPM, there are Projects, WBSs,
Activities, Milestones, Assignments, and Expenses etc. It does not recognize Elements, Network, and Components as independent
objects. 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.
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 8
2 SAP Project System (PS) to Oracle Primavera P6 EPPM
2.1 Preparation
You may review the configurations, and preparations before using SAP PS to Primavera Project transfer. The configuration file,
SAPPSConfiguration.xml, for Primavera transfer exists in config/im/primavera/ps. This file includes configuration for Object
transferability, time unit conversion, Control Key configuration, Relationship Type configuration, WBS/Network rules and Time Unit
of measures for both SAP ERP and Primavera system. Adjust and change these values as per your SAP and Primavera system
configuration.
2.1.1
Primavera Global Data Creation
By default, SAP EPC creates all required Primavera global data for example, Resource, Calendar, Codes, UDF, Notebook Topic etc.
required for creation of the Project and its related data during each Project Transfer. You may restrict creation of Primavera Global
data (or Project related data) in your workflow.
All Primavera rules related to writing data exist in the CRUDRuleWritePrimaveraProject.xml file. This file exists in
config/im/primavera/ps folder. Review this file and make changes as required for your use case. You can restrict creation or update
of ant supported Primavera business object by writing rule in this file. SAP EPC uses rules defined in this file to control the writing
behavior of each Primavera object.
o
EPS
In transfers from SAP PS to Primavera, SAP EPC creates the SAPEPS as an EPS node if it is missing and creates Projects under
SAPEPS. You may review and modify this mapping as per your use case. This mapping exists in the file
SAPProjectSystemLIMToProjectCIM.xsl located at config/im/primavera/ps folder.
o
Calendar
By default, SAP EPC creates calendar in Primavera but it is not populating calendar details; for example, working hours, holidays,
and working days in Primavera. Make sure to synchronize details of each calendar in Primavera and SAP system. Calendar data
is required for scheduling as well populating date and time details. If calendar data mismatches than you may see discrepancies
in your planned and scheduling data. Our recommendation is to create, update, synchronize and verify calendar details in SAP
ERP and Primavera system manually before running the data transfer.
If there is a calendar at the Activity or Project level and configuration in SAPPSConfiguration.xml file does not exist for this
particular calendar, then SAP EPC use conversion units from the default <Conversion> configuration defined in the
SAPPSConfiguration.xml. These conversion units are used to convert hours for calculating planned units and lag fields during
transfer.
o
Resource
During transfers from SAP EPC to Primavera, SAP EPC creates the Primavera labor resource if it does not exist. As the SAP EPC
administrator, you must understand the additional details a Primavera user needs to add to the created labor resource. If the
resource ID is modified in Primavera, it impacts future transfers. This is a key field for SAP Enterprise Project Connection.
o
Notebook Topic
SAP EPC creates Activity notes for data objects in Primavera. The names of the Activity notes begin with SAP. You must not
change the Activity notes names. If the name is changed, SAP EPC recreates it in a future transfer.
o
Project Code
SAP EPC creates Project codes in Primavera. Project codes begin with SAP. Project code names must not be changed. If the
name is changed, SAP EPC will recreate the code in a future transfer.
When SAP EPC creates the value in Primavera code value and description are populated and the same data are placed in each
field. Primavera users find it easier to work with the data if the descriptions are changed. You can change the description for a
code value manually and SAP EPC does not update the field.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
9
o
Activity Code
SAP EPC creates global Activity codes in Primavera. Global Activity codes begin with SAP. The global Activity code names
must not be changed. If the name is changed, SAP EPC recreates the code in a future transfer.
When SAP EPC creates the value in Primavera, code value and description are populated and the same data are placed in each
field. Primavera users find it easier to work with the data if the descriptions are changed. You can change the description for a
code value manually and SAP EPC does not update the field.
o
User Defined Field (UDF)
SAP EPC creates user-defined fields in Primavera. The user-defined fields begin with SAP. The user defined field names must
not be changed. If the name is changed, SAP EPC recreates it in a future transfer.
NOTE: For list of Project Codes, Activity Codes, and UDF Values used for mappings, see SAPProjectSystemLIMToProjectCIM.xsl
file exist in config/im/primavera/ps folder.
2.2 Workflow
SAP EPC SIS contains a workflow that includes multiple steps to transfer the data from SAP Project System to Oracle Primavera.
This workflow consists of a series of steps which represents a particular part of the business process.
Highlights of the EPC SIS SAP Project System (PS) to Oracle Primavera P6 EPPM workflow, are described below.
1.
Reads SAP PS Project related data from SAP using SAP PS standard BAPIs
2.
Maps and applies business rules to SAP PS Project data, and outputs Primavera Project xml.
3.
Read CRUD Rules for writing Primavera dataset
4.
Send Primavera Project dataset and CRUD rules instruction to SAP EPC Primavera Adaptor for writing.
5.
Send Email to user who initiated workflow with Primavera write response.
6.
Return workflow response back to caller.
Workflow and Mappings file details:
Workflow Name
SapToP3eProjectSync
Workflow File
config/datapath/operations/sapps_saptop6-operations.xml
Mappings File
config/im/primavera/ps/ map_sapProject_to_primaveraProject.xsl
Mapping Functions File
config/im/primavera/ps/PSProject-Functions.xsl
Configuration File
config/im/primavera/ps/SAPPSConfiguration.xml
Primavera CRUD Data Rule File
config/im/primavera/ps/CRUDRuleWritePrimaveraProject.xml
Workflow Input Parameters:
idStr
(Required) SAP Project ID used for transferring Project from SAP to
Primavera
user
User who initiated the workflow execution request.
server
SAP ERP Server (host) name.
client
SAP ERP client number.
systemNumber
SAP ERP System Number.
Workflow Steps:
1
Builds BAPI BAPI_PROJECT_GETINFO request with idStr (SAP Project ID as input)
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 10
2
Execute BAPI BAPI_PROJECT_GETINFO using the request built in Step 1.
3
Build BAPI_NETWORK_GETINFO request.
4
Execute BAPI_NETWORK_GETINFO using the request built in Step 3.
5
Merge all SAP data into one XML (Merge all BAPI responses from above steps)
6
Map SAP Project to Primavera Project (Mappings). This is a mapping file for all business objects and its fields.
7
Convert dataset to Primavera format (system file). This is SAP EPC system file that converts Project dataset
to its local Primavera format.
8
Read CRUD Primavera Write Rules. This steps reads Primavera data related rules that is which
objects are allowed for creation or update and it also contains some field level rules.
9
Execute Primavera Write. Send Project dataset to Primavera for writing.
10
Send Email with response (if configured). If Email is configured in SAP EPC Configuration than this
step sends email to user.
11
Create Final response XML. This is final step of the workflow that contains response xml for
returning back to the user.
List of BAPIs used in SAP PS to Primavera synchronization workflow:
o
o
BAPI_PROJECT_GETINFO – Retrieves SAP Project and WBS related data
BAPI_NETWORK_GETINFO – Retrieves Network, Activity, Element and Component related data
2.3 Object Mappings
Object Mapping from SAP Project System to Oracle Primavera P6 EPPM
No
SAP Project System
Oracle Primavera P6 EPPM
o
Project Definition
Project
o
WBS Element
WBS
o
Network
WBS, Activity Code Assignment
o
WBS Milestone
Activity Milestone
o
Activity
Activity
o
Activity with Work Center
Resource Assignment
o
Activity with Cost
Expense
o
Activity Milestone
Activity Milestone
o
Activity Element with Work Center
Resource Assignment
o
Activity Element with Cost
Expense
o
Material Component
Resource Assignment
o
Material Component
Expense
o
Work Center
Resource (Labor)
o
Material
Resource (Material)
o
Relationship
Relationship
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
11
2.4 SAP Project Field Mappings
The Project information in Oracle Primavera P6 EPPM is the nearest equivalent to a Project definition in SAP Project System
Project. Following table has mappings of Project, Project Note, Project Code values.
·
·
·
·
·
SAP EPC creates Projects in P6 EPPPM under “SAPEPS” EPS node.
SAP EPC checks and updates only changed existing Project data in Primavera.
Notebook topic “SAP Last Updated “is created and filled with the current date and time of the SAP EPC integration service
engine.
You can either user Project Code or UDF on Primavera side for mapping Project level fields or custom fields at Project level
in SAP PS.
Check Primavera write rules for Project Object in config/im/primavera/ps/CRUDRuleWritePrimaveraProject.xml file. You
can set Project fields available for update or create.
NOTE: There are several other Project level fields available for mappings. Go to config/im/schemas/p6Project.xsd file to see list of
additional fields available at this object level for mappings.
SAP
Primavera
PROJECT
PROJECT
SAP PS Object Information:
·
·
BAPI: BAPI_PROJECT_GETINFO,
TABLE: E_PROJECT_DEFINITION
Primavera Business Object Information:
·
·
·
Project
ProjectNote
ProjectCode
Supported CRUD Action:
·
·
Create
Update
No
SAP Project System
Primavera – Project Fields
Condition if any
1
PROJECT_DEFINITION
ProjectId
o
Mandatory Key field.
2
DESCRIPTION
Name
o
Mandatory field.
3
-
ParentEPS
o
Set to hard-coded EPS with name
“SAPEPS”
4
START
PlannedStartDate
o
Only set during Project creation.
5
START
AnticipatedStartDate
6
FINISH
AnticipatedFinishDate
7
CALENDAR
ActivityDefaultCalendar
8
SYSTEM_STATUS
Status
o
Set to Planned.
9
-
ActivityDefaultActivityType
o
Set to “Task Dependent”
Project Note
No
SAP Project System
Primavera – Project Note
Condition if any
1
PROJECT_DEFINITION
ProjectId
o
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
Mandatory field.
CUSTOMER
© 2016 SAP AG. All rights reserved. 12
No
SAP Project System
Primavera – Project Note
Condition if any
2
PROJECT_DEFINITION
WBSCode
o
Mandatory field.
3
-
Note (text)
o
Current date time of data transfer to
Primavera.
4
-
NotebookTopicName
o
Set to hard-coded “SAP Last Updated”
Project Codes
No
SAP Project System
Primavera – Project Code
Condition if any
1
PROJECT_DEFINITION
SAP Project
o
Mandatory field.
2
PLANT
SAP Plant
o
Mandatory field.
3
BUS_AREA
SAP Business Area
4
CONTROLLING_AREA
SAP Controlling Area
5
PROFIT_CTR
SAP Profit Center
6
PROJECT_CURRENCY
SAP Proj Currency
7
PROJECT_CUREENCY_ISO
SAP Proj Curr ISO
8
NETWORK_PROFILE
SAP Network Profile
o
Mandatory field.
9
PROJECT_PROFILE
SAP Project Profile
o
Mandatory field.
10
OBJECTCLASS
SAP Object Class
11
BUDGET_PROFILE
SAP Budget Profile
12
WBS_SCHED_PROFILE
SAP WBS Sched Prof
13
CSH_BDGT_PROFILE
SAP Cash Budget Prof
14
PLAN_PROFILE
SAP Plan Profile
15
COMP_CODE
SAP Comp Code
16
EQUITY_TYPE
SAP Equity Type
17
CALENDAR
SAP Calendar
18
TIME_UNIT
SAP Time Unit
19
TIME_UNIT_ISO
SAP Time Unit ISO
20
TAXJURCODE
SAP Tax Jurisdiction
21
PLAN_BASIC
SAP Plan Basic
22
PLAN_FCST
SAP Plan Forecast
23
-
SAP Transfer
o
Set to “Yes” for transferring updates
back to SAP.
2.5 SAP WBS Mappings
SAP Project System WBS structure display is different from Primavera WBS structure display. Primavera displays structure in
hierarchy and might show duplication of values in the display.
·
·
SAP EPC checks and updates only changed Project data if exists in Primavera.
Check Primavera write rules for Project Object in config/im/primavera/ps/CRUDRuleWritePrimaveraProject.xml file. You
can set WBS fields available for update or create.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
13
NOTE: There are several other Project level fields available for mappings. Go to config/im/schemas/ p6Project.xsd file to see list of
additional fields available at this object level for mappings.
SAP
Primavera
WBS
WBS Element
SAP PS Object Information:
BAPI: BAPI_PROJECT_GETINFO,
·
·
TABLE: E_WBS_HIERARCHIE_TABLE, E_WBS_ELEMENT_TABLE
Primavera Business Object Information:
·
·
WBS
UDF (User Defined Fields)
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera - WBS Fields
Condition if any
1
WBS_ELEMENT
WBSCode
o
o
o
Mandatory Key field.
Make sure length of WBS Code field in
Primavera is set same as WBS_ELEMENT
in SAP PS.
Length:
P6:WBSCode=SAP.WBS_ELEMENT
2
DESCRIPTION
Name
o
Mandatory field.
3
UP
ParentWBS
o
Retrieved using hierarchy table.
(E_WBS_HIERARCHIE_TABLE)
4
PROJECT_DEFINITION
ProjectId
5
WBS_BASIC_START_DATE
AnticipatedStartDate
6
WBS_BASIC_FINISH_DATE
AnticipatedFinishDate
User Defined Fields
No
SAP Project System
Primavera – User Defined Fields
Condition if any
1
WBS_ELEMENT
SAP WBS Element
o
Mandatory field.
2
UP
SAP Parent WBS Element
(E_WBS_HIERARCHIE_TABLE)
3
PROJ_TYPE
SAP WBS Project Type
4
COMP_CODE
SAP WBS Company Code
5
PLANT
SAP WBS Plant
6
PROFIT_CTR
SAP Profit Center
7
-
SAP Transfer
o
Set to “Yes” for transferring updates back
to SAP.
8
-
SAP Object
o
Set to “WBS_ELEMENT”.
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 14
2.6 SAP Network Mappings
SAP Project System’s Network object does not have corresponding object in Primavera. There is no such object as a network in
Primavera. It is mapped as WBS under the WBS Element that it exist in SAP PS. Activities belongs to the NETWORK in SAP PS will
be created under the WBS Element that it belongs to and not the NETWORK.
·
·
·
SAP EPC checks and updates only changed data if exists in Primavera.
Check Primavera write rules for Project Object in config/im/primavera/ps/CRUDRuleWritePrimaveraProject.xml file. You
can set WBS fields available for update or create.
NETWORK is also mapped as Activity Code assigned to the Activity in Primavera.
NOTE: There are several other NETWORK level fields available for mappings. You can map those fields as UDF in Primavera.
SAP
Primavera
WBS
NETWORK
SAP PS Object Information:
BAPI: BAPI_PROJECT_GETINFO,
·
·
TABLE: E_NETWORK
Primavera Business Object Information:
·
·
WBS
UDF (User defined fields)
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera - WBS Fields
Condition if any
1
NETWORK
WBS Code
o
Mandatory Key field.
2
SHORT_TEXT
Name
o
Mandatory field. Unique Name within
Project.
3
WBS_ELEMENT
ParentWBS
o Mandatory Key field.
4
PROJECT_DEFINITION
ProjectId
5
START_DATE
AnticipatedStartDate
6
FINISH_DATE
AnticipatedFinishDate
User Defined Fields (UDF)
No
SAP Project System
Primavera – User Defined Fields
1
WBS_ELEMENT
SAP WBS Element
2
-
SAP Object
3
NETWORK
SAP Network
4
PROFILE
SAP Network Profile
5
MSP_CONTROLLER
SAP MRP Controller
6
NETWORK_TYPE
SAP Network Type
Condition if any
o
o
o
Mandatory Field.
Set to “NETWORK”.
This is required field to identify
whether it is WBS or Network object.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
15
No
SAP Project System
Primavera – User Defined Fields
Condition if any
7
-
SAP Transfer
o
8
PLANT
SAP Plant
9
PROFIT_CTR
SAP Profit Center
Set to “Yes” for transferring updates
back to SAP.
2.7 SAP Activity Mappings
SAP Network Activities are mapped directly as Activities in Primavera. Primavera itself does not differentiate between different
types of Activities. However, the control key for an Activity appears in the Activity Code.
Primavera
SAP
Activity
Activity
SAP PS Object Information:
BAPI: BAPI_NETWORK_GETINFO,
·
·
TABLE: E_ACTIVITY_TABLE
Primavera Business Object Information:
·
·
·
Activity
Activity Code
UDF
Supported CRUD Action:
·
·
Create
Update
No
SAP Project System
Primavera - Activity
Condition if any
1
NETWORK-ACTIVITY
Activity Id
o
o
Mandatory Field.
Maps to two fields i.e. <NETWORK><ACTIVITY>.
o
Separated by “-“separator.
2
DESCRIPTION
Name
o
Mandatory Field.
3
-
Type
o
Default set to “Task Dependent”
4
-
DurationType
o
Default set to “Fixed Duration and Units”
5
WBS_ELEMENT
WBSCode
6
FACTORY_CALENDAR
CalendarName
o
If not set, Primavera will use Activity default
calendar.
7
ACTUAL_START_DATE
ActualStartDate
8
ACTUAL_FINISH_DATE
ActualFinishDate
9
EARLY_START_DATE
PlannedStartDate
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 16
No
SAP Project System
Primavera - Activity
Condition if any
10
EARLY_FINISH_DATE
PlannedFinishDate
11
-
PercentCompleteType
o
Default set to “Physical”
12
DURATION_NORMAL
PlannedDuration
o
Maps to DURATION_NORMAL for “internal”
and “cost” type of SAP Activities.
13
PLND_DELRY
PlannedDuration
o
Maps to PLND_DELRY for “service” and
“external” type of SAP Activities.
13
CONSTRAINT_TYPE_START
PrimaryConstraintType
o
Set only if Task is not started or finished and
constraint values are not null.
o
If no Finish Constraint is set then
o
o
Set to Start On for
CONSTRAINT_TYPE=1
o
Set to Start On or After for
CONSTRAINT_TYPE=2
o
Set to Start On or Before for
CONSTRAINT_TYPE=3
If START and FINISH constraint exist then
o
o
If only Finish constraint exist then
o
14
CONSTRAINT_START_DATE
Set to Start On or After
Set to Finish On or Before
PrimaryConstraintDate
o
Set only if Task is not started or finished and
start constraint date value is not null.
CONSTRAINT_START_TIME
15
-
SecondaryConstraintType
o
Set only if no start constraint and finish
constraint values are not null.
16
CONSTRAINT_FINISH_DATE
SecondaryConstraintDate
o
Set only if Task is not started or finished, start
constraint exist and finish constraint date
value is not null.
CONSTRAINT_FINISH_TIME
Activity Codes
·
Some of the Activity Codes are commented out (not transferring) by default. Uncomment any of these Activity Codes to
transfer as per your business use case.
No
SAP Project System
Primavera – Activity Codes
Condition if any
1
ACTIVITY
SAP Activity
o
Mandatory Field.
2
NETWORK
SAP Network
o
Mandatory Field.
3
CONTROL_KEY
SAP Control Key
o
Mandatory Field.
4
WBS_ELEMENT
SAP WBS Element
5
-
SAP Transfer
o
Set to “Yes” for transferring updates back to
SAP.
6
COST_ELEM
SAP Cost Element
o
7
PRIORITY
SAP Priority
o
o
Not transferring by default. (Commented out).
Uncomment this code to transfer data.
8
FUNC_AREA_LONG
SAP Functional Area
9
PLANT
SAP Plant
10
PROFILE_CTR
SAP Profit Center
o
o
Not transferring by default. (Commented out).
Uncomment this code to transfer data.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
17
No
SAP Project System
Primavera – Activity Codes
Condition if any
11
DISTRIBUTING_KEY
SAP Distributing Key
o
o
Not transferring by default. (Commented out).
Uncomment this code to transfer data.
12
TAXJURCODE
SAP Tax Juridiction
o
o
Not transferring by default. (Commented out).
Uncomment this code to transfer data.
13
OBJECTCLASS
SAP Object Class
o
o
Not transferring by default. (Commented out).
Uncomment this code to transfer data.
14
FACTORY_CALENDAR
SAP Factory Calendar
15
OBJECTCLASS_EXT
SAP Object Class Ext
o
o
Not transferring by default. (Commented out).
Uncomment this code to transfer data.
16
PROJECT_SUMMARIZATION
SAP Project Summ
o
o
Not transferring by default. (Commented out).
Uncomment this code to transfer data.
17
MATL_GROUP
SAP Material Group
User Defined Fields
·
User defined fields in SAP are mapped to P6EPPM UDF as shown in mapping table below. By default, transfer of these
fields is off. Go to SAPPSCOnfiguration.xml -> NetworkActivityUDF section for Primavera to turn the transfer for fields ON.
If you want transfer only some of these SAP User fields than comment out rest of the fields from transferring.
No
SAP Project System
Primavera – User Defined Fields
1
USER_FIELD_CHAR20_1
SAP USER_FIELD_CHAR20_1
2
USER_FIELD_CHAR20_2
SAP USER_FIELD_CHAR20_2
3
USER_FIELD_CHAR10_1
SAP USER_FIELD_CHAR10_1
4
USER_FIELD_CHAR10_2
SAP USER_FIELD_CHAR10_2
5
USER_FIELD_DATE1
SAP USER_FIELD_DATE1
6
USER_FIELD_DATE2
SAP USER_FIELD_DATE2
7
USER_FIELD_FLAG1
SAP USER_FIELD_FLAG1
8
USER_FIELD_FLAG2
SAP USER_FIELD_FLAG2
Condition if any
2.8 Milestone Mappings
SAP EPC SIS supports both WBS Element Milestones and Activity Milestones. They are both represented as milestone tasks under
a WBS summary task in Primavera.
2.8.1
SAP WBS Milestone Mappings
This is shown as an Activity with a duration of zero days for which the type is set as Start Milestone. It is distinguished from an
Activity milestone by the entry in the SAP Object Activity Code. Value of SAP Object Activity code for WBS Milestone is
“WBS_MILESTONE”.
SAP
Primavera
WBS Milestone
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
Activity Milestone
CUSTOMER
© 2016 SAP AG. All rights reserved. 18
SAP PS Object Information:
BAPI: BAPI_PROJECT_GETINFO,
·
·
TABLE: E_WBS_MILESTONE_TABLE
Primavera Business Object Information:
·
·
Activity
UDF (User Defined Fields)
Supported CRUD Action:
·
·
Create
Update
No
SAP Project System
Primavera – Activity
(Milestone)
Condition if any
1
MILESTONE_NUMBER
ActivityId
o
2
DESCRIPTION
Name
3
-
Type
4
WBS_ELEMENT
WBSCode
5
ACTUAL_DATE. ACTUAL_TIME
ActualStartDate
o
Set to date and time
6
-
DurationType
o
Set to “Fixed Duration and Units/Time”
hard-coded value.
7
-
PercentCompleteType
o
Set to “Physical” hard-coded value.
8
FIXED_MILESTONE_DATE_BASIC
PrimaryConstraintDate
o
Set to date and time
PrimaryConstraintType
o
“Start On or After” hard-coded value.
Mandatory Key field.
Mandatory field. Unique Name within
Project.
o
Set to “Start Milestone” hard-coded
value
Mandatory field.
FIXED_MILESTONE_TIME_BASIC
9
-
User Defined Fields
No
SAP Project System
Primavera – User Defined
Fields
Condition if any
1
-
SAP Object
o
o
o
Mandatory field.
Set to “WBS_MILESTONE”
This is required value to identify whether
it is WBS Milestone in SAP or Activity
Milestone.
2
WBS_ELEMENT
SAP WBS Element
3
MILESTONE_USAGE
SAP Usage
4
EARNED_VALUE_INDICATOR
SAP Prog. Analysis
5
TREND_ANALYSIS_INDICATOR
SAP trend Analysis
6
SALES_DOC_DATE_INDICATOR
SAP Sales Doc Date
7
INVOICE_PERCENTAGE
SAP Invoice Percent
8
-
SAP Transfer
o
Set to “Yes” hard-coded value for
transferring updates back to SAP.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
19
2.8.2
SAP Activity Milestone Mappings
This is shown as an Activity with a duration of zero days for which the type is set as Start Milestone. It is distinguished from a WBS
Milestone by the entry in the SAP Object Activity Code. Value of SAP Object Activity code for Activity Milestone is
“ACTIVITY_MILESTONE”.
SAP
Primavera
SAP Transfer
Activity Milestone
Activity Milestone
SAP PS Object Information:
BAPI: BAPI_NETWORK_GETINFO,
·
·
TABLE: E_ACTIVITY_MILESTONE
Primavera Business Object Information:
·
·
Activity
Activity Code
Supported CRUD Action:
·
·
Create
Update
No
SAP Project System
Primavera – Activity (Milestone)
Condition if any
1
MILESTONE_NUMBER
Activity Id
2
DESCRIPTION
Name
o
Mandatory Field.
3
-
Type
o
Set to “Start Milestone” hard-coded
value
4
WBS_ELEMENT
WBSCode
5
ACTUAL_DATE, ACTUAL_TIME
ActualStartDate
o
Set to date and time
6
-
DurationType
o
Set to “Fixed Duration and
Units/Time” hard-coded value.
-
PlannedDuration
o
Set to “0” value.
7
-
PercentCompleteType
o
Set to “Physical” hard-coded value.
8
FIXED_MILESTONE_DATE_BASIC
PrimaryConstraintDate
o
Set to date and time
PrimaryConstraintType
o
Set to “Start On or After” hard-coded
value.
Mandatory Key Field.
FIXED_MILESTONE_TIME_BASIC
9
-
No
SAP Project System
Primavera – Activity Codes
Condition if any
1
-
SAP Object
o
o
o
2
WBS_ELEMENT
SAP WBS Element
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
Mandatory Field.
Set to “ACTIVITY_MILESTONE”.
This is required value to identify
whether it is WBS Milestone in SAP or
Activity Milestone.
CUSTOMER
© 2016 SAP AG. All rights reserved. 20
No
SAP Project System
Primavera – Activity Codes
3
MILESTONE_USAGE
SAP Usage
4
EARNED_VALUE_INDICATOR
SAP Prog. Analysis
5
TREND_ANALYSIS_INDICATOR
SAP trend Analysis
6
SALES_DOC_DATE_INDICATOR
SAP Sales Doc Date
7
INVOICE_PERCENTAGE
SAP Invoice Percent
8
-
SAP Transfer
Condition if any
o
Set to “Yes” hard-coded value for
transferring updates back to SAP.
2.9 Resource Mappings
2.9.1
SAP Work Center Mappings
In SAP PS, Work Centers can be assigned at Activity or Activity Element level for “internal” types of Activities. Primavera does not
use the 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 Work Center and Activity Type values are combined to depict the resource in Primavera and assigned to the task as
an assignment with capacity planning and actuals work data.
SAP Work Center assigned at SAP Activity and SAP Activity Element having type ”internal” with Activity Type data will be
transferred as Primavera as Resource during this work flow.
o
SAP
Primavera
Resource
Activity, Activity Element
Work Center
SAP PS Object Information:
BAPI: BAPI_NETWORK_GETINFO,
·
·
TABLE: E_ACTIVITY_TABLE, E_ACTIVITY_ELEMENT
Primavera Business Object Information:
·
Resource
Supported CRUD Action:
·
Create
No.
SAP
Primavera – Resource
Condition if any
1
WORK_CNTR-ACTTYPE
Resource Id
o
Mandatory Field.
o
Maps to two fields separated by “-“ i.e.
<WORK_CNTR>-<ACTTYPE>
Set to “Labor”
2
-
Type
o
3
WORK_CNTR-ACTTYPE
Name
Maps to two fields separated by “-“ i.e.
<WORK_CNTR>-<ACTTYPE>
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
21
No.
SAP
Primavera – Resource
Condition if any
4
-
IsActive
o
2.9.2
Set to “True”
SAP Material Component Mappings
SAP PS Material is mapped to the Primavera Resource with type Material.
Primavera
SAP
Resource
Material
SAP PS Object Information:
BAPI: BAPI_NETWORK_GETINFO,
·
·
TABLE: E_COMPONENT
Primavera Business Object Information:
·
Resource
Supported CRUD Action:
·
Create
No.
SAP
Primavera – Resource
Condition if any
1
MATERIAL
Resource Id
o
Mandatory Field.
2
-
Type
o
Set to “Material”
3
MATL_DESC
Name
4
-
IsActive
o
Set to “True”
2.10 Assignment Mappings
2.10.1
SAP Activity: Work Center - Assignment Mappings
In SAP PS, Work Centers can be assigned at Activity or Activity Element level for “internal” types of Activities. Primavera 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 Primavera and assigned to the task as
an assignment with capacity planning and actuals work data.
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 22
Primavera
SAP
Resource Assignment
Activity: Work Center
SAP PS Object Information:
·
·
BAPI: BAPI_NETWORK_GETINFO,
TABLE: E_ACTIVITY_TABLE
Primavera Business Object Information:
·
·
ResourceAssignment
UDF
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera – Resource Assignment
Condition if any
1
NETWORK-ACTIVITY
Activity Id
o
o
Mandatory Field.
Maps to two fields i.e. <NETWORK><ACTIVITY>. Separated by “-“separator.
2
WORK_CNTR-ACTTYPE
Resource Id
o
Mandatory Field.
o
Maps to two fields separated by “-“ i.e.
<WORK_CNTR>-<ACTTYPE>
3
COST_ELEM
CostAccount Id
4
WORK_ACTIVITY
PlannedUnits
5
DURATION_NORMAL
PlannedDuration
6
PLANNED_COST
PlannedCost
User Defined Fields
No
SAP Project System
Primavera – User Defined Fields
Condition if any
1
ACTIVITY
SAP Activity
o
Mandatory Field.
2
NETWORK
SAP Network
o
Mandatory Field.
3
NETWORK-ACTIVITY
Multiple Assignment Unique Number
o
Mandatory Field.
o
Multiple Assignment Unique Number is
set to Network ID-Activity ID
4
DESCRIPTION
SAP Description
o
5
-
SAP Transfer
o
Set to “Yes” hard-coded value for
transferring updates back to SAP.
6
-
SAP Object
o
Set to “ACTIVITY_RESOURCE”.
o
This is to identify the Assignment
between Work Center at Activity level or
Work Center at Activity Element level in
SAP PS.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
23
2.10.2 SAP Activity Element: Work Center - Assignment Mappings
In SAP PS, Work Centers can be assigned at Activity or Activity Element level for “internal” types of Activities. Primavera 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 Primavera and assigned to the task as
an assignment with capacity planning and actuals work data.
Primavera
SAP
Resource Assignment
ActivityElement: Work Center
SAP PS Object Information:
·
·
BAPI: BAPI_NETWORK_GETINFO,
TABLE: E_ACTIVITY_ELEMENT
Primavera Business Object Information:
·
·
Resource Assignment
UDF
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera – Resource Assignment
Condition if any
1
NETWORK-ACTIVITY
Activity Id
o
o
Mandatory Field.
Maps to two fields i.e. <NETWORK><ACTIVITY>. Separated by “-“separator.
2
WORK_CNTR-ACTTYPE
Resource Id
o
Mandatory Field.
o
Maps to two fields separated by “-“ i.e.
<WORK_CNTR>-<ACTTYPE>
3
COST_ELEM
CostAccount Id
4
WORK_ACTIVITY
PlannedUnits
5
DURATION_NORMAL
PlannedDuration
6
PLANNED_COST
PlannedCost
7
ACTUAL_COST
ActualCost
8
ACTUAL_START_DATE
ActualStratDate
9
ACTUAL_FINISH_DATE
ActualFinishDate
10
WORK_ACTUAL
ActualUnits
11
WORK_ACTIVITY
PlannedUnits
User Defined Fields
No
SAP Project System
Primavera – User Defined Fields
Condition if any
1
ACTIVITY
SAP Activity
o
Mandatory Field.
2
NETWORK
SAP Network
o
Mandatory Field.
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 24
No
SAP Project System
Primavera – User Defined Fields
Condition if any
3
NETWORK-ACTIVITYELEMENT
Multiple Assignment Unique Number
o
Mandatory Field.
o
Multiple Assignment Unique Number is
set to Network ID-Activity ID-ELEMENT
o
This fields is required since in SAP PS,
you can have multiple Activity Element of
an Activity having same Work Center.
This field will identify which
ActivityElement resource assignment
belongs to in P6EPPM.
Mandatory Field.
4
ELEMENT
SAP Activity Element
o
5
DESCRIPTION
SAP Description
o
6
PLANT
SAP Plant
o
7
CONTROL_KEY
SAP Control Key
o
8
-
SAP Transfer
o
Set to “Yes” hard-coded value for
transferring updates back to SAP.
9
-
SAP Object
o
Set to “ELEMENT_RESOURCE”.
o
This is to identify the Assignment
between Work Center at Activity level or
Work Center at Activity Element level in
SAP PS.
2.10.3 SAP Material Component - Assignment Mappings
Primavera does not have any objects that are hierarchically subordinate to tasks. You can only represent Material Components in
Primavera as Material Resources for an Activity.
Primavera
SAP
Resource Assignment
Material Component
SAP PS Object Information:
·
·
BAPI: BAPI_NETWORK_GETINFO,
TABLE: E_COMPONENT
Primavera Business Object Information:
·
·
Resource Assignment
UDF
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera – Resource Assignment
Condition if any
1
NETWORK-ACTIVITY
Activity Id
o
Mandatory Field.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
25
No.
SAP Project System
Primavera – Resource Assignment
2
MATERIAL
Resource Id
3
GL_ACCOUNT
CostAccount Id
4
ENTRY_QUANTITY
PlannedUnits
Condition if any
o
Maps to two fields i.e. <NETWORK><ACTIVITY>. Separated by “-“separator.
o
Mandatory Field.
User Defined Fields
No
SAP Project System
Primavera – User Defined Fields
Condition if any
1
ACTIVITY
SAP Activity
o
Mandatory Field.
2
NETWORK
SAP Network
o
Mandatory Field.
3
MATERIAL-COMPONENT
Multiple Assignment Unique
Number
o
Mandatory Field.
o
Multiple Assignment Unique Number is
set to MATERIAL - COMPONENT
o
This field is required since in SAP PS, you
can have multiple Components having
same Material. This field will identify
which Component resource assignment
belongs to in P6EPPM.
4
MATERIAL
SAP Material
o
Mandatory Field.
5
COMPONENT
SAP Component
o
Mandatory Field.
5
ITEM_NUMBER
SAP Item Number
6
MATL_DESC
SAP Description
7
ITEM_TEXT
SAP Item Number Text
8
PRICE
SAP Price
9
PRICE_UNIT
SAP Price Unit
o
10
PLANT
SAP Plant
o
11
MATL_GROUP
SAP Material Group
o
12
-
SAP Transfer
o
Set to “Yes” hard-coded value for
transferring updates back to SAP.
13
-
SAP Object
o
Set to “MATERIAL”.
o
This is to identify the Assignment
between Work Center at Activity level or
Work Center at Activity Element level in
SAP PS.
2.11 Expense Mappings
2.11.1
SAP Activity: Cost, Service, External - Expense Mappings
SAP Activity with type Cost, Service or External are mapped to the Primavera Expense.
o
Activity with Control Key=Cost and it has Planned Cost
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 26
o
Activity with Control Key=Service or External and it has Price data.
Primavera
SAP
Expense
Activity
SAP PS Object Information:
BAPI: BAPI_NETWORK_GETINFO,
·
·
TABLE: E_ACTIVITY_TABLE
Primavera Business Object Information:
·
Activity Expense
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera - Expense
Condition if any
1
NETWORK-ACTIVITY
Activity Id
o
o
Mandatory Field.
Maps to two fields i.e. <NETWORK><ACTIVITY>. Separated by “-“separator.
2
NETWORK-ACTIVITY
ExpenseItem
o
o
Mandatory Field.
Maps to two fields i.e. <NETWORK><ACTIVITY>. Separated by “-“separator.
3
COST_ELEM
CostAccount Id
4
PLANNED_COST
PlannedUnits
o
Mapped when Control Key =Cost
5
PRICE_UNITS
PlannedUnits
o
Mapped when Control Key = Service or
External.
6
PLANNED_COST
PlannedCost
o
o
Mapped when Control Key =Cost
Primavera field PlannedCost is mapped to
the PLANNED_COST field but it can be map
to the ACTIVITY_COST from SAP PS.
Implement this based on your business
requirement.
o
7
PRICE
PlannedCost
8
DESCRIPTION
ExpenseDescription
9
-
10
-
2.11.2
o
Mapped when Control Key = Service or
External.
AutoComputeActuals
o
Set to “false”
AccrualType
o
Set to “End of Activity”
SAP Activity Element: Cost, Service, External - Expense Mappings
SAP Activity Element with type Cost, Service and External is mapped to the Primavera Expense.
o
o
Activity Element with Control Key=Cost and it has Planned Cost
Activity Element with Control Key=Service or External and it has Price data.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
27
Primavera
SAP
Expense
ActivityElement
SAP PS Object Information:
BAPI: BAPI_NETWORK_GETINFO,
·
·
TABLE: E_ACTIVITY_ELEMENT
Primavera Business Object Information:
·
Activity Expense
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera - Expense
Condition if any
1
NETWORK-ACTIVITY
Activity Id
o
o
Mandatory Field.
Maps to two fields i.e. <NETWORK><ACTIVITY>. Separated by “-“separator.
2
NETWORK-ACTIVITYELEMENT
ExpenseItem
o
o
Mandatory Field.
Maps to three fields i.e. <NETWORK><ACTIVITY>-<ELEMENT>. Separated by ““separator.
3
COST_ELEM
CostAccount Id
4
PLANNED_COST
PlannedUnits
o
Mapped when Control Key =Cost
5
PRICE_UNITS
PlannedUnits
o
Mapped when Control Key = Service or
External.
6
PLANNED_COST
PlannedCost
o
o
Mapped when Control Key =Cost
Primavera field PlannedCost is mapped to
the PLANNED_COST field but it can be map
to the ACTIVITY_COST from SAP PS.
Implement this based on your business
requirement.
o
7
PRICE
PlannedCost
8
DESCRIPTION
ExpenseDescription
9
-
10
-
2.11.3
o
Mapped when Control Key = Service or
External.
AutoComputeActuals
o
Set to “false”
AccrualType
o
Set to “End of Activity”
SAP Material Component - Expense Mappings
SAP Material Component is mapped to the Primavera Expense.
o
Mapped if Material Component has Quantity data.
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 28
Primavera
SAP
Expense
Material Component
SAP PS Object Information:
BAPI: BAPI_NETWORK_GETINFO,
·
·
TABLE: E_COMPONENT
Primavera Business Object Information:
·
Activity Expense
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera - Expense
Condition if any
1
NETWORK-ACTIVITY
Activity Id
o
o
Mandatory Field.
Maps to two fields i.e. <NETWORK><ACTIVITY>. Separated by “-“separator.
2
MATERIAL-COMPONENT
ExpenseItem
o
o
Mandatory Field.
Maps to two fields i.e. <MATERIAL><COMPONENT>. Separated by “-“separator.
3
GL_ACCOUNT
CostAccount Id
4
ENTER_QUANTITY
PlannedUnits
6
PRICE
PricePerUnit
7
MATL_DESC
ExpenseDescription
8
-
AutoComputeActuals
o
Set to “false”
9
-
AccrualType
o
Set to “End of Activity”
2.12 SAP Relationship Mapping
Since relationships are common to both the SAP Project System and Oracle Primavera P6 EPPM, 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 Oracle Primavera P6 EPPM these intervals are only expressed in absolute units,
that is days or weeks and so on.
In SAP Project System 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 Oracle Primavera P6 EPPM. Therefore only one relationship is transferred.
You can use the Predecessors and Successors fields in Oracle Primavera P6 EPPM to display the Activity to which an Activity is
linked. If the relationship is not an FS relationship (default value), the relationship type is displayed. If there is a time interval between
the two activities, that interval is also displayed. Here the activities are referred to by their ID.
In Oracle Primavera P6 EPPM an Activity that must start or finish before another Activity can begin is called a predecessor Activity.
An Activity that depends on the start or finish of a preceding Activity is called a successor Activity.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
29
Primavera
SAP
Relationship
Relationship
SAP PS Object Information:
·
·
BAPI: BAPI_NETWORK_GETINFO,
TABLE: E_RELATION
Primavera Business Object Information:
·
Relationship
Supported CRUD Action:
·
·
Create
Update
No.
SAP Project System
Primavera - Relationship
Condition if any
1
RELATION_TYPE
Attribute “type”
o
o
o
o
o
Mandatory field.
FF FinishFinish
FS FinishStart
SF StartFinish
SS StartStart
2
PROJECT_DEFINITION
PredecessorProjectID
o
Mandatory field.
3
NETWORK_PREDECESSOR
PredecessorActivityID
o
o
o
Mandatory field.
Maps to two fields i.e. <NETWORK><ACTIVITY>.
Separated by “-“separator.
ACTIVITY_ PREDECESSOR
4
PROJECT_DEFINITION
SuccessorProjectID
o
Mandatory field.
5
NETWORK_SUCCESSOR
SuccessorActivityID
o
o
o
Mandatory field.
Maps to two fields i.e. <NETWORK><ACTIVITY>.
Separated by “-“separator.
o
If no LAG, then default to “0’
ACTIVITY_ SUCCESSOR
6
DURATION_RELATION
Lag
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 30
3 Oracle Primavera P6 EPPM to SAP Project System (PS)
Because the Primavera objects must have a particular format to be mapped successfully to the SAP Project System this is the more
complex of the two mapping scenarios. Objects created in Primavera have to fulfill certain criteria before they can be transferred to
the Project System. Also, Scheduling in Primavera and the SAP Project System differs in detail. This can cause discrepancies in
scheduling data due to scheduling calculation when transferring related data between the two programs.
3.1 Workflow
SAP EPC SIS contains a workflow that includes multiple steps to transfer the data from Oracle Primavera P6 EPPM to SAP Project
System. This workflow consists of a series of steps which represents a particular part of the business process.
Highlights of the EPC SIS SAP Project System to Oracle Primavera P6 EPPM workflow, are described below.
1.
Reads the requested Primavera Project data.
2.
Reads SAP PS Project related data from SAP using SAP PS standard BAPIs
3.
Maps and applies business rules to SAP PS and Primavera 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.
NOTE: SAP PS BAPI “BAPI_PROJECT_MAINTAIN” locks Project during processing of the data. This Project which is in process by
the BAPI won’t allow any modification by any user. This BAPI may take long time to process your data. If you have
concern/issue with Project locking than consider using SAP PS granular function modules (BAPI) for processing Activity or
other SAP PS Project related data.
Workflow and Mappings file details:
Workflow Name
P3eToSapProjectSync
Workflow File
config/datapath/operations/sapps_p6tosap-operations.xml
Mappings File
config/im/primavera/ps/ map_ primaveraProject_to_sapProject.xsl
Mapping Functions File
config/im/primavera/ps/PSProject-Functions.xsl
Configuration File
config/im/primavera/ps/SAPPSConfiguration.xml
Primavera Read CRUD Rule File
config/im/primavera/ps/CRUDRuleReadPrimaveraProject.xml
Workflow Input Parameters:
idStr
(Required) SAP Project ID used for transferring Project from SAP to Primavera
user
User who initiated the workflow execution request.
server
SAP ERP Server (host) name.
client
SAP ERP client number.
systemNumber
SAP ERP System Number.
Workflow Steps:
No
Step
Description
Main Purpose
1
Build_CRUDPrimavera
ReadRule
This step builds Primavera Project request including
Project whereclause using idStr(Project ID as input
Read Primavera Project
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
31
passed to workflow request), List of Primavera
business objects to be read etc.
2
Execute_PrimaveraRe
ad
Executes Primavera readProject method using data
request information built in step 1.
Read Primavera Project
3
PrimaveraProject
Converts data to Primavera Project Xml simplified format.
Read Primavera Project
4
Build_BAPI
BAPI_PROJECT_GETI
NFO
This steps builds BAPI request with idStr (Project ID
as input passed to workflow request)
Read SAP Project
2
Execute_BAPI
BAPI_PROJECT_GETI
NFO
Executes BAPI request built in Step 1 to read Project
data from SAP PS.
Read SAP Project
3
Build_BAPI_NETWORK
_GETINFO
This steps builds BAPI request to fetch network
data.
Read SAP Project
4
Execute
BAPI_NETWORK_GETI
NFO using the request
built in Step 3.
Executes BAPI request built in Step 1 to read
Network and Activity related data from SAP PS.
Read SAP Project
5
SAPProject
Merge all BAPI responses from above steps
Read SAP Project
6
Map_PrimaveraProject
_to_SAPProject
Map SAP Project to Primavera Project (Mappings). This is
a mapping file for all business objects and its fields.
Mappings
8
Execute_BAPI_PROJE
CT_MAINTAIN
Executes BAPI for writing data to SAP PS.
Write SAP Project
10
Send_Email
Send response (if configured). If Email is configured
in SAP EPC Configuration than this step sends
email to user.
Email response
11
FinalResponse
This is final step of the workflow that contains
response xml for returning back to the user.
Send Response
List of BAPIs used in SAP PS to Primavera synchronization workflow:
o
o
o
BAPI_PROJECT_GETINFO – Retrieves SAP Project and WBS related data
BAPI_NETWORK_GETINFO – Retrieves Network, Activity, Element and Component related data
BAPI_PROJECT_MAINTAIN – Writes data to SAP PS
3.2 Object Mappings
Object Mapping from Oracle Primavera P6 EPPM (P6 EPPM) to SAP Project System
No
Primavera
SAP Project System
1
Project
Project Definition
2
WBS
WBS Element
4
Activity
Activity
5
Activity Milestone
Activity Milestone
6
Activity Milestone
WBS Milestone
6
Assignment
Activity Element
7
Relationship
Relationship
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 32
3.3 SAP Project Mappings
The Project information in Oracle Primavera P6 EPPM is the nearest equivalent to a Project definition in SAP Project System
Project.
SAP
Primavera
Project
Project
SAP PS Object Information:
·
·
BAPI: BAPI_PROJECT_MAINTAIN,
TABLE: I_PROJECT_DEFINITION, I_PROJECT_DEFINITION_UPD
Primavera Business Object Information:
·
·
Project
ProjectCode
Supported CRUD Action:
·
·
·
Update
Create * - SAP EPC ‘Transfer Project’ Transaction do not support creation of Project from Primavera to SAP Project
System. But you can execute this workflow using any REST client or from your custom SAP UI transaction. Creation of
NETWORK and MILESTONE objects are not supported using this workflow.
Workaround for Project creation is to create empty Project with network in SAP Project System and transfer your
Project data for synchronization from Primavera.
No
Primavera - Project
SAP Project System
Condition if any
1
Project Id
PROJECT_DEFINITION
o
2
Name
DESCRIPTION
o This field is updatable.
3
StartDate
START
o
This field is updatable.
4
FinishDate
FINISH
o
This field is updatable.
5
Project Code: SAP Project Profile
PROJECT_PROFILE
o Only required during creation
of Project
6
ActivityDefaultCalendar
CALENDAR
o This field value is set only
during creation but if your
use case requires this to be
updatable than modify
mappings accordingly.
Mandatory field.
Note: You can add more Project fields mapping. Check fields available for updating Project in SAP PS. Check documentation of
BAPI_PROJECT_MAINTAIN and for I_PROJECT_DEFINITION table.
3.4 SAP WBS Mappings
The WBS information in Oracle Primavera P6 EPPM is the nearest equivalent to a WBS Element in SAP Project System Project.
·
In SAP, max length supported for WBS Element 24 characters but in Primavera the length of the WBS Code is configurable
and supports up-to 40 characters. Make sure data enter in Primavera matches the length of data in SAP system.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
33
·
Mappings first checks data from WBS Code in Primavera and if is invalid than it gets WBS data from UDF: SAP WBS
Element. You can remove or modify this mapping as per your requirement. Function that provides this mapping is
“PS:getSAPWBS” in ps-functions.xml file.
SAP
Primavera
WBS
WBS Element
WBS can be transferred from Primavera to SAP if following conditions are met:
·
·
·
UDF value of: "SAP Transfer" not equals "No" - i.e. allowed transfer to SAP
Length of WBS in Primavera is less than 25.
WBS System Status in SAP not equal to TECO, CLSD, LKD
SAP PS Object Information:
·
·
BAPI: BAPI_PROJECT_MAINTAIN,
TABLE: I_WBS_ELEMENT_TABLE, I_WBS_ELEMENT_TABLE_UPDATE
Primavera Business Object Information:
·
·
WBS
UDF
Supported CRUD Action:
·
·
Update
Create
No
.
Primavera - WBS
SAP Project System
Condition if any
1
WBS Code
WBS_ELEMENT
o
o
o
o
Mandatory field.
Max length supported is 24 characters.
Accepts alphanumeric entries.
Value of this object must be unique in the
Project structure.
Or
UDF: SAP WBS Element
2
Project Id
PROJECT_DEFINITION
o
Mandatory field.
3
Name
DESCRIPTION
o
This field is updatable.
4
AnticipatedStartDate
WBS_BASIC_START_DATE*
o This field is commented out. See *Note below.
o This field is updatable.
5
AnticipatedFinishDate
WBS_BASIC_FINISH_DATE*
o This field is commented out. See *Note below.
o This field is updatable.
6
StartDate
WBS_ACTUAL_START_DATE*
o This field is commented out. See *Note below.
o This field is updatable.
7
FinishDate
WBS_ACTUAL_FINISH_DATE*
o This field is commented out. See *Note below.
o This field is updatable.
* Note:
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 34
o
By default, WBS date field mappings are commented out since updating this field depends on additional Project information.
If you are sending WBS START and FINISH dates and if it is not reflecting correctly in SAP PS, contact SAP PS functional
expert or open a message with SAP PS component.
Hint: Updating SAP Project System WBS dates - this might require following conditions to be met:
1.
2.
3.
4.
The SAP Project must have "Released" status.
The SAP WBS Scheduling Profile must be set to "Backwards Scheduling".
Setting an actual finish date for a WBS element requires the status to be REL and all lower-level WBS
elements and, if necessary, the assigned activities must have the CONF status.
See SAP Note 2092962.
o You can add more WBS fields mapping. Check fields available for updating WBS in SAP PS. Check documentation of
BAPI_PROJECT_MAINTAIN and for I_WBS_ELEMENT_TABLE table.
3.5 SAP WBS Hierarchy Mappings
To create or update WBS Element hierarchy in SAP PS, following Primavera WBS fields is mapped.
·
·
·
In SAP, max length supported for WBS Element 24 characters but in Primavera the length of the WBS Code is configurable
and supports up-to 40 characters. Make sure data enter in Primavera matches the length of data in SAP system.
Make sure your WBS structure has all valid WBS Code with correct length and is unique in Project structure.
Mappings first checks data from WBS Code in Primavera and if is invalid than it gets WBS data from UDF: SAP WBS
Element. You can remove or modify this mapping as per your requirement. Function that provides this mapping is
“PS:getSAPWBS” in ps-functions.xml file.
SAP PS Object Information:
·
·
BAPI: BAPI_PROJECT_MAINTAIN,
TABLE: I_WBS_HIERARCHIE_TABLE
Primavera Business Object Information:
·
·
WBS
UDF
WBS can be transferred from Primavera to SAP if following conditions are met:
·
·
UDF value of: "SAP Transfer" not equals "No" - i.e. allowed transfer to SAP
Length of WBS in Primavera is less than 25.
Supported CRUD Action:
·
Update
Primavera - WBS
SAP Project System
Condition If any
WBS Code
WBS_ELEMENT
Mandatory field.
Project Id
PROJECT_DEFINITION
Mandatory field.
Immediate Parent WBS Code
UP
Mandatory field.
Parent WBS – One level Up.
Immediate Child WBS Code
DOWN
Mandatory field.
Child WBS – One level Down.
Preceding Sibling WBS Code
LEFT
Mandatory field.
Same level sibling WBS – Same level Up.
Following Sibling WBS Code
RIGHT
Mandatory field.
Same level sibling WBS – Same level down.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
35
3.6 SAP Network Activity Mappings
Activities in Primavera are the equivalent of activities in the SAP Project System. An Activity number in SAP PS can contain four
characters and you can only use this number of characters in Primavera of mapping Activity Id in SAP SP.
Activity can be transferred from Primavera to SAP if following conditions are met:
·
·
·
·
“SAP Network’ Activity Code exist with valid network value.
Activity System Status in SAP not equal to TECO, CLSD, LKD
DELETION_FLAG in SAP for this Activity is not true i.e. Activity not deleted in SAP.
Project Maintain BAPI fails if request contains Activity that is marked for deletion in SAP PS or has specific System
Status.
·
Activity Code: SAP Control Key – Required for new Activity creation only. (If not provided, it defaults to “internal”)
·
Activity Code: SAP Plant – Optional for new Activity creation only.
·
Activity Code: SAP Transfer – Optional (Set value to “No” if you do not want to transfer Activity to SAP PS)
SAP
Primavera
Activity
Activity
SAP PS Object Information:
BAPI: BAPI_PROJECT_MAINTAIN,
·
·
TABLE: I_ACTIVITY, I_ACTIVITY_TABLE
Primavera Business Object Information:
·
·
·
·
Activity
Activity Code
Resource Assignment
Resource Assignment – UDF
Supported CRUD Action:
·
·
Update
Create
No
Primavera - Activity
SAP Project System
Condition if any
1.
Project Id
PROJECT_DEFINITION
o Mandatory field.
2.
Activity Id
NETWORK
o
o
Or
Activity Code: SAP Network
3
Activity Id
ACTIVITY
Or
Activity Code: SAP Activity
o
Mandatory field.
Primavera Activity maps to two SAP fields
i.e. <NETWORK>-<ACTIVITY>.
Gets network number from text before '-'.
o
12 characters long. Numeric entry.
o
o
Mandatory field.
Primavera Activity maps to two SAP fields
i.e. <NETWORK>-<ACTIVITY>.
Gets Activity number from text after '-'.
o
4 characters long. Numeric entry only.
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 36
No
Primavera - Activity
SAP Project System
Condition if any
4
Activity Code: SAP Control
Key
CONTROL_KEY
o
o
Mandatory field for new Activity only.
Control Key is required field for creating new
Activity in SAP PS.
if getting invalid/null control key from
Primavera then map it to the default value
from configuration file SAPPSconfiguration.xml
5
Name
DESCRIPTION
o
This field is updatable.
6
Parent WBS Code
WBS_ELEMENT
o
Mandatory field.
o
Primavera Parent WBS Code which maps to
SAP WBS Element
7
PrimaryConstraintType,
CONSTRAINT_TYPE_START
This field is updatable.
Or
Set value from constraint that is of type
“Start” from Primavera.
SecondaryConstraintType
If no “Start” constraint set in Primavera
than it defaults to “1” (Start On)
8
9
PrimaryConstraintDate
CONSTRAINT_START_DATE
o
PrimaryConstraintDate
CONSTRAINT_START_TIME
o This field is updatable.
PrimaryConstraintType,
CONSTRAINT_TYPE_FINISH
This field is updatable.
Or
Set value from constraint that is of type
“Finish” from Primavera.
SecondaryConstraintType
10
SecondaryConstraintDate
This field is updatable.
o
If no “Finish” constraint set in Primavera
than it defaults to “1” (Finish On)
CONSTRAINT_FINISH_DATE
o
This field is updatable.
CONSTRAINT_FINISH_TIME
o
This field is updatable.
WORK_ACTIVITY
o
This field is updatable.
o
PlannedUnits is mapped from Primavera
ResourceAssignment mapped to this
Activity and if it is exist.
o
This is for Internal type of Activity in SAP PS.
Or
PrimaryConstraintDate
11
SecondaryConstraintDate
Or
PrimaryConstraintDate
11
ResourceAssignment
/PlannedUnits
12
-
UN_WORK
Set to “H”
13
-
UN_WORK_ISO
Set to “HUR”
14
ResourceAssignment
WORK_CNTR
o
/ResourceId
o
o
Primavera Resource maps to two SAP fields
i.e. < WORK_CNTR >-< ACTTYPE>.
Maps in the case of new
ResourceAssignment or Resource changes
in Primavera and do not match
WORK_CNTR in Activity is SAP PS.
Gets value from ResourceId before ‘-‘.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
37
No
Primavera - Activity
SAP Project System
Condition if any
15
ResourceAssignment
ACTTYPE
o
o
Primavera Resource maps to two SAP fields
i.e. < WORK_CNTR >-< ACTTYPE>.
Maps in the case of new
ResourceAssignment or Resource changes
in Primavera and do not match
WORK_CNTR in Activity is SAP PS.
Gets value from ResourceId after ‘-‘.
/ResourceId
o
16
Activity Code: SAP Plant
PLANT
o
Mandatory field for new Activity creation.
17
CalendarName
FACTORY_CALENDAR
o
Mandatory field for new Activity only.
19
PlannedDuration
DURATION_NORMAL
o This field is updatable.
o
This mapping applies to SAP Activity with
type “Internal”
20
-
DURATION_NORMAL_UNIT
Set to ‘TAG’
21
-
DURATION_NORMAL_UNIT_ISO
Set to DAY
22
PlannedDuration
PLND_DELRY
o This field is updatable.
o This mapping applies to SAP Activity with
type External or Service.
NOTE: You can add more Activity fields mapping. Check fields available for updating Project in SAP PS. Check documentation of
BAPI_PROJECT_MAINTAIN and for I_ACTIVITY table.
3.7 SAP Activity Element Mappings
Labor Resource Assignment of Primavera is mapped to the Activity Element of type internal in SAP PS.
NOTE: Activity Element of type Service, External and Cost are not mapped. You can add mappings for these objects in your
Integration Solution.
Activity Element can be transferred from Primavera to SAP if following conditions are met:
·
·
·
Activity System Status in SAP not equal to TECO, CLSD, LKD
Has valid value of NETWORK, ACTIVITY and ELEMENT from UDF in Primavera.
Activity Code: SAP Element – Required. This is mapped to ELEMENT field. Enter value in either this SIS will use
‘Multiple Assignment Unique Number’ UDF to get the value.
·
Activity Code: SAP Activity – Required. This is mapped to ACTIVITY field. Enter value in either this SIS will use
‘Multiple Assignment Unique Number’ UDF to get the value.
·
Activity Code: SAP Network– Required. This is mapped to NETWORK field. Enter value in either this SIS will use
‘Multiple Assignment Unique Number’ UDF to get the value.
·
SAP Description – Required. Maps to the SAP Element description.
·
SAP Transfer – Optional (Set value to “No” if you do not want to transfer Activity to SAP PS)
·
SAP Control Key – Required for new Activity Element creation only. (If not provided, it defaults to “internal”)
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 38
SAP
Primavera
ResourceAssignment
Activity Element
SAP PS Object Information:
·
·
BAPI: BAPI_PROJECT_MAINTAIN,
TABLE: I_ACTIVITY_ELEMENT, I_ACTIVITY_ELEMENT_UPDATE
Primavera Business Object Information:
·
·
Resource Assignment
Resource Assignment – UDF
Supported CRUD Action:
·
·
Update
Create
No
Primavera – Resource
Assignment
SAP Project System
Condition if any
1.
UDF: SAP Network
NETWORK
o
o
Or
UDF: Multiple Assignment
Unique Number
o
o
2.
UDF: SAP Activity
ACTIVITY
o
o
Or
UDF: Multiple Assignment
Unique Number
o
o
3.
UDF: SAP Element
ELEMENT
o
o
Or
UDF: Multiple Assignment
Unique Number
o
o
4.
UDF: SAP Control Key
CONTROL_KEY
o
o
o
o
Mandatory field.
Maps to UDF Assignment level
UDF.
Gets network number from one of
the mentioned UDF.
12 characters long. Numeric entry.
Mandatory field.
Maps to UDF Assignment level
UDF.
Gets ACTIVITY number from one
of the UDF.
4 characters long. Numeric entry
only.
Mandatory field.
Maps to UDF Assignment level
UDF.
Gets ELEMENT value from one of
the UDF.
4 characters long. Numeric entry
only.
Mandatory field.
Maps to UDF Assignment level
UDF.
Required field for creating new
Element in SAP.
If getting invalid/null control key
from UDF then map it to the
default value from configuration
file.
5.
UDF: SAP Description
DESCRIPTION
This field is updatable.
6.
Resource Id
WORK_CNTR
o
o
o
o
Mandatory field.
Primavera Resource Id maps to
two SAP fields i.e. < WORK_CNTR
>-< ACTTYPE>.
Gets Work Center value before ‘-‘.
4 characters long.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
39
No
Primavera – Resource
Assignment
SAP Project System
Condition if any
7.
Resource Id
ACTTYPE
o
o
o
o
Mandatory field.
Primavera Resource Id maps to
two SAP fields i.e. < WORK_CNTR
>-< ACTTYPE>.
Gets ACTVTYPE value after ‘-‘.
4 characters long.
8.
UDF: SAP Plant
PLANT
o
May be required field for creating
new Activity Element.
9.
PlannedUnits
WORK_ACTIVITY
This field is updatable.
11
-
UN_WORK
Set to “H”
12
-
UN_WORK_ISO
Set to “HUR”
NOTE: You can add more Element fields mapping. Check fields available for updating Project in SAP PS. Check documentation of
BAPI_PROJECT_MAINTAIN and for I_ACTIVITY_ELEMENT table.
3.8 SAP Relationship Mappings
Since relationships are common to both the SAP Project System and Primavera, there are no difficulties mapping them. The four
types of relationship that is Finish-Start (FS), Start-Start (SS), Finish-Finish (FF), and Start-Finish (SF) are used in both programs.
You can also transfer Duration / Lag, expressed in absolute values of one of the two activities.
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
Primavera
Relationship
Relationship
SAP PS Object Information:
·
·
BAPI: BAPI_PROJECT_MAINTAIN,
TABLE: I_ RELATION, I_RELATION_UPDATE
Primavera Business Object Information:
·
Relationship
Supported CRUD Action:
·
·
Update
Create
No.
Primavera Relationship
SAP Project System
Condition If any
1
PredesessorActivityId
NETWORK_PREDECESSOR
o
o
o
o
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
Mandatory field.
Primavera Activity Id maps to two SAP
fields i.e. <NETWORK>-<ACTIVITY>.
Gets network number from text before '-'.
12 characters long. Numeric entry.
CUSTOMER
© 2016 SAP AG. All rights reserved. 40
No.
Primavera Relationship
SAP Project System
Condition If any
2
PredesessorActivityId
ACTIVITY_PREDECESSOR
o
o
o
o
3
SuccessorActivityId
NETWORK_SUCCESSOR
o
o
o
o
4
SuccessorActivityId
5
Type
ACTIVITY_SUCCESSOR
RELATION_TYPE
Mandatory field.
Primavera Activity Id maps to two SAP
fields i.e. <NETWORK>-<ACTIVITY>.
Gets Activity number from text after '-'.
4 characters long. Numeric entry only.
Mandatory field.
Primavera Activity Id maps to two SAP
fields i.e. <NETWORK>-<ACTIVITY>.
Gets network number from text before '-'.
12 characters long. Numeric entry.
o
o
Mandatory field.
Primavera Activity Id maps to two SAP
fields i.e. <NETWORK>-<ACTIVITY>.
Gets Activity number from text after '-'.
4 characters long. Numeric entry only.
o
o
o
o
o
Mandatory field.
Relationship Types in both systems:
FinishFinish (FF)
FinishStart (FS)
StartFinish (SF)
o
o
StartStart (SS)
6
Lag
DURATION_RELATION
This field is updatable.
7
-
DURATION_RELATION_UNIT
Set to “STD”
8
-
DURATION_RELATION_UNIT_ISO
Set to “HUR”
3.9
SAP Milestone Mappings
In SAP PS, you can create milestone at WBS or at Activity level. Milestone tasks can be used for various purpose. It represents the
progress milestones achieved for WBS or an Activity. These SAP PS milestones are mapped to an Activity in Primavera with type
Milestone. Only UPDATE action is implemented in this SIS for both WBS and Activity Milestone from Primavera to SAP PS.
3.9.1
SAP WBS Milestone Mappings
WBS Milestone in SAP PS is mapped to the Start Milestone Activity in Primavera. It is distinguished from an Activity milestone by
the entry in the SAP Object Activity Code Field. Value of SAP Object Activity Code field for WBS Milestone is “WBS_MILESTONE”.
Activity Element can be transferred from Primavera to SAP if following conditions are met:
·
·
Activity Code SAP Object : value = ”WBS_MILESTONE”
Activity Code: SAP Milestone Usage set when value exist.
·
Activity Code: SAP Transfer – Optional (Set value to “No” if you do not want to transfer Activity to SAP PS)
·
12 character long Milestone Number.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
41
SAP
Primavera
Activity
Start Milestone
WBS Milestone
SAP PS Object Information:
·
·
BAPI: BAPI_PROJECT_MAINTAIN,
TABLE: I_ WBS_MILESTONE, I_MILESTONE_TABLE_UPDATE
Primavera Business Object Information:
·
·
Activity
Activity Code
Supported CRUD Action:
·
Update
No.
Primavera - Activity
SAP Project System
Condition If any
1.
Activity Id
MILESTONE_NUMBER
o Mandatory Field
o 12 character long numeric number.
2.
WBS Code
WBS_ELEMENT
o Mandatory Field
3.
Name
DESCRIPTION
o This field is updatable.
4.
ActualStartDate
ACTUAL_DATE
o This field is updatable.
5.
ActualStartDate
ACTUAL_TIME
o This field is updatable.
6.
PlannedStartDate
FIXED_MILESTONE_DATE_BASIC
o This field is updatable if
OFFSET_START_END_INDICATOR or
LATEST_DATES_INDICATOR is NOT
marked.
7.
ActivityCode: SAP Invoice
Percentage
INVOICE_PERCENTAGE
o This field is updatable.
8.
ActivityCode: SAP Object
-
o Set as ‘WBS_MILESTONE’
o This code is used to identify whether it
is WBS Milestone or Activity Milestone
in SAP PS.
9.
3.9.2
ActivityCode: SAP Usage
MILESTONE_USAGE
o This field is updatable.
SAP Activity Milestone Mapping
WBS Milestone in SAP PS is mapped to the Start Milestone Activity in Primavera. It is distinguished from an Activity Milestone by
the entry in the SAP Object Activity Code Field. Value of SAP Object Activity Code field for Activity Milestone is
“ACTIVITY_MILESTONE”.
Activity Element can be transferred from Primavera to SAP if following conditions are met:
·
·
Activity Code SAP Object : value = ”WBS_MILESTONE”
Activity Code: SAP Milestone Usage set when value exist.
·
Activity Code: SAP Transfer – Optional (Set value to “No” if you do not want to transfer Activity to SAP PS)
·
12 character long Milestone Number.
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 42
SAP
Primavera
Activity
Start Milestone
Activity Milestone
SAP PS Object Information:
·
·
BAPI: BAPI_PROJECT_MAINTAIN,
TABLE: I_ ACTIVITY_MILESTONE, I_ACTIVITY_TABLE_UPDATE
Primavera Business Object Information:
·
·
Activity
Activity Code
No.
Primavera - Activity
SAP Project SYstem
Condition If any
10.
Activity Id
MILESTONE_NUMBER
o Mandatory Field
o 12 character long numeric number.
11.
ActivityCode: SAP
Network
NETWORK
o Mandatory Field
12.
ActivityCode: SAP Activity
ACTIVITY
o Mandatory Field
13.
Name
DESCRIPTION
o This field is updatable.
14.
ActualStartDate
ACTUAL_DATE
o This field is updatable.
15.
ActualStartDate
ACTUAL_TIME
o Set as Fixed Duration and Units/time
16.
PlannedStartDate
FIXED_MILESTONE_DATE_BASIC
o This field is updatable if
OFFSET_START_END_INDICATOR or
LATEST_DATES_INDICATOR is NOT
marked.
17.
ActivityCode: SAP Invoice
Percentage
INVOICE_PERCENTAGE
o Set as ‘Start On or After’.
18.
ActivityCode: SAP Object
-
o Set as ‘ACTIVITY_MILESTONE’
o This code is used to identify whether it
is WBS Milestone or Activity Milestone
in SAP PS.
19.
ActivityCode: SAP Usage
MILESTONE_USAGE
This field is updatable.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
43
www.sap.com/contactsap
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
CUSTOMER
© 2016 SAP AG. All rights reserved. 44
Material Number
© 2016 SAP AG or an SAP affiliate company. All rights reserved.
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.
CUSTOMER
SAP Project System - Oracle Primavera P6 EPPM Sample Integration Solution(SIS)
© 2016 SAP AG. All rights reserved.
45