In version 4.x and 5.x the location of User Defined data in the database has changed.

UDFTYPE- This table contains the values for the type of User Defined Fields. These were previously displayed as the UDF labels.

This table contains the following fields

udf_type_id - This is a unique number assigned for each udf type. (Example: user_type_label of user_text1 might have a udf_type_id of 128)

table_name – The database table that this UDF is defined against. (Example: rsrc is the Resources data table)

udf_type_name – the fixed field name for the field name (Example: user_field_128)

udf_type_label – The customizable value that is displayed in the Project Management application (Example: user_text1)

logical_data_type – The type of data contained for this record (Example: FT_TEXT)

UDFVALUE- This table contains the value for each User Defined Field. These were previously the data assigned to a User Defined Field.

This table contains the following fields

udf_type_id – Defines from the UDFTYPE table the type of User Defined Field

fk_id – Foreign Key ID

proj_id – Project Unique key id for the Project the UDF is used in

udf_date – If a date type of UDF is used, this is the stored value for the UDF

udf_text – If a text type of UDF is used, this is the stored value for the UDF

udf_number – If a number type of UDF is used, this is the stored value for the UDF

SPECIAL NOTES:

If the UDF is an Activities User Defined Field, then the fk_id would be the task_id in the TASK table and the proj_id would be proj_id from the PROJECT table for the project utilizing this UDF.

If the UDF is an Activity Resource Assignment User Defined Field, then the fk_id would be the taskrsrc_id in the TRSRC table and the proj_id would be proj_id from the PROJECT table for the project utilizing this UDF.

If the UDF is an Activity Steps User Defined Field, then the fk_id would be the proc_id in the TASKPROC table and the proj_id would be proj_id from the PROJECT table for the project utilizing this UDF.

If the UDF is an Issues Defined User Defined Field, then the fk_id would be the issue_id in the PROJISSU table and the proj_id would be proj_id from the PROJECT table for the project utilizing this UDF.

If the UDF is a Project Expenses User Defined Field, then the fk_id would be the cost_item_id in the PROJCOST table and the proj_id would be proj_id from the PROJECT table for the project utilizing this UDF.

If the UDF is a Projects User Defined Field, then fk_id and proj_id will be the same. This will be the value for proj_id in the PROJECT table

If the UDF is a Resources User Defined Field, then the fk_id would be the rsrc_id in the RSRC table. The proj_id will be NULL since resources are not project specific.

If the UDF is a Risks User Defined Field, then the fk_id would be the rick_id in the PROJRISK table and the proj_id would be proj_id from the PROJECT table for the project utilizing this UDF.

Event Code: CVRJC-2214-A while importing a project in Project Management

*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          15-Jun-07 12:29 PM

Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    CVRJC-2214-A
Message:      
  TCCustomVirtualRow.getJoinedColItems: TASKACTV row
  has blank task_id

Context:
  1: TfrmWizImport.wizImportFinish
  2: TfrmWizImport.wizImportBeforeShowPage
  3: TfrmWizImport.RunImportWizard
  4: TfrmMain.actHomeExecute
  5: TfrmMain.actFileImportExecute
  6: TCFormManager.SetToolbar
  7: TfrmLogin.FormCreate
  8:
  9:
  10:

1. Download / Launch the xerFileParser&Builder.xls utility.
    
   SEE: Solution ID: prim4145 - ”How to use the XER Parser utility”
    


2. Click: Load XER file… (button on the ‘General’ tab)
   Browse to the file in question.
    


3. Once the XER is loaded, click: Diagnostics… (button on the ‘General’ tab)
    


4. Set the ‘xer File Parser & Builder’ dialog box to contain the following criteria:
    

• Select Diagnostics: ‘cross check FK’


• Select Table: ‘TASK’


• Select Field(s): ’TASK_ID’


• Select Secondary Table: ’TASKACTV’


• Select Secondary Field(s): ’TASK_ID’
   
  The screen should look like this:
   
  
   

Once complete, the ‘Diagnostic’ tab will list instances where ’TASK_ID’ values appear in the TASKACTV table, but not in the corresponding parent record (TASK table).
 

 

If the above fix does not work or you receive errors when performing the diagnostic, the steps below describe how to perform the diagnostic actions manually:

The orphaned records need to be removed.  The orphaned records are often associated with the same tasks orphaned in the UDFVALUE table. If you went through solution prim16871 already, please keep that orphaned task list and skip to step 6 below.

1. Use the xerFileParser&Builder.xls to repair the XER file.  More information can be found in solution prim4145: How to use the XER Parser utility.

Once the XER is open, Click on TASK.

2. Then highlight the task_id field.

Then copy and paste this column into a new Excel spread sheet.

3. Then go to the General tab and click on the TASKACTV table.

Click and highlight the task_id column.

Copy this column into the second column of the new Excel spread sheet that already has the TASK task_id column.

4. Then type the following formula into the second row of the third column. 

=VLOOKUP(B2,$A$2:$A$#,1,0)  Where B is the TASKACTV task_id column, A is the TASK task_id column and # is the row number of the last TASK task_id item for column A. 

Then double-click on the bottom right corner of that cell so that it automatically places the formula in the rest of the cells below.

5. Go to Data, Filter, and choose AutoFilter.  This will give you a drop down menu to choose a group of rows.  Look for all of the rows that have #N/A (may have to filter for a custom value).  These are the orphaned records. 

6. Now, delete the rows with matching task_id values on the TASKACTV  tab in the xerFileParser&Builder.xls. 

Finally, on the general tab, click the Build XER button.

Choose a new name for the “fixed” XER file.

Re-import the file.

When the Status cell is clicked on, the Parameter option goes back to None.

This has been fixed in Cost Management 4.1 Service Pack 1.

To download the latest service pack, see solution Cost Management 4.1 Service Pack 3

Go to Task Manager (<ctrl><alt><delete>), Performance tab and look at the available physical memory.

then add PM.EXE to the Data Execution Prevention Exception List:

Enabling the DEP Exception List

If DEP causes a problem with your applications, a dialog box appears to let you know.

Figure 4   Dialog box that appears if an application has attempted to execute and has encountered a problem with DEP

In cases where DEP causes application failures, Microsoft strongly recommends that you contact the application vendor to determine if a DEP-compatible update is available. Installing such an update is the preferred solution for application compatibility issues with DEP.

If no update is available for your application, follow these steps to access and to configure the Exception List. The Exception List is the list of applications that are excluded from DEP.

Note: The DEP exception list functionality is only available if the DEP configuration is set to protect all programs and services. If you configure your computer to protect only essential Windows components and services, the exception list is unavailable.

Requirements to perform this task

Enabling the DEP Exception List

To enable the DEP exception list

1.	Click Start, and then click ControlPanel.
2.	Under Pickacategory, click PerformanceandMaintenance.
3.	Under or Pick a Control Panel icon, click System.
4.	Click the Advanced tab. Figure 5   System Properties – Advanced tab
5.	In the Performance area, click Settings. Figure 6   Performance Options
6.	Click the DataExecutionPrevention tab. Figure 7   Data Execution Prevention tab
7.	Click Add.
8.	Locate and select the executable for the application that is failing, and then click Open.
9.	In the warning box, click OK. The selected program now appears in the DEP program area.
10.	Click Apply, and then click OK. A dialog box appears and informs you that you must restart your computer for the setting to take effect. Click OK.

Verifying DEP Exception List Settings Are Applied

To verify Memory Protection settings are applied

Cost Management is an Earned Value-based project cost management system. To properly collect performance information from status reported in a scheduled period, you must define the Earned Value Techniques for each task. 

There are several formulas used for Earned Value (EV) calculation including:

Percent/Units Complete:  EV is equal to the cumulative status percent value of a task multiplied against the task Budget At Completion. 
Note: This is used if percent start (i.e. user_number1) and percent complete (i.e. user_number2) is set to 1 when populated from Project Management.

Level of Effort (LOE): EV is equal to the scheduled budget value. Tasks with an LOE technique do not show a schedule variance.
Note: This is used if percent start and percent complete is set to 0 when populated from Project Management.

Discrete (Standard and Custom): EV is equal to the specified start percentage value (once the task is statused as started) then multiplied against the task Budget At Complete throughout the life of the task until the task is statused as complete. When the task is statused as 100 percent complete, EV is equal to the finish percentage value multiplied against the Budget at Complete (start and finish percent values should add together and equal 100 percent – 20/80, 40/60, etc.).
Note: For 20/80, percent start = .20 and percent complete = .80 when populated from Project Management.

Weighted Milestone: EV is equal to the percentage value (or weight) assigned to a milestone multiplied against the Budget At Completion for the task the milestone is assigned to when that milestone is statused at 100 percent complete (the percentage value or the weight for milestones should add together and equal 100 percent).
Note: This has to be set directly in Cost Management.  Can not be brought over from Project Management.

Note: After creating or importing status and EV Techniques, you must summarize performance.

Import Earned Value Technique field designations from Primavera Project Management using two of the Number fields ( user_number1 through user_number4 ) available in the Primavera Project Management project. These designations indicate the type of EV Technique to apply in Cost Management.  See solution prim18663 for more information.

Note: In Cost Management 4.1 service pack 1 or later, all Activity text and number user defined fields come over.  Does not have to be called user_number1, etc.

Complete the following steps to import Earned Value Techniques from Primavera Project Management:

1. Establish the desired Earned Value Technique designations in the Primavera Project Management Number fields.  The designations are listed in the following table:
   
   
   

   CM EV Technique       PM Percent Start Designation    PM Percent Complete Designation
   
   

   Percent/Units Complete     1                                                       1
   Level of Effort (LOE)          0                                                       0
   Discrete                           Percentage Start Factor                        Percentage Finish Factor
                                                                                                                                                               


2. Choose Window, Interface Mapping (if not already open).
    


3. Choose File, Open.  Navigate to the MyDocuments (or equivalent) folder and connect to the Project Management database UDL.
   Note: You can also access the Project Management database UDL in the Source Browser.  Choose Window, Source Browser.  Then double-click the Project Management database UDL.
   


4. In the Interface Mapping window, select the Primavera Project Management project from the list of projects.
    


5. In the Interface Mapping window, map the source fields to the destination fields as listed in the following table:
   
   
   

   Source Fields                                           Destination Fields           

   
   

   General: number1 (i.e. user_number1 )             Technique: Percent Start

   
   

   General: number2 (i.e. user_number2 )             Technique: Percent Complete
                                                                                                                  

   
    


6. Choose View, Project structure (if not already open).
    


7. Expand the project structure to the Baseline Basis you created that contains the baseline data.
    


8. Right-click on the Baseline Basis and choose Interface, External Source-(Primavera Project), Update.
    


9. Validate that the Earned Value Techniques were correctly imported per the following instructions:
   
   Right-click on the Baseline Basis and choose Summarize, Performance.  Right-click on the Baseline Basis and choose Refresh.  Select the desired task in the Project structure and bring up the Attribute Browser (Window, Attribute Browser).  In the Technique tab, verify the Earned Value Technique.
    


10. If desired, run an Earned Value Method report to view Earned Value Techniques for the Baseline Basis.  Right-click on the Baseline Basis and choose Report, WBS Support, Earned Value Method.

1.  In the Projects view, highlight the project, go to Window, Attribute Browser, General tab and in the Schedule Name Attribute add the project name as the Value.

Note:  The value for the Schedule Name Attribute needs to be the same name as the top WBS level (i.e. the Project Name that is in PM).

2.  Go to Window, Preferences Browser, Spreadsheet tab and check that the Setting for Cost Burdens Preference is checked for Prime.

3.  Highlight the Project, right click and Select Data View, choose your Cost data view.

4.  In the spreadsheet, place a cell in edit mode and go to View, Cumulative To Date.

5.  Highlight the project, right click, choose Interface, myPrimavera, and select the PM database.

6.  When Processing is complete, open PM, choose the WBS View and add the columns CM Actual Cost and CM Actual Esc Cost to view the actual cost.

ALTER TABLE TASK
DROP CONSTRAINT FK_TASK_PROJECT;

DROP INDEX NDX_TASK_1;

ALTER TABLE TASK
ADD CONSTRAINT FK_TASK_PROJECT
FOREIGN KEY (PROJ_ID) REFERENCES PROJECT (PROJ_ID);

CREATE INDEX NDX_TASK_1
ON TASK ( PROJ_ID );

1. Identify the activity type.
    
   NOTE: Please reference prim909 to understand the difference between Independent and Task type activities.
    


2. Change activity type to Independent.
    


3. Modify the resource calendar(s) to work on the desired days.
    


4. Add a Resource duration for the respective resources assignments in the resource dialog box.
    


5. Click: OK

When adding Time or Expenses, the default location in the Add Row pop up window is the ‘Project Location’.  This is the proper behavior if there is no position; In other words, time is being submitted against a role, not a position.

Below are the possible outcomes for the default location depending on what is selected in the Add Row window: 

• If a position or task is selected, the location should default from the position.


• If a role is selected, the location should default from the project.


• If an organizational unit is selected, the location should default from the resource.

NOTE: In unrestricted projects, resources can enter time against a position or a role on a project, and this will default to the position location or the project location respectively.

See also related issues:

If an application were able to write outside of its assigned storage area, it could overwrite another applications’, or even Windows’, instructions or data.  Rather than allow this (which could result in a loss of data or in a more serious crash), Windows generates an error.  “Access Violation” errors are the same things as “Invalid Page Faults” and “General Protection Faults” and all three are simply the symptoms of a computer ‘crash’.

Access Violation errors are rarely an indication of a major problem with the software and the difficulty in tracing the source of Access Violation errors lies in the fact that they are generic.  There isn’t a common way to fix all Access Violation errors because there are so many different (and unpredictable) situations which can cause them.

AVAA errors have also been observed to be a symptom of corrupt layouts, particularly if they occur mostly while working with layouts, e.g.

• Opening or saving layouts


• Adding or removing columns


• Changing bar definitions


• Applying filters

A corrupt layout may also be the cause of AVAA errors when opening the software (for example, if the user has disabled the welcome screen and set the software up to open the last project – this will also open the most recently used layout).

It is not possible to ‘fix’ a corrupt layout and if it is suspected that a layout has become corrupt, a new, clean layout should be created.  Because corruption can potentially be copied across if a corrupt layout is saved to create a new layout, it is best to open a layout which is rarely or never used and save this as the new layout.

For further information about how data can become corrupt, please see the following knowledgebase solution:

prim29241 ”Why data may become corrupted”

Client PC:

1. Closing down other programs or processes to free up resources for Project Manager.  Click Ctrl, Alt + Delete and choose Task Manager, Performance.  Compare Physical Total Memory to Available Memory.  AVAA0 errors may occur when less than 25% of total memory is available.

2. Log completely out of Project Manager/Project Management and then log back in.  Try running the process again.

3. Reboot the computer.

Database:

1. Restore a previous clean Backup of the Project or Database to determine if the Error still occurs. The problem could be data integrity related.

Steps to recreate:

1. Create a new team from a template.


2. Change one position to flex.


3. Alter some other data on the position.


4. Save and close.


5. Receive error.

Workaround:

Click Refresh link in upper left corner of web application.  This should remove the error.

To receive Primavera 8.5:

Please contact Primavera Customer Support by selecting the “Send us your feedback and comments by creating a support incident here” link below.

[Settings]
EnableMaterialResources=
CalcCosts=
LumpSumAsExpense=
MergeSubprojects=
LogName=P3 Activity Log Info
ConvertUnits=
[WBS]
WbsAsActCode=
KeepUnused=

Add any of the following parameters as needed:  

 *For more information, please view link–>  Solution ID: prim47812 ”Resource Units section of the prmconvert.ini file.”

1.  The project time entry must be restricted, either by position or task, in the Financial Rules of the project.  An unrestricted project cannot track Estimate to Complete (ETC).

2.  The Track Estimate to Complete checkbox must be checked in the Financial Rules of the project.

3.  The user to be notified of a change in ETC must be listed and selected (by checkbox) in the Financial Rules of the project.

4.  There must be a Work Breakdown Structure (WBS) on the project. 

• ETC cannot be tracked on Root, Summary or Milestone tasks.  In other words, ETC can only be tracked on a child task or a task with no children.  Only tasks that are eligible for ETC tracking will appear in the time entry drop-down.  However, if no WBS is in place the root task will be the only task available, and time can be entered against it.  If enabled, ETC will still be requested from the resource, but the ETC for the root task itself cannot be changed.

NOTE: The notification is triggered by the pollster which fires every night at midnight by default.  The notification should be received the next day.

NOTE: Whenever a resource enters time on a task that is being tracked for ETC, they will receive a pop up window upon submission where they can enter a new ETC.  If the resource chooses not to override the existing ETC, it will be adjusted by the amount of time entered, and no notification will be sent.

NOTE: The Estimate to Complete (ETC) Notification process does not involve the notifications set in the Configuration Application.

Note that the workflow is basically no longer valid as the underlying commitment referenced by the workflow no longer exists (often times, this is because the commitment was shortlisted).

Workaround: Send a new staffing request.

Example:

Activity Planned Duration = 20h

Resource Planned Duration = 100h

In the above example, both resources are non-driving. Therefore, the resource assignment’s Planned Duration will not roll-up to the activity level duration.

If the desired result is to have the resource assignments drive the activity, check the box “Drive Activity Dates”.

If the desired result is to have the Resource assignments not drive the activity and work on different dates, uncheck the box “Drive Activity Dates”.  Then a lag can also be placed on the Resource for it to start after the activity.

Note:  The resource calendar will be ignored if the Activity Type is set to Task Dependent.  The only time the Resource calendar is used is if the Activity type is Resource Dependent.

1.  Ensure that you have a full and current backup of the Project Management database.

2.  Run the following query against the database (substituting the name of the admuser in the PMDB schema if necessary).  Please be aware that any rows returned from that query are orphaned task records.

select * from admuser.task where proj_id not in (select proj_id from admuser.project);

3.  If the users of the Project Management software feel that their projects are complete and are working correctly, delete the orphaned records, using the following SQL statement:

delete from admuser.task where proj_id not in (select proj_id from admuser.project);

To resolve this issue with Interbase:

1.  Make a backup of the database.

2.  Open the Interbase Console by going to Start, Programs, Interbase, Interbase Console.

3. Log into the Interbase Console by right clicking the local server and selecting login.  Enter sysdba as your username and masterkey as your password.

4.  Expand the local server, right click database and select register.  When the box comes up select the location of your gdb file, and again enter sysdba and masterkey as the username and password.

5.  Go to the Tools menu, and select Interactive SQL.

6.  Enter the following line into the command window:

7.  Run a delete statement to get rid of the task_id’s for the invalid proj_id’s:

Delete from Task where task_id = <task_id that was returned in the previous select statement>;

    delete all the task_id’s that came back from the select statement

8.  Go to the Transactions menu, and choose Commit.

You will now be able to upgrade the database.