User Manual for P6 to SAP Interface

User Manual
1
P6 To SAP Interface - Table of Contents
Requirements to Integrate Primavera Projects in SAP

SAP Scenario
P6 Project minimum requirements to integrate into SAP
P6 Adjustments suitable for SAP
P6 SAP Interface assumptions
P6 SAP Interface Features

Product Logon
Product Usage in conjunction with P6
P6 SAP Dashboard
Project Control Department ( PCON / SIPC )

Selecting OBS to filter EPS Job nodes
Locating P6 Project ID within EPS
Viewing Activity Codes within the P6 Project selected
Selecting Activity Code as WBS aligned with CBS in SAP to be exported
Page 2 2
P6 To SAP Interface - Table of Contents

Selecting Activity Code as Procurement Step to be exported in SAP
Selecting Optional SAP Branch Code
Choosing the Set of Dates (Basic or Forecast)
Task Dependent Only Flag meaning
Running the Export to SAP
Files Produced by Product
Viewing Log after Export
P6 SAP Technical Specification

Page 3 3
SAP Scenario
SAP element that identifies the activities is called Network.

In a network, each activity (A) has a max 4 digits limitation as ID field, that is each activity has a
maximum of 4 chars/numbers defined (i.e. A010, A020, et..)

A
Page 4 4
SAP Scenario
Each SAP network is linked to a Project WBS = CBS through the field Project Def. (B) in the assignment
folder of network header data.
In the example below network N032154 (C) is linked to Project 032154 (D) that has a specific WBS =
CBS.
D
C

B
Page 5 5
SAP Scenario
WBS Element is the key field through which activities dates (Basic and/or Forecast, Early and/or Late)
in SAP network (E) are summarized in the corresponding Project WBS dates (F).

F
Page 6 6
SAP Scenario
Moreover, for each activity in the network is available a SAIPEM code (Procurement Step) that
identifies procurement element part of a sequence of homogeneous activities in order to manage a
specific object.
In the sample the activity A020 – CATALYST:P.O. has the code value ORD (G) that means Purchase
Order, to identify that the activity is related to the Order of the object CATALYST.
Obviously the P.O. comes after other activities part of the sequence like the Purchase Requisition
(RDA) or the Bidding or the Technical Evaluation.

G
Page 7 7
SAP Scenario
Here follows a list for the available SAP Procurement Step Code Values, with description both in Italian
& English
Code Italian Description English Description
APP - APPROVAZIONE CLIENTE CLIENT APPROVAL

ARR - ARRIVO IN CANTIERE SITE ARRIVAL
CGA - CONCLUSIONE GARA TENDER CLOSING
COL - COLLAUDO FINAL TEST

COSTR- COSTRUZIONE CONSTRUCTION
ENG - INGEGNERIA ENGINEERING
FOR - FORNITURA SUPPLY
ORD - ORDINE ORDER
PT - PARERE TECNICO TECHNICAL EVALUATION
RDA - RICHIESTA D'APPROVVIGIONAMENTO REQUEST OF SUPPLY
RDO - RICHIESTA D'ORDINE REQUEST OF ORDER
TAB - TABULAZIONE OFFERTA TECHNICAL BID
TRA - TRASPORTO (ARR. MEZZO PRINCIPALE) TRANSPORT
Page 8 8
P6 Project minimum requirements to integrate into SAP
To integrate P6 project in SAP, the following minimum requirements must be satisfied:

 Activity ID to be exported into SAP must be 4 digits made.
 An Activity Flat Code As Project (20 chars) must be defined to identify WBS/CBS in SAP
 An Activity Flat Code As Project (5 chars) must be defined to identify Procurement Step for each
activity
 Activity Code value for each activity in point 2 must exist into SAP WBS/CBS Project structure.
 Activity Code values for each activity in point 3 must cannot differ from list values explained in slide 7

1
Page 9 9
P6 Project minimum requirements to integrate into SAP
Here following the Activity Flat Code As Project about SAP WBS/CBS (1) and SAP Procurement Step
(2).
1 2

Page 10 10
P6 Adjustments suitable for SAP
In this chapter, are suggested some P6 actions in order to bypass certain limitations coming from SAP.
Activity ID 4 digits made – About this SAP limitation, you can proceed with the following steps:
1. If you want to maintain original P6 Activity IDs (A), you can save them into a User Defined
Field, using a specific Global Change P6 feature (B). (Optional)
2. You can renumber Activity IDs using a base of 4 digits and auto numbering feature of P6 (C).

A
Page 11 11
Here following the details about the Global Change (A) specification in order to store the original
Activity ID with more then 4 digits to preserve it into a User Defined Field (UDF) already available
defined as “GL – Activity ID” (B).
In the Global Change specification, is defined ‘where’ row (C) for selecting all Activities in your project
and a ‘then’ row (D) where you set the UDF “GL – Activity ID” with the content of Activity ID for each
activity.

B
A C
Page 12 12
After storing original P6 Activity IDs in your schedule, you have to renumber all activities involved in
SAP transfer with a new coding definition 4 digits long, suitable for SAP.
This can be done, selecting all activities involved in auto numbering (A) and then, right clicking the
mouse and selecting related feature “Renumbering Activity IDs” (B).

B
Page 13 13
When you launch “Renumbering Activity IDs” feature (A) you’ll be prompted to decide which kind of
auto numbering to realize.
We suggest to choose a letter Prefix (ex. “A”) and a Suffix numeric base (like 100 for ex.) and an
increment value (ex. 1), this to obtain a series of Activity IDs with 4 digits starting from A100 and going
on with A101, A102, et..

B
Page 14 14
In case that the number of activities is greater than 1000, you are obliged to split the renumbering in
different minor groups less than 1000, giving a different Prefix for each group (A), to guarantee a 4
digits long using a different letter as prefix.

A
Page 15 15
P6 SAP Interface assumptions
Here following some assumptions about product to be considered:
 Interface between Oracle Primavera Professional Project Management (P6) and SAP doesn’t
includes subprojects, ‘cause in P6 each subproject becomes a project; so you must handle multiple
projects into one unique project in order to transfer data to SAP.
 Oracle P6 – SAP Integration has been developed with two software components (versus Oracle
Primavera and versus SAP), so it does not include deleting activities operations in both
environments.
 Activity deletion in SAP network and Oracle P6 project is executed in a separate way and is due to
user.

 Interface between Oracle P6 and SAP doesn’t include creation of a SAP network from P6, or a
creation of a P6 Project from SAP.
 Creation functions, regarding project and network have to be executed in a separate way, using
different features inside two products (Transaction CN21 – Create Network in SAP e File New
Project in Oracle P6).
 Interface is one-way, from P6 to SAP and not vice versa, ‘cause SAP is not the official schedule
engine.
Page 16 11
Product Logon
 When you launch the product, 1st screen is related to credentials to be used to logon.
 Credentials elements are exactly the same as the one used in P6 access logon.
 You have to insert the same Login Name as P6 (your SAIPEM account, i.e. SA045673) (A) and the
password previously defined in P6 (B).
 An important recommendation is that you must execute a summarize project feature in P6 (C)
before running the interface.

C
Page 17 12
Product Usage in conjunction with P6
P6 SAP Interface can be run even if you’ve left open the P6 project in P6, just remind to press F5
(Data Refresh) (C) if you make changes on project before using the interface.

C
Page 18 13
P6 SAP Dashboard
Main dialog window is divided into 5 different areas:

 On the left at the top, the space showing the P6 EPS structure (A), at the bottom general data of a
selected project in the EPS (B).
 On the right at the top, the space dedicated to Activity Codes list (C), according the selected project
and at the bottom (D) the selected parameters suitable to export in SAP.
 Finally on the right side you can find all command buttons to execute operations (E).
 Except for the command buttons area (E), all other areas are sizeable using area separators
between them and scrollable using scroll bars.

A
C
E
D
B
Page 19 14
Selecting OBS to filter EPS Job nodes
First of all, you have to press OBS command button to select OBS element to which the project is
related to (A), then once selected an OBS element (B), it will be shown the EPS structure with the set
of projects linked to that OBS element (C).

C
Page 20 15
Locating P6 Project ID within EPS
Once available the EPS structure with the list of P6 projects, you can select the desired one to start
the export process to SAP, just clicking on the row corresponding to the project (light blue row in the
picture) (A). You can also use Ctrl + F (Find) feature to search a specific project, giving the project ID
or description or part of them (B).

B
Page 21 16
Viewing Activity Codes within the P6 Project selected
After selected the desired P6 project, you must click on View command button (A) to make available
the list of Activity Codes as Project defined for that project (B).
Clicking on each plus symbol of the desired Activity Code As Project will shown all the code values
defined for that Activity Code As Project (C).

C
Page 22 17
Selecting Activity Code as WBS aligned with CBS in SAP to be exported
Having Activity Code list available (A), user must select the one that is concerned to WBS/CBS in SAP
(B), in the case of below picture P6SAP_WBS_(PRJ) and right click being on the row selected it will
appear another dialog in order to choose the “Set as WBS Code” function (C).

B
Page 23 18
After set the previously selected Activity Code As Project as the WBS/CBS Code for SAP (C), you’ll
see a green alert beside WBS Code in the bottom part with the Activity Code As Project Name (D).
You can reset your selection anytime, just position the mouse cursor on the row about the code (D)
and right click the mouse choosing the option delete (E).

C D
D E
Page 24 19
Selecting Activity Code as Procurement Step to be exported in SAP
Having Activity Code list available (A), user must select the one that is concerned to Procurement Step
in SAP (B), in the case of below picture P6SAP_SAP ACTION CODE and right click being on the row
selected it will appear another dialog in order to choose the “Set as Procurement Step” function (C).

C
Page 25 20
After set the previously selected Activity Code As Project as the Procurement Step for SAP (C), you’ll
see a green alert beside Procurement Step in the bottom part with the Activity Code As Project Name
(D).
You can reset your selection anytime, just position the mouse cursor on the row about the code (D)
and right click the mouse choosing the option delete (E).

C
D E
Page 26 21
Selecting Optional SAP Branch Code
After you have set the other Activity Codes mandatory for SAP, you can set an optional Branch Code,
only if your project in SAP is related to a SAP Branch.
When you locate on the SAP Branch Code row (A), you can chose one SAP Branch from the list of
ones available (B).

Once selected the SAP Branch Code from the list (B), you have the green alert also for this parameter
(C); if you do not compile this parameter the alter remains yellow, ‘cause It’s optional.
You can reset your selection anytime, just position the mouse cursor on the row about the SAP Branch
code (C) and right click the mouse choosing the option delete (D).
C D
Page 27 22
Choosing the Set of Dates (Basic or Forecast)
Another parameter mandatory is the Dates parameter (1), set as per default with the “(C) Cardine /
Basic” value (2).
It means that you are exporting Basic or Baseline or Target Dates of your schedule from P6 to SAP.
If you want to switch to Forecast or Current Dates of your schedule to be exported, you have to
choose the value “(P) Previsione / Forecast” from the list (3).

1 2
Page 28 23
Task Dependent Only Flag meaning
This parameter (A) means that the product will filter only activities that are defined as “task dependent”
in P6.
This filter is independent from any others developed in P6.
All other kind of activities, like milestones, WBS, resource dependent and LOE will be discarded.
You cannot unmark this flag parameter.

A
Page 29 24
Running the Export to SAP
Once you have set all parameters suitable for export, you can click on Run command button (A) to
start data export process of the schedule previously selected.

Page 30 25
Running the Export to SAP
When data export process ends, you’ll see a popup window showing that export files have been
successfully created (A).
Export files are created in C:\TEMP directory of local PC on which is executed the interface.

A
Page 31 26
Files Produced by Product
After the completion of export process ascii files created in your local drive c:\temp directory, have the
extension P2S that means “Primavera to SAP”.
Here follows file list:
1. XXXXGEN.P2S – General Schedule Data (where XXXX is the P6 project ID)
2. XXXXATT.P2S – Schedule Activities (where XXXX is the P6 project ID)
3. XXXXLEG.P2S – Schedule Links between Activities (where XXXX is the P6 project ID)
4. XXXXWBS.P2S – Schedule WBS Structure (where XXXX is the P6 project ID)

4
3
2
1
Page 32 27
Viewing Log after Export
Each time you run the export, you can view the log file to check if there are some eventual errors /
warnings.
Log file is readable clicking on View Log command button (A).

A
Page 33 28
Viewing Log after Export
Here following a sample of log file in which there are a few errors conditions, like the Activity ID length
different then 4 chars (A) or Procurement Step code not included in SAP Procurement Step list of
values (B) or Predecessor / Successor ID different then 4 chars (C).
If log file doesn’t contain errors / warnings, it means that the export has been successfully completed
correctly.

A
Page 34 29
You can find details on principles of development about this product in our Project Control Portal in the
related document “P6SAP_Technical_Specification.pdf” of P6SAP section under Primavera
directory.

Page 35 30

User Manual for P6 to SAP Interface

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

User Manual for P6 to SAP Interface

Загружено:

Авторское право:

Доступные форматы

User Manual

Requirements to Integrate Primavera Projects in SAP

P6 SAP Interface Features

Project Control Department ( PCON / SIPC )

P6 SAP Interface Features

P6 SAP Technical Specification

Project Control Department ( PCON / SIPC )

SAP element that identifies the activities is called Network.

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Code Italian Description English Description

APP - APPROVAZIONE CLIENTE CLIENT APPROVAL

Project Control Department ( PCON / SIPC )

To integrate P6 project in SAP, the following minimum requirements must be satisfied:

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Main dialog window is divided into 5 different areas:

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Project Control Department ( PCON / SIPC )

Вам также может понравиться