MOVE TAB

Use this tab to select data, based on a range of Costpoint Projects, to be moved into P3. The system moves Costpoint data into P3 in accordance with the mappings established in the Set Up Projects and Set Up Resources tabs and the most recent data that has been gathered and prepared in the Gather/Prepare tab. The P3 Errors grid details data that could not be moved from Costpoint to P3.

Execute this process after completing all mappings in the Set Up Projects and Set Up Resources tabs and gathering and preparing the data in the Gather/Prepare tab.   

Select Costpoint Project ID

Use this group box to select a range of Costpoint data to be moved into P3. The range must be within the range of data that has been gathered and prepared.

Range

Use the drop-down box to select the range of Costpoint Project IDs to be moved into P3.Valid options are "All," "One," "Range," "From Beginning," and "To End." The default for this field is "All." 

From

Enter, or use Lookup to select, the starting Costpoint Project ID to be moved into P3. If you select "All" or "From Beginning" in the Range field, this field will be inactive.

To

Enter, or use Lookup to select, the ending Costpoint Project ID to be moved into P3. If you select "All," "One," or "To End" in the Range field, this field will be inactive.

Move

Select this pushbutton to move the data that has been staged in Costpoint by the Gather and Prepare process into P3. 

P3 Errors Grid

The errors grid displays information on data that could not be moved from Costpoint to P3. This includes a review of the data and an error message indicating why the error occurred  (e.g., data could not be transferred because an employee that charged time to a Costpoint project ID has not been mapped to P3. The error message would be, "Resource activity has been detected with no resource mappings."). If errors occur, correct the mappings or make sure project IDs exist and re-run the Move process.

There are two types of errors in general:

1. Preprocessing errors (before the actual Move operation) where the gathered rows are examined to ensure that associated mappings exist. The system generates error messages if the gathered rows are not mapped. 

2. During the Move operation, the system generates error messages if P3 does not have the mapped Project and/or Activity and/or Resources.

Errors

Processing errors

There are three types of preprocessing errors:

• No mappings for this gathered row (Labor): "Empl/Vend-Emp/Vend/Org/Acct/PLC/GLC" = "EE/VE/VV/OO/AA/PP/GG"        

• This message indicates that there is no Grouping information available for this gathered labor row (i.e., no mapping exists for the labor side of the project). An example of this message is:

• No mappings for this gathered row (Labor): "Empl/Vend-Emp/Vend/Org/Acct/PLC/GLC" = "1001/100001/100001/1.01/1001-039/EN/EN"

• No mappings for this gathered row (Non-Labor): "Acct/Org" = "AA/OO"

• This message indicates that there is no grouping information available for this gathered non-labor row (i.e., no mapping exists for the non-labor side of the project). An example of this message:

• No mappings for this gathered row (Non-Labor): "Acct/Org" = "1001-043/1.01"

• No mappings for this gathered row: "Empl/Vend/Vend-Empl" = "EE/VV /EV "

• No mappings for this gathered row: "Empl/Vend/Vend-Empl/Org" = "EE/VV /VE/OO "

• No mappings for this gathered row: "Empl/Vend/Vend-Empl/Acct" = "EE /VV/VE/AA"

• No mappings for this gathered row: "Empl/Vend/Vend-Empl/GLC" = "EE /VV/VE/AA/GG"

• No mappings for this gathered row: "Empl/Vend/Vend-Empl/PLC" = "EE /VV/VE/PP"

• No mappings for this gathered row: "GLC" = "GG"

• No mappings for this gathered row: "GLC/Org" = "GG/OO"

• No mappings for this gathered row: "GLC/Acct" = "GG/AA"

• No mappings for this gathered row: "PLC" = "PP"

• No mappings for this gathered row: "PLC/Org" = "PP/OO"

• No mappings for this gathered row: "PLC/Acct" = "PP/AA"

• No mappings for this gathered row: "Acct" = "AA"

• No mappings for this gathered row: "Many-Acct" = "AA"

• No mappings for this gathered row: "Acct/Org" = "AA/OO"

These 14 error messages are generated for the various mappings (11 for labor, 3 for non-labor).  If there is at least one mapping for each type of cost (labor/non-labor) for the project, the application will attempt to match the gathered row with a specific grouping. If there is no match in the mapping setup, an error is generated.  For example, if the project has "GLC" on the labor side, the system compares the "GLC" column of the gathered row with the contents of the mapping table for the labor side of the project.  In other words, if it finds "Engineer" as the GLC of the gathered row, it goes to the same project in the mapping table and tries to find "Engineer". If it fails to find it (even though other GLCs have been mapped), the system produces the following error:

• No mappings for this gathered row: GLC = "Engineer"

Move Errors

The following messages are generated during the actual Move operation.

• P3 Project ID does not exist in P3.

• The P3 Project mapped in the Set Up Projects Mapping grid no longer exists in P3.  The mapping columns are automatically validated when mappings are created. The identified P3 Project was deleted from P3 after the project mapping was created.

• P3 Activity ID does not exist in P3 for the specified P3 Project ID.

• The P3 Activity mapped in the Set Up Projects Mapping grid no longer exists in P3. The mapping columns are automatically validated when mappings are created. The identified P3 Activity was deleted from P3 after the project mapping was created.

• P3 Resource ID does not exist in P3 for the identified P3 Activity.

• The P3 Resource ID mapped in the Set Up Resources Mapping grid no longer exists in P3.  The mapping columns are automatically validated when mappings are created. The identified P3 Resource was deleted from P3 after the resource mapping was created.                                

• Missing P3 "BURDEN" resource - it must be created in P3 and assigned to P3 activity         

• Burden costs are generated if the option Burden Type in the Set Up Project tab is either "T" or "A." These costs are summarized in gathered non-labor rows. The application looks for the "BURDEN" resource in P3 to move them in.

The interface does not update the data date in P3 during the Move process.  Update the data date and schedule the project after the interface is run. 

Burden is moved as described below only if burden is selected to be gathered and prepared, has been mapped, and a resource called "Burden" is created in P3 and assigned to the mapped P3 Activity ID.

• At each Costpoint Project ID where burden is mapped to be moved, the system adds all Burden Costs for Labor and Non-labor to create a total burden cost.  The value for the total burden cost is moved into the P3 resource identified as "Burden" for the P3 Project and Activity ID mapped to the Costpoint Project ID.

• Burden is defined as indirect cost allocations excluding fee.

Current Period and Inception to Date Hours and Costs are always over written in P3 when using the interface.  The Close-out function in P3 which adds current period units and cost data to the Inception to date unit and cost data and then zero's out the current period unit and cost data does not need to be executed when using the interface.

The Range of data that is moved into P3 must be part of the Range of data that was gathered and prepared.  For example, if you gather and prepare data for one Costpoint Project ID and select to move ALL data, only the data for the one Costpoint Project ID that has been gathered and prepared is moved into P3.