Update Schedule Sheet Activities V2 from Oracle® Primavera™ P6 XML

Description

This method will insert/update activities into any project or shell schedule sheet. It will not overwrite existing activities in the schedule sheet based on the data mapping parameter.

Support

This method can only support updation of activities in project or shell level schedule sheets.

Installation: ASP and Self host

Level	Yes or No
Company Level	No
Project or Shell Level	Yes

Prototype

public XMLObject updateScheduleActivitiesV2(String shortname, String authcode, String projectNumber, String sheetName, String sheetXML, String scheduleOptions);

Parameters

Parameter	Description
shortname	Identifier of the company, company's short name
authcode	Authentication code for the company, in text string
projectNumber	Identifier of a project or shell.
sheetname	Name of Schedule Sheet to import activities into.
sheetXML	Content of activities to import. This is obtained from the Primavera P5/P6 xml content. The Primavera XML content should be generated by exporting the full Primavera project.
scheduleOptions	This element will allow message to carry optional information. Following are the tags under this element
MapName	Name of the data mapping that should be used while processing XML file
ActivityIdentifier	Possible values are GUID, ID. ID is the tag of Activity Id in Primavera.
CBS_NoOfLevelsToMerge	This parameter will take a numeric value. This parameter can be used by user to specify how many levels (CBS Levels) in P6 XML file should be merged together. EXAMPLE: Assume that P6 has following structure (5.ON.DA.DA03.F350.U11.095.ABC20.CAct04) If you specify 3 then two levels will be merged together. But which 3 segments will be based on the next parameter (CBS_startmergefrom)
CBS_StartMergeFrom	This parameter will take a numeric value. Value of this parameter will be used to determine the level from which this merge should start. EXAMPLE: In the above example, if a user specifies 2, then system will start from level 2 and merge ON, DA and DA03. So after the merge the CBS Code build by import program will be 5.ONDADA03.F350.U11.095.ABC20.CAct04
ActivityDeletion	Indicate to delete activities from schedule sheet in Primavera Unifier if it is deleted in P6.

Return Value

See Return Values.

Sample Method

updateScheduleActivitiesV2("acme","acme_authcode","Proj-0001","Schedule Sheet 001", "<XML Content>","Data Mapping 001","Id");

Additional Information

You must perform appropriate data mapping setups on the target schedule sheet. This includes mapping Unifier Schedule Sheet columns to Primavera XML elements, and setting appropriate XML Import options.

This method will insert/update activities into any project or shell schedule sheet. The method will utilize the data mapping setup to update only those elements that are mapped.

The method errors out if the data mapping option does not allow merge.

Activities are uniquely identified within Primavera by the Globally Unique Id (<GUID>) or the identified provided as part of XML file. GUID will be used if ActivityIdentifier is empty or blank.

Resource assignments will be imported (inserted/updated) if the ‘Import Resource Assignments' checkbox is selected. Resource assignments will be matched by Resource Name.

This service can be used for both Project (Standard) and Shells of cost code type CBS.

Activity identified with this creation method can be GUID or ID
On the options tab of Data Mapping, merge existing schedule option should be checked.
CBS Code will be derived automatically based on the XML file. For more information see Associate CBS Codes with Activities.
In a Project, the activities are grouped together by CBS Codes.

The following shows a sample project data:

In this sample, the activities A1160, A1180 are under a CBS Code built by the following sequence of codes:
- P -00050-EV-C-OB.5 Execute
- P -00050-EV-C-OB.5.ON Onshore
- P -00050-EV-C-OB.5.ON.DA LNG Facilities
- P -00050-EV-C-OB.5.ON.DA.DA03 LNG Shared Facilities
- and so forth ...
In this sample, activity A1160 (Plot Plan) is associated with CBS Code: P -00050-EV-C-OB.5.ON.DA.DA03.F350.U11.095.ABC20.CAct04. The XML file that is generated by Unifier does not include the entire string of CBS Code with all segments. The structure of the XML file is built based on the Parent/Child CBS segments. As a result, activity A1160 (Plot Plan) has reference to its immediate parent segment, which in this example is CAct04, only. The CAct04 segment will have a reference to ABC20 segment, the ABC20 has reference to 095 and so on.

To associate an activity with a CBS Code, the system will go through this hierarchical structure of CBS segments to build the final CBS Code. Unifier will perform this function when CBS Code import option is checked on the Options tab of Data Mapping. The CBS Code string generated will then be validated with leaf level CBS Codes created under Cost Manager. If the CBS Code is available, then the activity will be associated with the CBS Code. If the CBS Code is not available, then the import process will fail.

Additional options are available to create entire string of CBS Code. These options can be used to address any structural differences between the way CBS Codes are built in Unifier Cost Manager and CBS Codes in Primavera Project.
- Levels: User can choose number of CBS segments that should be considered while processing a Primavera XML file. For example, if user enters 8 then last segment CAct04 will not be considered while building CBS Code.
- Suffix Mask: User can optionally enter a suffix mask, which will be added to the end of CBS Codes built based on Primavera XML file. Users can either enter a constant value of select a data element from activity attribute form.
  Note: With the help of this data element being selected as suffix, it is possible to build CBS Code and assign it to an activity based on attributes of activities coming from P6 instead of the CBS Code hierarchy of the activities.
ActivityDeletion tag logic is based on the "Delete Activity" checkbox available on data mapping window in Unifier. Following is the logic for this tag

Delete Checkbox	Activity Deletion	Behavior
Unchecked	Auto or Confirm	Activity Deletion tag is ignored. Activities that are removed under source schedule will not be removed from the Schedule Sheet
Checked	Auto	Activity Deletion tag is considered Activities that are removed under source schedule will be deleted automatically under Unifier Schedule Sheet.
Checked	Confirm	Activity Deletion tag is considered Activities that are removed under source schedule will not be deleted. System will return an error and will not update Primavera Unifier schedule sheet. If no activities are removed under the source schedule then the system will update the Schedule Sheet.

Delete Checkbox

Activity Deletion

Behavior

Unchecked

Auto or Confirm

Activity Deletion tag is ignored.

Activities that are removed under source schedule will not be removed from the Schedule Sheet

Checked

Auto

Activity Deletion tag is considered

Activities that are removed under source schedule will be deleted automatically under Unifier Schedule Sheet.

Checked

Confirm

Activity Deletion tag is considered

Activities that are removed under source schedule will not be deleted.

System will return an error and will not update Primavera Unifier schedule sheet.

If no activities are removed under the source schedule then the system will update the Schedule Sheet.

ActivityDeletion tags are only considered for updateScheduleSheetFromFileV2 service and not for create.