Coon nn neecct tiingg EE--BBuussiinee sss SSuuiitee 155 RR22 · PDF fileCoon nn neecct tiingg EE--BBuussiinee sss SSuuiitee 155 RR22 ... Setting Up EBS Connectivity through Web Services

CCoonnnneeccttiinngg EE--BBuussiinneessss SSuuiittee

1155 RR22

MMaayy 22001166

3

Contents

Overview ................................................................................................ 7

Setting Up the Integration Environment .......................................................... 9

Prerequisites for Connecting with P6 ................................................................. 9

Post-Installation Tasks .................................................................................. 9

Configuring Gateway Domain for P6 Event Notification ................................... 10

Enabling Encryption Between Primavera Gateway and P6 Adapter ..................... 12

Setting Up EBS Connectivity through Web Services ........................................ 13

Extending WebLogic Domain for Web Services Connectivity ............... 14

Setting up EBS Connectivity through RMI .................................................... 15

Configuring the Gateway User Interface .................................................... 15

Configuring Gateway Settings ................................................... 15

Adding an EBS Application Deployment Connection ......................... 16

Adding an EnterpriseTrack Deployment Connection ......................... 18

Adding a P6 Deployment Connection........................................... 19

Defining Business Flows ............................................................................. 21

Creating New Business Flows ......................................................................... 21

Using Business Flows Delivered in Gateway ........................................................ 22

Connecting with P6 EPPM ............................................................................. 22

Master Data Flow Type ......................................................................... 22

Business Objects Supported in Master Data Flow ............................ 22

Field Mapping Templates for Master Data Business Objects ................ 23

Setting Provider-Specific Parameters .......................................... 23

Project Data Flow Type ........................................................................ 24

Business Objects Supported in Project Data Flow ............................ 25

Field Mapping Templates for Project Data Business Objects ............... 26

Setting Provider- Specific Parameters ......................................... 28

Connecting with Instantis EnterpriseTrack ......................................................... 31

Project Data Flow Type ........................................................................ 32

Business Objects Supported in Project Data Flow ............................ 32

Field Mapping Templates for Project Data Business Objects ............... 33

Setting Provider-Specific Parameters .......................................... 33

Defining Synchronizations .......................................................................... 37

Master Data Synchronization ......................................................................... 37

Project Data Synchronizations ....................................................................... 37

Creating New Synchronization Jobs ................................................................. 39

Using Synchronizations Delivered in Gateway ..................................................... 39

Connecting E-Business Suite

4

Transferring Data between Applications: Example ............................................. 40

Appendix A: About Flow Steps ..................................................................... 43

Define the Flow Steps in a Flow ..................................................................... 43

Flow Sequence When Using Master Data .................................................... 44

Flow Sequence When Using Project Data ................................................... 44

Flow Sequence When Using the Compare Step ............................................. 45

Appendix B: Fields Supported in Mapping Templates .......................................... 47

Fields Supported with P6 EPPM ...................................................................... 47

Activity Mapping ................................................................................ 47

Activity Budget Field Mappings-Current ..................................................... 47

Activity budget Field Mappings- Original .................................................... 48

Activity Budget Field Mappings - Proposed .................................................. 48

Activity Relationship Fields ................................................................... 49

Assignment Actual Updates .................................................................... 49

Assignment Budget Field Mappings - Current ............................................... 49

Activity Budget Field Mappings - Original ................................................... 50

Activity Budget Field Mappings - Proposed .................................................. 50

Assignment Mapping ............................................................................ 51

Expense Category Fields ....................................................................... 51

Financial Period Fields ......................................................................... 51

Project Budget Field Mappings-Current ..................................................... 52

Project Budget Field Mappings - Original .................................................... 52

Project Budget Field Mappings - Proposed .................................................. 52

Project Header Mappings ...................................................................... 53

Resource Fields ................................................................................. 53

Resource Rates .................................................................................. 53

Role Fields ....................................................................................... 54

Role Rates ........................................................................................ 54

Update Actuals .................................................................................. 54

WBS Field Mapping .............................................................................. 55

WBS Budget Field Mappings - Current........................................................ 55

WBS Budget Field Mappings - Original ....................................................... 55

WBS Budget Field Mappings - Proposed ...................................................... 56

Fields Supported with Instantis EnterpriseTrack .................................................. 56

EnterpriseTrack Project Mapping ............................................................. 56

EnterpriseTrack ProjectFinance Mapping ................................................... 57

EnterpriseTrack ProjectFinanceElement Mapping ......................................... 57

Appendix C: P6 Objects Supported in Gateway for Events ................................... 57

For More Information ................................................................................ 59

Where to Get Documentation ........................................................................ 59

Contents

5

Where to Get Training ................................................................................ 63

Where to Get Support ................................................................................. 63

Documentation Accessibility ......................................................................... 64

Legal Notices .......................................................................................... 65

7

Primavera Gateway is an application that facilitates sharing and synchronizing project, resource, and other data between Primavera applications and enterprise applications. By using providers, which are used as a channel to connect with the corresponding software application, Primavera Gateway enables you to combine management and scheduling functionality of Primavera applications with other enterprise software. Providers can reside on either side of a data flow connecting a source application with a destination application.

Using Primavera Gateway, E-Business Suite data can be shared with the following Primavera applications:

P6 EPPM

Integrating E-Business Suite with P6 EPPM enables sharing master data and project data related to activities, resource assignments, and WBS.

Instantis EnterpriseTrack

Integrating E-Business Suite with Instantis EnterpriseTrack enables sharing project header and project finance related data. Primavera Gateway facilitates the data integration process.

Primavera Gateway facilitates the above integrations by delivering the following providers:

EBS provider

The EBS provider enables you to share data from E-Business Suite application.

P6 provider

The P6 provider enables you to share data from P6 EPPM application.

EnterpriseTrack provider /

The EnterpriseTrack provider enables you to share data with E-Business Suite application. For more details on setting up this integration, also see the Connecting with EnterpriseTrack guide.

IT professionals or administration personnel who are responsible for setting up the Primavera Gateway and scheduling jobs and synchronizations within your organization should use this guide. This guide describes how to setup the integration environments to enable data exchange with E-Business Suite.

Overview

9

This section describes the how to setup the integration environment in Gateway.

In This Section

Prerequisites for Connecting with P6 ......................................................................... 9 Post-Installation Tasks .............................................................................................. 9

Prerequisites for Connecting with P6

To set up an environment for data exchange through Primavera Gateway, download, install, and configure the following applications:

To connect with P6 EPPM, install:

E-Business Suite application

Install the database scripts for the EBS provider. For detailed instructions, see the EBSProviderR10\db folder of the EBS provider software download.

P6 EPPM application

P6 Adapter

Primavera Gateway application selecting the P6 and EBS providers

To use P6 Event Provider delivered in Gateway, event notification must be enabled in P6 as well as in Gateway. For more details, see the Using Events with P6 Guide. Ensure the following features are enabled in P6 EPPM:

Eventing is enabled

JMS Queue is used for messaging

Also enable event notification in Gateway. For more details, see Configuring Gateway Domain for P6 Event Notification (on page 10).

For detailed installation instructions, see the Installation and Configuration guide for each product. For specific supported software versions, see the Tested Configurations document for each application.

Post-Installation Tasks

After completing all the prerequisites for setting up the integration environment, perform the following procedures outlined in this section.

Setting Up the Integration Environment


10

Configuring Gateway Domain for P6 Event Notification

If you choose to use the P6 Event provider delivered in Gateway, then configure the Gateway WebLogic domain to consume P6 event messages as follows:

1) Ensure the Primavera Gateway domain is running.

2) Log in to the WebLogic Administration Server Console for the Gateway domain:

a. In a browser, enter the following location:

http://<hostname>:<port>/console

Where, hostname and port is the hostname and port of your Primavera Gateway domain in WebLogic. The default port is 7001.

b. Enter the WebLogic administrator user name and password.

3) In the Change Center pane, select Lock and Edit before you make any changes to the domain.

4) Create a JMS server as follows:

a. In the Domain Structure pane, expand Services, Messaging, JMS Servers.

b. In the Summary of JMS Servers pane, select New.

Note: Select Next on each screen to advance to the next step.

1. Enter a Name for the JMS Server. For example, Gateway JMS Server.

2. Select Create a New Store.

3. Select Type as File Store from the drop-down.

4. Enter a Name for the File Store.

5. Select the Target for the file store:

For Admin server, select AdminServer.

For Managed server, select GatewayCluster.

6. Enter the Directory or the physical location of the file store. For example, c:\JMSFilestore.

7. Select OK.

8. Select Finish.

5) Create a JMS module as follows:

a. In the Domain Structure pane, expand Services, Messaging, and JMS Modules

b. In the Summary of JMS Modules pane, select New.

1. Enter a Name for the JMS module.

2. Depending on your configuration, select the Target for the file store, as AdminServer, or GatewayCluster for a managed server.

3. Select Finish.

6) Create a Foreign Server in the JMS module as follows:

a. In the Domain Structure pane, expand Services, Messaging, and JMS Modules.

b. Select the JMS module created in step 5.

c. On the Configuration tab of the Settings for <JMS Module> pane, select New.


11

d. Select Foreign Server.

e. Enter a Name for the foreign server.

f. Depending on the configuration, select the Target as AdminServer, or gatewayCluster for a Managed server.

g. Select Advanced Targeting and then select Create a New SubDeployment.

h. Enter a name for the subdeployment and then select OK.

i. Select the created subdeployment from the drop-down.

j. Depending on your configuration, select the Target as AdminServer, or gatewayCluster for a Managed server, and the JMS server created in step 4.

k. Select Finish.

l. Select Save to save the foreign server with a subdeployment.

7) Enter configuration settings for the foreign server created as follows:

a. Select the foreign server created in step 6.

b. In the Settings for <Foreign Server Name> pane, select the Configuration tab, and then the General tab.

c. Select the new foreign server created and enter values for the following configuration settings:

In the JNDI Initial Context Factory field, retain the default value.

In the JNDI Connection URL field, enter the URL to the P6 EPPM domain in the format: t3://<P6_EPPM_host>:<port>/

In the JNDI Properties Credential field, enter the P6 EPPM WebLogic domain password.

In the Confirm JNDI Properties Credential field, reconfirm the entered password.

In the JNDI Properties field, enter the P6 EPPM WebLogic domain user name in the following format: java.naming.security.principal=<P6 EPPM WebLogic domain user name>

Select Save. The newly created foreign server displays in the Configuration tab.

d. Create a connection factory for the foreign server as follows:

1. In the Settings for <Foreign Server Name> pane, select the Configuration tab, and then the Connection Factories tab.

2. Select New.

3. Enter a Name for the connection factory.

4. Enter the Local JNDI Name. For example, jms/newCF.

Note: Make a note of the value entered in this field. You will need to enter this value to set up an event provider to a P6 Application deployment.

5. Enter the JNDI name of the P6 EPPM Connection Factory as the Remote JNDI Name.

6. Select OK.

e. Create a destination for the foreign server as follows:

1. In the Settings for <Foreign Server Name> pane, select the Configuration tab, and then the Destinations tab.


12

2. Select New.

3. Enter a name for the foreign destination.

4. In the Local JNDI Name, enter the name of the JMS queue used by Gateway. For example, jms/newGWQueue.

Note: Make a note of the value entered in this field. You will need to enter this value to set up an event provider to a P6 Application deployment.

5. Enter the name of the P6 EPPM JMS queue as the Remote JNDI Name. For example, jms/P6Queue.

6. Select OK.

8) In the Change Center pane, select Activate Changes to enforce all the changes made to the domain.

Enabling Encryption Between Primavera Gateway and P6 Adapter

To ensure all requests and responses between Primavera Gateway and P6 Adapter are encrypted:

1) Create a Keystore file as follows:

a. Create a folder, for example, C:\keystore.

b. Use the Java keytool genkey command to create a keystore with the private key:

From the command line, execute:

keytool -genkey -alias <alias_name> -keyalg RSA -sigalg SHA1withRSA

-keypass <keyPassword> -storepass <storePassword> -keystore <keystore

file location>

Where:

<alias> is the key alias

<keyPassword> is the password of the private key

<storePassword> is the password of the keystore

For example:

keytool -genkey -alias myAlias -keyalg RSA -sigalg SHA1withRSA

-keypass myPassword -storepass myPassword -keystore

c:\keystore\keystore.jks

c. Enter information for each of the following questions:

What is your first and last name?

Enter the Gateway host name.

What is the name of your organization?

What is the name of your city or locality?

What is the name of your state or province?

What is the two-letter country code for this unit? For example, US.

Is CN=<Gateway host name>, OU=<organization unit name>, O=<organization

name>, L=<location>, ST=<state code>, C=<country code> correct? Enter Y or N.


13

Note: If P6Adapter is deployed on other than a Gateway machine, then

copy the keystore folder with keystore.jks to the P6Adapter machine.

2) In the Gateway user interface, select the Configuration tab and enter deployment information for P6. For more details, see Adding a P6 Deployment Connection (on page 19).

3) In P6 EPPM administration application:

a. Enter the keystore information that was entered in the keystore file. The values must be identical.

b. Modify the message protection node setting as follows:

Set the Require Timestamp value as True.

Set the Require Digital Signature for Incoming Messages value as True.

Set the Require Encryption for Incoming Messages value as True.

In the KeyStore Type field, enter JKS.

In the File Location field, enter the location of the .jks file. For example, c:\keystore\keystore.jks.

In the KeyStore Password field, enter the password for the keystore file provided in keytool command.

In the Private Key Alias field, enter the alias name provided in keytool command.

In the Private Key Password field, enter the private key password for the keystore file provided in the keytool command.

Set the Encrypt Response value as True.

4) After encryption is set, restart the P6 adapter domain in WebLogic.

Setting Up EBS Connectivity through Web Services

To set up EBS connectivity through Web Services from Primavera Gateway:

1) Depending on the EBS release, setup the integrated SOA Gateway on EBS:

For EBS 12.1.3 see Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12 (Doc ID 556540.1).

For EBS 12.2.4 see Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID 1311068.1).

Note: SOA connectivity to EBS through webservices supports Username Token and SAML (sender vouches) security policies as required by EBS integrated SOA gateway setup.

2) Apply the database schema using the database setup documentation provided with the EBS provider database code.

3) Manually generate and deploy the webservices wsdl for the EBS APIs. For more details, see Appendix A - Setting up SOA Web Services in the MD.120 P6_EBS_Integration guide delivered with the EBS provider in the media pack. Ensure that services generated and deployed using EBS Integrated SOA gateway have synchronous interfaces only. The current release of EBS provider does not support connecting to EBS via asynchronous service calls.


14

Extending WebLogic Domain for Web Services Connectivity

Extend the WebLogic domain with JRF and OWSM for Primavera Gateway to connect to EBS using web services through SOA Gateway as follows:

1) Open a terminal window and run the WebLogic configuration utility:

On Windows: cd <WEBLOGIC_HOME>\wls_server_10.3\common/bin

run config.bat

On Linux and Solaris: cd <WEBLOGIC_HOME>/wls_server_10.3/common/bin

./config.sh

2) On the Welcome screen, select Extend an existing WebLogic domain, select Next.

Note: Select Next to advance to the next screen.

3) On the Select a Weblogic Domain Directory screen, select the existing Gateway domain. By default, displays PrimaveraGateway.

4) On the Select Extension Source screen, select the following:

On WebLogic 12c, select:

Oracle Enterprise Manager

Oracle WSM Policy Manager

Oracle JRF

On WebLogic 11g, select:

Oracle WSM Policy Manager

Oracle JRF

5) On the Specify Domain Name screen, select Next.

6) On the JDBC Component Schema screen, select the OWSM MDS Schema and review the following information:

Vendor: Oracle

Driver: Oracle’s Driver (Thin) for Service Connections

Version:Enter the Oracle version number

Schema Owner: The owner of the OWSM MDS Schema.

Schema Password: The password for the schema.

DBMS/Service: The associated DBMS/ Service name

Host Name: The server name for the OWSM schema.

Port: The port number for the server. By default, it is 1521.

7) On the JDBC Component Schema screen, if the connection test passes, select Next.

8) On the Select Optional Configuration, select Next.

9) On the Configuration Summary screen, select Extend.

10) When complete, select Done.

Note: When you extend the domain the Dname option must be added back.


15

Setting up EBS Connectivity through RMI

To set up EBS connectivity through RMI from Primavera Gateway:

1) Generate a dbc (db connectivity) file in EBS specific to the Primavera Gateway IP.

For detailed instructions refer to the following topics in the Oracle E-Business Suite Software Development Kit for Java (includes AppsDataSource, Java Authentication and Authorization Service, session management) Readme: Patch 13882058 (Doc ID 974949.1) on Oracle Support:

Register the External Node and Generate the Desktop DBC File

Set Up Necessary Oracle E-Business Suite Users

2) Copy the generated dbc file from EBS to a Gateway server directory. Make a note of the Gateway server directory name and location. You will need this when adding an EBS deployment in the Gateway user interface.

Configuring the Gateway User Interface

Based on the application you plan to integrate EBS data with, configure Gateway and specify the connectivity to the corresponding applications.

Configuring Gateway Settings

Use the Settings dialog box to configure Primavera Gateway settings such as the Help location or whether to create new code values during synchronization. The settings available in this dialog box may vary depending on the specific providers Primavera Gateway is currently using.

The following settings must be configured for a Primavera Gateway deployment.

To configure the settings:

1) Select Settings and select Settings.

2) Update the settings as necessary and select Save when finished.

On the General tab:

Help URL: The Oracle Technology Network (OTN) Help location is http://docs.oracle.com/cd/E63838_01/help/en/index.html. If you deployed the local Help, enter the default Help URL location as: http://<hostname>:<port>/gatewayhelp.

Maximum number of job logs to display: Enter a value to control the number of logs displayed on the Monitoring page.

Maximum wait time for the parallel load/convert steps to complete (in minutes): Enter the number of minutes after which a synchronization job process is to be timed out. By default, the duration is set to 30 minutes. The job status of a timed-out synchronization is set to Failed.

Maximum concurrent jobs in a node: Enter the maximum number of jobs that can be executed concurrently at a node.

Job Polling Interval (in seconds): Enter the wait time interval in seconds to check the database if there are new jobs to run.

If you choose to integrate with P6, enter the following information on the P6 tab:


16

Create new resource code values during synchronization to P6: Select this option to enable the creation of new resource code values in the P6 EPPM resource code dictionary if these values do not already exist.

Create new project code values during synchronization to P6: Select this option to enable the creation of new project code values in the P6 EPPM project code dictionary if these values do not already exist.

Create new activity code values during synchronization to P6: Select this option to enable the creation of new global activity code values in the P6 EPPM activity code dictionary if these values do not already exist.

Include time zone when exporting from P6: Select this option to export P6 server time zone information along with P6 date and time fields. By default, this option is not selected, except for spread interval data in P6.

Note: This time zone setting applies only for a P6 - Prime integration.

Update activity resource assignments when assigned UDF values match: Enter the UDF code value that is assigned to resource assignments which you want to update during a synchronization. Use this to update the resource assignment with the matching UDF value when the assignment exists multiple times on an activity.

Maximum wait time for the summarizer to complete (in seconds): Enter the amount of time in seconds to wait for the summarizer to complete before a warning is given.

On the Mail Configuration tab:

SMTP Server: Enter the SMTP server address of your email server.

Port Number: Enter the port number of your email server.

Email Security: Select the applicable email security type.

Email Address: Enter the email address for the user who set up Primavera Gateway.

Authorized User: Enter the user name for this email account.

Password: Enter the password for the authorized user.

Bounce Email Address: Enter an alternate email address to be used if mail fails to be delivered to the first email address.

Adding an EBS Application Deployment Connection

To move data between applications, you must first add application deployment connections for E-Business Suite and P6 EPPM so Primavera Gateway knows where to get and send information.

To add an application deployment connection you must specify the Endpoint URL for each application:

1) Enter the Primavera Gateway URL in the format:

http://<host name>:<port number>/gateway

Where, <host name> and <port number> should match those of your Primavera Gateway domain.

2) Login to Primavera Gateway with administration credentials.

3) Select Configuration.


17

4) Select Deployments.

5) Select Add to invoke the Add Deployment wizard.

6) On the General tab, name the deployment and select Next.

7) On the Deployment tab, set up EBS connectivity from Gateway choosing any of the three methods listed below:

To connect Primavera Gateway with EBS using JDBC:

EBS Database JDBC Connect String: Enter the JDBC connect string for the EBS database.

EBS Database User Name: Enter the name of the EBS database administrator.

EBS Database Password: Enter the password of the EBS database administrator.

To connect Primavera Gateway with EBS using RMI:

Enable RMI Connection to EBS: Set the value as True.

EBS Application User Name for RMI Connection: Enter the name of user having RMI connection in EBS.

EBS Application Password for RMI Connection Enter the password of the user having RMI connection in EBS.

DBC file location on Gateway server for RMI Connection: Enter the location of the dbc file on the Gateway server that was generated using the procedure Setting up EBS Connectivity through RMI (on page 15).

To connect Primavera Gateway with EBS using web services through SOA Gateway:

Enable Web Service Connection to EBS: Set the value as True.

Version of Oracle EBS: Enter the database version as 12.1.3 or 12.2..

EBS Web Service Host Enter the web service host address in the following formats:

For EBS 12.1.3: http://<server:port>/webservices/SOAProvider/plsql/xpa_validate_objects_pkg/?wsdl

For EBS 12.2: http://<server:port>/soa-infra/services/default/<DBSID>_PLSQL_XPA_VALIDATE_OBJECTS_PKG/XPA_VALIDATE_OBJECTS_PKG_Service?wsdl

EBS Web Service User Name: Enter the name of the EBS Web Services user.

EBS Web Service Password: Enter the password of the EBS Web Services user.

EBS Web Service NLS Language: Enter the NLS language used for Web Services.

EBS Web Service Organization ID Enter the organization ID using Web Services connection.

EBS Web Service Responsibility Application: Enter the name of the responsibility application.

EBS Web Service Responsibility: Enter the Responsibility key which uniquely identifies the Responsibility name.

Note: Use this field to specify user-defined values for a JDBC or a web

service connection when defining a business flow.

EBS Web Service Security Group: Enter the name of the Web Services security group.

To enable encryption when using SOA Web services:


18

Enable Encryption for Web Service Connection: Set the value as True.

Credential Key Enter the unique credential key to access the credential store framework that stores the public and private keys for the certificate required for the SAML sender to vouch security between Gateway and the EBS provider.

Keystore File Location: Enter or browse and select the keystore file location for the EBS Provider.

For more details on how to generate the keystore file, see Setting Up SAML Token Security for Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3 (Doc ID 1144313.1) or Setting Up SAML Token Security for Oracle E-Business Suite Integrated SOA Gateway Release 12.2 (Doc ID 1332262.1).

Server Public Key Alias: Enter the server public key alias name of the EBS server keystore that is stored in client keystore. The public key is used to encrypt the outgoing message from Gateway to EBS web services.

8) Select Test Connection ensure connectivity with Gateway.

9) Select Save.

Adding an EnterpriseTrack Deployment Connection

To move data between applications, Primavera Gateway needs to know where to get and send information. If you choose to integrate with Instantis EnterpriseTrack, add an application deployment connection for Oracle Instantis EnterpriseTrack by specifying an Endpoint URL as follows:




2) Login to Primavera Gateway with administration credentials.



5) Select Add.

6) Follow the steps in the Add Deployment wizard to name the deployment and set the following parameters:

EnterpriseTrack Login ID: Enter the login ID that has all the necessary permissions to update project attributes. Otherwise, project import may fail.

EnterpriseTrack Password: Enter the password of the EnterpriseTrack user.

EnterpriseTrack Login URL: Enter the URL for accessing the application in the format: http://<server_name>/SiteWand/Submission/<accountname>.

EnterpriseTrack Initiative: Enter a valid initiative to create or update a project.

Date Format: Enter a valid date format supported in EnterpriseTrack.

EnterpriseTrack Connector Debug Flag: Set the flag value to Y if you want to enable debugging generate a log file.

7) Select Test Connection ensure connectivity with Gateway.

8) Select Save.


19

Adding a P6 Deployment Connection

To move data between applications, Primavera Gateway needs to know where to get and send information. You set this up by adding application deployment connections by specifying an Endpoint URL for each application.

Add a P6 deployment connection as follows:




2) Log in to Primavera Gateway with administration credentials.



5) Select Add to invoke the Add Deployment wizard.

6) On the General tab, select P6 Provider, and name the deployment.

Note: Select Next on each screen to advance to the next step.

7) On the Deployment tab, set up P6 connectivity from Gateway:

User Name: Enter the name of the P6 administrator.

Password: Enter the case-sensitive password of the P6 administrator.

Endpoint: Enter the URL to connect to the P6 adapter in the format:

http:<host name>:<port>/p6adapter/services/SyncServiceV1

Authentication Type: Select SAML 2.0 or Username Token from the drop-down.

SAML 2.0 Token File: If you chose SAML 2.0 authentication, then browse or enter the location of the downloaded SAML 2.0 token XML file that is used by the P6 adapter for authentication.

P6 Database Instance ID: Enter the database instance ID associated with the P6 application.

Enable Encryption: If you want to enable encryption for the P6 adapter, select True and enter the following information:

Keystore File: Enter, or browse and locate the keystore file.

For more details on how to generate a keystore file and keystore password, see Enabling Encryption Between Primavera Gateway and P6 Adapter (on page 12).

Keystore Password: Enter the password for the keystore file.

Certificate Alias: Enter the certificate alias used for authentication.

P6 Currency: Enter the base currency for the P6 deployment.

8) (Optional) If you choose to synchronize P6 events on the Web using the delivered P6 Event provider, enter the following information in the Event Provider tab:


20

In the JMS Connection Factory field, enter the local JNDI name from the Connection Factory object created in Configuring Gateway Domain for P6 Event Notification (on page 10). The connection factory contains a set of configuration parameters to connect with the P6 event provider.

In the JMS Queue field, enter the local JNDI name of the JMS Queue used to send and receive messages on P6 events from the destination setup created in Configuring Gateway Domain for P6 Event Notification (on page 10).

9) Select Test Connection to ensure the connectivity with P6 is established.

10) Select Save.

21

To transfer data between applications, you first need to define business flows. These business flows will then be used to set up synchronization jobs in Gateway that execute the data transfer. For each business flow you must determine the following:

What data will move between application deployments?

What is the default role of each provider?

What common business objects exist between the applications?

You can either use the out-of-the-box business flows delivered in Gateway or create new business flows if these don't fit your needs. Both options are outlined in detail. You can create multiple business flows.

In This Section

Creating New Business Flows ................................................................................. 21 Using Business Flows Delivered in Gateway ........................................................... 22 Connecting with P6 EPPM ...................................................................................... 22 Connecting with Instantis EnterpriseTrack ............................................................... 31

Creating New Business Flows

Depending on the applications, and the flow types supported in an integration, to create a new business flow in Primavera Gateway:

1) In the navigation menu, select Flow Type and choose the Project Data or Master Data business flow type.

Select this flow type to transfer project data between any two applications or between two distinct deployments of the same application. For example, transfer project data from a P6 Testing environment to a P6 Production environment.

2) Select Business Flows.

3) Select Add.

4) Follow the Add Business Flow wizard to define which project data or master data will move between the applications. Select Save.

Tips

You can also edit an existing flow. To do so, select the flow you want to edit, select Edit, and move through the wizard to update the flow.

When you enter a name for the business flow, use a name that will help you remember the type and direction of information in this flow.

Defining Business Flows


22

Using Business Flows Delivered in Gateway

To edit an out-of-the-box business flow delivered in Primavera Gateway:

1) In the navigation menu, select Flow Type and choose the Project Data or Master Data flow type.

2) Select Business Flows.

3) Select Edit....

4) Follow the Edit Business Flow wizard to define which project data will move between the applications.

5) Select Save.

Tip

When you enter a name for the business flow, use a name that will help you remember the type and direction of information in this flow.

Connecting with P6 EPPM

For EBS integration with P6, the following flow types are supported:

Master Data Flow Type (on page 22)

Project Data Flow Type (on page 24)

This section describes the business flows, field mapping templates, and parameters delivered out-of-the-box in Primavera Gateway for exchanging data between E-Business Suite and P6 EPPM applications.

Master Data Flow Type

Use the Master Data flow type to transfer master data business objects from EBS to P6 identified in the Business Objects Supported in Master Data Flow (on page 22). The Synch EBS Master Data to P6 master data business flow is delivered out-of-the-box for a EBS - P6 integration in Gateway.

Business Objects Supported in Master Data Flow

The following business objects are supported between the P6 and EBS applications in the Master Data business flow. These business objects can be transferred using the field-mapping templates delivered in Gateway. To view a list of field-mapping templates provided in Gateway, see Field Mapping Templates for Master Data Business Objects (on page 23).

When EBS is the source provider, the following business objects are supported between P6 and EBS applications in the Master Data flow type:

EBS Source Business Objects Gateway Business Object

P6 Destination Business Object

ExpenseCategory ExpenseCategory ExpenseCategory


23



FinancialPeriod FinancialPeriod FinancialPeriod

Resource Resource Resource

ResourceRate ResourceRate ResourceRate

Role Role Role

RoleRate RoleRate RoleRate

Field Mapping Templates for Master Data Business Objects

The following table lists all field-mapping templates and the business flows that support each master data business object. Each business object can be supported by more than one field-mapping template. You can edit the delivered business flows to include or exclude business objects by selecting the corresponding field-mapping templates or also create your own if these templates don't fit your needs. For a detailed list of the fields mapped in each template, see Appendix B: Fields Supported in Mapping Templates (on page 47).

EBS Source Business Objects

Associated Field Mapping Templates

Used in ...

ExpenseCategory Expense Category Fields

FinancialPeriod Financial Period Fields

Resource Resource Fields Synch EBS Master Data to P6

ResourceRate Resource Rates

Role Role Fields

RoleRate Role Rates

Setting Provider-Specific Parameters

Based on the role of EBS and P6 providers and the data to be transferred in the business flow the following provider-specific parameters will display as either source or destination application parameters in the Add Business Flow wizard.

Users having the role of a Gateway administrator can access and view all the parameters listed below. Set the behavior of these parameters in the business flow by specifying the Attribute for each as any of the following values: Hidden, Optional, Read-only, or Required.


24

Note: Data identified by each parameter is processed by a flow step of the business flow. For more information on flow steps, see Appendix A: About Flow Steps (on page 43). All values specified in the filter parameters will be used in the Load step of the flow for loading data from

the providers designated as the source or the destination.

EBS Provider Application Parameters

When EBS is the source provider in the master data flow, set values and attributes for the following parameters:

Resource Lists (Required)

Use this setting to specify multiple Planning Resource Lists by name as comma-separated values.

Exclude Material Resources from Import (Optional)

Use this setting to determine if material resources are to be excluded when sending data from EBS.

P6 Provider Application Parameters

When P6 is the destination provider in the master data flow, set values and attributes for the following parameters:

Resource Destination

Use this setting to specify the location of the Resource objects imported into P6. This information is used in the Save step of the flow.

Calculate Cost from Units

Use this setting to determine whether to calculate costs from the units. This information is used in the Save step of the flow.

Auto Compute actuals

Select this setting if you want the actuals to be auto-computed in P6. This information is used in the Save step of the flow.

Role Destination

Use this setting to specify the location of the role objects imported into P6. This information is used in the Save step of the flow.

Save Data to P6 if there are errors

Use this setting to determine whether to save the imported data in P6 with errors.

Delete data that no longer exists in the source application?

Use this setting to determine whether data that no longer exists in the source application is to be deleted in the destination application. This parameter must be used in conjunction with the Compare flag selected in the Business Flow wizard.

Project Data Flow Type

Use the Project Data flow type to transfer project data business objects identified in the Business Objects Supported in Project Data Flow (on page 25). The following types of project data business flows are delivered for an EBS - P6 integration in Gateway:


25

Synch EBS Project(s) to P6

Synch P6 project(s) to EBS

Instantiate EBS Project(s) from P6

Each business flow uses one or more field-mapping templates that handle the data transfer of specific business objects and its corresponding fields. You can edit these delivered business flows or also create additional business flows and field-mapping templates to fit your needs. After creating new business flows or editing the above business flows you can create synchronization jobs that use the defined project data business flows to transfer project data. For more details, see Defining Synchronizations (on page 37).

Business Objects Supported in Project Data Flow

The following business objects are supported between EBS and P6 applications in the Project Data flow. These business objects can be transferred using the field-mapping templates delivered in Gateway. To view a list of field-mapping templates provided in Gateway, see Field Mapping Templates for Project Data Business Objects (on page 26)

When P6 is the source provider, the following business objects are supported between P6 and EBS applications in the Project Data flow type:

P6 Source Business Objects Gateway Business Object

EBS Destination Business Object

Project Project Project

WBS WBS WBS

Activity Activity Activity

ResourceAssignment ResourceAssignment ResourceAssignment

Relationship Relationship Relationship

When EBS is the source provider, the following business objects are supported between P6 and EBS applications in the Project Data flow type:



Activity Activity Activity


Relationship Relationship Relationship

Resource Resource Resource

ResourceAssignment ResourceAssignment ResourceAssignment

WBS WBS WBS


26

Field Mapping Templates for Project Data Business Objects

The following tables list all field-mapping templates and the business flows that support each project data business object. Each business object can be supported by more than one field-mapping template. You can edit the delivered business flows to include or exclude business objects by selecting the corresponding field-mapping templates or also create your own if these templates don't fit your needs. For a detailed list of the fields mapped in each template, see Appendix B: Fields Supported in Mapping Templates (on page 47).



Used in ...

Activity Activity Mapping Synch EBS Project(s) to P6 business flow

Activity Budget Field Mappings-Current

Update Actuals

Activity Budget Field Mappings-Original

Activity Budget Field Mappings-Proposed

Project Project Budget Field Mappings - Current

Project Budget Field Mappings - Original

Project Budget Field Mappings - Proposed

Project Header Mappings

Relationship Activity Relationship Fields

Resource Resource Fields

ResourceAssignment Assignment Mapping

Assignment Budget Field Mappings-Original

Assignment Budget Field Mappings-Current

Assignment Budget Field Mappings-Proposed

Assignment Actual Updates

WBS WBS Field Mapping

WBS Budget Field Mappings - Original


27



Used in ...

WBS Budget Field Mappings - Current

WBS Budget Field Mappings - Proposed

P6 Source Business Objects


Used in ...

Activity Activity Mapping the following business flows:

Instantiate EBS Project(s) from P6 business flow

Synch P6 Project(s) to EBS business flow



Activity Budget Field Mappings-Original

Activity Budget Field Mappings-Proposed

Project Project Header Mappings the following business flows:



Project Budget Field Mappings - Current




28

P6 Source Business Objects


Used in ...


Relationship Activity Relationship Fields the following business flows:



WBS WBS Field Mappings the following business flows:







Setting Provider- Specific Parameters

Based on the role of EBS and P6 providers and the data to be transferred in the business flow the following provider-specific parameters will display as either source or destination application parameters in the Add Business Flow wizard.



29




When EBS is the source provider in a project data flow, set values and attributes for the following parameters:

ERP Project Filter

Use this setting to identify and transfer ERP Project business objects from the source application. Enter multiple values for ImportProjectIds as comma-separated values. Select Add row to enter multiple ERP Project business objects.

Project Plan

Use this setting to specify the Project Plan. Options include, Work Plan and Financial Plan.

Plan Versions

Use this setting to select the plan version for transfer to P6. Options include: Current Working, Current Baselined, and Original.

Leaf Level Task as Activity

Use this setting to determine whether the activities can be transferred as leaf level tasks or top level tasks in EBS.

Create Material Resources Only

Use this setting to determine whether to create only material resources class or all resource classes from EBS.

Budget Type

Use this setting to specify a budget type or financial plan type for each EBS Project Accounting to transfer the budgets from EnterpriseTrack to EBS.

Primavera Calendar Working Hours

Use this setting to specify the Project Calender working hours per day in the Primavera application.

When EBS is the destination provider in a Project Data flow, set values and attributes for the following parameters:

Project Plan


Export Activity as Leaf Level Task


Project / Project Template Number (Required only for project creation)

Use this setting to specify the Project or Project Template Number if there is no field mapping.

Project / Task Organization Name (Required only for project creation)

Use this setting to specify the Project Organization Name if there is no field mapping.


30

Planning Resource List (Required only for Resource Assignments)

Use this setting to specify the Planning Resource List Name if there is no field mapping.

Budget Type (Required only for Exporting Financial Plan)

Use this setting to specify a budget type or financial plan type as per EBS Project Accounting to transfer budgets from P6 to EBS.

Budget Entry Method (Required only for Exporting Financial Plan)

Use this setting to specify a budget entry methods when budgets are created in project costing from P6 to EBS.



Save Data to EBS if there are errors

Use this setting to determine whether to save the data in EBS with errors.

Delete Data that no longer exists in source application?


EBS Responsibility for Project Synch from third-party

Use this setting to define the EBS Responsibility Key of responsibility name to determine operating unit to allow to create a project in EBS in different operating units.

EBS User Name for Project Synch from third-party

Use this setting to define the EBS User name for EBS Initialization.

P6 Provider Application Parameters

When P6 is the source provider in a project data flow, set values and attributes for the following parameters:

P6 Filter

Use this setting to identify and transfer Projects business objects in P6. Enter multiple values for the following fields as comma-separated values: EPS Ids, Project Ids, Project Code Type Name, and Project Code Value. Click Add row to enter multiple Project business objects.

Spread Period Type

Use this setting to select the default spread period type in P6 EPPM. Options include: Week, Month, Day, and Financial Period.

Activity Filter

Use this setting to identify and transfer Project business objects in P6. Enter multiple values for the following fields as comma-separated values: Activity Ids, Activity Status, Activity Type, and Activity Code. Click Add row to enter multiple Activity business objects.

Resource Assignment Filter

Use this setting to identify and transfer ResourceAssignments business objects in P6. Enter multiple values for the following fields as comma-separated values: Resource Ids and Resource Type. Click Add Row to enter multiple ResourceAssignment objects.


31

Baseline Ids

Use this setting to identify and transfer Baseline IDs in P6. Enter multiple values as comma-separated values. This parameter is specific to a Unifier - P6 integration only.

Summarize project(s) before synchronization?

Use this setting to determine whether to summarize projects before a synchronization.

Synchronize WBS Hierarchy

Use this setting to determine to what extent you would like to synchronize the WBS hierarchy in P6. Options include: Complete, Partial, or Levels. The P6 WBS setting in P6 will override the Gateway setting.

When P6 is the destination provider in a Project Data flow, set values and attributes for the following parameters:

EPS Location

Use this setting to define the EPS node when new projects are created in P6.

Resource Destination

Use this setting to specify the location of the Resource objects imported into P6.

Role Destination

Use this setting to specify the location of the role objects imported into P6.

Calculate Costs from Units

Use this setting to determine whether to calculate costs from the units.

Auto Compute Actuals

Select this setting if you want the actuals to be auto-computed in P6.

Schedule project(s) after synchronization?

Use this setting to determine whether to schedule projects after a synchronization.

Summarize project(s) after synchronization?

Use this setting to determine whether to summarize projects after a synchronization.

Save data to P6 if there are errors

Use this setting to determine whether to save the imported data in P6 with errors.

Synchronize one project at a time

A single project is usually split into multiple child projects in Gateway and executed for synchronization. By default all child projects are executed simultaneously. Use this setting to determine whether to synchronize one project at a time.

Connecting with Instantis EnterpriseTrack

For integrations with EnterpriseTrack, only Project Data flow type is supported in Gateway. Project data such as project header and project finance data, including budget or actual data can be exchanged between EBS and Instantis EnterpriseTrack applications.


32

Note: Data files specific to EBS - EnterpriseTrack integration are available in the ..\EBSProvider\Data\etrack folder of the Primavera Gateway installation. Ensure you run the Gateway configuration utility to install the etrack folder to support this integration. For more details on

using the configuration utilities, refer to the Gateway Installation Guide.

This section describes the business flows, field mapping templates, and parameters delivered out-of-the-box in Primavera Gateway for exchanging data between EBS and Instantis EnterpriseTrack applications.

Project Data Flow Type

Use the Project Data flow type to transfer project data business objects identified in the Business Objects Supported in Project Data Flow (on page 32). The following types of project data business flows are delivered for an EnterpriseTrack - EBS integration in Gateway:

Project Flow from EnterpriseTrack to EBS

Project Flow from EBS to EnterpriseTrack

Business Objects Supported in Project Data Flow

The following business objects are supported between EBS and EnterpriseTrack applications using the Project Data flow type. These business objects can be transferred using the field-mapping templates delivered in Gateway. To view a list of field mapping templates provided in Gateway, see Field Mapping Templates for Project Data Business Objects (on page 33).

When EnterpriseTrack is the source provider, the following business objects are supported between EnterpriseTrack and EBS applications in the Project Data flow type:

EnterpriseTrack Source Business Objects

Gateway Business Objects

EBS Destination Business Objects

Project

ProjectFinance

ProjectFinanceElement

When EBS is the source provider, the following business objects are supported between EnterpriseTrack and EBS applications in the Project Data flow type:


EnterpriseTrack Destination Business Object


BudgetHeader ProjectFinance ProjectFinance

BudgetDetails ProjectFinanceElement

ProjectFinanceElement


33

Field Mapping Templates for Project Data Business Objects

The following tables lists all field-mapping templates and the business flows that support each project data business object. Each business object can be supported by more than one field-mapping template. You can edit the delivered business flows to include or exclude business objects by selecting the corresponding field-mapping templates or also create your own if these templates don't fit your needs. For a detailed list of the fields mapped in each template, see Appendix B: Fields Supported in Mapping Templates (on page 47).

EnterpriseTrack Source Business Objects


Used In...

Project EnterpriseTrack Project Mapping

Project Flow from EnterpriseTrack to EBS business flow

ProjectFinance EnterpriseTrack ProjectFinance Mapping

ProjectFinanceElement EnterpriseTrack ProjectFinanceElement Mapping"



Used in...

Project EnterpriseTrack Project Mapping

Project Flow from EBS to EnterpriseTrack business flow

BudgetHeader EnterpriseTrack ProjectFinance Mapping

BudgetDetails EnterpriseTrack ProjectFinanceElement Mapping

Setting Provider-Specific Parameters

Based on the role of EnterpriseTrack and EBS providers and the data to be transferred in the business flow the following provider-specific parameters will display as either source or destination application parameters in the Add or Edit Business Flow wizard.



34



EnterpriseTrack Provider Application Parameters

When EnterpriseTrack is the source provider in a project data flow, set values and attributes for the following parameters:

EnterpriseTrack Mandatory Roles (῀separated list. Required only for project creation.)

Use this setting to specify the user roles only when creating a new project in EnterpriseTrack from E-Business Suite.

EnterpriseTrack Login IDs of Mandatory Roles (῀separated list. Required only for project creation.)

Use this setting to specify the login IDs only when creating a new project in EnterpriseTrack from E-Business Suite.

When EnterpriseTrack is the destination provider in a project data flow, set values and attributes for the following parameters:

EnterpriseTrack Project ID

Use this setting to specify the project ID to be sent from EnterpriseTrack.

EnterpriseTrack Project Name

Use this setting to identify the project to be sent from EnterpriseTrack by its project name.

Note: If Project ID and Project Name are both provided, then Project ID is used to search the project.

Specify the following settings only if you send Project Finance data from EnterpriseTrack:

EnterpriseTrack Project Sub Object

Use this setting to additional objects that are to be transferred with a Project business object. Options include:

Project Metadata

Project Finance Structure

Project Finance Current

Project Finance Snapshot

Finance Data Search Mode (M for Monthly / Y for Yearly / A for Aggregate)

Use this setting to select the time length of the finance data.

From Month (YYYY/MM Format)

Use this setting to specify the start year and month to send data from EnterpriseTrack.

EnterpriseTrack Project Finance Snapshot Name (Required only for project finance snapshot export)

Use this setting to specify the name of the ProjectFinanceSnapshot business object.


35

To Month (YYYY/MM Format)

Use this setting to specify the end year and month to send data from EnterpriseTrack.

From Year (YYYY Format)

Use this setting to specify the start year to send data from EnterpriseTrack.

To Year (YYYY Format)

Use this setting to specify the end year to send data from EnterpriseTrack.

Group Name (Use * if you need data for all groups)

Use this setting to specify groups to be sent from EnterpriseTrack.

Category Name (Use * if you need data for all groups)

Use this setting to specify Category Names to be sent from EnterpriseTrack.

Element Name (Use * if you need data for all groups)

Use this setting to specify Element Names to be sent from EnterpriseTrack.




When EBS is the source provider in a project data flow, set values and attributes for the following parameters:

ERP Project Filter

Use this setting to identify and transfer ERP Project business objects from the source application. Enter multiple values for ImportProjectIds as comma-separated values. Select Add row to enter multiple ERP Project business objects.

Project Plan


Plan Versions

Use this setting to select the plan version for transfer to P6. Options include: Current Working, Current Baselined, and Original.

Leaf Level Task as Activity

Use this setting to map the lowest leaf level tasks in EBS as an Activity. Otherwise, these are mapped to WBS by default.

Create Material Resources Only

Use this setting to determine whether to create only material resources class or all resource classes from EBS.

Budget Type





36

When EBS is the destination provider in a Project Data flow, set values and attributes for the following parameters:

Project Plan


Export Activity as Leaf Level Task


Project / Project Template Number (Required only for project creation in EBS PA)

Use this setting to specify the Project or Project Template Number if there is no field mapping.

Project Organization Name (Required only for project creation in EBS PA)

Use this setting to specify the Project Organization Name if there is no field mapping.

Planning Resource List (Required only for Resource Assignments in EBS PA)

Use this setting to specify the Planning Resource List Name if there is no field mapping.

Budget Type


Budget Entry Method (Required only for Financial Plan in EBS PA)

Use this setting to specify a budget entry method when budgets are created in Project Costing from EnterpriseTrack to EBS.



Save data to EBS if there are errors

Use this setting to determine whether to save the data in EBS with errors.

Delete data that no longer exists to source application?


EBS Responsibility for Project Synch from third party

Use this setting to define the EBS Responsibility Key of responsibility name to determine operating unit to allow to create a project in EBS in different operating units.

EBS User Name for Project Synch from third party

Use this setting to specify the user names of personnel who can synchronize projects from a third party.



37

The business flows delivered or created in Gateway are used in synchronizations that perform the actual data transfers. For each of the out-of-the-box business flows delivered in Gateway, a corresponding out-of-the-box synchronization is delivered. You can either use the delivered synchronization or create new synchronizations if these don't fit your needs. Both options are outlined in detail.

In This Section

Master Data Synchronization................................................................................... 37 Project Data Synchronizations ................................................................................. 37 Creating New Synchronization Jobs ........................................................................ 39 Using Synchronizations Delivered in Gateway ........................................................ 39

Master Data Synchronization

For an EBS - P6 integration in Gateway, the Synch EBS Master Data to P6 master data synchronization is delivered out-of-the-box to support the delivered Synch EBS Master Data to P6 master data business flow listed in Master Data Flow Type (on page 22) .

Note: The out-of-the-box synchronization name is always identical to the

out-of-the-box business flow name.

Project Data Synchronizations

Depending on the applications being integrated, the following project data synchronizations are delivered in Gateway:

EBS - P6 integration

The following project data synchronizations are delivered out-of-the-box:

Instantiate EBS Project(s) from P6

Synch EBS Project(s) to P6

Synch P6 Project(s) to EBS

EBS - EnterpriseTrack Integration /

The following project data synchronizations are delivered out-of-the-box:

Project Flow(Sync) from EBS to EnterpriseTrack /

Project Flow(Sync) from EnterpriseTrack to EBS /

Defining Synchronizations

39

Creating New Synchronization Jobs

Create synchronization jobs that use the defined business flows to transfer data between EBS and P6 applications. To transfer data between applications, you need to create and run a synchronization. You have the option to run the synchronization on demand, run based on the occurrence of specific events, or schedule it to run regularly at a time and date of your choosing.

Before you can transfer data between applications, you first need to define business flows and configure connections for the applications in the data flow.

Tip: If an integration supports master data, then synchronize the master data between applications before you synchronize project data. This will ensure that each deployment has the information necessary to synchronize project data.

To transfer data between applications:

1) Select Synchronizations.

2) Select Add.

3) Follow the steps in the Add Synchronization wizard to name and configure the synchronization. Select Save when finished.

4) Transfer data between applications using any of the following options:

To run a synchronization on demand, highlight the synchronization and select Run.

To review the data that will be moved from the source application, highlight the synchronization and select Run with Review.

To schedule an event-based synchronization, highlight the synchronization, and select Run on Event.

To schedule the synchronization to run at a certain date and time, select the synchronization and select Edit Schedule.

5) Enter information for the synchronization in the Edit Schedule dialog box and select Save when finished.

6) To delete a synchronization, highlight the synchronization and select Delete. Select Yes in the Confirmation dialog box.

Tip

You can run an existing synchronization at any time by selecting a synchronization and selecting Run.

Using Synchronizations Delivered in Gateway

To use the out-of-the-box synchronizations delivered in Gateway:


2) Select Edit...

3) Follow the steps in the Edit Synchronization wizard to name and configure the synchronization. Select Save when finished.


40

4) Transfer data between applications using any of the following options:

To run a synchronization on demand, highlight the synchronization and select Run.

To review the data that will be moved from the source application, highlight the synchronization and select Run with Review.

To schedule an event-based synchronization, highlight the synchronization, and select Run on Event.

Note: You can set up an event-based synchronization using the delivered P6 event provider only if P6 is the source provider in the defined flow. To set up event-based synchronizations for any other provider you will need to develop an event provider for your provider. For more details, refer to the Developer's Guide.

To schedule the synchronization to run at a certain date and time, select the synchronization and select Edit Schedule.

5) Enter information for the synchronization in the Edit Schedule dialog box and select Save when finished.

6) To delete a synchronization, highlight the synchronization and select Delete. Select Yes in the Confirmation dialog box.

This example demonstrates how to synchronize data between applications and monitor the data transfer. For more details on Primavera Gateway features and functionality, see the Primavera Gateway Online Help.

For this example, assume that you want to export project data from P6 Deployment into EBS Deployment using a synchronization called Synchronize Project Data from P6 to Oracle E-Business Suite. Also assume that you will use the Synch Project Data from Oracle E-Business Suite to P6 business flow.

Note: Always synchronize master data, if applicable, between applications before you synchronize project data. This will ensure that each deployment has the information necessary to synchronize project data.

Prerequisites

This example assumes that the following prerequisites have been completed:

Primavera Gateway is installed and running.

An application deployment called P6 Deployment has been added to Primavera Gateway.

An application deployment called EBS Deployment has been added to Primavera Gateway.

Transferring Data between Applications: Example

Transferring Data between Applications: Example

41

A business flow called Synchronize Project Data from P6 to Oracle E-Business Suite has been created to define the flow of data between applications.

Move Data between Applications

1) After you log into Primavera Gateway, select Synchronizations.

2) Select Add.

3) In the Add Synchronization wizard:

a. Select Synchronize Project Data from P6 to Oracle E-Business Suite from the Business Flow list.

b. Select P6 from the Source list.

c. Select EBS Deployment Deployment from the Destination list.

d. Select Next.

e. Modify the synchronizations to include the correct project filter and EPS location.

f. Review the parameters and select Next.

Note: The parameter value selected in the synchronization is unaffected although you may change the parameter’s default value when editing the business flow.

g. Review the Synchronization Summary and select Save.

4) Select the Synchronize Project Data from P6 to Oracle E-Business Suite synchronization and select Run with Review, Run, or Run on Event.

When you select Run, proceed to monitor the synchronization job on the Monitoring page.

When you select Run with Review:

a. On the Summary page, review a list of business objects and the fields associated with each business object identified by the synchronization job.

b. After completing the review, select Commit to set up the synchronization.or select Cancel.

When you select Run on Event:

c. Select P6UpdateEventListener from the Listener Name list and enter the Delay (in minutes) to run the synchronization when an event occurs.

d. Select Project from the Business Object list and enter Id in Fields, and then select Add Row.

e. Select Save.

You have now set up an event to run a synchronization job when an update is made to any project ID .

Note: You can disable an existing event synchronization by clicking Disable in the Listener Instance wizard. To enable a disabled schedule, click Enable in the Listener Instance wizard.

Monitor a Synchronization Job

After you run the synchronization, you can check to see that it is working properly by finding the synchronization on the Monitoring page.


42

1) Select Monitoring.

2) In the Filter lists, select All Jobs by Type and Project Data. The synchronization jobs will be filtered using these selections.

3) Select the Job link for Synchronize Project Data from P6 to Oracle E-Business Suite.

4) Select Convert from Source to Gateway format and then select Gateway Format. Data for this flow step, including information if there is a failure, will display.

5) If you are a user with data access privileges, select Download to download the log files of the synchronization job.

6) Select Close.

Edit a Synchronization Job Schedule

After monitoring the synchronization job, if you are satisfied with the synchronization, you can schedule times when the synchronization will run.


2) Select the Synchronize Project Data from P6 to Oracle E-Business Suite synchronization and select Edit Schedule.

3) In the Edit Schedule wizard, schedule a date and time when the synchronization will be run:

Note: Synchronizations can also be run on demand by selecting the synchronization and selecting Run.

a. Select Weekly from the Frequency list.

b. Select Tuesday from the list of weekdays.

c. Enter 09/04/2015 15:00 in the Starts field.

Time should be entered in a twenty-four hour format.

d. Select the End after occurrence(s) option and enter 8 in the field.

Note: You can disable a existing schedule by clicking Disable in the Edit Schedule wizard. To enable a disabled schedule, click Enable in the Edit Schedule wizard.

e. Select Save.

43

In This Section

Define the Flow Steps in a Flow .............................................................................. 43

Define the Flow Steps in a Flow

Flows contain one or more flow steps. Each flow is a distinct sequence of the types of flow steps listed below:

Load

This step loads the source data and passes it on to the next step.

Convert

This step converts the source data to the Gateway data structure and the destination data structure.

Compare

This step compares the source and destination data and identifies changed, deleted, and added objects so that the system can synchronize the data efficiently.

To ensure that the data that follows the same structure when it is compared, both the source and the destination data must be converted to the Gateway format before it can be compared. When identifying objects that are deleted in the source data, the compare step uses the cross reference table to determine whether the data has been synchronized in the past, the presence of the data in the cross reference table indicates that the data has been synchronized in the past. During the Compare step, the system marks objects that have been deleted in the source data for deletion in the destination system only if the record is in the cross reference table and a delete parameter is associated with the flow.

This step compares the source and destination data and identifies the delta or differences for the next step.

Note: Project Data flow supports the Compare step. Master Data does not support the Compare step.

Review

(Optional) This step enables you to review the source data before updating the data in the destination application.

Update

This step saves the data into the destination system.

Save Feedback

(Optional) This step saves details on the changes made in each step and provides this information to the source provider.

Appendix A: About Flow Steps


44

Flow Sequence When Using Master Data

The Master data flow type, if applicable to an integration, is used to specifically transfer master data between distinct environments of the P6 application. For example, you would use this flow to transfer data from a P6 Testing environment to P6 production environment. The steps are organized as follows:

Load from Source: This step loads the master data from the source application into the Gateway Framework so that it can be processed.

Convert from Source to Gateway Format: This step converts the source master data from the source format to the Gateway format.

Load from Destination: This step loads project data from the destination application into the Gateway framework so that it can be processed.

Convert from Destination to Gateway Format: This step converts destination's master data to the Gateway format. The converted data is used for the Compare step.

Compare Data: This step compares the converted source Gateway data with the destination Gateway data. This step compares each XML object and uses the following rules to determine how the data is synchronized in the Update Destination step.

If the data is in the source object but not in the destination object, the data is created in the destination object during the Update Destination step.

If the data is in the destination object but not in the source node, the system performs the following steps:

* Inspects the cross reference tables to determine whether the data has ever been synchronized.

* Determines whether the Delete parameter has been set for the flow.

If the data is in the cross-reference tables and the delete parameter has been set for the flow, the data is deleted from the destination during the Update Destination step. Otherwise, the data is not deleted in the Update Destination step.

Objects that contain updated data are marked for synchronization.

Objects that contain the same data in both the source and the destination nodes are ignored.

Convert to Destination Format: This step converts the master data from Gateway format to the destination format.

Review data: (Optional) This step enables you to review the source data before updating the data in the destination application.

Update Destination: This step saves the master data into the destination application's database.

Save Feedback: (Optional) This step saves details on the changes made in each step and provides this information to the source provider.

Flow Sequence When Using Project Data

The Project data flow type, if applicable to an integration, is used to specifically to transfer project data between two applications or between two distinct deployments of the P6 application. For example, you would use this flow to transfer project data from a P6 Testing environment to P6 production environment. The steps are organized as follows:

Appendix A: About Flow Steps

45

Load from Source: This step loads the master data from the source application into the Gateway framework so that it can be processed.

Convert from Source to Gateway Format: This step converts the source project data from the source format to the Gateway format.

Load from Destination: This step loads the project data from the destination application into the Gateway framework so that it can be processed.

Convert from Destination to Gateway Format: This step converts the destination project data to the Gateway format.

Compare Project Data: This steps compares the source data with the destination data in the current Gateway format.

Convert to Destination Format: This step converts the project data from Gateway format to the destination format.

Review data: (Optional) This step enables you to review the source data before updating the data in the destination application.

Update Destination: This step saves the project data into the destination application's database.

Save Feedback: (Optional) This step saves details on the changes made in each step and provides this information to the source provider.

Flow Sequence When Using the Compare Step

A flow that supports a Compare step loads the project from both sides, determines the delta between each side, and uses only the difference to synchronize the data during the final update.

Unlike the normal flow that consists of four steps (load, convert to Gateway, convert from Gateway, and Update Destination), a flow that supports the Compare step includes the following additional steps:

Load data from the other application

Convert the data to the Gateway format

Compare

The Compare step is supported by the Gateway framework code; providers do not have to implement it. Providers will need to implement the extra load and convert steps as these must be implemented by the the provider of the destination application. The destination provider must ask for the key of the project that is being loaded to the source side of the implementation when supporting the compare functionality.

Source Provider

In the Project Data flow, the source provider needs to communicate to the destination side which project it is loading when the Primavera Gateway loads the initial project data from the source side. To do that, the source provider must implement the getProjectKeyForCompare method in the FlowProvider interface.

Normally, a provider will determine which project it is to load from the filter or the parameters that users set in the Gateway user interface. The implementation of the method needs to return a Gateway side value of this project key.

The following is a sample code snippet from the Project Data flow in SampleProvider.java:


46

@Override public Map<String, String> getProjectKeyForCompare(String flowType, FlowContext context) throws ProviderException { SampleFlowType type = getFlowType(flowType); switch (type) { case SyncProjectImport: String sampleProjectKey = (String) context.getParameter("ImportProjectId"); if (StringUtils.isEmpty(sampleProjectKey)) { return null; } else { Map<String, String> keyMap = new HashMap<String, String>(); keyMap.put("ObjectId", context.getXRefValueByGuest("Project", sampleProjectKey)); keyMap.put("Id", sampleProjectKey); return keyMap; } default: throw new UnsupportedOperationException("Compare not supported."); } }

Destination Provider

Similarly, in the Project Data flow, the destination provider needs to ask for the project key so that it can load the same project. To do that, the destination provider must implement the methods in the LoadStepContext interface.

The LoadStepContext interface has two methods for this use case:

isLoadStepForCompare method can tell you whether this load step is invoked as a companion load step for the Compare mechanism.

getProjectKeyForCompare method can tell you which project you should load. The project key returned by getProjectKeyForCompare is already a destination side value.

The following is a code snippet from the Project Data flow in ProjectLoadStep of the Sample provider:

if (context.isLoadStepForCompare()) { Map<String, String> projectKeys = context.getProjectKeyForCompare(); String projectId = null; if (projectKeys != null) { String objectId = projectKeys.get("ObjectId"); if (StringUtils.isEmpty(objectId)) { projectId = projectKeys.get("Id"); } else { projectId = objectId; } } if ((projectId == null) || projectId.isEmpty()) { return new PDIDocumentImpl(); } else { return getOneProject(projectId, context); } }

47

In This Section

Fields Supported with P6 EPPM .............................................................................. 47 Fields Supported with Instantis EnterpriseTrack ...................................................... 56

Fields Supported with P6 EPPM

The following field-mapping templates are delivered in Gateway for exchanging data between P6 and EBS applications.

Activity Mapping

This project data field-mapping template creates an Activity object with activity mappings in the destination application. The following fields are mapped from each application:

EBS P6

TASK_NUMBER Id

PARENT_TASK_NUMBER WBSCode

COMPLETION_DATE PlannedFinishDate

TASK_NAME Name

START_DATE PlannedStartDate

ACTIVITY_TYPE Type


This project data field-mapping template creates an Activity object activity budget field mappings with current costs in the destination application. The following fields are mapped from each application:

EBS P6

VERSION_NUMBER EBSBudgetVersionNumber

RAW_COST EBSBudgetCurrentCost

Appendix B: Fields Supported in Mapping Templates


48

EBS P6


TASK_NUMBER Id

VERSION_NAME EBSBudgetVersionName

BUDGET_STATUS_CODE EBSBudgetStatusCode

Activity budget Field Mappings- Original

This project data field-mapping template creates an Activity object activity budget field mappings with original costs in the destination application. The following fields are mapped from each application:

EBS P6


RAW_COST EBSBudgetOriginalCost


TASK_NUMBER Id



Activity Budget Field Mappings - Proposed

This project data field-mapping template creates an Activity object activity budget field mappings with proposed costs in the destination application. The following fields are mapped from each application:

EBS P6


RAW_COST EBSBudgetProposedCost


TASK_NUMBER Id




49

Activity Relationship Fields

This project data field-mapping template creates a Relationship object in the destination application. The following fields are mapped in each application.

EBS P6

TO_PROJECT_NUMBER PredecessorProjectId

FROM_PROJECT_NUMBER SuccessorProjectId

TO_TASK_NUMBER PredecessorActivityId

FROM_TASK_NUMBER SuccessorActivityId

RS_SUBTYPE_CODE Type

LAG Lag

Assignment Actual Updates

This project data field-mapping template updates a ResourceAssignment object in the destination application. The following fields are mapped from each application.

EBS P6

ACTUAL_QUANTITY ActualUnits

ACTUAL_COST ActualCost

TASK_NUMBER ActivityId

Assignment Budget Field Mappings - Current

This project data field-mapping template creates a ResourceAssignment object with current budget cost information in the destination application. The following fields are mapped from each application.

EBS P6

QUANTIY EBSBudgetCurrentQuantity






50

EBS P6


Activity Budget Field Mappings - Original

This project data field-mapping template creates a ResourceAssignment object with current budget cost information in the destination application. The following fields are mapped from each application.

EBS P6


QUANTITY EBSBudgetOriginalQuantity





BUD_LINE_BURDENED_COST EBSBudgetCurrentCost

Activity Budget Field Mappings - Proposed

This project data field-mapping template creates a ResourceAssignment object with proposed budget cost information in the destination application. The following fields are mapped from each application.

EBS P6


QUANTITY EBSBudgetProposedQuantity





BUD_LINE_BURDENED_COST EBSBudgetProposedCost

DESCRIPTION EBSBudgetVersionName


51

Assignment Mapping

This project data field-mapping template creates a ResourceAssignment object with Assignment mappings in the destination application. The following fields are mapped from each application.

EBS P6

RESOURCE_CLASS_CODE ResourceType


PLANNED_EFFORT PlannedUnits

IS_PRIMARY_RESOURCE IsPrimaryResource

PLANNED_COST PlannedCost

BUDGET_START_DATE PlannedStartDate

BUDGET_END_DATE PlannedFinishDate

ROLE_NUMBER RoleId

RESOURCE_NUMBER ResourceId

Expense Category Fields

This master data field-mapping template creates a new ExpenseCategory object in the destination application.

EBS P6

RESOURCE_NAME Name

Financial Period Fields

This master data field-mapping template creates a new FinancialPeriod object in the destination application.

EBS P6

PERIOD_NAME Name

END_DATE EndDate

START_DATE StartDate


52

Project Budget Field Mappings-Current

This project data field-mapping template creates a budget information to the project object with current costs in the destination application. The following fields are mapped in each application:

EBS P6

SEGMENT1 Id



RAW_COST EBSBudgetCurrentCode



This project data field-mapping template creates a budget information to the project object with original costs in the destination application. The following fields are mapped in each application:

EBS P6

SEGMENT1 Id





BUD_LINE_BURDENED_COST EBSBudgetCurrentCost


This project data field-mapping template creates a budget information to the project object with proposed costs in the destination application. The following fields are mapped in each application:

EBS P6

SEGMENT1 Id





53

EBS P6


Project Header Mappings

This project data field-mapping template adds project header information and creates a new project object in the destination application. The following fields are mapped in each application:

EBS P6

SEGMENT1 Id

NAME Name

DESCRIPTION Description

PROJECT_START_DATE PlannedStartDate

COMPLETION_DATE MustFinishByDate

Resource Fields

This field mapping template can be used in a master data and a project data business flow to create a new Resource object in the destination application. The following fields are mapped in the applications:

EBS P6

RESOURCE_CLASS_CODE ResourceType

EMAIL_ADDRESS EmailAddress

EMPLOYEE_NUMBER EmployeeId

UNIT_OF_MEASURE UnitofMeasureAbbreviation

RESOURCE_ID Id

RESOURCE_NAME Name

Resource Rates

This field mapping template can be used in an master data business flow to create a new ResourceRate object in the destination application. The following fields will be mapped from each application:


54

EBS P6

RATE_START_DATE EffectiveDate

RATE PricePerUnit

Role Fields

This field mapping template can be used in an master data business flow to create a new Role object in the destination application.

EBS P6

RESOURCE_NAME Name

RESOURCE_ID Id

Role Rates

This field mapping template is used in the master data business flow to create a new RoleRate object in the destination application.

EBS P6

RATE PricePerUnit

Update Actuals

This project data field-mapping template updates an Activity object in the destination application. The following fields are mapped from each application:

EBS P6

DATA_DATE DataDate

ACTUAL_FINISH_DATE ActualFinishDate

TASK_NUMBER Id


ACTUAL_START_DATE ActualStartDate

PERCENT_COMPLETE PhysicalPercentComplete


55

WBS Field Mapping

This field mapping template creates a new WBS object in the destination application. The following fields are mapped in each application:

EBS P6

TASK_NUMBER Code

TASK_NAME Name


This field mapping template creates a new WBS object with budget information with current costs in the destination application. The following fields are mapped in each application:

EBS P6

TASK_NUMBER Code




VERSION_NAME EBSBudgetVersionNamer


This field mapping template creates a new WBS object with budget information with original costs in the destination application. The following fields are mapped in each application:

EBS P6

TASK_NUMBER Code






56


This field mapping template creates a new WBS object with budget information with proposed costs in the destination application. The following fields are mapped in each application:

EBS P6

TASK_NUMBER Code





Fields Supported with Instantis EnterpriseTrack

The following field-mapping templates are delivered in Gateway for exchanging data between Oracle Instantis EnterpriseTrack and EBS applications.

EnterpriseTrack Project Mapping

This project data field-mapping template creates a new project object in the EBS application. The following fields are mapped:

EBS EnterpriseTrack

NAME project_name

CARRYING_OUT_ORGANIZATION_NAME business_unit

PROJECT_ORGANIZATION division

PROJECT_TYPE project_type

PROJECT_TYPE roadmap

PROJECT_START_DATE start_date

COMPLETION_DATE planned_realization_date

CREATED_FROM_PROJECT fintemplateid

PROJECT_CURRENCY_CODE currency_code

CALENDAR_NAME calendar_id

DESCRIPTION keywords

Appendix C: P6 Objects Supported in Gateway for Events

57

EnterpriseTrack ProjectFinance Mapping

This project data field-mapping template creates a new ProjectFinance object in the destination application. The following fields are mapped:

EBS EnterpriseTrack

OPERATION_TYPE operation_type

FIN_EDIT_TYPE fin_edit_mode

FIN_DATA_TYPE fin_data_type

EnterpriseTrack ProjectFinanceElement Mapping

This project data field-mapping template creates a new ProjectFinanceElement object in the destination application. The following fields are mapped:

EBS EnterpriseTrack

TASK_LEVEL element_class

BUD_LINE_BURDENED_COST value

ELEMENT_TYPE element_type

TASK_NUMBER id

PARENT_TASK_NUMBER parent_id

TASK_ID sequence_number

TASK_NUMBER display_name

The following P6 business objects are supported in Gateway for P6 event notifications.

P6 Objects

Activity

ActivityExpense

Appendix C: P6 Objects Supported in Gateway for Events


58

P6 Objects

ActivityRisk

EPS

Project

ResourceAssignment

Risk

RiskImpact

RiskResponseAction

RiskResponseActionImpact

RiskResponsePlan

WBS

59

In This Section

Where to Get Documentation .................................................................................. 59 Where to Get Training ............................................................................................. 63 Where to Get Support ............................................................................................. 63 Documentation Accessibility .................................................................................... 64

Where to Get Documentation

Complete documentation libraries for Primavera Gateway releases are available on the Oracle Technology Network (OTN) at:

http://www.oracle.com/technetwork/documentation/default-1923957.html

From this location you can either view libraries online or download them to have local copies. We recommend viewing them from OTN to ensure you always access the latest versions, including critical corrections and enhancements.

Primavera Gateway is configured to access its help system on OTN. However, a downloadable version of the Gateway help system is also available on OTN if you need to download, deploy, and access a local copy.

The documentation assumes a standard setup of the product, with full access rights to all features and functions.

The following table describes the core documents available for Primavera Gateway and lists the recommended readers by role.

Title Description

Gateway Help Describes how to work with Primavera Gateway and provides information to help users accomplish tasks.

All users should read the Help.

Gateway Developer's Guide

Provides information on how third-party systems such as enterprise resource management (ERP) and enterprise asset management (EAM) systems can create their own providers in order to integrate with Primavera products.

Developers of third-party providers that integrate with Primavera products via Primavera Gateway should read this book.

For More Information


60

Title Description

Gateway Customization Guide

Provides information on how to customize an existing third-party integration.

Developers interested in customizing existing third-party providers that integrate with Primavera products via Primavera Gateway should read this book.

Gateway Provider Reference Guide

Provides a list of the business objects available for each supported provider.


EBS Provider Reference Guide

Provides a list of the business objects available for the EBS provider.


VCP Provider Reference Guide

Provides a list of the business objects available for the VCP provider.


Manual Deployment Guide

Provides information on how to manually install and configure Primavera Gateway.

The Primavera Gateway network administrator/database administrator and the administrator for the third-party or ERP system should read this guide.

Gateway Installation and Configuration Guide

Provides information on how to install and configure Primavera Gateway. Primavera Gateway is a product that facilitates integrations with Primavera products and third-party systems such as enterprise resource management (ERP) and enterprise asset management (EAM) systems.


Gateway Upgrade Guide Provides a sequence of procedures that must be completed to upgrade to a new version of Primavera Gateway.



61

Title Description

Gateway Performance and Sizing Guide

Provides hardware and software requirements for deploying Primavera Gateway.


Gateway Security Guide Provides guidelines on establishing a highly secure environment for all Primavera Gateway environments.


Gateway API Programmer's Guide

Provides instructions on how to access and use Primavera Gateway REST APIs.

The Primavera Gateway network administrator/database administrator and Primavera Gateway users having the Gateway Developer role should read this guide.

Connecting with Instantis EnterpriseTrack

Provides instructions on how to setup the integration environment for Oracle Instantis EnterpriseTrack in Primavera Gateway.

The Primavera Gateway network administrator/database administrator and the administrator for the third-party system should read this guide.

Connecting Prime and P6 EPPM

Provides instructions on how to setup the integration environment between Oracle Primavera Prime and P6 Enterprise Project Portfolio Management in Primavera Gateway.


Connecting Unifier and P6 EPPM

Provides instructions on how to setup the integration environment between Oracle Primavera Unifier and P6 Enterprise Project Portfolio Management in Primavera Gateway.


Migrating P6 Data Between Distinct Environments

Provides instructions on how to setup the integration environment between distinct P6 deployments to transfer P6 data in Primavera Gateway.

The Primavera Gateway network administrator/database administrator and the administrator should read this guide.


62

Title Description


Provides instructions on how to setup the integration environments for Oracle E-Business Suite with P6 Enterprise Project Portfolio Management and Instantis EnterpriseTrack in Primavera Gateway.


Connecting Value Chain Planning and P6 EPPM

Provides instructions on how to setup the integration environment between Oracle Value Chain Planning and P6 Enterprise Project Portfolio Management in Primavera Gateway.


Configuring Gateway for Single Sign On

Provides instructions on how to configure Oracle Access Manager (OAM) and then enable Single Sign On for Primavera Gateway.

The Primavera Gateway network administrator/database administrator should read this guide.

Primavera Cloud Service Administrator's Guide

This guide describes how to configure and administer Primavera products hosted on the Oracle Cloud for industries. It supersedes all the other installation and configuration guides for Primavera products, since they are for on-premises deployments.

Cloud administrators should read this guide.

Gateway Licensing Information User Manual

Lists licensing information of all third-party software that is used or associated with the Oracle software program.

Tested Configurations Lists the configurations that have been tested and verified to work with Primavera Gateway.


Distributing Information to the Team

You can copy the online documentation to a network drive for access by project participants. Each team member can then view or print those portions that specifically relate to his or her role in the organization.

Throughout this documentation, the Security Guidance icon helps you to quickly identify security-related content to consider during the installation and configuration process.


63

Where to Get Training

To access comprehensive training for all Primavera products, go to:

http://education.oracle.com

Oracle Learning Library

The Oracle Learning Library (OLL) provides online learning content covering Primavera products. Content includes videos, tutorials, articles, demos, step-by-step instructions to accomplish specific tasks, and self-paced interactive learning modules. To access the learning library’s Primavera content, go to:

http://www.oracle.com/goto/oll

Where to Get Support

If you have a question about using Oracle products that you or your network administrator cannot resolve with information in the documentation or help, click http://support.oracle.com/. This page provides the latest information on contacting Oracle Global Customer Support, knowledge articles, and the support renewals process. For more information about working with Support, visit https://support.oracle.com/epmos/faces/DocumentDisplay?id=888813.2 to view Support Tools & Tips.

To get the latest information about Critical Patch Updates, visit http://www.oracle.com/technetwork/topics/security/alerts-086861.html.

Primavera Gateway integrates with different Oracle applications; when you create a Service Request, be sure to open the request with the proper Support team. To ensure you reach the proper Support team, enter the correct product information when you create the Service Request. Each product has its own support line.

Use the Primavera Gateway support line when you are having installation, configuration, connection, or application issues related to Primavera Gateway.

Use one of the following support lines when you are having installation or configuration issues that do not relate to Primavera Gateway.

P6 Enterprise Project Portfolio Management (EPPM)

Oracle Primavera Prime

Primavera Unifier

Oracle Instantis EnterpriseTrack

Oracle E-Business Suite

Oracle Value Chain Planning

Oracle WebLogic Server

Oracle Server

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/us/corporate/accessibility/support/index.html.


64

Using Primavera's Support Resource Centers

Primavera’s Support Resource Center provides links to important support and product information. Primavera's Product Information Centers (PICs) organize documents found on My Oracle Support (MOS), providing quick access to product and version specific information such as important knowledge documents, Release Value Propositions, and Oracle University training. PICs also offer documentation on Lifetime Management, from planning to installs, upgrades, and maintenance.

Visit https://support.oracle.com/epmos/faces/DocumentDisplay?id=1486951.1 to access links to all of the current PICs.

PICs also provide access to:

Communities are moderated by Oracle providing a place for collaboration among industry peers to share best practices.

News from our development and strategy groups.

Education contains a list of available Primavera product trainings through Oracle University. The Oracle Advisor Webcast program brings interactive expertise straight to the desktop using Oracle Web Conferencing technology. This capability brings you and Oracle experts together to access information about support services, products, technologies, best practices, and more.

For more information about working with Support, visit https://support.oracle.com/epmos/faces/DocumentDisplay?id=888813.2.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

65

Oracle Primavera Connecting E-Business Suite

Copyright © 2013, 2016, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products and services from third-parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Legal Notices

Documents

Coon nn neecct tiingg EE--BBuussiinee sss SSuuiitee 155 RR22 · PDF fileCoon nn neecct tiingg EE--BBuussiinee sss SSuuiitee 155 RR22 ... Setting Up EBS Connectivity through Web Services