For you information, this is a problem that I have discovered. Not sure of it is mine alone, or a global issue. This could be a huge issue in some cases.
I recently exported material resource assignments from Primavera to Excel. In the resulting output, all of the material values were off by a factor of 10 (i.e. what was entered into Primavera as 1,000, was exported as 10,000). Upon further investigation, we realized that every one of the exported values ended with a "3".
The material resource was assigned a unit of measure (UoM) of m3. It appears that the numeric value from the UoM was exported with the actual quantity, in the quantity field, as if it were part of the value itself. An export of the UoM field indicated m3 as one would expect. With testing, it was confirmed that this did not happen if the UoM chosen was alphabetic only, and not alphanumeric (i.e. CuM wasn’t a problem while m3 was).
Our platform is Primavera 5.0, SP1, running on a SQL Server 2000 backend (soon to be upgraded when IT has the infrastructure fully in place). I am unsure if this problem exists with other versions.
I was unable to find this issue referenced directly on the Primavera knowledgebase, but I have submitted a support request in order to get it logged.
Tony
I recently exported material resource assignments from Primavera to Excel. In the resulting output, all of the material values were off by a factor of 10 (i.e. what was entered into Primavera as 1,000, was exported as 10,000). Upon further investigation, we realized that every one of the exported values ended with a "3".
The material resource was assigned a unit of measure (UoM) of m3. It appears that the numeric value from the UoM was exported with the actual quantity, in the quantity field, as if it were part of the value itself. An export of the UoM field indicated m3 as one would expect. With testing, it was confirmed that this did not happen if the UoM chosen was alphabetic only, and not alphanumeric (i.e. CuM wasn’t a problem while m3 was).
Our platform is Primavera 5.0, SP1, running on a SQL Server 2000 backend (soon to be upgraded when IT has the infrastructure fully in place). I am unsure if this problem exists with other versions.
I was unable to find this issue referenced directly on the Primavera knowledgebase, but I have submitted a support request in order to get it logged.
Tony