How do I resolve the 'not a valid integer' error when performing an SDEF import?

 

Introduction

A common practice for QCS users is to perform imports from their Primavera scheduling system. In QCS this is referred to as a "NAS import" but most QCS users and the technicians at the RMS Support Center use the term "SDEF import". A SDEF import is a very complex operation. QCS looks at many factors while importing data from a SDEF file and as a result many different error messages may be presented to the QCS user. A common error message, shown below, is the "not a valid integer" error. In this article we will show what causes this error and how to resolve it.

 

Cause of the Error

All SDEF exports created by Primavera must adhere to the SDEF standard established by the USACE. Part of this standard requires that "Project ID" used in Primavera for the USACE contract be four characters long. As Primavera does not validate the number of characters you use for the project ID you must make sure that exactly four characters are used. If an amount other than four characters are used then QCS will report errors during import. Here is what happens. Say a project ID of "622" was used in Primavera on a USACE contract as shown in the screen shot below:

When the SDEF file is created Primavera does not validate the length and as a result the SDEF file shown below is created:

In the "PROJ" line Primavera enters the three character project ID of "622". Since the ID is one character short the following fields are all shifted left by one character including the project start and finish dates on the far right. These two dates are read by QCS during the SDEF import. If they are shifted left by one character then in the SDEF screen shot above where QCS expects to see the day "26" it sees "6N' and since "6N" cannot be converted into a number QCS reports the error shown in the first screen shot.

 

Resolving the Error

Thankfully resolving the error is much simpler than explaining it. To resolve this error the Primavera user will have to change the project ID from "622" to something that is four characters long like "0622".

The same logic as described above also applies to project ID that are longer than four characters.