Primavera® P6™

SDEF Conversion
Copyright © Primavera 1999 - 2007. All rights reserved.

While reasonable efforts have been made to ensure the accuracy of this document, Primavera assumes no
liability resulting from any omission or inaccuracies in this document or from use of the information obtained
herein. Primavera reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in
content hereof with no obligation to notify any person of revisions or changes. Primavera does not assume any
liability arising out of the application or use of any product described herein; neither does it convey license under
its patent rights or the rights of others.

Please send your comments to:

Primavera Systems, Inc.

Three Bala Plaza West
Bala Cynwyd, PA 19004
Telephone: 1-610-667-8600
FAX: 1-610-667-7894
World Wide Web site: http://www.primavera.com

Computer Software Copyrights: The Primavera software products described in this document may not be
copied, reproduced, modified, or distributed in any manner without Primavera's express written permission.

Use and Disclosure Restrictions: The software described in this document is the property of Primavera
Systems. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the
terms of the agreement.

U.S. Government Restricted Rights: If the Software is acquired for or on behalf of the United States of
America, its agencies and/or instrumentalities (“U.S. Government”), it is provided with RESTRICTED
RIGHTS. The Software and accompanying documentation are “commercial computer software” and
“commercial computer software documentation,” respectively, pursuant to 48 C.F.R. 12.212 and 227.7202, and
“restricted computer software” pursuant to 48 C.F.R. 52.227-19(a), as applicable. Use, modification, repro-
duction, release, performance, display or disclosure of the Software and accompanying documentation by the
U.S. Government are subject to restrictions as set forth in this Agreement and pursuant to 48 C.F.R. 12.212,
52.227-14 (Alternate III), 52.227-19, 227.7202, and 1852.227-86, as applicable.

Trademarks: Primavera, the Primavera sundial logo, P3, P3e, P3e/c, Primavera Enterprise, Primavera Evolve,
Primavera Expedition, Primavera Project Planner, Primavera TeamPlay, Primavision, PrimeContract, and
SureTrak are either trademarks, registered trademarks, or service marks of Primavera in the United States and/or
in other countries. All other trademarks mentioned herein are the property of their respective owners.
Certain products included in the software require the following disclosures:

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on
an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and limitations under the License.

*****

The Apache Software License, Version 1.1

Copyright (c) 2000 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:

1 Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2 Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3 The end-user documentation included with the redistribution, if any, must include the following acknowl-
edgment:
"This product includes software developed by the Apache Software Foundation
(http://www.apache.org/)."

Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party
acknowledgments normally appear.

4 The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products
derived from this software without prior written permission. For written permission, please contact
[email protected].
5 Products derived from this software may not be called "Apache", nor may "Apache" appear in their name,
without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE
SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

*****

Copyright 1994-2006 Sun Microsystems, Inc. All Rights Reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:

■ Redistribution of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
■ Redistribution in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.

Neither the name of Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote
products derived from this software without specific prior written permission.

This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDI-
TIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL NOT BE
LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR
DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS
LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT,
SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO
USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.

You acknowledge that this software is not designed, licensed or intended for use in the design, construction,
operation or maintenance of any nuclear facility.

*****

Portions copyright (c) Macromedia, Inc. All rights reserved.

*****

Copyright (c) 2002-2006 JGoodies Karsten Lentzsch. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:

■ Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
■ Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
■ Neither the name of JGoodies Karsten Lentzsch nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.

*****

Printed in the United States of America

Table of Contents
SDEF Overview .......................................................................................8
Obtaining SDEF specifications..................................................................... 8
Primavera’s SDEF Conversion Utilities ....................................................... 9

Conversion Considerations.................................................................10
Activity Code Structure Requirements ....................................................... 13

Using Primavera’s SDEF Conversion Update....................................14

Convert a Project Management Module Project to SDEF .......................... 14
Convert an SDEF File to a Project Management Module Project .............. 15

Primavera 7
SDEF Overview
In 1986, the US Army Corps of Engineers recognized the need for a Standard
Data Exchange Format (SDEF) to facilitate the exchange of data among
contractors using various project management tools. The format chosen was a
132-character per line, fixed-length ASCII file, with data items, field positions,
and field lengths explicitly defined by the SDEF specification.

Obtaining SDEF specifications

The complete SDEF specification document is available online from the US
Army Corps of Engineers’ official library for Engineer Regulation ER1-1-11
dated June 15, 1995, located at
http://www.usace.army.mil/publications/eng-regs/er1-1-11/entire.pdf

8
 SDEF Overview

Primavera’s SDEF Conversion Utilities

In Primavera’s Project Management module, you can exchange project data with
other Primavera users by converting projects to Primavera’s Proprietary
Exchange Format (XER). Using Primavera’s import/export capability, you can
then convert an XER file an SDEF data file, and vice versa. Primavera converts
data between the XER and SDEF formats using the following utilities:
Š SDEF to XER (P330XERConvert.exe)
Š XER to SDEF (XERP330Convert.exe)
Use Primavera’s SDEF conversion capabilities when you want to
Š exchange project data with contractors and owners who do not use
Primavera products.
Š provide project data in the SDEF format whenever required by your contract.

Release Notes 9
 Conversion Considerations

Conversion Considerations
Primavera projects can store far more data than the SDEF specification requires.
For example, the SDEF file structure allows for only one application of a
resource per activity, while Primavera enables you to apply a resource to an
activity repeatedly using resource lags and durations.
Primavera projects intended for use with the SDEF interface should comply with
the SDEF specification. You should not utilize the additional capabilities that
Primavera offers because the SDEF file structure cannot store the additional data.
The following are items to consider when exchanging data between the XER and
SDEF formats:
Š Activity limit: SDEF files cannot contain more than 10,000 activities.
When converting XER files to SDEF, only the first 10,000 activities are
exported.
Š Activity descriptions: The SDEF file structure only allows activity
descriptions up to 30 characters long. When converting XER files to SDEF,
only the first 30 characters of the description are exported.
Š Suspend and resume dates: The SDEF standard does not recognize
suspend and resume dates, so suspend and resume dates are not exported to
SDEF.
Š Activity totals: The SDEF file structure does not store individual resource
budgets as Primavera does. Instead, SDEF stores total budgeted cost and
total budgeted units for each activity. The conversion utility totals costs and
units for each activity’s resources in conformance with the SDEF standard.
Š Cost per unit: The SDEF standard uses a calculated cost per unit for each
activity defined as the activity’s budget cost divided by its budget quantity.
Primavera’s SDEF conversion conforms to this standard.
Š Milestones: The SDEF standard does not recognize milestones as activities.
If your Primavera project uses milestones, the converter stores these as zero-
duration activities.

Release Notes 10
 Conversion Considerations

Š Calendars: Calendars in SDEF are only one character; therefore, calendar

names from Primavera are truncated to one character. You are limited to 36
calendars in SDEF (A through Z and 0 through 9).
Š Required User-defined Fields (Contract Number and Contractor
Name): SDEF files contain fields named Contract Number and Contractor
Name. These fields do not exist in the Project Management module. When
converting an SDEF file to XER, if the Contract Number and Contractor
Name fields do not exist as user-defined fields (UDFs) in the Project
Management module project, they will be automatically created during the
import process. If the Contract Number and Contractor Name UDFs were
previously defined in a project (to be used for a different purpose), you
should rename the preexisting UDFs before importing an SDEF file.
To store this data in a Project Management module project before you
convert it to SDEF, you must create Project UDFs named 'Contract Number'
and 'Contractor Name'. These UDFs must have a Data Type of Text. If you
do not create these UDFs, the Contract Number and Contractor Name fields
will be blank when you convert an XER file to an SDEF file.
In SDEF files, values in the Contract Number field cannot be longer than six
characters. When a Contract Number UDF value is more than six characters,
this value is truncated to the first six characters when you convert to SDEF.
Š Required User-defined Field (STMA): SDEF files store activity stored
material cost data in a field named STMA. This field does not exist in
Primavera. When converting an SDEF file to XER, if the STMA field does
not exist as a UDF in the Project Management module project, it will be
automatically created during the import process. If the STMA UDF was
previously defined in a project (to be used for a different purpose), you
should rename the preexisting UDF before importing an SDEF file.
To store this data in a Project Management module project before you
convert it to SDEF, you must create an Activity UDF named 'STMA'. This
UDF must have a Data Type of Cost. If you do not create this UDF, the
STMA field will be blank when you convert an XER file to an SDEF file.

Release Notes 11
 Conversion Considerations

Š Activity IDs: The SDEF standard does not support activity IDs longer than
ten characters, while Primavera projects may contain activity IDs longer
than ten characters. Activity IDs are truncated to the first ten characters
when converting a Primavera project to SDEF. Due to this truncation, it is
possible that duplicate activity IDs will be encountered during the
conversion; if so, the conversion is aborted. To ensure that conversions to
SDEF are not aborted, Primavera projects should not contain activity IDs
longer than ten characters. If activity IDs must be longer than ten characters
in Primavera, the first ten characters must be unique.
Š Durations: The SDEF standard does not support durations longer than 999
days. If your Primavera project contains durations longer than 999 days,
these durations will convert to zero in the SDEF file.
Š Data mapping: The following table describes how some Primavera data is
converted to SDEF:

SDEF Field Primavera Field or Calculation

Total Qty Budgeted Units for the activity assignment
Cost Per Unit Budgeted Cost divided by the Budgeted Units for
the activity assignment
Qty to Date Actual Units for the activity assignment
Activity Cost Budgeted Cost for the activity assignment
Cost to Date Actual Regular Cost for the assignment plus the
Stored Material Cost (STMA) for the activity
Note: The Stored Material Cost is derived from
the Activity UDF named 'STMA'. Refer to the
“Required User-defined Field (STMA)” bullet
item on the previous page for more information.

Release Notes 12
 Conversion Considerations

Activity Code Structure Requirements

The US Army Corps of Engineers requires all projects to use a predefined
activity code structure. This structure specifies the name and maximum length of
each activity code in the project. The SDEF format adheres to this structure;
therefore, all Primavera projects being exported to SDEF format must have an
activity code structure that exactly matches the predefined structure.
The following table shows the required activity code structure:

Max
Code Length Description
WRKP 3 Workers per day
RESP 4 Responsibility
AREA 4 Area
MODF 6 MOD or Claim #
BIDI 6 Bid Item
PHAS 2 Phase
CATW 1 Category of work
FOW 30 Feature of work

Note: The Description column is for your information only. The Project
Management module does not support activity code descriptions. When
creating the activity code structure, you only need to create each code
and specify the maximum length. You also need to make sure you define
each activity code as a global activity code.
Note: When converted, the code value for the “Feature of Work” activity
code displays in the Activity Codes Description column of the XER file,
and a unique code value is generated by the converter. For all other
activity codes, the code value displays in the Activity Codes Code Value
column of the XER file.

Release Notes 13
 Using Primavera’s SDEF Conversion Update

Using Primavera’s SDEF Conversion

Update
This section explains how to:
Š convert Project Management module projects to SDEF files
Š convert SDEF files to Project Management module projects.

Convert a Project Management Module Project to SDEF

Complete the following steps to convert a Project Management module project to
SDEF:
1. In the Project Management module, open the project you want to convert
and export it to an XER file.
For specific instructions on exporting projects to an XER file, refer to the
Primavera Administrator’s Guide.
2. Double-click XERP330Convert.exe in the c:\Program Files\Common
Files\Primavera Common\Convert folder to run the conversion utility.
3. In the XER to SDEF Project Conversion dialog, click Browse to select the
XER file you want to convert to SDEF, then click Next.
4. Enter the path and filename for the SDEF file you want to create, then click
Next.
5. Select the Don’t transfer costs option if desired, then click Finish. The Don’t
transfer costs option was added to the program for use primarily on cost
reimbursement contracts where a firm fixed price does not exist.
When the conversion is complete, the utility creates a log file named
[filename]_ConversionFromP3e.log. View the log file to obtain
information about the conversion, including problems that were encountered
during the conversion.

Release Notes 14
 Using Primavera’s SDEF Conversion Update

Convert an SDEF File to a Project Management Module

Project
Complete the following steps to convert an SDEF file to a Project Management
module project:
1. Double-click P330XERConvert.exe in the c:\Program Files\Common
Files\Primavera Common\Convert folder to run the conversion utility.
2. In the SDEF to XER Project Conversion dialog, choose SDEF as the
conversion type, then click Next.
3. Click Browse to select the SDEF file you want to convert, then click Next.
4. Click Browse to select the XER file you want to overwrite or enter a new
XER filename, then click Next.
5. Click Finish.
6. In the Project Management module, choose File, Import. Follow the wizard
prompts to import the XER file.
For specific instructions on importing XER files in the Project Management
module, refer to the Primavera Administrator’s Guide.

Release Notes 15