Gateway E-Business Suite Setup Guide for On-Premises · Gateway E-Business Suite Setup Guide for...

GGaatteewwaayy EE--BBuussiinneessss SSuuiittee SSeettuupp GGuuiiddee ffoorr OOnn--PPrreemmiisseessVVeerrssiioonn 1188

AAuugguusstt 22001188

3

Contents

Overview ........................................................................................................................................... 9

Setting Up the Integration Environment ......................................................................................... 11

Integration Installation Prerequisites .................................................................................................. 11

Managing Personally Identifiable Information .................................................................................... 13

Post-Installation Tasks ......................................................................................................................... 13

Configuring Gateway Domain for P6 Event Notification for On-Premises .............................. 13

Enabling Encryption Between Gateway and P6 Web Services ................................................ 16

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

Extending EBS WebLogic Domain for Web Services Connectivity ................................... 17

Setting up EBS Connectivity through RMI ................................................................................. 18

Configuring the Primavera Gateway User Interface ................................................................. 19Configuring Gateway Settings ............................................................................................ 19

Adding an EBS Application Deployment Connection ........................................................ 21

Adding an EnterpriseTrack Deployment Connection ........................................................ 23

Adding or Editing a P6 Deployment Connection ............................................................... 23

Adding or Editing a Prime Deployment Connection .......................................................... 25

Adding or Editing a Unifier Deployment Connection ........................................................ 25

Copying Provider Deployments .......................................................................................... 26

Gateway Setup and Data Transfer Process Flow ........................................................................... 27

Working with Data Dictionaries ...................................................................................................... 31

Features of Provider Data Dictionaries ............................................................................................... 31

Editing Objects and Fields in Data Dictionaries ................................................................................. 34

Deleting Fields from Data Dictionaries ............................................................................................... 36

Defining Field-Mapping Templates ................................................................................................. 37

Adding or Editing Field-Mapping Templates ....................................................................................... 37

Copying Field-Mapping Templates ...................................................................................................... 38

Deleting Field-Mapping Templates ...................................................................................................... 39

Defining Business Flows ................................................................................................................. 41

Adding Business Flows ......................................................................................................................... 41

Copying Business Flows ....................................................................................................................... 42

Using Business Flows Delivered in Gateway ...................................................................................... 42

Connecting with P6 EPPM .................................................................................................................... 43

Master Data Flow Type .............................................................................................................. 43Business Objects Supported in Master Data Flow ........................................................... 43

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

Setting Provider-Specific Parameters ............................................................................... 44

Project Data Flow Type .............................................................................................................. 46Business Objects Supported in Project Data Flow ........................................................... 46

Gateway E-Business Suite Setup Guide for On-Premises

4

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

Setting Provider- Specific Parameters .............................................................................. 51

Connecting with Instantis EnterpriseTrack ......................................................................................... 54

Project Data Flow Type .............................................................................................................. 55

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



Connecting with Oracle Prime Projects ............................................................................................... 60

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

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


Project Data Flow ....................................................................................................................... 62

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



Connecting with Unifier ........................................................................................................................ 68

Master Data Flow Type .............................................................................................................. 68Business Objects Supported in Master Data Flow ........................................................... 69

Field-Mapping Template for Master Data Business Objects ........................................... 69


Project Data Flow Type .............................................................................................................. 71Business Objects Supported in Project Data Flow ........................................................... 71

Field-Mapping Templates for Project Data Business Objects .......................................... 72


Defining Synchronizations .............................................................................................................. 81

Master Data Synchronization .............................................................................................................. 81

Project Data Synchronizations ............................................................................................................. 81

Adding Synchronization Jobs ............................................................................................................... 82

Copying Synchronizations .................................................................................................................... 83

Using Synchronizations Delivered in Gateway .................................................................................... 84

Transferring Data between Applications: Example ......................................................................... 85

Appendix A: About Flow Steps ........................................................................................................ 89

Define the Flow Steps in a Flow .......................................................................................................... 89

Flow Sequence When Using Master Data ................................................................................ 90

Flow Sequence When Using Project Data ................................................................................. 90

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

Flow Sequence When Using External Custom Step ................................................................. 93

Flow Sequence When Using Internal Custom Step for On-Premises ...................................... 93

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

Fields Supported with P6 EPPM .......................................................................................................... 95

Send EBS Actuals to P6 ............................................................................................................. 95

Send EBS Actual Progress to P6 ............................................................................................... 96

Contents

5

Send EBS Cost Code Details to P6 Activity Expense ................................................................ 96

Send EBS Cost Code Details to P6 ............................................................................................ 97

Send EBS Financial Elements to P6 Expense Category........................................................... 97

Send EBS Financial Period to P6 Financial Period .................................................................. 97

Send EBS Resource to P6 Resource ......................................................................................... 98

Send EBS Resource Rates to P6 Resource Rates ................................................................... 98

Send EBS Role to P6 Resource ................................................................................................. 98

Send EBS Role to P6 Role ......................................................................................................... 99

Send EBS Role Rates to P6 Role Rates .................................................................................... 99

Send P6 Actuals to EBS ............................................................................................................. 99

Send P6 Actual Progress to EBS ............................................................................................. 100

Send P6 Cost Code Details at Activity Expense to EBS ......................................................... 100

Send P6 Cost Code Details to EBS .......................................................................................... 100

Send P6 EXP Actuals to EBS.................................................................................................... 101

Sync EBS and P6 Activity ......................................................................................................... 101

Sync EBS and P6 Activity Cost Budget .................................................................................... 102

Sync EBS and P6 Activity Forecast Budget ............................................................................. 102

Sync EBS and P6 Activity Forecast Revenue .......................................................................... 103

Sync EBS and P6 Activity Revenue Budget ............................................................................ 104

Sync EBS and P6 Financial Assignment Cost Budgets .......................................................... 104

Sync EBS and P6 Financial Assignment Revenue Budget .................................................... 105

Sync EBS and P6 Financial Assignment Forecast Budget ..................................................... 106

Sync EBS and P6 Financial Assignment Forecast Revenue .................................................. 107

Sync EBS and P6 Financial Element Assignments ................................................................ 108

Sync EBS and P6 Activity Relationships ................................................................................. 108

Sync EBS and P6 Assignment Cost Budget ............................................................................ 108

Sync EBS and P6 Assignment Forecast Budget ..................................................................... 109

Sync EBS and P6 Assignment Forecast Revenue .................................................................. 110

Sync EBS and P6 Assignment Revenue Budget ..................................................................... 111

Sync EBS and P6 Resource Assignments ............................................................................... 112

Sync EBS and P6 Project Cost Budget .................................................................................... 112

Sync EBS and P6 Project Revenue Budget ............................................................................ 113

Sync EBS and P6 Project Forecast Budget ............................................................................. 113

Sync EBS and P6 Projects ....................................................................................................... 114

Sync EBS and P6 Project Forecast Revenue .......................................................................... 114

Sync EBS and P6 WBS ............................................................................................................. 115

Sync EBS and P6 WBS Cost Budget........................................................................................ 115

Sync EBS and P6 WBS Revenue Budget ................................................................................ 116

Sync EBS and P6 WBS Forecast Budget ................................................................................ 117

Sync EBS and P6 WBS Forecast Revenue .............................................................................. 118

Fields Supported with Prime Projects ............................................................................................... 119

Send EBS Resource to Prime Resource ................................................................................. 119

Send EBS Role to Prime Role .................................................................................................. 119


6

Send EBS Leaf Tasks to Prime Activity ................................................................................... 119

Send EBS Project Data to Prime ............................................................................................. 120

Send EBS Relationships to Prime ........................................................................................... 120

Send EBS Resource Assignments to Prime ............................................................................ 121

Send EBS Top/Middle Tasks to Prime WBS ........................................................................... 121

Send Prime Activities to EBS ................................................................................................... 121

Send Prime Project Data to EBS ............................................................................................. 122

Send Prime Relationships to EBS ........................................................................................... 122

Send Prime Resource Assignments to EBS ............................................................................ 123

Send Prime WBS Data to EBS ................................................................................................. 123

Fields Supported with Instantis EnterpriseTrack.............................................................................. 123

EnterpriseTrack Project Mapping ............................................................................................ 123

EnterpriseTrack ProjectFinance Mapping ............................................................................... 124

EnterpriseTrack ProjectFinanceElement Mapping ................................................................. 124

Fields Supported with Unifier ............................................................................................................ 125

Send EBS Resource to Unifier Role......................................................................................... 125

Send EBS ContractHeader to Unifier PurchaseOrder ............................................................ 125

Send EBS ContractDetail to Unifier PurchaseOrderDetail ..................................................... 125

Send EBS CostBudgetDetails to Unifier BudgetApprovalDetail ............................................ 126

Send EBS CostBudgetDetails to Unifier BudgetChangeDetail .............................................. 126

Send EBS CostBudgetHeader to Unifier BudgetApproval...................................................... 127

Send EBS CostBudgetHeader to Unifier BudgetChange ....................................................... 127

Send EBS Expenditure Item Detail to Unifier Payment Detail ............................................... 127

Send EBS Expenditure Item Header to Unifier Payments ..................................................... 128

Send EBS FundHeader to Unifier FundAppropriation ............................................................ 128

Send EBS FundDetail to Unifier FundAppropriationDetail ..................................................... 128

Send EBS InvoiceHeader to Unifier Invoice ............................................................................ 129

Send EBS InvoiceDetails to Unifier InvoiceDetails ................................................................. 129

Send EBS RevenueBudgetHeader to Unifier BudgetApproval .............................................. 130

Send EBS RevenueBudgetHeader to Unifier BudgetChange ................................................ 130

Send RevenueBudgetDetails to Unifier BudgetApprovalDetails ........................................... 130

Send EBS RevenueBudgetDetail to Unifier BudgetChangeDetail ......................................... 131

Sync EBS and Unifier Projects ................................................................................................. 131

Sync EBS WBS to Unifier CBS .................................................................................................. 132

Send Unifier BudgetApproval to EBS CostBudgetHeader ...................................................... 132

Send Unifier BudgetApproval to EBS RevenueBudgetHeader .............................................. 132

Send Unifier BudgetApprovalDetail to EBS CostBudgetDetail .............................................. 132

Send Unifier BudgetApprovalDetail to RevenueBudgetDetails ............................................. 133

Send Unifier BudgetChange to EBS CostBudgetHeader ....................................................... 133

Send Unifier BudgetChange to EBS RevenueBudgetHeader ................................................ 134

Send Unifier BudgetChangeDetail to EBS CostBudgetDetail ................................................ 134

Send Unifier BudgetChangeDetail to EBS RevenueBudgetDetail ......................................... 135

Send Unifier CBS to EBS WBS ................................................................................................. 135

Contents

7

Send Unifier Contract to EBS ContractHeader ....................................................................... 135

Send Unifier ContractDetail to EBS ContractDetail ................................................................ 135

Send Unifier FundAppropriation to EBS FundHeader ............................................................ 136

Send Unifier FundAppropriationDetail to EBS FundDetail ..................................................... 136

Send Unifier Payments to EBS Expenditure (Miscellaneous) ................................................ 136

Send UnifierPaymentDetail to EBS Expenditure (Miscellaneous) ......................................... 137

Send Unifier PurchaseOrder to EBS ContractHeader ............................................................ 137

Send Unifier PurchaseOrderDetail to EBS ContractDetail ..................................................... 137

Appendix C: Supported Object Mappings ..................................................................................... 139

P6 Business Objects Supported in Gateway for Event Notifications .............................................. 139

EBS Business Objects Supported in Gateway .................................................................................. 139

Legal Notices ................................................................................................................................ 141

9

Overview

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:

Oracle Prime Projects

Integrating E-Business Suite with Oracle Prime Projects enables sharing master data and project data related to projects, WBS, activities, resource assignments, relationships, resources and roles.

P6 EPPM

Integrating E-Business Suite with P6 EPPM enables sharing master data and project data related to projects, WBS, activities, resource assignments, relationships, resources, roles, expense category, and financial periods.

Instantis EnterpriseTrack

Integrating E-Business Suite with Instantis EnterpriseTrack enables sharing project header and project finance related data.

Primavera Unifier

Integrating E-Business Suite with Primavera Unifier enables sharing master and project data related to Projects, CBS, Activity, Budget Approval, Budget Changes, Contracts, Purchase Order, Fund Appropriations, Invoice and Vendor.

File Provider

Integrating E-Business Suite with an XML data source enables sharing master data and project data using Primavera Gateway.

Primavera Gateway facilitates the above integrations by delivering the following provider applications:

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.

Prime provider

The Prime provider enables you to share data from Oracle Prime Projects application.

EnterpriseTrack provider

The EnterpriseTrack provider enables you to share data with E-Business Suite application.

Unifier provider


10

The Unifier provider enables you to share master data and project data related to project, WBS, activities, resources, roles, budgets and expenditure items data with E-Business Suite.

File Provider

The File provider enables you to send and receive data to and from a file in either XML or CSV file formats. For more details on setting up an integration with the File provider, refer to the Primavera Gateway File Provider Setup Guide.

This guide describes:

How to setup the integration environment to enable data exchange between EBS and the Primavera applications listed above.

The available business objects, field mapping templates, source and destination application parameters, business flows, and synchronizations, delivered out-of-the-box in the Gateway user interface.

IT professionals or administration personnel who are responsible for setting up the integration environment, and Gateway developers responsible for creating field-mapping templates, and business flows in the Gateway user interface for your organization should use this guide.

11

Setting Up the Integration Environment

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

In This Section

Integration Installation Prerequisites ........................................................................ 11 Managing Personally Identifiable Information .......................................................... 13 Post-Installation Tasks ............................................................................................ 13

Integration Installation Prerequisites

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

EBS Integration with Oracle Prime Projects

To connect with Oracle Prime Projects, install:

E-Business Suite application

Install the database scripts for the EBS provider. For detailed instructions, see the EBSProviderR<version_number>\db folder of the EBS provider software download.

Oracle Prime Projects

Primavera Gateway application selecting the Prime and EBS providers.

To use flexible object mapping in Primavera Gateway which allows you to create custom business object mappings in Gateway and customize the EBS provider, use the gateway configuration utility to install the CustomizationXRef.xml file located in the <Primavera_Gateway_home>\providers\ebsprovider\data\moredata folder. For more details on flexible object mapping, see the Primavera Gateway Provider Customization Guide and the Online Help.

EBS Integration with EnterpriseTrack

To connect with Instantis EnterpriseTrack, install:



Oracle Instantis EnterpriseTrack

Primavera Gateway application selecting the EnterpriseTrack and EBS providers



12

EBS Integration with P6

To connect with P6 EPPM, install:



P6 EPPM application with P6 Web Services

Note: P6 Web Services supports SAML 2.0 authentication. P6 Web Services supports SAML 2.0 authentication. If you choose to use SAML 2.0 authentication between the P6 provider in Gateway and P6 EPPM, then SAML authentication must be enabled in P6 EPPM and Primavera Gateway applications. The server administrator must download the SAML token XML file on the Gateway server machine where the P6 deployment is to be created.

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 P6 EPPM Business Object Events Guide. Ensure the following features are enabled in P6 EPPM:

Eventing is enabled

JMS Queue is used for messaging

Also enable event notification in Primavera Gateway. For more details, see Configuring Gateway Domain for P6 Event Notification for On-Premises (on page 13).


To customize the EBS adapter using User Hooks refer to the EBS P6 Integration User Hooks Guide in the EBS Provider software download.

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.

EBS Integration with Unifier

To connect with Unifier, install:



Primavera Unifier

Primavera Gateway application selecting the Unifier and EBS providers


13


EBS Integration with File Provider

To connect with Primavera Gateway's File provider, install:


Primavera Gateway application selecting the File and EBS providers

For more details, see the Primavera Gateway File Provider Setup Guide.

Managing Personally Identifiable Information

Consent notices enable you to convey to your users how personally identifiable information (PII) is collected, processed, stored, and transmitted, along with details related to applicable regulations and policies. Consent notices also alert users that the action they are taking may risk exposing PII. Primavera Gateway helps you to ensure that you have requested the appropriate consent to collect, process, store, and transmit the PII your organization holds as part of Primavera Gateway data.

For more details on how to configure consent forms and manage PII data in Gateway, see Gateway Administration Guide.

Post-Installation Tasks

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

Configuring Gateway Domain for P6 Event Notification for On-Premises

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) Sign 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:


14

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. In the Type list, select File Store.

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 of 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.

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. In the subdeployment list, select the created subdeployment.

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.


15

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. For example, jms/P6ConnectionFactory.

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.

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.


16

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

Enabling Encryption Between Gateway and P6 Web Services

To ensure all requests and responses between Primavera Gateway and P6 Web Services are encrypted, you need a keystore file for encryption. There are several methods for generating a keystore file. You can use the following sequence to generate and use the same keystore file on all servers:

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.

Note: If P6 Web Services is deployed on other than a Gateway machine, then copy the keystore folder with keystore.jks to the P6 Web Services machine.

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

3) In P6 EPPM administration application:

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


17

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.

If the encryption is on in Primavera Gateway, then NONCE and CREATED are included in the header for UserName Token authentication. To enable this:

Set the NONCE value as True.

Set the CREATED value as True.

4) After encryption is set, restart P6 Web Services.

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.x, see Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12 (Doc ID 556540.1).

For EBS 12.2.x, 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.

Extending EBS 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:


18

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.

Setting up EBS Connectivity through RMI

To set up EBS connectivity through RMI from Primavera Gateway:


19

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 Version 2.0.1 (includes AppsDataSource, Java Authentication and Authorization Service, session management) Readme: Patch 13882058 (Doc ID 974949.1):

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 Primavera Gateway User Interface

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

Configuring Gateway Settings

Use the Settings dialog box to configure 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.

To configure Gateway application settings:

1) Select and then select Settings.

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

On the General tab:

Help URL: Enter the help system hosted by Oracle as http://docs.oracle.com/cd/E91470_01/help

(On-premises only) If you deployed the local Help, then 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.

Auto delete job after XX days (0 turns off auto delete): Enter the number of days that a job log can be retained before it is auto deleted. Enter 0 to turn off auto delete.

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.

Job Timeout value (in minutes): Enter the wait time interval in minutes to timeout a synchronization job.


20

Maximum File Size Limit (in MB): Enter the maximum file size limit for uploading files from Gateway user interface or from external applications. The file size limit applies to all providers and all supported file formats: CSV, XML, XLS, and XLSX.

Maximum job log size for XML format (in MB): Enter the maximum file size limit for job log size. Job log files over 10 MB are saved in JSON format by default.

Enable Configurable Consent Forms: Select this option to display the Consent Formstab on the Configurations page in Gateway. If you enable this option and then proceed to configure and enable specific consent forms, your users will need to give their consent to gain full access to specific features and functions of Gateway.

Disable logging for Jobs: For integrations with Unifier, select this option to improve performance with large sets of earned value management data.

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

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 notselected, except for spread interval data in P6.

Note: This time zone setting applies only for a P6 - Prime Projects 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. Choices include, SSL, TLS, and None.

Email Address: Enter the email address for the user who is to be notified.

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.

On the Server tab:


21

Server Log Detail Level: Indicate the type of detailed information to be included in the server log file:

Error: Select this value to display application errors in the log file.

Info: Select this value to display a brief description in the log file.

Debug: Select this value to display a general debugging event.

Off: Select this value to not generate any server log details.

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) Sign in to Primavera Gateway with administration credentials.

3) In the sidebar, select Configuration.

4) Select the Deployments tab.

5) Select Add... to invoke the Deployment wizard.

6) In the General step, name the deployment and select Next.

7) In the Deployment step, 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 18).

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

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


22

Version of Oracle EBS: Enter the EBS version. For supported versions, see the Tested Configurations document

EBS Web Service URL: 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

or

https://<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

or

https://<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:

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.


23

8) Select Test Connection ensure connectivity with Gateway.

9) Select Save.

Tips

You can also edit a deployment and select Save in any step to exit the wizard.

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:


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

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




5) Select Add... to invoke the Add Deployment wizard.

6) In the General step, select EnterpriseTrack from the Select Application Provider list, and name the deployment.

7) In the Deployment step, set up EnterpriseTrack connectivity from Gateway as follows:

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.

8) Select Test Connection ensure connectivity with Gateway is established.

9) Select Save.

Tips


Adding or Editing a P6 Deployment Connection

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

Add or edit a P6 deployment connection as follows:


24


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

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




5) Select Add... or Edit....

The Deployment wizard displays.

6) In the General step, select P6 from the Select Application Provider list, and name the deployment.


7) In the Deployment step, set up P6 connectivity from Gateway as follows:

P6 Webservices authentication type: Select the authentication type as SAML2.0 Token or UserName Token.

Username: Enter the name of the P6 administrator.

Password: If you chose UserName Token authentication, enter the case-sensitive password of the P6 administrator.

Endpoint URL: Enter the URL to connect with P6 Web Services in the format, http:<host name>:<port>/p6ws/services/SyncServiceV1

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

SAML 2.0 Token File: If you chose SAML2.0 Token authentication, then browse or enter the location of the downloaded SAML 2.0 token XML file used by P6 Web Services for authentication.

Enable Encryption: Select this option if you want to enable encryption when using P6 web services.

Keystore File: Enter or Browse... to the keystore file.

For more details on how to generate a keystore file and keystore password, see Enabling Encryption Between Gateway and P6 Web Services (on page 16).

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:

(On-premises only) 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 for On-Premises (on page 13). 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 for On-Premises (on page 13).


25

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

10) Select Save.

Tips


Adding or Editing a Prime Deployment Connection

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

Add or edit a Prime Projects deployment connection as follows:




4) Select Add... or Edit... to invoke the Deployment wizard.

5) In the General step, select Prime Projects from the Select Application Provider list, and name the deployment.

6) In the Deployment step, set up Prime Projects connectivity from Gateway as follows:

User Name: Enter the name of the user with administration access to the Prime Projects application.

Password: Enter the password to the Prime Projects application.

End Point: Enter the URL to connect to the Prime Projects application in the format: http://<server>:port/primeapi

7) Select Test Connection to ensure connectivity with Prime Projects is established.

8) Select Save.

Adding or Editing a Unifier 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 Unifier deployment connection as follows:




4) Select Add... or Edit... to invoke the Deployment wizard.

5) In the General step, select Unifier from the Select Application Provider list, and name the deployment.

6) In the Deployment step, set up Unifier connectivity from Gateway as follows:

Short Name: Enter the short name of the company used in Unifier.

Authentication Code: Enter the authentication code to use when data is integrated with Unifier from external systems using web services.


26

End Point URL: Enter the URL to connect with Unifier application in the format: http://<host name>:<port>

7) Select Test Connection to ensure connectivity with Unifier is established.

8) Select Save.

Tips


Copying Provider Deployments

To use a provider deployment in multiple distinct environments efficiently and effectively, you can simply create a copy of the current deployment and reuse. When a deployment is copied, all the attributes and values of the current provider deployment are carried over to the copy by default. Edit the copied version as needed to support the specific environment.

To copy a provider deployment:



3) Select the deployment you want to copy, select the Actions menu, and then select Copy.

The Deployment wizard displays a copy of the current provider deployment.

4) In the General step:

a. Rename the deployment in the Deployment Name field.

The default name of the copied deployment is always created with the word, Copy. For example, a copy of the Unifier Deployment will be named Unifier Deployment Copy by default.

b. Edit the description of the copied deployment in the Description field.


5) In the Deployment step:

a. Edit the connection information from Gateway as needed.

Note: Passwords cannot be copied, and must be entered manually.

b. Select Test Connection to ensure connectivity with the source or destination application.

6) Select Save to add the deployment.

27

Gateway Setup and Data Transfer Process Flow

This process flow outlines the key decision points in setting up an integration between any two ERP applications, using Gateway. Use this process flow in conjunction with chapters in this guide as well as the detailed examples provided in Gateway Online Help.

To troubleshoot issues when transferring data encountered in:

Step A of the process flow, refer to the procedures in the chapter, Working with Field-Mapping Templates.

Step B or D of the process flow, refer to the procedures in the chapter, Defining Business Flows.


28

Step C or E of the process flow, refer to the procedures in the chapter, Defining Synchronizations.

Gateway Setup and Data Transfer Process Flow

29

31

Working with Data Dictionaries

Provider data dictionaries and the Gateway data dictionary can be customized to modify fields for existing objects.

The EBS, EnterpriseTrack, P6, and Prime Projects data dictionaries can be modified to:

Edit existing objects

Add, edit, and delete existing fields

The Gateway, Unifier, and File data dictionaries support additional features. For more details, refer to the Features of Provider Data Dictionaries (on page 31) and Primavera Gateway File Provider Setup Guide.

A provider object can be modified by using the Objects and Fields wizard from the Data Dictionary menu.

In This Section

Features of Provider Data Dictionaries .................................................................... 31 Editing Objects and Fields in Data Dictionaries ....................................................... 34 Deleting Fields from Data Dictionaries ..................................................................... 36

Features of Provider Data Dictionaries

All providers extend complete or partial support for objects and fields that are dynamically created in an enterprise application. For example, when new business process objects and fields created in Unifier user interface, corresponding Gateway objects can be created within Unifier to support a Gateway integration. In Gateway, you can add and edit new objects and fields in File, Gateway, and Unifier data dictionaries corresponding to objects created in the native ERP application. All other provider data dictionaries allow you to only add, edit, and delete fields within a business object.

The following table outlines the features supported by each provider data dictionary.

Provider Data Dictionaries

Support Complete Partial

Features Gateway File Unifier EBS EnterpriseTrack

MSP P6 Prime Projects

VCP

Add Features at Object Level

Add objects to data dictionary

Yes Yes Yes No No No No No No


32





VCP

Copy objects to data dictionary


Add fields to an object

Yes Yes Yes Yes Yes Yes Yes Yes Yes

Add flow type (master or project) supported for an object


Add Flow Direction (source, destination, or both) for an object


Add cross-reference key mappings for an object


Add Features at Field Level

Add fields to an object


Edit Features at Object Level

Edit object name and description


Edit fields supported by an object


Edit flow type (master or project) supported for an object

Yes Yes Yes Yes No No No No No

Edit flow direction (source, destination, or both) of an object

Yes Yes Yes Yes No No No No No


33





VCP

Edit cross-reference key mappings of an object


Edit Features at Field Level

Edit fields supported by an object


Delete Features at Object Level

Delete objects Yes Yes Yes No No No No No No

Delete fields supported by an object


Delete flow type (master or project) supported for an object


Delete flow direction (source, destination, or both) of an object


Delete cross-reference key mappings of an object


Delete Features at Field Level

Delete fields supported by an object



34

Editing Objects and Fields in Data Dictionaries

Depending on the provider and the data dictionary selected, a provider object can be edited at two levels using the Objects and Fields wizard:

Editing at the object level

At the object level, the following information can be updated for an object:

Name and description of the object

Fields supported by the object

Flows supported for the object

Cross-reference keys of the object

Editing an object at the field Level

At the field level, add, update or delete fields supported by the object.

Editing at the Object Level

Edit a provider object at the object level as follows:

1) In the sidebar, select Data Dictionary.

2) Select any of the following provider data dictionaries: Gateway, File, or Unifier.

3) Select the row listing the object you want to edit, and then select Edit... on the Data Dictionary page.

The Object and Fields wizard displays.

4) If you edit an object in the Gateway, File, or Unifier data dictionaries, select the General step to edit the Object Name and Description of the object.

Otherwise select Next.


5) In the Fields step, add fields, or edit current fields supported by the business object:

a. Enter a Field Name for the new field.

b. In the Field Type field, select the data type of the field. Choices include: Boolean, DateTime, Double, ForeignKey, Integer, and String.

c. If you add a ForeignKey field, then select the Join to Object to join the new field with an existing object in that provider's dictionary.

d. Select Read Only Field to indicate the field value cannot be modified.

e. Select any of the following actions:

Select Add to add the field to the field table.

Select Update to edit an existing field in the field table.

Select Reset to undo all the changes made in the step.

Select Delete to delete a field from the field table.

f. Repeat this sequence in the Fields step to add multiple fields to a provider object.

6) If you edit an object in the Gateway, File, or Unifier data dictionaries, then select the Flow Control step to edit the combination of Flow Type and Flow Direction to be associated with the provider object only. Select any of the following actions:


35

Select Add to add the Flow Type and Flow Direction combination.

Select Delete to delete an existing Flow Type and Flow Direction combination.

7) In the Cross Reference step, setup the cross-reference key field to be associated with the Gateway object.

a. In the Key Field field, select the field to be used as the cross-reference key for the object in Gateway.

b. In the Gateway Objects field, select the Gateway business object from the drop-down to map the cross-reference key of the provider object.

Note: You can also map the provider object to a new Gateway object that has already been added using this procedure.

c. Select any of the following actions:

Select Add to add the cross-reference key and Gateway object combination to the Key table.

Select Delete to delete a cross-reference and business object combination from the Key table.

8) In the Summary step, review a summary of all selections made.

a. Expand each step title to review the selections made in that step.

b. Select any of the following actions:

Select Back to navigate to a specific step and make changes.

Select Save toto confirm the changes made to the provider object.

Note: See the Gateway Online Help for an example of editing at the object level.

Editing at the Field Level

Edit a provider object at the field level to update the list of fields supported by the object as follows:

1) In the sidebar, select Data Dictionary.

2) Select a provider data dictionary. For example, Prime.

A list of objects supported in the data dictionary displays.

3) Select an object in the data dictionary. For example, Currency.

A list of fields supported by the object displays.

4) Select Edit....

The Object and Fields wizard displays.

5) In the General step, select Next.


6) In the Fields step, add fields, or edit current fields supported by the object:

a. Enter a Field Name for the new field.


36

b. In the Field Type field, select the data type of the field. Choices include: Boolean, DateTime, Double, ForeignKey, Integer, and String.

c. If you add a ForeignKey field, then select the Join to Object to join the new field with an existing object in that provider's dictionary.

d. Select Read Only Field to indicate the field value cannot be modified.

e. Select any of the following actions:

Select Add to add the field to the field table.

Select Reset to undo all the changes made in the step.

Select Delete to delete an existing field from the field table.

f. Repeat this sequence in the Fields step to add multiple fields to a provider object.

7) In the Flow Control, and Cross Reference steps, select Next.

8) In the Summary step, review a summary of all selections made.




Select Save to confirm the changes made to the provider object.

Deleting Fields from Data Dictionaries

Fields can be deleted as follows:

1) In the sidebar, select Data Dictionary, and choose a provider data dictionary.

2) Select a provider object.

3) Select the field to delete, select the Actions menu and then select Delete.

4) If the field is associated with a field-mapping template, a confirmation message displays.

Note: If the field is associated with a field-mapping template, then the field will be deleted from all mapping templates.

5) Select Confirm to delete the field.

37

Defining Field-Mapping Templates

Any object in a provider's data dictionary can be associated with one or more Gateway objects, and each Gateway object can be associated with one or more field-mapping templates. The field-mapping templates determine how a Gateway object, and the corresponding provider object with its supported fields are used in a business flow. To create a business flow that processes specific data between any two applications, you must select the field-mapping template supporting that Gateway object in a particular business flow.

Essentially, the field-mapping templates which connect provider objects with Gateway objects determine where the data will reside in the destination application.

This chapter describes procedures to add, copy and delete field-mapping templates in Gateway.

In This Section

Adding or Editing Field-Mapping Templates ............................................................ 37 Copying Field-Mapping Templates .......................................................................... 38 Deleting Field-Mapping Templates .......................................................................... 39

Adding or Editing Field-Mapping Templates

Gateway delivers field-mapping templates for Gateway objects that can be used in business flows. Alternatively, you can also create additional field-mapping templates to suit your requirements.

Note: Field-mapping templates can be created using Groovy code or the canonical format (Direct) format of Gateway.

To add field mapping templates:


2) Select the Customization tab.

3) Select a Gateway business object from the drop-down and select Add... or Edit....

All field-mapping templates associated with the Gateway business object display in the field-mapping template table.

4) To add a field-mapping template, select Add....

or

Select a field mapping template in the Field Mapping Name column and then select Edit....

5) In the General step:

a. Enter a name for the field mapping template in the Template Name field.

b. Select the type of template being created from the Template Type drop-down.

Select Groovy if the template will use Groovy code.


38

Select Direct if the template will use the canonical format of Gateway.

c. Select a provider in Provider 1 drop-down.

d. Select a provider in the Provider 2 drop-down.

e. Select the object to be supported by the field mapping template in the Provider 1 Objectdrop-down.

f. Select the object to be supported by the field mapping template in the Provider 2 Objectdrop-down.

g. (Optional) Select Use Criteria Step to set a specific condition for using the field-mapping template in the Criteria step of the wizard.


6) In the Criteria step, specify the condition for field mappings:

a. Select the field from the Fields drop-down of Provider 1.

b. Select the field from the Fields drop-down of Provider 2.

c. Enter the Conditions to be satisfied by Provider1 and Provider 2 fields respectively.

d. Select Validate Condition to validate the syntax entered in the Condition text box for the provider fields.

7) In the Mappings step, specify field mappings supported by the template:

a. Select Auto Generate to generate mappings for fields that are common to both providers and Gateway.

For identical fields existing in both providers and Gateway, field mapping names are auto-suggested and populated for each provider.

b. Specify additional field mappings as follows:

1. Select the fields supported by the template in the drop-downs of both providers, and Gateway.

2. Select Add.

3. Repeat Step b to add multiple fields.

8) In the Summary step:

a. Review all the selections made in the previous steps.



Select Save to add the field-mapping template.

Note: Multiple provider objects can be mapped to a single provider object. For example, when you select Sample as Provider 1 and P6 as Provider 2, both objects in the Sample provider, WorkOrder and WBS, map to the WBS object in P6.

Copying Field-Mapping Templates

Copy a field-mapping template if you want to maintain similar versions of an existing template that can be used for different purposes within a specific integration scenario.

Defining Field-Mapping Templates

39

Note: Providers and provider objects cannot be changed when a template is copied.

To copy a field-mapping template:



3) In the Field Mapping Templates section, select a Gateway object from the drop-down.

A master list of all mapping templates supporting the Gateway business object across all integrations displays.

4) In the Field Mapping Name column, select a template that you want to copy, then select the Actions menu, and select Copy.

The Template wizard displays a copy of the selected mapping template.

Editing the Template Copy

Edit the template copy as follows:

1) In the General step, rename the template and select Next.


2) In the Mappings step, select the field that is to be supported as follows:

3) Select the field to be supported in the data dictionary of the providers selected as Provider 1and Provider 2, and Gateway, and then select Add.

4) (Optional) Select field-mappings that need not be supported and then select Delete.

5) In the Summary step, review all the selections made in the previous steps:




Select Save to add the provider object to the data dictionary.

The mapping template can now be used in a business flow.

For a detailed example. see Gateway Help.

Deleting Field-Mapping Templates

Delete mapping templates as follows:



3) In the Field Mapping Name column, select the mapping template, then select the Actions menu and select Delete.

4) In the Confirmation dialog box, select Confirm to acknowledge the deletion.

41

Defining Business Flows

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

Adding Business Flows ........................................................................................... 41 Copying Business Flows ......................................................................................... 42 Using Business Flows Delivered in Gateway ........................................................... 42 Connecting with P6 EPPM ...................................................................................... 43 Connecting with Instantis EnterpriseTrack ............................................................... 54 Connecting with Oracle Prime Projects ................................................................... 60 Connecting with Unifier ............................................................................................ 68

Adding 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 sidebar, select Flow Type.

2) Select Project Data or Master Data 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.

3) Select Business Flows.

4) Select Add.

5) 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.


42

Copying Business Flows

When you need to create a new business flow similar to an existing flow, copy the current business flow and then edit as needed.

To copy a business flow:

1) In the sidebar, select Flow Type.

2) Select Master Data or Project Data.

3) Select the row listing the business flow you want to copy, select the Actions menu and then select Copy.

The Business Flow wizard displays a copy of the current business flow with the word Copy. For example, Send Unifier Roles to P6 Copy.

4) In the General step, rename the business flow and select Next.


5) In the Mappings step:

a. Select the Gateway Object Name and the Field-Mapping Name for each object to be supported in the business flow.

b. In the Applied For field, select the type of actions that will be performed for each object:

Create: Creates new values

Update: Updates existing values

Both: Create and update values

Note: You can also add a new field-mapping template for a business object in the Customization tab, and then select it in the Mappingsstep.

6) In the Source App Parameters step, select the source field values, if any, and the attributes of the source parameters.

7) In the Destination App Parameters step, select the destination field values, and the behavior of the destination parameters.

8) In the Summary step, review all the selections made in the previous steps:




Select Save to add the duplicated business flow.

Using Business Flows Delivered in Gateway

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

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

2) Select Business Flows.


43

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 43)

Project Data Flow Type (on page 46)

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 43). The Synch to Send 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 44).

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

FinancialPeriod FinancialPeriod FinancialPeriod

Resource Resource Resource

ResourceRate ResourceRate ResourceRate

Role Role Role

RoleRate RoleRate RoleRate


44

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 95).

EBS Source Business Objects

Associated Field Mapping Templates

Used in ...

ExpenseCategory Send EBS Financial Elements to P6 Expense Category

Send EBS Master Data to P6 business flow

FinancialPeriod Send EBS Financial Period to P6 Financial Period


Resource Send EBS Resource to P6 Resource


ResourceRate Send EBS Resource Rates to P6 Resource Rates


Role Send EBS Role to P6 Role Send EBS Master Data to P6 business flow

RoleRate Send EBS RoleRates to P6 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.


45

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 89). 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.

Note: EBS is not set up to be a destination provider in a master data flow.

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.


46

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 46). The following types of project data business flows are delivered for an EBS - P6 integration in Gateway:

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 81).

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 47).

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


P6 Destination Business Object

Activity Activity Activity

ExpenditureItemDetails ActivityExpense ActivityExpense

ExpenditureItemDetails ResourceAssignment ResourceAssignment

FinancialElementAssignment ActivityExpense ActivityExpense

Project Project Project

Relationship Relationship Relationship


ResourceAssignment ResourceAssignment ResourceAssignment

WBS WBS WBS

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


47

P6 Source Business Objects Gateway Business Object

EBS Destination Business Object


ActivityExpense ActivityExpense FinancialElementAssignment




WBS WBS WBS

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 95).

When EBS is the source application, the following business objects and field mapping templates can be used to transfer data to P6 in a business flow:


Associated Field Mapping Templates Used in ...

Activity Sync EBS and P6 Activity Cost Budget

Send EBS Project(s) to P6 business flow

Sync EBS and P6 Activity Forecast Revenue

Sync EBS and P6 Activity

Send EBS Actual Progress to P6

Sync EBS and P6 Activity Forecast Budget

Send P6 Actual Progress to EBS

Sync EBS and P6 Activity Revenue Budget

Activity Mapping - Scheduled Dates

ActivityExpense Sync EBS and P6 Financial Element Assignments


48



Sync EBS and P6 Financial Assignment Cost Budgets

Sync EBS and P6 Financial Assignment Revenue Budget

Sync EBS and P6 Financial Assignment Forecast Budget

Sync EBS and P6 Financial Assignment Forecast Revenue

Send P6 EXP Actuals to EBS

Send EBS Actuals to P6 EXP

Send EBS Cost Code Details to P6

Send P6 Cost Code Details at Activity Expense to EBS

Project Sync EBS and P6 Projects Send EBS Project(s) to P6 business flow

Sync EBS and P6 Project Cost Budget

Sync EBS and P6 Project Revenue Budget

Sync EBS and P6 Project Forecast Budget

Sync EBS and P6 Project Forecast Revenue

Relationship Sync EBS and P6 Activity Relationships

Send EBS Project(s) to P6 business flow

ResourceAssignment

Sync EBS and P6 Resource Assignments

Sync EBS and P6 Assignment Cost Budget

Sync EBS and P6 Assignment Revenue Budget

Sync EBS and P6 Assignment Forecast Budget

Sync EBS and P6 Assignment Forecast Revenue


49




Send P6 Cost Code Details to EBS

Send EBS Actuals to P6

Send P6 RAS Actuals to EBS

WBS Sync EBS and P6 WBS Send EBS Project(s) to P6 business flow

Sync EBS and P6 WBS Cost Budget

Sync EBS and P6 WBS Revenue Budget

Sync EBS and P6 WBS Forecast Budget

Sync EBS and P6 WBS Forecast Revenue

When P6 is the source application, the following business objects and field mapping templates can be used to transfer data to EBS in a business flow:

P6 Source Business Objects


Activity Sync EBS and P6 Activity the following business flows:

Send P6 Project(s) to EBS


Sync EBS and P6 Activity Cost Budget




ActivityExpense Sync EBS and P6 Financial Element Assignments



50







Project Sync EBS and P6 Projects the following business flows:







Relationship Sync EBS and P6 Activity Relationships

the following business flows:



ResourceAssignment








51



Send P6 Actuals to EBS

WBS Sync EBS and P6 WBS the following business flows:







Setting Provider- Specific Parameters





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 any of the following fields as comma-separated values: Project Number, Descriptive Flexfields, or Class Category. Select Add row to enter multiple ERP Project business objects.

Project Plan


52

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

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 budgets from EBS.

Primavera Calendar Working Hours

Use this setting to specify the default working hours per day in the project calendar of 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.

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 for each EBS Project Accounting to transfer budgets from 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?



53


EBS Responsibility for Project Synch from third-party

Use this setting to define the EBS responsibility key of responsibility name to determine the operating unit to create a project in a specific operating unit of EBS of a multi-operating unit EBS environment.

EBS User Name for Project Synch from third-party

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

Publish Workplan after synchronization?

Use this setting to determine whether to publish the workplan structure in EBS after the synchronization.

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 Project data in P6. You can identify project data based on Project Ids, EPS Ids, Project Code, Project Code Type Name, and Project Code Value. You can identify a project using any of the following criteria:

Entering multiple values for Project Id and Project Code as comma-separated values.

Entering multiple values for EPS Id as comma-separated values.

Entering multiple Project Codes with values in the following format:Type Name = Value Name

For example:

a. In the Fields list, select Project Code.

b. In the Value list, enter: Integrate to P6 = Yes

c. Select Add Row.

To specify a second condition for the Project Code:

d. In the Fields list, select Project Code.

e. In the Value list, enter: Sales Country Code = DE

Select Add Row.

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. Select Add row to enter multiple Activity business objects.

Resource Assignment Filter


54

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. Select Add Row to enter multiple ResourceAssignment objects.

Baseline Ids

Use this setting to select the baseline information to transfer from P6. Choices include: No Baseline, Baseline Names, Project Baseline, and All Baselines. 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 synchronization job is usually split into multiple child jobs with each child job transferring data in each project. By default all child jobs are executed simultaneously. Use this setting to determine whether to synchronize data from 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.


55

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 and Configuration 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.


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

Send Enterprise Track Project(s) to EBS

Send EBS Project(s) to Enterprise Track


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 56).

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


ProjectFinance ProjectFinance CostBudgetHeader

ProjectFinanceElement ProjectFinanceElement

CostBudgetDetails

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


CostBudgetHeader ProjectFinance ProjectFinance


56


EnterpriseTrack Destination Business Object

CostBudgetDetails ProjectFinanceElement

ProjectFinanceElement


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 95).

EnterpriseTrack Source Business Objects


Used In...

Project EnterpriseTrack Project Mapping

Send Enterprise Track Project(s) to EBS business flow

ProjectFinance EnterpriseTrack ProjectFinance Mapping

ProjectFinanceElement EnterpriseTrack ProjectFinanceElement Mapping"



Used in...

Project EnterpriseTrack Project Mapping

Send EBS Project(s) to Enterprise Track business flow

CostBudgetHeader EnterpriseTrack ProjectFinance Mapping

CostBudgetDetails EnterpriseTrack ProjectFinanceElement Mapping


57


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.



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


58

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.

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.





ERP Project Filter


Project Plan



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



Budget Type


59

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



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

Project Plan




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


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


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


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 for transferring data to EBS.



Save data to EBS if there are errors




EBS Responsibility for Project Synch from third party


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.



60




Connecting with Oracle Prime Projects

For EBS integration with Oracle Prime Projects, the following flow types are supported:

Master Data Flow (on page 60)

Project Data Flow (on page 62)

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 Oracle Prime Projects applications.

Master Data Flow

Use the Master Data flow type to transfer master data business objects from EBS to Prime identified in the Business Objects Supported in Master Data Flow. The following types of master data business flows are delivered for an EBS - Prime Projects integration in Gateway:

Send EBS Resource to Prime Resource

Send EBS Role to Prime Role


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 61).

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


Prime Destination Business Object


Role Role Role


61

Field Mapping Templates for Master Data Business Objects




Used in ...

Resource Send EBS Resource to Prime Resource

Send EBS Resource to Prime Resource business flow

Role Send EBS Role to Prime Role Send EBS Role to Prime Role business flow


Based on the role of EBS and Prime 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.









Note: EBS is not set up to be a destination provider in a master data


62

flow.

Prime Provider Application Parameters

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

Prime Location Filter

Use this setting to specify the Prime location filter.

Workspace Location

Use this setting to specify the default workspace and populate it in a synchronization. If the value is set in Primavera Gateway, then Prime Projects will check if the Prime Workspacefield value exists and will use it to create the project.

EBS must send all global data assigned to the project with the project flow and all of that global data must be assigned to the workspace to determine where the project will be created in Prime Projects.



Only delete data that has been linked previously with the source application?

To use this parameter, you must also select the parameter, Delete data that no longer exists in the source application? During a synchronization, when the data is compared between the source and the destination application, data that has been added only in the destination application will not be deleted. However, if you deleted source data that was previously synced in the destination application, it will also be deleted from the destination application.

Project Data Flow

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

Send EBS Project(s) to Prime

Send Prime Project(s) to EBS

Instantiate EBS Project(s) from Prime

Instantiate Prime Project(s) from EBS

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 81).


63


The following business objects are supported between EBS and Prime 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.

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


Prime Destination Business Object






WBS WBS WBS

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

Prime Source Business Objects Gateway Business Object






Send


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 95).

When EBS is the source application, the following business objects and corresponding field mapping templates can be used to send data to Prime:


64



Used in ...

Activity Send EBS Leaf Tasks to Prime Activity

Send EBS Project(s) to Prime business flow

Project Send EBS Project Data to Prime





Relationship Send EBS Relationships to Prime


Resource Send EBS Resource to Prime Resource

ResourceAssignment Send EBS Resource Assignments to Prime

WBS Send EBS Top/Middle Tasks to Prime WBS


When Prime is the source application, the following business objects and corresponding field mapping templates can be used to send data to EBS:

Prime Source Business Objects


Used in ...

Activity Send Prime Activities to EBS Send Prime Project(s) to EBS business flow

Project Send Prime Project Data to EBS




Relationship Send Prime Relationships to EBS

Send Prime Project(s) to EBS business flow

ResourceAssignment Send Prime Resource Assignments to EBS

WBS Send Prime WBS Data to EBS Send Prime Project(s) to EBS business flow


65







ERP Project Filter


Project Plan






Budget Plan Type




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

Project Plan




66




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


Planning Resource List (Required only for project creation in EBS PA)


Budget Plan Type




Primavera Calendar Working Days


Save Data to EBS if there are errors


EBS Responsibility for Project Sync from third party


EBS User Name for Project Sync from third party




Send Bulk Task to EBS? (shared structure and workplan versioning disabled)

This parameter helps to transfer five thousand and above tasks in EBS with good performance with Task API (such as save data to EBS if there are errors parameter enabled.) couldn’t able to do.






67



Prime Provider Application Parameters

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

Prime Project Filter

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

You can identify a project using any of the following criteria:

Entering multiple values for Project Id and Project Code as comma-separated values.

Entering multiple values for Workspace Id as comma-separated values.

Entering multiple Project Codes with values in the following format:Type Name = Value Name

For example:

a. In the Fields list, select Project Code.

b. In the Value list, enter: Integrate to Prime = Yes

c. Select Add Row.

To specify a second condition for the Project Code:

d. In the Fields list, select Project Code.

e. In the Value list, enter: Sales Country Code = DE

f. Select Add Row.

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

Workspace Location

Use this setting to specify the default workspace and populate it in a synchronization. If the value is set in Primavera Gateway, then Prime Projects will check if the Prime Workspacefield value exists and will use it to create the project.

EBS must send all global data assigned to the project with the project flow and all of that global data must be assigned to the workspace to determine where the project will be created in Prime Projects.




68





Connecting with Unifier

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

Master Data Flow Type (on page 68)

Project Data Flow Type (on page 71)

Note: Data files specific to EBS -unifier integration are available in the <Primavera_Gateway_Home>\EBSProvider\Data\Unifier folder of the Primavera Gateway installation. Ensure you run the Gateway configuration utility to install the Unifier folder to support this integration. For more details on using the configuration utilities, refer to the Primavera Gateway Installation and Configuration Guide.

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 Unifier applications.

Master Data Flow Type

Use the Master Data flow type to transfer project data business objects identified in the Business Objects Supported in Master Data Flow (on page 69). The Send EBS Resource to Unifier Role master data business flows is delivered for an EBS - Unifier integration in Gateway.

A business flow can use 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 master data business flows to transfer master data. For more details, see Defining Synchronizations (on page 81).


69


The following business objects are supported between the Unifier 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 Template for Master Data Business Objects (on page 69).

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


Unifier Destination Business Object

CustomerHeader Vendor Vendors

CustomerDetails VendorDetail VendorsDetail


Role Role Role

Field-Mapping Template for Master Data Business Objects



Associated Field Mapping Template

Used in ...

Resource Send EBS Resource to Unifier Role

Send EBS Resource to Unifier Role business flow

Role none delivered none delivered

Vendor Send EBS Customer Header to Unifier Vendors

VendorDetail Send EBS Customer Detail to Unifier VendorsDetail


Based on the role of EBS and Unifier 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.


70








Exclude Material Resources from Import (Optional)



Note: EBS is not set up to be the destination provider in the master data flow.

Unifier Provider Application Parameters

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

Business Process Name

Use this setting to enter the name of the business process to which the data should be associated in Unifier.

Business Process Detail Tab Name

Use this setting to enter the Detail tab name of the business process to which the data should be associated in Unifier.

Line Item Identifier

Use this setting only when you need to update line items. Enter the name of the data element (not label) that is to be updated in the Detail tab of the business process.





71

Note: Unifier is not set up to be the source provider in the master data flow.


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

Send EBS Budget to Unifier Initial Budget

Send EBS Expenditure Items to Unifier Payments

Send EBS Projects/WBS to Unifier Projects/CBS

Send Unifier Projects to EBS Projects

Send Unifier Initial Budget to EBS Budget

Each business flow can use 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 81).


The following business objects are supported between the Unifier and EBS applications in the project 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 Project Data Business Objects (on page 72).

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



ContractHeader PurchaseOrder ProjectCommits

ContractDetails PurchaseOrderDetail ProjectCommitsDetail

CostBudgetHeader BudgetApproval OtherProjectCosts

CostBudgetDetails BudgetApprovalDetail OtherProjectCostsDetail

CostBudgetHeader BudgetChange OtherProjectCosts

CostBudgetDetails BudgetChangeDetail OtherProjectCostsDetail

ExpenditureItemHeader Payment OtherProjectCosts

ExpenditureItemDetails PaymentDetail OtherProjectCostsDetail


72



FundHeader FundAppropriationDetail

OtherProjectCostsDetail

InvoiceHeader Invoice ProjectInvoices

InvoiceDetails InvoiceDetail ProjectInvoicesDetail

RevenueBudgetHeader BudgetApproval OtherProjectCosts

RevenueBudgetDetails BudgetApprovalDetail OtherProjectCostsDetail

RevenueBudgetHeader BudgetChange OtherProjectCosts

RevenueBudgetDetails BudgetChangeDetail OtherProjectCostsDetail


WBS CBS CBS

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

Unifier Source Business Objects

Gateway Business Object


OtherProjectCosts BudgetChange RevenueBudgetHeader

OtherProjectCosts Payment ExpenditureItemHeader

OtherProjectCosts PaymentDetail ExpenditureDetails

OtherProjectCostsDetail BudgetApprovalDetail RevenueBudgetDetails

OtherProjectCostsDetail BudgetChangeDetail RevenueBudgetDetails

OtherProjectCostsDetail PaymentDetail ExpenditureDetails

OtherProjectCostsDetail BudgetChangeDetail RevenueBudgetDetails


CBS CBS WBS

Field-Mapping Templates for Project Data Business Objects

The following table 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 95).


73

When EBS is the source application, the following business objects and corresponding field mapping templates can be used to send data to Unifier:



Used in ...

Activity none delivered none delivered

BudgetApproval Send EBS CostBudgetHeader to Unifier BudgetApproval




Send EBS RevenueBudgetHeader to Unifier BudgetApproval

BudgetApprovalDetail Send EBS CostBudgetDetails to Unifier BudgetApprovalDetail




Send RevenueBudgetDetails to Unifier BudgetApprovalDetails

BudgetChange Send EBS CostBudgetHeader to Unifier BudgetChange

Send EBS Budget to Unifier Initial Budget business flow

Send EBS RevenueBudgetHeader to Unifier BudgetChange

BudgetChangeDetail Send EBS CostBudgetDetails to Unifier BudgetChangeDetail

Send EBS Budget to Unifier Initial Budget business flow

Send EBS RevenueBudgetDetail to Unifier BudgetChangeDetail

FundAppropriation Send EBS FundHeader to Unifier FundAppropriation

FundAppropriationDetail Send EBS FundDetail to Unifier FundAppropriationDetail


74



Used in ...

Invoice Send EBS InvoiceHeader to Unifier Invoice

InvoiceDetail Send EBS InvoiceDetails to Unifier InvoiceDetails

Payment Send EBS Expenditure Item Header to Unifier Payments

Send EBS Expenditure Items to Unifier Payments business flow

PaymentDetail Send EBS Expenditure Item Detail to Unifier Payment Detail


Project Sync EBS and Unifier Projects the following business flows:





PurchaseOrder Send EBS ContractHeader to Unifier PurchaseOrder

PurchaseOrderDetail Send EBS ContractDetail to Unifier PurchaseOrderDetail

WBS Sync EBS to Unifier CBS Send EBS Projects/WBS to Unifier Projects/CBS business flow

When Unifier is the source application, the following business objects and corresponding field mapping templates can be used to send data to EBS:



Used in ...

Activity none delivered none delivered

BudgetApproval Send Unifier BudgetApproval to EBS CostBudgetHeader

Send Unifier Initial Budget to EBS Budget business flow


75



Used in ...

Send Unifier BudgetApproval to EBS RevenueBudgetHeader

BudgetApprovalDetail Send Unifier BudgetApprovalDetail to EBS CostBudgetDetail


Send Unifier BudgetApprovalDetail to RevenueBudgetDetails

BudgetChange Send Unifier BudgetChange to EBS CostBudgetHeader


Send Unifier BudgetChange to EBS RevenueBudgetHeader

BudgetChangeDetail Send Unifier BudgetChangeDetail to EBS CostBudgetDetail


Send Unifier BudgetChangeDetail to EBS RevenueBudgetDetail

CBS Send Unifier CBS to EBS WBS

Contract Send Unifier Contract to EBS ContractHeader

ContractDetail Send Unifier ContractDetail to EBS ContractDetail

FundAppropriation Send Unifier FundAppropriation to EBS FundHeader

FundAppropriationDetail Send Unifier FundAppropriationDetail to EBS FundDetail

Invoice Send EBS InvoiceHeader to Unifier Invoice

InvoiceDetail Send EBS InvoiceDetails to Unifier InvoiceDetails

Payment Send Unifier Payments to EBS Expenditure (Miscellaneous)


76



Used in ...

PaymentDetail Send UnifierPaymentDetail to EBS Expenditure (Miscellaneous)

Project Sync EBS and Unifier Projects the following business flows:



PurchaseOrder Send Unifier PurchaseOrder to EBS ContractHeader

PurchaseOrderDetail Send Unifier PurchaseOrderDetail to EBS ContractDetail


Based on the role of EBS and Unifier 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 Developer or 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.



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

ERP Project Filter



77

Project Plan






Budget Type




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

Project Plan






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


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


Budget Type






Save data to EBS if there are errors




78


EBS Responsibility for Project Synch from third-party


EBS User Name for Project Synch from third-party






Unifier Provider Application Parameters

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

Unifier Project Filter

Use this setting to identify and transfer project business objects in Unifier. Enter multiple values for the following fields as comma-separated values: by objects, fields, and values: ImportProjectIds, and ShellAttribute. Select Add row to transfer multiple Project business objects.

Source Business Process Name

Use this setting to enter the name of a business process in Unifier.

Record Number(s)

Use this setting to enter record numbers in Unifier.

Cost Column Name

Use this setting to enter the cost column names in Unifier.

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

Unifier Project Location

Use this setting to enter the project location in Unifier.

Unifier Project Template Number

Use this setting to enter the template number to be associated with the project created in Unifier.

Business Process Name

Use this setting to enter the name of the business process to which the data should be associated in Unifier.


79

Business Process Detail Tab Name

Use this setting to enter the Detail tab name of the business process to which the data should be associated in Unifier.

Line Item Identifier

Use this setting only when you need to update line items. Enter the name of the data element (not label) that is to be updated in the Detail tab of the business process.



81

Defining Synchronizations

A synchronization in Gateway is a job set up to run on-demand or on schedule to exchange data between the source and destination applications.

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 (OOTB) business flows delivered in Gateway, a corresponding synchronization is also 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.

This chapter outlines procedures to set up and run synchronizations in Gateway.

In This Section

Master Data Synchronization................................................................................... 81 Project Data Synchronizations ................................................................................. 81 Adding Synchronization Jobs .................................................................................. 82 Copying Synchronizations ....................................................................................... 83 Using Synchronizations Delivered in Gateway ........................................................ 84

Master Data Synchronization

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

For an EBS - Unifier integration in Gateway, the Send EBS Resource to Unifier Role master data synchronization is delivered out-of-the-box to support the delivered Send EBS Resource to Unifier Role master data business flow listed in in Master Data Flow Type (on page 68).

For an EBS - Prime integration in Gateway, the following master data synchronizations are delivered out-of-the-box to support the delivered master data business flow listed in Master Data Flow (on page 60):



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:


82

EBS - Prime Integration

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



Send EBS Project(s) to Prime


EBS - P6 integration



Send EBS Project(s) to P6


EBS - EnterpriseTrack Integration


Send EBS Project(s) to Enterprise Track

Send Enterprise Track Project(s) to EBS

EBS - Unifier Integration







Adding 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.

Prerequisites

Configure application deployment connections for the source and destination applications in the data flow.

Business flows must be setup for the data transfer.

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.

Procedure

To transfer data between applications:

Defining Synchronizations

83

1) In the sidebar, select Synchronizations, and then select Add....

2) Follow the steps in the Synchronization wizard to name and configure the synchronization.

Note: If you edit a synchronization and change the business flow, then you must review and update the parameters as needed.

3) Select Save in any step of the wizard to save the changes and exit the wizard instantly.

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 the Actions menu and then select Run with Review.

Note: If you are a user or administrator with no data access privileges, once a synchronization is Run with Review, you cannot review the actual data being transfered in each step of a job nor download the job details. When you select the Review link, an error message, Insufficient Permissions, is displayed.

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

Note: (On-premises only) 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 Primavera Gateway Provider Development Guide.

To schedule the synchronization to run at a certain date and time, or a specific sequence of synchronizations, select the synchronization, select the Actions menu and then select Edit Schedule....

5) To delete a synchronization:

a. Highlight the synchronization.

b. Select the Actions menu and then select Delete.

Select Yes in the Confirmation dialog box.

Copying Synchronizations

When you need to create a new synchronization similar to an existing synchronization, copy the current synchronization and then edit the copy as needed.

To copy a synchronization in Gateway:

1) In the sidebar, select Synchronizations.

2) Select the synchronization you want to copy, then select the Actions menu and select Copy.

The Synchronization wizard displays a copy of the current synchronization.


84

3) In the Flow and Deployments step:

a. Rename the synchronization in the Synchronization Name field.

The default name of the duplicate synchronization is always created with the word, Copy. For example, Send Prime Project Data to P6 Copy.

b. Select the business flow that is to be used by the synchronization in the Business Flowfield.


4) In the Parameters step, edit the value of each parameter as needed.

5) In the Summary step, review a summary of all the selections made in the previous steps.

Select any of the following actions:


Select Save to add the synchronization.

The synchronization is now available for running and monitoring.

Using Synchronizations Delivered in Gateway

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

1) In the sidebar, select Synchronizations, and then select Edit....

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

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

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

To review the data that will be moved from the source application before the synchronization is executed, select a synchronization, select the Actions menu, and then select Run with Review.

To schedule an event-based synchronization, select a synchronization, select the Actionsmenu, and then select Run on Event.

Note: (On-premises only) 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 Primavera Gateway Provider Development Guide.

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

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

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

Transferring Data between Applications: Example

85


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.

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.


86

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.

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.

1) Select Synchronizations.

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.


87

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.

89

Appendix A: About Flow Steps

In This Section

Define the Flow Steps in a Flow .............................................................................. 89

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 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.

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.

(Optional) External Custom Step

This step loads the external custom step if defined for a data flow specific to an integration. The external custom step can be added anywhere in the above flow sequence.


90

Flow Sequence When Using Master Data

The Master data flow type, if applicable to an integration, is used to specifically transfer master data between two applications or distinct environments of the the same application. For example, to transfer data from a P6 Testing environment to P6 production environment or transfer data from P6 to Prime. 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 master 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.

Flow Sequence When Using Project Data

The Project data flow type, if applicable to an integration, is used 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:

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


91

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.

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:


92

@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); }

}


93

Flow Sequence When Using External Custom Step

An external custom step can be used in a project data or master data flow, and can be limited to an integration between specific provider applications. For example, you would use a project data flow with an external custom step to transfer project data from a Sample to File integration. The steps are organized as follows:


(Optional) <External Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the external custom step to the source data.

For more details on how to create an external custom step, download the External Custom Step SDK from the Help menu in Gateway.

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


(Optional) <External Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the external custom step to the destination data.


(Optional) <External Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the external custom step to the destination data.

Flow Sequence When Using Internal Custom Step for On-Premises

An internal custom step can be used in a project data or master data flow, and can be limited to an integration between specific provider applications. Internal custom steps can be used anywhere in e flow sequence. For example, you would use a project data flow with an internal custom step to transfer project data from a Sample to File integration. The steps are organized as follows:


(Optional) <Internal Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the internal custom step to the source data.

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


(Optional) <Internal Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the internal custom step to the destination data.


(Optional) <Internal Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the internal custom step to the destination data.

95

Appendix B: Fields Supported in Mapping Templates

In This Section

Fields Supported with P6 EPPM .............................................................................. 95 Fields Supported with Prime Projects .................................................................... 119 Fields Supported with Instantis EnterpriseTrack .................................................... 123 Fields Supported with Unifier ................................................................................. 125

Fields Supported with P6 EPPM

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

Send EBS Actuals to P6

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

EBS Gateway P6

ACTUAL_QUANTITY ActualUnits ActualUnits

ACTUAL_COST ActualCost ActualCost

TASK_NUMBER ActivityId ActivityId

SYSTEM_LINKAGE EBS_RAS_SYSTEM_LINKAGE

EBS_RAS_SYSTEM_LINKAGE

EXPENDITURE_TYPE

EBS_RAS_EXPENDITURE_TYPE


EXPENDITURE_ITEM_DATE

ActualStartDate ActualStartDate

RESOURCE_NUMBER

ResourceId ResourceId

EXPENDITURE_ORG_NAME

EBS_RAS_EXPENDITURE_ORG_NAME



96

Send EBS Actual Progress to P6

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 Gateway P6

AS_OF_DATE DataDate DataDate

ACTUAL_FINISH_DATE

ActualFinishDate ActualFinishDate

TASK_NUMBER Id Id

PARENT_TASK_NUMBER

WBSCode WBSCode

ACTUAL_START_DATE


BASE_PERCENT_COMPLETE

PercentComplete PercentComplete

Send EBS Cost Code Details to P6 Activity Expense

Description: This two-way project data field-mapping template creates an ActivityExpense object in P6 or a FinancialElementAssignment object in EBS, depending on the destination application. The following fields are mapped in each application:

EBS Gateway P6


CBS_NAME EBS_EXP_CBS_NAME EBS_EXP_CBS_NAME

COST_CODE EBS_EXP_COST_CODE EBS_EXP_COST_CODE

COST_CODE_NAME EBS_EXP_COST_CODE_NAME

EBS_EXP_COST_CODE_NAME

COST_CODE_ATTRIBUTE

EBS_EXP_COST_CODE_ATTRIBUTE

EBS_EXP_COST_CODE_ATTRIBUTE

COST_CODE_CATEGORY

EBS_EXP_COST_CODE_CATEGORY

EBS_EXP_COST_CODE_CATEGORY

QUANTITY_CURRENTWORKING

PlannedUnits PlannedUnits

RESOURCE_NUMBER DocumentNumber DocumentNumber


97


Description: This two-way project data field-mapping template creates a ResourceAssignment object in the destination application. The following fields are mapped in each application.

EBS Gateway P6


COST_CODE EBS_RAS_COST_CODE EBS_RAS_COST_CODE

COST_CODE_NAME EBS_RAS_COST_CODE_NAME

EBS_RAS_COST_CODE_NAME

COST_CODE_ATTRIBUTE

EBS_RAS_COST_CODE_ATTRIBUTE

EBS_RAS_COST_CODE_ATTRIBUTE

COST_CODE_CATEGORY

EBS_RAS_COST_CODE_CATEGORY

EBS_RAS_COST_CODE_CATEGORY

CBS_NAME EBS_RAS_CBS_NAME EBS_RAS_CBS_NAME

RESOURCE_NUMBER ResourceId ResourceId

Send EBS Financial Elements to P6 Expense Category

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

EBS Gateway P6

RESOURCE_NAME ExpenseCategory Name

Send EBS Financial Period to P6 Financial Period

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

EBS Gateway P6

PERIOD_NAME Name Name

END_DATE EndDate EndDate

START_DATE StartDate StartDate


98

Send EBS Resource to P6 Resource

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 Gateway P6

RESOURCE_CLASS_CODE ResourceType ResourceType

EMAIL_ADDRESS EmailAddress EmailAddress

EMPLOYEE_NUMBER EmployeeId EmployeeId

UNIT_OF_MEASURE UnitofMeasureAbbreviation UnitofMeasureAbbreviation

RESOURCE_ID Id Id

RESOURCE_NAME Name Name

Send EBS Resource Rates to P6 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:

EBS Gateway P6

RATE_START_DATE EffectiveDate EffectiveDate

RATE PricePerUnit PricePerUnit

Send EBS Role to P6 Resource

Depending on the destination application, this master data field mapping template creates a Role object in EBS or a Resource object in P6. The following fields are mapped in the Resource object in Gateway:

EBS Gateway P6

RESOURCE_ID Id Id



99

Send EBS Role to P6 Role

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

EBS Gateway P6

RESOURCE_ID Id Id


Send EBS Role Rates to P6 Role Rates

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

EBS Gateway P6

RATE PricePerUnit PricePerUnit

Send P6 Actuals to EBS

This project data field-mapping template creates an ExpenditureitemDetails object in EBS using data from the ResourceAssignment object in P6. The following fields are mapped from each application:

EBS Gateway P6






RESOURCE_NUMBER

ResourceId ResourceId

EXPENDITURE_TYPE









100

Send P6 Actual Progress to EBS


EBS Gateway P6

AS_OF_DATE DataDate DataDate

ACTUAL_FINISH_DATE

ActualFinishDate ActualFinishDate

TASK_NUMBER Id Id

PARENT_TASK_NUMBER

WBSCode WBSCode

ACTUAL_START_DATE


BASE_PERCENT_COMPLETE

PercentComplete PercentComplete


Description: This two-way project data field-mapping template creates an ActivityExpense object in P6 or a FinancialElementAssignment object in EBS, depending on the destination application. The following fields are mapped in each application:

EBS Gateway P6


COST_CODE EBS_EXP_COST_CODE EBS_EXP_COST_CODE



Description: This two-way project data field-mapping template creates an ResourceAssignment object in P6 or EBS, depending on the destination application. The following fields are mapped in each application:

EBS Gateway P6


COST_CODE EBS_RAS_COST_CODE EBS_RAS_COST_CODE


101

EBS Gateway P6


Send P6 EXP Actuals to EBS

This project data field-mapping template creates an ExpenditureItemDetails object in EBS from the ActivityExpense object in P6 when EBS is the destination application. The following fields are mapped in each application:

EBS Gateway P6




RESOURCE_NUMBER

DocumentNumber DocumentNumber

EXPENDITURE_TYPE

EBS_EXP_EXPENDITURE_TYPE

EBS_EXP_EXPENDITURE_TYPE




EBS_EXP_EXPENDITURE_ITEM_DATE

EBS_EXP_EXPENDITURE_ITEM_DATE


EBS_EXP_EXPENDITURE_ORG_NAME

EBS_EXP_EXPENDITURE_ORG_NAME

Sync EBS and P6 Activity


EBS Gateway P6

TASK_NUMBER Id Id

PARENT_TASK_NUMBER

WBSCode WBSCode

COMPLETION_DATE PlannedFinishDate PlannedFinishDate

TASK_NAME Name Name

START_DATE PlannedStartDate PlannedStartDate


102

EBS Gateway P6

ACTIVITY_TYPE Type Type

Sync EBS and P6 Activity Cost Budget

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 Gateway P6

BUDGET_TYPE_PLAN_CLASS

EBS_ACT_BUDGET_TYPE_PLAN_CLASS


VERSION_NUMBER EBS_ACT_BUDGET_VERSION_NUMBER

EBS_ACT_BUDGET_VERSION_NUMBER

RAW_COST_ORIGINAL EBS_ACT_BUDGET_ORIGINAL_COST

EBS_ACT_BUDGET_ORIGINAL_COST

RAW_COST_CURRENTWORKING

EBS_ACT_BUDGET_PROPOSED_COST

EBS_ACT_BUDGET_PROPOSED_COST

RAW_COST_CURRENTBASELINED

EBS_ACT_BUDGET_CURRENT_COST

EBS_ACT_BUDGET_CURRENT_COST

PARENT_TASK_NUMBER

WBSCode WBSCode

TASK_NUMBER Id Id

VERSION_NAME EBS_ACT_BUDGET_VERSION_NAME

EBS_ACT_BUDGET_VERSION_NAME

BUDGET_STATUS_CODE

EBS_ACT_BUDGET_STATUS_CODE

EBS_ACT_BUDGET_VERSION_NAME


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

EBS Gateway P6




VERSION_NUMBER EBS_ACT_FORECAST_VERSION_NUMBER

EBS_ACT_FORECAST_VERSION_NUMBER


103

EBS Gateway P6


EBS_ACT_FORECAST_PROPOSED_COST

EBS_ACT_FORECAST_PROPOSED_COST


EBS_ACT_FORECAST_CURRENT_COST

EBS_ACT_FORECAST_CURRENT_COST

RAW_COST_ORIGINAL

EBS_ACT_FORECAST_ORIGINAL_COST

EBS_ACT_FORECAST_ORIGINAL_COST

PARENT_TASK_NUMBER

WBSCode WBSCode

TASK_NUMBER Id Id

VERSION_NAME EBS_ACT_FORECAST_VERSION_NAME

EBS_ACT_FORECAST_VERSION_NAME

BUDGET_STATUS_CODE

EBS_ACT_FORECAST_STATUS_CODE

EBS_ACT_FORECAST_STATUS_CODE


Description: This two-way project data field-mapping template creates an Activity object in the destination application. The following fields are mapped in each application.

EBS Gateway P6

REV_BUDGET_TYPE_PLAN_CLASS

EBS_ACT_REV_BUDGET_TYPE_PLAN_CLASS


REV_VERSION_NUMBER

EBS_ACT_FORECAST_REV_VERSION_NUMBER

EBS_ACT_FORECAST_REV_VERSION_NUMBER

REV_REVENUE_CURRENTWORKING

EBS_ACT_FORECAST_REV_PROPOSED_COST

EBS_ACT_FORECAST_REV_PROPOSED_COST

REV_REVENUE_CURRENTBASELINED

EBS_ACT_FORECAST_REV_CURRENT_COST

EBS_ACT_FORECAST_REV_CURRENT_COST

REV_REVENUE_ORIGINAL

EBS_ACT_FORECAST_REV_ORIGINAL_COST

EBS_ACT_FORECAST_REV_ORIGINAL_COST

REV_PARENT_TASK_NUMBER

WBSCode WBSCode

REV_TASK_NUMBER

Id Id

REV_VERSION_NAME

EBS_ACT_FORECAST_REV_VERSION_NAME

EBS_ACT_FORECAST_REV_VERSION_NAME


104

EBS Gateway P6

REV_BUDGET_STATUS_CODE

EBS_ACT_FORECAST_REV_STATUS_CODE

EBS_ACT_FORECAST_REV_STATUS_CODE


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 Gateway P6




REV_VERSION_NUMBER

EBS_ACT_REVENUE_BUDGET_VERSION_NUMBER

EBS_ACT_REVENUE_BUDGET_VERSION_NUMBER


EBS_ACT_REVENUE_BUDGET_PROPOSED_COST

EBS_ACT_REVENUE_BUDGET_PROPOSED_COST


EBS_ACT_REVENUE_BUDGET_CURRENT_COST

EBS_ACT_REVENUE_BUDGET_CURRENT_COST


EBS_ACT_REVENUE_BUDGET_ORIGINAL_COST

EBS_ACT_REVENUE_BUDGET_ORIGINAL_COST

REV_PARENT_TASK_NUMBER

WBSCode WBSCode

REV_TASK_NUMBER

Id Id

REV_VERSION_NAME

EBS_ACT_REVENUE_BUDGET_VERSION_NAME

EBS_ACT_REVENUE_BUDGET_VERSION_NAME


EBS_ACT_REVENUE_BUDGET_STATUS_CODE

EBS_ACT_REVENUE_BUDGET_STATUS_CODE


Description: This two-way project data field-mapping template maps the FinancialElementAssignment object in EBS to the ActivityExpense object in P6 . The following fields are mapped in each application:


105

EBS Gateway P6


EBS_EXP_BUDGET_TYPE_PLAN_CLASS


VERSION_NUMBER EBS_EXP_BUDGET_VERSION_NUMBER

EBS_EXP_BUDGET_VERSION_NUMBER

RAW_COST_ORIGINAL EBS_EXP_BUDGET_ORIGINAL_COST

EBS_EXP_BUDGET_ORIGINAL_COST


EBS_EXP_BUDGET_PROPOSED_COST

EBS_EXP_BUDGET_PROPOSED_COST


EBS_EXP_BUDGET_CURRENT_COST

EBS_EXP_BUDGET_CURRENT_COST

QUANTITY_ORIGINAL EBS_EXP_BUDGET_ORIGINAL_QTY

EBS_EXP_BUDGET_ORIGINAL_QTY


EBS_EXP_BUDGET_PROPOSED_QTY

EBS_EXP_BUDGET_PROPOSED_QTY

QUANTITY_CURRENTBASELINED

EBS_EXP_BUDGET_CURRENT_QTY

EBS_EXP_BUDGET_CURRENT_QTY


VERSION_NAME EBS_EXP_BUDGET_VERSION_NAME

EBS_EXP_BUDGET_VERSION_NAME

BUDGET_STATUS_CODE

EBS_EXP_BUDGET_STATUS_CODE

EBS_EXP_BUDGET_VERSION_NAME


Description: This two-way project data field-mapping template maps the FinancialElementAssignment object in EBS to the ActivityExpense object in P6 . The following fields are mapped in each application:

EBS Gateway P6


EBS_EXP_REVENUE_BUDGET_TYPE_PLAN_CLASS


REV_VERSION_NUMBER

EBS_EXP_REVENUE_BUDGET_VERSION_NUMBER

EBS_EXP_REVENUE_BUDGET_VERSION_NUMBER

REV_QUANTITY_ORIGINAL

EBS_EXP_REVENUE_BUDGET_ORIGINAL_QTY

EBS_EXP_REVENUE_BUDGET_ORIGINAL_QTY

REV_QUANTITY_CURRENTWORKING

EBS_EXP_REVENUE_BUDGET_PROPOSED_QTY

EBS_EXP_REVENUE_BUDGET_PROPOSED_QTY


106

EBS Gateway P6

REV_QUANTITY_CURRENTBASELINED

EBS_EXP_REVENUE_BUDGET_CURRENT_QTY

EBS_EXP_REVENUE_BUDGET_CURRENT_QTY


EBS_EXP_REVENUE_BUDGET_ORIGINAL_COST

EBS_EXP_REVENUE_BUDGET_ORIGINAL_COST


EBS_EXP_REVENUE_BUDGET_PROPOSED_COST

EBS_EXP_REVENUE_BUDGET_PROPOSED_COST


EBS_EXP_REVENUE_BUDGET_CURRENT_COST

EBS_EXP_REVENUE_BUDGET_CURRENT_COST

REV_TASK_NUMBER ActivityId ActivityId

REV_VERSION_NAME

EBS_EXP_REVENUE_BUDGET_VERSION_NAME

EBS_EXP_REVENUE_BUDGET_VERSION_NAME

BUDGET_STATUS_CODE

EBS_EXP_REVENUE_BUDGET_STATUS_CODE

EBS_EXP_REVENUE_BUDGET_STATUS_CODE


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

EBS Gateway P6




VERSION_NUMBER EBS_EXP_FORECAST_VERSION_NUMBER

EBS_EXP_FORECAST_VERSION_NUMBER


EBS_EXP_FORECAST_PROPOSED_COST

EBS_EXP_FORECAST_PROPOSED_COST


EBS_EXP_FORECAST_CURRENT_COST

EBS_EXP_FORECAST_CURRENT_COST

RAW_COST_ORIGINAL

EBS_EXP_FORECAST_ORIGINAL_COST

EBS_EXP_FORECAST_ORIGINAL_COST


EBS_EXP_FORECAST_PROPOSED_QTY

EBS_EXP_FORECAST_PROPOSED_QTY


EBS_EXP_FORECAST_CURRENT_QTY

EBS_EXP_FORECAST_CURRENT_QTY

QUANTITY_ORIGINAL

EBS_EXP_FORECAST_ORIGINAL_QTY

EBS_EXP_FORECAST_ORIGINAL_QTY


107

EBS Gateway P6


VERSION_NAME EBS_EXP_FORECAST_VERSION_NAME

EBS_EXP_FORECAST_VERSION_NAME

BUDGET_STATUS_CODE

EBS_EXP_FORECAST_STATUS_CODE

EBS_EXP_FORECAST_STATUS_CODE


Description: This two-way project data field-mapping template creates an ActivityExpense object in P6 or a FinancialElementAssignment object in EBS based on the destination application. The following fields are mapped in each application.

EBS Gateway P6




REV_VERSION_NUMBER

EBS_EXP_REVENUE_FORECAST_REV_VERSION_NUMBER

EBS_EXP_REVENUE_FORECAST_REV_VERSION_NUMBER


EBS_EXP_FORECAST_REV_PROPOSED_COST

EBS_EXP_FORECAST_REV_PROPOSED_COST


EBS_EXP_FORECAST_REV_CURRENT_COST

EBS_EXP_FORECAST_REV_CURRENT_COST


EBS_EXP_FORECAST_REV_ORIGINAL_COST

EBS_EXP_FORECAST_REV_ORIGINAL_COST


EBS_EXP_FORECAST_REV_PROPOSED_QTY

EBS_EXP_FORECAST_REV_PROPOSED_QTY


EBS_EXP_FORECAST_REV_CURRENT_QTY

EBS_EXP_FORECAST_REV_CURRENT_QTY


EBS_EXP_FORECAST_REV_ORIGINAL_QTY

EBS_EXP_FORECAST_REV_ORIGINAL_QTY

REV_TASK_NUMBER

ActivityId ActivityId

REV_VERSION_NAME

EBS_EXP_FORECAST_REV_VERSION_NAME

EBS_EXP_FORECAST_REV_VERSION_NAME


EBS_EXP_FORECAST_REV_STATUS_CODE

EBS_EXP_FORECAST_REV_STATUS_CODE


108

Sync EBS and P6 Financial Element Assignments

Description: This two-way project data field-mapping template maps the FinancialElementAssignment EBS object to an Activity Expense P6 object. The following fields are mapped in each application:

EBS Gateway P6


PLANNED_EFFORT PlannedUnits PlannedUnits

PLANNED_COST PlannedCost PlannedCost

ALIAS ExpenseItem ExpenseItem


EXPENDITURE_TYPE ExpenseCategoryName ExpenseCategoryName

Sync EBS and P6 Activity Relationships

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

EBS Gateway P6

TO_PROJECT_NUMBER PredecessorProjectId PredecessorProjectId

FROM_PROJECT_NUMBER SuccessorProjectId SuccessorProjectId

TO_TASK_NUMBER PredecessorActivityId PredecessorActivityId

FROM_TASK_NUMBER SuccessorActivityId SuccessorActivityId

RS_SUBTYPE_CODE Type Type

LAG Lag Lag


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.


109

EBS Gateway P6


EBS_RAS_BUDGET_TYPE_PLAN_CLASS



EBS_RAS_BUDGET_PROPOSED_QTY



EBS_RAS_BUDGET_CURRENT_QTY


QUANTIY_ORIGINAL EBS_RAS_BUDGET_ORIGINAL_QTY

EBS_RAS_BUDGET_ORIGINAL_QTY


EBS_RAS_BUDGET_PROPOSED_COST



EBS_RAS_BUDGET_CURRENT_COST


RAW_COST_ORIGINAL EBS_RAS_BUDGET_ORIGINAL_COST

EBS_RAS_BUDGET_ORIGINAL_COST

VERSION_NUMBER EBS_RAS_BUDGET_VERSION_NUMBER

EBS_RAS_BUDGET_VERSION_NUMBER

BUDGET_STATUS_CODE

EBS_RAS_BUDGET_STATUS_CODE



VERSION_NAME EBS_RAS_BUDGET_VERSION_NAME

EBS_RAS_BUDGET_VERSION_NAME


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 Gateway P6




VERSION_NUMBER EBS_RAS_FORECAST_VERSION_NUMBER

EBS_RAS_FORECAST_VERSION_NUMBER


EBS_RAS_FORECAST_PROPOSED_COST

EBS_RAS_FORECAST_PROPOSED_COST


110

EBS Gateway P6


EBS_RAS_FORECAST_CURRENT_COST

EBS_RAS_FORECAST_CURRENT_COST

RAW_COST_ORIGINAL

EBS_RAS_FORECAST_ORIGINAL_COST

EBS_RAS_FORECAST_ORIGINAL_COST


VERSION_NAME EBS_RAS_FORECAST_VERSION_NAME

EBS_RAS_FORECAST_VERSION_NAME

BUDGET_STATUS_CODE

EBS_RAS_FORECAST_STATUS_CODE

EBS_RAS_FORECAST_STATUS_CODE


EBS_RAS_FORECAST_PROPOSED_QTY

EBS_RAS_FORECAST_PROPOSED_QTY


EBS_RAS_FORECAST_CURRENT_QTY

EBS_RAS_FORECAST_CURRENT_QTY

QUANTITY_ORIGINAL EBS_RAS_FORECAST_ORIGINAL_QTY

EBS_RAS_FORECAST_ORIGINAL_QTY


Description: This two-way project data field-mapping template creates a ResourceAssignment object in the destination application. The following fields are mapped in the ResourceAssignment object of Gateway for each application.

EBS Gateway P6


EBS_RAS_REV_BUDGET_TYPE_PLAN_CLASS



EBS_RAS_FORECAST_REV_PROPOSED_COST

EBS_RAS_FORECAST_REV_PROPOSED_COST


EBS_RAS_FORECAST_REV_CURRENT_COST

EBS_RAS_FORECAST_REV_CURRENT_COST


EBS_RAS_FORECAST_REV_ORIGINAL_COST

EBS_RAS_FORECAST_REV_ORIGINAL_COST


EBS_RAS_FORECAST_REV_PROPOSED_QTY

EBS_RAS_FORECAST_REV_PROPOSED_QTY


EBS_RAS_FORECAST_REV_CURRENT_QTY

EBS_RAS_FORECAST_REV_CURRENT_QTY


111

EBS Gateway P6


EBS_RAS_FORECAST_REV_ORIGINAL_QTY

EBS_RAS_FORECAST_REV_ORIGINAL_QTY

REV_VERSION_NUMBER

EBS_RAS_FORECAST_REV_VERSION_NUMBER

EBS_RAS_FORECAST_REV_VERSION_NUMBER


EBS_RAS_FORECAST_REV_STATUS_CODE

EBS_RAS_FORECAST_REV_STATUS_CODE


REV_VERSION_NAME EBS_RAS_FORECAST_REV_VERSION_NAME

EBS_RAS_FORECAST_REV_VERSION_NAME


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 Gateway P6





EBS_RAS_REVENUE_BUDGET_CURRENT_COST

EBS_RAS_REVENUE_BUDGET_CURRENT_COST


EBS_RAS_REVENUE_BUDGET_PROPOSED_COST

EBS_RAS_REVENUE_BUDGET_PROPOSED_COST


EBS_RAS_REVENUE_BUDGET_ORIGINAL_COST

EBS_RAS_REVENUE_BUDGET_ORIGINAL_COST


EBS_RAS_REVENUE_BUDGET_PROPOSED_QTY

EBS_RAS_REVENUE_BUDGET_PROPOSED_QTY


EBS_RAS_REVENUE_BUDGET_CURRENT_QTY

EBS_RAS_REVENUE_BUDGET_CURRENT_QTY


EBS_RAS_REVENUE_BUDGET_ORIGINAL_QTY

EBS_RAS_REVENUE_BUDGET_ORIGINAL_QTY

REV_VERSION_NUMBER

EBS_RAS_REVENUE_BUDGET_VERSION_NUMBER

EBS_RAS_REVENUE_BUDGET_VERSION_NUMBER


EBS_RAS_REVENUE_BUDGET_STATUS_CODE

EBS_RAS_REVENUE_BUDGET_STATUS_CODE



112

EBS Gateway P6

REV_VERSION_NAME EBS_RAS_REVENUE_BUDGET_VERSION_NAME

EBS_RAS_REVENUE_BUDGET_VERSION_NAME


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 Gateway P6




PLANNED_COST PlannedCost PlannedCost

PLANNING_START_DATE PlannedStartDate PlannedStartDate

PLANNING_END_DATE PlannedFinishDate PlannedFinishDate

ROLE_NUMBER RoleId RoleId



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 Gateway P6


EBS_PRJ_BUDGET_TYPE_PLAN_CLASS


SEGMENT1 Id Id

BUDGET_STATUS_CODE

EBS_PRJ_BUDGET_STATUS_CODE

EBS_PRJ_BUDGET_STATUS_CODE

VERSION_NAME EBS_PRJ_BUDGET_VERSION_NAME

EBS_PRJ_BUDGET_VERSION_NAME


EBS_PRJ_BUDGET_CURRENT_COST

EBS_PRJ_BUDGET_CURRENT_COST


113

EBS Gateway P6


EBS_PRJ_BUDGET_PROPOSED_COST

EBS_PRJ_BUDGET_PROPOSED_COST

RAW_COST_ORIGINAL EBS_PRJ_BUDGET_ORIGINAL_COST

EBS_PRJ_BUDGET_ORIGINAL_COST

VERSION_NUMBER EBS_PRJ_BUDGET_VERSION_NUMBER

EBS_PRJ_BUDGET_VERSION_NUMBER


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 Gateway P6


EBS_PRJ_REV_BUDGET_TYPE_PLAN_CLASS


SEGMENT1 Id Id


EBS_PRJ_REV_BUDGET_STATUS_CODE

EBS_PRJ_REV_BUDGET_STATUS_CODE

REV_VERSION_NAME EBS_PRJ_REV_BUDGET_VERSION_NAME

EBS_PRJ_REV_BUDGET_VERSION_NAME


EBS_PRJ_REV_BUDGET_CURRENT_COST

EBS_PRJ_REV_BUDGET_CURRENT_COST


EBS_PRJ_REV_BUDGET_PROPOSED_COST

EBS_PRJ_REV_BUDGET_PROPOSED_COST


EBS_PRJ_REV_BUDGET_ORIGINAL_COST

EBS_PRJ_REV_BUDGET_ORIGINAL_COST

REV_VERSION_NUMBER

EBS_PRJ_REV_BUDGET_VERSION_NUMBER

EBS_PRJ_REV_BUDGET_VERSION_NUMBER


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:


114

EBS Gateway P6




VERSION_NUMBER EBS_PRJ_FORECAST_VERSION_NUMBER

EBS_PRJ_FORECAST_VERSION_NUMBER


EBS_PRJ_FORECAST_PROPOSED_COST

EBS_PRJ_FORECAST_PROPOSED_COST


EBS_PRJ_FORECAST_CURRENT_COST

EBS_PRJ_FORECAST_CURRENT_COST

RAW_COST_ORIGINAL EBS_PRJ_FORECAST_ORIGINAL_COST

EBS_PRJ_FORECAST_ORIGINAL_COST

SEGMENT1 Id Id

REV_VERSION_NAME EBS_PRJ_FORECAST_VERSION_NAME

EBS_PRJ_FORECAST_VERSION_NAME


EBS_PRJ_FORECAST_STATUS_CODE

EBS_PRJ_FORECAST_STATUS_CODE

Sync EBS and P6 Projects

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 Gateway P6

SEGMENT1 Id Id

NAME Name Name

DESCRIPTION Description Description

PROJECT_START_DATE PlannedStartDate PlannedStartDate

COMPLETION_DATE MustFinishByDate MustFinishByDate


Description: This two-way project data field-mapping template creates an Project object in the destination application. The following fields are mapped in each application.


115

EBS Gateway P6




REV_SEGMENT1 Id Id


EBS_PRJ_FORECAST_REV_STATUS_CODE

EBS_PRJ_FORECAST_REV_STATUS_CODE

REV_VERSION_NAME EBS_PRJ_FORECAST_REV_VERSION_NAME

EBS_PRJ_FORECAST_REV_VERSION_NAME


EBS_PRJ_FORECAST_REV_PROPOSED_COST

EBS_PRJ_FORECAST_REV_PROPOSED_COST


EBS_PRJ_FORECAST_REV_CURRENT_COST

EBS_PRJ_FORECAST_REV_CURRENT_COST


EBS_PRJ_FORECAST_REV_ORIGINAL_COST

EBS_PRJ_FORECAST_REV_ORIGINAL_COST

REV_VERSION_NUMBER

EBSRevenueBudgetVersionNumber

EBSRevenueBudgetVersionNumber

Sync EBS and P6 WBS

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

EBS Gateway P6

TASK_NUMBER Code Code

TASK_NAME 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 Gateway P6


EBS_WBS_BUDGET_TYPE_PLAN_CLASS




116

EBS Gateway P6


EBS_WBS_BUDGET_CURRENT_COST



EBS_WBS_BUDGET_PROPOSED_COST


RAW_COST_ORIGINAL EBS_WBS_BUDGET_ORIGINAL_COST

EBS_RAS_BUDGET_ORIGINAL_COST

VERSION_NUMBER EBS_WBS_BUDGET_VERSION_NUMBER

EBS_RAS_BUDGET_VERSION_NUMBER

BUDGET_STATUS_CODE

EBS_WBS_BUDGET_STATUS_CODE


VERSION_NAME EBS_WBS_BUDGET_VERSION_NAME

EBS_RAS_BUDGET_VERSION_NAME


EBS_WBS_BUDGET_PROPOSED_QTY



EBS_WBS_BUDGET_CURRENT_QTY


QUANTIY_ORIGINAL EBS_WBS_BUDGET_ORIGINAL_QTY

EBS_RAS_BUDGET_ORIGINAL_QTY


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 Gateway P6


EBS_WBS_REV_BUDGET_TYPE_PLAN_CLASS


REV_TASK_NUMBER

Code Code


EBS_WBS_REVENUE_BUDGET_PROPOSED_COST

EBS_WBS_REVENUE_BUDGET_PROPOSED_COST


EBS_WBS_REVENUE_BUDGET_CURRENT_COST

EBS_WBS_REVENUE_BUDGET_CURRENT_COST


EBS_WBS_REVENUE_BUDGET_ORIGINAL_COST

EBS_WBS_REVENUE_BUDGET_ORIGINAL_COST


117

EBS Gateway P6

REV_VERSION_NUMBER

EBS_WBS_REVENUE_BUDGET_VERSION_NUMBER

EBS_WBS_REVENUE_BUDGET_VERSION_NUMBER

SEGMENT1 Id Id


EBS_WBS_REVENUE_BUDGET_STATUS_CODE

EBS_WBS_REVENUE_BUDGET_STATUS_CODE

REV_VERSION_NAME

EBS_WBS_REVENUE_BUDGET_VERSION_NAME

EBS_WBS_REVENUE_BUDGET_VERSION_NAME


EBS_WBS_REVENUE_BUDGET_PROPOSED_QTY

EBS_WBS_REVENUE_BUDGET_PROPOSED_QTY


EBS_WBS_REVENUE_BUDGET_CURRENT_QTY

EBS_WBS_REVENUE_BUDGET_CURRENT_QTY

QUANTITY_ORIGINAL

EBS_WBS_REVENUE_BUDGET_ORIGINAL_QTY

EBS_WBS_REVENUE_BUDGET_ORIGINAL_QTY


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 Gateway P6




VERSION_NUMBER EBS_WBS_FORECAST_VERSION_NUMBER

EBS_WBS_FORECAST_VERSION_NUMBER


EBS_WBS_FORECAST_PROPOSED_COST

EBS_WBS_FORECAST_PROPOSED_COST


EBS_WBS_FORECAST_CURRENT_COST

EBS_WBS_FORECAST_CURRENT_COST

RAW_COST_ORIGINAL

EBS_WBS_FORECAST_ORIGINAL_COST

EBS_WBS_FORECAST_ORIGINAL_COST


EBS_WBS_FORECAST_PROPOSED_QTY

EBS_WBS_FORECAST_PROPOSED_QTY


EBS_WBS_FORECAST_CURRENT_QTY

EBS_WBS_FORECAST_CURRENT_QTY

QUANTITY_ORIGINAL

EBS_WBS_FORECAST_ORIGINAL_QTY

EBS_WBS_FORECAST_ORIGINAL_QTY


118

EBS Gateway P6


VERSION_NAME EBS_WBS_FORECAST_VERSION_NAME

EBS_WBS_FORECAST_VERSION_NAME

BUDGET_STATUS_CODE

EBS_WBS_FORECAST_STATUS_CODE

EBS_WBS_FORECAST_STATUS_CODE


Description: This two-way project data field-mapping template creates a WBS object in the destination application. The following fields are mapped in each application.

EBS Gateway P6




REV_VERSION_NUMBER

EBS_WBS_FORECAST_REV_VERSION_NUMBER

EBS_WBS_FORECAST_REV_VERSION_NUMBER


EBS_WBS_FORECAST_REV_PROPOSED_COST

EBS_WBS_FORECAST_REV_PROPOSED_COST


EBS_WBS_FORECAST_REV_CURRENT_COST

EBS_WBS_FORECAST_REV_CURRENT_COST


EBS_WBS_FORECAST_REV_ORIGINAL_COST

EBS_WBS_FORECAST_REV_ORIGINAL_COST


EBS_WBS_FORECAST_REV_PROPOSED_QTY

EBS_WBS_FORECAST_REV_PROPOSED_QTY


EBS_WBS_FORECAST_REV_CURRENT_QTY

EBS_WBS_FORECAST_REV_CURRENT_QTY


EBS_WBS_FORECAST_REV_ORIGINAL_QTY

EBS_WBS_FORECAST_REV_ORIGINAL_QTY

REV_TASK_NUMBER

Code Code

REV_VERSION_NAME

EBS_WBS_FORECAST_REV_VERSION_NAME

EBS_WBS_FORECAST_REV_VERSION_NAME


EBS_WBS_FORECAST_REV_STATUS_CODE

EBS_WBS_FORECAST_REV_STATUS_CODE


119

Fields Supported with Prime Projects

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


This master data and project data field mapping template creates a new Resource objectId in Prime. The following fields from EBS are mapped:

EBS Gateway Prime

RESOURCE_ID Id Id



EMAIL_ADDRESS EmailAddress EmailAddress

EMPLOYEE_NUMBER EmployeeId EmployeeId

ENABLED_FLAG IsActive IsActive


This master data field mapping template creates a EBS Role in Prime. The following fields from EBS are mapped:

EBS Gateway Prime

RESOURCE_ID Id Id


Send EBS Leaf Tasks to Prime Activity

This project data field mapping template creates tasks within the Activity object in Prime. The following fields from EBS are mapped:

EBS Gateway Prime

TASK_NAME Name Name

TASK_NUMBER Id Id


SCHEDULED_START_DATE StartDate StartDate


120

EBS Gateway Prime

SCHEDULED_FINISH_DATE FinishDate FinishDate



STATUS_CODE Status Status

PARENT_TASK_NUMBER WBSCode WBSCode

PROJECT_NAME ProjectId ProjectId

PARENT_TASK_ID WBSObjectId ParentActivity

Send EBS Project Data to Prime

This project data field mapping template creates a Project in Prime. The following fields from EBS are mapped:

EBS Gateway Prime

SEGMENT1 Id ProjectId

NAME Name ProjectName



PROJECT_STATUS_NAME Status Status

COMPLETION_DATE MustFinishByDate PlannedFinishDate

Send EBS Relationships to Prime

This project data field mapping template creates a Relationship object in Prime. The following fields from EBS are mapped:

EBS Gateway Prime


LAG Lag Lag





121

EBS Gateway Prime


Send EBS Resource Assignments to Prime

This project data field mapping template creates a ResourceAssignment object in Prime. The following fields from EBS are mapped:

EBS Gateway Prime






RESOURCE_ASSIGNMENT_ID AssignmentCode AssignmentCode

Send EBS Top/Middle Tasks to Prime WBS

This project data field mapping template creates a WBS object in Prime. The following fields from EBS are mapped:

EBS Gateway Prime


TASK_NAME Name Name

Send Prime Activities to EBS

This project data field mapping template creates an Activity object in EBS. The following fields from Prime are mapped:

EBS Gateway Prime

TASK_NAME Name Name

TASK_NUMBER Id Id


SCHEDULED_START_DATE StartDate StartDate


122

EBS Gateway Prime

SCHEDULED_FINISH_DATE FinishDate FinishDate



STATUS_CODE Status Status

PARENT_TASK_NUMBER WBSCode WBSCode

PARENT_TASK_ID WBSObjectId WBSObjectId

Send Prime Project Data to EBS

This project data field mapping template creates a Project object in EBS. The following fields from Prime are mapped:

EBS Gateway Prime

SEGMENT1 Id ProjectId




PROJECT_STATUS_NAME Status Status

COMPLETION_DATE MustFinishByDate PlannedFinishDate

Send Prime Relationships to EBS

This project data field mapping template creates a Relationship object in EBS. The following fields from Prime are mapped:

EBS Gateway Prime


LAG Lag Lag






123

Send Prime Resource Assignments to EBS

This project data field mapping template creates a ResourceAssignment object in EBS. The following fields from Prime are mapped:

EBS Gateway Prime






Send Prime WBS Data to EBS

This project data field mapping template creates a WBS object in EBS. The following fields from Prime are mapped:

EBS Gateway Prime


TASK_NAME Name Name

SEGMENT1 ProjectId ProjectId

PARENT_TASK_ID ParentObjectId ParentObjectId

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 Gateway EnterpriseTrack

NAME Name project_name

CARRYING_OUT_ORGANIZATION_NAME

BusinessUnit business_unit


124


PROJECT_ORGANIZATION BusinessUnit division

PROJECT_TYPE EBSProjectType project_type

PROJECT_TYPE EBSProjectType roadmap

PROJECT_START_DATE PlannedStartDate start_date

COMPLETION_DATE FinishDate planned_realization_date

CREATED_FROM_PROJECT EBSETFinTemplateId fintemplateid

PROJECT_CURRENCY_CODE EBSETCurrencyCode currency_code

CALENDAR_NAME ActivityDefaultCalendarName

calendar_id

DESCRIPTION Description keywords

EnterpriseTrack ProjectFinance Mapping

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


OPERATION_TYPE OperationType operation_type

FIN_EDIT_TYPE FinanceEditMode fin_edit_mode

FIN_DATA_TYPE FinanceDataType 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:


TASK_LEVEL ElementClass element_class

BUD_LINE_BURDENED_COST

Value value

ELEMENT_TYPE ElementType element_type

TASK_NUMBER Id id


125


PARENT_TASK_NUMBER ParentId parent_id

TASK_ID SequenceNumber sequence_number

TASK_NAME DisplayName display_name

Fields Supported with Unifier

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

Send EBS Resource to Unifier Role

This master data field-mapping template creates a new role object in Unifier, from a Resource object in the EBS application. The following fields are mapped to Gateway's Resource object:

EBS Gateway Unifier

RESOURCE_ID Id uuu_role_id

RESOURCE_NAME Name uuu_role_name

Send EBS ContractHeader to Unifier PurchaseOrder

This project data field-mapping template creates a new ContractHeader object in EBS or a ProjectCommits object in Unifier. The following fields are mapped in the PurchaseOrder object in Gateway:

EBS Gateway Unifier

AGREEMENT_NUMBER RecordNo record_no

CUSTOMER_NAME Title title

CUSTOMER_NAME VendorName ugenVendorBP

Send EBS ContractDetail to Unifier PurchaseOrderDetail

This project data field-mapping template creates a new ContractDetails object in EBS or a ProjectCommitsDetail object in Unifier. The following fields are mapped in the PurchaseOrderDetail object in Gateway:


126

EBS Gateway Unifier

AGREEMENT_ID ParentObjectId ParentElementId

CUSTOMER_NUMBER LineNo li_num

CUSTOMER_NAME ShortDesc short_desc

DESCRIPTION Description description

AMOUNT Quantity uuu_quantity

AMOUNT PricePerUnit uuu_unit_price

TASK_NUMBER BitemId bItemID

Send EBS CostBudgetDetails to Unifier BudgetApprovalDetail

Depending on the direction of the business flow, this project data field-mapping template can create a new CostBudgetDetails object in EBS or an OtherProjectCostsDetail object in the Unifier application. The following fields are mapped to the BudgetApprovalDetail object of Gateway:

EBS Gateway Unifier

VERSION_NUMBER RecordNo record_no

BUDGET_VERSION_ID ParentObjectId ParentElementId

TASK_NUMBER BitemId bitemID


Quantity uuu_quantity


Amount amount

TXN_STANDARD_COST_RATE PricePerUnit uuu_unit_price

TASK_NAME ShortDesc short_desc

Send EBS CostBudgetDetails to Unifier BudgetChangeDetail

This project data field-mapping template maps a CostBudgetDetails object in EBS to an OtherProjectCostsDetail object in Unifier. The following fields are mapped in the BudgetChangeDetail object in Gateway:

EBS Gateway Unifier



127

EBS Gateway Unifier



QUANTITY_BUDGET_CHANGE


RAW_COST_BUDGET_CHANGE

Amount amount

TXN_STANDARD_COST_RATE

PricePerUnit uuu_unit_price


Send EBS CostBudgetHeader to Unifier BudgetApproval

Depending on the direction of the business flow, this project data field-mapping template can create a new CostBudgetHeader object in EBS or an OtherProjectCosts object in the Unifier application. The following fields are mapped in Gateway's BudgetApproval object:

EBS Gateway Unifier


VERSION_NAME Title title

Send EBS CostBudgetHeader to Unifier BudgetChange

This project data field-mapping template maps a CostBudgetHeader object in EBS to an OtherProjectCosts object in Unifier. The following fields are mapped:

EBS Gateway Unifier



Send EBS Expenditure Item Detail to Unifier Payment Detail

Depending on the direction of the business flow, this project data field-mapping template can create a new ExpenditureItemDetails object in EBS or an OtherProjectCostsDetail object in the Unifier application. The following fields are mapped in the PaymentDetail object in Gateway:


128

EBS Gateway Unifier

EXPENDITURE_ITEM_ID RecordNo record_no

EXPENDITURE_ID ParentObjectId ParentElementId

PARENT_TASK_NUMBER BitemId bitemId

PROJECT_RAW_COST Amount amount

EXPENDITURE_ITEM_ID ShortDesc short_desc

Send EBS Expenditure Item Header to Unifier Payments

This project data field-mapping template creates an OtherProjectCosts object in Unifier from the ExpenditureItemHeader object in EBS or an application. The following fields are mapped in Gateway's Payment object:

EBS Gateway Unifier

EXPENDITURE_ID RecordNo record_no

INCURRED_BY_PERSON Title title

ATTRIBUTE10 Status status

Send EBS FundHeader to Unifier FundAppropriation

This project data field-mapping template creates a new OtherProjectCosts object in the Unifier application from the FundHeader object in EBS. The following fields are mapped in FundAppropriation object in Gateway:

EBS Gateway Unifier


Send EBS FundDetail to Unifier FundAppropriationDetail

This project data field-mapping template creates a new OtherProjectCostsDetail object in the Unifier application from the FundDetails object in EBS. The following fields are mapped in FundAppropriationDetail object in Gateway:

EBS Gateway Unifier

CUSTOMER_NAME ShortDesc short_desc


129

EBS Gateway Unifier


INVPROC_ALLOCATED_AMOUNT

Amount amount

PROJECT_FUNDING_ID ParentObjectId ParentElementId

AGREEMENT_ID RowId row_id

Send EBS InvoiceHeader to Unifier Invoice

This project data field-mapping template creates a new ProjectInvoices object in the Unifier application from the InvoiceHeader object in EBS. The following fields are mapped in Invoice object in Gateway:

EBS Gateway Unifier


ATTRIBUTE2 ContractNumber uconContractNumberTXT16

ATTRIBUTE2 RefId refid


INVOICE_DATE InvoiceDate upaInvoiceDateDOP

Send EBS InvoiceDetails to Unifier InvoiceDetails

This project data field-mapping template creates a new ProjectInvoicesDetail object in the Unifier application from the InvoiceDetails object in EBS. The following fields are mapped in InvoiceDetail object in Gateway:

EBS Gateway Unifier

INVOICE_AMOUNT Amount amount

RA_INVOICE_NUMBER ParentObjectId ParentElementId

LINE_NUM Quantity uuu_quantity

ATTRIBUTE1 BitemId bItemID

INVOICE_AMOUNT PricePerUnit uuu_unit_price

LINE_NUM ShortDesc short_desc


130

Send EBS RevenueBudgetHeader to Unifier BudgetApproval

This project data field-mapping template creates a new OtherProjectCosts object in the Unifier application from the RevenueBudgetHeader object in EBS. The following fields are mapped using the BudgetApproval object in Gateway:

EBS Gateway Unifier

REV_VERSION_NUMBER RecordNo record_no

REV_VERSION_NAME Title title

Send EBS RevenueBudgetHeader to Unifier BudgetChange

This project data field-mapping template maps a RevenueBudgetHeader object in EBS to an OtherProjectCosts object in Unifier. The following fields are mapped using the BudgetChange object in Gateway:

EBS Gateway Unifier



Send RevenueBudgetDetails to Unifier BudgetApprovalDetails

Depending on the direction of the business flow, this project data field-mapping template can create a new CostBudgetDetails object in EBS or an OtherProjectCostsDetail object in the Unifier application. The following fields are mapped using the BudgetApprovalDetail object in Gateway:

EBS Gateway Unifier







Amount amount




131

EBS Gateway Unifier


Send EBS RevenueBudgetDetail to Unifier BudgetChangeDetail

This project data field-mapping template maps a RevenueBudgetDetails object in EBS to an OtherProjectCostsDetail object in Unifier. The following fields are mapped in the BudgetChangeDetail object in Gateway:

EBS Gateway Unifier


REV_BUDGET_VERSION_ID ParentObjectId ParentElementId

REV_TASK_NUMBER BitemId bitemID

REV_QUANTITY_BUDGET_CHANGE


REV_REVENUE_BUDGET_CHANGE

Amount amount


REV_TASK_NAME ShortDesc short_desc

Sync EBS and Unifier Projects

Depending on the direction of the business flow, this project data field-mapping template can create a new Project object in the EBS or Unifier applications. The following fields are mapped to the Project object in Gateway:

EBS Gateway Unifier

SEGMENT1 Id ProjectNumber


DESCRIPTION Description description

PROJECT_START_DATE PlannedStartDate uuu_project_start_date

PROJECT_TYPE ProjectType uuu_int_schedule_type

PROJECT_STATUS_NAME Status uuu_shell_status


132

Sync EBS WBS to Unifier CBS

Depending on the direction of the business flow, this project data field-mapping template can create a new WBS object in EBS or a CBS object in Unifier applications. The following fields are mapped to the WBS object in Gateway:

EBS Gateway Unifier

TASK_NUMBER Code code

TASK_NAME Name item

PARENT_TASK_ID ParentObjectId parentid

Send Unifier BudgetApproval to EBS CostBudgetHeader

This project data field-mapping template creates a new CostBudgetHeader object in EBS from the OtherProjectCosts object in the Unifier application. The following fields are mapped using the BudgetApproval object in Gateway:

EBS Gateway Unifier



Send Unifier BudgetApproval to EBS RevenueBudgetHeader

This project data field-mapping template creates a new RevenueBudgetHeader object in EBS from the OtherProjectCosts object in the Unifier application. The following fields are mapped using the BudgetApproval object in Gateway:

EBS Gateway Unifier



Send Unifier BudgetApprovalDetail to EBS CostBudgetDetail

This project data field-mapping template creates a new CostBudgetDetail object in EBS from the CostBudgetDetails object in the Unifier application. The following fields are mapped using the BudgetApprovalDetail object in Gateway:


133

EBS Gateway Unifier







Amount amount



Send Unifier BudgetApprovalDetail to RevenueBudgetDetails

This project data field-mapping template creates a new RevenueBudgetDetails object in Unifier from the OtherCostBudgetDetail object in EBS application. The following fields are mapped using the BudgetApprovalDetail object in Gateway:

EBS Gateway Unifier



REV_TASK_NUMBER BitemId bItemID




Amount amount



Send Unifier BudgetChange to EBS CostBudgetHeader

This project data field-mapping template creates a new CostBudgetHeader object in EBS from the OtherProjectCosts object in the Unifier application. The following fields are mapped using the BudgetChange object in Gateway:


134

EBS Gateway Unifier



Send Unifier BudgetChange to EBS RevenueBudgetHeader

This project data field-mapping template creates a new RevenueBudgetHeader object in EBS from the OtherProjectCosts object in the Unifier application. The following fields are mapped using the BudgetChange object in Gateway:

EBS Gateway Unifier



Send Unifier BudgetChangeDetail to EBS CostBudgetDetail

This project data field-mapping template creates a new CostBudgetDetail object in EBS from the OtherProjectCostsDetails object in the Unifier application. The following fields are mapped using the BudgetChangeDetail object in Gateway:

EBS Gateway Unifier




QUANTITY_BUDGET_CHANGE


RAW_COST_BUDGET_CHANGE

Amount amount





135

Send Unifier BudgetChangeDetail to EBS RevenueBudgetDetail

This project data field-mapping template creates a new RevenueBudgetDetail object in EBS from the OtherProjectCostsDetails object in the Unifier application. The following fields are mapped using the BudgetChangeDetail object in Gateway:

EBS Gateway Unifier



REV_TASK_NUMBER BitemId bItemID



REV_REVENUE_BUDGET_CHANGE

Amount amount



Send Unifier CBS to EBS WBS

CBS not a project data mapping template. master data?

Send Unifier Contract to EBS ContractHeader

This project data field mapping template creates a ContractHeader object in EBS from the ProjectCommits object in Unifier.The following fields are mapped using the Contract object in Gateway:

EBS Gateway Unifier



AGREEMENT_TYPE ContractType upoContractTypePD

TERM_NAME ContractTerms upoContractTermsMLT4000

Send Unifier ContractDetail to EBS ContractDetail

This project data field mapping template creates a ContractDetails object in EBS from the ProjectCommitsDetail object in Unifier.The following fields are mapped using the ContractDetail object in Gateway:


136

EBS Gateway Unifier


AMOUNT Amount amount

Send Unifier FundAppropriation to EBS FundHeader

This project data field-mapping template creates a FundHeader object in EBS application from the OtherProjectCosts object in EBS. The following fields are mapped in FundAppropriation object in Gateway:

EBS Gateway Unifier


DATE_ALLOCATED CreateDate uuu_creation_date

Send Unifier FundAppropriationDetail to EBS FundDetail

This project data field-mapping template creates a FundDetail object in the EBS application from the OtherProjectCostsDetails object in Unifier. The following fields are mapped in FundAppropriationDetail object in Gateway:

EBS Gateway Unifier

BUDGET_TYPE_CODE Description description

PM_FUNDING_REFERENCE TabId uuu_tab_id

ALLOCATED_AMOUNT Amount amount

AGREEMENT_NUMBER RowId row_id

Send Unifier Payments to EBS Expenditure (Miscellaneous)

This project data field-mapping template creates an ExpenditureItemHeader object in EBS from the OtherProjectCosts object in the Unifier application. The following fields are mapped in Gateway's Payment object:

EBS Gateway Unifier


RecordNo record_no


137

EBS Gateway Unifier

SYSTEM_LINKAGE Description description

EXPENDITURE_ITEM_DATE CreateDate uuu_creation_date

Send UnifierPaymentDetail to EBS Expenditure (Miscellaneous)

This project data field-mapping template creates an ExpenditureItemDetails object in EBS from the OtherProjectCostsDetail object in the Unifier application. The following fields are mapped in Gateway's PaymentDetail object:

EBS Gateway Unifier

ACTUAL_COST Amount amount

ACTUAL_QUANTITY Amount amount

EXPENDITURE_TYPE ShortDesc short_desc


Send Unifier PurchaseOrder to EBS ContractHeader

This project data field-mapping template creates a ContractHeader object in EBS from the ProjectCommits object in the Unifier application. The following fields are mapped in Gateway's Purchase object:

EBS Gateway Unifier



Send Unifier PurchaseOrderDetail to EBS ContractDetail

This project data field-mapping template creates a ContractDetails object in EBS from the ProjectCommitsDetail object in the Unifier application. The following fields are mapped in Gateway's PurchaseOrderDetail object:

EBS Gateway Unifier


AMOUNT Amount amount


138

EBS Gateway Unifier

TERM_NAME ShortDesc short_desc

AGREEMENT_TYPE Description description

139

Appendix C: Supported Object Mappings

In This Section

P6 Business Objects Supported in Gateway for Event Notifications ...................... 139 EBS Business Objects Supported in Gateway ....................................................... 139

P6 Business Objects Supported in Gateway for Event Notifications

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

Activity

ActivityExpense

ActivityRisk

EPS

Project

ResourceAssignment

Risk

RiskImpact

RiskResponseAction

RiskResponseActionImpact

RiskResponsePlan

WBS

EBS Business Objects Supported in Gateway

The following table is the master list of mappings between EBS business objects and Gateway business objects supported in Gateway. Use these objects to add custom field-mapping templates and then define additional business flows that support custom field-mapping templates specific to your organization's needs to integrate with any other provider application.

Alternatively, you can also use flexible object mapping to define custom cross-references between objects and then create field-mapping templates and business flows that support . For more details on flexible object mapping, see the Primavera Gateway Provider Customization Guide and Primavera Gateway Online Help.

Note: Always ensure the source and destination provider applications have a common set of Gateway business objects to support an integration.


140

EBS Business Objects Gateway Business Object

Activity Activity

BudgetApprovalDetail BudgetChangeDetail

ContractDetails ContractDetail

ContractHeader Contract

CostBudgetHeader BudgetApproval

CostBudgetDetails BudgetApprovalDetail

CostBudgetHeader BudgetChange

CostBudgetDetails BudgetChangeDetail

ExpenseCategory ExpenseCategory

ExpenditureItemHeader Payment

ExpenditureItemDetails PaymentDetail

FinancialPeriod FinancialPeriod

FundDetails FundAppropriationDetail

FundHeader FundAppropriation

InvoiceHeader Invoice

InvoiceDetails InvoiceDetail

Project Project

ProjectFinance ProjectFinance

ProjectFinanceElement ProjectFinanceElement

Relationship Relationship

Resource Resource

ResourceAssignment ResourceAssignment

ResourceRate ResourceRate

Role Role

RoleRate RoleRate

WBS WBS

141

Oracle Primavera Gateway E-Business Suite Setup Guide for On-Premises

Copyright © 2013, 2018, 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.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

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

Date post:	27-Jul-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

Gateway E-Business Suite Setup Guide for On-Premises · Gateway E-Business Suite Setup Guide for...

Documents