Supported Field Mapping Templates

The following tables show the field mappings supported in each field mapping template. Select the appropriate flow type, object, field mapping template, and corresponding synchronization in Primavera Gatewayto share data between applications:

Project Header Mappings

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

EBS

P6

SEGMENT1

Id

NAME

Name

DESCRIPTION

Description

SCHEDULED_START_DATE

PlannedStartDate

SCHEDULED_FINISH_DATE

MustFinishByDate

BUDGET_ORIGINAL_COST

EBSBudgetOriginalCost

BUDGET_PROPOSED_COST

EBSBudgetProposedCost

BUDGET_CURRENT_COST

EBSBudgetCurrentCost

BUDGET_ORIGINAL_QUANTITY

EBSBudgetOriginalQuantity

BUDGET_PROPOSED_QUANTITY

EBSBudgetProposedQuantity

BUDGET_CURRENT_QUANTITY

EBSBudgetCurrentQuantity

BUDGET_VERSION_NUMBER

EBSBudgetVersionNumber

BUDGET_VERSION_NAME

EBSBudgetVersionName

BUDGET_STATUS_CODE

EBSBudgetStatusCode

PROJECT_STATUS_CODE

EBSProjectStatus

PROJECT_TYPE

EBSProjectType

PROJECT_ORGANIZATION

EBSProjectOrgName

CALENDAR_WORKING_HOURS

EBSCalendarWorkingHours

Activity Relationship Fields

This field mapping template can be used in the import project data and export project data business flows to create a Relationship object in the destination application. The following fields are mapped in each application.

EBS

P6

TO_PROJECT_NUMBER

PredecessorProjectId

FROM_PROJECT_NUMBER

SuccessorProjectId

TO_TASK_NUMBER

PredecessorActivityId

FROM_TASK_NUMBER

SuccessorActivityId

RS_SUBTYPE_CODE

Type

LAG

Lag

Activity Mapping

This field mapping template can be used in the import project data and export project data business flows to create an Activity object with activity mappings in the destination application. The following fields will be mapped from each application:

EBS

P6

TASK_NUMBER

Id

PARENT_TASK_NUMBER

WBSCode

SCHEDULED_FINISH_DATE

PlannedFinishDate

TASK_NAME

Name

DATA_DATE

DataDate

PERCENT_COMPLETE

PercentComplete

SCHEDULED_START_DATE

PlannedStartDate

ACTIVITY_TYPE

Type

BUDGET_ORIGINAL_COST

EBSBudgetOriginalCost

BUDGET_PROPOSED_COST

EBSBudgetProposedCost

BUDGET_CURRENT_COST

EBSBudgetCurrentCost

BUDGET_ORIGINAL_QUANTITY

EBSBudgetOriginalQuantity

BUDGET_PROPOSED_QUANTITY

EBSBudgetProposedQuantity

BUDGET_CURRENT_QUANTITY

EBSBudgetCurrentQuantity

BUDGET_VERSION_NUMBER

EBSBudgetVersionNumber

BUDGET_VERSION_NAME

EBSBudgetVersionName

BUDGET_STATUS_CODE

EBSBudgetStatusCode

Assignment Mapping

This field mapping template can be used in an import project data and export project data business flow to create a Resource Assignment object with Assignment mappings in the destination application. The following fields will be mapped from each application.

EBS

P6

RESOURCE_CLASS_CODE

ResourceType

TASK_NUMBER

ActivityId

PLANNED_EFFORT

PlannedUnits

IS_PRIMARY_RESOURCE

IsPrimaryResource

RESOURCE_NUMBER

ResourceId

ROLE_NUMBER

RoleId

BUDGET_ORIGINAL_COST

EBSBudgetOriginalCost

BUDGET_PROPOSED_COST

EBSBudgetProposedCost

BUDGET_CURRENT_COST

EBSBudgetCurrentCost

PLANNED_COST

PlannedCost

BUDGET_ORIGINAL_QUANTITY

EBSBudgetOriginalQuantity

BUDGET_PROPOSED_QUANTITY

EBSBudgetProposedQuantity

BUDGET_CURRENT_QUANTITY

EBSBudgetCurrentQuantity

BUDGET_VERSION_NUMBER

EBSBudgetVersionNumber

BUDGET_VERSION_NAME

EBSBudgetVersionName

BUDGET_STATUS_CODE

EBSBudgetStatusCode

ACTUAL_QUANTITY

ActualUnits

ACTUAL_COST

ActualCost

WBS Field Mapping

This field mapping template can be used in the import project data and an export project data business flows to create a new WBS object in the destination application. The following fields are mapped in each application:

EBS

P6

TASK_NUMBER

Code

TASK_NAME

Name

SCHEDULED_START_DATE

StartDate

SCHEDULED_FINISH_DATE

FinishDate

ACTUAL_START_DATE

SummaryActualStartDate

ACTUAL_FINISH_DATE

SummaryActualFinishDate

BUDGET_ORIGINAL_COST

EBSBudgetOriginalCost

BUDGET_PROPOSED_COST

EBSBudgetProposedCost

BUDGET_CURRENT_COST

EBSBudgetCurrentCost

BUDGET_ORIGINAL_QUANTITY

EBSBudgetOriginalQuantity

BUDGET_PROPOSED_QUANTITY

EBSBudgetProposedQuantity

BUDGET_CURRENT_QUANTITY

EBSBudgetCurrentQuantity

BUDGET_VERSION_NUMBER

EBSBudgetVersionNumber

BUDGET_VERSION_NAME

EBSBudgetVersionNamer

BUDGET_STATUS_CODE

EBSBudgetStatusCode

Resource Fields

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

EBS

P6

RESOURCE_NUMBER

Id

RESOURCE_NAME

Name

RESOURCE_CLASS_CODE

ResourceType

EMAIL_ADDRESS

EmailAddress

EMPLOYEE_NUMBER

EmployeeId

UNIT_OF_MEASURE

UnitofMeasureAbbreviation

Resource Rates

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

EBS

P6

RATE_START_DATE

EffectiveDate

RATE

PricePerUnit

Role Fields

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

EBS

P6

RESOURCE_NUMBER

Id

JOB_NAME

Name

Role Rates

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

EBS

P6

RATE_START_DATE

EffectiveDate

RATE

PricePerUnit

Expense Category Fields

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

EBS

P6

EXPENDITURE_TYPE

Name

Financial Period Fields

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

EBS

P6

PERIOD_NAME

Name

END_DATE

EndDate

START_DATE

StartDate

Related Topics

Connecting with P6 EPPM

Supported Business Flows



Legal Notices
Copyright © 2013, 2015, Oracle and/or its affiliates. All rights reserved.

Last Published Tuesday, May 31, 2016