Part 4

i
Table of Contents
Part 4: Batch and File Structures 1
Using the P3 Batch System 4
Overview 5
General Rules for Batch Processing 8
P3 Screen/Batch Function Table 11
Sample Run Streams 15
Standard Records 31
ACAT 32
ACCESS 34
ACTV 37
ACTVR 40
ADD 41
ALIA 43
BCAL 44
BRT1 45
BRT2 46
CALENDAR 47
CALENDAR LIST 49
CDEF 50
CDI 52
CHDR 54
CODE 55
COPY AND RENAME 57
COTL 58
CURV 60
CUSD 62
DATE 64
DRT1 66
DRT2 67
Table of Contents ii
END 68
ESTABLISH TARGET 69
ETC 70
EXECUTE 72
GENERATE (command) 73
GENERATE (record) 74
INPUT 79
INTERRUPT 81
LIST 82
LIST STATISTICS 83
MCAL - Hourly 84
MCAL - Daily 86
MCAL - Weekly and Monthly 87
MHOL 88
PCAL 90
PERIOD CLOSEOUT 92
PREC 93
PRED 95
PROJ 97
RATE 99
RCAL 101
RHOL 103
REMOVE 104
RESR 105
RETL 109
RETURN 111
RLIM 112
SNUM 114
SUCC 115
RULES 117
TITLE DATA 119
TITLE LIST 120
UPDATE 121
WBSA 123
WBSD 124
WBST 125
Table of Contents iii
Batch Error Messages 126
P3 2.0 Files 131

P3 Data Tables 132
P3 Data Table Connections 139
P3 File Structures 140
Project Directory File (XXXXDIR.P3) 141
XXXXDIR.P3: Data in 100001 record 146
USERFIL.P3 149
XXXXACT.P3 152
XXXXREL.P3 155
XXXXRES.P3 156
XXXXSPR.P3 158
XXXXLOG.P3 159
XXXXWBS.P3 160
XXXXTTL.P3 161
XXXXACC.P3 162
XXXXRLB.P3 163
XXXXITM.P3: Data in Dictionary Records 165
XXXXITM.P3: Data in Data Item Value Records 166
XXXXSTR.P3 167
XXXXHOL.P3 168
XXXXCAL.P3 169
XXXXSRT.P3 171
XXXXREP.P3 / XXXXPLT.P3 172
XXXXAC2.P3 175
USERS50.P3 176
XXXXLAY.P3 177
XXXXSTW.P3 179
P3.INI Options 180
SureTrak 2.0 Files 201

SureTrak File (XXXXSTW.P3) 202
Webster Timesheet File (XXXXTIM.P3) 203
STWIN.INI File Settings 204
Table of Contents iv
Expedition 6.0 Files 229

Expedition Database Tables 230
All Documents Module (View) 231
Attachments (Base) 233
Change Management Module (View) 234
Change Management Module (Base) 241
Change Orders Module (View) 248
Change Orders Module (Base) 254
Contacts Module (View) 260
Contacts Module (Base) 264
Contracts Module (View) 267
Contracts Module (Base) 273
Contracts & Purchase Orders Module (View) 279
Conversion (Base) 283
Correspondence Received Module (Base) 284
Correspondence Received & Correspondence Sent Module (View) 286
Correspondence Sent Module (Base) 288
Cost Worksheet Module (View) 290
Cost Worksheet Module (Base) 292
Custom Data Items (Base) 297
Daily Reports Module (Base) 298
Distribution Lists (View) 303
Distribution Lists (Base) 304
Drawing Sets Module (Base) 305
Drawings Module (View) 307
Drawings Module (Base) 309
Field Initialization (Base) 315
Filters (Base) 316
Generate (Base) 317
InBasket Module (Base) 318
Insurance Module (Base) 320
Invoices Module (Base) 322
Issues Module (Base) 323
Item Descriptions (View) 325
Item Descriptions (Base) 328
Letters Module (Base) 331
Table of Contents v
Mail (View) 333

Mail (Base) 334
Materials Delivery (View) 336
Materials Delivery (Base) 339
Meeting Minutes Module (Base) 343
Notepads Module (Base) 345
Notices Module (Base) 347
Paper Sizes (Base) 350
Project Preferences (Base) 351
Proposals Module (View) 356
Proposals Module (Base) 360
Punch List Module (Base) 364
Purchase Orders Module (View) 366
Requests Module (Base) 371
Requisitions Module (View) 374
Requisitions Module (Base) 379
Roles (View) 384
Roles (Base) 385
Saved User Layouts (Base) 386
Security (Base) 387
Selection Tree (Base) 388
Sorts (Base) 390
Specification Sections (Base) 391
Status (View) 392
Status (Base) 393
Submittal Packages Module (View) 394
Submittal Packages Module (Base) 396
Submittals Module (View) 398
Submittals Module (Base) 405
Telephone Records Module (Base) 412
Transmittals Module (Base) 414
Trends Module (View) 420
Trends Module (Base) 422
Wizards (Base) 424
vi
Part
4 Batch and File Structures
In this part:
Using the P3 Batch System

Standard Records
P3 2.0 Files
SureTrak 2.0 Files
Expedition 6.0 Files
Using the P3 Batch System explains this powerful tool for inputting,
updating, reporting, and processing project data using text file
commands, rather than a user interface.
Standard Records perform many of the functions available in the
program's dialog boxes from adding a new project to building project
dictionaries. This chapter details how to format these records using a
text file.
P3 2.0 Files details the file structures of all P3 data files. Use this information when writing programs that directly access P3 data using RA,
Btrieve, OLE automation, or ODBC. This chapter also includes the
content, format, and data table relationships of the Btrieve data dictionaries used for ODBC access.
SureTrak 2.0 Files describes SureTrak-specific information stored in the

P3 file set, resource information stored by Webster, and SureTraks .INI
file parameters. Apart from this data, SureTrak and P3 share data files.
Expedition 6.0 Files lists details of the Expedition database organized by
program module and data table.
4-4
Using the P3 Batch System

In this chapter:
Overview
General Rules for Batch
Processing
P3 Screen/Batch
Function Table
Sample Run Streams
Batch processing is a fast and powerful way to create and

update Primavera projects. By eliminating the interactive user
interface, Batch processing can complete many of your regular
updating processes in less time than when using the interactive
mode.
Using the P3 Batch System 4-5
Overview
The P3 Batch system makes it easy to develop complex project networks because it
enables you to input large quantities of data at one time. It also enables you to quickly
update resource and cost data. The batch file provides a record of all entries and changes
to the project database.
For a listing of record layouts for
creating, adding to, and updating
projects, see the Standard
Records chapter.
Use the Batch system as an alternative way to input data, or in conjunction with the interactive program. For example, first run the interactive program to set up the foundation for
a new project, and then use the Batch system to add detailed activity records to complete
the project network.
P3 uses the Btrieve record management system to handle project files. Primavera
Systems provides the necessary Btrieve record manager program (copied to your
programs directory when you install P3) that invokes and releases Btrieve as necessary.
You don't need the complete Btrieve system for normal operations; you will need it,
however, if you want to access project files outside the program interface. The complete
system includes the utility package program and a set of programming language interfaces and object modules. You can also use the query and report writing systems, Xtrieve
and XQL, to extract information from P3 project files. Btrieve, Xtrieve, and XQL are
available from Pervasive Software, Inc.
P3 checks new data thoroughly for accuracy before adding them to the database. Files
produced or modified externally using systems such as Btrieve and XQL may not be
supported and may cause errors while you are using either program.
Batch input files Instructions to the batch processor are provided as data records in a
plain text file. Each record or line in the data file contains a specific instruction to the batch
processor, and each instruction corresponds to a function or dialog box in the interactive
system.
Although you can create data files for the Batch system using spreadsheet or database
software, Primavera recommends using an ASCII- or ANSI-based text editor. You should
be familiar with the text-editing procedures for creating and saving text files before you
use them for batch processing.
Run streams, commands, and records One batch input file can instruct the batch
processor to perform one operation on one project or many operations on the same
project. It can also address more than one project. Each set of records that performs an
independent operation is called a run stream. For example, a batch input file can contain
one run stream to add a project and define calendars, another to define project dictionaries, and a third to add activities and relationships.
Record sequence The batch processor searches for three categories of records in a
batch input file:
Command records always precede definition data. These records, also known as
PROJ records, identify a project and instruct the processor to execute specific
commands. Every run stream begins with a PROJ record containing a command. The
last record in an input file must be a PROJ record with the END command.
Project-level data records provide detailed instructions about the project schedule,
calendar, nonworkperiods, activity codes and titles, resources and titles, resource
calendars, cost accounts and titles, and report titles. Project-level records follow
command records.
Activity-level data records define specific data about activities, such as durations,
precedence relationships, resource and cost data, and constraints. These records
always follow the EXECUTE command. The initial entry of activity data in a new
project begins with an INPUT record. Every subsequent update to activity information
begins with an UPDATE record. An activity-data run stream ends with a RETURN
record.
General Rules for Batch Processing

To use the Batch system successfully, follow these rules:
For instructions on creating a

batch input file, see Generating
an Input File in the Sample Run
Streams section, later in this
chapter.
Use up to eight characters for the batch input file name and up to three characters for
an optional filename extension.
Place data records in the correct sequence.
Type all commands in uppercase letters. Titles and descriptions can be uppercase,
lowercase, or mixed.
Do not type alphabetic data in numeric fields. Data must be justified to the left or right
within each field as specified.
Leave blanks in the first four spaces of a record if you want the Batch system to skip
the record. Use the remainder of the record to record comments in the file.
Verify your data before processing. The Batch system checks the data only for
correct format and sequence.
Correct a mistake by creating a reversing entry. It is usually better to use the interactive mode for small changes.
Avoid processing the same batch file twice by clearly naming your files.
Back up your project files as well as your batch files.
Processing the batch input file You must create a batch input file before you can use
the P3 batch data-entry system.
To set up the P3 Batch system program icon

1 From Program Manager, open the group window that you want to add the program
item to.
2 Choose File, New. Select Program Item, then click OK.
3 Type PRMBATCH.EXE in the Command line field, and the path to the file in the
Working directory field. For example,
Command line:
PRMBATCH.EXE
Working directory: C:\P3WIN\P3PROGS

4 Click OK.
To process a batch input file
1 Double-click the P3 Batch icon.
2 Choose the file extension that you want to use (.P3 or, for backward compatibility with
Finest Hour projects, .FH).
3 Select the input file in the File Name field, then click Run.
If necessary, use the Drives or Directories list boxes to display input files from other
locations. To change the projects directory, click the Dir (directories) button.
Output is directed to the file P3.OUT unless you specify another filename in the batch
run stream.
4 Click Exit.
You should set your USERLOC to a different directory than the projects directory. This
prevents your input files from being overwritten by another user who is processing a batch
file at the same time as you.
Experiment with the Batch system on a test project before using it on an active project.
Also, back up your projects before updating with the Batch system (choose Tools, Project
Utilities, Back Up).
The program processes the file in its entirety through the batch routines and then tests
the data. Diagnostic messages are directed to the P3.OUT file, a designated filename, or
the printer specified in the first PROJ record of the batch file. If P3 detects no errors, the
diagnostic report includes an audit trail of the selected batch commands. The following
figure shows part of a diagnostic report.
PROJ APX2 ADD
----------PROJECT-APX2 ADDED
DAILY PROJECT CALENDAR SPECIFIED
PROJ APX2 CALENDARD
MON
WHEN GENERATING CALENDAR, WEEKEND HOLIDAYS WILL BE MOVED TO NEAREST WEEKDAY

PCAL 25JUL96
19JUL96
13FEB98
----------CALENDAR SPECIFICATIONS INSERTED

MCAL 1
----------
MON
FRI
CALENDAR 1 DAILY MON TUE WED THU FRI

MHOL 1
21FEB97
MHOL 1
30MAY97
MHOL 1
5SEP96
MHOL *
1JAN
MHOL *
4JUL
MHOL *
25DEC
MHOL *
6SEP97
MHOL *
25NOV96
26NOV96
8 HOLIDAY(S) INSERTED
To increase the Batch system processing speed, you can suppress automatic data
validation by placing an X in column 8 of the INPUT/UPDATE record; however, keep in
mind that without validation you risk introducing invalid data. Suppress data validation
only after thoroughly checking your data.
P3 Screen/Batch Function Table

The following table lists common functions and their associated interactive dialog boxes
and batch commands. Refer to the next chapter for detailed information about individual
record layouts.
Batch Command/
Record Type
Function
Interactive Command
Add a new project group
File, New
CALENDAR, PCAL,
MCAL, MHOL, RCAL,
RHOL/ADD
Define project titles
File, New or File, Project Overview
DRT1-2/
TITLE DATA
Define an activity coding

structure
Data, Activity Codes: Activity codes option,

Activity ID option, and Aliases option
CDEF/
TITLE DATA
Define a WBS coding

structure
Data, WBS: Structure button
WBSD/
TITLE DATA
Define custom data items
Data, Custom Data Items: Activity or

Resource options
CUSD/
TITLE DATA
Define nonlinear distributions Data, Resource Curves
CURV/
TITLE DATA
Add a project to a project

group
File, New
COTL, BRT1, BRT2

BCAL/
TITLE DATA
Define a Cost account

structure
Data, Cost Accounts
ACAT/
TITLE DATA
Change an existing calendar Data, Calendars
CALENDAR, PCAL
MCAL, MHOL, RCAL,
RHOL
Function
Interactive Command
Batch Command/
Record Type
Copy an existing project
Tools, Project Utilities, Copy
COPY AND RENAME
Print a calendar list
Data, Calendars, Print button
CALENDAR LIST
Define a baseline plan
File, Project Overview, Targets
ESTABLISH
TARGET
Delete a project
Tools, Project Utilities, Delete
REMOVE
Reset period cost and

resource quantity
Data, Resources, Close Out button
PERIODCLOSEOUT
Add, delete, or change

activity data
Insert, Activity; Edit, Delete; Edit, Edit
ACTV or ACTVR/INPUT
or UPDATE
Assign custom data item

values to activities and
resources
Data, Custom Data Items
CDI/
INPUT or UPDATE
Define activity relationships
Successors and Predecessors Activity detail PREC or SUCC PRED/

forms
INPUT or UPDATE
Assign activity codes
Activity Codes detail form
CODE/
INPUT or UPDATE
Assign WBS codes
WBS detail form
WBSA/
INPUT or UPDATE
Add notes to activities
Log detail form
LIST/
INPUT or UPDATE
Assign resources
Resources detail form
RESR/
INPUT or UPDATE
Adjust target dates
Dates detail form
DATE/
INPUT or UPDATE
Set Autocost rules
Tools, Options, Autocost Rules
RULES
Begin run stream
N/A*
PROJ
Function
Interactive Command
Batch Command/
Record Type
End file
N/A*
END
Recalculate ETC
N/A*
ETC
Begin activity-specific data
N/A*
EXECUTE
End activity-specific data
N/A*
RETURN
Create records from existing N/A*

project
GENERATE
List interruptible activities
INTERRUPT
N/A*
* Not Applicable. These commands or records are specific to the Batch system and do not correspond
precisely to any interactive feature in P3.
Table conventions The record layout tables shown in this section use the following
abbreviations and conventions.
Contents
- A for alphabetic data only
- N for numeric data only
- A/N for alphanumeric data
Data justification
- In general, numbers are justified to the right, all other data are justified to the left:
L is for data justified to the left
R is for data justified to the right
C is for centered data
-- appears when no justification is required
Valid data
- For some records the Batch system recognizes the following numbering system
for dictionary codes:
C01-C20 for activity code classifications 1 through 20
A01-A04 for activity ID code classifications 1 through 4
- In other cases, the actual code (DEPT, RESP) is used. Check the record layout
tables to determine the correct format.
Dates
- Dates in batch run streams use DDMMMYY format. For hourly projects, specify
hours and minutes using HH:MM format.
- DD is 01-31 for day of month, MMM is JAN-DEC for month of year; and YY is 7099 for years in the 20th century (1970-1999) and 00-69 for years in the 21st
century (2000-2069).
- HH is 00-24 for hour, and MM is 00 for minutes in hourly projects. When using the
interactive program, the completion time that appears onscreen is 1 minute earlier
than specified. For example, 24:00 appears as 23:59.
- Rolling dates, such as DD+3W or SD-2M, are valid for date fields only if they are
valid for the corresponding field in P3.
Calendars
- Every project must have one calendar designated as calendar 1. The calendar ID
can be any number from 1 through 9 or any letter from A through Z, excluding I, O,
V, and W.
- Every resource has a calendar, which is built from one of the projects calendars.
Each resource calendar can have its own unique work schedule, holidays, exceptions, and so forth.
Sample Run Streams

This section provides sample run streams that demonstrate various batch commands and
show you how they can be applied. Use these examples as models for building your own
batch input files.
In a multiuser (network) environment, a valid user name is required on the PROJ line
(columns 51-58) in all run streams.
Generating an input file The following run stream generates the contents of a project
group into one large text file that can be divided into individual run streams.
PROJ APEX GENERATE
GENERATE ALL
APEX
PROJ APEX END
JOHN
INTO C:\P3WIN\PROJECTS\APEXPROJ.OUT
You can generate data from the sample project (APEX), or one of your own projects.
Refer to the descriptions for the GENERATE command and GENERATE record layout for
more information.
Adding a new project The following run stream adds a new project group and defines
its calendar 1:
PROJ
PROJ
PCAL
MCAL
MHOL
MHOL
MHOL
APEX ADD
APEX CALENDARD
27SEP96
19JUL96
1
MON
FRI
1
H
21FEB97
1
H
30MAY97
1
H
5SEP97
JOHN
MON
Y
13FEB98
Calendar 1 Daily MON TUE WED THU FRI
MHOL *
H
1JAN
MHOL *
H
4JUL
MHOL *
H
25DEC
MHOL *
H
6SEP96
MHOL *
H
25NOV96
RETURN
PROJ APEX END
26NOV96
Defining network relationships Use the INPUT record when you first add network data
to the project. Use the UPDATE record for subsequent runs. The following run stream
contains all the basic network definitions:
PROJ APEX EXECUTE
INPUT
YES YES
ACTVAAS100
O 10
ACTVAAS101
O 20
ACTVAAS102
O 10
ACTVAAS103
O 18
ACTVAAS104
O 13
ACTVAAS105
O 20
ACTVAAS106
O 18
ACTVAAS107
O 30
PREC AS100
AS101
PREC AS101
AS102
PREC AS101
AS204
PREC AS101
AS216
PREC AS102
AS310
PREC AS102
CS300
PREC AS103
AS105
JOHN
Define System Requirements
System Design
Approve System Design
Install Robot Base
Run Sealant, Air, and Water Piping
Install Temperature Control Equipment
Set & Connect Robots
Install System & Misc. Components
FS
FS
-10
-10*
*
1
1
1
1
1
1
1
1
PREC AS104
PREC AS105
PREC AS106
RETURN
PROJ APEX END
AS105
AS106
AS107
SS
5
*
*
First add all activities in ACTV records, then define relationships in PREC (precedence)
records. When you use an INPUT record, you must define the activities referenced by the
PREC records in the same run stream; when you use an UPDATE record, the activities
must already exist in the project or must have been specified in earlier ACTV records in
the same run stream.
The Batch system verifies each record as it is processed and flags any data errors. It also
identifies open ends (activities without predecessors or successors).
Building an Activity Codes Dictionary The following run stream defines the activity
coding structure for the project and then provides descriptions for the code values:
PROJ
CDEF
CDEF
CDEF
CDEF
CDEF
CDEF
COTL
COTL
COTL
COTL
APEX TITLE DATA

JOHN
CODE 1 3 DEPT Department
CODE 2 8 RESP Responsibility
CODE 3 13 PHAS Phase
CODE 4 18 STEP Step
CODE 5 23 ITEM Item
ACT
1 2 SUBP Project ID
C01
CON Construction Department
C01
ENG Engineering Department
C01
ISD Information Systems Department
C01
PCH Purchasing Department
4
1
3
2
COTL C02
COTL C02
COTL C02
COTL C02
COTL C02
COTL C02
COTL C02
COTL C02
COTL C03
COTL C03
COTL C03
COTL C03
COTL C03
COTL C03
RETURN
PROJ APEX END
ACME
EVANS
FOLEY
HARIS
MASON
MILLS
NOLAN
VENDR
CLOSE
DESGN
FINSH
FOUND
INSTL
PROCR
Acme Motors - Owner

6
Tim Evans - Program Manager
4
Meg Foley - Purchasing Manager
5
Linda Haris - Director of Software Engineering 3
Andy Mason - Director of Development
1
Tom Mills - Director of Hardware Engineering
2
Joe Nolan - Construction Manager
7
Vendor
8
Close-In Phase
9
Design and Engineering Phase
1
Finishes and Closeout Phase
10
Foundation Construction Phase
6
Installation Phase
5
Procurement Phase
2
Assigning code values to activities The following run stream assigns activity code
values to activities:
PROJ APEX EXECUTE
UPDATE
YES YES
CODE AS100
ENGMASONDESGN
CODE AS101
ENGMASONDESGN
CODE AS102
ENGMASONDESGN
CODE AS108
ISDMILLSSYS1
CODE AS109
ISDMILLSSYS1
CODE AS200
PCHFOLEYPROCR
CODE AS206
PCHVENDRPROCR
JOHN
ASDSG
ASDSG
ASDSG
HRDWR
HRDWR
TEMPC
TEMPC
CODE BA530
CODE CS311
CODE CS770
RETURN
PROJ APEX END
ENGACME PROCR
ISDMILLSINSTL
ISDEVANSINSTL
BRICK
CNVYS
CNVYS
Defining alias codes and assigning titles The following run stream defines an alias
code and assigns titles to the combined codes:
PROJ
ALIA
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
COTL
APEX TITLE DATA

JOHN
C03C02
DCAA PHAS + RESP
255
C03C02
CLOSENOLAN Close-In Phase-Nolan's Responsibility
255
C03C02
DESGNACME Design Phase-Acme Motor's Responsibility
255
C03C02
DESGNMASON Design Phase-Mason's Responsibility
255
C03C02
DESGNNOLAN Design Phase-Nolan's Responsibility
255
C03C02
FINSHNOLAN Finishes Phase-Nolan's Responsibility
255
C03C02
FOUNDNOLAN Foundation Phase-Nolan's Responsibility
255
C03C02
INSTLEVANS Installation Phase-Evans' Responsibility
255
C03C02
INSTLMILLS Installation Phase-Mills' Responsibility
255
C03C02
PROCRACME Procurement Phase-Acme Motor's Responsibility
255
C03C02
PROCRFOLEY Procurement Phase-Foley's Responsibility
255
C03C02
PROCRMASON Procurement Phase-Mason's Responsibility
255
C03C02
PROCRNOLAN Procurement Phase-Nolan's Responsibility
255
C03C02
PROCRVENDR Procurement Phase-Vendor's Responsibility
255
C03C02
ROUGHNOLAN Rough-In Phase-Nolan's Responsibility
255
C03C02
STRUCNOLAN Foundation Phase-Nolan's Responsibility
255
C03C02
SYS1 EVANS System Integration Phase 1-Evans' Responsibility255
C03C02
SYS1 HARIS System Integration Phase 1-Haris' Responsibility255
C03C02
SYS1 MILLS System Integration Phase 1-Mills' Responsibility255
RETURN
PROJ APEX END
Building a WBS Codes Dictionary The following run stream defines the WBS coding
structure for the project and then provides descriptions (titles) for the codes:
PROJ APEX TITLE
WBSD
1 2
WBSD
2 2
WBSD
3 1
WBSD
4 1
WBST
AM
WBST
AM01
WBST
AM011
WBST
AM012
WBST
AM012A
WBST
AM012B
WBST
AM012C
WBST
AM013
WBST
AM014
WBST
AM014A
WBST
AM02
WBST
AM021
WBST
AM022
WBST
AM022A
WBST
AM022B
WBST
AM023
WBST
AM023A
WBST
AM023B
DATA
.
.
.
.
JOHN
Acme Motors Expansion Project

Automated System
System Engineering
Hardware
Temperature Control Equipment
Robot Controller
System Controller
Software
Training
Manuals
Conveyor System
System Design and Engineering
Field Operations
Installation
Onsite Testing
Materials
Conveyors
Operation Manuals
WBST
AM03
WBST
AM031
WBST
AM032
WBST
AM033
WBST
AM034
WBST
AM034A
WBST
AM034B
WBST
AM034C
WBST
AM035
WBST
AM035A
WBST
AM035B
WBST
AM035C
WBST
AM036
WBST
AM036A
WBST
AM036B
WBST
AM036C
WBST
AM036D
RETURN
PROJ APEX END
Office Building Addition

Design and Engineering
Foundation
Structure
Mechanical/Electrical Systems
Elevator
HVAC
Plumbing and Electrical
Exterior Finishes
Brick
Roof
Doors and Windows
Interior Finishes
Plumbing and Lighting Fixtures
Floor and Carpeting
Carpentry
Paint
Assigning WBS codes to activities The following run stream assigns WBS codes to
activities:
PROJ APEX EXECUTE
UPDATE YES YES
WBSA AS100
AM011
WBSA AS101
AM011
WBSA AS103
AM012B
WBSA AS104
AM012B
JOHN
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
WBSA
AS105
AS106
AS107
AS108
AS109
AS110
AS111
AS112
AS113
AS114
AS115
AS116
AS117
AS118
AS150
AS201
AS202
AS204
AS205
AS206
AS213
AS214
AS215
AS216
AS218
AS240
AS250
AS260
AM012A
AM012B
AM012C
AM012C
AM012
AM012
AM012
AM012
AM013
AM012B
AM013
AM013
AM013
AM014A
AM013
AM012A
AM012A
AM011
AM011
AM012A
AM012C
AM012C
AM012C
AM011
AM012C
AM012
AM012C
AM012B
WBSA AS265
WBSA AS270
WBSA AS275
WBSA AS280
WBSA AS285
WBSA AS310
WBSA AS315
WBSA AS500
WBSA AS600
WBSA AS900
RETURN
PROJ APEX END
AM012
AM012B
AM012
AM013
AM013
AM012
AM012
AM013
AM013
AM01
Defining names for custom data items The following run stream shows how to build a
Custom Data Item Dictionary using CUSD records:
PROJ APEX TITLE DATA
CUSDA PLSTS07Planned Start
CUSDA PARTC20Part Number
CUSDR ORBCP09Orig Budget Cost
RETURN
PROJ APEX END
JOHN
PLFNF07Planned Finish
INSPC20Inspector
ORBQP09Orig Budget Qty
Assigning data to custom data items Use custom data item (CDI) records to assign
activity or resource information to custom data items. You can define up to eight activity
custom data items and eight resource custom data items per resource in a project. The
following run stream shows information relating to custom data items:
PROJ APEX EXECUTE

UPDATE YES YES
CDI AS100
CDI AS100
CDI AS100
ANALYST
CDI AS100
ATM ENG
CDI AS101
CDI AS101
CDI AS101
CDI AS101
ANALYST
CDI AS101
ATM ENG
CDI AS101
DES ENG
CDI AS102
CDI AS102
CDI AS102
ANALYST
RETURN
PROJ APEX END
JOHN
11101
11101
L
L
11101
11101
11101
L
L
L
11101
PLST
PLFN
ORBC
ORBC
PLST
PLFN
APPR
ORBC
ORBC
ORBC
PLST
PLFN
ORBC
19JUL97
30JUL97
1200.00
1760.00
2AUG97
27AUG97
360.00
4800.00
7040.00
4800.00
30AUG97
13SEP97
1200.00
Building a Resource/Cost Account Dictionary The following run stream contains cost
account categories and numbers, resource definitions, unit prices, and limits for resource
leveling:
RETL
11101
RETL
11211
RETL
11213
RETL
11221
RETL
11223
RETL
11231
JOHN
Automation System Design
Temperature Control Equipment-Design
Temperature Control Equipment-Install
Robot Controller-Design
Robot Controller-Install
System Controller-Design
RETL
RETL
RETL
RETL
RATE
RETL
RATE
RLIM
RETL
RATE
RLIM
RETL
RATE
RLIM
RETL
RATE
RLIM
RETL
RATE
RLIM
RETL
RATE
RETL
RATE
RLIM
RETL
RATE
RLIM
11233
11314
11415
ACCTS
ACCTS
ANALYST
ANALYST
ANALYST
ATM ENG
ATM ENG
ATM ENG
DES ENG
DES ENG
DES ENG
ELECTRCN
ELECTRCN
ELECTRCN
EQUIPMNT
EQUIPMNT
EQUIPMNT
FLD ENG*
FLD ENG*
FLD ENG1
FLD ENG1
FLD ENG1
FLD ENG2
FLD ENG2
FLD ENG2
Hrs
System Controller-Install
Software Processor
Automation System Training & Manuals
Accounts Manager
Hrs
Analyst-Systems Automation
16.00
30.00
4
22.00
8
30.00
16
32.00
40
2980.00
1
8 UNTIL
0
Hrs Automation Systems Engineer
0 UNTIL
16 UNTIL
Hrs Design Engineer
0 UNTIL
24 UNTIL
Hrs Electrician
0 UNTIL
48 UNTIL
Each Equipment-Crane
0 UNTIL
1 UNTIL
Hrs Field Eng-All
0 UNTIL
0 UNTIL
0 UNTIL
25.00
Hrs
25.00
8
20.00
8
Field Eng-Senior
10 UNTIL
Hrs Field Engineer
10 UNTIL
RETL FLD ENG3

RATE FLD ENG3
RLIM FLD ENG3
ACAT C CONTRCTR
ACAT E EQUIPMNT
ACAT L LABOR
ACAT M MATERIAL
RETURN
PROJ APEX END
Hrs
17.00
8
Field Eng-Assistant
8 UNTIL
0 UNTIL
Assigning resource quantities The T in column 33 of each RESR record indicates that
the amount applied to the activity is the total budget quantity of this resource. The TDQ in
columns 56-58 indicates that the amount in columns 59-66 is the actual quantity to date.
In columns 67-69, ETQ refers to the estimated quantity to complete. Compare these data
to the RESR records shown in Assigning Resource Costs. The following run stream
assigns resource quantities:
PROJ APEX EXECUTE
UPDATE YES YES
RESR AS100
ANALYST
RESR AS100
ATM ENG
RESR AS101
DES ENG
RESR AS101
ANALYST
RESR AS101
ATM ENG
RESR AS102
PRG MGR
RESR AS102
ANALYST
RESR AS103
FLD ENG1
RESR AS103
HWSPEC
RESR AS104
PLUMBER
JOHN
40.00T
80.00T
160.00T
160.00T
320.00T
20.00T
40.00T
144.00T
72.00T
104.00T
0
0
0
0
0
0
0
0
0
0
13
11101
11101
11101
11101
11101
11101
11101
11223
11223
11223
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
40.00ETQ
80.00ETQ
160.00ETQ
160.00ETQ
320.00ETQ
20.00ETQ
40.00ETQ
.00ETQ
.00ETQ
.00ETQ
.00
.00
.00
.00
.00
.00
.00
144.00
72.00
104.00
RESR AS105
RESR AS105
RESR AS105
RESR AS106
RESR AS106
RESR AS107
RESR AS107
RESR AS108
RESR AS108
RESR AS109
RETURN
PROJ APEX END
FLD ENG1
HWSPEC
ELECTRCN
FLD ENG2
HWSPEC
HWSPEC
FLD ENG3
HWSPEC
FLD ENG1
FLD ENG1
200.00T
80.00T
200.00T
144.00T
72.00T
240.00T
240.00T
32.00T
128.00T
192.00T
0
0
0
0
0
0
0
0
0
0
11213
11213
11213
11223
11223
11233
11233
11233
11233
11223
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
LTDQ
.00ETQ
.00ETQ
.00ETQ
.00ETQ
.00ETQ
.00ETQ
.00ETQ
.00ETQ
.00ETQ
.00ETQ
200.00
80.00
200.00
144.00
72.00
240.00
240.00
32.00
128.00
192.00
Assigning resource costs The C in column 33 of each RESR record indicates that the
amount applied to the activity is the budgeted cost of this resource. The TDC in columns
56-58 indicates that the amount in columns 59-66 is the actual cost to date. In columns
67-69, ETC refers to the estimated cost to complete. Compare these data to the RESR
records shown in Assigning Resource Quantities. The following run stream assigns
resource costs:
PROJ APEX EXECUTE
UPDATE YES YES
RESR AS100
ANALYST
RESR AS100
ATM ENG
RESR AS101
DES ENG
RESR AS101
ANALYST
RESR AS101
ATM ENG
RESR AS102
PRG MGR
RESR AS102
ANALYST
RESR AS103
FLD ENG1
JOHN
1200.00C
1760.00C
4800.00C
5160.00C
7040.00C
673.00C
1200.00C
3600.00C
11101
11101
11101
11101
11101
11101
11101
11223
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
1200.00ETC
.00
1760.00ETC
.00
4800.00ETC
.00
5160.00ETC
.00
7040.00ETC
.00
673.00ETC
.00
1200.00ETC
.00
.00ETC 3600.00
RESR AS103
RESR AS104
RESR AS105
RESR AS105
RESR AS105
RESR AS106
RESR AS106
RESR AS107
RESR AS107
RESR AS108
RESR AS108
RESR AS109
RETURN
PROJ APEX END
HWSPEC
PLUMBER
FLD ENG1
HWSPEC
ELECTRCN
FLD ENG2
HWSPEC
HWSPEC
FLD ENG3
HWSPEC
FLD ENG1
FLD ENG1
1224.00C
3432.00C
5000.00C
1360.00C
6400.00C
2880.00C
1224.00C
4080.00C
4080.00C
544.00C
3200.00C
4800.00C
11223
11223
11213
11213
11213
11223
11223
11233
11233
11233
11233
11223
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
LTDC
.00ETC
.00ETC
.00ETC
.00ETC
.00ETC
.00ETC
.00ETC
.00ETC
.00ETC
.00ETC
.00ETC
.00ETC
1224.00
3432.00
5000.00
1360.00
6400.00
2880.00
1224.00
4080.00
4080.00
544.00
3200.00
4800.00
Closing out a period The following run stream resets all actual costs and actual
quantities this period to zero:
PROJ APEX EXECUTE
UPDATE YES YES
PERIOD CLOSEOUT
RETURN
PROJ APEX END
JOHN
Tracking interruptible activities Use the INTERRUPT record to track interruptible

activities in your project. This report contains the following information: activity ID and
description, early start and finish dates, late start and finish dates, interruptible early start
and late finish dates, original and remaining durations, and interruptible early and late
durations.
Assigning dates You can quickly assign dates to activities with the Batch system, using
a run stream such as the following:
PROJ APEX EXECUTE
UPDATE YES YES
DATE AS100
27SEP96
DATE AS101
27SEP96
DATE AS102
27SEP96
DATE AS103
29SEP96
DATE AS104
29SEP96
DATE AS105
2NOV96
DATE AS106
2DEC96
DATE AS107
29DEC96
DATE AS108
10FEB97
DATE AS109
10FEB97
DATE AS110
10FEB97
DATE AS111
17MAR97
DATE AS112
17MAR97
DATE AS113
1APR97
DATE AS114
5APR97
RETURN
PROJ APEX END
JOHN
24SEP96
24SEP96
24SEP96
22OCT96
15OCT96
1DEC96
28DEC96
9FEB97
4MAR97
16MAR97
16MAR97
17MAR97
17MAR97
4APR97
5APR97
27SEP96
27SEP96
27SEP96
7OCT96
26OCT96
2NOV96
2DEC96
29DEC96
25FEB97
10FEB97
10FEB97
17MAR97
17MAR97
1APR97
5APR97
24SEP96
24SEP96
24SEP96
1NOV96
11NOV96
1DEC96
28DEC96
9FEB97
18MAR97
16MAR97
16MAR97
17MAR97
17MAR97
4APR97
5APR97
Setting Autocost rules The following run stream changes Autocost rules using Batch:
PROJ APEX RULES
PROJ APEX END
Y N SN YYY YY Y Y BCN
JOHN
To change rules interactively, choose Tools, Options, Autocost Rules.
PROJ APEX INTERRUPT
JOHN
Listing data The following run stream assigns log information to activities:
PROJ APEX EXECUTE
UPDATE YES YES
LIST AS100
LIST AS101
LIST AS101
LIST AS101
LIST AS102
LIST AS102
LIST AS116
LIST AS116
LIST AS116
LIST AS116
LIST AS150
LIST AS200
LIST AS200
LIST AS200
LIST AS200
LIST AS200
LIST AS204
LIST AS204
LIST AS204
LIST AS204
LIST AS204
RETURN
PROJ APEX END
JOHN
1
1
2
3
1
2
1
2
3
4
1
1
2
3
4
5
1
2
4
5
6
System design includes hardware and software

components and their integration. A materials
listing is also required.
Final approval of design is necessary before
proceeding.
Programming includes minor revisions to existing
software.
Phase II of System Integration begins.

Refer to Design specification #01270.
Engineer required to submit technical spec

drawings for temperature control equipment.
Additional resource needed to complete this
activity on-schedule. Approved change of
time and a half increase over original budget.
4-31
Standard Records
In this chapter:
ACAT
ACCESS
ACTV
ACTVR
ADD
ALIA
BCAL
BRT1
BRT2
CALENDAR
CALENDAR LIST
CDEF
CDI
CHDR
CODE
COPY AND RENAME
COTL
CURV
CUSD
DATE
DRT1
DRT2
END
ESTABLISH TARGET
ETC
EXECUTE
GENERATE (command)
GENERATE (record)
INPUT
INTERRUPT
LIST
LIST STATISTICS
MCAL - hourly
MCAL - daily
MCAL - weekly and monthly
MHOL
PCAL
PERIOD CLOSEOUT
PREC
PRED
PROJ
RATE
RCAL
RHOL
REMOVE
RESR
RETL
RETURN
RLIM
RULES
SNUM
SUCC
TITLE DATA
TITLE LIST
UPDATE
WBSA
WBSD
WBST
BATCH ERROR
MESSAGES
You can use standard

records to perform many of
the functions available in
the interactive program's
dialog boxes from adding a
new project to building
project dictionaries. This
chapter lists the standard
records in alphabetical
order.
Standard Records 4-32
ACAT
Resource leveling and resource/cost control use resource and/or cost codes. The
Resource Dictionary contains the following information:
Descriptive titles of cost accounts and resources
Units of measure for each resource
Cost account categories such as labor, material, and equipment
Resource availability limits for use during resource leveling. The limits can vary
through six periods over time.
Resource cost rates. P3 uses unit prices per resource quantity to calculate costs to
complete; these rates can vary through six periods over time.
Use the ACAT record to specify cost account categories. Specify up to 26 cost account
categories (A-Z) per project. Define up to six categories per ACAT record; add as many
ACAT records as necessary.
Field Record
Name:
Category 1
Category 2
Category 3
Category 4
Category 5
Category 6
Type
Del.
Code
Title
Code
Title
Code
Title
Code
Title
Code
Title
Code
Title
Columns:
1-4
8-15
17
19-26
28
30-37
39
41-48
50
52-59
61
63-70
Example:
ACAT
LABOR
MATERIAL
EQUIPMNT
Field Name
Columns
Contents
Justification
Valid Data
Record Type
1-4
--
ACAT
Delete
--
Normally blank D to delete all category titles
Field Name
Columns
Contents
Justification
Valid Data
Category
Code
6
17
28
39
50
61
--
Any value. For example, M for material, L for

labor, or E for equipment
Title
8-15
19-26
30-37
41-48
52-59
63-70
A/N
Any description
ACCESS
The ACCESS record generates a list of all users in a project and their level of access
rights.
Field
Record Type
Name:
ProjectName
CommandData
Suppress User List
Return Code
19
20
AccessLevel Username
OutputDevice
Columns:
1-4
6-9
11-16
Example:
PROJ
APEX
ACCESS
Field Name
Columns
Contents
Justification
Valid Data
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Any four-character project name, or ????

to list all users in all projects
Command
Data
11-16
ACCESS
Suppress User 19
List
N - Suppress list of users
Return Code
20
R - Display return code for user list
Access Level
21
R - Read Only or Restricted

W - Read Write
X - Exclusive Read Write
Blank - Check for existence of user in
USERFIL.P3
Username
51-58
A/N
Valid username (of user processing the

Batch run)
A/N
Any filename with or without extension;

use PRINTN to send output to default
printer, or leave blank to save output in
P3.OUT
Output Device 75-139
21
51-58
75-139
JOHN
PRINTN
In a multiuser (network) environment, a valid username is required in columns 51-58

of the first PROJ record in the run stream.
The following is a list of possible return codes from using the ACCESS record followed by
a sample Visual Basic code fragment for capturing return codes.
900 - User does not exist
901 - USERFIL.P3 does not exist
902 - Other users in project
903 - Could not find DIR record
904 - Could not open DIR file
905 - Single user system trying to access a multiuser project.
906 - Rights file does not exist.
907 - Project does not have an owner assigned.
908 - No rights exist for user for the project
909 - User can not be downgraded from RW to RO.
910 - Insufficient access rights
911 - Project exclusively locked by another user.
1000+ - Number of users in the current project.
Sample Visual Basic Code Fragment for Capturing Return Codes
'// The following requires MSGBLAST.VBX. This is available free from Microsoft.
'// Setup Message Blaster

MsgBlaster1.hWndTarget = Me.hWnd
MsgBlaster1.MsgList(0) = WM_USER + 300
'// Batch File Name

BatchFile = C:\P3WIN\BATCH.INP
'// Location of the project
ProjectDirectory = C:\P3WIN\PROJECTS
'// Project Extension
ProjectExtension = P3
BatchTask% = Shell(PRMBATCH.EXE REPORTS & BatchFile & & Str(Me.hWnd) & &
Str(WM_USER + 300) & ProjectDirectory & /EXTENSION= & ProjectExtension, 7)
Do
DoEvents
Loop Until GetModuleUsage(BatchTask%) = 0
Sub MsgBlaster1_Message (msgval As Integer, wParam As Integer, lParam As Long, ReTurnVal As
Long)
If msgval = (WM_USER + 300) Then
MsgBox Batch return code & Str(wParam)
End If
End Sub
ACTV
The ACTV record lets you add, delete, or change activities in a project. Specify information for each activity, such as duration, percent complete, description, user-imposed
schedule constraints, activity type, leveling type, and so on.
Alphanumeric activity IDs containing fewer than 10 characters can be positioned
anywhere in the Activity ID field, but this position must be consistent throughout the
project records.
Field Record
Name:
Type
Input
Type
Activity ID
Dur. Type
Activity
Duration
Percent
Complete
21-23
Columns:
1-4
6-15
16
17-20
Example:
ACTV
AS280
ActivityTitle
Date
Type
Imposed
Date/Time
Cal. ID
Frac. %
Complete
Longest
Path Flag
Activity
Type
Levelng
Type
24-71
72-73
74-85
86
87-91
92
93
94
TEST SOFTWARE
Field Name Columns
Contents Justification Valid Data
Record
Type
--
ACTV
Input Type 5
--
A to add, D to delete, C to change activity

data.
If blank, A is assumed following INPUT,
C is assumed following UPDATE
Activity ID
6-15
A/N
--
Any value up to 10 alphanumeric characters
Duration
Type
16
--
O for original duration,

C or R for current (remaining) duration
Duration
17-20
0-9999 work units: days, weeks, or months
Percent
Complete
21-23
0-100
A/N
Any value
1-4
Activity Title 24-71
Field Name Columns
Date Type
72-73
AS - actual start
AF - actual finish
ES - start no earlier than
EF - finish no earlier than
FF - finish flag
FM - finish milestone
LS - start no later than
LF - finish no later than
MS - mandatory start
MF - mandatory finish
ON - start on
SF - start flag
SM - start milestone
XF - expected finish
ZTF - zero total float
ZFF - zero free float or blank
Imposed
Date
74-80
A/N
Imposed date in DDMMMYY format or

DELETE to remove imposed date
Time
81-85
A/N
Time in HH:MM format
Calendar ID 86
A/N
--
Calendar ID: 1-9 or A-Z (excluding I, O, V,

and W)
Fractional
Percent
Complete
87-91
0.0 - 100.0
Longest
Path Flag
92
--
Blank for noncritical; C for critical; D for delete
Comments
Field Name Columns
Activity
Type
93
--
0 - Task
1 - Independent
2 - Meeting
3 - Start Milestone
4 - Finish Milestone
5 - Hammock
6 - WBS
7 - Topic
8 - Start Flag
9 - Finish Flag
Leveling
Type
94
--
0 - Normal
1 - Immediate Priority
2 - Split
3 - Stretch
4 - Crunch
5 - Stretch & Crunch
ACTV records follow an INPUT or UPDATE record.

To indicate both actual start and finish dates, use an ACTV record for each.
To indicate both start and finish constraints, use an ACTV record for each.
Activity ID fields defined in the CDEF record refer to the 10-character activity ID string
in columns 6-15.
Data entered in column 92 are overwritten when you schedule or level the project.
This record contains two percentage fields: columns 21-23 and 87-91. To record a
percentage with decimal places, use the Fractional Percent Complete field; if you
record percentages in both fields, P3 uses the latter by default.
The Task activity type is compatible with the Normal, Immediate Priority, and Split
leveling types. The Independent activity type is compatible with all leveling types. All
other activity types ignore the Leveling Type field.
ACTVR
The ACTVR record renumbers activities. The existing ID is deleted; the new ID is added;
and the predecessors/successors are adjusted accordingly.
Field Record
Name:
Type
Comments
Input
Type
Current ID
New ID
Columns:
1-4
6-15
19-28
Example:
ACTV
A1
D11
Field Name Columns
Contents
Justification
Valid Data
Record
Type
--
ACTV
Input Type 5
--
R to renumber
Current ID
6-15
A/N
--
Current activity ID
New ID
19-28
A/N
--
New activity ID
1-4
ACTVR records follow an INPUT or UPDATE record.

If you attempt to assign a new activity ID that already exists, P3 ignores the ID and
prints an error message.
ADD
The ADD command is used with the CALENDAR command and the PCAL and MCAL
records to create a new project.
Field Record
Name:
Type
Comments
Project
Decimal
Command Username
Name
Display
Columns:
1-4
6-9
11-13
51-58
64
Example:
PROJ
APEX
ADD
JOHN
Field Name Columns Contents
Justification Valid Data
Record Type 1-4
--
PROJ
Project
Name
6-9
A/N
--
Four-character name of new project; no blank

characters permitted
Command
11-13
--
ADD
Username
51-58
A/N
Valid username
Decimal
Display
64
A/N
--
0 to display resource and cost data with zero

decimal places; 2 or any character to display data
with two decimal places
In a multiuser (network) environment, a valid username is required in columns 51-58

of the first PROJ record in the run stream.
If you attempt to add a project group with a name that already exists in your PROJ
directory, P3 rejects the name and prints an error message.
The ADD command must be followed by the CALENDAR command and PCAL and
MCAL records that define the following calendar data:
Project group start date
Project group completion date
Start and end workperiods

Duration specified in hours, days, weeks, or months
Calendar start date
Nonworkperiods and exceptions
Project group data date
Error conditions
Project name already exists
Error in PROJ record
ALIA
Once you define activity code and activity ID fields, use the ALIA record to define aliases
for these fields. Combinations of up to five code fields can also be titled, or up to four if the
combination includes activity ID codes.
Field Record
Name:
Code Field Identifier
Alias
Alias
Type
Type
Name
Title
Columns:
1-4
6-8
9-11
12-14
15-17
18-20
22-25
27-74
Example:
ALIA
C1
C2
DCAA
PHASE AND
RESP
Field Name
Comments
Input
Columns Contents Justification
Valid Data
Record Type 1-4
--
ALIA
Input Type
--
Normally blank; D to delete all alias values for this

project
Code Field
Identifiers
6-8
9-11
12-14
15-17
18-20
A/N
--
Code field identifier; for activity ID fields use A01A04; for activity code fields use C01-C20
Alias Name
22-25
A/N
--
Alias code name
Alias Title
27-74
A/N
--
Description (title) of the alias
ALIA records normally follow CDEF records.
You cannot combine activity ID fields and activity code fields (for example, A01C01).
BCAL
Each project within a project group has its own data date. The BCAL record, which
appears in the Title Data section of the Batch file, stores this date. The BCAL record
follows the projects COTL record, which identifies the project within the group.
Field
Name:
Record
Type
Project Data
Date
Imposed Finish
Date
Columns:
1-4
6-17
36-47
Example:
BCAL
15OCT96
Field Name
Columns
Contents
Justification
Valid Data
Record Type
1-4
--
BCAL
Project Data Date 6-18
A/N
--
DDMMMYY HH:MM
Imposed Finish
Date
A/N
--
DDMMMYY HH:MM
34-46
* MM is 01-12 for month of year and YY is 70-99 for years in the 20th century (1970-1999)
and 00-69 for years in the 21st century (2000-2069).
BRT1
The BRT1 record records title information for a project within a project group. The record
appears in the Title Data section of the Batch file, following the projects COTL record.
Field
Name:
Record
Type
Company
Name
Project
Title
Columns:
1-4
6-41
45-80
Example:
BRT1
Field Name
Columns
Contents
Justification
Valid Data
Record Type
1-4
A/N
--
BRT1
Company
Name
6-41
A/N
--
Any value
Project Title
45-80
A/N
--
Any value
BRT2
The BRT2 record carries report title information for a project within a project group. The
record appears in the Title Data section of the Batch file, following the projects COTL
record.
Field
Name:
Record
Type
Report Center
Heading
Project Number/
Version
Columns:
1-4
14-61
62-77
Example:
BRT2
Field Name
Columns
Contents
Justification
Valid Data
Record Type
1-4
A/N
--
BRT2
Report Center Heading
14-61
A/N
--
Any value
Project Number/Version
62-77
A/N
--
Any value
CALENDAR
Use the CALENDAR command to define project calendar data such as the project
planning unit and holidays.
Field
Name:
Record
Type
Project
Name
Command
Planning
Unit
Shifts Per
Day
Start Time 1st

Shift
Shift
Duration
21
23-27
29-33
Columns:
1-4
6-9
11-18
19
Example:
PROJ
APEX
CALENDAR
Week
Starts On
Holiday
35-37
39
51-58
MON
JOHN
Username
Field Name
Columns
Contents Justification
Valid Data
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Four-character name of existing project
Command
11-18
--
CALENDAR
Planning Unit
19
--
H - hour; D - day; W - week; M - month
Shifts Per Day
21
--
1-6
Start Time First

Shift
23-27
A/N
--
Start time of first shift in HH:MM format
Shift Duration
29-33
A/N
--
Standard duration of each shift in HH:MM

format; the product of shifts per day and shift
duration cannot exceed 24 hours
Week Starts On
35-37
--
Day of week: MON, TUE, WED, THU, FRI,

SAT, SUN; default is MON
Holiday
39
--
Y or blank to move holiday to nearest

workday;
N to leave holiday date unchanged
Username
51-58
A/N
Valid username
Comments
Error conditions
The CALENDAR command is followed by PCAL, MCAL, and MHOL records that
define the following calendar data:
Project group start date
Project group completion date
Start and end workperiods
Calendar start date
Nonworkperiods and exceptions
Project group data date
You can establish the planning unit (column 19) only once for each project group.
Once you define the planning unit, you can change it only by copying and renaming
the project group. (In P3, choose Tools, Project Utilities, Copy).
The Week Starts On field (columns 35-37) determines the start of the workweek in
weekly projects. For projects with a planning unit of hour or day, this value is used for
reporting. The start day of the workweek has no effect on a monthly project.
Use the Holiday field (column 39) to specify whether to move a holiday or a specially
designated nonworkday that falls on a regularly scheduled nonworkday (weekend) to
the nearest workday. This field pertains only to daily projects.
Nonexistent project name
Invalid start day of the week
Holiday date format error
CALENDAR LIST
Once you define a calendar for a project, use the CALENDAR LIST command in a PROJ
record to print the project calendar(s). The report indicates which timeperiods are
workperiods and which timeperiods are nonworkperiods.
Field
Record Type
Name:
Project Name
Command
Username
Start Date
End Date
Columns:
1-4
6-9
11-23
51-58
66-69
70-73
Example:
PROJ
APEX
CALENDAR LIST
JOHN
1196
897
Field Name Columns Contents Justification Valid Data

Record
Type
1-4
--
PROJ
Project
Name
6-9
A/N
--
Command
11-23
--
CALENDAR LIST prints project calendars
Username
51-58
A/N
Valid username
Start Date
66-69
Start month and year of calendar to be printed
End Date
70-73
Last month and year of calendar to be printed.* If end

date is left blank, entire calendar is printed.
* MM is 01-12 for month of year and YY is 70-99 for years in the 20th century (1970-1999)
and 00-69 for years in the 21st century (2000-2999).
Comments
A PROJ record with the END command must follow the CALENDAR LIST command.
You must establish at least one calendar using the MCAL record before you can use
the CALENDAR LIST command.
Always specify the last month and/or year of the calendar to be printed.
CDEF
An activity coding structure can use up to 10 characters of the activity ID string for activity
ID fields and up to 64 characters of the activity code string for activity code fields.
Individual activity ID or code fields are identified within the activity ID and activity code
string. Titles can be assigned to codes and combinations of codes.
Use the code field definition (CDEF) record to establish the type of code field (activity
code or activity ID), the location of the field in the activity ID or code string, and the name
and description of the field. Each CDEF record defines a single code field.
Field
Name:
Record Type
Del.
Field Type
Field No.
End Position
Name
Description
Columns:
1-4
6-9
11-12
14-15
17-20
22-69
Example:
CDEF
CODE
DEPT
DEPARTMENT

Record
Type
1-4
--
CDEF
Delete
--
Normally blank; D to delete this definition*
Field Type 6-9
CODE or ACT
Field
Number
11-12
Order number of code or activity of fields defined:

1-4 for ACT fields,
1-20 for CODE fields
End
Position
14-15
End position of field in ACTV record (columns 6-15)

or CODE record (columns 17-80):
1-10 for ACT records,
1-64 for CODE records
Name
17-20
A/N
Any value
Description 22-69
A/N
Any value
* Specify CODE in columns 6-9 to delete a previously defined activity code field; specify
ACT to delete a previously defined activity ID field.
Comments
Code field definitions appear in the Activity Codes Dictionary in P3.
You must define codes before you can organize, select, or summarize the project.
Define up to 20 activity code fields and up to four activity ID fields.
Activity ID fields refer to the 10-character activity ID string in columns 6-15 of the
ACTV record.
The CDEF record is normally followed by COTL records to define code values and
titles.
CDI
The CDI record assigns data to user-defined data items, activities, or resources. The
Name and Data fields (columns 37-40 and 44-63) must be predefined through the CUSD
record.
Field
Name:
Record Type
Activity ID
Resource
Cost Account
Res. Des.
Name
Input Type
Data
Columns:
1-3
5-14
15-22
23-34
35
37-40
42
44-63
Example:
CDI
MP1
PLST
15JAN9713:

Record
Type
1-3
--
CDI
Activity ID
5-14
A/N
--
Up to 10-character value per ACTV record
Resource
15-22
A/N
Blank if entering data for activity; if resource, specify

the resource name
Cost
Account
23-34
A/N
Blank if entering data for an activity custom data

item; if a resource custom data item, specify the cost
account number (optional)
Resource 35
Designator
A/N
--
Blank or resource designator
Name
A/N
Name of custom data item
Input Type 42
--
D to delete; blank to add
Data
A/N
For Date items specify start date (S) or finish date (F)
in DDMMMYY HH:MM format; for Character items
(C) specify up to 20 characters; for Numeric items (N)
specify 1-10 digits; for Precision numeric items (P)
specify 4-11 digits
37-40
44-63
Comments
Activities referenced by the activity ID must exist, or ACTV records must precede the
CDI record.
The resource name, cost account number, and resource designator must be defined
before you can process CDI records.
CHDR
Use the CHDR record to change the PROJ path without terminating a run stream. This
enables you to work with projects located in several locations in the same run stream.
Field
Name:
Record Type
Columns:
1-4
6-70
CHDR
C:\P3\PROJECTS
Field Name
Columns
Contents
Justification
Valid Data
Record Type
1-4
--
CHDR
A/N
--
Drive and directory where project is

located
Change Path To 6-70
Example
Change Path To
The following run stream adds custom data item codes to projects APEX and CNCT,
located in different directories.
CHDR C:\P3WIN\NEWPROJ
RETURN
PROJ CNCT TITLE DATA
RETURN
PROJ CNCT END
JOHN
INSPC20Inspector
JOHN
INSPC20Inspector
CODE
Use the CODE record to assign activity codes to an activity.
Field
Name:
Record Type
Input Type
Columns:
1-4
Example:
CODE
Activity ID
Code Values
6-15
17-80
A1
ENGMASON1

Record
Type
Comments
CODE
Input Type 5
--
Normally blank; D to delete all code assignments for

this activity
Activity ID
6-15
A/N
--
Code
Values
17-80
A/N
1-4
Code data must correspond with code field

definition (see CDEF record)
Type asterisks (*) rather than blanks in place of any code values that you do not want
to change. For example, to change the code string INSPECMACH to INSPECBOIL,
type ******BOIL in the Code Values field.
Blanks in the 64-character string overwrite existing data.
Only one CODE record is permitted per activity.

The activity referenced by the activity ID must exist, or ACTV records must precede
the CODE record.
Activity IDs with fewer than 10 characters can be positioned anywhere in the Activity
ID field, but this position must be consistent throughout the project for all ACTV,
PREC, SUCC, PRED, CODE, RESR, LIST, and DATE records.
Modify codes by reprocessing the record.
COPY AND RENAME

Use the COPY AND RENAME command to make a copy of an existing project. You can
then perform what-if analyses on the duplicate project to examine alternative resource
and scheduling scenarios.
Field
Record Type Project Name
Name:
Error conditions
Command
New Name
User-name
Columns:
1-4
6-9
11-25
27-30
51-58
Example:
PROJ
APEX
COPY AND RENAME
AUTO
JOHN
Field Name
Valid Data
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Command
11-25
--
COPY AND RENAME
New Name
27-30
--
Four-character name for new project
Username
51-58
A/N
Valid username
Unable to allocate space for project, or not enough memory to copy files
Nonexistent project to be copied
COTL
Code titles print automatically on schedule reports when combined with the Skip Page,
Skip Lines, and Summarize On Codes report options.
Once you define activity code and activity ID fields, use the COTL record to specify code
titles for these fields. Combinations of up to five code fields can also be titled. You can
also use the COTL record to add a project to a project group, or to delete a project from a
group.
Field Record
Name:
Specified Code Fields
Type
Del.
1st
2nd
3rd
4th
5th
Code Value
Code Title
Order
Columns:
1-4
6-8
9-11
12-14
15-17
18-20
22-31
33-80
81-83
Example:
COTL
Code Value
ENG
ENGINEERING DEPARTMENT
Field Name
C1
Valid Data
Record Type 1-4
--
COTL
Delete
--
Normally blank; D to delete all code titles
Specified
Code Fields
6-8
9-11
12-14
15-17
18-20
A/N
--
Code field identifier; for activity ID fields use A01A04; for activity code fields use C01-C20. To add
a project to a project group, specify SUB in
columns 6-8; to delete an existing project, specify
SD in columns 6-8. Add or delete the projects
SUBP code field value using the A01 field.
Code Value
22-31
A/N
Actual code value(s). If adding a project, specify

its four-character project name in columns 22-25
and its two-character Project ID in columns 27-28.
Code Title
33-80
A/N
Title of code value; DELETE removes the existing

specified code value and code title
Order
81-83
If blank, sorted alphabetically; if 1-255, specified

number is primary sort
Comments
When right-justifying the code value in columns 22-31, trailing spaces are significant.
For example, in the case of a 3-character code value in a 5-character code field, type
the three characters in columns 27-29.
COTL records normally follow the CDEF record.
The following example illustrates an activity ID code field title:

Record Type
COTL
Code Field
A1
Code Value
C
Code Title
CONVEYOR SYSTEM
If an activitys ID contains a C in Activity ID field 1 (the first defined character in the activity
ID string), the activity is part of the Conveyor System.
The following example shows a single activity code title record:
Record Type
COTL
Code Field
C1
Code Value
PCH
Code Title
PURCHASING DEPARTMENT
If an activity carries PCH in Activity Code field 01, the activity is part of the purchasing
department.
The following example defines a code combination:
Record Type
Code Field Combination
Combination Code Value
COTL
C1C2
1ACME
Code Title
RESPONSIBILITY OF ACME
MOTORS
In this example, Activity Code field 1 (C01) represents the phase of the project. A 1 in
this field denotes the Design and Procurement phase. ACME in Activity Code field 2
(C02, Responsibility) means that ACME motors is responsible for that activity. The combination of the two codes, C01C02, is assigned the title Responsibility of ACME Motors.
You cannot combine Activity ID fields and Activity Code fields (for example, A01C01).
CURV
P3 distributes resource usage and costs evenly across an activity unless you specify
nonlinear distribution using curves. Use the CURV record to assign a cumulative resource
percent complete at each 10% increment of resource duration. Since each number is
cumulative, each value must be equal to or greater than the value from the previous
period, and the last value must be 100.
Field Record
Input
Res.
Type
Type
Des.
Columns:
1-4
Example:
CURV
Name:
Percent of Duration
Description
0%
10%
20%
8-27
29-31
33-35
37-39
BACKLOADED
Percent of Duration
30%
40%
50%
60%
70%
80%
90%
100%
41-43
11
45-47
18
49-51
27
53-55
38
57-59
51
61-63
65
65-67
82
69-71
100
Field Name
Columns Contents Justification Valid Data
Record Type 1-4
--
CURV
Input Type
--
Normally blank; D to delete assignment specified

by resource designator
Resource
Designator
A/N
--
0-9 or A-F
Description
8-27
A/N
Any value
Field Name
Percent of
Duration
29-31
33-35
37-39
41-43
45-47
49-51
53-55
57-59
61-63
65-67
69-71
L or R
0 - 100, whole numbers only
CUSD
Use the CUSD (custom data definition) record to define additional fields by activity or
resource assignment.
Field Record
Name:
Input
Type
Input
7
Columns:
1-4
Example:
CUSD
Field Name
Field 1
Type
Name
Type
Length
8-11
12
PLST
Columns Contents
Field 2
Description
Input
Name
Type
Length
Description
13-14
15-30
32
33-36
37
38-39
40-55
13
PLANNED START
PLFN
13
PLANNED FINISH
Record Type 1-4
--
CUSD
Input Type
--
A for activity; R for resource; D to delete all CUSD

records
Fields 1 and 2 7
- Input
- Name
A/N
Specify the name of the custom data item
- CUSD Type 12
37
--
Classify CUSD type:

S for start date; F for finish date; N for number; P
for precision numeric; C for character
- Length
1-20 for character; 1-10 for number; 1-11 for

precision numeric; 7 or 13 for dates
A/N
Any value
8-11
33-36
13-14
38-39
- Description 15-30
40-55
Blank to add data field

D to delete field
Comments
The CUSD record must follow an EXECUTE command.

The maximum number of fields is two per CUSD record. The total maximum number
of fields per run stream is eight for both activity custom data items and resource
custom data items.
If you place a D in column 5, all custom data items are deleted. You cannot differentiate between activity and resource custom data items.
DATE
The DATE record temporarily overwrites the calculated dates for an activity. Use this
record with caution.
Field Record
Name:
Type
Early Start
Activity ID
Date
Time
25-29
Columns:
1-4
6-15
17-23
Example:
DATE
A13
3NOV97
Early Finish
Date
Time
32-38
40-44
4DEC97
Late Start
Date
Time
47-53
55-59
7NOV97
Late Finish
Suspend
Resume
Date
Time
Date
Time
Date
Time
62-68
70-74
77-83
85-89
92-98
100-104
6DEC97
Field Name
Columns
Record Type
1-4
--
DATE
Activity ID
6-15
A/N
--
Use up to 10 alphanumeric characters
Early Start Date
17-23
A/N
Imposed early start date in DDMMMYY format
- Time
25-29
A/N
Time of day in HH:MM format
Early Finish - 32-38

Date
A/N
Imposed early finish date in DDMMMYY format
- Time
40-44
A/N
Late Start Date
47-53
A/N
Imposed late start in DDMMMYY format
- Time
55-59
A/N
Late Finish Date
62-68
A/N
Imposed late finish date in DDMMMYY format
- Time
70-74
A/N
Suspend Date
77-83
A/N
Imposed suspend date in DDMMMYY format; D

to delete this date
- Time
85-89
A/N
Comments
Field Name
Columns
Resume Date
92-98
A/N
Imposed resume date in DDMMMYY format; D to

delete this date
- Time
100-104
A/N
No other calculated data, such as float or driving relationships, recognize these

imposed dates.
When you schedule or level a project, P3 overwrites both the early start and finish
dates and the late start and finish dates.
When they are generated using the DATE record, start flags and start milestones
show finish dates in addition to their start dates; finish flags and finish milestones
show start dates in addition to their finish dates.
If you specify a resume date, a suspend date is required. The resume date must be
later than the suspend date.
DRT1
Use the DRT1 record to specify the company name and project title in your project.
Field
Record Type Company Name
Name:
Project Title
Columns:
1-4
6-41
45-80
Example:
DRT1
ACME MOTORS
PLANT EXPANSION AND MODERNIZATION
Field Name
Columns
Contents
Record Type
1-4
--
DRT1
Company Name
6-41
A/N
Any value
Project Title
45-80
A/N
Any value
DRT2
Use the DRT2 record to change the report center heading for reports and graphics.
Field
Record Type
Name:
Report Title
Project Version
Columns:
1-4
14-61
62-77
Example:
DRT2
PROJECT SCHEDULE
P3WIN Version 2.0
Field Name
Record Type
1-4
--
DRT2
Report Title
14-61
A/N
Any value
Project Version
62-77
A/N
Any value
END
The END command terminates the Batch file. Only one END command can appear in
each file. The Batch system ignores any data following this command.
Field
Record Type
Name:
Project Name
Command
Columns:
1-4
6-9
11-13
Example:
PROJ
APEX
END
Field Name
Columns Contents
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Four-character project name
Command
11-13
--
END
ESTABLISH TARGET
The ESTABLISH TARGET command creates a new target schedule. Create up to two
targets containing schedule, resource, and cost data.
Field
Record Type
Name:
Comments
Project Name
Command
Target Name
Username
Columns:
1-4
6-9
11-37
39-42
51-58
Example:
PROJ
APEX
ESTABLISH TARGET SCHEDULE-1
PLAN
JOHN
Field Name
Valid Data
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Command
11-37
A/N
--
ESTABLISH TARGET SCHEDULE-n where n

specifies Target 1 or Target 2
Target Project
Name
39-42
A/N
--
Four-character name of target project
Username
51-58
A/N
Valid username
The ESTABLISH TARGET command must be followed by an END command.
Specify either Target 1 or 2 in column 37.
ETC
The ETC command recalculates the estimated quantity at completion (EAC) and the
estimated quantity to complete (ETC) based on progress. Progress is determined by the
resource percent complete (RPC) or activity percent complete (PCT), and the actual to
date quantity (TDQ). If the resource percent complete is blank, P3 uses the activity
percent complete. The Batch processor uses the following formulas to calculate estimate
to complete (ETC):
EAC = (TDQ RPC) x 100
or
EAC = (TDQ PCT) x 100, if the RPC is blank
ETC = EAC TDQ
Before using this command, set both parts of Autocost Rule 5 to N so that P3 does not
calculate actual cost and quantity to date. For activities with progress, specify actual cost
and quantity to date, as well as resource percent complete.
Field
Name:
Record Type
Project Name Command
Produce Audit Report
Username
Columns:
1-4
6-9
11-37
20-22
51-58
Example:
PROJ
APEX
ETC
REP
JOHN
Field Name
Valid Data
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Produce Audit
Report
20-22
--
REP
Username
51-58
A/N
Valid username
Audit Filename
75-139
Audit report filename
Comments
The ETC command recalculates ETC for all activities in the network.
EXECUTE
The EXECUTE command instructs the P3 Batch system to process specific activity data.
Field
Name:
Comments
Record Type
Project Name
Command
Username
Columns:
1-4
6-9
11-17
51-58
Example:
PROJ
APEX
EXECUTE
JOHN
Field Name
Columns
Valid Data
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Command
11-17
--
EXECUTE
Username
51-58
A/N
Valid username
The EXECUTE command must be followed by an INPUT, UPDATE, or REPORT

record. The last record of the EXECUTE run stream must be RETURN.
GENERATE (command)
Use the GENERATE command to create ANSI text Batch records for all existing
calendar, title, resource, activity, and code records in your project. You can also use it to
create templates for frequently used projects. GENERATE lets you write specified Batch
records to a new input data file. You can then use a text editor to revise the data and
create a new project or update an existing project.
Field
Name:
Comments
Record Type
Project Name
Command
Username
Columns:
1-4
6-9
11-18
51-58
Example:
PROJ
APEX
GENERATE
JOHN
Field Name
Columns
Contents
Justification
Valid Data
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Command
11-18
--
GENERATE
Username
51-58
A/N
Valid username
The GENERATE command must be followed by one or more GENERATE records to

specify output and options.
GENERATE (record)
Use the GENERATE record to specify different types of output and file options. These
selections are listed under the Output and Options headings that follow this record layout
description.
Field
Name:
Columns:
Record
Options
Type
Output
Name
From Sort
Into Filename
1-8
10-14
16-19
21-29
31-94
ALL
CAR5
FROM SORT
INTO C:\P3WIN\P3OUT\SAMPLE.TXT
Example: GENERATE
Field Name Columns Contents
Output
Justification
Valid Data
Record
Type
1-8
--
GENERATE
Output
10-14
Type of record to output into the generated file
Options Name
16-19
A/N
--
Four-character name of new project to be created with

run stream produced by GENERATE ALL
- From Sort 21-29
FROM SORT Select from current filter file
- Into
31-34
INTO
- Filename 36-94
Path and filename for the generated file
In order to use the FROM SORT option, be sure that the following section and entry
appear in the P3.INI file:
[Options]
CreateSrtWithFlt=1
The output contains records of the type specified. Note that these records are
generated in the order in which you specify them. This order is important if you plan to
use the generated records as input to another Batch run, as P3 will not process
certain records if they are out of sequence. The following record types are listed in the
correct order:
CDEF generates CDEF records of activity ID and activity code field definitions.
COTL generates COTL records of activity ID and activity code field titles.
DRT generates DRT1 and DRT2 records of project title information.
RETL generates RETL records of resources and cost accounts and titles.
ACAT generates ACAT records for all cost account category titles.
RLIM generates RLIM records for resource limits and through dates.
RATE generates RATE records for resource prices per unit and through dates.
CUSD generates CUSD records with data definitions for activities and resources.
CDI generates CDI records with data assignments to activities or resources.
CURV generates CURV records for nonlinear distribution of resources.
ALI generates ALIAS records of alias code field definitions.
ACTV generates ACTV records of activity data including activity ID, original duration,
percent complete, and activity title. If A, C, or D follows ACTV, the letter is added to the
output record. Use this feature to add, change, or delete activities.
ACTVR generates ACTVR records of activity IDs.

CODES generates CODE records for all activity code assignments to activities.
PREC generates PREC records for all precedence relationships among the various activities in terms of successor activities for each activity (same as SUCC).
SUCC generates SUCC records for all precedence relationships among the various activities in terms of successor activities for each activity (same as PREC).
PRED generates PRED records for all precedence relationships among the various activities in terms of predecessor activities for each activity.
CONST generates ACTV records for all activities with user-imposed schedule
constraints.
DATE generates DATE records including early start/finish, late start/finish, and suspend/
resume dates and times for all activities.
RESR generates RESR records for all activities with resources, resource quantities, and
cost accounts.
COST generates RESR records for all activities with resources, cost accounts, and cost
amounts.
LOGnn generates LIST records for all activities with data in the log file. The nn represents the line number (1-99) in the log. If nn is omitted, P3 generates all log lines.
PROG generates ACTV progress records including activity number, remaining duration,
percent complete, and actual start and finish dates for activities with progress.
WBSD generates WBS Dictionary information for a project.

WBS generates WBS assignments for all activities.
ADD generates calendar information, Autocost rules, and title data for a project. You can
use this output file to add other projects through the P3 Batch system.
ALL generates Batch records for the output types described (except ACTVR), in the
appropriate order for input to the P3 Batch system. This record also generates the
required PROJ, INPUT, and RETURN records; the END record at the end of the
generated file; and blank lines between groups of records for readability. The project
name appears in these records as four question marks (????) unless you specify a new
project name. Use columns 16-19 to specify a project name in the generated input file.
To generate Primavera Version 4.1 (for DOS) project data output, type a 4 in
column 13, immediately after the ALL specification.
CUSD generates CUSD records with data definitions for activities and resources.
CDI generates CDI records with data assignments to activities or resources.
CURV generates CURV records for nonlinear distribution of resources.
Options
New project name (columns 16-19)
Specify a new project name for the generated data file created with the GENERATE ALL
record. Do not specify a new project name for any other GENERATE record.
FROM SORT (columns 21-29)
FROM SORT generates Batch records of the types specified, from the most recent filter
file. If you omit FROM SORT, P3 uses all activities to generate Batch records.
INTO [filename] (columns 31-94)
INTO [filename] names the data file that contains the processed records. If omitted, the
data file is named GEN.OUT, and is stored in the USERLOC directory. If you generate
more than one record type into the same output file, all output is concatenated; no data is
lost. Alternatively, you may use the INTO option to send data for multiple records to
different files.
Comments
The GENERATE record must be preceded by the PROJ record with the GENERATE
command. Refer to the sample run stream for Generating an Input File at the
beginning of this chapter for more details.
The END command must be the last record in this Batch file.
INPUT
Use the INPUT or UPDATE record to add or change activity data. The first run after
adding a new project must use the INPUT record. All subsequent runs require the
UPDATE record. If you specify INPUT for a project that already contains activity information and you execute the Batch job, the Batch program prompts you to either overwrite
the existing data with the new data or terminate the Batch run.
Field
Name:
Record Type
Validate
Full List
Open End List
Columns:
1-6
9-11
13-15
Example:
UPDATE
NO
NO
Field Name
Columns Contents
Justification
Valid Data
Record Type
1-6
INPUT or UPDATE
Validate
Blank or X
Full List
9-11
YES to print complete list of all activity records

in run stream; NO to print only a diagnostic list
of project-level data and open-end list, if
specified
YES to print list of activities with no successors

or predecessors; NO to print only a diagnostic
list of project-level data and full list, if specified
Open End List 13-15
Comments
Normally blank; X suppresses normal data

validation
An INPUT or UPDATE record must follow a PROJ record with the EXECUTE
command.
An INPUT or UPDATE run stream must end with a RETURN record.
Use the INPUT record only once to initiate a project; thereafter, use UPDATE.
Activity ID Field
An INPUT or UPDATE record must precede any ACTV, PREC, SUCC, PRED,
CODE, RESR, PERIOD CLOSEOUT, LIST, or DATE record.
When using INPUT, the activities referenced by PREC, SUCC, and PRED records
need not be defined with ACTV records first. These activities must, however, be
defined somewhere within the same run stream.
When using UPDATE, activities must already exist before they are referenced by
PREC, SUCC, and PRED records. These activities can be defined in a previous run
stream, earlier in the same run stream, or by using the activity detail forms.
If you suppress validation, the program will not check for the existence of referenced
activities, resources, or cost accounts. Relationships to nonexistent activities will not
be prevented.
The Activity ID field appears in the ACTV, ACTVR, PREC, SUCC, PRED, CODE, RESR,
LIST, and DATE records. The position of data in this field is user-defined; however, it
must be consistent with the P3 interactive system and among all Batch records. The interactive system automatically right justifies activity IDs that contain all numeric characters.
If the activity ID includes one or more letters, blank spaces, or special characters, P3
positions the data as they are entered. Activity IDs can use all 10 available characters.
How you choose to place data in the Activity ID field also affects the definition of code
fields within the activity ID; the CDEF record references column positions within the
available 10 characters relative to the first (left-most) column.
INTERRUPT
The INTERRUPT command has no effect on the project files. It prepares a report of interruptible activitiesthose activities affected if scheduled using the interruptible scheduling
option. The report shows the activity ID and description; original, remaining, and interruptible durations; and the interruptible start, early start, and early finish dates. The interruptible duration represents the time in workperiods from the interruptible start to the
constrained finish date.
Field
Name:
Record Type
Project Name
Command
Username
Columns:
1-4
6-9
11-19
51-58
Example:
PROJ
APEX
INTERRUPT
JOHN
Field Name
Columns
Valid Data
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Command
11-19
--
INTERRUPT
Username
51-58
A/N
Valid username
LIST
The LIST record contains additional descriptive information about an activity. The P3
interface refers to these items as log records.
Field
Record Type Input Type Activity ID
Name:
Comments
Columns:
1-4
Example:
LIST
6-15
Mask
Rec. No.
Del.
Description
Del. All
20
21-22
23
24-71
72
B3
BE SURE TO COMPLETE PUNCH LIST
Field Name
Record Type
1-4
--
LIST
Input Type
--
Normally blank; D to delete all LIST records for

the activity
Activity ID
6-15
A/ N
--
Use a 10 character value for each ACTV record
Mask
20
--
Normally blank; M to mask record in printing
Record Number 21-22
1-99
Delete
23
--
Normally blank; D to delete LIST record
Description
24-71
A/N
Any value
Delete All
72
--
Normally blank;
D to delete all LIST records in the project
Use a maximum of 99 LIST records per activity.

the LIST record.
Activity IDs can be justified to the right or left, but they must be consistent throughout
the project for all records.
To delete all LIST records for the entire project, specify only LIST in columns 1-4 and
D in column 72.
LIST STATISTICS
The LIST STATISTICS command instructs the P3 Batch system to print statistics for the
project.
Field
Record Type
Name:
Project
Name
Command
Username
Columns:
1-4
6-9
11-25
51-58
Example:
PROJ
APEX
LIST STATISTICS
JOHN
Field Name
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Command
11-25
--
LIST STATISTICS
Username
51-58
A/N
Valid username
Output
Error Conditions
This command produces a list that includes the project name, network type, data
date, project start date, project completion date, code field definitions, activity field
definitions, calendar information (including all holidays), and default report titles.
Error in PROJ record or nonexistent project name.
MCAL - Hourly
Use the MCAL record to specify the characteristics of calendar definitions. Calendar data
must be defined before you can use any activity-level commands. The first three fields are
the same for each planning unit; the remainder of the MCAL record depends on the
planning unit selected. Each calendar must have a separate MCAL record.
Field
Record
Cal.
Name:
Monday
Tuesday
Wednesday
Thursday
Type
ID
Del.
Start
End
Start
End
Start
End
Start
End
Columns:
1-4
15-19
21-25
27-31
33-37
39-43
45-49
51-55
57-61
Example:
MCAL
6:
24:
6:
24:
6:
24:
6:
24:
Friday
Saturday
Sunday
Start
End
Start
End
Start
End
Calendar Title
63-67
6:
69-73
24:
75-79
6:
81-85
24:
87-91
6:
93-97
24:
99-114
TWO SHIFTS
Field Name Columns
Valid Data
Record Type 1-4
--
MCAL
Calendar ID 6
A/N
--
Calendar ID - 1-9 or A-Z (excluding I, O, V, and W)
Delete
--
D to delete calendar
Monday to
Sunday Start Time
15-19
27-31
39-43
51-55
63-67
75-79
87-91
A/N
Start time in HH:MM format; specify 00:00 or blank

spaces for days when work does not occur
Field Name Columns
Valid Data
- End Time
21-25
33-37
45-49
57-61
69-73
81-85
93-97
A/N
End time in HH:MM format; specify 00:00 or blank

spaces for days when work does not occur
Calendar
Title
99-114
A/N
Any value
MCAL - Daily
planning unit selected. Each calendar must have a separate MCAL record
Field
Name:
Record Type
Cal. ID
Del.
Start Day
End Day
Calendar Title
Columns:
1-4
15-17
21-23
45-60
Example:
MCAL
MON
FRI
FIVE-DAY WEEK
Field Name
Columns Contents
Record Type 1-4
--
MCAL
Calendar ID
A/N
--
Calendar ID: 1-9 or A-Z (excluding I, O, V, and W)
Delete
--
Start Day of
Workweek
15-17
--
Day of week: MON, TUE, WED, THU, FRI, SAT,

SUN
End Day of
Workweek
21-23
--
Day of week: MON, TUE, WED, THU, FRI, SAT,

SUN
A/N
Any value
Calendar Title 45-60
Comments
The start and end days of the workweek determine when activities are scheduled.
The Start Day field is not the same as the days of the week specified in columns 3537 of the CALENDAR command, which is used for reporting purposes when the
planning unit is any value other than week.
MCAL - Weekly and Monthly

planning unit selected. Each calendar must have a separate MCAL record
Field
Name:
Comments
Record Type
Cal. ID
Del.
Calendar Title
Columns:
1-4
45-60
Example:
MCAL
MONTHLY
Field Name
Valid Data
Record Type
1-4
--
MCAL
Calendar ID
A/N
--
Calendar ID - 1-9 or A-Z (excluding I, O, V,

and W)
Delete
--
Calendar Title
45-60
A/N
--
Any value
An MCAL record must follow the PCAL record when adding a project or changing a
calendar.
MHOL
The MHOL record specifies the start and finish dates or times for calendar nonworkperiods and exceptions.
Field
Record
Calendar
Holiday
Non
Type
Delete
ID
Delete
or Ex.
Columns:
1-4
Example:
MHOL
Name:
Field Name
Start
End
Date
Time
10
14-20
22-26
23NOV97
Date
Time
30-36
38-42
24NOV97
Valid Data
Record Type 1-4
--
MHOL
Delete
--
Normally blank; D to delete all exceptions and

nonworkperiods in the project
Calendar ID
A/N
--
Calendar ID. Use 1-9 or A-Z (excluding I, O, V, and

W). Specify an asterisk (*) to apply a nonworkperiod or exception to all calendars
Holiday
--
Normally blank
Delete
D to delete a single nonworkperiod or exception as

defined by remainder of record
Nonworkperiod or
Exception
10
--
W to specify an exception (workperiod during what

would otherwise be nonworktime); H to specify a
nonworkperiod (holiday)
Start - Date
14-20
A/N
Start date for nonworkperiod/exception in

DDMMMYY format
- Time
22-26
A/N
End - Date
30-36
A/N
End date for nonworkperiod/exception in

DDMMMYY format
- Time
38-42
A/N
Comments
End date and time are not required if the start date and time make up the entire
nonworkperiod or exception.
Specify start and end times without their accompanying dates for nonworkperiods or
exceptions that occur daily on hourly or shift calendars.
Leave the year blank to specify an annual nonworkperiod or exception.
Use two MHOL records to specify annual nonworkperiods or exceptions that span the
end of one year and the start of the next (for example, from 25DEC to 05JAN). The
first record defines the holiday or the exception to the end of the first year; the second
defines the period from the beginning of the following year.
PCAL
The PCAL record establishes project group schedule information. Use PCAL with the
ADD and CALENDAR commands when defining new projects and with the CALENDAR
command when changing existing calendars.
Field Record
Name:
Data Date
Project Start Date
Project Compl. Date
Compl.Date Calendar Start Calendar Start Start Date
Type
Date
Time
Date
Time
Date
Time
Del.
Date
Time
Del.
Columns:
1-4
6-12
14-18
20-26
28-32
34-40
42-46
48
50-56
58-62
64
Example:
PCAL
24JUL96
3AUG97
Latest Calculated Early Finish

Date
Time
66-72
74-78
Field Name
Record Type
1-4
--
PCAL
Data
- Date
6-12
A/N
Data date for schedule calculation in

DDMMMYY format
- Time
14-18
A/N
Data date time of day in HH:MM format
Project Start
- Date
20-26
A/N
Project start date in DDMMMYY format
- Time
28-32
A/N
Project start time in HH:MM format
Project Completion
- Date
34-40
A/N
Project completion date in DDMMMYY

format
- Time
42-46
A/N
Project completion time in HH:MM format
Completion Date
Delete
48
--
If D, delete project completion date;

otherwise leave blank
Comments
Field Name
Calendar Start
- Date
50-56
A/N
If blank, uses calendar start date
- Time
58-62
A/N
Calendar start time in HH:MM format
Start Date Delete
64
--
D to delete calendar start date
Latest Calculated
Early Finish - Date
66-72
A/N
Latest calculated early finish date in

DDMMMYY format
- Time
74-78
A/N
Latest calculated early finish time in HH:MM

format
The PCAL record must follow the CALENDAR command; MCAL records must follow
the PCAL record when you add a project or change a calendar.
You must specify the record type and project start date when using the PCAL record
with the ADD command.
You can change the project start date or completion date in the PCAL record using
the PROJ CALENDAR command.
PERIOD CLOSEOUT
The PERIOD CLOSEOUT record resets the current period costs and resource quantities
to zero.
Field
Name:
Comments
Record Type
Columns:
1-15
Example:
PERIOD CLOSEOUT
The PERIOD CLOSEOUT record must be preceded by the UPDATE record.
PREC
PREC records (identical to SUCC records) describe precedence relationships in terms of
successor activities. Use either record to add a new successor relationship or to delete an
existing one.
Field Record
Name:
Input
Activity
Successor 1
Type
Type
ID
Activity ID
Rel. Type
Lag
Columns:
1-4
6-15
17-26
28-29
34-37
Example:
PREC
A1
A11
Successor 2
Driving Flag Activity ID Rel. Type
38
39-48
A12
50-51
Lag
Driving Flag
56-59
60
*
Successor 3
Activity ID
Rel Type
Lag
Driving Flag
61-70
A13
72-73
78-81
82
*
Field Name
Record Type
1-4
--
PREC or SUCC
Input Type
--
Normally blank;
D to delete all successors for this activity
Activity ID
6-15
A/N
10-character activity ID
Successors 1,
2, and 3
- Activity ID
17-26
39-48
61-70
A/N
--
- Relationship
Type
28-29
50-51
72-73
SS for start to start

FF for finish to finish
FS or blank for finish to start
SF for start to finish
D to delete relationship between two activities
- Lag
34-37
56-59
78-81
For hourly, shift, daily, weekly, or monthly

calendars -999 to 9999; lag expressed in
planning units
Comments
Field Name
- Driving Flag
38
60
82
--
* to specify driving relationship;

to remove driving flag
You must use PREC, SUCC, or PRED records to define activity relationships.
When using INPUT, the activities referenced by PREC and SUCC records need not
be defined with ACTV records first. These activities must, however, be defined
somewhere in the same run stream.
PREC and SUCC records. These activities can be defined in a previous run stream,
earlier in the same run stream, or by using the interactive program.
PREC or SUCC records do not change data for existing relationships. To change
data such as relationship types or lag, delete the existing relationship and then
redefine it with a new PREC or SUCC record.
PREC or SUCC records normally follow ACTV records.
Data entered in columns 38, 60, and 82 are overwritten when you calculate a
schedule or level the project.
PRED
The PRED record describes precedence relationships in terms of predecessor activities.
Use this record to add a new predecessor relationship or to delete an existing one.
Field
Record
Input
Type
Type
Columns:
1-4
Example:
PRED
Name:
Predecessor 1
ActivityID
Activity ID
Rel. Type
Lag
Driving Flag
6-15
17-26
28-29
34-37
38
A1
C3
SS
Predecessor 2
Predecessor 3
Activity ID
Rel. Type
Lag
Driving Flag
Activity ID
Rel. Type
Lag
Driving Flag
39-48
50-51
56-59
60
61-70
72-73
78-81
82

Record Type 1-4
--
PRED
Input Type
--
Normally blank;
D to delete all predecessors for this activity
Activity ID
6-15
A/N
Prede17-26
cessors 1, 2, 39-48
and 3
61-70
- Activity ID
A/N
--
28-29
Relationship 50-51
Type
72-73
SS for start to start; FF for finish to finish; FS or

blank for finish to start;
SF for start to finish; D to delete relationship
between two activities
- Lag
For hourly, shift, daily, weekly, or monthly calendars

-999 to 9999; lag expressed in planning units
34-37
56-59
78-81

- Driving
Flag
Comments
38
60
82
--

When using INPUT, the activities referenced by PRED records need not be defined
with ACTV records first. These activities must, however, be defined somewhere
within the same run stream.
PRED records. These activities can be defined in a previous run stream, earlier in the
same run stream, or by using the interactive program.
A PRED record does not change the data for existing relationships. To change data
such as relationship types or lag, delete the existing relationship and then redefine it
with a new PRED record.
PRED records normally follow ACTV records.
PROJ
P3 uses the PROJ record to identify the project being created or updated and to execute
commands. A PROJ record must appear at the beginning of a run stream, and the final
record in a Batch input file must be a PROJ record with the END command. PROJ
records within the run stream execute additional commands.
Field
Record Type
Name:
Project Name
Command Data
Autocost Option
User- name
Output Device
Columns:
1-4
6-9
11-48
49
51-58
75-139
Example:
PROJ
APEX
EXECUTE
C/R
JOHN
PRINTN
Field Name
Columns Contents
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Four-character project name
ACCESS
ADD
CALENDAR
CALENDAR LIST
COPY AND RENAME
END
ESTABLISH TARGET
ETC
EXECUTE
GENERATE
INTERRUPT
LIST STATISTICS
REMOVE
RULES
SCHEDULE
TITLE DATA
TITLE LIST
Command Data 11-48
Field Name
Comments
Columns Contents
Autocost Option 49
Username
51-58
A/N
Valid username
Output Device
75-139
A/N
Any filename with or without extension; use

PRINTN to send output to printer port LPT1;
leave blank to save output in P3.OUT
Used only with the RULES command to

specify when the application of Autocost rules
occurs: when moving between cells, or
between resources. Valid entries are C or R.
P3 uses only the filename specified in columns 75-139 of the first PROJ record to
store output. If the designated filename does not include a drive/path/extension, P3
writes it to your USERLOC directory. P3 ignores all filenames that appear later in the
Batch input file.
RATE
Resource cost rates are unit prices per quantity of resource used to calculate budget,
actual to date, and estimate to complete costs. These rates can vary over time.
Resource limits are used only during resource leveling. Specify normal and maximum
limits of resource availability. The limits can vary over time.
The RATE record defines the price per unit for resources.
Field
Name:
Record
Input
Price Per UnitInterval 1
Type
Type
Resource
Del.
Amount
Date
Time
Amount
Date
Time
Amount
Date
Time
Columns:
1-4
6-13
14
15-22
23-29
30-34
35-42
43-49
50-54
55-62
63-69
70-74
Example:
RATE
8.
31DEC96
88.
31DEC97
FLD ENG

Amount
Date
Time
75-82
83-89
90-94
Field Name
Valid Data
Record Type
1-4
--
RATE
Input Type
--
Normally blank; D to delete rates for all

resources
Resource
6-13
Eight-character resource code
Delete
14
--
Normally blank; D to delete rates for only

this resource (all intervals)
Intervals 1-4
- Price Per Unit
15-22
35-42
55-62
75-82
Type the amount with decimal point
Comments
Field Name
Valid Data
- Date
23-29
43-49
63-69
83-89
A/N
Through date of price interval in DDMMMYY

format
- Time
30-34
50-54
70-74
90-94
A/N
Specify up to six price intervals by adding a second RATE record in which intervals 5
and 6 replace intervals 1 and 2, respectively.
Define resources using the RETL record before you assign rates.
RATE records are optional. If you include them, P3 uses them for automatic costing
when generating reports.
Omit the (through) date for an interval if the price holds constant through the end of
the project.
RCAL
Each resource has its own calendar, which is initially a copy of one of the projects base
calendars. Specify each resources calendar, its base calendar, and the resources work
schedule using RCAL records.
Field Record
Name: Type
Input
Type
Resource
Base
Calendar
Use Base
Calendars
Workweek
Sun.
Mon.
Tues.
Wed.
Thurs.
Fri.
Sat.
8-15
17-18
20
22-45
47-70
72-95
97-120
122-145
147-170
172-195
Columns:
1-4
Example:
RCAL
Field Name
Record Type
1-4
--
RCAL
Input Type
--
Resource
8-15
A/N
Defined resource name
Base Calendar
17-18
ID number of a valid base calendar from 1-31
Base Calendars 20
Workweek
Y/N
Sunday
22-45
A/N
Indicate work (1) or nonwork (.) for each of the

24 hours of the day
Monday
47-70
A/N

24 hours of the day
Tuesday
72-95
A/N

24 hours of the day
Field Name
Wednesday
97-120
A/N

24 hours of the day
Thursday
122-145
A/N

24 hours of the day
Friday
147-170
A/N

24 hours of the day
Saturday
172-195
A/N

24 hours of the day
RHOL
Each resource calendar can have its own holidays to differentiate the resource calendar
from its base calendar template. Define resource holidays using the RHOL record.
Field
Name:
Record Type
Input Type
Resource
Date of Holiday
Hourly Work Indicator
8-15
17-23
25-48
Columns:
1-4
Example:
RHOL
Field Name
Columns
Record Type
1-4
--
RHOL
Input Type
--
Resource
8-15
A/N
Valid resource name
Date of Holiday 17-23
A/N
DDMMMYY
Hourly Work
Indicators
A/N
25-48

24 hours of the day
REMOVE
The REMOVE command deletes a project from the P3 projects directory (PROJ).
Field
Name:
Record Type
Project Name
Command
Username
Columns:
1-4
6-9
11-16
51-58
Example:
PROJ
APEX
REMOVE
JOHN
Field Name
Record Type
1-4
--
PROJ
Project Name 6-9
A/N
--
Command
11-16
--
REMOVE
Username
51-58
A/N
Valid username
Output
Error Conditions
Attempting to remove a project that is not on file
Insufficient rights to delete project
This command deletes project files. If you use this record to delete a project group,
P3 also deletes all projects within it.
RESR
The RESR record assigns resources and resource quantities. This record also allows you
to combine cost accounts, categories, and costs with resources.
Field
Name:
Record Type
Input Type
Columns:
1-4
Example:
RESR
Activity ID
Del.
6-15
16
A1
Cost
Actual Amount
Resource Original Amount
RTC
Lag
Dur.
Pct. Compl.
34-36
37-40
41-43
17-24
25-32
33
DES ENG
Forecast Amount
Res.
Frac.
Res. Driv.
Acct.
Acct. Cat.
TP/TD
Amt.
QCTC
Amt.
Des.
Pct.Compl.
Dur. Flg
44-54
311
55
L
56-58
TDQ
59-66
6
67-69
ETQ
70-77
80
81-85
15.4
86
Field Name
Valid Data
Record Type 1-4
--
RESR
Input Type
--
Normally blank;
D to delete all resource/cost data for this activity
Activity ID
6-15
A/N
--
Use a 10-character value for each ACTV record
Delete
16
--
Normally blank; D to delete resource and cost

amounts for this resource and cost account, and to
delete resource and cost account
Resource
17-24
A/N
Any valid resource as defined in Resource

Dictionary (see RETL record)
Original
Amount
25-32
Original estimate or budget amount in monetary or

resource units. Valid numbers are up to
2,147,483,647 (if displaying zero decimals) or
21,474,836.47 (if displaying two decimals.) Do not
include commas when typing data.
Field Name
Valid Data
RTC
33
R - original amount is units per timeperiod

T - original amount is budgeted quantity
C - original amount is budgeted cost
Resource
Lag
34-36
Resource
Duration
37-40
Normally blank to set resource duration equal to

activity duration; value of 1-9999 represents
number of workperiods resource is used after time
lag
Resource
Percent
Complete
41-43
0-100
Cost
Account
Number
44-54
A/N
L or R
Optional data; assign up to 11 alphanumeric

characters to identify resource/cost account
Cost
Account
Category
55
Optional data; use one character to specify cost

category. Category must be defined in ACAT
record or interactive system first
Actual
56-58
Amount --TP
or TD -Quantity or
Cost
TDC for actual to date cost;

TDQ for actual to date quantity;
TPC for this-period cost;
TPQ for this-period quantity *
-- Amount
Actual this period quantity/cost amount in

monetary or resource units. Valid numbers are up
to 2,147,483,647 (if displaying zero decimals) or
21,474,836.47 (if displaying two decimals.) Do not
59-66
--
Normally blank to spread resources evenly over

activity duration; value of 1-999 delays start of
resource use by this number of workperiods after
activity start, then spreads use evenly over
resource duration
Field Name
Valid Data
Forecast
Amount -QCTC
67-69
ETC = estimated cost to complete

ETQ = estimated quantity to complete
FRC = estimated (forecast) cost at completion
FRQ = estimated (forecast) quantity at completion
-- Amount
70-77
Estimated (forecast) amount in monetary or

resource units. Valid numbers are up to
2,147,483,647 (if displaying zero decimals) or
21,474,836.47 (if displaying two decimals). Do not
Resource
Designator
80
A/N
--
Any value; combine with resource name or

nonlinear curve lines to identify resources
assigned to this activity
Fractional
Percent
Complete
81-85
0.0 - 100.0
--
* to designate as driving;
Blank for not driving;
D to delete
Resource86
Driven
Duration Flag
* TPC (this-period cost) and TPQ (this-period resource quantity) appear in the Cost and
Resources forms as actual cost this period and actual quantity this period. If you specify
TPC or TPQ, P3 accumulates TPC to calculate the actual cost to date and TPQ to
calculate actual quantity to date (according to Autocost rule 6 - Link Actual to Date and
Actual this Period).
Comments
Resource and cost accounts must exist before RESR records can be processed.
the RESR record.
Alphanumeric activity IDs of less than 10 characters can be positioned anywhere in

the Activity ID field, but this position must be consistent throughout the project for all
records.
If you initially combine a resource and account number in a single RESR record,
specify both fields again when updating resource and cost information. If you specify
only the resource or cost account number when updating, the P3 Batch system
assigns the data to the activity as a new resource or cost account.
If estimate/forecast to complete is omitted, P3 calculates it automatically during
scheduling if you have chosen to perform Autocost computations during each
schedule calculation.
Actual to date amounts, if omitted, are calculated automatically at time of resource/
cost reporting or scheduling.
Daily rates of resources/costs are calculated automatically.
The C in column 33 of each RESR record indicates that the amount applied to the
activity is the budgeted cost of this resource. The TDC in columns 56-58 specifies
that the amount in columns 59-66 is the actual cost to date. In columns 67-69, ETC
refers to the estimated cost to complete. Compare these data to the RESR records
shown in Assigning Resource Quantities.
This record contains two percentage fields: columns 41-43 and 81-85. To record a
percentage with decimal places, use the Fractional Percent Complete field; if you
record percentages in both fields, P3 uses the latter by default.
RETL
Use the RETL record to define resources in the Resource Dictionary and to define cost
accounts in the Cost Accounts Dictionary.
Field
Name:
Record Type
Input Type
Resource
Cost Account
Delete
Unit of Measure
Columns:
1-4
6-13
15-26
27
28-31
Example:
RETL
FLD ENG
MD
Resource or Cost
Account Title
33-72
FIELD SERVICE
ENGINEER
Driven Dur. Flag

73
*
Field Name
Valid Data
Record Type
1-4
--
RETL
Input Type
--
Normally blank; D to delete Resource and Cost

Accounts Dictionaries
Resource
6-13
A/N
Any value
Cost Account 15-26
A/N
L or R
Any value
Delete
27
--
Normally blank; D to delete resource or cost

account number and title
Unit of
Measure
28-31
Any value
Resource or 33-72
Cost Account
Title
Any value
Resource73
Driven
Duration Flag
--
* to designate driving;
Blank for not driving;
D to delete
Comments
You must process RETL records before assigning resources and/or cost accounts to
individual activities.
Assign titles to resources or cost accounts.
You can justify account numbers of fewer than 11 characters to the left or the right.
However, you should justify numbers consistently in the Account Number field for all
RETL and RESR Batch records.
RETURN
The RETURN command must terminate Batch sequences that begin with the EXECUTE
command or the TITLE DATA command. Multiple RETURN records can appear in one
run stream.
Field
Name:
Record Type
Columns:
1-6
Example:
RETURN
RLIM
Use the RLIM record to specify resource limits for leveling.
Field Record
Name:
Input
Type
Type
Columns:
1-4
Example:
RLIM
Resource LimitsInterval 1
Resource
Del.
Normal
Max.
6-13
14
18-22
4
FLD ENG
Resource LimitsInterval 2
Until
Date
Time
Normal
Max.
Until
Date
Time
27-31
33-37
39-45
46-50
55-59
64-68
70-74
76-82
83-87
UNTIL
Field Name
Record Type
1-4
RLIM
Input Type
--
Normally blank; D to delete all limits for all

resources
Resource
6-13
A/N
Eight-character resource
Delete
14
--
Normally blank; D to delete limits for only this

resource (all intervals)
Resource
Limits Intervals
1 and 2 Normal
18-22
55-59
Normal periodic resource availability
- Maximum
27-31
64-68
Maximum periodic resource limit
- Until
33-37
70-74
UNTIL
- Date
39-45
76-82
A/N
Through date/time of resource limits in

DDMMMYY format;
Blank to use project completion date
- Time
46-50
83-87
A/N
Comments
Impose up to six sets of limit intervals by creating additional RLIM records. Use a
second RLIM record for intervals 3 and 4 and a third RLIM record for intervals 5 and
6. These additional records must follow the first RETL record of the series.
Leave the last Date field you use blank if the resource limits extend through the
project finish.
If the last through date field has a date earlier than the projects finish date, P3
assumes unlimited availability for the resource from the through date until the
projects finish.
P3 accepts RLIM records for resources defined by RETL records.
RULES
Use the RULES command to set Autocost rules for estimating costs within the project
group.
Field
Name:
Command
Set
Date
Columns:
1-4
6-9
11-15
17-20
22-28
Example:
PROJ
APEX
RULES
EMH
24JUL96
Autocost Rules
Autocost Recalculate
User-
Option
Costs
name
30
Y
32
N
34-35
SN
37-39
YYY
41-42
YY
44
Y
46
N
48
B
49
C
50
N
51-58
JOHN
Field Name
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Four-character name of existing project group
Command
11-15
--
RULES
Set
17-20
A/N
Any value
Date
22-28
A/N
Date rules set in DDMMMYY format
Autocost Rules 30
- Rule 1
--
Y or N (Y to link remaining duration and schedule

percent complete)
- Rule 2
32
--
Y or N (Y to freeze resource units per day)
- Rule 3
34
--
A or S (A to add actual to estimate to complete, S

to subtract actual from estimate at completion)
35
--
Y or N (Y to allow negative estimate to complete)
37
--
Y or N (Y to use current unit prices to recalculate

budget costs)
- Rule 4
Field Name
38
--

actual costs)
39
--

estimate to complete costs)
41
--
Y or N (Y to use update percent complete against

budget to estimate actual quantity)
42
--
Y or N (Y to use update percent complete against

budget to estimate actual cost)
- Rule 6
44
--
Y or N (Y to link actual date and actual this

period)
- Rule 7
46
--
Y or N (Y to link budget and EAC for nonprogressed activities)
- Rule 8
48
--
B or E (E to calculate variance as EAC - Budget,

B to calculate variance as Budget - EAC)
Autocost
Option
49
--
Specify application of Autocost rules when

moving between cells or resources. Valid entries
are C or R.
Recalculate
Costs
50
--
Y or N (Y to recalculate and store cost each time

the schedule is calculated)
Username
51-58
A/N
Valid username
- Rule 5
Comments
The RULES command affects the rules of the project group. Use the interactive
program to set rules for individual projects within the project group.
SNUM
Use the SNUM command to show the registered serial numbers that are in use or not in
use.
Field
Name:
Record Type
ListingType
CurrentOnly
User name
Output Device
Columns:
1-4
6-9
11-18
20-26
51-58
75-139
Example:
SNUM
LIST
INUSE
CURRENT
JOHN
P3.OUT
Field Name
Comments
List
Columns
Record Type 1-4
--
SNUM
List
6-9
--
LIST
Listing Type
11-18
--
INUSE
NOTINUSE
Current Only 20-26
Current - Serial number for current version only;

Blank - all versions
Username
51-58
A/N
Valid username
Output
Device
75-139
A/N
Any filename with or without extension; use

PRINTN to send output to printer port LPT1; leave
blank to save output in P3.OUT
When you process a run stream that uses the SNUM record, one serial number is
always locked.
The SNUM record is a standalone record; it does not need to be part of a project run
stream.
SUCC
SUCC records (identical to PREC records) describe precedence relationships in terms of
successor activities. Use either record to add a new successor relationship or to delete an
existing one.
Field Record
Name:
Input
Activity
Successor 1
Successor 2
Type
Type
ID
Activity ID
Rel. Type
Lag
Driving Flag
Activity ID
Rel. Type
Lag
Driving Flag
Columns:
1-4
6-15
17-26
28-29
34-37
38
39-48
50-51
56-59
60
Example:
PREC
A1
A11
A12
Successor 3
Activity ID
Rel Type
Lag
Driving Flag
61-70
A13
72-73
78-81
82
*
Field Name
Valid Data
Record Type 1-4
--
PREC or SUCC
Input Type
--
Normally blank; D to delete all successors for this

activity
Activity ID
6-15
A/N
Successors
1, 2, and 3
- Activity ID
17-26
39-48
61-70
A/N
--
28-29
Relationship 50-51
Type
72-73
SS for start to start; FF for finish to finish; FS or

blank for finish to start; SF for start to finish; D to
delete relationship between two activities
- Lag
For hourly, shift, daily, weekly, or monthly

calendars -999 to 9999; lag expressed in planning
units
34-37
56-59
78-81
Comments
Field Name
Valid Data
- Driving
Flag
38
60
82

--
You must use PREC, SUCC, or PRED records to define activity relationships.
When using INPUT, the activities referenced by PREC and SUCC records need not
be defined with ACTV records first. These activities must, however, be defined
somewhere in the same run stream.
PREC and SUCC records. These activities can be defined in a previous run stream,
earlier in the same run stream, or by using the interactive program.
PREC or SUCC records do not change data for existing relationships. To change
data such as relationship types or lag, delete the existing relationship and then
redefine it with a new PREC or SUCC record.
PREC or SUCC records normally follow ACTV records.
Data entered in columns 38, 60, and 82 are overwritten when you calculate a
schedule or level the project.
TITLE DATA
Use the TITLE DATA command to specify project group and individual project titles as
well as titles for activity codes, resources, and cost accounts. Complete this command
with a RETURN record.
Field
Name:
Comments
Command
Username
Columns:
1-4
6-9
11-20
51-58
Example:
PROJ
APEX
TITLE DATA
JOHN
Field Name
Columns
Contents
Justification
Valid Data
Record Type
1-4
--
PROJ
Project Group
Name
6-9
A/N
--

group
Command
11-20
--
TITLE DATA
Username
51-58
A/N
Valid username
Use the DRT1 and DRT2 record layouts to define headings for your output.
TITLE LIST
The TITLE LIST command lists all titles for codes, resources, and projects in the
database.
Field
Name:
Record Type
Project Name
Command
Username
Columns:
1-4
6-9
11-20
51-58
Example:
PROJ
APEX
TITLE LIST
JOHN
Field Name
Columns
Contents
Record Type
1-4
--
PROJ
Project Name
6-9
A/N
--
Four-character name of existing project group
Command
11-20
--
TITLE LIST
Username
51-58
A/N
Valid username
Comments
Error Conditions
Nonexistent project name
This command produces a list of titles for projects, codes, and resource and cost
accounts.
UPDATE
Use the INPUT or UPDATE record to add or change activity data. The first run after
adding a new project must use the INPUT record. All subsequent runs require the
UPDATE record. If you specify INPUT for a project that already contains activity information and you execute the Batch job, the Batch program prompts you to either overwrite
the existing data with the new data or terminate the Batch run.
Field
Name:
Record Type
Validate
Full List
Open-End List
Columns:
1-6
9-11
13-15
Example:
UPDATE
NO
NO
Field Name
Record Type
1-6
Validate
Blank or X
Full List
9-11
YES to print complete list of all activity records in

run stream; NO to print only a diagnostic list of
project-level data and open-end list, if specified
YES to print list of activities with no successors or

predecessors; NO to print only a diagnostic list of
project-level data and full list, if specified
Open End List 13-15
Comments
INPUT or UPDATE
Normally blank; X suppresses normal data
validation
An INPUT or UPDATE record must follow a PROJ record with the EXECUTE
command.
An INPUT or UPDATE run stream must end with a RETURN record.
Use the INPUT record only once to initiate a project; thereafter, use UPDATE.
Activity ID Field
An INPUT or UPDATE record must precede any ACTV, PREC, SUCC, PRED,
CODE, RESR, PERIOD CLOSEOUT, LIST, or DATE record.
When using INPUT, the activities referenced by PREC, SUCC, and PRED records
need not be defined with ACTV records first. These activities must, however, be
defined somewhere within the same run stream.
PREC, SUCC, and PRED records. These activities can be defined in a previous run
stream, earlier in the same run stream, or by using the activity detail forms.
If you suppress validation, the program will not check for the existence of referenced
activities, resources, or cost accounts. Relationships to nonexistent activities will not
be prevented.
The Activity ID field appears in the ACTV, ACTVR, PREC, SUCC, PRED, CODE, RESR,
LIST, and DATE records. The position of data in this field is user-defined; however, it
must be consistent with the P3 interactive system and among all Batch records. The interactive system automatically right justifies activity IDs that contain all numeric characters.
If the activity ID includes one or more letters, blank spaces, or special characters, P3
positions the data as they are entered. Activity IDs can use all 10 available characters.
How you choose to position data in the Activity ID field also affects the definition of code
fields within the activity ID; the CDEF record references column positions within the
available 10 characters relative to the first (left-most) column.
WBSA
Use the WBSA record to assign a WBS code to an activity.
Field
Record Type
Name:
Comments
Columns:
1-4
Example:
WBSA
Input Type
5
Activity ID
WBS Code
6-15
17-64
A1
AM12B
Field Name Columns Contents Justification
Valid Data
Record
Type
1-4
--
WBSA
Input Type
--
Normally blank;
D to delete the WBS value for the activity
Activity ID
6-15
A/N
--
Any value up to 10 alphanumeric characters
WBS Code
17-64
A/N
1-48 alphanumeric characters. This code must

correspond with the field-width definition set with
the WBSD record, excluding separators.
One WBSA record is permitted per activity.
The activity referenced by the activity ID must exist.
WBSD
Use the WBSD record to define the WBS structure, including level number, field width,
and separator character. Each WBSD record defines a single WBS level.
Field
Name:
Comments
Record Type
Input Type
WBS Level Number
Field Width
Separator
Character
Columns:
1-4
11-12
14-15
17
Example:
WBSD
Field Name
Valid Data
Record Type
1-4
--
WBSD
Input Type
--
Normally blank; D to delete this definition
Level Number 11-12
Level number 1-20
Field Width
14-15
1-48
Separator
17
--
--
P3 uses a period (.) by default, but you can use

any character
Field widths for a single level cannot exceed 10 characters. The combined field
widths for all WBS levels cannot exceed 48 characters.
WBST
WBST records define WBS codes and their titles once the WBS structure is defined using
WBSD records.
Field
Record Type
Name:
Columns:
1-4
Example:
WBST
Field Name
Comments
Input Type
5
WBS Code
Title
9-56
58-105
AM12B
SYSTEM ENGINEERING
Record Type 1-4
--
WBST
Input Type
--
Normally blank; D to delete this WBS title
WBS Code
9-56
A/N
Specify a WBS code without separators
Title
58-105
A/N
Title (description) for the WBS code
WBST records normally follow the WBSD records.

The level at which the value of each record is placed in the outline is determined by
which WBS field contains the right-most nonblank character.
The Batch processor supplies any superior levels that do not already exist.
Embedded blanks are significant in the WBS code.
Batch Error Messages

This section lists common P3 Batch system error messages. If you encounter an error not
listed here, check each record in the run stream for valid data, contents, and code justification. Also, refer to the sample run streams to verify that records are in the correct
sequence in the file.
Error 1
Invalid Report Type Specified
Error 2
Invalid Target Specification

Suggestion: Make sure the target specified is an existing target schedule
Error 3
Invalid Code Element

Suggestion: This error often indicates that the report specification contains activity
codes that do not exist for this project. Verify spelling and justification in the specified
criteria. Create another report specification.
Error 4
Invalid Line Type Specification
Error 5
Activity Line Not Specified
Error 6
Invalid Record Type for Reporting

Suggestion: Before processing a Batch file, make sure you save all the necessary
blank spaces. Check the spelling of record names.
Error 7
Invalid Report Date
Error 8
Invalid Copy and Rename Specifier
Error 9
Invalid MASK Element

Suggestion: Review the report specification. The mask element specified for skip
may not apply to the current project.
Error 10
Invalid File Specified on Report Record
Error 11
Invalid Start Day of Week (Day)
Error 12
Not Used
Error 13
Project Record Data Error

Suggestion: Examine the PROJ record in the Batch file. Make sure you allowed all
necessary blank spaces (no tabs allowed), and that all alphabetic characters are
uppercase.
Error 14
Invalid Command
Suggestion: Check the command specified on the PROJ record in the Batch file.
Error 15
Project Not Found

Suggestion: Check the spelling of the project name. The number zero and the letter
O are not interchangeable.
Error 16
Invalid Establish Target Specifier
Error 17
Project Has Not Been Scheduled
Error 18
Project in Use, Access Denied
Error 19
Input Record Sequence Error

Suggestion: Check the order of input records in the Batch file. If adding a new
project, make sure a PCAL record immediately follows the PROJ record.
Error 20
Calendar Specification Error

Suggestion: Check the dates specified in the PCAL record of the Batch file. All dates
must be in DDMMMYY HH:MM format (for example, 01JAN97 06:00). Hours and
minutes are used for hourly projects only.
Error 21
Invalid Project Group Name
Error 22
Project Group Name Already Exists

Suggestion: Change the name of the project group to be added to avoid duplicates.
Error 23
Target Schedule Designation Invalid

Suggestion: Verify the column position of codes on the ESTABLISH TARGET line.
Make sure the target schedule is either 1 or 2.
Error 24
Invalid Execute Command

Suggestion: Check the spelling and spacing of the EXECUTE command.
Error 25
Invalid Report Command
Error 26
Invalid Selection Element

Suggestion: Verify the spelling and justification of the specified criteria on the SELE
line in the file.
Error 27
Invalid Equality Type
Error 28
Invalid Limit Values
Error 29
Invalid Input Record Select File Established
Error 30
Invalid Record Type in Update Run
Error 31
Invalid Activity ID - Data Ignored

Suggestion: Check columns 6-15 of the Batch file against the appropriate record
layout. When adding new activities, make sure the PREC, PRED, or SUCC record
follows the ACTV record for the activity referenced in columns 6-15. Or execute the
PREC, PRED, or SUCC record in a separate run after all activities have been added
to the network. The error diagnostic report displays asterisks under the field in error
to indicate the correct format.
Error 32
Activity Not Found in File

Suggestion: Check the activity number. When adding new activities, make sure the
PREC, PRED, or SUCC record for a new activity immediately follows the ACTV
record for that activity. Or execute the PREC, PRED, or SUCC record in a separate
run after all activities have been added to the network.
Error 33
Added Activity Already Exists

Suggestion: Check the activity number.
Error 34
Format Error, Columns Flagged

Suggestion: The field with the incorrect format is specified by asterisks. Make sure
the data do not exceed specified field limits and that numeric fields do not contain
alphabetic data. Also, check your project for any activities that have start to start
relationships with finish milestones or finish to finish relationships with start
milestones.
Error 35
New Activity Already Exists
Error 38
Illegal Cursor Position (row/column)
Error 39
Invalid Resource
Error 40
Attempt to Delete a Nonexistent Project
Error 46
Invalid Record Type in Loading Library

Suggestion: Make sure columns 1-4 in the Batch file indicate a record type that is
correctly associated with the TITLE DATA command. Check the record sequence for
the correct type of specification.
Error 47
Invalid Data
Suggestion: Check the data on the CDEF record of the Batch file. Make sure all field
definitions are valid.
Error 48
Invalid Title Data

Suggestion: Check the COTL record of the Batch file for consistency.
Error 49
Code Value Not in File

Suggestion: Check the spelling of the code value for which a title is to be deleted.
Error 54
Resource/Cost Account Not Used by This Activity
Error 55
Array Overflow
Error 56
Resource/Cost Account Both Blank
Error 57
Error in ES Targ
Error 59
Summary Must Be Preceded by SORT
Error 60
Missing NLOG Record
Error 61
Invalid Masking Specified
Error 62
Invalid Code Fields Specified
Error 63
No Timescale Specification Record

Suggestion: Specify a timescale in hours/shifts/days/weeks/months when requesting
a timescale report.
Error 64
Invalid Timescale Specified

Suggestion: The report specification contains an invalid timescale. Make sure H, S,
D, W, or M (for hours, shifts, days, weeks, or months) is specified for the timescale,
and check the range of months specified to ensure that the dates do not exceed the
project calendar.
Errors 66 to 75
Unused
Error 76
Invalid Resource Code

Suggestion: Check the spelling of resource code(s) in the Batch file. Make sure a
resource code is defined before it is assigned to activities. Verify the code justification as defined in the Resource Dictionary (RETL record).
Error 77
Invalid Equality Type
Error 78
Invalid Select Element

Suggestion: The selection criteria specified in the resource/cost report specification
are invalid. Check the RSEL line in the run stream for valid data.
Error 80
Invalid Resource - Data Ignored

Suggestion: Make sure you defined resource codes in the Batch file before you
execute the UPDATE or INPUT record.
Error 81
Invalid Critical Flag
Errors 82 to 88
Unused
Error 90
Invalid Target File Specified

Suggestion: Review the target specification in the run stream. Make sure Target 1
exists before you produce a resource/cost report with target data.
Error 91
Invalid Report Specification
Error 92
Invalid Cumulative Curve Specification
Error 93
Invalid Profile Curve Specification
Error 94
Invalid Usage Report Specification
Error 95
Invalid Resource Report Run Stream Record

Suggestion: This error usually occurs when selection criteria in the report specification are invalid. Verify the code justification (R or L) as defined in the Resource
Dictionary (RETL record). Also check the RSEL line in the file for valid selection
criteria.
Error 96
Invalid Resource Report Specified
Errors 98 to 99
Undefined Calendar
4-131
P3 2.0 Files
In this chapter:
P3 Data Tables
P3 Data Table Connections
P3 File Structures
P3.INI Options
This chapter provides the contents of the P3 2.0 files including

data tables and their structures. The contents of the P3.INI file
are listed also.
Data dictionary files provide the link to P3s project files, and
must be created for any P3 project you want to access through
another ODBC-compliant application. This chapter provides the
contents of the data tables; one data table exists for each
project file. For purposes of accessing P3 with other applications, such as Microsoft Excel or ReportSmith, you need only
choose the data tables that contain the fields you want.
P3 2.0 Files 4-132
P3 Data Tables
The following data tables are created for a project, depending on which mode (normal or
advanced) you select in the Update Data Dictionary dialog box in P3. Normal mode
generates the most commonly used fields in P3, such as activity ID, early dates, late
dates, and total float. Advanced mode lists all P3 data fields within the report writers.
P3 updates the data dictionary files, FILE.DDF and FIELD.DDF, and creates three
temporary files (XXXXAIT, XXXXRIT, and XXXXDTL) so you can readily access project
data. The XXXXAIT, XXXXRIT, and XXXXDTL file structures are provided later in this
chapter.
.
Table
Normal Mode
Advanced Mode
ACC - Cost Accounts
CostAccountNumber
ACCTitle
CostAccountNumber
ACCTitle
P3 2.0 Files 4-133
Table
Normal Mode
Advanced Mode
ACT - Activities
ActID
ActivityTitle
CalId
OrigDur
RemDur
Pct
ES
ActID
ActivityTitle
CalId
OrigDur
RemDur
Pct
ES
ESHour
EF
EFHour
LS
LSHour
LF
LFHour
TotalFloat
Activitycodes
FreeFloat
ESInternal
EFInternal
LSInternal
LFInternal
ASorEDConstraint
AForLLDConstraint
ASFlag
AFFlag
ASorConstraintFlag
AForConstraintFlag
SuspendDate
ResumeDate
Milestone
CriticalFlag
DurationCalcCode
VarianceSort/Select
STActivityType
EF
LS
LF
TotalFloat
Activitycodes
FreeFloat
ESInternal
EFInternal
LSInternal
LFInternal
ASorEDConstraint
AForLLDConstraint
ASFlag
AFFlag
P3 2.0 Files 4-134
Table
Normal Mode
AIT - Activity Custom Data ActID

Items
ActivityCustomDataItems
Advanced Mode
ActID
Res
CostAccountNumber
ResourceID
ActivityIDext
ActivityCustomDataItems
DIR - Project Directory
Not available
ProjVersion
AutocostSet
AutocostDate
AutocostRules
ScheduleLogic
InterruptibleFlag
LatestEarlyFinish
Target#1Name
Target#2Name
LeveledSwitch
TotalFloatType
StartDayOfWeek
MasterCalType
GraphicSummaryProj
DecimalPlaces
SummaryCalID
EndDateFromM/S
SSLagFromAS/ES
WBSW01 WBSS01...WBSS20
HolidayConvention
ProjType
MastCalTypeAux
SchedMast/Sub
UpdateSubDataDate
DTL - Activity Code

Details
CodeName
CodeValue
Description
CodeName
CodeValue
Description
P3 2.0 Files 4-135
Table
Normal Mode
Advanced Mode
HOL - Calendar Holidays Not available
CalID
StartOfHoliday
EndOfHoliday
LOG - Activity Log
ActID
LogSeqNumber
LogMask
LogRecord Info
ActID
LogSeqNumber
LogMask
LogRecord Info
ActIDExt
REL - Activity Relationships
PredAct
SuccAct
LagType
DrivingRel
PredAct
PredActExt
SuccActExt
SuccAct
LagType
DrivingRel
P3 2.0 Files 4-136
Table
Normal Mode
Advanced Mode
RES - Resources
ActID
ResID
CostAccountNumber
PctComplete
Lag
RemDur
ResDesignator
DrivingResource
BudgetQuantity
QTYThisPeriod
QTYToDate
QTYAtCompletion
BudgetCost
CostThisPeriod
CostToDate
CostAtCompletion
ActID
ResID
CostAccountNumber
PctComplete
Lag
RemDur
ResDesignator
DrivingResource
BudgetQuantity
QTYThisPeriod
QTYToDate
QTYAtCompletion
BudgetCost
CostThisPeriod
CostToDate
CostAtCompletion
STResEarlyStart
STResEarlyFinish
STResLateStart
STResLateFinish
RIT - Resource Custom

Data Items
ActID
Res
CostAccountNumber
ResourceID
ActID
Res
CostAccountNumber
ResourceID
ActIDext
ResourceCustomDataItems
ResourceCustomDataItems
P3 2.0 Files 4-137
Table
Normal Mode
Advanced Mode
RLB - Resource
Dictionary
ResID
UnitOfMeasure
ResTitle
EscalationVal1
EscalationDate1
EscalationVal2
EscalationDate2
EscalationVal3
EscalationDate3
EscalationVal4
EscalationDate4
EscalationVal5
EscalationDate5
EscalationVal6
EscalationDate6
NormLimVal1
MaxLimVal1
LimToDate1
NormLimVal2
MaxLimVal2
LimToDate2
NormLimVal3
MaxLimVal3
LimToDate3
NormLimVal4
MaxLimVal4
LimToDate4
NormLimVal5
MaxLimVal5
LimToDate5
NormLimVal6
MaxLimVal6
LimToDate6
ShiftNum
ShiftLimitTable
DrivingResource
ResID
UnitOfMeasure
ResTitle
EscalationVal1
EscalationDate1
EscalationVal2
EscalationDate2
EscalationVal3
EscalationDate3
EscalationVal4
EscalationDate4
EscalationVal5
EscalationDate5
EscalationVal6
EscalationDate6
NormLimVal1
MaxLimVal1
LimToDate1
NormLimVal2
MaxLimVal2
LimToDate2
NormLimVal3
MaxLimVal3
LimToDate3
NormLimVal4
MaxLimVal4
LimToDate4
NormLimVal5
MaxLimVal5
LimToDate5
NormLimVal6
MaxLimVal6
LimToDate6
ShiftNum
ShiftLimitTable
DrivingResource
P3 2.0 Files 4-138
Table
Normal Mode
Advanced Mode
SRT - Current Sort
Not available
SeqNumber
ActID
STR - WBS Dictionary
Indicator
CodeValue
Codetitle
Indicator
CodeValue
Codetitle
IndicatorExt
CodeValueSeg1
TTL - Code Titles
Not available
CodeName
CodeValue
Description
SortOrder
WBS - WBS Records
ActivityID
CodeValue
Indicator
ActivityID
CodeValue
Indicator
P3 2.0 Files 4-139
P3 Data Table Connections

To access multiple data tables at once, you need to link key fields. For example, if you
want to report on cost accounts for each activity, you need to link the ACT and RES files
through the activity ID field, and link the RES and ACC files through the cost account
number field. The following figure shows the data tables created in advanced mode; the
field names in italics indicate the fields used to link the data tables.
Code Name
DIR
ACT
Calendar ID
General project
information Table
Activities Table
Activity ID
REL
Relationships
Table
LOG
Log records Table
WBS
Assignments
Table
SRT
Current sort Table
Code Value
DTL
ReadOnly
Activity code
titles/values Table
Holiday file Table
RES
Resource
assignments
Table
Cost Account Nmbr.
Resource ID
TTL - Updates P3
HOL
AIT
Read Only
Activity custom
data items Table
STR
RLB
WBS Structure
Table
Resource
dictionary Table
RIT
Read Only
Resource custom
data items Table
ACC
Cost Accounts
Table
4-140
P3 File Structures
Project Directory File
(XXXXDIR.P3)
XXXXDIR.P3: Data in
100001 record
XXXXDIR.P3: Data in
100002 record
XXXXDIR.P3: Data in
100003 record
USERFIL.P3
XXXXACT.P3
XXXXREL.P3
XXXXRES.P3
XXXXSPR.P3
XXXXLOG.P3
XXXXWBS.P3
XXXXTTL.P3
XXXXACC.P3
XXXXRLB.P3
XXXXITM.P3: Data in
Dictionary Records
XXXXITM.P3: Data in
Data Item Value Records
XXXXSTR.P3
XXXXHOL.P3
XXXXCAL.P3
XXXXSRT.P3
XXXXREP.P3 /
XXXXPLT.P3
XXXXAC2.P3
USERS50.P3
XXXXLAY.P3
XXXXSTW.P3
P3 file structures are index-accessed, variable-length files

created by Btrieve. Btrieve provides multikey access to
records; relational access among files; automatic key
maintenance support for duplicate, modifiable, and
segmented keys; and unrestricted file sizes. Some files
have multiple or segmented keys.
File names are shown in parenthesis, and XXXX is used to
denote the four-character project name. Data locations
within a file refer to four-byte integer or character words. In
some cases, a four-byte word may contain multiple logical
fields, and not all bytes in each word are used.
Key fields are listed for each file structure. ND indicates no
duplicates allowed, D indicates duplicates are allowed, M
indicates modifiable, and SEG indicates segmented.
P3 2.0 Files 4-141
Project Directory File (XXXXDIR.P3)

.H\&+$5 1'0
BYTE
WORD
DESCRIPTION
1-4
4 blanks for project group name or project name (CHAR*4)
5-8
Sequence number (INT*4)

0 = main record
100001 - 100003 = calendar information
9-12
Product code
0 = P3
1= Finest Hour
Product code * 10000 + rev. * 100
(0 * 10000 + 2.0 * 100 = 200)
13-16
Project start date (yyyymmddqq)
17-20
Holiday Convention
0 = default
1 = don't move holiday to nearest workday
21-24
Project ID (CHAR*2)
25-28
Project finish date (yyyymmddqq)
29-32
Report counter
33-56
9-14
Code field length definitions (4 field length per word)
57-60
15
Type of project (PDM = 0)
61-64
16
Data date (last scheduled) (yyyymmddqq)
65-68
17
Calendar start date (yyyymmddqq)
P3 2.0 Files 4-142
BYTE
WORD
DESCRIPTION
69-72
18
Oracle flag (CHAR*4)

('ORAC' if Oracle project, else Btrieve)
72-108
19-27
Default company title (CHAR*36)
109-144
28-36
Default project title (CHAR*36)
145-192
37-48
Default report title (CHAR*48)
193-208
49-52
Project version (CHAR*16)
209-240
53-60
Not used.
241-244
61
Autocost set field (CHAR*4)
245-248
62
Autocost date field (yyyymmddqq)
249-264
63-66
Autocost rules (14 CHAR*1)

Y/'N' - Link RD and PCT
'Y'/'N' - Freeze UPT
'A'/'S' - Add (ATD+ETC) or subtract (EACATD)
'Y'/'N' - Allow negative ETC
'Y'/'N' - Recompute BC if BQ changed
'Y'/'N' - Recompute CTD if QTD changed
'Y'/'N' - Recompute CTC if QTC changed
'Y'/'N' - Estimate QTD using BQ x PCT
'Y'/'N' - Estimate CTD using BC x PCT
'B'/'E' - Variance is BudgetEAC or EACBudget
'Y'/'N' - Autocost during scheduling
'Y'/'N' - Link ATD and ATP
'Y'/'N' - Link EAC and Budget
P3 2.0 Files 4-143
BYTE
WORD
DESCRIPTION
'C'/'R' - Autocost by Cell or Resource
265-276
67-69
Not used
277-280
70
Schedule logic (INT*4)

0 = retained logic
1 = progress override
281-284
71
Interruptible flag (INT*4)

0 = non-interruptible
1 = interruptible
285-288
72
Latest early finish date (yyyymmddqq)
289-292
73
Target 1 name (CHAR*4)
293-296
74
Not used
297-300
75
Target 2 name (CHAR*4)
301-304
76
Not used
305-308
77
Leveled switch (INT*2)

0 = Not leveled
1 = Leveled early
2 = Leveled late
3 = Leveled both
Total Float Type (INT*2)
0 = Start
1 = Finish
2 = Most critical
309-312
78
Schedule open ends as critical flag (CHAR*1)
P3 2.0 Files 4-144
BYTE
WORD
DESCRIPTION
Leveling - save data into SPR file flag (CHAR*1)
1 = dont store data
0 = store data
311-312
313-316
Not used
79
Start day of the week (INT*2)

Mon = 1
Tue = 2
Wed = 3
Thu = 4
Fri = 5
Sat = 6
Sun = 7
317-320
80
Project group calendar type (INT*2)

Hour = 3
Day = 5
Week = 6
Month = 7
321-324
81
Byte 321: Graphic reports - summary projects (CHAR*1)

'S' = summary project else blank
Byte 322: Scheduling in project group, project, or both ('M'/'S'/'B')
Byte 323: Decimal places ('0'/'2')
Byte 324: Update project's data date to match project group's data date ('Y'/'N')
325-328
82
Byte 325: Summary calendar ID
P3 2.0 Files 4-145
BYTE
WORD
DESCRIPTION
Byte 326: Calculate total float using end date of project group or project
M = project group
S = project
Byte 327: SS lag from AS/ES
'0' = ES
'1' = AS
Byte 328: OEM/ANSI Flag
'1' = Converted
329-368
83-92
WBS widths and separators (CHAR*40)

(Stored Width, Sep., Width, Sep., etc.; with Width as CHAR*1 and Sep. as
CHAR*1)
369-372
93
INTRPROJ project index (INT*4)
373-376
94
INTRPROJ last scheduled date (INT*4)
377-380
95
Leveling: Maximum number of splits (INT*2)

Leveling: Maximum split nonworktime (INT*2)
381-384
96
Leveling: Min contiguous worktime between splits (INT*2)

Leveling: Minimum % of UPT for stretching (INT*2)
385-388
97
Leveling: Maximum % of UPT for crunching (INT*2)

(Bytes 387 - 388 not used)
389-504
98-126
Not used
Physical record size = (126*4) + (8*0 keys allow duplicates) = 504 bytes
Page size = 512 bytes [unused bytes per page = 512 6 (1*504)] = 2 bytes
P3 2.0 Files 4-146
XXXXDIR.P3: Data in 100001 record

Key: CHAR*8 (ND-M)
BYTE
WORD DESCRIPTION
1-4
Four blank characters
5-8
100001 = Extension record #1
9-442
3-111
Start hour of work for each day of the week for each calendar (INT*2)
443-473 111-119 Not used

476-480 120
Number of shifts per day (0-6)(INT*4)
481-484 121
First shift start time in quarter hours (INT*4)
485-488 122
Duration of shifts in quarter hours (INT*4)
489-504 123-126 Not used
P3 2.0 Files 4-147

Key: CHAR*8 (ND-M)
BYTE
WORD DESCRIPTION
1-4
5-8
9-442
3-111
Finish hour of work for each day of the week for each calendar (INT*2)
FINHR(7,31)
Value = 96 for a full day
443-473 111-119 Defines which calendar IDs are used (31 1-byte values)
Not used = 0; Hour = 3; Day = 5; Week = 6; Month = 7
474-504 119-126 Not used
P3 2.0 Files 4-148

Key: CHAR*8 (ND-M)
BYTE
WORD DESCRIPTION
1-4
5-8
9-504
3-126
Calendar description of each of the 31 calendars (CHAR*16)

Byte
9-24
25-40
41-56
etc.
Word
3-6
7-10
11-14
Description
Cal.1 title
Cal.2 title
Cal.3 title
P3 2.0 Files 4-149
USERFIL.P3
Key: CHAR*8 (ND-M)
BYTE
WORD DESCRIPTION
1-8
1-2
User name
9-12
Add project: always 0 (INT*2) (Bytes 11-12 not used)
13-20
4-5
Output filename for DOS (CHAR*8)
21-24
Summary percent option (INT*4)

0 = Duration; 1 = Resource; 2 = Cost
25-28
Graphics reports plotter/printer type for WIN (INT*4)
29-32
Budget/earned value indicator

0 = Current budget (INT*4)
1 = Target budget
33-36
Not used
37-40
10
Printer type (INT*2)

Byte 39: Compressed mode ('Y'/'N')
Byte 40: Graphic report sight lines
'.' = short dashed line
'-' = long dashed line
S' = solid line
41-104
11-26
Printer codes
105-112 27-28
Password
113-120 29-30
Not used
P3 2.0 Files 4-150
BYTE
WORD DESCRIPTION
121-156 31-39
Bar chart printer characters

1st byte of each word = character
2nd byte of each word = normal color
3rd byte of each word = critical color
4th byte of each word = not used
157-160 40
User access type (INT*2)

10 = privileged user
else = normal user
Print sort/select criteria (INT*2)
161-164 41
Not used
165-172 42-43
Latest plotter output filename (CHAR*8)
173-176 44
Graphics report output: Output/Save/View/Ask

('O'/'S'/'V'/'A' - CHAR*1)
Separate Sheets ('Y'/'N') (CHAR*1)
Sheet size (INT*2)
177-180 45
Not used
181-184 46
PV Printer Number (INT*2)

Postscript Font (INT*2)
185-192 47-48
Latest View Filename (CHAR*8)
193-196 49
Not used
197-200 50
PV Output Device (CHAR*4)
201-220 51-55
Not used
221-224 56
Validate Activity Codes (INT*4)

0 = don't validate codes (default)
1 = validate activity codes
225-228 57
Not used
P3 2.0 Files 4-151
BYTE
WORD DESCRIPTION
229-232 58
Not used
233-236 59
Latest mail message number (INT*4)
237-240 60
Byte 237 = Disk Specification (CHAR*1)

Byte 238 = Mail Notification (CHAR*1)
Byte 239 = Autosort number (CHAR*1)
Byte 240 = Activity Forms window (CHAR*1)
241-276 61-69
Not used
277-280 70
Byte 277: Tabular reports output:

Print, Save, View, Ask ('P'/'S'/'V'/'A')
Byte 278: Not used
Bytes 279-280: Lines per page (INT*2)
281-360 71-90
Not used
361-384 91-96
User full name (CHAR*24)
385-396 97-99
User telephone number (CHAR*12)
397-436 100-109 Graphics reports output directory path (CHAR*40)

437-444 110-111 Not used
445-456 112-114 Output filename for WIN (CHAR*12)
457-504 115-126 Not used
P3 2.0 Files 4-152
XXXXACT.P3
Key: CHAR*10 (ND-M)
BYTE
WORD DESCRIPTION
1-12
1-3
Activity ID (CHAR*10)
13-16
Free float (INT*2)

Calendar ID # (INT*2)
17-20
Duration calculation code (INT*4)

ZT = 1
ZF = 2
HA = 3
XF = yyyymmddqq
21-24
Original duration (INT*2)

Remaining duration (INT*2)
25-28
Actual start or early date constraint flag (INT*2)

99 = Actual
1 = ES
3 = EF
6 = ON
10 = MS
11 = MF
Actual finish or late date constraint flag (INT*2)
99 = Actual
2 = LS
4 = LF
6 = ON
29-32
Percent complete (INT*4)

(4 digits = PCT*10)
P3 2.0 Files 4-153
BYTE
WORD DESCRIPTION
33-36
Early start (yyyymmddqq)
37-40
10
Late start (yyyymmddqq)
41-44
11
Actual start (yyyymmddqq)
45-48
12
Actual finish (yyyymmddqq)
49-52
13
Early finish (yyyymmddqq)
53-56
14
Late finish (yyyymmddqq)
57-60
15
Total Float (INT*2)

Byte 59: Milestone (CHAR*1)
0 = NM
1 = SM
2 = FM
5 = SF
6 = FF
Byte 60: Critical flag ('C' or blank)
61-64
16
Bytes 61-62: Not used

Byte 63: Estimate Quality
65-68
17
Reserved for SureTrak use
69-72
18
SureTrak Activity Type (CHAR*1)

0 = Task; 1 = Independent; 2 = Meeting; 3 = SM; 4 = FM; 5 = Hammock; 6 = WBS;
7 = Topic; 8 = SF; 9 = FF
SureTrak Leveling Type (CHAR*1)
0 = Normal; 1 = Immediate; 2 = Splittable; 3 = Stretchable;
4 = Crunchable; 5 = Stretchable and Crunchable
Bytes 71-72 not used
73-136
19-34
Activity codes (64 characters)
P3 2.0 Files 4-154
BYTE
WORD DESCRIPTION
137-184 35-46
Activity title (48 characters)
185-188 47
Suspend date (yyyymmddqq)
189-192 48
Resume date (yyyymmddqq)
193-196 49
Constraint types (4 CHAR*1)
197-200 50
Constraint #1 (yyyymmddqq)
201-204 51
205-208 52
209-212 53
213-216 54
Early start date - Btrieve
217-220 55
Late start date - Btrieve
221-224 56
Early finish date - Btrieve
225-228 57
Late finish date - Btrieve
229-232 58
Byte 229: Early start hour (1-24)

Byte 230: Late start hour (1-24)
Byte 231: Early finish hour (1-24)
Byte 232: Late finish hour (1-24)
233-234 59
Byte 233: Actual start (' ' or 'A')

Byte 234: Actual finish (' ' or 'A')
235-236
Not used
237-244 60-61
Not used
Physical record size = (61*4) = 244 bytes

Page size = 1024 bytes
Unused bytes per page = 1024 6 (244*4) = 42 bytes
P3 2.0 Files 4-155
XXXXREL.P3
Key 1: CHAR*26 (ND-M)
Key 2: CHAR*26 (ND-M-SEG)
Segment 1: Words 4-6
Segment 3: First 2 bytes of word 7
BYTE
WORD DESCRIPTION
1-12
1-3
Predecessor activity (CHAR*10)
13-24
4-6
Successor activity (CHAR*10)
25-28
Successor lag type (INT*2)

SS = 1
FS = 2
FF = 3
SF = 4
Successor lag value (INT*2)
29
Driving relationship (CHAR*1)

D = successor early dates are driven by predecessor
Physical record size = (7*4) + 1 + (8*0 key allow duplicates) = 29 bytes

P3 2.0 Files 4-156
XXXXRES.P3
Key 1:CHAR*10 (D-M) Words 1-3
Key 2:CHAR*8 (D-M) Words 4-5
Key 3:CHAR*31 (ND-M-SEG)
Segment 3: Bytes 1-10
Segment 4: Byte 39
BYTE
WORD DESCRIPTION
1-12
1-3
Activity ID(CHAR*10)
13-20
4-5
Resource ID (CHAR*8)
21-32
6-8
Cost Account Number (CHAR*12)
33-36
Percent complete (INT*2)

(4 digits = PCT*10)
Lag (INT*2)
37-40
10
Resource remaining duration (INT*2)

Byte 39: Resource ID (CHAR*1)
Byte 40: Driving Resource (CHAR*1)
'*' = driving
blank = not driving
41-44
11
Original quantity budget estimate
45-48
12
Actual quantity for period
49-52
13
Actual quantity to date
53-56
14
Forecast quantity
57-60
15
Early start
61-64
16
Early finish
P3 2.0 Files 4-157
BYTE
WORD DESCRIPTION
65-68
17
Not used
69-72
18
Original cost budget estimate
73-76
19
Actual cost for period
77-80
20
Actual cost to date
81-84
21
Forecast cost
85-88
22
Late start
89-92
23
Late finish
93-96
24
Not used
NOTE: Values in words 11-14 and 18-21 have been multiplied by 100 if the decimal places setting in byte
323 of DIR file is equal to '2'.
Page size = 1024 bytes [unused bytes per page = 1024 6 (120*8)] = 58 bytes
P3 2.0 Files 4-158
XXXXSPR.P3
Key: CHAR*31 (ND-M)
BYTE
WORD DESCRIPTION
1-10
1-3
11-18
3-5
Resource (CHAR*8)
19-30
5-8
Cost account (CHAR*12)
31
Resource ID/Curve (CHAR*1)
32
Unused (CHAR*1)
33-??
9-??
Resource/cost spread data:

For task activities, the key is the Activity ID and blanks for the resource, cost
account, and curve. The data is a series of start and finish dates signifying the
periods that the activity works. Limit is 8000 pairs.
For independent activities, the key is the Activity ID, resource, cost account, and
values that represent the usage per workperiod on the resource calendar (first
value starts at the resource ES). Limit is 16000 workperiod values.
Physical record size = Variable record length

(Maximum record = 64032 bytes)
P3 2.0 Files 4-159
XXXXLOG.P3
Key: CHAR*14 (ND-M)
BYTE
WORD DESCRIPTION
1-12
1-3
13-16
Log sequence number (INT*2)

Mask character (CHAR*2)
(Mask is not part of key)
Log sequence number:
1-99 = log information
17-64
5-16
Log record information

P3 2.0 Files 4-160
XXXXWBS.P3
Segment 1: bytes 1-10
Segment 2: byte 61
Segment 1: byte 61
BYTE
DESCRIPTION
1-10
11-12
Unused
13-60
Code value (CHAR*48)
61
Indicator (CHAR*1) 'W' for WBS records
Physical record size = (61) + (8*0 keys allow duplicates) = 61 bytes

P3 2.0 Files 4-161
XXXXTTL.P3
Segment 1:word 1
or
Segment 2:byte 65
Segment 3:words 2-4
BYTE
WORD DESCRIPTION
1-4
Code field designation (INT*4)

(10 digits, 5 pairs)
5-16
2-4
Code field value (right-justified) (4 characters per word) OR ******** in first 8 bytes,
code field name in last 4 bytes (CHAR*12)
17-64
5-16
Title description (48 characters)
65
17
User-defined sort order

CHAR(1) - CHAR(255)
Physical record size = (16*4) + 1 + (8*0 keys allow duplicates)=65 bytes

P3 2.0 Files 4-162
XXXXACC.P3
Key: CHAR*12 (ND-M)
BYTE
WORD DESCRIPTION
1-12
1-3
Cost Account Number (CHAR*12)

******** in first 8 bytes, category in last 4 bytes
13-16
Not used
17-56
5-14
Cost Account Title (CHAR*40)

or
Cost Category Description (CHAR*8)

P3 2.0 Files 4-163
XXXXRLB.P3
Key: CHAR*10 (ND-M-SEG)
Segment 1:words1-2
Segment 2:bytes 173-174
BYTE
WORD DESCRIPTION
1-8
1-2
Resource code (CHAR*8)
9-12
Unit of measure (CHAR*4)
13-52
4-13
Resource description (40 characters)
53-56
14
1st escalation value
57-60
15
1st escalation up to date (yyyymmddqq)
61-68
16-17
2nd escalation
69-76
18-19
3rd escalation
77-84
20-21
4th escalation
85-92
22-23
5th escalation
93-100
24-25
6th escalation
101-104 26
1st normal limit value
105-108 27
1st maximum limit value
109-112 28
1st limit up to date (yyyymmddqq)
113-124 29-31
2nd limit
125-136 32-34
3rd limit
137-148 35-37
4th limit
149-160 38-40
5th limit
161-172 41-43
6th limit
P3 2.0 Files 4-164
BYTE
WORD DESCRIPTION
173-176 44
Shift number (1-6) (INT*2)

(If no shift table, value is 1)
Shift limit table (INT*2)
0 = No
1 = Yes
177-180 45
Driving resource (INT*2)

0 = No
1 = Yes
Page size = 1024 bytes [unused bytes per page = 1024 6 (180 * 5) = 118 bytes
P3 2.0 Files 4-165
XXXXITM.P3: Data in Dictionary Records

Key: CHAR*33 (ND-M)
Note: The structure of information described is repeated up to 8 custom data items.
BYTE
WORD DESCRIPTION
1-32
1-8
32 asterisks (CHAR*32)
33
A = Activity custom data item

R = Resource/cost custom data item
34-36
Not used
37-40
Field name (CHAR*4)
41
Field type (CHAR*1)

'C' = Character field
'S, 'F' = Start/finish date field
'N' = Numeric (0 decimals)
'P' = Precision (2 decimals)
42
Field length (CHAR*1)

CHAR(1) through CHAR(20)
43-58
Data item description (CHAR*16)
59-??
Bytes 37-58 are repeated for up to 8 custom data items

Maximum record = 212 bytes
P3 2.0 Files 4-166
XXXXITM.P3: Data in Data Item Value Records

Key: CHAR*33 (ND-M)
BYTE
WORD DESCRIPTION
1-10
1-3
13-20
4-5
Resource for resource items

OR
8 asterisks for activity items (CHAR*8)
21-32
6-8
Cost account for resource items

OR
12 asterisks for activity items (CHAR*12)
33
Resource ID for resource items

OR
1 asterisk for activity items (CHAR*1)
37-??
10-??
When extracting custom data item values, remember that all Character field values
occupy as much space as their defined length (rounded up to the nearest word
boundary), and all other types (Date/Numeric/Precision) occupy 4 bytes each.

Maximum record = 196 bytes
P3 2.0 Files 4-167
XXXXSTR.P3
Key 1: CHAR*4 (D-M)
Bytes 1-4
Key 2: CHAR*4 (D-M)
Bytes 9-12
Segment 1:Byte 1
Segment 2:Bytes 9-56
BYTE
DESCRIPTION
Indicator (CHAR*1) 'W' for WBS records.
Unused
3-4
Level number (INT*2)
5-8
Unused
9-56
Code value (CHAR*48)
57-104
Code title (CHAR*48)
Physical record size = (104) + (8*2 keys allow duplicates) = 120 bytes
P3 2.0 Files 4-168
XXXXHOL.P3
Segment 1:Bytes 1-2
Segment 2:Bytes 3-6
Segment 3:Bytes 7-10
BYTE
WORD DESCRIPTION
1-12
1-3
Calendar ID (INT*2)
1-31 = Calendar holidays
32 = Global holidays
101-131 = Calendar exceptions
132 = Global exceptions
Start of Holiday (INT*4)(bytes 3-6)
End of Holiday (INT*4)(bytes 7-10)
Notes:
1. Annual holidays (04JUL) have 1970 for their year.
2. Full day holidays have 99 in the QQ portion of the start holiday date, regardless of planning unit.
3. For hourly projects, generic nonworkhours (12:00) have 01JAN72 in the date portion.
Physical record size = (2*4) + 2 + (8*0 keys allow duplicates) = 10 bytes
P3 2.0 Files 4-169
XXXXCAL.P3
BYTE
DESCRIPTION
1-4
NCALS: Number of calendars defined (INT*4)
5-128
KALEN(31): Relates calendar ID to consecutive calendar number starting at 1(INT*4)

CAL.ID = 1 (1)KALEN(1)=1
CAL.ID = 5 (5)KALEN(2)=5
CAL.ID = C (12)KALEN(3)=12
129-8048
KALS(1980): Bit pattern of work (0) and nonwork (1)periods (INT*4)
8049-12008
KALCUM(1980): Each element corresponds to KALS(1980)12008 to give the work

period associated with each unit of time; values are offset by 32767 (INT*2)
12009-12136
KALBAK(32): Relates the consecutive calendar number to the actual calendar ID

(INT*4)
KALEN(1) = 1 KALBAK(1) = 1
KALEN(2) = 5 KALBAK(5) = 2
KALEN(3) = 12 KALBAK(12) = 3
12137-12198
CALTYP(31): Array containing planning unit for calendars that are defined. Calendars
that are not defined contain 0 (INT*2)
12199-12202
KALSTR: Start of generated calendar in YYYYMMDDQQ format (INT*4)
12203-12206
5.0 KALFIN: End of generated calendar in YYYYMMDQQ format (INT*4)
12207-12210
5.0 NDATES: Number of planning units for project NDATES = (1980*32)/NCALS

(INT*4)
12211-12214
5.0 NDIM: Dimension of KAL and KALCUM arrays (1980)(INT*4)
12215-12218
NHOLS: Number of holidays defined (INT*4)
12219-12222
MCL4: Planning unit of project (INT*4)
P3 2.0 Files 4-170
BYTE
DESCRIPTION
12223-12226
ADFIN: End of generated calendar in absolute time (INT*4)
12227-12230
ADST: Start of generated calendar in absolute time (INT*4)
12231-12234
DURSFT: Duration of shifts in quarter hours (INT*4)
12235-12238
NSHFT: Number of shifts per day (0-6) (INT*4)
12239-12242
TFSHFT: Time of the first shift of the day in quarter hours (INT*4)
12243-12246
ISDOFW: Start day of the week (1 = MON, 2 = TUE,...7 = SUN) (INT*4)
12247-12250
5.1 KALFIN: End of generated calendar in YYYYMMDDQQ format (INT*4
12251-12254
5.1 NDATES: Number of planning units for project (INT*4)
12255-12258
5.1 NDIM: Dimension of KAL and KALCUM arrays (16000) (INT*4)
12259-12262
5.1 ADFIN: End of generated calendar in absolute time (INT*4)
12263-?????
5.1 extra data for KALS & KALCUM

The amount of this data is given by:
((5.1 NDATES) 32 (5.0 NDATES) 32)* NCALS * 6)
The data is stored for each calendar in turn, alternating elements of KALS and KALCUM
P3 2.0 Files 4-171
XXXXSRT.P3
Key 1: INT*4 (ND-M)
BYTE
WORD DESCRIPTION
1-4
5-16
2-4

P3 2.0 Files 4-172
XXXXREP.P3 / XXXXPLT.P3
Key 1: CHAR*6 (ND-M) in bytes 1-6
Key 2: CHAR*1 (D-M) in byte 7
BYTE
DESCRIPTION
1-2
Report/plot type (CHAR*2)

RU = Res. profile
CU = Cost profile
RR = Res. cumulative
CR = Cost cumulative
RC = Res. control
CC = Cost control
RP = Res. productivity
CP = Cost productivity
RE = Res. earned value
CE = Cost earned value
RT = Res. tabular usage
CT = Cost tabular usage
RL = Res. loading
CL = Cost loading
RM = Res. matrix
AM = Activity matrix
EX = Export
IM = Import
SC = Scheduling
NL = Network logic
TD = Tabular data entry
RW = Report writer
Plot Types:
TL = Timescale logic
BC = Bar chart
3-4
Report Number (CHAR*2)

01-99
CHAR(1) - CHAR(255)
PL = Pure logic
P3 2.0 Files 4-173
BYTE
DESCRIPTION
Report Card Designation

(CHAR*1)
CHAR(1) = REPORT
CHAR(70) = RSLD
CHAR(145) = GRP
CHAR(5) = SELE
CHAR(75) = PEN
CHAR(150) = RSEL
CHAR(10) = SORT
CHAR(76) = PEN1
CHAR(160) = VBAR
CHAR(15) = SUMM
CHAR(80) = MASK
CHAR(162) = SCHD
CHAR(20) = RESP
CHAR(85) = TDEC
CHAR(166) = ADD
CHAR(25) = TMSC
CHAR(90) = SKIP
CHAR(170) = VUSG
CHAR(30) = TSCA
CHAR(95) = BAND
CHAR(171) = IF
CHAR(35) = BARC
CHAR(98) = SUMM
CHAR(172) = THEN
CHAR(36) = DATM
CHAR(100) = RESL
CHAR(173) = ELSE
CHAR(37) = DATA
CHAR(105) = RESO
CHAR(175) = RPWT
CHAR(40) = NLOG
CHAR(110) = RACR
CHAR(180) = MATX
CHAR(41) = WRIT
CHAR(115) = RDAT
CHAR(181) = MTXT
CHAR(45) = PPDM
CHAR(120) = PROF
CHAR(185) = AMTX
CHAR(46) = PADM
CHAR(125) = LABL
CHAR(186) = RMTX
CHAR(50) = LOUT
CHAR(130) = CUMM
CHAR(247) = (Not Used)
CHAR(55) = SPEC
CHAR(135) = RPEN
CHAR(248) = SRT1
CHAR(60) = IMPO
CHAR(136) = RPN1
CHAR(249) = SRT2
CHAR(61) = HEAD
CHAR(140) = USAG
CHAR(250) = SRT3
CHAR(65) = DATE
CHAR(144) = LEVL
P3 2.0 Files 4-174
BYTE
DESCRIPTION
CHAR(1) = first record

CHAR(2-99) = following
records
Report Series Letter

(CHAR*1)
A-Z
8-120
Report Card Data
P3 2.0 Files 4-175
XXXXAC2.P3
Key: CHAR*12 (ND-M)
BYTE
WORD DESCRIPTION
1-4
Project Name (CHAR*4) ('
5-12
2-3
Username (CHAR*8)
13-16
Access level (INT*2)

1 = read only; 2 = read write; 3 = exclusive read write;
4 = exclusive read only
' = Project Group name)
Project Owner (INT*2)

0 = not a project owner; 1 = project owner
17-20
Restricted access report series ID (CHAR*2)
21-24
Restricted access bit flags (INT*4)
25-32
7-8
Not used

P3 2.0 Files 4-176
USERS50.P3
Key: CHAR*20 (ND-M)
BYTE
WORD DESCRIPTION
1-4
Project Group Name (CHAR*4)
5-8
Project Name (CHAR*4)
9-16
3-4
Username (CHAR*8)
17-20
Reserved
21-24
Access Level (INT*2)

1 = Read only
2 = Read write
3 = Exclusive read write
4 = Exclusive read only
Project Owner (INT*2)
0 = not project owner
1 = project owner
25-32
7-8
SureTrak

P3 2.0 Files 4-177
XXXXLAY.P3
Segment 1:Bytes 1-2
Segment 2:Bytes 3-4
Segment 3:Bytes 5-6
BYTE
DESCRIPTION
1-2
Layout ID (CHAR*2)
3-4
Record type (INT*2)

0 = Bar info (colors)
1 = Screen colors
2 = Date format
3 = Default font
4 = Endpoints
5 = Filter specification
6 = Font info
7 = Graphic info (bars)
8 = Bar label info
9 = Tabular/graphic info
10 = Grouping
11 = View information
12 = Outliner
13 = Page breaks
14 = Print options (general)
P3 2.0 Files 4-178
BYTE
DESCRIPTION
15 = Print options (tabular/graphics)
16 = Print titles
17 = Resource/cost graphic info
18 = Row heights
19 = Scroll bar positions
20 = Selection
21 = Splitter positions
22 = Tabular info (columns)
23 = Timescale info
24 = Layout title
25 = Semaphore for writing to layout file
26 = Items added for 1.1
5-6
7-250
Layout record data
P3 2.0 Files 4-179
XXXXSTW.P3
P3 and SureTrak use this file to store and communicate information when using a
SureTrak project in P3 or when using a P3 project in SureTrak.
Project configuration information
Single default layout (STW)
Layout pointer (last layout used)
Activity priorities
Filters
SureTrak Resource dictionary information not supported by P3:

revenue
driving flags (stored elsewhere in P3)
leveling flags
base calendar (stored elsewhere in P3)
resource limits by project within a project group
Resource calendar information
Holidays for resource calendars
SureTrak target dates
Outline codes for project groups and member projects
SureTrak reports
Default activity codes
P3 2.0 Files 4-180
P3.INI Options
The P3.INI file, located in the Windows directory, contains information about how P3 is
configured. P3 uses the information in this file when you load P3 so that it starts with your
preferred settings. Generally you do not need to change this file, since P3 makes the
changes for you as you use P3. You can, however, change the file using a text editor
such as Notepad. To include remarks in the P3.INI file, begin each line of the remark with
a semicolon (;). Before you make changes, you should always back up the P3.INI file.
This chapter describes the contents of the P3.INI file, including optional settings that are
not automatically written to the file by P3.
Organization of the file P3.INI is organized by section. Each section name is enclosed
in brackets. For example, the section that controls the directories that P3 uses for
program files, projects, and other program elements appears as [Directories]. Each line
below the section name represents a setting related to the sections title. Each setting
contains the name of the setting, followed by an equals sign and the specific value for the
setting.
Most setting are added to the P3.INI file during Setup; other settings are optional. If you
have used P3 since it was first installed, your P3.INI file may be slightly different then
those settings listed in this section; it now contains any configuration options you set up
while using P3.
P3 2.0 Files 4-181
[Directories]
[International]
Setting
Comments
Progloc = N:\P3WIN\P3PROGS
Location of Read Only program files
Workloc = N:\P3WIN\P3WORK
Location of Read/Write program files
Userloc = C:\P3WIN\P3OUT
Location of user-created & configuration files
Proj = C:\P3WIN\PROJECTS
Default project directory
Prmzloc = N:\P3WIN\P3WORK\PRMZFIL.P3
Location of PRMZFIL.P3/FH file
UserfilLoc = N:\P3WIN\USERFIL.P3
Location of USERFIL.P3/FH file
BatchProjLoc = C:\P3WIN\PROJECTS
Default project directory for Batch
BatchLoc = C:\P3WIN\P3OUT
Default directory for Batch input file
BackupRestoreDir = A:\
Default Backup/Restore directory
Setting
Comments
Dictionary = C:\P3WIN\P3WORK\P3DICT.DAT Variable points to the directory where the

P3DICT.DAT file is stored. This file lists all the
possible languages that a P3WIN Layout can use
(without installing a special version of Windows with
foreign language support.)
Language = 0x0409
The variable stores the last language setting used in

P3.
ForceNumericDateFormat = 0
Set the variable to 0 to show all dates in this format:

JAN/31/94 or 31/JAN/94
Set the variable to 1 to show strictly numeric dates: 01/
31/94 or 31/01/94
This option controls which formats are available in the
Date Format dialog box.
P3 2.0 Files 4-182
[ReportSmith]
Setting
Comments
Message = 1
A setting of 1 indicates that P3 has not started

ReportSmith yet; P3 issues a warning message
concerning not changing directories.
A setting of 0 indicates that P3 has already started
ReportSmith, and will not issue a warning message.
[Calendar Options]
[Display]
Setting
Comments
NonWorkperiodText =
RGB value (color) for nonworkperiod text
NonWorkperiodBkgd =
RGB value (color) for nonworkperiod background
MonthlyIncrement =
# of months each click of the double-arrow buttons (on

the vertical slide bar of the calendar) will move the
calendar ahead or back for monthly calendars
Setting
Comments
Maximize = 1
Not Used
WindowPos = 0,1,-1,-1,-1,-1,80,80,794,545
Exact coordinates for size of the screen.
If the first 2 numbers are 2,3 then P3 starts in full If the display is moved off the screen, delete this
screen mode.
section and it will be regenerated automatically upon
starting P3.
If the first 2 numbers are 0,1 then P3 starts in
minimized mode.
The remaining numbers give the position and
size of the minimized screen, and are saved
each time you exit P3.
P3 2.0 Files 4-183
[Display]
Setting
Comments
File1 = C:\P3WIN\PROJECTS\APEX
The list of the last four projects opened, as seen in the

file menu.
File2 = C:\P3WIN\PROJECTS\ENGR
File2 = C:\P3WIN\PROJECTS\ENGR
File3 = C:\P3WIN\PROJECTS\CLIN
File4 = C:\P3WIN\PROJECTS\SWDV
DataDateWidth = X
Thickness of the data date line, expressed in points.
StripLeadingBlanks = 0
A setting of 0 (default) preserves leading blanks, so

that purely numeric activity IDs are right-justified
A setting of 1 removes leading blanks. Purely numeric
activity IDs are left-justified, but note that positionsensitive
Activity IDs such as A or A will both be leftjustified to A.
Unassigned =
Set the variable to the text you want to display in the

grouping band for activities having no assigned value
for cost account, cost category, or resource when
grouping by cost account, cost category, or resource.
By default (that is, if you omit this variable from the
Display section) the banding text for the group will
read UNASSIGNED.
Uncategorized =
Set the variable to the text you want to display in the

grouping band for activities having no assigned activity
code or activity ID code when grouping by activity
codes or activity ID codes. By default (that is, if you
omit this variable from the Display section) the
banding text for the group will be blank.
P3 2.0 Files 4-184
[Toolbar]
Setting
Comments
ToolTop = 21,20,22,57,
Initial toolbar icons (New, Open, Help, Tutorial)
ToolTab =
Toolbar icons displayed in Bar View
21,20,72,73,74,37,42,58,59,60,25,74,39,67,68,
52,53,35,74,27,33,32,74,36,49,45,74,71,26,44,
74,41,70,65,74,22,57,
ToolPng =
Toolbar icons displayed in PERT
21,20,86,37,74,76,77,74,58,59,60,74,29,30,118
,81,74,46,47,40,63,117,74,119,61,49,74,35,70,
65,74,80,79,75,121,74,22,
[Options]
ShowToolTips =
1 = Show bubble help when mouse pointer rests on

toolbar icons
0 = Do not show bubble help when mouse pointer
rests on toolbar icons
ColorIcons =
1 = display toolbar icons in color

0 = display toolbar icons in grayscale
LargeIcons =
1 = large icons
0 = small icons
Setting
Comments
LineSeparator= <character>
Changes the line separator used in the Columns

dialog box to a character other than the pipe symbol
(|). International users can use this switch if their
keyboards do not have the pipe symbol.
CreateSrtWithFlt = 1
Creates an SRT file every time P3 executes a filter.

The SRT file is used in Batch (Generate From Sort)
and Monte Carlo.
P3 2.0 Files 4-185
[Options]
Setting
Comments
CopyExternalRels = 1
When copying activities to the Clipboard, a setting of 1

copies all relationships involving the selected activities. In the Paste dialog, the checkbox labeled Paste
external relationships? is only enabled if this option is
set to 1 in P3.INI.
PhysicalReadOnly = 0
The default setting is 0; set the variable to 1 to support

Read Only project directories.
ExclForActIDEdit = 0
A setting of 0 allows editing of activity IDs without

exclusive access. When set to 1, a user must have
exclusive access to edit IDs.
Debug = 0
If set to 1, debugging code is activated and sent to

DBWIN. Use only when requested by Technical
Support staff.
UnlinkAllRels = 0
0 = unlink only finish to start relationships in the

selected group.
1 = unlink all internal relationships in the selected
group.
AutoAdd = 1
Setting found in the Activity Inserting Options dialog

box.
1 = automatically numbers activities
0 = do not automatically number
AutoIncrement = #

box.
# is the number by which you want to automatically
increment activities.
AddWithForm = 0

box regarding the presence of the Activity Form while
adding activities.
0 = activity form does not appear
1 = activity form appears
P3 2.0 Files 4-186
[Options]
[Curves]
Setting
Comments
NoBorderInPatternLegend = 1
Default setting is 1 (no border drawn around the

pattern legend section of the legend).
Set the option to 0 to have P3 draw a border.
UsePolyPolygon = 1
Use this setting only if the borders of some polygons

(such as necked bars, endpoints, and PERT activity
end shapes) sporadically fail to appear when the
screen redraws. This can occur with some graphics
cards; this setting should alleviate the problem.
Setting
Comments
1=Linear,0,10,10,10,10,10,10,10,10,10,10,
Default resource curves. Users can define up to 99

template curves and use the Template function in the
Resource dictionary to list any 16 of them as the
currently available curves.
2=Triangular,0,2,6,10,14,18,18,14,10,6,2,
triangular Increase,0,2,3,6,7,9,11,13,14,17,18
triangular Decrease,0,18,17,14,13,11,9,7,6,3,2,
5=Back Loaded,0,7,7,7,7,7,13,13,13,13,13,
6=Front Loaded,0,13,13,13,13,13,7,7,7,7,7,
7=Trapezoidal,0,2,7,11,15,15,15,15,11,7,2,
8=Bell Shape,0,1,3,8,15,23,23,15,8,3,1,
9=Three Step,0,8,8,8,13,13,13,13,8,8,8,
P3 2.0 Files 4-187
[Applications]
Setting
Comments
App1 = Monte Carlo
This section enables the launching of up to 5 applications from the Tools menu.
App2 = MS Write
App# specifies the wording of the menu item on the

Tools menu. The number is underlined in the menu,
and functions as a hotkey for starting the application.
App3 = Paintbrush
App4 = SureTrak for Windows
App5 = CC:Mail
Cmd1 = c:\mcwin\mcprogs\mc.exe /u:$user /
d:$projdir /p:$proj /s:$serial
Cmd# specifies the command P3 executes when the

item is selected. Applications can be DOS- or
Windows-based executables, or batch files.
Cmd2 = c:\windows\write.exe
Cmd3 = c:\windows\pbrush.exe
c:\windows\argyle.bmp
Cmd4 = c:\stwin\stw.exe
Cmd5 = read.bat
[Layouts]
Setting
Comments
ItemA = C:\P3WIN\PROJECTS\APEX
P3WIN keeps track of the last 25 layouts opened for

each project. If a project isnt listed, P3 opens it using
the first layout.
C:\P3WIN\PROJECTS\APEX = 01,A[]
You can delete this section and P3 will regenerate it.
LRU = ABC
Item<letter> = path to project and project name
ItemB = C:\P3WIN\PROJECTS\CLIN
Project = <layout number>, Letter assignment (in

alphabetical order)
P3 2.0 Files 4-188
[Layouts]
Setting
Comments
C:\P3WIN\PROJECTS\CLIN = 01,B[]
LRU = all the letters that have been used by subsequent entries
ItemC = C:\P3WIN\PROJECTS\ENGR
[] = set of brackets required in each entry
C:\P3WIN\PROJECTS\ENGR = 01,C[]
[Currentscheme]
Setting
Comments
Name = P3 Defaults
This and the following sections store color settings for
Columns = 0,56
default and user-defined color schemes. You can
Column Titles = 0, 44
define up to 25 color schemes interactively using the
Timescale = 0, 44
Colors dialog box.
Bars background/text = 0, 56
Highlight color = 31006, 4
Normal usage = 1
Above normal usage = 6
Above maximum usage = 3
Current
Current estimate curve = 9
Earned value curve = 2
Scheduled budget curve = 11
Pure logic = 56
Data Date = 2
P3 2.0 Files 4-189
[Colorscheme1]
Setting
Comments
Name = Pale Blue Header

Columns = 0,56
Column Titles = 0, 44
Timescale = 0, 44
Bars background/text = 0, 56
Highlight color = 31006, 4
Normal usage = 1
Above normal usage = 6
Above maximum usage = 3
Current estimate curve = 9
Earned value curve = 2
Scheduled budget curve = 11
Pure logic = 56
Data Date = 2
[Mail Options]
Setting
Comments
AddressSubstitution = 0/1
If this variable is set to 1 and automatic addressing is

used, if P3 cannot send mail to the address found in
the description of the data item, it looks for an
alternate address in the [Mail Addresses] section of
P3.INI.
P3 2.0 Files 4-190
[Mail Options]
Setting
Comments
Server =
Options are MAPI, VIM, or NOTES. If you have

multiple mail systems installed and want to force P3 to
choose one other than the system's default, specify it
here.
MultRecipItem =
Last code used for addressing. P3 sets it to an activity

code value or the values Resource, Cost Account
(11) or Cost Account (12).
Relationships = 0/1
Set to 1 to send relationships during a custom Send

operation.
LastSent =
This variable stores a value identifying all the items

that were sent in the last mail message. Each item has
a numeric value, and this calculated variable is the
sum of all those values.
ActivityEditKey = 0110110
Each digit of this variable refers to an activity data item

that is sent: 0 for non-editable, 1 for editable
ResourceEditKey = 0110110
Each digit of this variable refers to a resource data

item that is sent: 0 for non-editable, 1 for editable
StatusSheetType = 0
0 = custom status sheet

1 = standard sheet using RD
17 = standard sheet using PCT
InboxMessageLimit = 150
Specify the maximum number of most-recent

messages to display.
ShowSendTargetMsg = 1
1 = issue a message reminding the sender to also

send the target project if one exists
0 = do not issue a message
P3 2.0 Files 4-191
[Mail Addresses]
[Mail Act Fields]
Setting
Comments
MD = Demuth, Meg
Specify an alias address if the complete mail address

is longer than 36 characters or if you dont want to see
the actual E-mail address as a title in P3.
Setting
Comments
<All activity data items being sent will appear

here>
[Mail Res Fields]
Setting
Comments
<All resource data items being sent will appear

here>
[Exclusive]
Setting
Comments
C:\P3WIN\PROJECTS\APEX = #
# = 0 or 1
1 opens project in Exclusive mode;
0 opens project in non-exclusive mode.
This option is saved for each project when you close it.
P3 2.0 Files 4-192
[Btrieve]
Setting
Comments
patch110 = 1
Patch related to running OEM2ANSI automatically in

ReportSmith.
1 = Don't run OEM2ANSI (use if working with a P3 for
Windows project)
0 = Run OEM2ANSI (use if working with a P3 for DOS
project)
This option and path only are relevant if the project
uses characters in the extended ASCII character set
(above 126).
[PrintOpts]
Debug =
If set to 1, all Btrieve operations in Batch and P3.EXE

are dumped to DBWIN. Set this option only if
requested by Primavera technical support personnel.
Version =
Specifies the minimum version of Btrieve required to

run P3. Default is 6.
RetryCount =
Specifies the number of retries to attempt when a

Btrieve call fails. This is only done on status codes that
warrant a retry.
ConvertToUNC = 1
1 = convert filenames to Universal Naming Convention

format before passing to Btrieve
0 = turn off automatic conversion
Setting
Comments
PrintCalFontIndex = 1
Must be set to 1.
NoSkipMoveShiftText = #
# is a number that is the sum of any or all the numbers

1, 2, 4, and 8. The options corresponding to these
numbers are described below. If you choose to use
none of these options, do not include the NoSkipMoveShiftText setting at all.
P3 2.0 Files 4-193
[PrintOpts]
Setting
Comments
Options A through D allow the user to simulate the
behavior of P3 version 1.1 regarding the placement of
text around activity bars when the bars or their text
were truncated by, or totally outside, the borders of the
printed area defined by the timescale specified for
printed output.
Option A: Normally, P3 2.0 will not display text that is

positioned to the left or the right of a bar if the left or
right edge of the bar is not at least partially visible
within the printed timeframe. You can force P3 to print
the text even if the bar is not visible by adding 1 to the
value of #.
Option B: Normally, if the left or right edge of the

printed timeframe truncates part of the text on one side
of a bar, P3 2.0 automatically moves the text to the
opposite side of the bar, assuming there is no other
text already there. You can suppress this automatic
feature by adding 2 to the value of #.
Option C: Normally, if the left or right edge of the

timeframe being printed truncates part of the text on
one side of a bar, P3 2.0 automatically moves the text
to the opposite side of the bar and appends it
(following a separator character) to any other text
already on the other side. You can suppress this
automatic feature by adding 4 to the value of #.
P3 2.0 Files 4-194
[PrintOpts]
Setting
Comments
Option D: Normally, if text in the top-left, top, top-right,
bottom-left, bottom, or bottom-right positions would be
truncated by the beginning or end of the timescale, P3
automatically shifts the text to the left or right so that it
all appears. You can suppress this automatic feature
by adding 8 to the value of #.
[Extension]
[Performance]
[PrintSetup]
Setting
Comments
EXT = P3
Default project extension.
BatchExt = P3
Default project extension for Batch.
Setting
Comments
RCG Maximum Groups = 24
Number of groups cached in memory for resource/cost

tables and profiles. Default is 24.
RCG Background Spread = 0
0 = Process resource/cost spread in the background

so you can continue to work in the Bar view without
delay.
1 = Don't process in background; draw results before
proceeding.
TabularGraphicsRowCache Size=200
Number of activities to read into cache. Default is 200.
Setting
Comments
GrayscaleMapping = 0
0 = Use colors (for Print Preview).

1 = Use grayscale mapping.
P3 2.0 Files 4-195
[StartUp]
[Debug]
[Special Printers]
Setting
Comments
LastError = 0
0 = Startup detected no errors.
Setting
Comments
RCG Level =
Options for use by technical support
DumpColumnInfo =
personnel while troubleshooting.
Setting
Comments
SYMPTOMS AND CODES ARE LISTED

BELOW:
This section is only used in resolving problems with

unusual print devices. The term <printer name> refers
to the name of the printer displayed in the Print Setup
dialog box. If a problem exists on multiple printers, use
the name All Printers as the <printer name>. If
several of the described problems occur, add the
values specified for each problem and use the total as
the variable value.
<printer name> = 128
When using a color printer, diagonal lines are drawn in

a vertical curtain.
Text improperly positioned in the center of the Activity

columns section of the layout.
Prevents pen plotters from drawing relationship lines

through activity boxes in PERT view.
<printer name> = 1
Prints nondriving relationship lines as dashes instead

of dots.
P3 2.0 Files 4-196
[Special Printers]
[Splash]
[BackupRestoreOptions]
Setting
Comments
Width Offset = 3
Use if characters are dropped or repeated between

horizontal pages of graphics output. Valid values are
1-6; try different values until the best one is found.
Height Adjust = 1
Adjusts height of PRMTEXT. Use positive or negative

values (in pixels) to increase or decrease the current
height of Primavera Text objects if the text is being
clipped during printing.
Setting
Comments
SHOW = 1
0 = Don't display splash screen while loading P3.

1 = Display splash screen while loading P3.
Setting
Comments
Specifications = 1
1 = Restore report and plot specifications when

restoring a backup.
0 = Don't restore report and plot specifications when
restoring a backup.
SubprojectRelations = 1
1 = Restore relationships (within the project group)

that are external to the project.
0 = Do not restore relationships (within the project
group) that are external to the project.
MergeSubdirectories = 1
1 = Copy new values added to project dictionaries to

their project group dictionaries.
0 = Disregard new values.
Compressed = 1
1 = Compressed backups.
0 = Uncompressed backups.
P3 2.0 Files 4-197
[BackupRestoreOptions]
[FindObjects]
[Graphics]
[Executables]
Setting
Comments
RemoveAccessList = 1
1 = Remove access list when backing up.

0 = Don't remove access list when backing up.
UseOldCompression = 1
1 = Use ARC compression to back up projects. Use

this option to be compatible with P3 version 1.1 and
P3 for DOS. Default setting is 0 or blank.
Setting
Comments
List Type = 0
Saves the last switch setting from the Find Objects

dialog box. Values are:
0 = Both
1 = Attached
2 = Unattached
Setting
Comments
Max Objects = 600
Specify the maximum number of graphics objects to

read into memory when opening a layout. If you
cannot open a layout that contains a large number of
attached objects, increasing this setting may resolve
the problem.
Setting
Comments
PrmBatchEXE = C:\P3WIN\PRMBATCH.EXE
In some circumstances, when running P3 across a

network you can increase speed by storing and
loading certain program files from your local hard drive
rather than loading them across the network.
P3 2.0 Files 4-198
[Executables]
[Windows Help]
Setting
Comments
P3BtrvEXE = C:\P3WIN\P3BTRV.EXE
This option specifies the location of certain P3

executable files. In addition, the P3.EXE file can be
copied locally, but it need not be mentioned in this
section; instead, point the P3 icon to the local
directory. Also, include the local directory where you
are storing these P3 executables as the first item in
your path statement.
ASortWinDLL = C:\P3WIN\ASORTWIN.DLL
Note: you can copy the entire PROGLOC directory to

your local drive, or use this feature to obtain speed
benefits without using the disk space to store the
entire directory. If you are running the BTRIEVE NLM
(network loadable module), the *.BIN files from the
PROGLOC directory must reside on the server rather
than the local drive.
Setting
Comments
JumpColor = 0 128 0
(default) green
JumpColor = 0 0 128
blue
JumpColor = 128 0 0
red
The JumpColor setting defines the display color of
jumps (words that automatically display other help
information when you click them) in P3 help. The
argument to this parameter is the RGB value of the
desired color. You can design your own colors by
choosing any value between 0 and 128 for the red,
green, and blue components of the jump color. Three
possibilities are shown above.
P3 2.0 Files 4-199
[Batch]
[AdvancedSchedule
LevelOptions]
Setting
Comments
ProduceRTF = 1
A setting of 1 produces all report output using RTF

(rather than ANSI) text, even if none of the requested
report specifications call for RTF.
Setting
Comments
LevelDump = 1
Set the value to 1 to include resource usage per

timeperiod in the leveling output report for resources
being split/stretched/crunched.
StatDump = 1
Set the value to 1 to write leveling data to a file, in

ASCII format.
StatDumpFileName =
Specifies the StatDump filename (stored in the

USERLOC) directory.
ShowWorkPeriods = 1
Set the value to 1 to include workperiod numbers in

the dump file.
Note: Use of these data dumps slows the leveling
process dramatically, and can generate very large
files. These options are intended only for troubleshooting.
4-201
SureTrak 2.0 Files

In this chapter:
SureTrak File
(XXXXSTW.P3)
Webster Timesheet File
(XXXXTIM.P3)
STWIN.INI File Settings
In Concentric Project Management, SureTrak and P3 share

data files that use the .P3 filename extension. Refer to the P3
2.0 Files chapter for a complete file structure and data table
listing.
When using P3 and SureTrak together, P3 creates an
additional file that stores data specific to SureTrak. This file,
XXXXSTW.P3 (where XXXX represents the project name), is
located in your SureTrak projects directory.
Webster for Primavera stores the nonproject time of personnel
resources in the file XXXXTIM.P3, where XXXX represents the
P3 or SureTrak project name.
This chapter also lists the contents of the STWIN.INI file.
SureTrak 2.0 Files 4-202
SureTrak File (XXXXSTW.P3)

The XXXXSTW.P3 file stores the following information:
Project configuration information
Single default layout (STW)
Layout pointer (last layout used)
Activity priorities
Filters
Resource calendars and holidays (used by P3 also)
Resource Dictionary information not supported by P3

- revenue
- leveling flags
Outline codes for project groups and member projects
SureTrak reports
Default activity codes
Manual page breaks
State of collapsed activity group bands
Webster Timesheet File (XXXXTIM.P3)

The Webster Administrator can authorize Webster users to record nonproject time, such
as vacations, holidays, or sick time, using Webster for Primaveras Hours view. Webster
stores this nonproject data in the XXXXTIM.P3 (where XXXX represents your projects
name) file. Webster stores time use one week per record using the following data
structure.
Y/N
Length
Starting
position
Ending
position
Data
type
Comments
acResID
char
The resource ID
actid
10
18
char
The activity ID
CostAcct
12
19
30
char
The cost account
desig
31
31
char
The resource designator
timeTypeCode
32
33
char
First 2 characters of activity ID
weekStartDate
34
37
date
Start date (in P3 date format)
day1
38
39
uint
Time field 1
day2
40
41
uint
Time field 2
day3
42
43
uint
Time field 3
day4
44
45
uint
Time field 4
day5
46
47
uint
Time field 5
day6
48
49
uint
Time field 6
day7
50
51
uint
Time field 7
decflag
52
53
uint
Decimal flag
(1 = fixed point, 0 = integer)
Field name
STWIN.INI File Settings

The STWIN.INI file contains information about how you want SureTrak to work. SureTrak
uses the information in this file when you start SureTrak, so that it uses your preferences.
The STWIN.INI file is located in your \WINDOWS directory. You can use a text editor,
such as Notepad, to make changes to this file. However, you can specify nearly all your
preferences from within SureTrak, since most settings in this file reflect your most recent
choices in various dialog boxes. If you make changes directly to the STWIN.INI file, back
up the file first.
Like all .INI files, the STWIN.INI file contains several sections, each beginning with a
section name enclosed in brackets. For example, the section that controls which directories SureTrak uses for layouts, projects, clip art, and other program elements is [Directories]. Each line below the section name represents a setting related to that section.
Each setting consists of a name followed by an equal sign and a value, for example:
[Directories]
Layouts = C:\STWIN\LAYOUTS
When the setting options are 0 or 1, 0 means No and 1 means Yes. To include a remark
in the STWIN.INI file, type each line of the remark on a line beginning with a semicolon (;).
The rest of this section lists the STWIN.INI setting options by section. If you have used
SureTrak since it was first installed, your STWIN.INI file may have different settings from
those listed in this section because SureTrak updates the file to match the configuration
options you set.
[Endpoints]
This section enables you to add more symbols and endpoint choices to SureTrak. You
can see and select these additional choices in the Style columns in the Bars dialog box
and in the Bars and Endpoint Options dialog box (choose Format, Bars, then click
Options). The default STWIN.INI contains the following endpoint settings:
Setting
Comments
1 = POLYGON, Right Triangle, 100, 1, 1, 3,

0,0, 100,50, 0,100
Adds one symbol to the endpoint list: a

triangle that points right
2= POLYGON, Left Triangle, 0, 1, 1, 3,

0,50, 100,0, 100,100
Adds one symbol to the endpoint list: a

triangle that points left
5 = FONT, Wingdings, 50, 1, 0,

0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF,
0xFFFFFFFF, Wingdings, Regular
Adds all of the Wingding font characters to

the endpoint list
6 = FONT,Symbol, 50, 1, 0,
0xFFFFFFFF, Symbol, Regular
Adds all of the Symbol font characters to

the endpoint list
To add characters from a particular font to the list of available endpoints, add an entry to
STWIN.INI. The following example adds the numeric characters from the ZapfDingbats
font, making them available in the drop-down list as endpoints.
9 = FONT, Dingbats, 50, 1, 0, 0x0, 0x0, 0x0, 0x0, 0xFFFFF, 0xFFFFF000, 0x0, ZapfDingbats,
Bold
The elements of the statement correspond to a numeric ID = FONT; font name; centerpoint on vertical axis between 0 and 100; a number indicating in which bar chart elements
the font is available (1 for endpoints, 2 for bars, 3 for both); a number indicating whether
the font should be outlined (0 for no outline, 1 for an outline); seven hexadecimal numbers
separated by commas, each of whose binary equivalent represents one row of the
Windows Character Map; the name of the Windows font; and the style of the font.
A standard Windows accessory program, Character Map, displays all the characters of
any font on a grid, 32 characters across and 7 characters down. Specify which characters
of a font you want to use by converting each row of the grid to a binary number, and
making note of the numbers hexadecimal equivalent. This is simple to do using the
Windows Calculator.
1 Open the Windows Calculator, then choose View, Scientific.
2 Choose Bin for Binary, and DWord.
3 Open the Windows Character Map and position it so you can view both the Calculator
and Character Map simultaneously.
In the font field, select the font with the character(s) you want to use.
4 Starting on the top row, right corner of the Character Map grid and reading across the
entire first row from right to left, type a 1 in the calculator for each character that you
want to make available, and type a 0 for each character you do not want to make
available. You cannot input leading zeros; this is not a problem, since the calculation
begins with the first 1. Be sure to type enough 1s or 0s after the first 1 to account for
all remaining symbols on the row.
5 Select Hex to convert the binary number into hexadecimal form. Note the resulting
number for this row. Repeat the process for each row of the Character Map grid. Use
each resulting Hex value, in order, in the endpoint statement.
To add rectangles to the bar and/or endpoint choices, add a statement to the STWIN.INI
as shown:
8 = RECTANGLE, RoundedRec, 50, 1, 0, 25,100
The elements of the statement correspond to:

A numeric ID = RECTANGLE; any name; centerpoint on vertical axis between 0 and 100;
a number indicating which bar chart element(s) the rectangle can replace (1 for endpoint,
2 for bar, 3 for both); a number indicating whether interiors should be filled (0 to fill all
interiors, 1 to fill alternate interiors); relative degree of edge rounding, represented by a
number between 0 and 100; and relative height represented by a number between 0 and
100.
To add circles to the bar and/or endpoint choices, add a statement to the STWIN.INI
using this format:
7 = CIRCLE, Elongated, 50, 1, 0, 25,100

A numeric ID = CIRCLE; any name; centerpoint on vertical axis between 0 and 100; a
number indicating which bar chart element(s) the shape can apply to (1 for endpoints, 2
for bars, 3 for both); a number indicating whether interiors should be filled (0 to fill all
interiors, 1 to fill alternate interiors); relative width represented by a number between 0
and 100; and relative height represented by a number between 0 and 100.
To add polygons to the bar and/or endpoint choices, add a statement to the STWIN.INI
using this format:
6 = POLYGON, Triangle, 100, 1, 1, 3, 0,0, 100,50, 0,100

A numeric ID = POLYGON; any name; centerpoint on vertical axis between 0 and 100; a
number indicating which bar chart element(s) the shape can replace (1 for endpoint, 2 for
bar, 3 for both); a number indicating whether interiors should be filled (0 to fill all interiors,
1 to fill alternate interiors); the number of sides for the polygon.
To add metafiles to the list of available bar and/or endpoint symbols, add a statement to
the STWIN.INI using this format:
5 = Metafile, Logo, 50, 1, 1, C:\graphics\our_logo.wmf

A numeric ID = METAFILE; any name; centerpoint on vertical axis between 0 and 100; a
number indicating which bar chart element(s) the metafile can replace (1 for endpoints, 2
for bars, 3 for both); a number indicating whether the pictures should be outlined (0 for no
outline, 1 for outline); the path to the metafile.
You can also use bitmap files as endpoints. To use a bitmap, use the Metafile
format, replacing METAFILE with BITMAP and specifying a .BMP file.
[Directories]
This section controls where SureTrak looks for various components of the application.
Initially, it reflects the directory choices you made during Setup.
Setting
Comments
Program = [drive and directory]
Path to STW.EXE; usually \STWIN.
Setting
Comments
Layouts = [drive and directory]
Path to layouts; usually

\STWIN\LAYOUTS.
Projects = [drive and directory]
Default path to projects; usually

\STWIN\PROJECTS.
Graphics = [drive and directory]
Default path to clipart; usually

\STWIN\CLIPART.
Templates = [drive and directory]
Path to template projects directory.
SoftBridgeScripts = [drive: directory, 0-1]
Path to SoftBridge scripts or programs,

usually \STWIN\SCRIPTS; 0 = SBL
scripts, 1 = SBX programs.
The following are optional directories:
[Special Printers]
and [PERT Special
Printers]
SoftBridgeInclude = [drive and directory]
Path to SBL include files.
SoftBridgeBinary = [drive and directory]
Path to SBL binary files.
Work = [drive and directory]
Path to SureTrak read/write files.

SSCDB.STW must be read/write.
UserFil = [drive and directory]
Path to P3 and FH access rights files.
These sections enable you to override certain printer characteristics for improved
compatibility with SureTrak. Type a statement using the format
Printer Driver Name = Value
The value is the sum of the following option values:

Value
Comments
Emulate styled line drawing (dashed and dotted lines).
Clip text for activity columns (when the width of the

column is smaller then the length of the text).
Use rectangle drawing instead of filling.
Compact clipping rectangle. (Use this setting if lines are

not clipped around bars on large output media.)
16
Draw text without clipping rectangle (for OEM plotter

drivers, activity columns only)
HP LaserJet 4/4M = 3
Enables HP LaserJet 4 to emulate styled line drawing

and clips text for the activity columns.
HP LaserJet III = 3
Enables HP LaserJet III to emulate styled line drawing

and clips text for the activity columns.
Primavera Plot = 4
Enables Primavera Plotter driver to use rectangle

drawings.
To use any of the above settings for all printers you are using with SureTrak, specify All
Printers rather than a specific printer driver name. For example, the setting All Printers =
16 draws text without clipping what is behind it.
[PERTOptions]
[PERTDisplay]
This section controls reorganization of the PERT view.

Value
Comments
MaxActsPerRow = [ 1 - 32767 ]
Specifies the maximum number of activities per row

when reorganizing the PERT view.
This section controls the group title text for the Uncategorized band in grouped PERT
layouts.
Value
Comments
Uncategorized = [ text ]
Specify the text to use in the Uncategorized band.
[Mail Act Fields] This section contains the activity information you want to include in
mail messages, corresponding to your preferences in the Mail Setup dialog box. Use the
dialog box, rather than the .INI file, to change mail activity settings.
[Mail Res Fields] This section contains the resource information you want to include in
mail messages, corresponding to your preferences in the Mail Setup dialog box. Use the
dialog box, rather than the .INI file, to change mail resource settings.
[DDF Options]
SureTrak uses information in this section to update the FILE.DDF and FIELD.DDF files
when you save the project. SureTrak uses ODBC file access and Btrieve drivers when
saving projects using the P3 file format.
Setting
Comments
NoDDF = [0 or 1]
1 SureTrak will not prompt you to create

DDF files, which are necessary for ODBC.
0 the Update Data Dictionary dialog box
appears when you save project in P3 format.
[User]
ActivityCodes = 1
SureTrak updates the activity codes portion

of the data dictionary files.
CustomDataItems = 1
SureTrak updates the Custom Data Items

portion of the data dictionary files.
Advanced = [0 or 1]
1 Uses Advanced option;

0 Uses Normal option.
The first two settings identify this as your copy of SureTrak. You can use the next two
settings to open P3/FH-format projects, that require you to type a valid user name.
Setting
Comments
Name = [your name]
Company = [your company name]
Login = [your P3 user name]
Bypasses P3/FH login prompt if you are a

valid user for the P3 project.
[Format]
Setting
Comments
AutoLogin = [0 or 1]
0 SureTrak always asks for a login

name.
1 SureTrak allows login bypass.
This section contains SureTrak format settings.

Setting
Comments
MDI_Size = [number]
Size of SureTrak application window.
Client_Size = [number]
Size of project window.
Undo_Level = [number]
Number of activities you can recover using

Undo; limited by RAM.
ClipboardFormats = [SureTrak, P3, Limits the Clipboard formats SureTrak

Tab-delimited]
uses.
[Menu Files]
[Detail Windows]
This section identifies the four projects listed at the bottom of SureTrak's File menu.
This section controls the location of detail forms. When you display detail forms, SureTrak
remembers their last position onscreen and returns them to that position. The coordinates
are listed in order: left, top, right, and bottom.
Setting
Comments
Codes = [coordinates]
Last location of detail form.
Constraints = [coordinates]
[Legend]
Setting
Comments
Costs = [coordinates]
Dates = [coordinates]
Preds = [coordinates]
Resources = [coordinates]
Succs = [coordinates]
Revenue = [coordinates]
This section controls the appearance of the Bar chart legend. From SureTrak, control the
appearance of the Bar chart legend by choosing View, Bar Chart Legend. The coordinates describe the legend's position: left, top, right, and bottom.
Setting
Comments
Box1 = [coordinates]
Position of legend.
On = [0 or 1]
Whether legend is displayed (1) or not (0).
[ResourceLegend] This section controls the appearance of the resource legend. You
can control the appearance of the resource legend from SureTrak by choosing View,
Resource Legend while the resource profile is displayed.
Setting
Comments
Position of legend.
On = [0 or 1]
Whether legend is displayed (1) or not (0).
[Toolbar]
This section controls the appearance of the main toolbar, startup toolbar, and print
preview toolbar. From within SureTrak, display toolbars from the View menu. Control the
appearance of the startup toolbar by choosing Tools, Customize, Toolbar when no
projects are open. Control the appearance of the main toolbar by choosing Tools,
Customize, Toolbar when a project is open. Control the appearance of the print preview
toolbar by choosing Tools, Customize, Toolbar while in print preview.
Setting
Comments
Color = [ 0 or 1 ]
Display color (1) or monochrome (0) tools.
Large = [ 0 or 1]
Display large (1) or small (0) tools.
Tools = [integer list]
Lists Main Toolbar tool IDs.
Help = [ 0 or 1]
Show toolbar help automatically (0) or using right

mouse button (1).
StartupTools = [integer list]
Lists Startup Toolbar tool IDs.
PreviewTools = [integer list]
Lists Print Preview Toolbar tool IDs.
Box1 = [l, t, r, b]
Left, top, right, and bottom coordinates of toolbar, giving

its size and position.
OutlineLayout = [ ]
Outline layout.
Pos = [ 0-6 ]
Project window edge to which the toolbar is attached: 0

- left, 1 - right, 2 - top, 3 - bottom, 6 - floating
Sizeable = [ 0 or 1 ]
Whether the floating toolbar is sizeable (1) or not (0).
[EditToolbar]
[Status Fields]
[Datometer]
This section controls the appearance of the editing toolbar. From within SureTrak, display
the editing toolbar by choosing View, Editing Toolbar. Control the appearance of the
editing toolbar by choosing Tools, Customize, Editing Toolbar.
Setting
Comments
On = [ 0 or 1]
Display (1) or hide (0) the editing toolbar.
Size and position of toolbar when floating.
Pos = [0-6]
Project window edge to which the toolbar is attached:

0 - left, 1 - right, 2 - top, 3 - bottom, 6 - floating
Sizeable = [0 or 1]
Specify whether the floating toolbar is resizeable (1) or

not (0).
EditTools = [integer list]
Lists editing toolbar tool IDs.
This section controls the display and content of the status bar. From within SureTrak,
display the status bar by choosing Tools, Options; click the View tab and mark the Status
Bar checkbox. Control its content by choosing Tools, Customize, Status Bar.
This section controls the width of the Datometer. From within SureTrak, display the
Datometer by choosing Tools, Options; click the View tab and mark the Datometer
checkbox. Size the Datometer by dragging its left edge to the width you want.
Setting
Comments
Datometer = [integer]
Width in characters.
[ResWinDetail]
[STW Options]
This section controls the appearance of the resource profile/table detail window. From
within SureTrak, you can display the resource profile/table detail window by clicking
inside a profile or table with the left or right mouse button.
Setting
Comments
Screen position of resource profile/table detail window.
This section controls options that apply to all projects you open. From within SureTrak,
you can control many of these options by choosing Tools, Options.
Setting
Comments
LeaveWindows = [0 or 1]
Controls detail forms when closing the Activity form.
MultipleWindows = [0 or 1]
Enables you to view multiple or single detail forms.
AutoSaveTime = [integer]
The time interval for SureTrak to automatically save your

projects; 0-120 minutes.
Confirmation = [0, 1 or 2]
To control confirmation dialog boxes when deleting data:

0 = all, 1 = unrecoverable only, 2 = none.
EditDates = [0 or 1]
Enables you to edit early and late dates on Activity form.
FontFormat = [font name, style, size]
Default font.
UseGlobalUSERS50 = [0 or 1]
For compatibility with German version of P3.
GlobalFileLocking = [0 or 1]
For compatibility with German version of P3.
Star Char = [ character ]
Enables you to change the character SureTrak uses to

identify constrained and calculated activities.
Setting
Comments
Title Separator = [ character ]
Enables you to change the character SureTrak uses to

separate activity column titles.
Mail Server =
[MAPI, VIM, SMI, or Notes16]
If you have more than one mail system available, controls

which SureTrak uses.
Mail UseResAddresses = [ 0 or 1]
Controls whether or not SureTrak reads resource E-mail

addresses from STWIN.INI; 1 reads the file, 0 does not.
If setting is 1, also see information on the use of the
[Mail ResAddresses] section.
Mail ByPassSend = [ 0 or 1 ]
If set to 1, SureTrak behaves as though there is no E-mail

system installed, and writes .PRD files directly to disk; if set
to 0, SureTrak uses E-mail.
Mail ByPassReceive = [ 0 or 1 ]
If set to 1, SureTrak behaves as though there is no E-mail

system installed, and reads .PRD files directly to disk; if set
to 0, SureTrak uses E-mail.
Mail Rel = [ 0 or 1 ]
Controls whether relationship information is included in mail

message.
Mail Separator = [ character ]
Specifies the character SureTrak uses to separate activity

information in mail messages.
Mail Bmp = [ 0 or 1 ]
Records whether or not you included a project picture in

your last mail message.
RunTutorOnStartup = [ 0 or 1 ]
Determines whether or not SureTrak prompts you to run the

SureTrak tutorial.
Custom Zoom = [ 10 - 400 ]
Identifies the last Custom Zoom level you used.
[Mail ResAddresses]
[Project Options]
This section lists resource codes and their associated E-mail addresses. SureTrak uses
this data if the Mail UseResAddresses option in the [STW Options] section is set to 1.
Setting
Comments
[Resource Code] = [E-mail address]
Example:
WRITER1 = langert@primavera.com
WRITER2 = clittle@primavera.com
This section controls options that apply to the open project. Control these options interactively by choosing Tools, Options, and clicking the various tabs to set options. Control
these options for new projects by using the same commands when no projects are open.
Setting
Comments
DefaultDuration = [ 0 or 1 ]
Default duration unit: 0 = hours; 1 = days (General tab).
DurationStyle = [ 0, 1, 2, 3 ]
How SureTrak displays durations: 0 = h, 1 = d, 2 = d-h,

3 = w-d-h (Project tab).
FloatStyle = [ 0 or 1 ]
How SureTrak displays float amounts: 0=h, 1=d (Project tab).
NumberofDecimals = [ 0 or 2 ]
How SureTrak displays resource, cost and revenue values:

0 = no decimal, 2 = two decimal places (Resource tab).
DefDurationType = [ 0, 1 ]
Default activity type: 0 = task, 1 = independent (Project tab).
PCTtoPD = [ 0 or 1 ]
Whether or not remaining duration is linked to percent

complete; 0 = no, 1 = yes (Resource tab).
PCTtoBQtoATD = [ 0 or 1 ]
Whether or not to use updated percent complete against

budget to estimate actual to date resources; 0 = no, 1 = yes
(Resource tab).
[Colors]
Setting
Comments
Freeze QA = [ 0 or 1 ]
Freeze resource units per hour; 0 = no, 1 = yes

(Resource tab).
Calc Costs = [ 0 or 1 ]
Recalculate the costs when quantity changes; 0 = no, 1 = yes

(Resource tab).
DefDurationValue = [ integer ]
Default duration in hours.
DateFormat =
[ DD/MM/YY combination ]
Default date format (Dates tab).
TimeSetting = [ 0, 12, 24 ]
Default time format: 0 = don't show time, 12 = 12-hour time,

24 = 24-hour time (Dates tab).
DateSeparator = [ character ]
Identifies separator character used in dates (Dates tab).
This section controls the color palettes. From within SureTrak, you can control the colors
by choosing Format, Screen Colors. The following palettes are included with SureTrak.
Palette
Setting
December
255, 16777215, 16777215, 0, 12632256, 0, 32768, 16777215,

16777215, 0, 16777215, 0, 16777215, 0, 65535,0,
Default
8388608, 16777215, 16777215, 0, 16777088, 0, 8388608,

16777215, 16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Fluorescent
8388863, 16777215, 16777215, 0, 65280, 0, 8388863,

16777215, 16777215, 0, 16777215,0, 16777215, 0, 65535, 0,
Frankfurter
255, 16777215, 16777215, 0, 8454143, 0, 255, 16777215,

16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Palette
Setting
Irish Isle
32768, 16777215, 16777215, 0, 8454016, 0, 32768,

16777215, 16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Leather
8388672, 16777215, 16777215, 0, 12632256, 0, 8388672,

16777215, 16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Monochrome
12632256, 0, 16777215, 0, 0, 16777215, 12632256, 0,

16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Ocean Breeze
8421376, 0, 16777215, 0, 16777088, 0, 8421376, 0,

16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Pastel
8454143, 0, 16777215, 0, 16776960, 0, 8454016, 0,

16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Rugby
128, 65535, 16777215, 0, 8388608, 16777215, 128, 65535,

16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Southwest
8454143, 0, 16777215, 0, 8421376, 16777215, 8454143, 0,

16777215, 0,16777215, 0, 16777215, 0, 65535, 8388608,
Spice
128, 16777215, 16777215, 0, 64, 16777215, 128, 16777215,

16777215, 0, 16777215, 0, 16777215, 0, 65535, 0,
Tweed
32896, 0, 16777215, 0, 12632256, 0, 32896, 0, 16777215, 0,

16777215, 0,16777215, 0, 65535, 0,
[Relationships]
[Toolmenu]
This section of the .INI file enables you to change the aspect ratio of relationship line
arrows.
Setting
Comments
Arrow = [pair of integers]
Specify height and width in tenths of a point; e.g.

30,20 means the arrow will be 3 X 2 pts.
This section enables you to add items to the Custom Tools menu. Add items as a convenient way to run other programs from within SureTrak (choose Tools, Custom Tools).
Setting
Comments
Toolname = [path and command] A tool can be an .EXE, .PIF, .BAT, .COM, or .SBX file. It
can also be a project name; include the .P3, .FH, or .MPX
extension if it is not a SureTrak type project. You can
append command line options just as though you were
starting the program from a command line. Insert an
ampersand before the letter of the Tool name you want to
use as a hotkey. For example,
Global &Change = C:\STWIN\SCRIPTS\GBLCHNG.SBX
adds the Global Change script to the menu with C as the
hotkey for the command.
<Menu Break> # = 1
Insert one or more separator bars between items on the

Custom Tools menu. For the first separator, replace the
pound sign with the number 1; use 2 for the next separator,
and so forth. Type the 1 to the right of the equals sign for all
separators.
[Startup]
[Features]
These command lines specify other programs or projects that SureTrak runs upon
startup.
Setting
Comments
[entry name] = [command line]
An item can be an .EXE, .PIF, .BAT, .COM, or .SBX file. It

can also be a project name; include the .P3, .FH, or .MPX
extension if it is not a SureTrak type project. The [entry
name] can be any unique name.
This section enables you to customize your use of SureTrak.

Setting
Comments
Quick Add = [0 or 1]
Display the Activity form when adding activities; 0 = yes, 1 = no

(default).
Arrow Add = [0 or 1]
Add an activity or row when you press the down arrow from the
bottom row of a table; 0 = no, 1 = yes (default)
Start to Finish = [0 or 1]
Allow start to finish relationship types; 0 = no, 1 = yes (default).
Add Dicts = [0-7]
Controls the addition of dictionary entries when assigning values

not already in dictionary to activities: 0 = never add to dictionaries,
1 = add resources, 2 = add activity codes, 3 = add resources and
activity codes, 4 = add WBS codes, 5 = add resources and WBS
codes, 6 = add WBS and activity codes, 7 = add resource, activity,
and WBS codes.
FDates = [0 or 1]
Controls rounding-up display of finish date time:

1 = xx:59 (e.g. 4:59), 0 = xx:00 (e.g. 5:00).
Debug = [0 or 1]
Enable (1) or disable (0) debug messages.
Setting
Comments
System Font = [Font name]
Specify the system font for use in the status bar, forms and tables,
edit bar, Datometer, calendars, drop-down lists and menus, and
so forth.
Topic Only = [0 or 1]
When organizing the Bar chart view in Outline mode, use the level
font and color only on topic activities (rather than on all activities at
a particular outline level): 0 = no, 1 = yes.
No Sched = [0 or 1]
Automatic scheduling occurs when opening a SureTrak (DOS

version 2.0) or .MPX project: 0 = yes, 1 = no.
Wrap Tools = [0 or 1]
Toolbars wrap onto multiple rows when too wide for screen:
0 = no, 1 = yes.
ScriptMode = [0 to 7]
Specify SBL debug mode for running scripts.
First Work Day = [0-7]
Specify which weekday falls on the increments of a weekly

timescale (0 = use first workday of the Global workweek, 1-7 =
Sunday-Saturday).
Report Dlg Apply = [0 or 1]
Double-clicking a report on the Report menu applies the report (1)

or prints it (0).
Stay Dead = [0 or 1]
SureTrak-type projects saved with Reorganize Automatically

turned off will (0) or will not (1) reorganize automatically when
reopened.
New Project Type = [0-3]
Default file type for new projects; 0 = SureTrak; 1 = Project Group;

2 = Concentric (P3); 3 = Finest Hour.
Cleanup Level = [integer]
Number of memory blocks created before leveler reuses earlier

memory blocks.
Setting
Comments
Small Res Index = [integer]
Number of memory blocks created before profile reuses earlier

memory blocks.
Driving Resources = [0 or 1]
Default setting when creating a new resource:

0 = nondriving, 1 = driving.
Level Resources = [0 or 1]
Default setting when creating a new resource:

0 = do not level, 1 = level.
Default Res QA = [integer]
Default quantity of resource to be assigned when assigning new

resource.
OLE = [0 or 1]
Allow attachment of many types of OLE objects (1), or allow

attachment of .WMF, .BMP, and .PMT files only.
P3 Save Option = [0, 1, 2, 4]
When saving a P3 project, also create and save these matching

SureTrak files: 0 = all files in STW, 1 = external layout file,
2 = external filter file; 4 = external report file.
Auto Increment = [integer]
Set the increment to use when automatically generating activity

IDs.
Setting
Comments
Language = [ # ]
Set the language used to display the timescale and default

column headings by replacing the # with the language code from
the following list:
0 = default language (English)
1 = Arabic*
2 = Portuguese (Brazilian)
3 = Chinese (Traditional)*
4 = Chinese (Simplified)*
5 = Russian*
6 = Danish
7 = Dutch
8 = French
9 = German
10 = Greek*
11 = Hebrew*
12 = Italian
13 = Japanese*
14 = Norwegian
15 = Spanish
16 = Swedish
17 = Turkish*
18 = Polish*
19 = Hindi*
20 = Bahasa Malaysia
21 = Romanian
22 = Czech*
23 = Korean*
24 = Bosnian
25 = Hungarian*
26 = Ukrainian*
27 = Icelandic
*: Languages marked with an asterisk require a localized version
of Windows to display their character set.
[Backup & Restore]
This section corresponds to the settings in the Backup and Restore dialog boxes.
Settings report information about the last backup performed; change settings to change
options for the next backup or restore operation.
Setting
Comments
CompressBackup = [0 or 1]
Indicates whether the last backup was compressed (1)

or non-compressed (0).
Shared Layouts = [0 or 1]
Indicates whether the last backup included shared

layouts (1) or not (0).
Tab-Graph Reports = [0 or 1]
Indicates whether the last backup included P3 tabular/

graphical reports (1) or not (0).
No Access List = [0 or 1]
Indicates whether the last backup included the P3

access list (0) or not (1).
External Relationships = [0 or 1]
Indicates whether the last restoration included

external relationships (1) or not (0).
Merge Dictionaries = [0 or 1]
Indicates whether the last restoration merged

dictionary data (1) or not (0).
BackType = [0,1,2,3]
Identifies the file format of the last backup:

0 = SureTrak; 1 = Project Group; 2 = Concentric (P3);
3 = Finest Hour.
BackFromDir = [path]
Identifies the Backup From drive and directory.
BackToDir = [path]
Identifies the Backup To drive and directory.
4-229
Expedition 6.0 Files

In this chapter:
Expedition Database
Tables
All Documents
Attachments
Change Management
Change Orders
Contacts
Contracts
Contracts & Purchase
Orders
Conversion
Correspondence
Received
Correspondence
Received & Sent
Correspondence Sent
Cost Worksheet
Custom Data Items
Daily Reports
Distribution Lists
Drawing Sets
Drawings
Field Initialization
Filters
Generate
InBasket
Insurance
Invoices
Issues
Item Descriptions
Letters
Mail
Materials Delivery
Meeting Minutes
Notepads
Notices
Paper Sizes
Project Preferences
Proposals
Punch List
Purchase Orders
Requests
Requisitions
Roles
Saved User Layout
Security
Selection Tree
Sorts
Specification Sections
Status
Submittal Packages
Submittals
Telephone Records
Transmittals
Trends
Wizards
Expedition stores all

project data in a
Sybase SQL Anywhere
database. These topics
list the tables, and
fields within those
tables, in an Expedition
database. Use this
information to create
reports or to exchange
Expedition data with
other ODBC-compliant
database applications
Expedition 6.0 Files 4-230
Expedition Database Tables

While you are working in Expedition, you can review database table and field information
by clicking the right mouse button in any field. Expedition displays the name of the current
field and the name of the database table which contains that field in the status bar at the
bottom of the workspace.
The Expedition database contains base tables and views. A view is a combination of two
or more base tables which brings together related information. Views also contain calculated fields, so if you are creating a report, it is a good idea to use a view instead of a base
table.
Please note that this chapter was compiled before the final version of
Expedition 6.0. If you find a table or field in your database that does not
appear in this chapter, contact Expedition Technical Support by phone at
1-603-253-8484 or via the Internet at exptech@primavera.com.
All Documents Module (View)

Table
Column Name
Data Type
Length
Decimals
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
approved_date
ball_in_court
ball_in_court_ini
cedt_master_key
cemt_master_key
cemt_number
change_date
change_issue
change_number
cntr_from_vndr
cntr_master_key
cntr_to_vndr
completion_date
contract_number
cost
currency_type
distributed_to
exchange_ptr
from_manager
from_vendor
from_vendor_ini
has_completed
has_started
is_approved
item_type
date
char
char
char
char
char
date
char
char
char
char
char
date
char
numeric
char
char
integer
char
char
char
smallint
smallint
smallint
char
4
8
3
26
26
12
4
6
8
8
26
8
4
12
20
4
16
4
22
8
3
2
2
2
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
CRVW
last_edit_by
last_edit_date
master_key
next_step
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_from_abbrev
ref_from_abbrev_ini
ref_number
ref_resource
ref_to_abbrev
ref_to_abbrev_ini
ref_type
remarks
required_date
responded_date
restricted_to
security_flag
spec_section
start_date
status
sys_item_type
title
to_manager
to_vendor
to_vendor_ini
char
timestamp
char
char
char
char
char
char
char
char
char
char
char
char
char
long varchar
date
date
char
char
char
date
char
char
char
char
char
char
8
8
26
8
8
16
12
1
8
3
8
8
8
3
4
32767
4
4
8
1
10
4
4
4
35
22
8
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Attachments (Base)
Table
Column Name
Data Type
Length
Decimals
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
DLNK
attachment
base_item_type
base_master_key
base_parent_key
base_sys_item_type
date_linked
item_type
last_edit_by
last_edit_date
linked_by_user
linked_by_vndr
linked_by_vndr_ini
master_key
move_to_tklr_date
private_note_indicator
project_name
restricted_to
security_flag
subject
sys_item_type
long varchar
char
char
char
char
date
char
char
timestamp
char
char
char
char
date
char
char
char
char
char
char
32767
4
26
26
4
4
4
8
8
8
8
3
26
4
1
8
8
1
80
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Change Management Module (View)

Table
Column Name
Data Type
Length
Decimals
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
ball_in_court
ball_in_court_ini
cemt_document_date
cemt_estimate_number
cemt_estimated
cemt_estimated_costs_posted
cemt_estimated_date
cemt_final
cemt_final_costs_posted
cemt_final_date
cemt_negotiated
cemt_negotiated_costs_posted
cemt_negotiated_date
cemt_proceed
cemt_quoted
cemt_quoted_costs_posted
cemt_quoted_date
cemt_reason_code
cemt_rejected
cemt_status
cemt_title
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
char
char
date
char
numeric
smallint
date
numeric
smallint
date
numeric
smallint
date
smallint
numeric
smallint
date
char
smallint
char
char
char
char
char
char
8
3
4
12
19
2
4
19
2
4
19
2
4
2
19
2
4
12
2
4
36
8
3
26
4
0
0
0
0
5
0
0
5
0
0
5
0
0
0
5
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
cntr_to_vndr
cntr_to_vndr_ini
company_name
contract_number
contract_type
cost_code
currency_type
estimated
estimated_costs_posted
estimated_date
estimated_doc_description
estimated_master_key
estimated_sales_tax
estimated_sys_item_type
estimated_time_change
estimated_view_desc_tag
exchange_ptr
final
final_costs_posted
final_date
final_doc_description
final_master_key
final_sales_tax
final_sys_item_type
final_time_change
final_view_desc_tag
item_type
last_edit_by
char
char
char
char
char
char
char
numeric
smallint
date
char
char
numeric
char
integer
varchar
integer
numeric
smallint
date
char
char
numeric
char
integer
varchar
char
char
8
3
36
12
4
12
4
19
2
4
30
26
17
4
4
66
4
19
2
4
30
26
17
4
4
66
4
8
0
0
0
0
0
0
0
5
0
0
0
0
3
0
0
0
0
5
0
0
0
0
3
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
CEDT
last_edit_date
latest_amount
latest_time_change
master_key
negotiated
negotiated_costs_posted
negotiated_date
negotiated_doc_description
negotiated_master_key
negotiated_sales_tax
negotiated_sys_item_type
negotiated_time_change
negotiated_view_desc_tag
order_number
parent_key
project_name
quoted
quoted_costs_posted
quoted_date
quoted_doc_description
quoted_master_key
quoted_sales_tax
quoted_sys_item_type
quoted_time_change
quoted_view_desc_tag
rejected
restricted_to
security_flag
timestamp
numeric
numeric
char
numeric
smallint
date
char
char
numeric
char
integer
varchar
char
char
char
numeric
smallint
date
char
char
numeric
char
integer
varchar
smallint
char
char
8
19
10
26
19
2
4
30
26
17
4
4
66
8
26
8
19
2
4
30
26
17
4
4
66
2
8
1
0
5
0
0
5
0
0
0
0
3
0
0
0
0
0
0
5
0
0
0
0
3
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CEDT
CEDT
CEDT
CEDT
spec_section
sys_item_type
use_this_record
workflow_phase
char
char
smallint
smallint
10
4
2
2
0
0
0
0
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
approved_changes
ball_in_court
ball_in_court_ini
change_issue
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
currency_type
description
document_date
estimate_number
estimated
estimated_date
estimated_doc_description
estimated_sales_tax
numeric
char
char
char
char
char
char
char
char
char
date
char
char
char
char
date
char
numeric
smallint
date
char
char
numeric
17
8
3
6
8
3
26
4
8
3
4
12
4
4
80
4
12
19
2
4
30
26
17
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
5
0
0
0
0
3
Table
Column Name
Data Type
Length
Decimals
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
estimated_view_desc_tag
exchange_ptr
final
final_costs_posted
final_date
final_doc_description
final_master_key
final_sales_tax
final_sys_item_type
final_time_change
final_view_desc_tag
item_type
last_edit_by
last_edit_date
lump_cost
lump_tax
master_key
master_key_a
negotiated
negotiated_date
negotiated_doc_description
char
integer
varchar
integer
numeric
smallint
date
char
char
numeric
char
integer
varchar
char
char
timestamp
numeric
numeric
char
char
numeric
smallint
date
char
char
numeric
char
integer
4
4
66
4
19
2
4
30
26
17
4
4
66
4
8
8
17
17
26
26
19
2
4
30
26
17
4
4
0
0
0
0
5
0
0
0
0
3
0
0
0
0
0
0
3
3
0
0
5
0
0
0
0
3
0
0
Table
Column Name
Data Type
Length
Decimals
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
negotiated_view_desc_tag
pending_changes
previous__date
proceed
project_name
project_name_a
quoted
quoted_costs_posted
quoted_date
quoted_doc_description
quoted_master_key
quoted_sales_tax
quoted_time_change
quoted_view_desc_tag
reason_code
rejected
remarks
restricted_to
revisd_cmpl_date
revised__date
scope
security_flag
start_date
status
subcon_total_estimated
subcon_total_final
subcon_total_negotiated
varchar
numeric
date
smallint
char
char
numeric
smallint
date
char
char
numeric
char
integer
varchar
char
smallint
long varchar
char
date
date
smallint
char
date
char
numeric
numeric
numeric
66
17
4
2
8
8
19
2
4
30
26
17
4
4
66
12
2
32767
8
4
4
2
1
4
4
25
25
25
0
3
0
0
0
0
5
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
5
5
5
Table
Column Name
Data Type
Length
Decimals
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
cemt_cnmt_view
subcon_total_quoted
sys_item_type
title
unit_cost
unit_tax
workflow_phase
numeric
char
char
numeric
numeric
smallint
25
4
36
17
17
2
5
0
0
3
3
0
Change Management Module (Base)

Table
Column Name
Data Type
Length
Decimals
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
ball_in_court
ball_in_court_ini
base_cntr_key
base_cntr_no
base_date
base_item_type
base_master_key
base_number
base_parent_key
base_sys_item_type
category
completion_date
cost_code
distributed_value
from_vendor
from_vendor_ini
is_imbalance
item_type
last_edit_by
last_edit_date
master_key
next_step
parent_key
project_name
ref_activity_id
char
char
char
char
date
char
char
char
char
char
char
date
char
numeric
char
char
smallint
char
char
timestamp
char
char
char
char
char
8
3
26
12
4
4
26
12
26
4
12
4
20
17
8
3
2
4
8
8
26
8
26
8
16
0
0
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
CDHT_TABLE
ref_cost_account
ref_cost_category
ref_resource
start_date
status
sys_item_type
to_vendor
to_vendor_ini
which_cost_type
char
char
char
date
char
char
char
char
char
20
1
8
4
4
4
8
3
16
0
0
0
0
0
0
0
0
0
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
ball_in_court
ball_in_court_ini
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
company_name
contract_number
contract_type
cost_code
currency_type
estimated
estimated_date
estimated_sales_tax
char
char
char
char
char
char
char
char
char
char
char
char
char
numeric
smallint
date
char
numeric
8
3
8
3
26
4
8
3
36
12
4
12
4
19
2
4
26
17
0
0
0
0
0
0
0
0
0
0
0
0
0
5
0
0
0
3
Table
Column Name
Data Type
Length
Decimals
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
exchange_ptr
final
final_costs_posted
final_date
final_master_key
final_sales_tax
final_sys_item_type
final_time_change
item_type
last_edit_by
last_edit_date
master_key
negotiated
negotiated_date
order_number
parent_key
project_name
quoted
quoted_costs_posted
quoted_date
quoted_master_key
char
integer
integer
numeric
smallint
date
char
numeric
char
integer
char
char
timestamp
char
numeric
smallint
date
char
numeric
char
integer
char
char
char
numeric
smallint
date
char
4
4
4
19
2
4
26
17
4
4
4
8
8
26
19
2
4
26
17
4
4
8
26
8
19
2
4
26
0
0
0
5
0
0
0
3
0
0
0
0
0
0
5
0
0
0
3
0
0
0
0
0
5
0
0
0
Table
Column Name
Data Type
Length
Decimals
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
CEDT_TABLE
quoted_sales_tax
quoted_time_change
rejected
restricted_to
security_flag
spec_section
sys_item_type
use_this_record
workflow_phase
numeric
char
integer
smallint
char
char
char
char
smallint
smallint
17
4
4
2
8
1
10
4
2
2
3
0
0
0
0
0
0
0
0
0
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
ball_in_court
ball_in_court_ini
change_issue
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
contract_number
contract_type
currency_type
document_date
estimate_number
estimated
estimated_date
char
char
char
char
char
char
char
char
char
char
char
char
date
char
numeric
smallint
date
8
3
6
8
3
26
4
8
3
12
4
4
4
12
19
2
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
5
0
0
Table
Column Name
Data Type
Length
Decimals
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
estimated_sales_tax
exchange_ptr
final
final_costs_posted
final_date
final_master_key
final_sales_tax
final_sys_item_type
final_time_change
item_type
last_edit_by
last_edit_date
master_key
negotiated
negotiated_date
previous__date
proceed
project_name
quoted
quoted_costs_posted
char
numeric
char
integer
integer
numeric
smallint
date
char
numeric
char
integer
char
char
timestamp
char
numeric
smallint
date
char
numeric
char
integer
date
smallint
char
numeric
smallint
26
17
4
4
4
19
2
4
26
17
4
4
4
8
8
26
19
2
4
26
17
4
4
4
2
8
19
2
0
3
0
0
0
5
0
0
0
3
0
0
0
0
0
0
5
0
0
0
3
0
0
0
0
0
5
0
Table
Column Name
Data Type
Length
Decimals
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
CEMT_TABLE
quoted_date
quoted_master_key
quoted_sales_tax
quoted_time_change
reason_code
rejected
remarks
restricted_to
revised__date
scope
security_flag
status
subcon_total_estimated
subcon_total_final
subcon_total_negotiated
subcon_total_quoted
sys_item_type
title
workflow_phase
date
char
numeric
char
integer
char
smallint
long varchar
char
date
smallint
char
char
numeric
numeric
numeric
numeric
char
char
smallint
4
26
17
4
4
12
2
32767
8
4
2
1
4
19
19
19
19
4
36
2
0
0
3
0
0
0
0
0
0
0
0
0
0
5
5
5
5
0
0
0
4
8
8
26
8
0
0
0
0
0
Change Management Module - Reason Codes

RESN_TABLE
RESN_TABLE
RESN_TABLE
RESN_TABLE
RESN_TABLE
item_type
last_edit_by
last_edit_date
master_key
project_name
char
char
timestamp
char
char
Table
Column Name
Data Type
Length
Decimals
RESN_TABLE
RESN_TABLE
RESN_TABLE
reason_code
reason_title
sys_item_type
char
char
char
12
23
4
0
0
0
Change Orders Module (View)

Table
Column Name
Data Type
Length
Decimals
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
CHDT
ball_in_court
ball_in_court_ini
completion_date
description
item_number
item_type
master_key
material_code
net_amount
next_step
parent_key
project_name
quantity
ref_activity_id
ref_cost_account
ref_cost_category
ref_item_num
ref_resource
sales_tax
sales_tax_rate
start_date
status
stock_number
sys_item_type
unit_price
char
char
date
long varchar
char
char
char
char
numeric
char
char
char
numeric
char
char
char
char
char
numeric
numeric
date
char
char
char
numeric
8
3
4
32767
5
4
26
12
30
8
26
8
17
16
12
1
10
8
17
19
4
4
30
4
19
0
0
0
0
0
0
0
0
6
0
0
0
3
0
0
0
0
0
3
5
0
0
0
0
5
Table
Column Name
Data Type
Length
Decimals
CHDT
units
char
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
approve_vendor1
approve_vendor1_ini
approve_vendor2
approve_vendor2_ini
approve_vendor3
approve_vendor3_ini
approved_date
approved_date2
approved_date3
ball_in_court
ball_in_court_ini
Bid_Package
cedt_master_key
cemt_master_key
cemt_number
change_date
change_in_sum
change_issue
change_number
cmpany_name3
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
char
char
char
char
char
char
date
date
date
char
char
char
char
char
char
date
numeric
char
char
char
char
char
char
char
char
char
8
3
8
3
8
3
4
4
4
8
3
9
26
26
12
4
17
6
8
36
8
3
26
4
8
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
completion_date
contract_number
contract_type
cost
currency_type
distributed_to
Drawing_Reference
exchange_ptr
from_cmpany_name
from_manager
from_vendor
from_vendor_ini
has_completed
has_started
is_approved
is_latest
item_type
last_edit_by
last_edit_date
Location
lump_cost
lump_tax
lump_tax_rate
master_key
net_change
new_sum
next_step
original_sum
date
char
char
numeric
char
char
char
integer
char
char
char
char
smallint
smallint
smallint
smallint
char
char
timestamp
char
numeric
numeric
numeric
char
numeric
numeric
char
numeric
4
12
4
20
4
16
12
4
36
22
8
3
2
2
2
2
4
8
8
12
17
17
19
26
17
19
8
17
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
3
5
0
3
3
0
3
Table
Column Name
Data Type
Length
Decimals
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
osha_reference
prior_date
prior_sum
Proceed
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_from_abbrev
ref_from_abbrev_ini
ref_number
ref_resource
ref_sys_type
ref_to_abbrev
ref_to_abbrev_ini
ref_type
remarks
required_date
responded_date
restricted_to
revisd_comp_date
security_flag
signed_by1
signed_by2
signed_by3
Spec_Reference
spec_section
start_date
char
date
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
long varchar
date
date
char
date
char
char
char
char
char
char
date
10
4
18
1
8
16
12
1
8
3
8
8
4
8
3
4
32767
4
4
8
4
1
22
22
22
10
10
4
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
CHMT
status
sys_item_type
time_change
title
to_cmpany_name
to_manager
to_vendor
to_vendor_ini
total_sales_tax
unit_cost
unit_tax
vendor_role
char
char
integer
char
char
char
char
char
numeric
numeric
numeric
char
4
4
4
35
36
22
8
3
18
17
17
4
0
0
0
0
0
0
0
0
3
3
3
0
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
approved_date
cedt_master_key
cemt_master_key
cemt_number
change_date
change_in_sum
change_issue
change_number
cntr_from_vndr
cntr_master_key
cntr_to_vndr
contract_number
from_vendor
has_completed
has_started
date
char
char
char
date
numeric
char
char
char
char
char
char
char
smallint
smallint
4
26
26
12
4
20
6
8
8
26
8
12
8
2
2
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
CRSM
is_approved
item_type
master_key
project_name
remarks
responded_date
status
sys_item_type
table_name
time_change
title
to_vendor
smallint
char
char
char
long varchar
date
char
char
char
integer
char
char
2
4
26
8
32767
4
4
4
10
4
35
8
0
0
0
0
0
0
0
0
0
0
0
0
Change Orders Module (Base)

Table
Column Name
Data Type
Length
Decimals
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
CHCO_TABLE
base_cemt_number
base_change_issue
base_change_number
base_cntr_from_vendor
base_cntr_number
base_cntr_to_vendor
base_cntr_type
base_cost
base_from_vendor
base_item_type
base_master_key
base_parent_key
base_responded_date
base_sys_item_type
base_time_change
base_title
base_to_vendor
date_collected
item_type
master_key
order_number
parent_key
project_name
sys_item_type
char
char
char
char
char
char
char
numeric
char
char
char
char
date
char
integer
char
char
date
char
char
integer
char
char
char
12
6
12
8
12
8
4
17
8
4
26
26
4
4
4
36
8
4
4
26
4
26
8
4
0
0
0
0
0
0
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
CHDT_TABLE
ball_in_court
ball_in_court_ini
completion_date
description
item_number
item_type
master_key
material_code
next_step
parent_key
project_name
quantity
ref_activity_id
ref_cost_account
ref_cost_category
ref_item_num
ref_resource
sales_tax
sales_tax_rate
start_date
status
stock_number
sys_item_type
unit_price
units
char
char
date
long varchar
char
char
char
char
char
char
char
numeric
char
char
char
char
char
numeric
numeric
date
char
char
char
numeric
char
8
3
4
32767
5
4
26
12
8
26
8
17
16
12
1
10
8
17
19
4
4
30
4
19
9
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
3
5
0
0
0
0
5
0
CHMT_TABLE
CHMT_TABLE
approve_vendor1
approve_vendor1_ini
char
char
8
3
0
0
Table
Column Name
Data Type
Length
Decimals
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
approve_vendor2
approve_vendor2_ini
approve_vendor3
approve_vendor3_ini
approved_date
approved_date2
approved_date3
ball_in_court
ball_in_court_ini
Bid_Package
cedt_master_key
cemt_master_key
cemt_number
change_date
change_in_sum
change_issue
change_number
cmpany_name3
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
currency_type
char
char
char
char
date
date
date
char
char
char
char
char
char
date
numeric
char
char
char
char
char
char
char
char
char
date
char
char
char
8
3
8
3
4
4
4
8
3
9
26
26
12
4
17
6
8
36
8
3
26
4
8
3
4
12
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
distributed_to
Drawing_Reference
exchange_ptr
from_cmpany_name
from_manager
from_vendor
from_vendor_ini
has_completed
has_started
is_approved
is_latest
item_type
last_edit_by
last_edit_date
Location
lump_cost
lump_tax
lump_tax_rate
master_key
net_change
next_step
original_sum
osha_reference
prior_date
Proceed
project_name
ref_activity_id
ref_cost_account
char
char
integer
char
char
char
char
smallint
smallint
smallint
smallint
char
char
timestamp
char
numeric
numeric
numeric
char
numeric
char
numeric
char
date
char
char
char
char
16
12
4
36
22
8
3
2
2
2
2
4
8
8
12
17
17
19
26
17
8
17
10
4
1
8
16
12
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
3
5
0
3
0
3
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
ref_cost_category
ref_from_abbrev
ref_from_abbrev_ini
ref_number
ref_resource
ref_sys_type
ref_to_abbrev
ref_to_abbrev_ini
ref_type
remarks
required_date
responded_date
restricted_to
revisd_comp_date
security_flag
signed_by1
signed_by2
signed_by3
Spec_Reference
spec_section
start_date
status
sys_item_type
time_change
title
to_cmpany_name
to_manager
to_vendor
char
char
char
char
char
char
char
char
char
long varchar
date
date
char
date
char
char
char
char
char
char
date
char
char
integer
char
char
char
char
1
8
3
8
8
4
8
3
4
32767
4
4
8
4
1
22
22
22
10
10
4
4
4
4
35
36
22
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
CHMT_TABLE
to_vendor_ini
unit_cost
unit_tax
vendor_role
char
numeric
numeric
char
3
17
17
4
0
3
3
0
Contacts Module (View)

Table
Column Name
Data Type
Length
Decimals
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
VNDT_FROM
address_line_1
address_line_2
address_line_3
beeper_phone
city
country
country_code
extension
fax
initials
item_type
location
mail_address
mail_method
master_key
mobile_phone
name
office_phone
parent_key
postal_code
project_name
state
sys_item_type
tax_id_number
title
char
char
char
char
char
char
char
char
char
char
char
char
char
smallint
char
char
char
char
char
char
char
char
char
char
char
36
36
36
18
28
30
10
4
18
3
4
8
254
2
26
18
22
18
26
15
8
30
4
20
22
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
VNDT_FROM
vendor_code
char
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
VNDT_TO
address_line_1
address_line_2
address_line_3
beeper_phone
city
country
country_code
extension
fax
initials
item_type
location
mail_address
mail_method
master_key
mobile_phone
name
office_phone
parent_key
postal_code
project_name
state
sys_item_type
tax_id_number
title
vendor_code
char
char
char
char
char
char
char
char
char
char
char
char
char
smallint
char
char
char
char
char
char
char
char
char
char
char
char
36
36
36
18
28
30
10
4
18
3
4
8
254
2
26
18
22
18
26
15
8
30
4
20
22
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
VNMT_FROM
ball_in_court
ball_in_court_ini
cannot_delete
company_name
completion_date
dbe
default_initials
default_location
item_type
last_edit_by
last_edit_date
master_key
mbe
next_step
project_name
ref_activity_id
remarks
restricted_to
security_flag
spec_section
start_date
status
sys_item_type
tax_id_number
vendor_abbrev
vendor_role
wbe
char
char
smallint
char
date
smallint
char
char
char
char
timestamp
char
smallint
char
char
char
long varchar
char
char
char
date
char
char
char
char
char
smallint
8
3
2
36
4
2
3
8
4
8
8
26
2
8
8
16
32767
8
1
10
4
4
4
20
8
4
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
VNMT_TO
ball_in_court
ball_in_court_ini
cannot_delete
company_name
completion_date
dbe
default_initials
default_location
item_type
last_edit_by
last_edit_date
master_key
mbe
next_step
project_name
ref_activity_id
remarks
restricted_to
security_flag
spec_section
start_date
status
sys_item_type
tax_id_number
vendor_abbrev
vendor_role
wbe
char
char
smallint
char
date
smallint
char
char
char
char
timestamp
char
smallint
char
char
char
long varchar
char
char
char
date
char
char
char
char
char
smallint
8
3
2
36
4
2
3
8
4
8
8
26
2
8
8
16
32767
8
1
10
4
4
4
20
8
4
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Contacts Module (Base)

Table
Column Name
Data Type
Length
Decimals
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
VNDT
address_line_1
address_line_2
address_line_3
beeper_phone
city
copies
country
country_code
extension
fax
initials
item_type
location
mail_address
mail_method
master_key
mobile_phone
name
office_phone
paper_size
parent_key
postal_code
project_name
state
sys_item_type
char
char
char
char
char
char
char
char
char
char
char
char
char
char
smallint
char
char
char
char
char
char
char
char
char
char
36
36
36
18
28
8
30
10
4
18
3
4
8
254
2
26
18
22
18
15
26
15
8
30
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
VNDT
VNDT
VNDT
tax_id_number
title
vendor_code
char
char
char
20
22
8
0
0
0
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
VNMT
ball_in_court
ball_in_court_ini
cannot_delete
company_name
completion_date
contract_number
dbe
default_initials
default_location
item_type
last_edit_by
last_edit_date
master_key
mbe
next_step
project_name
ref_activity_id
remarks
restricted_to
security_flag
spec_section
start_date
status
sys_item_type
char
char
smallint
char
date
char
smallint
char
char
char
char
timestamp
char
smallint
char
char
char
long varchar
char
char
char
date
char
char
8
3
2
36
4
12
2
3
8
4
8
8
26
2
8
8
16
32767
8
1
10
4
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
VNMT
VNMT
VNMT
VNMT
VNMT
tax_id
tax_id_number
vendor_abbrev
vendor_role
wbe
char
char
char
char
smallint
20
20
8
4
2
0
0
0
0
0
Contracts Module (View)

Table
Column Name
Data Type
Length
Decimals
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
CNDT
ball_in_court
ball_in_court_ini
completion_date
item_number
item_type
master_key
material_code
net_amount
next_step
package_number
parent_key
project_name
quantity
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
sales_tax
sales_tax_rate
start_date
status
stock_descriptn
submittal_number
sys_item_type
unit_price
char
char
date
char
char
char
char
numeric
char
char
char
char
numeric
char
char
char
char
numeric
numeric
date
char
long varchar
char
char
numeric
8
3
4
10
4
26
12
30
8
10
26
8
17
16
20
1
8
17
19
4
4
32767
15
4
19
0
0
0
0
0
0
0
6
0
0
0
0
3
0
0
0
0
3
5
0
0
0
0
0
5
Table
Column Name
Data Type
Length
Decimals
CNDT
units
char
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
accepted
accepted_by1
accepted_by2
accepted_date1
accepted_date2
allow_over_budget
approved_changes
balance
ball_in_court
ball_in_court_ini
Bid_Package
bill_add_line_1
bill_add_line_2
bill_add_line_3
bill_city
bill_company
bill_country
bill_country_code
bill_postal_code
bill_state
bill_vndr_abbrev
bill_vndr_abbrev_ini
calc_ret_to_pct_of_stored_mtl
calc_ret_to_pct_of_work
cedt_master_key
cemt_master_key
smallint
char
char
date
date
smallint
numeric
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
char
numeric
numeric
char
char
2
22
22
4
4
2
17
23
8
3
9
36
36
36
28
36
30
10
15
30
8
3
17
17
26
26
0
0
0
0
0
0
3
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
3
0
0
Table
Column Name
Data Type
Length
Decimals
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
cemt_number
completion_date
currency_type
dbe
description
distributed_to
document_date
document_number
exchange_ptr
fob_via
freight
from_add_line_1
from_add_line_2
from_add_line_3
from_city
from_company
from_country
from_country_code
from_postal_code
from_state
from_vendor
from_vendor_ini
has_completed
has_started
inv_to_date
item_type
last_edit_by
last_edit_date
char
date
char
smallint
char
char
date
char
integer
char
numeric
char
char
char
char
char
char
char
char
char
char
char
smallint
smallint
numeric
char
char
timestamp
12
4
4
2
80
16
4
12
4
30
17
36
36
36
28
36
30
10
15
30
8
3
2
2
17
4
8
8
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
Table
Column Name
Data Type
Length
Decimals
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
last_item_number
lump_cost
lump_tax
lump_tax_rate
managers_name
master_key
mbe
net_cost
next_step
num_approv_chng
pending_changes
project_name
prompt_for_get_when_latest
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
reference_number
remarks
req_first_line_item
req_increment_line_item
req_to_date
restricted_to
retain_material_stored
revisd_cmpl_date
revised_cntr_sum
security_flag
set_new_line_item_pct
char
numeric
numeric
numeric
char
char
smallint
numeric
char
integer
numeric
char
smallint
char
char
char
char
char
long varchar
char
numeric
numeric
char
smallint
date
numeric
char
numeric
10
17
17
19
30
26
2
18
8
4
17
8
2
16
20
1
8
30
32767
10
17
17
8
2
4
21
1
17
0
3
3
5
0
0
0
3
0
0
3
0
0
0
0
0
0
0
0
0
3
3
0
0
0
3
0
3
Table
Column Name
Data Type
Length
Decimals
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
ship_add_line_1
ship_add_line_2
ship_add_line_3
ship_city
ship_company
ship_country
ship_country_code
ship_postal_code
ship_state
ship_vndr_abbrev
ship_vndr_abbrev_ini
spec_section
start_date
status
sys_item_type
terms
to_add_line_1
to_add_line_2
to_add_line_3
to_city
to_company
to_country
to_country_code
to_postal_code
to_state
to_vendor
to_vendor_ini
total_cost
char
char
char
char
char
char
char
char
char
char
char
char
date
char
char
char
char
char
char
char
char
char
char
char
char
char
char
numeric
36
36
36
28
36
30
10
15
30
8
3
10
4
4
4
30
36
36
36
28
36
30
10
15
30
8
3
20
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
Table
Column Name
Data Type
Length
Decimals
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
CNMT
total_sales_tax
unit_cost
unit_tax
use_detail_pct_retain
use_detail_pct_tax
use_pct_of_stored_mtl
use_pct_of_work
wbe
numeric
numeric
numeric
smallint
smallint
smallint
smallint
smallint
18
17
17
2
2
2
2
2
3
3
3
0
0
0
0
0
Contracts Module (Base)

Table
Column Name
Data Type
Length
Decimals
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
CNDT_TABLE
ball_in_court
ball_in_court_ini
completion_date
item_number
item_type
master_key
material_code
next_step
package_number
parent_key
project_name
quantity
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
sales_tax
sales_tax_rate
start_date
status
stock_descriptn
submittal_number
sys_item_type
unit_price
units
char
char
date
char
char
char
char
char
char
char
char
numeric
char
char
char
char
numeric
numeric
date
char
long varchar
char
char
numeric
char
8
3
4
10
4
26
12
8
10
26
8
17
16
20
1
8
17
19
4
4
32767
15
4
19
9
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
3
5
0
0
0
0
0
5
0
Table
Column Name
Data Type
Length
Decimals
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
accepted
accepted_by1
accepted_by2
accepted_date1
accepted_date2
allow_over_budget
approved_changes
ball_in_court
ball_in_court_ini
Bid_Package
bill_add_line_1
bill_add_line_2
bill_add_line_3
bill_city
bill_company
bill_country
bill_country_code
bill_postal_code
bill_state
bill_vndr_abbrev
cedt_master_key
cemt_master_key
cemt_number
completion_date
currency_type
smallint
char
char
date
date
smallint
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
char
numeric
numeric
char
char
char
date
char
2
22
22
4
4
2
17
8
3
9
36
36
36
28
36
30
10
15
30
8
3
17
17
26
26
12
4
4
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
3
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
dbe
description
distributed_to
document_date
document_number
exchange_ptr
fob_via
freight
from_add_line_1
from_add_line_2
from_add_line_3
from_city
from_company
from_country
from_country_code
from_postal_code
from_state
from_vendor
from_vendor_ini
has_completed
has_started
inv_to_date
item_type
last_edit_by
last_edit_date
last_item_number
lump_cost
lump_tax
smallint
char
char
date
char
integer
char
numeric
char
char
char
char
char
char
char
char
char
char
char
smallint
smallint
numeric
char
char
timestamp
char
numeric
numeric
2
80
16
4
12
4
30
17
36
36
36
28
36
30
10
15
30
8
3
2
2
17
4
8
8
10
17
17
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
3
3
Table
Column Name
Data Type
Length
Decimals
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
lump_tax_rate
managers_name
master_key
mbe
next_step
num_approv_chng
pending_changes
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
reference_number
remarks
req_first_line_item
req_to_date
restricted_to
revisd_cmpl_date
security_flag
ship_add_line_1
ship_add_line_2
ship_add_line_3
ship_city
ship_company
numeric
char
char
smallint
char
integer
numeric
char
smallint
char
char
char
char
char
long varchar
char
numeric
numeric
char
smallint
date
char
numeric
char
char
char
char
char
19
30
26
2
8
4
17
8
2
16
20
1
8
30
32767
10
17
17
8
2
4
1
17
36
36
36
28
36
5
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
3
3
0
0
0
0
3
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
CNMT_TABLE
ship_country
ship_country_code
ship_postal_code
ship_state
ship_vndr_abbrev
spec_section
start_date
status
sys_item_type
terms
to_add_line_1
to_add_line_2
to_add_line_3
to_city
to_company
to_country
to_country_code
to_postal_code
to_state
to_vendor
to_vendor_ini
unit_cost
unit_tax
use_detail_pct_tax
use_pct_of_work
char
char
char
char
char
char
char
date
char
char
char
char
char
char
char
char
char
char
char
char
char
char
numeric
numeric
smallint
smallint
smallint
smallint
30
10
15
30
8
3
10
4
4
4
30
36
36
36
28
36
30
10
15
30
8
3
17
17
2
2
2
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
3
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CNMT_TABLE
wbe
smallint
Contracts & Purchase Orders Module (View)

Table
Column Name
Data Type
Length
Decimals
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
accepted
accepted_by1
accepted_by2
accepted_date1
accepted_date2
approved_changes
balance
ball_in_court
ball_in_court_ini
bill_add_line_1
bill_add_line_2
bill_add_line_3
bill_city
bill_company
bill_country
bill_country_code
bill_postal_code
bill_state
bill_vndr_abbrev
cedt_master_key
cemt_master_key
cemt_number
completion_date
currency_type
smallint
char
char
date
date
numeric
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
date
char
2
22
22
4
4
17
23
8
3
36
36
36
28
36
30
10
15
30
8
3
26
26
12
4
4
0
0
0
0
0
3
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
dbe
description
distributed_to
document_date
document_number
exchange_ptr
fob_via
freight
from_add_line_1
from_add_line_2
from_add_line_3
from_city
from_company
from_country
from_country_code
from_postal_code
from_state
from_vendor
from_vendor_ini
has_completed
has_started
inv_to_date
item_type
last_edit_by
last_edit_date
last_item_number
lump_cost
lump_tax
smallint
char
char
date
char
integer
char
numeric
char
char
char
char
char
char
char
char
char
char
char
smallint
smallint
numeric
char
char
timestamp
char
numeric
numeric
2
80
16
4
12
4
30
17
36
36
36
28
36
30
10
15
30
8
3
2
2
17
4
8
8
10
17
17
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
3
3
Table
Column Name
Data Type
Length
Decimals
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
lump_tax_rate
managers_name
master_key
mbe
net_cost
next_step
num_approv_chng
pending_changes
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
reference_number
remarks
req_to_date
restricted_to
revisd_cmpl_date
revised_cntr_sum
security_flag
ship_add_line_1
ship_add_line_2
ship_add_line_3
ship_city
ship_company
ship_country
ship_country_code
ship_postal_code
numeric
char
char
smallint
numeric
char
integer
numeric
char
char
char
char
char
char
long varchar
numeric
char
date
numeric
char
char
char
char
char
char
char
char
char
19
30
26
2
18
8
4
17
8
16
20
1
8
30
32767
17
8
4
21
1
36
36
36
28
36
30
10
15
5
0
0
0
3
0
0
3
0
0
0
0
0
0
0
3
0
0
3
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
CNMT_ALL_VIEW
ship_state
ship_vndr_abbrev
spec_section
start_date
status
sys_item_type
terms
to_add_line_1
to_add_line_2
to_add_line_3
to_city
to_company
to_country
to_country_code
to_postal_code
to_state
to_vendor
to_vendor_ini
total_cost
total_sales_tax
unit_cost
unit_tax
wbe
char
char
char
char
date
char
char
char
char
char
char
char
char
char
char
char
char
char
char
numeric
numeric
numeric
numeric
smallint
30
8
3
10
4
4
4
30
36
36
36
28
36
30
10
15
30
8
3
20
18
17
17
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
3
3
3
0
Conversion (Base)
Table
Column Name
Data Type
Length
Decimals
cvrt
cvrt
cvrt
cvrt
cvrt
cvrt
cvrt
conversion_status
date_converted
from_version
master_key
remarks
to_version
username
smallint
timestamp
char
integer
long varchar
char
char
2
8
8
4
32767
8
8
0
0
0
0
0
0
0
Correspondence Received Module (Base)

Table
Column Name
Data Type
Length
Decimals
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
ball_in_court
ball_in_court_ini
base_item_type
base_master_key
base_parent_key
base_sys_item_type
by_user
completion_date
contract_number
correspond_date
correspond_time
cost
description
from_vendor
from_vendor_ini
item_date
item_status
item_type
last_edit_by
last_edit_date
log_number
logged_by
master_key
next_step
number
char
char
char
char
char
char
smallint
date
char
date
char
numeric
char
char
char
date
char
char
char
timestamp
char
char
char
char
char
8
3
4
26
26
4
2
4
12
4
8
17
80
8
3
4
4
4
8
8
20
3
26
8
12
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
RCPT
project_name
ref_activity_id
remarks
response_date
restricted_to
security_flag
spec_section
start_date
status
subject
sys_item_type
to_vendor
to_vendor_ini
type_flag
user_name
char
char
long varchar
date
char
char
char
date
char
char
char
char
char
integer
char
8
16
32767
4
8
1
10
4
4
36
4
8
3
4
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Correspondence Received & Correspondence Sent

Module (View)
Table
Column Name
Data Type
Length
Decimals
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
ball_in_court
ball_in_court_ini
base_item_type
base_master_key
base_parent_key
base_sys_item_type
by_user
completion_date
correspond_date
correspond_time
cost
description
from_vendor
from_vendor_ini
item_date
item_status
item_type
last_edit_by
last_edit_date
log_number
logged_by
master_key
next_step
char
char
char
char
char
char
smallint
date
date
char
numeric
char
char
char
date
char
char
char
timestamp
char
char
char
char
8
3
4
26
26
4
2
4
4
8
17
80
8
3
4
4
4
8
8
20
3
26
8
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
CORR
number
project_name
ref_activity_id
remarks
response_date
restricted_to
security_flag
spec_section
start_date
status
subject
sys_item_type
to_vendor
to_vendor_ini
type_flag
user_name
char
char
char
long varchar
date
char
char
char
date
char
char
char
char
char
integer
char
12
8
16
32767
4
8
1
10
4
4
36
4
8
3
4
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Correspondence Sent Module (Base)

Table
Column Name
Data Type
Length
Decimals
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
ball_in_court
ball_in_court_ini
base_item_type
base_master_key
base_parent_key
base_sys_item_type
by_user
completion_date
contract_number
correspond_date
correspond_time
cost
description
from_vendor
from_vendor_ini
item_date
item_status
item_type
last_edit_by
last_edit_date
log_number
logged_by
master_key
next_step
number
char
char
char
char
char
char
smallint
date
char
date
char
numeric
char
char
char
date
char
char
char
timestamp
char
char
char
char
char
8
3
4
26
26
4
2
4
12
4
8
17
80
8
3
4
4
4
8
8
20
3
26
8
12
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
SENT
project_name
ref_activity_id
remarks
response_date
restricted_to
security_flag
spec_section
start_date
status
subject
sys_item_type
to_vendor
to_vendor_ini
type_flag
user_name
char
char
long varchar
date
char
char
char
date
char
char
char
char
char
integer
char
8
16
32767
4
8
1
10
4
4
36
4
8
3
4
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Cost Worksheet Module (View)

Table
Column Name
Data Type
Length
Decimals
CSCW
CSCW
cost_type_description
cost_type_sys
varchar
char
29
16
0
0
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
actuals_expended
actuals_issued
actuals_received
approved_var
bdgt_adjustment
bdgt_apprvd_rev
bdgt_est_rev
bdgt_orig_amnt
bdgt_pend_rev
bdgt_percent
bdgt_projected
bdgt_revised
Bid_Package
CATG
cmmt_adjustment
cmmt_apprvd_rev
cmmt_est_rev
cmmt_orig_amnt
cmmt_pend_rev
cmmt_percent
cmmt_projected
cmmt_revised
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
char
char
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
17
17
17
19
17
17
17
17
17
30
21
18
9
2
17
17
17
17
17
30
21
18
2
2
2
2
2
2
2
2
2
10
2
2
0
0
2
2
2
2
2
10
2
2
Table
Column Name
Data Type
Length
Decimals
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
CSMT
cost_code
description
DIVI
fund_adjustment
fund_apprvd_rev
fund_est_rev
fund_orig_amnt
fund_pend_rev
fund_percent
fund_projected
fund_revised
funding_var_ori
funding_var_tot
is_imbalance
item_type
last_edit_by
last_edit_date
master_key
order_code
original_var
pending_var
project_name
projected_var
restricted_to
security_flag
SPEC
sys_item_type
title
char
long varchar
char
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
numeric
smallint
char
char
timestamp
char
char
numeric
numeric
char
numeric
char
char
char
char
char
20
32767
3
17
17
17
17
17
30
21
18
18
22
2
4
8
8
26
20
18
20
8
22
8
1
6
4
34
0
0
0
2
2
2
2
2
10
2
2
2
2
0
0
0
0
0
0
2
2
0
2
0
0
0
0
0
Cost Worksheet Module (Base)

Table
Column Name
Data Type
Length
Decimals
CSCC
CSCC
cost_category_sys
cost_category_usr
char
char
12
12
0
0
CSCL
CSCL
CSCL
CSCL
cost_category_sys
cost_type_sys
header_bottom
header_top
char
char
char
char
12
16
16
16
0
0
0
0
CSCT
CSCT
CSCT
CSCT
CSCT
cost_category_sys
cost_subtype_sys
cost_type_sys
cost_type_usr
cost_worksheet_column
char
char
char
char
char
12
12
16
16
24
0
0
0
0
0
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
ball_in_court
ball_in_court_ini
base_cntr_key
base_cntr_no
base_date
base_item_type
base_master_key
base_number
base_parent_key
base_sys_item_type
category
char
char
char
char
date
char
char
char
char
char
char
8
3
26
12
4
4
26
12
26
4
12
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
CSDT
completion_date
cost_code
distributed_value
from_vendor
from_vendor_ini
is_imbalance
item_type
last_edit_by
last_edit_date
master_key
next_step
parent_key
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
start_date
status
sys_item_type
to_vendor
to_vendor_ini
which_cost_type
date
char
numeric
char
char
smallint
char
char
timestamp
char
char
char
char
char
char
char
char
date
char
char
char
char
char
4
20
17
8
3
2
4
8
8
26
8
26
8
16
20
1
8
4
4
4
8
3
16
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
actuals_expended
actuals_issued
actuals_received
bdgt_adjustment
numeric
numeric
numeric
numeric
17
17
17
17
2
2
2
2
Table
Column Name
Data Type
Length
Decimals
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
bdgt_apprvd_rev
bdgt_est_rev
bdgt_orig_amnt
bdgt_pend_rev
Bid_Package
CATG
cmmt_adjustment
cmmt_apprvd_rev
cmmt_est_rev
cmmt_orig_amnt
cmmt_pend_rev
cost_code
description
DIVI
fund_adjustment
fund_apprvd_rev
fund_est_rev
fund_orig_amnt
fund_pend_rev
is_imbalance
item_type
last_edit_by
last_edit_date
master_key
order_code
project_name
restricted_to
security_flag
numeric
numeric
numeric
numeric
char
char
numeric
numeric
numeric
numeric
numeric
char
long varchar
char
numeric
numeric
numeric
numeric
numeric
smallint
char
char
timestamp
char
char
char
char
char
17
17
17
17
9
2
17
17
17
17
17
20
32767
3
17
17
17
17
17
2
4
8
8
26
20
8
8
1
2
2
2
2
0
0
2
2
2
2
2
0
0
0
2
2
2
2
2
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CSMT_TABLE
CSMT_TABLE
CSMT_TABLE
SPEC
sys_item_type
title
char
char
char
6
4
34
0
0
0
CSTL
CSTL
CSTL
CSTL
CSTL
CSTL
alt_collating_seq
definition_name
definition_title
definition_value
master_key
parent_key
char
char
char
char
char
char
12
20
34
12
26
26
0
0
0
0
0
0
100
4
26
100
4
100
100
100
0
0
0
0
0
0
0
0
4
20
22
26
4
0
0
0
0
0
Cost Worksheet Module - Column Headings

HEADER_INFO
HEADER_INFO
HEADER_INFO
HEADER_INFO
HEADER_INFO
HEADER_INFO
HEADER_INFO
HEADER_INFO
datawindow
item_type
master_key
name
sys_item_type
system_text
user_text
window
char
char
char
char
char
char
char
char
Cost Worksheet Module - Cost Code Definitions

CSDF
CSDF
CSDF
CSDF
CSDF
colno
definition_name
description
master_key
start_column
integer
char
char
char
integer
Table
Column Name
Data Type
Length
Decimals
CSDF
width
integer
Custom Data Items (Base)

Table
Column Name
Data Type
Length
Decimals
CDTL
CDTL
CDTL
CDTL
CDTL
CDTL
CDTL
CDTL
alt_collating_seq
cdi_column_name
cdi_table_name
cdi_view_name
dictionary_title
dictionary_value
master_key
parent_key
char
char
char
char
char
char
char
char
22
20
30
30
50
22
26
26
0
0
0
0
0
0
0
0
GCDF
GCDF
GCDF
GCDF
GCDF
GCDF
GCDF
GCDF
GCDF
GCDF
cdi_class
cdi_decimal_places
cdi_length
cdi_name
cdi_table
cdi_type
cdi_view
colno
description
master_key
integer
integer
integer
char
char
char
char
integer
char
char
4
4
4
20
30
12
30
4
36
26
0
0
0
0
0
0
0
0
0
0
Daily Reports Module (Base)

Table
Column Name
Data Type
Length
Decimals
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
DREQ
ball_in_court
ball_in_court_ini
completion_date
description
equipment_source
equipment_type
item_type
last_edit_by
last_edit_date
master_key
next_step
parent_key
project_name
ref_activity_id
remark
restricted_to
security_flag
start_date
status
sys_item_type
unit
work_area
char
char
date
char
char
char
char
char
timestamp
char
char
char
char
char
long varchar
char
char
date
char
char
char
char
8
3
4
15
8
16
4
8
8
26
8
26
8
16
32767
8
1
4
4
4
4
11
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
DRLB
DRLB
apprentices
ball_in_court
char
char
4
8
0
0
Table
Column Name
Data Type
Length
Decimals
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
DRLB
ball_in_court_ini
category
completion_date
field_source
foremen
item_type
journeymen
last_edit_by
last_edit_date
master_key
next_step
parent_key
project_name
ref_activity_id
remark
restricted_to
security_flag
start_date
status
supervisors
sys_item_type
work_area
char
char
date
char
char
char
char
char
timestamp
char
char
char
char
char
long varchar
char
char
date
char
char
char
char
3
15
4
8
4
4
4
8
8
26
8
26
8
16
32767
8
1
4
4
4
4
11
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
DRMT
DRMT
DRMT
DRMT
DRMT
ball_in_court
ball_in_court_ini
Bid_Package
completion_date
contract_number
char
char
char
date
char
8
3
9
4
12
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
DRMT
daily_report
day_of_week
item_type
last_edit_by
last_edit_date
master_key
next_step
precipitation
project_name
ref_activity_id
report_date
report_no
report_period
restricted_to
security_flag
sky
start_date
status
sys_item_type
temperature
vendor_abbrev
vendor_abbrev_ini
wind
long varchar
char
char
char
timestamp
char
char
char
char
char
date
char
char
char
char
char
date
char
char
char
char
char
char
32767
10
4
8
8
26
8
10
8
16
4
5
16
8
1
10
4
4
4
10
8
3
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
DRVS
DRVS
DRVS
DRVS
ball_in_court
ball_in_court_ini
company_repsnted
completion_date
char
char
char
date
8
3
36
4
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
DRVS
item_type
last_edit_by
last_edit_date
master_key
next_step
parent_key
project_name
ref_activity_id
remark
restricted_to
security_flag
start_date
status
sys_item_type
time_of_visit
vendor_abbrev
vendor_abbrev_ini
visitor_name
char
char
timestamp
char
char
char
char
char
long varchar
char
char
date
char
char
char
char
char
char
4
8
8
26
8
26
8
16
32767
8
1
4
4
4
8
8
3
22
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
DSCH
DSCH
DSCH
DSCH
DSCH
DSCH
DSCH
DSCH
DSCH
activity_id
activity_title
early_finish
early_start
free_float
has_finished
has_started
item_type
master_key
char
char
date
date
integer
integer
integer
char
char
16
48
4
4
4
4
4
4
26
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
DSCH
DSCH
DSCH
DSCH
DSCH
DSCH
DSCH
original_duration
parent_key
percent_complete
project_name
remaining_duration
sys_item_type
total_float
integer
char
numeric
char
integer
char
integer
4
26
17
8
4
4
4
0
0
3
0
0
0
0
Distribution Lists (View)

Table
Column Name
Data Type
Length
Decimals
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
DLDT_VNDT
contact
contact_ini
copies
entered_by
extension
fax
is_from_group
item_type
last_edit_by
last_edit_date
mail_address
master_key
name
office_phone
paper_size
parent_key
project_name
restricted_to
security_flag
sys_item_type
char
char
char
char
char
char
smallint
char
char
timestamp
char
char
char
char
char
char
char
char
char
char
8
3
8
22
4
18
2
4
8
8
254
26
22
18
15
26
8
8
1
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Distribution Lists (Base)

Table
Column Name
Data Type
Length
Decimals
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
dldt_table
contact
contact_ini
entered_by
is_from_group
item_type
last_edit_by
last_edit_date
master_key
parent_key
project_name
restricted_to
security_flag
sys_item_type
char
char
char
smallint
char
char
timestamp
char
char
char
char
char
char
8
3
22
2
4
8
8
26
26
8
8
1
4
0
0
0
0
0
0
0
0
0
0
0
0
0
dlmt_table
dlmt_table
dlmt_table
dlmt_table
dlmt_table
dlmt_table
dlmt_table
dlmt_table
dlmt_table
dlmt_table
dlmt_table
distribution_list
entered_by
item_type
last_edit_by
last_edit_date
master_key
project_name
restricted_to
security_flag
sys_item_type
title
char
char
char
char
timestamp
char
char
char
char
char
char
12
22
4
8
8
26
8
8
26
4
23
0
0
0
0
0
0
0
0
0
0
0
Drawing Sets Module (Base)

Table
Column Name
Data Type
Length
Decimals
DSDW_TABLE
DSDW_TABLE
DSDW_TABLE
DSDW_TABLE
DSDW_TABLE
DSDW_TABLE
DSDW_TABLE
DSDW_TABLE
DSDW_TABLE
DSDW_TABLE
Drawing_Master_Key
Drawing_Revision_Master_Key
Drawing_Sketch_Master_Key
Item_Type
Master_Key
Project_Name
Revision_Number
Set_Master_Key
Sketch_Number
Sys_Item_Type
char
char
char
char
char
char
char
char
char
char
26
26
26
4
26
8
4
26
35
4
0
0
0
0
0
0
0
0
0
0
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
DSMT_TABLE
change_issue
drawing_phase
for_distribution
is_the_latest
item_type
last_edit_by
last_edit_date
master_key
parent_key
progress
project_name
ref_activity_id
set_date
set_name
char
char
integer
smallint
char
char
timestamp
char
char
numeric
char
char
date
char
6
8
4
2
4
8
8
26
26
17
8
16
4
12
0
0
0
0
0
0
0
0
0
2
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
DSMT_TABLE
DSMT_TABLE
set_title
sys_item_type
char
char
48
4
0
0
Drawings Module (View)

Table
Column Name
Data Type
Length
Decimals
DDRV_DRRV_VIEW
DDRV_DRRV_VIEW
DDRV_DRRV_VIEW
DDRV_DRRV_VIEW
DDRV_DRRV_VIEW
DDRV_DRRV_VIEW
DDRV_DRRV_VIEW
item_type
master_key
parent_key
project_name
revision_number
sys_item_type
title
char
char
char
char
char
char
char
4
26
26
8
4
4
35
0
0
0
0
0
0
0
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
DWMT_LATEST_VIEW
Item_Type
Latest_ddrv_Issued_Date
Latest_ddrv_master_key
Latest_ddrv_Reqd_Date
Latest_ddrv_Rev_No
Latest_ddrv_Sent_Date
Latest_drrv_master_key
Latest_drrv_Recd_Date
Latest_drrv_Reqd_Date
Latest_drrv_Rev_No
Latest_drrv_Sent_Date
latest_revision_master_key
latest_revision_number
latest_sent_date
master_key
parent_key
project_name
char
date
char
date
char
date
char
date
date
char
date
char
char
date
char
char
char
4
4
26
4
4
4
26
4
4
4
4
26
4
4
26
26
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
DWMT_LATEST_VIEW
Sys_Item_Type
char
Drawings Module (Base)

Table
Column Name
Data Type
Length
Decimals
DDRV_TABLE
DDRV_TABLE
DDRV_TABLE
DDRV_TABLE
DDRV_TABLE
DDRV_TABLE
DDRV_TABLE
DDRV_TABLE
DDRV_TABLE
DDRV_TABLE
Issued_Date
Item_Type
Master_Key
Parent_Key
Project_Name
Required_Date
Revision_Number
Sent_Date
Sys_Item_Type
Title
date
char
char
char
char
date
char
date
char
char
4
4
26
26
8
4
4
4
4
35
0
0
0
0
0
0
0
0
0
0
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
DDRW_TABLE
Comments
Copies
Item_Type
Master_Key
Paper_Size
Parent_Key
Percent_Progress
Project_Name
Returned_Date
Reviewer
Reviewer_Ini
Sent_Date
Status
Sys_Item_Type
long varchar
char
char
char
char
char
numeric
char
date
char
char
date
char
char
32767
8
4
26
15
26
17
8
4
8
4
4
4
4
0
0
0
0
0
0
2
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
DDRW_TABLE
Transmittal_Number
char
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
DRRV_TABLE
Item_Type
Master_Key
Parent_Key
percent_progress
Project_Name
Received_Date
Required_Date
Revision_Number
Sent_Date
Sys_Item_Type
Title
char
char
char
numeric
char
date
date
char
date
char
char
4
26
26
17
8
4
4
4
4
4
35
0
0
0
2
0
0
0
0
0
0
0
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
DRRW_TABLE
Comments
Copies
Item_Type
Master_Key
Paper_Size
Parent_Key
Percent_Progress
Project_Name
Returned_Date
Reviewer
Reviewer_Ini
Sent_Date
Status
Sys_Item_Type
long varchar
char
char
char
char
char
numeric
char
date
char
char
date
char
char
32767
8
4
26
15
26
17
8
4
8
4
4
4
4
0
0
0
0
0
0
2
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
DRRW_TABLE
Transmittal_Number
char
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
DSRW_TABLE
Comments
Copies
Item_Type
Master_Key
Paper_Size
Parent_Key
Percent_Progress
Project_Name
Returned_Date
Reviewer
Reviewer_Ini
Sent_Date
Status
Sys_Item_Type
Transmittal_Number
long varchar
char
char
char
char
char
numeric
char
date
char
char
date
char
char
char
32767
8
4
26
15
26
17
8
4
8
4
4
4
4
5
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
activity_id
area
bid_package
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
contract_number
char
char
char
char
char
char
char
char
char
char
16
15
15
8
3
26
4
8
3
12
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
DWMT_TABLE
contract_type
designer
designer_ini
discipline
drawing_number
drawing_phase
file_number
item_type
last_edit_by
last_edit_date
latest_ddrv_master_key
latest_drrv_master_key
latest_revision_master_key
latest_revision_number
latest_sent_date
master_key
parent_key
percent_progress
project_name
spec_section
sys_item_type
title
char
char
char
char
char
char
char
char
char
timestamp
char
char
char
char
date
char
char
numeric
char
char
char
char
4
8
3
12
35
8
12
4
8
8
26
26
26
4
4
26
26
17
8
10
4
48
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
char
char
char
15
23
4
0
0
0
Drawings Module - Bid Packages

BDPK_TABLE
BDPK_TABLE
BDPK_TABLE
Bid_Package
Description
Item_Type
Table
Column Name
Data Type
Length
Decimals
BDPK_TABLE
BDPK_TABLE
BDPK_TABLE
Master_Key
Project_Name
Sys_Item_Type
char
char
char
26
8
4
0
0
0
char
char
char
char
char
char
4
23
4
26
8
4
0
0
0
0
0
0
char
char
char
char
char
char
12
4
26
8
4
23
0
0
0
0
0
0
char
char
char
char
char
char
30
8
4
26
8
4
0
0
0
0
0
0
Drawings Module - Drawing Areas

AREA_TABLE
AREA_TABLE
AREA_TABLE
AREA_TABLE
AREA_TABLE
AREA_TABLE
Area_Code
description
Item_Type
Master_Key
Project_Name
Sys_Item_Type
Drawings Module - Drawing Disciplines

DISIPLINE_TABLE
DISIPLINE_TABLE
DISIPLINE_TABLE
DISIPLINE_TABLE
DISIPLINE_TABLE
DISIPLINE_TABLE
Discipline_Code
Item_Type
Master_Key
Project_Name
Sys_Item_Type
Title
Drawings Module - Drawing Phases

DWG_PHASE_TABLE
DWG_PHASE_TABLE
DWG_PHASE_TABLE
DWG_PHASE_TABLE
DWG_PHASE_TABLE
DWG_PHASE_TABLE
description
drawing_phase
Item_Type
Master_Key
Project_Name
Sys_Item_Type
Table
Column Name
Drawings Module - File Numbers
Data Type
Length
Decimals
FLNO_TABLE
FLNO_TABLE
FLNO_TABLE
FLNO_TABLE
FLNO_TABLE
FLNO_TABLE
char
char
char
char
char
char
23
12
4
26
8
4
0
0
0
0
0
0
smallint
char
char
char
char
char
char
char
date
date
char
char
char
2
8
4
4
26
26
8
4
4
4
35
4
35
0
0
0
0
0
0
0
0
0
0
0
0
0
Description
File_Number
Item_Type
Master_Key
Project_Name
Sys_Item_Type
Drawings Module - Sketches

DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
DWSK_TABLE
Approved
Designer
Designer_Ini
Item_Type
Master_Key
Parent_Key
Project_Name
Revision_Number
Sent_Date
Sketch_Date
Sketch_Number
Sys_Item_Type
Title
Field Initialization (Base)

Table
Column Name
Data Type
Length
Decimals
FINI
FINI
FINI
FINI
FINI
field_name
initial_value
is_modifiable
item_type
project_name
char
char
smallint
char
char
40
40
2
4
8
0
0
0
0
0
Filters (Base)
Table
Column Name
Data Type
Length
Decimals
FLTR
FLTR
FLTR
FLTR
FLTR
FLTR
FLTR
FLTR
base_item_type
filter_clause
filter_name
is_default
master_key
project_name
sys_item_type
table_name
char
long varchar
char
smallint
char
char
char
char
4
32767
23
2
26
8
4
20
0
0
0
0
0
0
0
0
Generate (Base)
Table
Column Name
Data Type
Length
Decimals
DMAP
DMAP
DMAP
DMAP
DMAP
DMAP
map_depth
map_entry_type
source_field
source_item
target_field
target_item
char
char
char
char
char
char
16
5
128
4
64
4
0
0
0
0
0
0
FMAP
FMAP
FMAP
FMAP
FMAP
map_set_name
source_field
source_item
target_field
target_item
char
char
char
char
char
4
64
4
64
4
0
0
0
0
0
InBasket Module (Base)

Table
Column Name
Data Type
Length
Decimals
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
ball_in_court
ball_in_court_ini
base_item_type
base_item_type_sys
base_master_key
base_parent_key
comments
completion_date
date_received
date_sent
description
entered_by
from_vendor
from_vendor_ini
has_been_read
item_date
item_number
item_status
item_type
last_edit_by
last_edit_date
log_number
mail_label_file
master_key
next_step
char
char
char
char
char
char
long varchar
date
date
date
char
char
char
char
smallint
date
char
char
char
char
timestamp
char
char
char
char
8
3
4
4
26
26
32767
4
4
4
80
3
8
3
2
4
12
4
4
8
8
20
254
26
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
BASK
project_name
receipt_requested
recipient_user_name
ref_activity_id
response_date
restricted_to
security_flag
sender_project
sender_user_name
sender_vendor
sender_vendor_ini
spec_section
start_date
status
sys_item_type
time_added
time_sent
to_vendor
to_vendor_ini
value
char
smallint
char
char
date
char
char
char
char
char
char
char
date
char
char
char
char
char
char
numeric
8
2
8
16
4
8
1
8
8
8
3
10
4
4
4
8
8
8
3
17
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
Insurance Module (Base)

Table
Column Name
Data Type
Length
Decimals
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
ball_in_court
ball_in_court_ini
cntr_from_vndr
cntr_from_vndr_ini
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
insurance_company
insurance_reqd
insurance_vndr
insurance_vndr_ini
insured_vendor
item_type
last_edit_by
last_edit_date
master_key
next_step
parent_key
policy_effect_date
policy_expires
policy_limit
policy_number
char
char
char
char
char
char
char
date
char
char
char
smallint
char
char
char
char
char
timestamp
char
char
char
date
date
char
char
8
3
8
3
4
8
3
4
12
4
36
2
8
3
8
4
8
8
26
8
26
4
4
36
36
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
INSR
policy_type
project_name
ref_activity_id
remarks
restricted_to
security_flag
start_date
status
sys_item_type
char
char
char
long varchar
char
char
date
char
char
36
8
16
32767
8
1
4
4
4
0
0
0
0
0
0
0
0
0
Invoices Module (Base)

Table
Column Name
Data Type
Length
Decimals
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
INVC
amount
amount_paid
ball_in_court
ball_in_court_ini
check_number
completion_date
distributed_to
invoice_date
invoice_title
item_type
last_edit_by
last_edit_date
master_key
next_step
number
parent_key
payment_date
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
start_date
status
sys_item_type
numeric
numeric
char
char
char
date
char
date
char
char
char
timestamp
char
char
char
char
date
char
char
char
char
char
date
char
char
17
17
8
3
12
4
16
4
80
4
8
8
26
8
12
26
4
8
16
20
1
8
4
4
4
3
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Issues Module (Base)

Table
Column Name
Data Type
Length
Decimals
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
ISDT
base_item_type
base_master_key
base_parent_key
base_sys_item_type
comments
date_linked
description
entered_by
from_vendor
from_vendor_ini
issue_name
item_date
item_number
item_status
item_type
log_number
master_key
parent_key
project_name
response_date
spec_section
sys_item_type
time_added
to_vendor
to_vendor_ini
char
char
char
char
long varchar
date
char
char
char
char
char
date
char
char
char
char
char
char
char
date
char
char
char
char
char
4
26
26
4
32767
4
27
3
8
3
6
4
12
4
4
10
26
26
8
4
10
4
8
8
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
ISDT
ISDT
ISDT
type_flag
user_name
value
integer
char
numeric
4
8
17
0
0
2
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ISMT
ball_in_court
ball_in_court_ini
change_issu_flag
completion_date
contract_number
date_closed
date_opened
issue_name
issue_number
issue_title
item_type
last_edit_by
last_edit_date
master_key
next_step
project_name
ref_activity_id
restricted_to
security_flag
start_date
status
sys_item_type
char
char
smallint
date
char
date
date
char
char
char
char
char
timestamp
char
char
char
char
char
char
date
char
char
8
3
2
4
12
4
4
6
5
49
4
8
8
26
8
8
16
8
1
4
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Item Descriptions (View)

Table
Column Name
Data Type
Length
Decimals
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
access_area
acronym
auto_increment_fld
blank_key_fields_allowed
can_have_attachments
can_have_costing
can_have_issues
can_have_p3
can_modify_initialize
category_name
child_items
contact_security_fields
cost_distribution_columns
custom_data_allowed
delete_with_project
description
dialog_title
document_form_file
document_sheet
document_to_print
exp_dba_table_name
fields_to_update_on_itemchanged
first_edit_field_on_detail
has_status_inspector
icon_title
char
char
char
char
smallint
smallint
smallint
smallint
smallint
char
char
char
char
smallint
smallint
char
char
char
char
char
char
char
char
smallint
char
4
4
40
127
2
2
2
2
2
4
30
254
80
2
2
30
30
254
30
80
30
254
254
2
30
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
in_use
is_primary
is_user_defined
is_user_modifiable
item_to_link
item_type
log_sheet
log_title
master_key
module_name
nonedit_key_fields
not_currently_operable
number_of_tabs
parent_items
parent_key_fields
report_file
report_to_print
shared_data_windows
sys_acronym
sys_description
sys_item_type
tab_sheet_names
tab_sheet_windows
table_name
title_field_list
unique_key_fields
unique_visible_key
vndr_ini_swap_flds
smallint
smallint
smallint
smallint
char
char
char
char
char
char
char
smallint
smallint
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
2
2
2
2
4
4
30
30
26
4
127
2
2
10
80
254
80
127
4
30
4
254
254
30
127
80
127
254
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
ITEM_MODL
ITEM_MODL
ITEM_MODL
ITEM_MODL
ITEM_MODL
ITEM_MODL
ITEM_MODL
ITEM_MODL
ITEM_MODL
ITEM_MODL
ITEM_MODL
acronym
description
document_sheet
item_type
log_sheet
log_title
master_key
modl_description
sys_acronym
sys_description
sys_item_type
char
char
char
char
char
char
char
char
char
char
char
4
30
30
4
30
30
26
30
4
30
4
0
0
0
0
0
0
0
0
0
0
0
Item Descriptions (Base)

Table
Column Name
Data Type
Length
Decimals
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
access_area
acronym
auto_increment_fld
backup_order
blank_key_fields_allowed
can_have_attachments
can_have_costing
can_have_issues
can_have_p3
can_modify_initialize
category_name
child_items
contact_security_fields
cost_distribution_columns
custom_data_allowed
delete_with_project
description
dialog_title
document_form_file
document_sheet
document_to_print
exp_dba_table_name
fields_to_update_on_itemchanged
first_edit_field_on_detail
has_status_inspector
char
char
char
integer
char
smallint
smallint
smallint
smallint
smallint
char
char
char
char
smallint
smallint
char
char
char
char
char
char
char
char
smallint
4
4
40
4
127
2
2
2
2
2
4
30
254
80
2
2
30
30
254
30
80
30
254
254
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
ITEM_TABLE
icon_title
in_use
is_primary
is_user_defined
is_user_modifiable
item_to_link
item_type
log_sheet
log_title
master_key
module_name
nonedit_key_fields
not_currently_operable
number_of_tabs
parent_items
parent_key_fields
report_file
report_to_print
shared_data_windows
sys_acronym
sys_description
sys_item_type
tab_sheet_names
tab_sheet_windows
table_name
title_field_list
unique_key_fields
unique_visible_key
char
smallint
smallint
smallint
smallint
char
char
char
char
char
char
char
smallint
smallint
char
char
char
char
char
char
char
char
char
char
char
char
char
char
30
2
2
2
2
4
4
30
30
26
4
127
2
2
10
80
254
80
127
4
30
4
254
254
30
127
80
127
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
ITEM_TABLE
vndr_ini_swap_flds
char
254
Letters Module (Base)

Table
Column Name
Data Type
Length
Decimals
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
ball_in_court
ball_in_court_ini
base_item_type
base_master_key
base_parent_key
base_sys_item_type
by_user
carbon_copy
completion_date
contract_number
correspond_date
correspond_time
cost
description
enclosures
from_vendor
from_vendor_ini
item_date
item_status
item_type
last_edit_by
last_edit_date
log_number
logged_by
master_key
char
char
char
char
char
char
smallint
char
date
char
date
char
numeric
char
char
char
char
date
char
char
char
timestamp
char
char
char
8
3
4
26
26
4
2
36
4
12
4
8
17
80
36
8
3
4
4
4
8
8
20
3
26
0
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
LTTR
next_step
number
project_name
ref_activity_id
remarks
response_date
restricted_to
security_flag
spec_section
start_date
status
subject
sys_item_type
to_vendor
to_vendor_ini
type_flag
user_name
char
char
char
char
long varchar
date
char
char
char
date
char
char
char
char
char
integer
char
8
12
8
16
32767
4
8
1
10
4
4
36
4
8
3
4
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Mail (View)
Table
Column Name
Data Type
Length
Decimals
VMAL
VMAL
VMAL
VMAL
VMAL
VMAL
VMAL
VMAL
VMAL
VMAL
VMAL
VMAL
code
company_name
first_name
initials
last_name
mail_address
mail_address_in_db
mail_method
master_key
name
project_name
vendor_initials
char
char
char
char
long varchar
char
char
smallint
char
char
char
varchar
8
36
22
3
32767
254
254
2
26
22
8
12
0
0
0
0
0
0
0
0
0
0
0
0
Mail (Base)
Table
Column Name
Data Type
Length
Decimals
MMAP
MMAP
MMAP
MMAP
MMAP
MMAP
MMAP
MMAP
MMAP
MMAP
MMAP
master_key
our_project_name
our_username
our_vendor
our_vendor_ini
person_name
their_group
their_project_name
their_username
their_vendor
their_vendor_ini
char
char
char
char
char
char
char
char
char
char
char
26
8
8
8
3
22
254
8
8
8
3
0
0
0
0
0
0
0
0
0
0
0
MMLU
MMLU
MMLU
MMLU
MMLU
MMLU
master_key
person_name
project_name
username
vendor
vendor_ini
char
char
char
char
char
char
26
22
8
8
8
3
0
0
0
0
0
0
eml_name
eml_path
item_type
master_key
project
char
char
char
char
char
11
255
4
26
4
0
0
0
0
0
Mail Queue
mail_queue
mail_queue
mail_queue
mail_queue
mail_queue
Table
Column Name
Data Type
Length
Decimals
mail_queue
mail_queue
mail_queue
mail_queue
mail_queue
recipients
remarks
sys_item_type
title
username
long varchar
long varchar
char
char
char
32767
32767
4
100
8
0
0
0
0
0
Materials Delivery (View)

Table
Column Name
Data Type
Length
Decimals
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
ball_in_court
ball_in_court_ini
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
currency_type
delivered_to
delivered_to_ini
do_update
exchange_ptr
final_delivery
first_delivery
item_type
last_edit_by
last_edit_date
master_key
material_name
material_title
next_step
char
char
char
char
char
char
char
char
date
char
char
char
char
char
smallint
integer
date
date
char
char
timestamp
char
char
char
char
8
3
8
3
26
4
8
3
4
12
4
4
8
3
2
4
4
4
4
8
8
26
12
80
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
ordered_from
ordered_from_ini
project_name
qty_amendment
qty_contract
qty_delivered
qty_not_req
quantity_balance
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
req_contr_from
req_contr_from_ini
req_contr_number
req_contr_sys_type
req_contr_to
req_contr_to_ini
req_contract_type
req_item_number
restricted_to
security_flag
spec_section
start_date
status
sys_item_type
tot_cost_balance
tot_cost_cntract
char
char
char
numeric
numeric
numeric
numeric
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
date
char
char
numeric
numeric
8
3
8
17
17
17
17
19
16
20
1
8
8
3
12
4
8
3
4
10
8
1
10
4
4
4
32
30
0
0
0
3
3
3
3
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
6
6
Table
Column Name
Data Type
Length
Decimals
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
MDMT
tot_cost_not_req
total_cost_amdmt
total_cost_dlvrd
unit_cost_amdmt
unit_cost_cntrct
units_amendment
units_contract
numeric
numeric
numeric
numeric
numeric
char
char
17
30
17
19
19
9
9
2
6
2
5
5
0
0
Materials Delivery (Base)

Table
Column Name
Data Type
Length
Decimals
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
ball_in_court
ball_in_court_ini
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
date_received
delivered_to
delivery_time
description
dyrt_parent_key
item_type
location
master_key
material_name
next_step
parent_key
project_name
quantity
ref_activity_id
char
char
char
char
char
char
char
char
date
char
char
date
char
char
char
char
char
char
char
char
char
char
char
numeric
char
8
3
8
3
26
4
8
3
4
12
4
4
8
8
11
26
4
14
26
12
8
26
8
17
16
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
Table
Column Name
Data Type
Length
Decimals
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
MDDT
remark
report_period
req_date
start_date
status
sys_item_type
ticket_no
long varchar
char
date
date
char
char
char
32767
16
4
4
4
4
10
0
0
0
0
0
0
0
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
ball_in_court
ball_in_court_ini
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
currency_type
delivered_to
delivered_to_ini
do_update
exchange_ptr
final_delivery
first_delivery
item_type
last_edit_by
char
char
char
char
char
char
char
char
date
char
char
char
char
char
smallint
integer
date
date
char
char
8
3
8
3
26
4
8
3
4
12
4
4
8
3
2
4
4
4
4
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
last_edit_date
master_key
material_name
material_title
next_step
ordered_from
ordered_from_ini
project_name
qty_amendment
qty_contract
qty_delivered
qty_not_req
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
req_contr_from
req_contr_from_ini
req_contr_number
req_contr_sys_type
req_contr_to
req_contr_to_ini
req_contract_type
req_item_number
restricted_to
security_flag
spec_section
start_date
timestamp
char
char
char
char
char
char
char
numeric
numeric
numeric
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
date
8
26
12
80
8
8
3
8
17
17
17
17
16
20
1
8
8
3
12
4
8
3
4
10
8
1
10
4
0
0
0
0
0
0
0
0
3
3
3
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
MDMT_TABLE
status
sys_item_type
tot_cost_not_req
total_cost_dlvrd
unit_cost_amdmt
unit_cost_cntrct
units_amendment
units_contract
char
char
numeric
numeric
numeric
numeric
char
char
4
4
17
17
19
19
9
9
0
0
2
2
5
5
0
0
Meeting Minutes Module (Base)

Table
Column Name
Data Type
Length
Decimals
MMAT
MMAT
MMAT
MMAT
MMAT
MMAT
MMAT
MMAT
MMAT
MMAT
MMAT
attendee_name
attendee_vendor
attendee_vendor_ini
company_name
did_attend
item_type
master_key
order_number
parent_key
project_name
sys_item_type
char
char
char
char
smallint
char
char
char
char
char
char
22
8
3
36
2
4
26
12
26
8
4
0
0
0
0
0
0
0
0
0
0
0
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
ball_in_court
ball_in_court_ini
Bid_Package
completion_date
date_due
description
item_number
item_type
last_edit_by
last_edit_date
master_key
next_step
order_number
char
char
char
date
date
long varchar
char
char
char
timestamp
char
char
char
8
3
9
4
4
32767
10
4
8
8
26
8
12
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
MMDT
org_meeting_num
parent_key
project_name
ref_activity_id
restricted_to
security_flag
start_date
status
sys_item_type
char
char
char
char
char
char
date
char
char
5
26
8
16
8
1
4
4
4
0
0
0
0
0
0
0
0
0
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
MMMT
contract_number
item_type
last_edit_by
last_edit_date
master_key
meeting_date
meeting_location
meeting_number
meeting_subject
meeting_time
project_name
restricted_to
security_flag
sys_item_type
char
char
char
timestamp
char
date
char
char
char
char
char
char
char
char
12
4
8
8
26
4
50
5
50
8
8
8
1
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Notepads Module (Base)

Table
Column Name
Data Type
Length
Decimals
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
NPDT
ball_in_court
ball_in_court_ini
csi_reference
date_closed
date_opened
date_required
Fine
item_number
item_type
last_edit_by
last_edit_date
master_key
next_step
note_pad
notes
osha_reference
parent_key
Priority
project_name
ref_activity_id
restricted_to
safety_category
Safety_Source
security_flag
status
char
char
char
date
date
date
numeric
char
char
char
timestamp
char
char
char
long varchar
char
char
char
char
char
char
char
char
char
char
8
3
10
4
4
4
17
5
4
8
8
26
8
8
32767
10
26
8
8
16
8
10
10
1
4
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
NPDT
sys_item_type
char
NPMT
NPMT
NPMT
NPMT
NPMT
NPMT
NPMT
NPMT
NPMT
NPMT
NPMT
contract_number
description
item_type
last_edit_by
last_edit_date
master_key
note_pad
project_name
restricted_to
security_flag
sys_item_type
char
char
char
char
timestamp
char
char
char
char
char
char
12
79
4
8
8
26
8
8
8
1
4
0
0
0
0
0
0
0
0
0
0
0
Notices Module (Base)

Table
Column Name
Data Type
Length
Decimals
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
approved_date
ball_in_court
ball_in_court_ini
Bid_Package
cedt_master_key
cemt_master_key
cemt_number
change_date
change_issue
change_number
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
cost
currency_type
distributed_to
exchange_ptr
from_manager
from_vendor
date
char
char
char
char
char
char
date
char
char
char
char
char
char
char
char
date
char
char
numeric
char
char
integer
char
char
4
8
3
9
26
26
12
4
6
8
8
3
26
4
8
3
4
12
4
17
4
16
4
22
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
from_vendor_ini
has_completed
has_started
item_type
last_edit_by
last_edit_date
master_key
next_step
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_from_abbrev
ref_from_abbrev_ini
ref_number
ref_resource
ref_sys_type
ref_to_abbrev
ref_to_abbrev_ini
ref_type
remarks
required_date
responded_date
restricted_to
security_flag
spec_section
start_date
status
char
smallint
smallint
char
char
timestamp
char
char
char
char
char
char
char
char
char
char
char
char
char
char
long varchar
date
date
char
char
char
date
char
3
2
2
4
8
8
26
8
8
16
12
1
8
3
8
8
4
8
3
4
32767
4
4
8
1
10
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CNTE
CNTE
CNTE
CNTE
CNTE
CNTE
sys_item_type
time_change
title
to_manager
to_vendor
to_vendor_ini
char
integer
char
char
char
char
4
4
35
22
8
3
0
0
0
0
0
0
Paper Sizes (Base)

Table
Column Name
Data Type
Length
Decimals
PAPER_SIZE_TABLE
PAPER_SIZE_TABLE
PAPER_SIZE_TABLE
PAPER_SIZE_TABLE
PAPER_SIZE_TABLE
PAPER_SIZE_TABLE
PAPER_SIZE_TABLE
Item_Type
Master_Key
order_code
Paper_Size
Project_Name
Size_Description
Sys_Item_Type
char
char
char
char
char
char
char
4
26
2
15
8
36
4
0
0
0
0
0
0
0
Project Preferences (Base)

Table
Column Name
Data Type
Length
Decimals
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
add_dunning_to_sent_log
ce_bdgt_estimated_cost_area
ce_bdgt_estimated_doc_type
ce_bdgt_final_cost_area
ce_bdgt_final_doc_type
ce_bdgt_negotiated_cost_area
ce_bdgt_negotiated_doc_type
ce_bdgt_quoted_cost_area
ce_bdgt_quoted_doc_type
ce_cmmt_estimated_cost_area
ce_cmmt_estimated_doc_type
ce_cmmt_final_cost_area
ce_cmmt_final_doc_type
ce_cmmt_negotiated_cost_area
ce_cmmt_negotiated_doc_type
ce_cmmt_quoted_cost_area
ce_cmmt_quoted_doc_type
ce_roll_cmmt_into_bdgt
inv_auto_fill_distribute
item_type
last_edit_by
last_edit_date
letters_template
lttr_close
lttr_logo_file_name
smallint
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
smallint
smallint
char
char
timestamp
long varchar
char
char
2
16
4
16
4
16
4
16
4
16
4
16
4
16
4
16
4
2
2
4
8
8
32767
36
255
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
PREF_TABLE
lttr_margin_bottom
lttr_margin_left
lttr_margin_right
lttr_margin_top
lttr_salutation
lttr_typed_by
master_key
project_name
sys_item_type
numeric
numeric
numeric
numeric
char
char
char
char
char
5
5
5
5
36
12
26
8
4
2
2
2
2
0
0
0
0
0
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
add_dunning_to_sent_log
allow_over_budget
architect
architect_abbrev
ball_in_court
ball_in_court_ini
company_abbrev
company_name
company_role
completion_date
contract_date
contract_title
dai_use_abbrev_to_get_p3_data
description
display_proj_summary_on_open
exp_proj_owner
smallint
smallint
char
char
char
char
numeric
numeric
char
char
char
date
date
char
smallint
long varchar
smallint
char
2
2
36
8
8
3
17
17
8
36
4
4
4
36
2
32767
2
8
0
0
0
0
0
0
3
3
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
finish_date
gen_contr_abbrev
general_contr
inv_auto_fill_distribute
item_type
job_number
last_edit_by
last_edit_date
made_from_demo
master_key
must_cost_contracts_pos
next_step
no_nocost_contracts_pos
owner_abbrev
owner_name
p3_data_date
p3_early_finish
p3_proj_finish
p3_proj_start
p3_proj_title
p3_version
perspective_proj
Primary_submittal_contact
proceed_date
project_manager
project_name
project_name_vendor_link
project_number
date
char
char
smallint
char
char
char
timestamp
smallint
char
smallint
char
smallint
char
char
date
date
date
date
char
char
char
char
date
char
char
char
char
4
8
36
2
4
36
8
8
2
26
2
8
2
8
36
4
4
4
4
36
16
8
36
4
36
8
8
36
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
PROJ
project_title
project_value
ref_activity_id
refresh_after_add_delete
req_first_line_item
restricted_to
sched_data_extn
sched_data_path
sched_data_proj
sched_subproj_id
security_flag
site_location
start_date
status
sys_item_type
tran_combine_vendors
tran_make_from_dist
tran_make_from_rev
tran_print_during_create
unique_cont_number
unique_purch_number
update_group_from_project
use_detail_pct_tax
char
numeric
smallint
char
smallint
char
numeric
char
smallint
char
char
char
char
char
numeric
char
date
char
char
smallint
smallint
smallint
smallint
smallint
smallint
smallint
smallint
smallint
36
17
2
16
2
10
17
8
2
3
254
8
2
1
17
36
4
4
4
2
2
2
2
2
2
2
2
2
0
2
0
0
0
0
3
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
PROJ
PROJ
PROJ
PROJ
PROJ
use_pct_of_work
vendor_add_to_group
vendor_to_use
version_num
smallint
smallint
smallint
char
char
2
2
2
8
8
0
0
0
0
0
Proposals Module (View)

Table
Column Name
Data Type
Length
Decimals
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
CPDT
ball_in_court
ball_in_court_ini
Bid_Package
completion_date
description
item_number
item_type
master_key
material_code
net_amount
next_step
parent_key
project_name
quantity
ref_activity_id
ref_cost_account
ref_cost_category
ref_item_num
ref_resource
sales_tax
sales_tax_rate
start_date
status
stock_number
sys_item_type
char
char
char
date
long varchar
char
char
char
char
numeric
char
char
char
numeric
char
char
char
char
char
numeric
numeric
date
char
char
char
8
3
9
4
32767
5
4
26
12
30
8
26
8
17
16
12
1
10
8
17
19
4
4
30
4
0
0
0
0
0
0
0
0
0
6
0
0
0
3
0
0
0
0
0
3
5
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CPDT
CPDT
unit_price
units
numeric
char
19
9
5
0
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
approved_date
approved_date2
ball_in_court
ball_in_court_ini
Bid_Package
cedt_master_key
cemt_master_key
cemt_number
change_date
change_issue
change_number
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
cost
currency_type
distributed_to
exchange_ptr
from_manager
date
date
char
char
char
char
char
char
date
char
char
char
char
char
char
char
char
date
char
char
numeric
char
char
integer
char
4
4
8
3
9
26
26
12
4
6
8
8
3
26
4
8
3
4
12
4
20
4
16
4
22
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
from_vendor
from_vendor_ini
has_completed
has_started
is_approved
is_latest
item_type
last_edit_by
last_edit_date
lump_cost
lump_tax
lump_tax_rate
master_key
next_step
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_from_abbrev
ref_from_abbrev_ini
ref_number
ref_resource
ref_sys_type
ref_to_abbrev
ref_to_abbrev_ini
ref_type
remarks
required_date
char
char
smallint
smallint
smallint
smallint
char
char
timestamp
numeric
numeric
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
char
long varchar
date
8
3
2
2
2
2
4
8
8
17
17
19
26
8
8
16
12
1
8
3
8
8
4
8
3
4
32767
4
0
0
0
0
0
0
0
0
0
3
3
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
CPMT
responded_date
restricted_to
security_flag
signed_by1
signed_by2
spec_section
start_date
status
sys_item_type
time_change
title
to_manager
to_vendor
to_vendor_ini
total_sales_tax
unit_cost
unit_tax
vendor_role
date
char
char
char
char
char
date
char
char
integer
char
char
char
char
numeric
numeric
numeric
char
4
8
1
22
22
10
4
4
4
4
35
22
8
3
18
17
17
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
3
3
0
Proposals Module (Base)

Table
Column Name
Data Type
Length
Decimals
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
CPDT_TABLE
ball_in_court
ball_in_court_ini
Bid_Package
completion_date
description
item_number
item_type
master_key
material_code
next_step
parent_key
project_name
quantity
ref_activity_id
ref_cost_account
ref_cost_category
ref_item_num
ref_resource
sales_tax
sales_tax_rate
start_date
status
stock_number
sys_item_type
unit_price
char
char
char
date
long varchar
char
char
char
char
char
char
char
numeric
char
char
char
char
char
numeric
numeric
date
char
char
char
numeric
8
3
9
4
32767
5
4
26
12
8
26
8
17
16
12
1
10
8
17
19
4
4
30
4
19
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
3
5
0
0
0
0
5
Table
Column Name
Data Type
Length
Decimals
CPDT_TABLE
units
char
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
approved_date
approved_date2
ball_in_court
ball_in_court_ini
Bid_Package
cedt_master_key
cemt_master_key
cemt_number
change_date
change_issue
change_number
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
currency_type
distributed_to
exchange_ptr
from_manager
from_vendor
from_vendor_ini
date
date
char
char
char
char
char
char
date
char
char
char
char
char
char
char
char
date
char
char
char
char
integer
char
char
char
4
4
8
3
9
26
26
12
4
6
8
8
3
26
4
8
3
4
12
4
4
16
4
22
8
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
has_completed
has_started
is_approved
is_latest
item_type
last_edit_by
last_edit_date
lump_cost
lump_tax
lump_tax_rate
master_key
next_step
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_from_abbrev
ref_from_abbrev_ini
ref_number
ref_resource
ref_sys_type
ref_to_abbrev
ref_to_abbrev_ini
ref_type
remarks
required_date
responded_date
restricted_to
smallint
smallint
smallint
smallint
char
char
timestamp
numeric
numeric
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
char
long varchar
date
date
char
2
2
2
2
4
8
8
17
17
19
26
8
8
16
12
1
8
3
8
8
4
8
3
4
32767
4
4
8
0
0
0
0
0
0
0
3
3
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
CPMT_TABLE
security_flag
signed_by1
signed_by2
spec_section
start_date
status
sys_item_type
time_change
title
to_manager
to_vendor
to_vendor_ini
unit_cost
unit_tax
vendor_role
char
char
char
char
date
char
char
integer
char
char
char
char
numeric
numeric
char
1
22
22
10
4
4
4
4
35
22
8
3
17
17
4
0
0
0
0
0
0
0
0
0
0
0
0
3
3
0
Punch List Module (Base)

Table
Column Name
Data Type
Length
Decimals
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
PNDT
ball_in_court
ball_in_court_ini
Bid_Package
currency_type
date_closed
date_opened
date_required
description
exchange_ptr
item_number
item_type
last_edit_by
last_edit_date
location
master_key
next_step
parent_key
project_name
ref_activity_id
restricted_to
security_flag
status
sys_item_type
value
char
char
char
char
date
date
date
long varchar
integer
char
char
char
timestamp
char
char
char
char
char
char
char
char
char
char
numeric
8
3
9
4
4
4
4
32767
4
5
4
8
8
35
26
8
26
8
16
8
1
4
4
17
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
Table
Column Name
Punch List Items
Data Type
Length
Decimals
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
PNMT
char
char
char
char
char
timestamp
char
char
char
char
char
char
char
char
char
char
numeric
12
8
3
4
8
8
50
26
8
8
8
1
22
4
8
3
17
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
contract_number
from_vendor
from_vendor_ini
item_type
last_edit_by
last_edit_date
long_descrpt
master_key
project_name
punch_list_name
restricted_to
security_flag
short_descrpt
sys_item_type
to_vendor
to_vendor_ini
total
Purchase Orders Module (View)

Table
Column Name
Data Type
Length
Decimals
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
accepted
accepted_by1
accepted_by2
accepted_date1
accepted_date2
allow_over_budget
approved_changes
balance
ball_in_court
ball_in_court_ini
bill_add_line_1
bill_add_line_2
bill_add_line_3
bill_city
bill_company
bill_country
bill_country_code
bill_postal_code
bill_state
bill_vndr_abbrev
cedt_master_key
cemt_master_key
smallint
char
char
date
date
smallint
numeric
numeric
char
char
char
char
char
char
char
char
char
char
char
char
char
numeric
numeric
char
char
2
22
22
4
4
2
17
23
8
3
36
36
36
28
36
30
10
15
30
8
3
17
17
26
26
0
0
0
0
0
0
3
3
0
0
0
0
0
0
0
0
0
0
0
0
0
3
3
0
0
Table
Column Name
Data Type
Length
Decimals
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
cemt_number
completion_date
currency_type
dbe
description
distributed_to
document_date
document_number
exchange_ptr
fob_via
freight
from_add_line_1
from_add_line_2
from_add_line_3
from_city
from_company
from_country
from_country_code
from_postal_code
from_state
from_vendor
from_vendor_ini
has_completed
has_started
inv_to_date
item_type
last_edit_by
last_edit_date
char
date
char
smallint
char
char
date
char
integer
char
numeric
char
char
char
char
char
char
char
char
char
char
char
smallint
smallint
numeric
char
char
timestamp
12
4
4
2
80
16
4
12
4
30
17
36
36
36
28
36
30
10
15
30
8
3
2
2
17
4
8
8
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
Table
Column Name
Data Type
Length
Decimals
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
last_item_number
lump_cost
lump_tax
lump_tax_rate
managers_name
master_key
mbe
net_cost
next_step
num_approv_chng
pending_changes
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
reference_number
remarks
req_first_line_item
req_to_date
restricted_to
revisd_cmpl_date
revised_cntr_sum
security_flag
char
numeric
numeric
numeric
char
char
smallint
numeric
char
integer
numeric
char
smallint
char
char
char
char
char
long varchar
char
numeric
numeric
char
smallint
date
numeric
char
numeric
10
17
17
19
30
26
2
18
8
4
17
8
2
16
20
1
8
30
32767
10
17
17
8
2
4
21
1
17
0
3
3
5
0
0
0
3
0
0
3
0
0
0
0
0
0
0
0
0
3
3
0
0
0
3
0
3
Table
Column Name
Data Type
Length
Decimals
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
ship_add_line_1
ship_add_line_2
ship_add_line_3
ship_city
ship_company
ship_country
ship_country_code
ship_postal_code
ship_state
ship_vndr_abbrev
spec_section
start_date
status
sys_item_type
terms
to_add_line_1
to_add_line_2
to_add_line_3
to_city
to_company
to_country
to_country_code
to_postal_code
to_state
to_vendor
to_vendor_ini
total_cost
char
char
char
char
char
char
char
char
char
char
char
char
date
char
char
char
char
char
char
char
char
char
char
char
char
char
char
numeric
36
36
36
28
36
30
10
15
30
8
3
10
4
4
4
30
36
36
36
28
36
30
10
15
30
8
3
20
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
Table
Column Name
Data Type
Length
Decimals
POMT
POMT
POMT
POMT
POMT
POMT
POMT
POMT
total_sales_tax
unit_cost
unit_tax
use_detail_pct_tax
use_pct_of_work
wbe
numeric
numeric
numeric
smallint
smallint
smallint
smallint
smallint
18
17
17
2
2
2
2
2
3
3
3
0
0
0
0
0
Requests Module (Base)

Table
Column Name
Data Type
Length
Decimals
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
answer
approved_date
approved_date2
ball_in_court
ball_in_court_ini
Bid_Package
cedt_master_key
cemt_master_key
cemt_number
change_date
change_issue
change_number
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
cost
currency_type
distributed_to
exchange_ptr
long varchar
date
date
char
char
char
char
char
char
date
char
char
char
char
char
char
char
char
date
char
char
numeric
char
char
integer
32767
4
4
8
3
9
26
26
12
4
6
8
8
3
26
4
8
3
4
12
4
17
4
16
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
Table
Column Name
Data Type
Length
Decimals
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
from_manager
from_vendor
from_vendor_ini
has_completed
has_started
item_type
last_edit_by
last_edit_date
master_key
next_step
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_from_abbrev
ref_from_abbrev_ini
ref_number
ref_resource
ref_sys_type
ref_to_abbrev
ref_to_abbrev_ini
ref_type
remarks
required_date
responded_date
restricted_to
security_flag
signed_by1
char
char
char
smallint
smallint
char
char
timestamp
char
char
char
char
char
char
char
char
char
char
char
char
char
char
long varchar
date
date
char
char
char
22
8
3
2
2
4
8
8
26
8
8
16
12
1
8
3
8
8
4
8
3
4
32767
4
4
8
1
22
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
CRQT
signed_by2
spec_section
start_date
status
sys_item_type
time_change
title
to_manager
to_vendor
to_vendor_ini
char
char
date
char
char
integer
char
char
char
char
22
10
4
4
4
4
35
22
8
3
0
0
0
0
0
0
0
0
0
0
Requisitions Module (View)

Table
Column Name
Data Type
Length
Decimals
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
balance
ball_in_court
ball_in_court_ini
completion_date
description
distributed_to
item_type
master_key
next_step
parent_key
percent_complete
percent_tax
prev_applcations
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
ref_update_item_num
req_detail_type
req_item_no
retain_amt
retain_pct
sales_tax
scheduled_value
numeric
char
char
date
char
char
char
char
char
char
numeric
numeric
numeric
char
char
char
char
char
char
integer
char
numeric
numeric
numeric
numeric
20
8
3
4
60
16
4
26
8
26
17
17
17
8
16
20
1
8
10
4
10
17
17
30
17
3
0
0
0
0
0
0
0
0
0
3
3
3
0
0
0
0
0
0
0
0
3
5
6
3
Table
Column Name
Data Type
Length
Decimals
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
RQDT
start_date
status
strd_not_in_d_e
sys_item_type
this_period
total_complete
unit_price
unit_type
was_from_3_0
date
char
numeric
char
numeric
numeric
numeric
char
smallint
4
4
17
4
17
19
19
6
2
0
0
3
0
3
3
5
0
0
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
amount_certified
application
application_no
balance_plus_ret
ball_in_court
ball_in_court_ini
certification
certified
certified_by
certified_date
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
complted_to_date
numeric
long varchar
char
numeric
char
char
long varchar
char
char
date
char
char
char
char
char
char
date
numeric
17
32767
5
21
8
3
32767
36
22
4
8
3
26
4
8
3
4
19
3
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
3
Table
Column Name
Data Type
Length
Decimals
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
contract_number
contract_type
contractor
contractor_by
contractor_date
currency_type
distributed_to
earned_minus_ret
exchange_ptr
from_a_contract
from_company
from_vendor
from_vendor_ini
is_certified
it_is_the_latest
item_type
last_edit_by
last_edit_date
master_key
net_change
next_step
orig_contrct_sum
payment_due
percent_complete
period_to
prev_additions
prev_amount_cert
prev_deductions
char
char
char
char
date
char
char
numeric
integer
smallint
char
char
char
smallint
smallint
char
char
timestamp
char
numeric
char
numeric
numeric
numeric
date
numeric
numeric
numeric
12
4
36
22
4
4
16
20
4
2
36
8
3
2
2
4
8
8
26
19
8
17
21
30
4
17
17
17
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
3
0
3
3
8
0
3
3
3
Table
Column Name
Data Type
Length
Decimals
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
RQMT
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
restricted_to
retain_completed_amt
retain_completed_pct
retain_stored_amt
retain_stored_pct
retain_total_amt
sales_tax_to_date
security_flag
start_date
status
sub_total_addtns
sub_total_ddctns
sum_to_date
sys_item_type
to_company
to_vendor
to_vendor_ini
total_additions
total_balance
total_deductions
total_detail_ret
total_detail_tax
total_percent
char
char
char
char
char
char
numeric
numeric
numeric
numeric
numeric
numeric
char
date
char
numeric
numeric
numeric
char
char
char
char
numeric
numeric
numeric
numeric
numeric
numeric
8
16
20
1
8
8
17
17
17
17
17
17
1
4
4
17
17
20
4
36
8
3
18
20
18
17
17
30
0
0
0
0
0
0
2
3
2
3
3
3
0
0
0
3
3
3
0
0
0
0
3
3
3
3
3
8
Table
Column Name
Data Type
Length
Decimals
RQMT
RQMT
RQMT
RQMT
RQMT
total_prev_appl
total_sched_valu
total_stored
totl_this_period
was_from_3_0
numeric
numeric
numeric
numeric
smallint
17
17
17
17
2
3
3
3
3
0
Requisitions Module (Base)

Table
Column Name
Data Type
Length
Decimals
RQCH
RQCH
RQCH
RQCH
RQCH
RQCH
RQCH
RQCH
RQCH
RQCH
RQCH
RQCH
additions
change_date
change_number
chng_master_key
chng_sys_item_type
deductions
item_type
master_key
parent_key
project_name
sys_item_type
title
numeric
date
char
char
char
numeric
char
char
char
char
char
char
17
4
8
26
4
17
4
26
26
8
4
35
3
0
0
0
0
3
0
0
0
0
0
0
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
ball_in_court
ball_in_court_ini
completion_date
description
distributed_to
item_type
master_key
next_step
parent_key
percent_complete
percent_tax
prev_applcations
char
char
date
char
char
char
char
char
char
numeric
numeric
numeric
8
3
4
60
16
4
26
8
26
17
17
17
0
0
0
0
0
0
0
0
0
3
3
3
Table
Column Name
Data Type
Length
Decimals
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
RQDT_TABLE
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
ref_update_item_num
req_detail_type
req_item_no
retain_amt
retain_pct
scheduled_value
start_date
status
strd_not_in_d_e
sys_item_type
this_period
unit_price
unit_type
was_from_3_0
char
char
char
char
char
char
integer
char
numeric
numeric
numeric
date
char
numeric
char
numeric
numeric
char
smallint
8
16
20
1
8
10
4
10
17
17
17
4
4
17
4
17
19
6
2
0
0
0
0
0
0
0
0
3
5
3
0
0
3
0
3
5
0
0
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
amount_certified
application
application_no
ball_in_court
ball_in_court_ini
certification
certified
certified_by
numeric
long varchar
char
char
char
long varchar
char
char
17
32767
5
8
3
32767
36
22
3
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
certified_date
cntr_from_vndr
cntr_from_vndr_ini
cntr_master_key
cntr_sys_type
cntr_to_vndr
cntr_to_vndr_ini
completion_date
contract_number
contract_type
contractor
contractor_by
contractor_date
currency_type
distributed_to
exchange_ptr
from_a_contract
from_company
from_vendor
from_vendor_ini
is_certified
it_is_the_latest
item_type
last_edit_by
last_edit_date
master_key
next_step
orig_contrct_sum
date
char
char
char
char
char
char
date
char
char
char
char
date
char
char
integer
smallint
char
char
char
smallint
smallint
char
char
timestamp
char
char
numeric
4
8
3
26
4
8
3
4
12
4
36
22
4
4
16
4
2
36
8
3
2
2
4
8
8
26
8
17
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
Table
Column Name
Data Type
Length
Decimals
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
period_to
prev_additions
prev_amount_cert
prev_deductions
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
restricted_to
retain_completed_amt
retain_completed_pct
retain_stored_amt
retain_stored_pct
retain_total_amt
sales_tax_to_date
security_flag
start_date
status
sub_total_addtns
sub_total_ddctns
sys_item_type
to_company
to_vendor
to_vendor_ini
total_detail_ret
total_detail_tax
total_prev_appl
date
numeric
numeric
numeric
char
char
char
char
char
char
numeric
numeric
numeric
numeric
numeric
numeric
char
date
char
numeric
numeric
char
char
char
char
numeric
numeric
numeric
4
17
17
17
8
16
20
1
8
8
17
17
17
17
17
17
1
4
4
17
17
4
36
8
3
17
17
17
0
3
3
3
0
0
0
0
0
0
2
3
2
3
3
3
0
0
0
3
3
0
0
0
0
3
3
3
Table
Column Name
Data Type
Length
Decimals
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
RQMT_TABLE
total_sched_valu
total_stored
totl_this_period
was_from_3_0
numeric
numeric
numeric
smallint
17
17
17
2
3
3
3
0
Roles (View)
Table
Column Name
Data Type
Length
Decimals
Role_System_Type
Role_System_Type
role_acronym
sys_role_type
char
char
4
23
0
0
Roles (Base)
Table
Column Name
Data Type
Length
Decimals
ROLE
ROLE
ROLE
ROLE
description
master_key
role_acronym
role_type_name
char
char
char
char
23
26
4
23
0
0
0
0
RTYP
RTYP
role_type_name
sys_role_type
char
char
23
23
0
0
Saved User Layouts (Base)

Table
Column Name
Data Type
Length
Decimals
USDT
USDT
USDT
USDT
USDT
datawindow
dw_syntax
table_name
user_name
window
char
long binary
char
char
char
50
32767
50
8
50
0
0
0
0
0
Security (Base)
Table
Column Name
Data Type
Length
Decimals
seca
seca
acronym
process
char
char
8
30
0
0
seci
seci
seci
seci
access
acronym
project_name
user_name
char
char
char
char
8
4
8
8
0
0
0
0
secp
secp
secp
secp
acronym
project_name
restricted_vendor
user_name
char
char
char
char
8
8
8
8
0
0
0
0
Selection Tree (Base)

Table
Column Name
Data Type
Length
Decimals
MODL
MODL
MODL
MODL
MODL
MODL
MODL
MODL
MODL
MODL
MODL
MODL
MODL
access_area
acronym
default_item
description
display_modl_in_tree
document_sheet
log_sheet
master_key
module_name
sys_acronym
sys_description
tree_description
tree_group
char
char
char
char
smallint
char
char
char
char
char
char
char
char
4
4
4
30
2
30
30
26
4
4
30
30
4
0
0
0
0
0
0
0
0
0
0
0
0
0
TREE
TREE
TREE
TREE
TREE
TREE
TREE
TREE
TREE
TREE
description
item_type
master_key
order_code
show_branch_in_tree
sys_acronym
sys_description
sys_item_type
sys_order_code
tree_name
char
char
char
integer
smallint
char
char
char
integer
char
24
4
26
4
2
4
24
4
4
4
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
TREI
TREI
TREI
TREI
TREI
TREI
TREI
TREI
TREI
TREI
TREI
TREI
TREI
item_acronym_sys
item_type
master_key
module_name
order_code
show_branch_in_tree
sys_item_type
sys_order_code
tree_branch_filter
tree_branch_name
tree_branch_name_sys
tree_name
tree_name_sys
char
char
char
char
integer
smallint
char
integer
long varchar
char
char
char
char
4
4
26
4
4
2
4
4
32767
24
24
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
Sorts (Base)
Table
Column Name
Data Type
Length
Decimals
SORT
SORT
SORT
SORT
SORT
SORT
SORT
SORT
base_item_type
is_default
master_key
project_name
sort_clause
sort_name
sys_item_type
table_name
char
smallint
char
char
long varchar
char
char
char
4
2
26
8
32767
23
4
20
0
0
0
0
0
0
0
0
Specification Sections (Base)

Table
Column Name
Data Type
Length
Decimals
SPEC
SPEC
SPEC
description
master_key
section_value
char
char
char
50
26
10
0
0
0
Status (View)
Table
Column Name
Data Type
Length
Decimals
Status_System_Type
Status_System_Type
status_acronym
sys_status_type
char
char
4
23
0
0
Status (Base)
Table
Column Name
Data Type
Length
Decimals
STAT
STAT
STAT
STAT
description
master_key
status_acronym
status_type_name
char
char
char
char
23
26
4
23
0
0
0
0
STYP
STYP
status_type_name
sys_status_type
char
char
23
23
0
0
Submittal Packages Module (View)

Table
Column Name
Data Type
Length
Decimals
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
ball_in_court
completion_date
contract_number
date_forwarded
date_received
date_returned
date_sent
forwarded_to
forwarded_to_ini
item_type
last_edit_by
last_edit_date
master_key
next_step
package_number
parent_key
project_name
received_from
received_from_ini
ref_activity_id
required_finish
required_start
returned_by
returned_by_ini
sent_to
char
date
char
date
date
date
date
char
char
char
char
timestamp
char
char
char
char
char
char
char
char
date
date
char
char
char
8
4
12
4
4
4
4
8
3
4
8
8
26
8
10
26
8
8
3
16
4
4
8
3
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBPG
SBPG
SBPG
SBPG
SBPG
SBPG
sent_to_ini
start_date
status
submittal_no
sys_item_type
title
char
date
char
char
char
char
3
4
4
15
4
35
0
0
0
0
0
0
Submittal Packages Module (Base)

Table
Column Name
Data Type
Length
Decimals
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
ball_in_court
ball_in_court_ini
Bid_Package
completion_date
contract_number
date_forwarded
date_received
date_returned
date_sent
def_forward_ori_dur
def_receive_ori_dur
def_return_ori_dur
def_sent_ori_dur
forwarded_to
forwarded_to_ini
item_type
items_appr_pkg
items_unappr_pkg
itms_submttd_pkg
last_edit_by
last_edit_date
master_key
next_step
package_number
parent_key
char
char
char
date
char
date
date
date
date
integer
integer
integer
integer
char
char
char
integer
integer
integer
char
timestamp
char
char
char
char
8
3
9
4
12
4
4
4
4
4
4
4
4
8
3
4
4
4
4
8
8
26
8
10
26
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
SBPK
pct_complete_pkg
project_name
received_from
received_from_ini
ref_activity_id
required_finish
required_start
restricted_to
returned_by
returned_by_ini
security_flag
sent_to
sent_to_ini
start_date
status
submittal_no
sys_item_type
title
total_items_pkg
numeric
char
char
char
char
date
date
char
char
char
char
char
char
date
char
char
char
char
integer
17
8
8
3
16
4
4
8
8
3
1
8
3
4
4
15
4
35
4
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Submittals Module (View)

Table
Column Name
Data Type
Length
Decimals
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
appr_activity
approval_finish
approval_lead_time
approval_start
approve_has_finished
approve_has_started
approved
ball_in_court
ball_in_court_ini
Bid_Package
code
completion_date
construction_activity
construction_finish
construction_has_finished
construction_has_started
construction_start
contract_number
days_elapsed
days_held
days_overdue
def_forward_ori_dur
def_receive_ori_dur
def_return_ori_dur
def_sent_ori_dur
char
date
integer
date
smallint
smallint
smallint
char
char
char
char
date
char
date
smallint
smallint
date
char
integer
integer
integer
integer
integer
integer
integer
16
4
4
4
2
2
2
8
3
9
12
4
16
4
2
2
4
12
4
4
4
4
4
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
delivery_actv
delivery_finish
delivery_has_finished
delivery_has_started
delivery_lead_time
delivery_start
drawing
fab_rel_activity
fab_release_fin
fab_release_lead_time
fab_release_st
fab_time
fabricate_actv
fabricate_finish
fabricate_lead_time
fabricate_start
fabstart_has_finished
fabstart_has_started
filed_app_date
filed_vendor
filed_vendor_ini
forwarded_to
forwarded_to_ini
item_number
item_type
items_in_submttl
last_date
last_edit_by
char
date
smallint
smallint
integer
date
char
char
date
integer
date
char
char
date
integer
date
smallint
smallint
date
char
char
char
char
char
char
integer
date
char
16
4
2
2
4
4
35
16
4
4
4
5
16
4
4
4
2
2
4
8
3
8
3
5
4
4
4
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
last_edit_date
latest_forward_date
latest_recvd_date
latest_return_date
latest_rev_number
latest_sent_date
master_key
next_step
package_number
parent_key
project_name
received_from
received_from_ini
ref_activity_id
release_has_finished
release_has_started
required_finish
required_start
restricted_to
resubmit_activity
resubmit_finish
resubmit_has_finished
resubmit_has_started
resubmit_lead_time
resubmit_start
returned_by
returned_by_ini
schedule_data_source
timestamp
date
date
date
char
date
char
char
char
char
char
char
char
char
smallint
smallint
date
date
char
char
date
smallint
smallint
integer
date
char
char
smallint
8
4
4
4
4
4
26
8
10
26
8
8
3
16
2
2
4
4
8
16
4
2
2
4
4
8
3
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
SBMT
second_app_code
second_app_code_ini
second_app_date
security_flag
sent_to
sent_to_ini
ship_activity
ship_finish
ship_has_finished
ship_has_started
ship_start
ship_time
source_vendor
source_vendor_ini
start_date
status
submit_act_date
submit_activity
submit_finish
submit_has_finished
submit_has_started
submit_lead_time
submit_start
submittal_no
submittal_reqd
sys_item_type
title
unsubmitted
char
char
date
char
char
char
char
date
smallint
smallint
date
char
char
char
date
char
date
char
date
smallint
smallint
integer
date
char
smallint
char
char
smallint
8
3
4
1
8
3
16
4
2
2
4
5
8
3
4
4
4
16
4
2
2
4
4
15
2
4
35
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBMT
SBMT
SBMT
user_appr_date
user_code
user_code_ini
date
char
char
4
8
3
0
0
0
SBMT_SBRV
SBMT_SBRV
SBMT_SBRV
SBMT_SBRV
project_name
sbrv_description
sbrv_revision_number
submittal_no
char
char
char
char
8
50
4
15
0
0
0
0
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
copies_prints
copies_sepias
copies_total
description
drawing_date
elpsd_cycle_time
end_date
forward_ori_dur
forwarded_date
held_begin_date
held_cycle_time
held_end_date
item_type
master_key
parent_key
project_name
receive_ori_dur
received_date
remarks
integer
integer
integer
char
date
integer
date
integer
date
date
integer
date
char
char
char
char
integer
date
long varchar
4
4
4
50
4
4
4
4
4
4
4
4
4
26
26
8
4
4
32767
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
SBRV
return_ori_dur
returned_date
review_set
reviewer_no
reviewer_status
revision_number
revision_status
sent_date
sent_ori_dur
set_ball_in_crt
set_ball_in_crt_ini
start_date
sys_item_type
integer
date
smallint
char
char
char
char
date
integer
char
char
date
char
4
4
2
5
4
4
4
4
4
8
3
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
copies_prints_set
copies_sepias_set
description_set
drawing_date_set
elpsd_cycle_time_set
end_date_set
forward_ori_dur_set
forwarded_date_set
held_begin_date_set
held_cycle_time_set
held_end_date_set
item_type
master_key
parent_key
integer
integer
char
date
integer
date
integer
date
date
integer
date
char
char
char
4
4
29
4
4
4
4
4
4
4
4
4
26
26
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
SBST
project_name
receive_ori_dur_set
received_date_set
remarks_set
return_ori_dur_set
returned_date_set
reviewer_no_set
reviewer_set_vndr
reviewer_set_vndr_ini
reviewer_status_set
revision_number_set
revision_status_set
sent_date_set
sent_ori_dur_set
start_date_set
sys_item_type
char
integer
date
long varchar
integer
date
char
char
char
char
char
char
date
integer
date
char
8
4
4
32767
4
4
5
8
3
4
4
4
4
4
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Submittals Module (Base)

Table
Column Name
Data Type
Length
Decimals
SBDS
SBDS
SBDS
SBDS
SBDS
SBDS
SBDS
SBDS
SBDS
SBDS
SBDS
SBDS
SBDS
copies
distributed_date
distributed_to
distributed_to_ini
distribution_list_title
item_type
master_key
parent_key
project_name
remarks
revision_number
sys_item_type
transmit
char
date
char
char
char
char
char
char
char
char
char
char
smallint
8
4
8
3
23
4
26
26
8
39
4
4
2
0
0
0
0
0
0
0
0
0
0
0
0
0
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
appr_activity
approval_finish
approval_lead_time
approval_start
approve_has_finished
approve_has_started
approved
ball_in_court
ball_in_court_ini
Bid_Package
code
char
date
integer
date
smallint
smallint
smallint
char
char
char
char
16
4
4
4
2
2
2
8
3
9
12
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
completion_date
construction_activity
construction_finish
construction_has_finished
construction_has_started
construction_start
contract_number
days_elpsd_date
days_held_date
days_over_date
def_forward_ori_dur
def_receive_ori_dur
def_return_ori_dur
def_sent_ori_dur
delivery_actv
delivery_finish
delivery_has_finished
delivery_has_started
delivery_lead_time
delivery_start
drawing
fab_rel_activity
fab_release_fin
fab_release_lead_time
fab_release_st
fab_time
fabricate_actv
fabricate_finish
date
char
date
smallint
smallint
date
char
date
date
date
integer
integer
integer
integer
char
date
smallint
smallint
integer
date
char
char
date
integer
date
char
char
date
4
16
4
2
2
4
12
4
4
4
4
4
4
4
16
4
2
2
4
4
35
16
4
4
4
5
16
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
fabricate_lead_time
fabricate_start
fabstart_has_finished
fabstart_has_started
filed_app_date
filed_vendor
filed_vendor_ini
forwarded_to
forwarded_to_ini
item_number
item_type
items_in_submttl
last_date
last_edit_by
last_edit_date
latest_forward_date
latest_recvd_date
latest_return_date
latest_rev_number
latest_sent_date
master_key
next_step
package_number
parent_key
project_name
received_from
received_from_ini
ref_activity_id
integer
date
smallint
smallint
date
char
char
char
char
char
char
integer
date
char
timestamp
date
date
date
char
date
char
char
char
char
char
char
char
char
4
4
2
2
4
8
3
8
3
5
4
4
4
8
8
4
4
4
4
4
26
8
10
26
8
8
3
16
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
release_has_finished
release_has_started
required_finish
required_start
restricted_to
resubmit_activity
resubmit_finish
resubmit_has_finished
resubmit_has_started
resubmit_lead_time
resubmit_start
returned_by
returned_by_ini
schedule_data_source
second_app_code
second_app_code_ini
second_app_date
security_flag
sent_to
sent_to_ini
ship_activity
ship_finish
ship_has_finished
ship_has_started
ship_start
ship_time
source_vendor
source_vendor_ini
smallint
smallint
date
date
char
char
date
smallint
smallint
integer
date
char
char
smallint
char
char
date
char
char
char
char
date
smallint
smallint
date
char
char
char
2
2
4
4
8
16
4
2
2
4
4
8
3
2
8
3
4
1
8
3
16
4
2
2
4
5
8
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
SBMT_TABLE
start_date
status
submit_act_date
submit_activity
submit_finish
submit_has_finished
submit_has_started
submit_lead_time
submit_start
submittal_no
submittal_reqd
sys_item_type
title
unsubmitted
user_appr_date
user_code
user_code_ini
date
char
date
char
date
smallint
smallint
integer
date
char
smallint
char
char
smallint
date
char
char
4
4
4
16
4
2
2
4
4
15
2
4
35
2
4
8
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
copies_prints
copies_sepias
description
drawing_date
end_date
forward_ori_dur
forwarded_date
held_begin_date
held_end_date
item_type
integer
integer
char
date
date
integer
date
date
date
char
4
4
50
4
4
4
4
4
4
4
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
SBRV_TABLE
master_key
parent_key
project_name
receive_ori_dur
received_date
remarks
return_ori_dur
returned_date
review_set
reviewer_no
reviewer_status
revision_number
revision_status
sent_date
sent_ori_dur
set_ball_in_crt
set_ball_in_crt_ini
start_date
sys_item_type
char
char
char
integer
date
long varchar
integer
date
smallint
char
char
char
char
date
integer
char
char
date
char
26
26
8
4
4
32767
4
4
2
5
4
4
4
4
4
8
3
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
copies_prints_set
copies_sepias_set
description_set
drawing_date_set
end_date_set
forward_ori_dur_set
forwarded_date_set
held_begin_date_set
integer
integer
char
date
date
integer
date
date
4
4
29
4
4
4
4
4
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
SBST_TABLE
held_end_date_set
item_type
master_key
parent_key
project_name
receive_ori_dur_set
received_date_set
remarks_set
return_ori_dur_set
returned_date_set
reviewer_no_set
reviewer_set_vndr
reviewer_set_vndr_ini
reviewer_status_set
revision_number_set
revision_status_set
sent_date_set
sent_ori_dur_set
start_date_set
sys_item_type
date
char
char
char
char
integer
date
long varchar
integer
date
char
char
char
char
char
char
date
integer
date
char
4
4
26
26
8
4
4
32767
4
4
5
8
3
4
4
4
4
4
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Telephone Records Module (Base)

Table
Column Name
Data Type
Length
Decimals
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
TELE
ball_in_court
ball_in_court_ini
completion_date
contract_number
date_received
description
entered_by
fr_phone_number
from_extension
from_name
from_vendor
from_vendor_ini
item_number
item_type
last_edit_by
last_edit_date
master_key
next_step
project_name
ref_activity_id
restricted_to
security_flag
start_date
status
subject
char
char
date
char
date
long varchar
char
char
char
char
char
char
char
char
char
timestamp
char
char
char
char
char
char
date
char
char
8
3
4
12
4
32767
3
18
4
22
8
3
5
4
8
8
26
8
8
16
8
1
4
4
33
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
TELE
TELE
TELE
TELE
TELE
TELE
TELE
sys_item_type
time_received
to_extension
to_name
to_phone_number
to_vendor
to_vendor_ini
char
char
char
char
char
char
char
4
8
4
22
18
8
3
0
0
0
0
0
0
0
Transmittals Module (Base)

Table
Column Name
Data Type
Length
Decimals
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
TRDS_TABLE
Add_Line_1
Add_Line_2
Add_Line_3
City
Company
Country
Country_Code
Item_Type
Master_Key
Parent_Key
Postal_Code
Project_Name
State
Sys_Item_Type
Vendor_Abbrev
Vendor_Abbrev_ini
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
char
36
36
36
28
36
30
10
4
26
26
15
8
30
4
8
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
base_item_type
base_master_key
base_parent_key
base_sys_item_type
copies
description
drawing_number
item_date
char
char
char
char
char
long varchar
char
date
4
26
26
4
2
32767
35
4
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
TRDT
item_number
item_type
master_key
number
package_number
paper_size
parent_key
project_name
rev_no
status
submittal_number
sys_item_type
char
char
char
char
char
char
char
char
char
char
char
char
5
4
26
15
10
15
26
8
4
4
15
4
0
0
0
0
0
0
0
0
0
0
0
0
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
after_loan
as_noted
as_requested
as_submitted
attached
attention
ball_in_court
ball_in_court_ini
bids_due
bids_due_date
change_order
completion_date
contract_number
copies_corrected
copies_for_app
smallint
smallint
smallint
smallint
smallint
char
char
char
smallint
date
smallint
date
char
integer
integer
2
2
2
2
2
22
8
3
2
4
2
4
12
4
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
copies_for_dist
copies_to_1
copies_to_2
distribute_to
distribution_list_title
for_approval
for_corrections
for_review
for_your_use
from_add_line_1
from_add_line_2
from_add_line_3
from_city
from_company
from_country
from_country_code
from_postal_code
from_state
from_vendor
from_vendor_ini
item_type
last_edit_by
last_edit_date
letter
master_key
next_step
other
other_string
integer
char
char
char
char
smallint
smallint
smallint
smallint
char
char
char
char
char
char
char
char
char
char
char
char
char
timestamp
smallint
char
char
smallint
char
4
79
79
8
23
2
2
2
2
36
36
36
28
36
30
10
15
30
8
3
4
8
8
2
26
8
2
24
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
plans
prints
project_name
ref_activity_id
reference_1
reference_2
reference_3
remarks
restricted_to
resubmit
returned
samples
security_flag
sent_via
separate_cover
shop_dwg
signed
specifications
start_date
status
submit
sys_item_type
to_add_line_1
to_add_line_2
to_add_line_3
to_city
to_company
to_country
smallint
smallint
char
char
char
char
char
long varchar
char
smallint
smallint
smallint
char
char
smallint
smallint
char
smallint
date
char
smallint
char
char
char
char
char
char
char
2
2
8
16
24
24
24
32767
8
2
2
2
1
22
2
2
22
2
4
4
2
4
36
36
36
28
36
30
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
TRMT
to_country_code
to_postal_code
to_state
to_vendor
to_vendor_ini
trans_date
trans_no
char
char
char
char
char
date
char
10
15
30
8
3
4
5
0
0
0
0
0
0
0
integer
integer
char
char
char
char
char
char
char
char
long varchar
long varchar
char
integer
integer
char
char
date
4
4
26
4
4
26
4
26
4
8
32767
32767
35
4
4
8
3
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Transmittals Module - Transmittal Queue

TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
as_requested
attached
base_child_key
base_child_sys_item
base_item_type
base_master_key
base_parent_item_type
base_parent_key
base_sys_item_type
copies
description
description_trdt
drawing_number
for_approval
for_your_use
from_vendor_code
from_vendor_code_ini
item_date
Table
Column Name
Data Type
Length
Decimals
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
TRNQ
item_type
master_key
number
other_string
paper_size
pkg_number
plans
project_name
reference_1
rev_no
sbmt_rev_not_dist
shop_drawings
status
submit
submttl_number
sys_item_type
time_in
title
to_vendor_code
to_vendor_code_ini
user_code
user_code_ini
user_name
char
char
char
char
char
char
integer
char
char
char
smallint
integer
char
integer
char
char
timestamp
char
char
char
char
char
char
4
26
15
30
15
10
4
8
26
4
2
4
4
4
15
4
8
35
8
3
8
3
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Trends Module (View)

Table
Column Name
Data Type
Length
Decimals
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
adjustment_date
adjustment_number
ball_in_court
ball_in_court_ini
by_vendor
by_vendor_ini
cedt_master_key
cemt_master_key
cemt_number
contract_number
cost_type_description
currency_type
distributed_to
entered_by
exchange_ptr
item_type
last_edit_by
last_edit_date
master_key
next_step
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
date
char
char
char
char
char
char
char
char
char
varchar
char
char
char
integer
char
char
timestamp
char
char
char
char
char
char
char
4
12
8
3
8
3
26
26
12
12
29
4
16
22
4
4
8
8
26
8
8
16
20
1
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
ADJT
remarks
restricted_to
security_flag
status
sys_item_type
time_change
title
value
long varchar
char
char
char
char
integer
char
numeric
32767
8
1
4
4
4
35
17
0
0
0
0
0
0
0
2
Trends Module (Base)

Table
Column Name
Data Type
Length
Decimals
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
adjustment_date
adjustment_number
ball_in_court
ball_in_court_ini
by_vendor
by_vendor_ini
cedt_master_key
cemt_master_key
cemt_number
contract_number
currency_type
distributed_to
entered_by
exchange_ptr
item_type
last_edit_by
last_edit_date
master_key
next_step
project_name
ref_activity_id
ref_cost_account
ref_cost_category
ref_resource
remarks
date
char
char
char
char
char
char
char
char
char
char
char
char
integer
char
char
timestamp
char
char
char
char
char
char
char
long varchar
4
12
8
3
8
3
26
26
12
12
4
16
22
4
4
8
8
26
8
8
16
20
1
8
32767
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table
Column Name
Data Type
Length
Decimals
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
ADJT_TABLE
restricted_to
security_flag
status
sys_item_type
time_change
title
value
char
char
char
char
integer
char
numeric
8
1
4
4
4
35
17
0
0
0
0
0
0
2
Wizards (Base)
Table
Column Name
Data Type
Length
Decimals
WZRD
WZRD
WZRD
WZRD
WZRD
WZRD
screen_count
screen_data
screen_names
source_item
target_item
wizard_name
integer
long varchar
long varchar
char
char
varchar
4
32767
32767
4
4
48
0
0
0
0
0
0
Copyright 1997 by Primavera Systems, Inc. All rights reserved. No part of this publication may be reproduced or used in any form or by any meansgraphic,
electronic, or mechanical, including photocopying, mimeographing, recording, taping, or in information storage and retrieval systemswithout written permission
from the publisher.
Please send your comments about Concentric Project Management to:
Primavera Systems, Inc.
Two Bala Plaza
Bala Cynwyd, PA 19004
Telephone: 1-610-667-8600
Fax: 1-610-667-7894
Internet: usatech@primavera.com
World Wide Web site: http://www.primavera.com
Expedition, Primavera Project Planner, P3, TimeSheet Professional for Primavera, and SureTrak Project Manager are registered trademarks; Monte Carlo, Parade,
Webster for Primavera, Primavera Enterprise Access Kit, PEAK, DataStore for Primavera, ReportSmith for Primavera, and Concentric Project Management are
trademarks of Primavera Systems, Inc.
All other brands and product names are trademarks or registered trademarks of their respective companies.
U.S. GOVERNMENT RESTRICTED RIGHTS: The SOFTWARE and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure
by the Government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS
252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software-Restricted Rights 48 CFR 52.227-19, and our GSA contract, as applicable.

Part 4

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Part 4

Transféré par

Droits d'auteur :

Formats disponibles

i

Table of Contents iii

Batch Error Messages 126

P3 2.0 Files 131

SureTrak 2.0 Files 201

Expedition 6.0 Files 229

Mail (View) 333

Using the P3 Batch System

SureTrak 2.0 Files describes SureTrak-specific information stored in the

Using the P3 Batch System

Batch processing is a fast and powerful way to create and

Using the P3 Batch System 4-5

Using the P3 Batch System 4-6

Using the P3 Batch System 4-7

Using the P3 Batch System 4-8

General Rules for Batch Processing

For instructions on creating a

Place data records in the correct sequence.

Back up your project files as well as your batch files.

Using the P3 Batch System 4-9

To set up the P3 Batch system program icon

Working directory: C:\P3WIN\P3PROGS

Using the P3 Batch System 4-10

WHEN GENERATING CALENDAR, WEEKEND HOLIDAYS WILL BE MOVED TO NEAREST WEEKDAY

----------CALENDAR SPECIFICATIONS INSERTED

CALENDAR 1 DAILY MON TUE WED THU FRI

Using the P3 Batch System 4-11

P3 Screen/Batch Function Table

Add a new project group

Define project titles

File, New or File, Project Overview

Define an activity coding

Data, Activity Codes: Activity codes option,

Define a WBS coding

Data, WBS: Structure button

Define custom data items

Data, Custom Data Items: Activity or

Define nonlinear distributions Data, Resource Curves

Add a project to a project

COTL, BRT1, BRT2

Define a Cost account

Data, Cost Accounts

Change an existing calendar Data, Calendars

Using the P3 Batch System 4-12

Copy an existing project

Tools, Project Utilities, Copy

COPY AND RENAME

Print a calendar list

Data, Calendars, Print button

Define a baseline plan

File, Project Overview, Targets

Tools, Project Utilities, Delete

Reset period cost and

Data, Resources, Close Out button

Add, delete, or change

Insert, Activity; Edit, Delete; Edit, Edit

Assign custom data item

Data, Custom Data Items

Define activity relationships

Successors and Predecessors Activity detail PREC or SUCC PRED/

Assign activity codes

Activity Codes detail form

Assign WBS codes