Project Controller Report

Report Assistant for Microsoft Dynamics

® SL

Project Controller Module

Last Revision: October 2012

(c)2012 Microsoft Corporation. All rights reserved. This document is provided "as-is." Information and

views expressed in this document, including URL and other Internet Web site references, may change

without notice. You bear the risk of using it.

Some examples are for illustration only and are fictitious. No real association is intended or inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft

product. You may copy and use this document for your internal, reference purposes.

Trademark

Microsoft, ActiveX, Excel, FRx, FrontPage, MapPoint, Outlook, SharePoint, Visual Basic, Visual Studio,

Windows, Windows and Windows Server are either registered trademarks or trademarks of Microsoft

Corporation, FRx Software Corporation, or their affiliates in the United States and/or other countries. FRx

Software Corporation is a subsidiary of Microsoft Corporation. Business Objects and the Business

Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, and other Business Objects products

and services mentioned herein as well as their respective logos are trademarks or registered trademarks of

Business Objects Software Ltd. Business Objects is an SAP company.

The names of actual companies and products mentioned herein may be trademarks or registered marks -

in the United States and/or other countries - of their respective owners.

The example companies, organizations, products, domain names, e-mail addresses, logos, people, places,

and events depicted herein are fictitious. No association with any real company, organization, product,

domain name, e-mail address, logo, person, place, or event is intended or should be inferred.

Warranty disclaimer Microsoft Corporation disclaims any warranty regarding the sample code

contained in this documentation, including the warranties of merchantability and fitness for a particular

purpose.

Limitation of liability The content of this manual is furnished for informational use only, is subject to

change without notice, and should not be construed as a commitment by Microsoft Corporation.

Microsoft Corporation assumes no responsibility or liability for any errors or inaccuracies that may

appear in this manual. Neither Microsoft Corporation nor anyone else who has been involved in the

creation, production or delivery of this documentation shall be liable for any indirect, incidental, special,

exemplary or consequential damages, including but not limited to any loss of anticipated profit or

benefits, resulting from the use of this documentation or sample code.

License agreement Use of this product is covered by a license agreement provided with the software

product. If you have any questions, please call the Microsoft Business Solutions Customer Assistance

Department at 800-456-0025 (in the U.S. or Canada) or +1-701-281-6500.

Table of Contents

How to use this Manual 1

Introduction 3 Manual Sections 3

Sort and Select Statements 5

Overview 6 Select Statements 6

Field 7 Operator 7

Value 11 Sort Statements 16

Field 17 Sort Type 18

Sort Ascending 18 Page Break 18

Total Break 19 Possible Values Chart 21

Data Field Illustrations 23

Overview 24 Tables 24

Project Controller Setup (PA.SET.00) – General Information Tab 26

Project Controller Setup (PA.SET.00) – PC Options and Setup Tab 27

Project Controller Setup (PA.SET.00) – Revenue Setup Tab 28 Project Controller Setup (PA.SET.00) – Equipment/UOP Setup Tab 29

Project Controller Setup (PA.SET.00) – Billed To Date Setup Tab 30 Project Controller Setup (PA.SET.00) – Bill to a Maximum Setup Tab31 Project Charge Entry (PA.CHG.00) 32

Project Maintenance (PA.PRJ.00)– Project Tab 33 Project Maintenance – Task Tab (PA.PRJ.00) 33

Project Maintenance - Budgets Tab (PA.PRJ.00) 36 Project Maintenance - Additional Info Tab (PA.PRJ.00) 37 Project Maintenance – Quick Send Tab (PA.PRJ.00) 39 Percent Complete and Revenue Recognition Setup (PA.PCM.00) 40

Budget Maintenance (PA.BSM.00) 41 Resource Assignment (PA.RAS.00) 42 Project Transaction Transfer (PA.PTT.00) 43

Project Employee Maintenance- Project Team Assignment Tab (PA.PEM.00) 46 Project Employee Maintenance - Projects by Employee Tab (PA.PEM.00) 48 Account Category Maintenance – Master Information Tab (PA.ACC.00)50

Account Category Maintenance – ID Fields (PA.ACC.00) 51

Account Category Maintenance-GL Cross-Reference (PA.ACC.00) 53 Code File Maintenance (PA.CFM.00) 55

Control Parameter Maintenance (PA.CNT.00) 56 Equipment/Resource Maintenance – Equipment Info Tab (PA.EQU.00)57 Equipment/Resource Maintenance-Additional Info Tab (PA.EQU.00) 59 Equipment Rate Maintenance (PA.ERM.00) 61 Fiscal Period Maintenance (PA.FPM.00) 63

Flexible Key Maintenance (PA.FKM.00) 65 Import/Export File Mapping (PA.IEM.00) 66 Site Maintenance (PA.SIT.00) 68 ID Maintenance (PA.IDM.00) 69

Report Information 71

Overview 72 Project Profile - Screen PA.010.00 73 Tasks Report (PA.020.00) 74

Budget Reports Report (PA.030.00) 75 Account Category Report (PA.040.00) 76 Employee Report (PA.050.00) 77

Project Charges Summary/Detail Report (PA.060.00) 78 Transaction List By Batch Report (PA.070.00) 79

Account Category/GL Account XREF Report (PA.080.00) 80 Project Task Summary Report (PA.100.00) 81 Project Aging/Recap Report (PA.110.00) 82

Project Profitability Report (PA.120.00) 83

Project Billing Analysis Report (PA.130.00) 84 Project Task Analysis Report (PA.140.00) 85 Project Transactions Report (PA.150.00) 86

Project Cost Analysis Report (PA.160.00) 87 Project List Report (PA.170.00) 88

Revenue & Billing Status Report (PA.180.00) 89 Billing Worksheet by Task/Project Report (PA.190.00) 90 Budget vs Actual Amounts/Units Report (PA.200.00) 91 Units of Production Report (PA.210.00) 92 Transaction Transfer Messages Report (PA.220.00) 93

Week End Date Listing Report (PA.910.00) 94 Code File Report (PA.810.00) 96

Code Type Report (PA.820.00) 97 ID Field Report (PA.830.00) 98 Control Parameters List Report (PA.840.00) 100 Report Column Listing Report (PA.850.00) 101 Pjt GL Account Distribution Report (PA.900.00) 102

Job Summary Report (PA.300.00) 103 Labor Hours Detail (PA.310.00) 104 Labor Hours and Cost Detail (PA.320.00) 105

ODC Detail (PA.330.00) 106

Revenue Detail (PA.340.00) 107 Cost Summary (PA.350.00) 108

Revenue Summary (PA.360.00) 109 Indirect Cost Analysis Report (PA.370.00) 110

Index Error! Bookmark not defined.

H O W T O U S E T H I S M A N U A L

What you will learn in this section:

In this section you will learn about the main sections in this Microsoft

Dynamics™ SL Report Assistant manual.

We will discuss the differences between sort and select statements.

We will review possible values that can be used for both sort and select

statement fields.

We will also be reviewing basic information about the data field

illustrations for each module data entry and maintenance screen.

You will learn about basic module report information: master table,

sort order, report name as stored in Crystal, and sort/select field

examples.

Introduction

Flexible reporting is a very important part of a company’s ability to effectively operate their business.

This manual is intended to assist you with flexible reporting in the Microsoft Dynamics™ SL Project

Controller module. It may also be of use during creation or modification of reports in the Crystal

Report writer.

Manual Sections

The manual is divided into three parts:

Sort and Select Statements - The first section describes the differences between sort statements and

select statements. It also describes each of the parameters that can be used in a sort or select statement

and gives examples of how to use them. This section should be a good reference for users struggling

with deciding which operator to use, or whether they need a select statement or a sort statement.

At the end of this section, a Possible Values Chart has been included. The chart displays values

stored in Microsoft Dynamics™ SL for some of the more common fields in the Project Controller

module. For example, project billing type values, project status values, employee status values, etc.

When performing sort and select statements, you may not be sure of the values for some of these

types of fields. The section displays some common fields with their possible values.

Data Field Illustrations - The second section contains a picture of data entry screens and

maintenance screens for the Project Controller module. There is a reference for each field in the

screen noting the table and field where the data from the field is stored in the Microsoft Dynamics™

SL data files, as noted through the Customization Manager module. For example, when entries are

made in the Project Maintenance screen, the data entered in the start date field is stored in the Pjproj

file, in a field named start_date. The illustration with the Project Maintenance screen in this section

includes a reference to the Start Date field, noting the value for the field is stored in

Pjproj.start_date.

Sample Even Page Header

4 Page

When printing a report, it is not always easy to determine the field to be used in a sort or select

statement. You may know the field in which the data was entered in a screen, but are unsure what the

field is called and the table in which the field is stored. With the information in this section, you can

quickly determine the entry needed in the Sort or Select Field.

Report Information - The third section contains pertinent information about each report in the

Project Controller module. The following information is contained in the section:

Master table - When using sort/select statements for printing reports, it is important to

know the master table name. If the field chosen for the sort/select statement is from the

master table, the result can be much faster report processing and more accurate results.

Sort order - If a report is sorted differently than designed, report totals and subtotals may

be inaccurate. Knowing the fields the report currently uses for the sort order may help

you produce accurate reports when using sort statements.

Report name as stored in Crystal - If you need to access the report to modify or copy it,

it is important to have the report names. Many reports have multiple formats available,

which makes it more difficult to determine the correct report to retrieve.

Sort/select field examples - A table is included with sort/select fields for many of the

more commonly used report filters for each report.

S O R T A N D S E L E C T S TAT E M E N T S


In this section you will learn about Microsoft Dynamics™ SL’s Select

statements, used to limit the records included on reports.

We will discuss Microsoft Dynamics™ SL’s Sort statements and their

fields: Field, Sort Type, Sort Ascending, Page Break, Total Break.

Report Assistant for Microsoft Dynamics™ SL – Project Controller Module

6 Page

Overview

Each of Microsoft Dynamics™ SL’s report screens include a Sort tab and a

Select tab which allow you to enter parameters used to limit the information

included on the reports. This section is intended to assist you with using those

Sort and Select options.

What is the difference between a Sort statement and Select statement? Select

statements limit the records to be included in a report. For example, if you enter a

Select statement to include only one project or task in a report, only records

meeting that criterion will be included in the report. If no records are found to

match the Select parameters entered, the report will still print, but without data.

Sort statements modify the sort order of the report. The report will still contain

all of the data that is in the original report, but the Sort statement will change the

order of the records when they are printed.

You can create multiple Sort and Select statements in one report.

The Sort and Select tabs appear the same for all reports. However, the available

fields for Sort/Select statements are different, depending on the tables included in

the report.

When creating Sort and Select statements, be aware that the results might not

always be what you expect. Reports are written with specific grouping criteria

and sort orders. When other fields are entered for Sort or Select parameters, the

report may not print or total properly, although data may still be printed. Section

3 of this manual details the master table and default sort order for each report.

Select Statements

As noted earlier, a Select statement is used to limit the records to be included in a

report. A Select statement is similar to a Filter. With the Select tab, you will enter

fields, operators and values that will make up the filter controlling which records

will be included in the report.

The Select tab contains multiple rows, with four (4) fields per row. These four

fields include: Field, Operator, Value and Boolean. These fields are discussed

below, along with examples.

Sort and Select Statements

Page 7

FIGURE 1-1: SELECT TAB

Field

The Field area is used to enter the table and field name to be used to filter the

records in the report. When in the Field area, you can use Microsoft Dynamics™

SL’s F3 inquiry function to view a list of available tables and fields for the

report. Sections 2 and 3 of this guide can also be used as a reference for field

names.

Note The list of available fields may include fields that are not used in the

report. If you use a field in the Select statement that is not used in the report,

you may get a blank report. See Section 3 for examples of fields commonly

used for Sort/Select statements for each report.

Occasionally, you may need to add a field to the Field list to be used in a Select

statement. This can be done by adding the ROI SELECT function to the report

through Crystal Reports. Refer to Knowledge Base article 867089 for

information on this process.

Note ROI stands for Report Options Interpreter.

Operator

The Operator field controls the type of filter to be applied to the records when the

system is gathering data for the report. The available Operators and examples of

their use are described below.


8 Page


Begins with

The ‘Begins With’ operator is useful when you need a report for a group with a

common factor. For example, if you need a report listing projects whose project

IDs begin with CO1, the following statement could be used.

Field Operator Value Boolean Pjproj.project Begins With CO1 And

Between

Use ‘Between’ when the report should only include records between a beginning

and ending range. In the value field, separate the upper and lower values with a

comma. In the following example, the report will include data for projects where

the IDs are CO123000 through CO990000, inclusive.

Field Operator Value Boolean Pjproj.project Between CO123000,CO990000 And

Note When using between, the report includes records matching the beginning

and ending values entered (i.e.CO123000 and CO990000 will be included in

the report).

Contains

The ‘Contains’ operator is used to select records which have a specified value

anywhere within a field. In the following example, the statement used would

result in a report including only those projects that have ‘123’ in their name.


Page 9

Field Operator Value Boolean Pjproj.project Contains 123 And

Equal

Use ‘Equal’ for an exact match. In the following example, only data for project

CO123000 will be included in the report.

Field Operator Value Boolean Pjproj.project Equal CO123000 And

Greater than

‘Greater than’ is used to include records larger (higher) than the value entered. In

the following example, only projects with a transaction amount greater than

$6,000 will be included in the report. (Also see ‘Greater than or equal to’ below.)

Field Operator Value Boolean Pjtran.tranamt Greater than 6000 And

Greater than or equal to

‘Greater than or equal to’ is used to include records containing the value entered,

as well as records greater than the value. In the following example, projects with

transaction amounts of $6,000 will be included in the report, along with projects

with transaction amounts higher than $6,000.

Field Operator Value Boolean Pjtran.tranamt Greater than or equal to 6000 And

In

The ‘In’ operator works similarly to the ‘Equal’ operator, but allows you to enter

multiple items in the Value field. In the example below, projects with project IDs

CO123000, CO124000, and CO990000 will be included in the report. If there are

no records for one of the values entered, it will simply be left off the report -

records for the other two values will still print.

Field Operator Value Boolean Pjproj.project In CO123000,CO124000,

CO990000

And

Is NULL

Using the ‘Is NULL’ operator will include records on the report for which the

selected field is empty. In the example below, the report will include projects for

which no start date has been entered in the start date field. When using ‘Is

NULL’, the Value field must be left blank.

Field Operator Value Boolean Pjproj.start_date Is NULL And


10 Page

Is not NULL

‘Is not NULL’ works the opposite of the ‘Is NULL’ operator. It is used to include

items on a report where a specified field has been filled in. In the example below,

the report will include projects for which an start date has been entered in the

start date field.

Field Operator Value Boolean Pjproj.start_date Is not NULL And

Less than

The ‘Less than’ operator is the opposite of the ‘Greater than’ operator, and is

used to select records for which a specified field is less than the amount in the

Value field. In the example below, a Project report will include Projects with a

transaction amount less than $2,000. Any projects with a transaction amount of

$2,000.00 or more will not be included on the report.

Field Operator Value Boolean Pjtran.tranamt Less than 2000.00 And

Less than or equal to

The ‘Less than or equal to’ operator works the same as the ‘Less than’ operator,

but will also include records with a value equal to the amount in the Value field.

In the example below, any projects that have a transaction amount of $2,000 or

less will be included on the report.

Field Operator Value Boolean Pjtran.tranamt Less than or equal to 2000.00 And

Not between

The ‘Not between’ operator is used to print a report for values outside a

particular range. For example, if you needed a report showing projects with

transaction amounts less than $2,000 or more than $10,000, the following

statement would be used.

Field Operator Value Boolean Pjtran.tranamt Not between 2000,10000 And

Note When using Not Between, the report does not include records matching

the beginning and ending values entered (i.e. projects with transaction

amounts of $2,000 or $10,000 will not be included in the report).


Page 11

Not contains

The ‘Not contains’ operator is used to exclude data from a report with broad

specifications. For example, if you wanted to exclude all the “Environmental”

jobs from the Project List (PA.170.00), the following statement could be used.

Note that any job with “Environmental” in the description will be excluded from

the report.

Field Operator Value Boolean Pjproj.project_desc Not contains ‘Environmental’ And

Not equal

The ‘Not equal’ operator is used to exclude specific data from a report. In the

example below, the report will be printed excluding projects where the project

manager is E01181.

Field Operator Value Boolean Pjproj.manager1 Not equal E01181 And

Not in

The ‘Not in’ operator works similarly to the ‘Not equal’ operator, but allows you

to enter multiple items in the Value field. In the example below, the report will

be printed to exclude projects where the project manager is E01181 or E01184.

Field Operator Value Boolean Pjproj.manager1 Not in E01181,E01184 And

Value

The Value field is used to enter data which Microsoft Dynamics™ SL should use

to compare with when selecting records to be included in the report. The previous

section included many examples for the Value field. However, there are

additional functions available.

Note The Value field is limited to seventy (70) characters.


12 Page


Note The Possible Values section on Page 21 contains helpful information

about values for True and False fields, Active and Inactive fields, checkboxes,

etc.

Wildcards

Microsoft Dynamics™ SL supports the use of wildcards in the value field of

select statements. In the following example, the report would include all

transactions where the Project ID begins with ‘CO1’ (i.e. CO123000, CO124000,

CO125000 etc.)

Field Operator Value Boolean Pjproj.project Equal CO1?????? And

A question mark ( ? ) is used when one character is being replaced. In the above

example, projects with a project ID of CO123000B would not be included in the

report. When multiple characters need to be looked at, an asterisk (*) is used. By

changing the value in the previous example to the one below, Microsoft

Dynamics™ SL would return all transactions with Project IDs starting with CO1,

regardless of the Project ID length.

Field Operator Value Boolean Pjproj.project Equal CO1* And


Page 13

Date Values

When using Date Values, you need to include the forward slashes in the date.

Quotes are not necessary. The month and day may be entered with or without

leading zeroes, and the year may be entered with 2 or 4-characters.

Field Operator Value Boolean Pjproj.start_date Greater than 01/30/2000 And

Pjproj.start_date Less than 2/7/2001 And

Dashes and Other Special Characters

Many fields in Microsoft Dynamics™ SL may contain dashes or other special

characters that require special consideration when entering values for Sort/Select

statements. Sometimes the values must be entered with the special characters and

other times they do not.

The governing factor is whether the special characters must be entered during

regular data entry. For example, if you have subaccounts which have been set up

with multiple segments, the segments may be separated with dashes or other

characters. During data entry, the system fills in the separator for you. When

making an entry for subaccount 05-25, you need only type 0525 in the data entry

screen. In this case, if you want to use subaccount 05-25 as a value for a Select

statement, the entry will be 0525, without the dash.

In other instances, the special characters may be required. For example, it is

possible to set up Project IDs with only one segment and then use dashes in the

ID field when creating Project IDs. In this case, since the dash is not a separator

between segments but is instead a part of the ID, the dash must be entered both

during data entry and when used in a Select statement.

For items such as phone numbers, zip codes and social security numbers, the

system supplies the special characters during data entry, so the characters should

not be entered in Select statements. (The one exception to this is date fields,

discussed above.)

In general, the way to test this is to open a screen where the item would be

entered and determine whether the dashes or other special characters are required

to be entered during data entry. If you don’t have to enter them during data entry,

then don’t enter them in the Select statement (once again, with the exception of

date fields, discussed above).

Fiscal Periods

Special care must be taken when using fiscal periods in Select statements. In

many of the report screens, there are fields used to specify the fiscal periods to be

included in the report. The fiscal period(s) entered in the report screen will be

used to select the data based on the period to post for the transaction.

In the Select tab, parameters can be entered to select data based on period

entered, period closed, period to post, etc. If the report screen includes fields for

restricting the periods to be reported, and you enter a select statement for period


14 Page

to post with a different period to post, the report will be blank, as it will not be

possible for any of the data to meet both criteria.

For example, the Project Transactions report has a field in the report screen to

specify fiscal period. If you enter 01-2000 in both fields, the report will include

only transactions posted to 01-2000. If you then enter the following select

statement in the Select tab, the report would be blank:

Field Operator Value Boolean Pjtran.fiscalno Equal 200102 And

However, the following Select statement would be allowable. Although it is

based on a field with a fiscal period value, it is searching for items entered in

other periods.

Field Operator Value Boolean Pjtran.fiscalno Less than 200101 And

Note that while fiscal periods are displayed in screens and reports as month and

then year (i.e. 06-2000), they are stored in the data files as year, then month.

Because of this, they must be entered in Select statements as shown in the

examples above.

Boolean

Often, you will need to enter more than one select statement, in order to print

only the needed information on the report. The Boolean value defines how the

multiple select statements are to be used together. There are two options in this

field which are described below.


Page 15


AND - When AND is used for the Boolean value, each record to be

included in the report must match the values for both of the select

statements. In the example below, the resulting report would include

only transactions for the customer ‘C376’ with a start date greater

than 01/31/2001.

Field Operator Value Boolean Pjproj.customer Equal C376 And

Pjproj.start_date Greater than 01/31/2001 And

OR - When OR is used for the Boolean value, records will be

included in the report if they meet the specifications of one of the

select statements. In the example below, records will be included in

the report if either the start date or the end date is less than 2/5/2001.

Field Operator Value Boolean Pjproj.start_date Less than 2/5/2001 And

Pjproj.end_date Less than 2/5/2001 Or

Boolean values can be used to create select statements with multiple rows of

select statements, which allows you to narrow report results as much as needed.

For example, assume you need a Project Transactions report showing Project

‘CO123000’, with a start date after 01/31/2001, and a subaccount equal to 01-

000-CD-00-00-1. Printing the Project Transactions report, using the following

Select statements, would give you this information.

Field Operator Value Boolean Pjproj.project Equal CO123000 And

Pjproj.start_date Greater than 1/31/2001 And

Pjproj.gl_subacct Equal 01000CD00001 And


16 Page

Sort Statements

The Sort tab contains multiple rows, with five (5) fields per row. When creating

Sort statements, the following five fields are used: Field, Sort Type, Sort

Ascending, Page Break and Total Break. These fields are discussed below, along

with examples.

FIGURE 1-5: SORT TAB

Often times a report will contain multiple sort fields. When creating a Sort

statement for a report containing multiple sort fields, you can help ensure more

accurate results by entering the same number of sort fields as in the original

report. Sometimes this also means leaving some of the sort fields in the order

they already are in the report.

For example, in the Project List report there is one sort field. The sort order

currently is set to Project ID. If you enter a one line Sort statement for the Project

Description, you will only get one Project per page. If you add a multiple sort

statement, indicating the Project ID is still the first sort, the report will print all of

the projects on one page.

Note Section 3 of this manual displays the default sort order for each report.


Page 17

Field

The sort Field is used to enter the table and field name on which you want the

report to base the sort. For example, the Project Lists report, Summary format, is

designed to sort by Project ID. If you want to sort the report by the manager

instead of the Project ID, you would enter the following Sort statement:

Field Sort Type Sort Ascending Page Break Total Break Pjemploy.manager1 Sort Field Checked Blank Blank

FIGURE 1-6: SUMMARY PROJECT LIST REPORT WITH DEFAULT SORT

HINT: Because the report’s first sort is project ID, and you want to add the

Project Manager sort to the project ID, entering the 1st sort to remain as the

Project ID and then changing the second sort to be the Project Manager,

helps ensures accurate results.

Note When in the Field area, you can use Microsoft Dynamics™ SL’s F3

inquiry function to view a list of available tables and fields for the report.

Sections 2 and 3 of this guide can also be used as a reference for field names.


18 Page

Sort Type

Sort Type identifies the type of field identified in Field. Group Field indicates

that the field is a report group that allows page and total breaks. Sort Field

indicates that the report data sorts by the values in the field, within existing

groups. Groups are always processed first, followed by sort fields.

Sort Ascending

The Sort Ascending field is used to specify whether the values will be sorted in

ascending or descending order. To sort in ascending order, check the box in this

field. To sort in descending order, leave the checkbox in this field blank.

Page Break

Checking the box in the Page Break field will cause the report to begin a new

page whenever the field in the Sort Field changes. The Page Break option is

useful for reports where you want one project per page.

For example, let’s say you want to print the Project Lists report, and you want to

sort by Project with a Page Break by Project. By entering the following Sort

statement, Microsoft Dynamics™ SL would print the first project on the first

page, the second Project on the next page, and so on. Figure 8 displays the

Project Lists with a Page Break by Project ID.

Field Sort Type Sort Ascending Page Break Total Break Pjproj.project Group Checked Checked Blank


Page 19

Total Break

The Total Break is used to change the total grouping of a report. There are two

important factors to keep in mind when creating Total Breaks. First, the report

must already have total rows included in the report. If the report is not written

with a total row, the following message appears when you try to process a report

with a Total Break.

FIGURE 1-7: TOTAL BREAK MESSAGE

The second thing to keep in mind is you need to specify a sort order for the field

or the Total Break will not work. Usually you will specify the field for the Total

Break to be the 1st sort order.

For example, the Project Profile report currently prints documents in order by

Project Id and then by Project Task. Figure 9 displays the standard Project Profile

report. By changing the sort to be first by Project Id, then by Customer and third

by Start Date, and indicating a Total Break on both the Project Id and Customer

fields, the Project Profile will now total documents by Project as displayed in

Figure 11.

Field Sort Type Sort Ascending Page Break Total Break Pjproj.project Group Checked Checked Checked

Pjproj.customer Sort Checked Blank Checked

Pjproj.start_date Sort Checked Blank Blank

CAUTION: The Total Break does not always work properly therefore you

should review the report carefully if you have selected a Total Break.


20 Page

FIGURE 1-8: PROJECT PROFILE WITH DEFAULT SORT

FIGURE 1-9: PROJECT PROFILE WITH SORT AND TOTAL BREAK ON PROJECT ID


Page 21

Possible Values Chart

The Value that is stored in a field might not always be obvious to the end user.

The following chart is intended to assist with values that are stored in some of the

Allocator fields. The Value/Format field is the value you would enter in the

Value field of a Select statement.

Field Value/Format Project Status

Active

Inactive

Purge

Terminate

A

H

P

T

Date fields 01/05/1999 or 01/05/99

Period fields such as period-to- post,

period-entered, etc.

200009

Fiscal Year fields 2000

Contract Types

Cost Plus

Cost Plus Fixed Fee

Cost Plus Incentive Fee

Fixed Price

Fixed Price w/COS Relief

Fixed Price plus Expenses

Fixed Price plus T&M Tasks

Internal

Time & Material

Time & Material to Rev

Units of Production

CP

CPFF

CPIA

FP

FPCS

FPE

FPTM

INTR

TM

TMR

UP

Employee Status

Active

Inactive

Hold

Purge

A

I

H

P

Batch Status:

On Hold

Balanced (Release Later)

Released - Not posted to GL

Released - Posted to GL

Released - Doesn’t effect GL

Partially Released

Voided

Deleted

H

B

U

P

C

S

V

D

TABLE 1: PROJECT CONTROLLER POSSIBLE VALUES


22 Page

D ATA F I E L D I L L U S T R AT I O N S


In this section you will learn about the fields in Project Controller data entry and

maintenance screens: their field names and the table and field where they are stored in the

Microsoft Dynamics™ SL data files.


24 Page

Overview

The information in this section contains a screen illustration of the data entry screens and most maintenance screens in the

Project Controller module. The information in this section can be very useful when performing Sort and Select statements,

writing reports in Crystal Reports, using SQL statements to verify information, or using ODBC.

Each screen is displayed with a callout box indicating the table and field name where the data is stored, as noted in the

FieldName field on the Property Window of the Customization Manager module. Some data is stored in multiple tables

and fields. Additional tables and fields may be noted in the callout box, however, there may still be additional tables or

fields where the data is stored.

Note Some fields within the data entry and maintenance screens are calculated or temporary fields specifically for the screen, and are

not fields that are actually stored in the database. These types of fields have been designated with the text ‘Calculated’ in the

following data field illustrations. Because these fields are calculated or temporary, they will not appear in sort/select inquiry lists or

Crystal Reports tables or field lists.

Note Some fields within the data entry and maintenance screens are variable fields that are specific to a screen, and are not fields that

are actually stored in the database. These types of fields have been designated with the text ‘Variable’ in the following data field

illustrations. Because these fields are variable or temporary, they will not appear in sort/select inquiry lists or Crystal Reports tables

or field lists.

Note Some fields within the data entry and maintenance screens are related to a Code Type. Code Types are logical tables that are

defined in Code Type Maintenance (PA.COT.00) and maintained in PJCODE. Values for each Code Type are entered in Code File

Maintenance (PA.CFM.00) and maintained in PJCONTRL.

Tables

When a batch is posted in Project Controller, a record is created in PJTRAN (Project Transaction File) for each detail line

in the batch. Each record will contain the batch number, along with other detail information. An additional corresponding

record will be created in an extended table named PJTRANEX (Project Transaction Extended Data). A record is also

updated or created in PJACTROL (Project Actual Rollup), PJACTSUM (Project/Task Actual Summary), PJPTDROL

(Project Current Rollup), and PJPTDSUM (Project/Task Current Summary). Other extended tables that exists in Project

Controller are PJPROJEX (Project Master Extended Information) and PJPENTEXT (Task Master Extended Information).

Data Field Illustrations

Page 25

The PJACTROL table maintains yearly summary information by project while PJACTSUM maintains yearly summary

information by project and task. The PJPTDROL table maintains project-to-date actual and budget summary data by

project and PJPTDSUM maintain summary project-to-date actual and budget information by project and task. The

PJBUDROL table maintains yearly budget summary information for each period by project while PJBUDSUM maintains

the yearly budget summary information for each period by project and task.

The PJCOMROL (Project Commitment Rollup) table maintains yearly project commitment summary data by project

while PJCOMSUM (Project/Task Commitment Rollup) maintains project-to-date summary commitment information by

project and task.


26 Page

Project Controller Setup (PA.SET.00) – General Information Tab

SETUPPA.current_peri

od

SETUPPA.lasttra

n

SETUPPA.lastcharg

h

SETUPPA.lastall

oc

setuppa.EnableApproverSelecti

on

SETUPPA.mgr2caption

SETUPPA.mgr1caption

SETUPPA.empmgr1caption

SETUPPA.empmgr2caption

SETUPPA.budgetcaption1



setuppa.DefaultApprover

setuppa.OtherApproverID

PrjMgr.Name

SETUPPA.delay_timer


Page 27

Project Controller Setup (PA.SET.00) – PC Options and Setup Tab

SETUPPA.iq_pm_id1

SETUPPA.iq_pm_id2

SETUPPA.HistBudget_flg

SETUPPA.autoinc_p_num

SETUPPA.autoinc_p_seg

SETUPPA.autoinc_p_type

SETUPPA.autoinc_t_num

SETUPPA.autoinc_t_type

SETUPPA.autoinc_t_seg

SETUPPA.close_check

SETUPPA.interface_list

setuppa.auto_FTT_flg

setuppa.postpriorperiod_flg

setuppa.PRSummarize_flg

SETUPPA.default_task_flg

SETUPPA.auto_default_task

SETUPPA.default_task

SETUPPA.no_post_proj

setuppa.task_desc_seg

MSPSetup.default_dayrange

SETUPPA.UZActive

SETUPPA.DefaultUZType

setuppa.NoZeroAmountsPosted

setuppa.recap_gl_flg

setuppa.batch_select_flg

setuppa.auto_start_methnum

setuppa.auto_start_flg

setuppa.communicator_dest

SETUPPA.multi_curr_flg


28 Page

Project Controller Setup (PA.SET.00) – Revenue Setup Tab

SETUPPA.rev_glac

ct SETUPPA.cont_value_ac

ct SETUPPA.defrev_gla

cct SETUPPA.rev_acct

SETUPPA.defrev_acc

t SETUPPA.unbilled_glac

ct SETUPPA.unbilled_a

cct SETUPPA.unbfee_ac

ct SETUPPA.unboh_acc

t SETUPPA.unbfee_glac

ct SETUPPA.wip_ac

ct SETUPPA.ret_acct

SETUPPA.rev_basi

s SETUPPA.rev_pos

t SETUPPA.unbrev_a

cct

SETUPPA.rev_sub

SETUPPA.unboh_glacct

SETUPPA.defrev_sub

SETUPPA.unbilled_sub

SETUPPA.wip_glacct

SETUPPA.unbfee_sub

SETUPPA.unboh_sub

SETUPPA.wip_sub

SETUPPA.ret_glacct

SETUPPA.ret_sub

SETUPPA.rev_basis

SETUPPA.rev_post

SETUPPA.unbrev_glacc

t SETUPPA.unbrev_sub


Page 29

Project Controller Setup (PA.SET.00) – Equipment/UOP Setup Tab

setuppa.equip_charge_ac

ct

setuppa.equip_offset_acc

t

setuppa.uop_acct

setuppa.equip_charge_glacct

setuppa.equip_offset_glacct


30 Page

Project Controller Setup (PA.SET.00) – Billed To Date Setup Tab

SETUPPA.btd_ac

ct

pjrules.acct

pjacct.acct_des

c


Page 31

Project Controller Setup (PA.SET.00) – Bill to a Maximum Setup Tab

pjprojmx.acct

pjprojmx.mx_id03

pjprojmx.acct_overm

ax

pjprojmx.acct_overmax_off

set

setuppa.billmaxemploye

e

setuppa.OverrideSu

b

pjprojmx.gl_acct_overmax

pjprojmx.gl_acct_offset

pjprojmx.acct_billing

SETUPPA.billmaxuseorigem

p


32 Page

Project Charge Entry (PA.CHG.00)

©

pjchargh.batch_type

pjchargh.batch_bal

pjchargh.fiscalno

pjchargh.system_cd

pjchargd.employee

pjchargh.rate_table_id

pjchargh.batch_status

pjchargd.auto_recalc_sw

pjchargd.project

pjchargd.Subtask_Name

pjchargd.trans_date

pjchargd.amount

pjchargd.CpnyId

pjchargd.voucher_line

pjchargd.equip_id

pjchargd.gl_subacct

pjchargd.units

pjchargd.tr_id02

pjchargd.tr_id01

pjchargd.pjt_entit

y

pjchargd.tr_comment

pjchargd.vendor_num

pjchargd.gl_acct

pjchargd.unit_of_measur

e pjchargd.bill_batch_id

pjchargd.tr_id08

pjchargd.acct

pjchargd.voucher_num

pjchargd.data1

pjchargh.last_detail_

num

pjchargh.batch_id pjchargh.rate_type_cd

pjchargh.batch_desc1

pjchargd.tr_id03

pjchargd.tr_id04

pjchargd.tr_id05

pjchargh.batch_amount


Page 33

Project Maintenance (PA.PRJ.00)– Project Tab

pjproj.end_date pjproj.project_desc

pjproj.billcuryid

pes.CpnyId prjmgr.name

pjproj.start_dat

e pjproj.contract

pjproj.purchase_order_num

pjproj.contract_type

codedesc.contdesc

pjprojex.rev_type

pjproj.budget_typ

e

bpjproj.status_18

pjproj.status_19

subacct.descr

pjproj.gl_subacct

salesperson.name

pjproj.status_ap

pjproj.status_pa

prjsuper.name

currncy.descr

curyrttp.descr

codedesc.allmdesc

codedesc.allm2desc

codedesc.rtabdesc

pjprojex.rate_table_labor

pjproj.billcuryfixedrate

customer.name

pjproj.bf_values_switch

pjproj.rate_table_id

pjproj.alloc_method_cd

pjproj.alloc_method2_cd

pjproj.slsPerID pjproj.customer pjproj.manager2 pjproj.manager1

pjproj.labor_gl_acct pjproj.status_po

pjproj.status_gl pjproj.status_ar pjproj.status_lb pjproj.status_in

pjproj.project

pes.CpnyName

pjproj.billratetypeid


34 Page

Project Maintenance – Task Tab (PA.PRJ.00)

Pjpent.pe_id03

Pjpent.pe_id02

Pjpent.pe_id05

Pjpent.pe_id08

Pjpentex.pe_id23

Pjpent.pjt_entity

Pjpent.pjt_entity_desc

Pjpent.contract_type

Pjpent.manager1

Pjemploy2.emp_name

Pjpent.pe_id01

Pjpent.pe_id09

Pjpent.status_gl

Pjpent.status_pa Pjpent.status_08

Pjpent.labor_class_cd

Pjpent.status_ap

Pjpent.status_ar

Pjpent.status_po

Pjpent.status_lb

Pjpent.status_in

Pjpent.start_date

Pjpent.end_date

Pjpent.fips_num

Pjpent.pe_id35

Pjpent.pe_id36

Pjpentex.pe_id12

Pjpentex.pe_id13

Pjpentex.pe_id14


Page 35

Note Project Controller provides additional fields to allow storage of user-defined data. These fields are called ID fields and are very

similar to the standard Microsoft Dynamics™ SL User1 through User8 fields. The major difference between the ID fields and the

User fields is that the ID fields are activated and added to screens without the Customization Manager module. ID Maintenance

(PA.IDM.00) determines whether the field is visible, the caption associated with the field, and how validation is performed on the data

entered into the field.

Note Some of the ID fields are reserved for system use and may not be defined or used by the user for any other purpose. In some

cases, reserved ID fields already have specific definitions, which are noted. In other cases, the ID fields are reserved for future use.


36 Page

Project Maintenance - Budgets Tab (PA.PRJ.00)

PJPTDSUM.pjt_entity

PJPTDSUM.acct

pjptdsum.total_budget_units

pjptdsum.rate

pjptdsum.total_budget_amount


Page 37

Project Maintenance - Additional Info Tab (PA.PRJ.00)

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity

PJPTDSUM.pjt_entity


38 Page









Page 39

Project Maintenance – Quick Send Tab (PA.PRJ.00)

PJProjedd.EDD

PJProjEdd.DeliveryMethod

PJProjedd.Priority

PJProjedd.EDDFax

PJProjedd.RequestorsEmail

PJProjedd.SendersEmail

PJProjedd.EmailFileType

PJProjedd.FaxReceiverName

PJProjEdd.EDDFaxPrefix

PJProjedd.FaxSenderName

PJProjedd.FaxSenderNbr

PJProjedd.FaxCover

PJProjedd.FaxUrgent

PJProjedd.SubjectText

PJProjEdd.bodytext

PJProjEdd.EDDFaxUseAreaCode

PJProjEdd.doctype

PJProjedd.FaxReview.pjt_entity

PJProjedd.FaxComment

PJProjedd.FaxReply

PJProjedd.FaxRecycle


40 Page

Percent Complete and Revenue Recognition Setup (PA.PCM.00)

Pjprojex.project

Pjprojex.rev_type

Rrflags.tasksubacct_flag

Pjprojex.entered_pc

Rrflags.units_flag

Pjpentex.pjt_entity

Pjpentex.entered_pc

Pjpentex.fee_percent

Pjpentex.revision_date

Pjpentex.pe_id20

Pjpentex.pe_id24

Pjproj.project_desc

Rrflags.task_flag

Pjprojex.pm_id24

Pjprojex.revision_date

Rrflags.rracct_type

Pjpent.pjt_entity_desc

Pjprojex.fee_percent


Page 41

Budget Maintenance (PA.BSM.00)

pjproj.project_desc

pjpent.pjt_entity_desc

pjacct.acct_desc

PJPTDSUM.total_budget_amount

pjptdsum.eac_amount

pjptdsum.eac_units

pjpent.project

pjptdsum.rate

pjptdsum.total_budget_units

PJPTDSUM.acct

pjpent.project


42 Page

Resource Assignment (PA.RAS.00)

pjpent.project

PJpentem.date_end

pjpentem.actual_units

pjpentem.budget_units

pjpentem.budget_amt

PJPENTEM.comment

pjpent.project

PJPENTEM.employee

PJEMPLOY.emp_name

PJPENTEM.SubTask_Name

PJPENTEM.Date_start

pjproj.project_desc

pjpent.pjt_entity_desc


Page 43

Project Transaction Transfer (PA.PTT.00)

PTTSelect.ptt_project

pttselect.ptt_task

pttselect.ptt_cpny

pttselect.ptt_acctcat pttselect.ptt_thruper

pttselect.ptt_fromper

pttselect.ptt_refnbr

pttselect.ptt_glacct

pttselect.ptt_glsub pttselect.ptt_wedate pttselect.ptt_empid

batch.batnbr

batch.perpost pttdisplay.ptt_select pttdisplay.ptt_transferred

pjtfrdet.toproject pjtfrdet.topjt_entity pjtran.fiscalno pjtfrdet.toacctcat pjtran.cpnyid pjtfrdet.toglacct pjtfrdet.tosubacct pjtran.employee pjtran.units pjtran.amount pjtranex.tr_id22 pjtran.trans_date pjtran.tr_comment pjtran.voucher_num pjtran.tr_id03

pttselect.ptt_enddat

e

pttselect.ptt_lbrc

ls pttselect.ptt_vendo

r pttselect.ptt_billable pttselect.ptt_module

pttselect.ptt_sortorder

1 pttselect.ptt_sortorder

2 pttselect.ptt_sortorde

r3

pttselect.ptt_startdat

e

pttselect.ptt_incbille

d

batch.status

pjtran.tr_id05

BatHandling.handlin

g

pjtran.vendor_num

pjtranex.system_cd

pjtran.batch_id

pjtran.batch_type

pjtran.project

pjtran.pjt_entity

pjtran.acct

pjtran.gl_acct

pjtran.gl_subacct

pjtran.tr_id08


44 Page

Employee and Resource Maintenance (PA.EMP.00)

Pjemploy.employee

Pjemploy.MSPType

Pjemploy.emp_status

Pjemploy.emp_type_cd

Pjemploy.date_hired

Pjemploy.CpnyId

Pjemploy.gl_subacct

Pjemploy.manager1

Pjemploy.manager2

Pjemploy.user_id

Pjemploy.StdDay Pjemploy.date_terminated

Pjemploy.em_id15

Pjemploy.em_id01 Pjemploy.em_id02

Pjemploy.em_id03

Pjemploy.emp_name

Pjemploy.MSPInterface

Pjemployxrefmsp.Employee_MSPName

PJEmployxrefmsp.projectmanager

Pjemploy.em_id21

Pjemploy.em_id22

Pjemploy.em_id23

Pjemploy.em_id24

Pjemploy.em_id25

Form1.destination

Pjemploy.em_id07

Pjemploy.em_id11

Pjemploy.em_id14

Subacct.descr

Cmpny.name Pjemploy.placeholder Pjemploy.Subcontractor

Pjemploy.stdweek Mgr1.name Pjemploy.exp_approval_max

Mgr2.name


Page 45









46 Page

Project Employee Maintenance- Project Team Assignment Tab (PA.PEM.00)

Proj.project

Proj.all_emp_sw

Pjprojem.employee

Empdet.emp_name

Proj.project_desc


Page 47









48 Page

Project Employee Maintenance - Projects by Employee Tab (PA.PEM.00)

Emp.employee

Pjprojem1.project

ProjDet.project_desc

Emp.emp_name


Page 49









50 Page

Account Category Maintenance – Master Information Tab (PA.ACC.00)

Pjacct.acct

Pjacct.acct_desc

Pjacct.acct_group_cd

Pjacct.acct_type

Pjacct.sort_num

Pjacct.acct_status

Pjacct.ca_id03

Pjacct.ca_id20

Pjacct.id1_sw

Pjacct.id2_sw

Pjacct.id3_sw

Pjacct.id5_sw

Pjacct.id4_sw

Slstaxcat.descr

Pjcode.code_value_desc


Page 51

Account Category Maintenance – ID Fields (PA.ACC.00)

Pjacct.ca_id01

Pjacct.ca_id02

Pjacct.ca_id06

Pjacct.ca_id16


52 Page









Page 53

Account Category Maintenance-GL Cross-Reference (PA.ACC.00)

Data.gl_account

Data.descr

Data.type


54 Page

Code Type Maintenance (PA.COT.00)

screenbuf.cv_len

pjcontrl.control_co

de screenbuf.ct_des

c screenbuf.data1_c

t screenbuf.data1_st

at screenbuf.data1_ca

p screenbuf.data1_va

l screenbuf.data2_st

at screenbuf.data2_ct

screenbuf.data2_ca

p screenbuf.data2_v

al screenbuf.data3_st


p screenbuf.data4_st


p

screenbuf.cat

screenbuf.emask

fieldclass.data1

screenbuf.data1_mask

screenbuf.data1_len

fieldclass.data2

screenbuf.data2_mask

screenbuf.data2_len


Page 55

Code File Maintenance (PA.CFM.00)

Note Code File Maintenance (PA.CFM.00) is used to store lists of user-defined codes to be used for the validation of data upon entry.

Data 1, Data 2, Data 3 and Data 4 are fields defined in Code Type Maintenance (PA.COT.00) that can be displayed and used to

attach ancillary data to a Code Value.

pjcontrl.control_co

de

pjcode.code_valu

e

pjcode.code_value_de

sc

pjcode.data1

pjcode.data2

pjcode.data3

pjcode.data4

ctdata.ct_desc

ctdata.cvalue_length

ctdata.cat_desc


56 Page

Control Parameter Maintenance (PA.CNT.00)

pjcontrl.control_typ

e

pjcontrl.control_co

de

pjcontrl.control_de

sc

Pjcontrl.control_dat

a


Page 57

Equipment/Resource Maintenance – Equipment Info Tab (PA.EQU.00)

Pjequip.equip_id

Pjequip.equip_type

Pjequip.CpnyId

Pjequip.gl_subacct

Pjequip.project_costbasis

Postto.glpost

Pjequip.er_id01

Pjequip.status

Pjcode.code_value_desc

Pes.CpnyName

Subacct.descr

Pjrpj.project_desc

Postto.pjtpost

Pjequip.equip_desc


58 Page









Page 59

Equipment/Resource Maintenance-Additional Info Tab (PA.EQU.00)

Pjequip.eq_id01

Pjequip.eq_id02

Pjequip.eq_id03

Pjequip.eq_id05


60 Page









Page 61

Equipment Rate Maintenance (PA.ERM.00)

Pjequip.equip_id

PjEqRate.project Pjequip.equip_id PjEqRate.effect_date Pjequip.equip_id PjEqRate.unit_of_measure Pjequip.equip_id PjEqRate.rate1 Pjequip.equip_id PjEqRate.rate2 Pjequip.equip_id PjEqRate.rate3 Pjequip.equip_id

Pjequip.equip_desc

PjProj.project_desc


62 Page









Page 63

Fiscal Period Maintenance (PA.FPM.00)

Pjfiscal.fiscalno

Pjfiscal.start_date

Pjfiscal.end_date

Pjfiscal.comment


64 Page

Flexible Report Column Maintenance (PA.RPC.00)

Pjrepcol.report_code

Pjrepcol.column_nbr

Pjrepcol.acct

Pjrepcol.gl_acct

Pjrepcol.desc1


Page 65

Flexible Key Maintenance (PA.FKM.00)

pjcontrl.control_code

Screenb.caption Screenb.nump Screenb.delim

Screenb.segX_cap

Screenb.segX_len

Screenb.segX_mask

Screenb.segX_val

fcScreen.data1

Screenb.segX_ct


66 Page

Import/Export File Mapping (PA.IEM.00)

Pjimpexp.map_type

Pjimpexp.map_id

Pjimpexp.map_desc

Pjimpexp.fld01_col

Pjimpexp.fld02_col

Pjimpexp.fld03_col

Pjimpexp.fld04_col

Pjimpexp.fld05_col

Pjimpexp.fld06_col

Pjimpexp.fld07_col

Pjimpexp.fld08_col

Pjimpexp.fld09_col


Page 67

Message Text Maintenance (PA.MSG.00)

pjtext.msg_num

pjtext.category_c

d

pjcode.code_value_de

sc

pjcontrl.control_typ

e


68 Page

Site Maintenance (PA.SIT.00)

Pjsite.terminalcode

Pjsite.terminalname

Pjsite.emailaddress

Pjsite.type_site


Page 69

ID Maintenance (PA.IDM.00)

screenb.reserv

screenb.len

screenb.mask

pjcontrl.control_cod

e

screenb.stat

screenb.ct

miscdata.data

1

screenb.val

screenb.cap

R E P O R T I N F O R M AT I O N


In this section you will learn the pertinent information about each

report in the Project Controller module: master table, sort order, report

name as stored in Crystal, sort/select field examples.


72 Page

Overview

The information in this section lists each report in the Project Controller module,

along with the following information:

Report Formats and Report Names

This section lists the name of the report format from the Report Format field of

the report screen. Next to the Report Format is the name of the Report as it is

stored in Crystal Reports. This information is also stored in the Rptcontrol.dat

file, which is part of the system database.

Master Table

Often times when you are looking at the inquiry list within the sort or select field

of a report, you will see the same field in more than one table. For example, the

project ID field (project) is in several tables. If you are entering a sort or select

statement based on an field which is contained in multiple tables, your report will

usually process faster if you use the field from the master table. This section

gives you the master table (or view table) that is used in the report.

Note A View is a ‘virtual table’ whose contents are defined by a SQL query

statement. A View appears like a table with columns and rows of data, but

does not exist in the database as a stored set of data values. All of the reports

that are written with a View, rather than a master table, begin with the letter

V. For purposes of sort and select statements, a View is just like any other

table in a report and can be accessed in sort and select statements.

Default Sort Fields

This section lists the sort fields, in the same order as they are in the report. If

different fields are selected when sorting a report, the totals on the report may no

longer be accurate. When running a report with a Sort statement, use this section

of the manual to see which fields the report currently uses as sort fields to help

you ensure your sort field is a good choice.

Common Sort Examples

At the bottom of each report there is a list of some of the common sort and select

fields you might use in the report, along with the possible values for the field

listed.

Note Special care must be used when entering IDs which may have more than

one segment, such as Subaccount Numbers, as well as when entering dates

and fiscal periods. If you experience problems with these items in Sort/Select

statements, please review Date Values on Page 13, Dashes and Other Special

Characters on Page 13 or Fiscal Periods on Page 13.

Report Information

Page 73

Project Profile - Screen PA.010.00

This report shows significant data from the Project Master table. The tasks

for the project and their budgets appear in the lower portion of the report.

The account categories whose budgets are presented must have the

Budgeted switch set to Yes in Acct Category Maintenance (PA.ACC.00).

The sort number assigned to the account category determines the relative

order in which the account categories appear.

Report Formats Report Name Master Table Default Sort Fields Standard Pa010 Pjproj Pjproj.project

Pjproj.pjt_entity

@acctsort

The following table shows fields typically used for Sort/Select parameters for

this report:

Sort/Select Item Field Name Format / Possible Values Project ID Pjproj.project Valid Project ID

Project Description Pjproj.project_desc Valid Project Description

Project Task ID Pjproj.pjt_entity Valid Task ID

Subaccount Number Pjproj.gl_subacct Valid Subaccount Number

Customer ID Pjproj.customer Valid Customer ID

Customer Name Customer.name Valid Customer Name

Contract Number Pjproj.contract Valid Contract Number

Contract Type Pjproj.contract_type CP, CPFF, CPIA, FP, FPCS, FPE,

FPTM, INTR, TM, TMR, UP

Project Start Date Pjproj.start_date 01/01/2001

Project End Date Pjproj.end_date 12/31/2001


74 Page

Tasks Report (PA.020.00)

This report produces a listing of tasks for each project. Task information

shown includes task ID, description, start and end dates, status, and

General Ledger subaccount.

Report Formats Report Name Master Table Default Sort Fields Standard Pa020 Pjpro Pjproj.project

Pjpent.pjt_entity


this report:







Report Information

Page 75

Budget Reports Report (PA.030.00)

The Budget Reports (PA.030.00) present comparisons of different types of

budgets. The Orig Budget, EAC and Variances (PA.030.00) report

compares the original budget amount and units against the EAC (estimate

at completion) amount and units for each task of a project and calculates

the variance between each budget type.

The Orig Budget, EAC and FAC (PA.030.00) report presents all three

types of budget data that are used in Project Management and Accounting.

The budgeted amount and units are shown for the original budget, the

EAC, and the FAC (forecast at completion).

Report Formats Report Name Master Table Default Sort Fields Orig Budget, EAC and

Variances

Pa030 Pjproj Pjproj.project

Pjpent.pjt_entity

Pjacct.sort_num

Pjptdsum.acct

Orig Budget, EAC and FAC Pa030f Pjproj Pjproj.project

Pjpent.pjt_entity

Pjacct.sort_num

Pjptdsum.acct


this report:







Account Category Pjptdsum.acct Valid Account Category


76 Page

Account Category Report (PA.040.00)

This report produces a listing of the account categories on file and shows

the account category code, description, type, sort number, and status. The

report is sorted alphabetically by account category.

Report Formats Report Name Master Table Default Sort Fields Standard Pa040 Pjacct Pjacct.acct


this report:

Sort/Select Item Field Name Format / Possible Values Account Category Pjacct.acct Valid Account Category

Account Category Description Pjacct.acct_desc Valid Account Category

Description

Account Category Status Pjacct.acct_status A – Active

I – Inactive

P – Purge

Account Category Group Pjacct.acct_group_cd Valid Account Category Group

Account Category Type Pjacct.acct_type AS – Asset

EX – Expense

NA – Non Accounting

LB – Liability

RV – Revenue

Report Information

Page 77

Employee Report (PA.050.00)

The Employee Report (PA.050.00) displays information from the

Employee Master table.

Report Formats Report Name Master Table Default Sort Fields Standard Pa050 Pjemploy Pjemploy.emp_name

Pjemploy.employee


this report:

Sort/Select Item Field Name Format / Possible Values Employee Name Pjemploy.emp_name Valid Employee Name

Employee ID Pjemploy.employee Valid Employee ID

Status Pjemploy.emp_status A – Active

H – Hold

I – Inactive

P – Purge

First Manager Pjemploy.manager1 Valid Employee ID

Second Manager Pjemploy.manager2 Valid Employee ID

Type Pjemploy.emp_type_cd Valid Employee Type


78 Page

Project Charges Summary/Detail Report (PA.060.00)

This report provides an audit trail for those transactions input directly into

Project Controller via Project Charge Entry (PA.CHG.00). Both summary

and detailed versions of the report are available. The summary version

presents only basic data such as project ID and description, task ID and

description, account category, transaction date, comment, units, and

amount, displaying two lines of information per entry.

Note: The entries made in Project Charge Entry (PA.CHG.00) do not

update the financial modules.

The detailed version of the report displays much of the subsidiary

transaction information such as employee ID, vendor ID, voucher number,

invoice number, etc. Options include the ability to select batches by status

(print only posted batches or print only unposted batches).

Report Formats Report Name Master Table Default Sort Fields Project Charges Summary Pa060 Pjchargh Pjchargh.batch_id

Pjcharghd.detail_num

Project Charges Detail Pa060 Pjchargh Pjchargh.batch_id

Pjcharghd.detail_num


this report:

Sort/Select Item Field Name Format / Possible Values Batch Number Pjchargh.batch_id Valid Batch Number

Account Category Pjchargd.acct Valid Account Category

Account Number Pjchargd.gl_acct Valid Account Number

Subaccount Number Pjchargd.gl_subacct Valid Subaccount Number

Inventory ID Pjchargd.invtid Valid Inventory ID

Project ID Pjchargd.project Valid Project Id

Task ID Pjchargd.pjt_entity Valid Task ID

Transaction Date Pjchargd.trans_date 09/27/00 or 09/27/2000

Vendor ID Pjchargd.vendor_num Valid Vendor ID

Voucher Number Pjchargd.voucher_num Valid Reference Number

Report Information

Page 79

Transaction List By Batch Report (PA.070.00)

This report displays the transactions contained in a specific batch. The

batch may have originated within Project Controller (a final revenue

recognition process generates this report automatically) or in other

modules such as Accounts Payable or Accounts Receivable. The

information is sorted by project, task, account category, and date.

Report Formats Report Name Master Table Default Sort Fields Standard Pa070 Pjtran Pjtran.fiscalno

Pjtran.system_cd

Pjtran.batch_id

Pjtran.detail_num


this report:

Sort/Select Item Field Name Format / Possible Values Batch Number Pjtran.batch_id Valid Batch Number

Account Category Pjtran.acct Valid Account Category

Employee ID Pjtran.employee Valid Employee ID

Account Number Pjtran.gl_acct Valid Account Number

Subaccount Number Pjtran.gl_subacct Valid Subaccount Number

Project ID Pjtran.project Valid Project ID

Task ID Pjtran.pjt_entity Valid Task ID

Fiscal Period Pjtran.fiscalno 200011

Transaction Date Pjtran.trans_date 09/27/00 or 09/27/2000

Vendor ID Pjtran.vendor_num Valid Vendor Number


80 Page

Account Category/GL Account XREF Report (PA.080.00)

This report provide a cross-reference between the account category codes

and the General Ledger account numbers with which they are associated.

The Account Category XREF (PA.080.00) report lists, by account

category, all the General Ledger account numbers linked to each account

category. The report presents such data as account category description

and status and account number description and status.

The GL Account XREF (PA.080.00) report presents the same data sorted

by the General Ledger account number. The report lists each account

number that is linked to an account category with its associated account

category beside it.

Report Formats Report Name Master Table Default Sort Fields Account Category XREF Pa080a Pj_Account Pj_Account.acct

Pj_Account.gl_acct

GL Account XREF Pa080b Pj_Account Pj_Account.gl_acct

Pj_Account.acct


this report:

Sort/Select Item Field Name Format / Possible Values Account Category Pjacct.acct Valid Account Category

Account Category Description Pjacct.acct_desc Valid Account Category

Description

Account Category Status Pjacct.acct_status A – Active

I – Inactive

P – Purge

Account Category Group Pjacct.acct_group_cd Valid Account Category Group

Account Category Type Pjacct.acct_type AS – Asset

EX – Expense

NA – Non Accounting

LB – Liability

RV - Revenue

Report Information

Page 81

Project Task Summary Report (PA.100.00)

This report can be used for a variety of purposes depending on the column

definitions. The example presents a comparison of current and project-to-

date labor expenditures (both amount and units) against the EAC

(estimated at completion) amount for the same labor account categories. It

also compares the total amount billable against the amount billed,

calculating the unbilled balance as the variance. The columns for this

report are defined using Flexible Report Column Maintenance

(PA.RPC.00).

Report Formats Report Name Master Table Default Sort Fields 0 Project Task Summary Pa100 Pjptdsum Pjptdsum.project

Pjptdsum.pjt_entity

@acctsort

Pjrepcol.column_nbr

0 Project Task Summary

(Curr)

Pa100 Pjptdsum Pjptdsum.project

Pjptdsum.pjt_entity

@acctsort

Pjrepcol.column_nbr


this report:

Sort/Select Item Field Name Format / Possible Values Project ID Pjptdsum.project Valid Project ID

Task ID Pjptdsum.pjt_entity Valid Task ID



82 Page

Project Aging/Recap Report (PA.110.00)

This report shows aged receivables by subaccount, project manager,

customer, project, and invoice in detail or recap(summary) format. Any

retained amounts also appear on the report. The Project Aging/Recap

Report (PA.110.00) presents the aged receivables with the invoice detail

suppressed.

Report Formats Report Name Master Table Default Sort Fields Project AR Aging Report Pa110 Ardoc Pjproj.gl_subacct

Pjemploy.emp_name

Pjproj.manager1

Ardoc.custid

Ardoc.ProjectId

Ardoc.Refnbr

Project AR Aging Recap

Report

Pa110 Ardoc Pjproj.gl_subacct

Pjemploy.emp_name

Pjproj.manager1

Ardoc.custid

Ardoc.ProjectId

Ardoc.Refnbr

Project AR Aging Graph Pa110 Ardoc @manager

Customer.name

Pjproj.project_desc

Ardoc.Refnbr


this report:

Sort/Select Item Field Name Format / Possible Values General Ledger Subaccount Pjproj.gl_subacct Valid Subaccount Number

Account Category Pjproj.acct Valid Account Category

Employee Name Pjemploy.emp_name Valid Employee Name

Employee ID Pjemploy.employee Valid Employee ID

Customer ID Ardoc.custid Valid Customer ID


Invoice Number Ardoc.refnbr Valid Reference Number

Project ID Ardoc.projectid Valid Project ID

Invoice Date Ardoc.docdate 09/27/00 or 09/27/2000

Report Information

Page 83

Project Profitability Report (PA.120.00)

This report presents a summary of revenue, expense, and margin data for

month-to-date, year-to-date, and project-to-date periods by subaccount,

project manager, customer, and project.

Report Formats Report Name Master Table Default Sort Fields Standard Pa120 Pjactsum Pjproj.gl_subacct

Pjemploy.emp_name

Pjproj.manager1

Pjproj.customer

Pjactsum.project

Pjactsum.pjt_entity

@acctsort


this report:

Sort/Select Item Field Name Format / Possible Values Subaccount Number Pjproj.gl_subacct Valid Subaccount Number

Account Category Pjproj.acct Valid Account Category

Project Manager Pjproj.manager1 Valid Employee ID




Project ID Pjactsum.project Valid Project ID

Task ID Pjactsum_pjt_entity Valid Task ID


84 Page

Project Billing Analysis Report (PA.130.00)

This report shows the unbilled balance of each task of a project and to

compare the amount billed against the maximum billable amount.

Report Formats Report Name Master Table Default Sort Fields Standard Pa130 Pjptdsum Pjproj.gl_subacct

Pjemploy.emp_name

Pjproj.manager1

Pjptdsum.project

Pjptdsum.pjt_entity

Pjptdsum.acct

Pjrepcol.column_nbr


this report.

Sort/Select Item Field Name Format / Possible Values Subaccount Pjproj.gl_subacct Valid Subaccount Number




Project ID Pjptdsum.project Valid Project ID


Report Information

Page 85

Project Task Analysis Report (PA.140.00)

This report can serve a variety of purposes depending on how the columns

are defined. The example shows labor hours, labor amount, and travel

amount for month-to-date (MTD) and project-to-date (PTD) periods. The

account categories being reported are defined in Flexible Report Column

Maintenance (PA.RPC.00). The MTD and PTD periods, as well as the

committed, total, period-to-date EAC, and variance columns are

predefined in the report layout.

Report Formats Report Name Master Table Default Sort Fields Standard Pa140 Pjptdsum Pjproj.gl_subacct

Pjemploy.emp_name

Pjproj.manager1

Pjptdsum.project

Pjptdsum.pjt_entity

@acctsort

Pjrepcol.column_nbr


this report.








86 Page

Project Transactions Report (PA.150.00)

This report will produce a listing of the project transaction records by

project for a selected period, including the amount and hours or units for

each transaction. The report sums the totals for each project and inserts a

page break at each new project.

Report Formats Report Name Master Table Default Sort Fields Standard Pa150 Pjtran Pjproj.gl_subacct

Pjmgr.emp_name

Pjproj.manager1

Pjtran.project

Pjtran.pjt_entity

Pjacct.sort_num

Pjtran.acct

Pjtran.trans_date


this report:

Sort/Select Item Field Name Format / Possible Values Batch Number Pjtran.batch_id Valid Batch Number

Account Category Pjtran.acct Valid Account Category

Employee ID Pjtran.employee Valid Employee ID

Employee Name Pjmgr.emp_name Valid Employee Name

Account Number Pjtran.gl_acct Valid Account Number

Subaccount Number Pjtran.gl_subacct Valid Subaccount Number

Project ID Pjtran.project Valid Project ID

Task ID Pjtran.pjt_entity Valid Task ID

Fiscal Period Pjtran.fiscalno 200011

Transaction Date Pjtran.trans_date 09/27/00 or 09/27/2000

Vendor ID Pjtran.vendor_num Valid Vendor Number

Report Information

Page 87

Project Cost Analysis Report (PA.160.00)

This report provides detailed cost information for charges associated with

a project. Only account categories defined as expenses appear on the

report. The detail line is at the account category level for each task with

subtotals by task and project. The estimate at completion (EAC) and either

original budget or forecast-at-completion (FAC) amounts are displayed on

the detail line along with month-to-date and project-to-date actual costs.

Percent complete figures, both reported and computed, also appear.

The report is sorted first by project ID, then by task ID, then by account

category. A page break occurs with a change in project.

Report Formats Report Name Master Table Default Sort Fields Estimated Pjt Cost Analysis Pa160 Pjptdsum Pjptdsum.project

Pjptdsum.pjt_entity

@acctsort

Forecasted Pjt Cost Analysis Pa160f Pjptdsum Pjptdsum.project

Pjptdsum.pjt_entity

@acctsort


this report:

Sort/Select Item Field Name Format / Possible Values Project Manager Pjproj.manager1 Valid Employee ID




Subaccount Pjproj.gl_subacct Valid Subaccount Number


88 Page

Project List Report (PA.170.00)

This report provides a master listing of projects on file. Information

presented includes the project ID and description, project manager,

company, customer, contract number, contract type, revenue recognition

method, start and end dates, and reported completion percentage at the

project level.

Report Formats Report Name Master Table Default Sort Fields Standard Pa170 Pjproj Pjproj.project


this report.








Report Information

Page 89

Revenue & Billing Status Report (PA.180.00)

This report displays a summary of the billing status and revenue by

project. Information displayed includes project ID and description,

contract type, revenue recognition method, project status, contract value,

revenue-to-date, billed-to-date, unbilled, retained amount (if applicable),

work in process, revenue backlog and billing backlog amounts. Totals are

shown by project manager.

Report Formats Report Name Master Table Default Sort Fields Standard Pa180 Pjptdrol Pjproj.gl_subacct

@managernameandnum

@contracttypeandproject

@acctsort


this report:


Account Category Pjptdrol.acct Valid Account Category


Contract Type Pjproj.contract_type CP, CPFF, CPIA, FP, FPCS,

FPE,FPTM, INTR, TM, TMR, UP

Project ID Pjptdrol.project Valid Project ID


90 Page

Billing Worksheet by Task/Project Report (PA.190.00)

This report is a turnaround documents designed to assist in determining

what to bill for the current period. Two versions of the report are

available. The Billing Worksheet by Project (PA.190.00) report presents a

project-level summary of charges preceding the current fiscal period,

current charges, prior billed amounts, and a calculated unbilled balance

owed by the customer. The columns to the right of the report are intended

as workspace to note adjustments or comments as desired. The Billing

Worksheet by Task (PA.190.00) report presents the same data at the task

level (where appropriate) as the Billing Worksheet by Project (PA.190.00)

report.

Report Formats Report Name Master Table Default Sort Fields Billing Worksheet by Task PA190a Pjproj Pjproj.gl_subacct

@managernameandnum

Pjproj.project

Pjactsum.pjt_entity

@wAcctgroup

@wBillaccount

@wSourceacctgroup

Billing Worksheet by Project PA190b Pjproj Pjproj.gl_subacct

@managernameandnum

Pjproj.project

@wAcctgroup

@wBillaccount

@wSourceacctgroup

This is a temporary field calculated for this report and is not stored in the

database. Therefore, the field is not available for Sort/Select statements in the

field list.


this report.


Task ID Pjactsum.pjt_entity Valid Task ID

Account Category Pjactsum.acct Valid Account Category



Report Information

Page 91

Budget vs Actual Amounts/Units Report (PA.200.00)

This report compares EAC and actual amounts for all revenue and expense

account categories for each task of a project. The total column for

expenses sums actual expenses and purchasing commitments. For each

task, there are expense, revenue, and net profit sections. In the expense

and revenue sections, there is one line of detail for each account category.

The account categories within the section are presented in sort number

order (assigned in the Acct Category Maintenance function). The report is

sorted by project, customer ID, and project manager. Each task begins on

a new page.

Report Formats Report Name Master Table Default Sort Fields Budget vs Actual Amounts Pa200 Pjptdsum Pjpjtmgr.emp_name

Pjproj.customer

Pjptdsum.project

Pjptdsum.pjt_entity

Pjacct.acct_type

Pjacct.sort_num

Pjptdsum.acct

Budget vs Actual Units Pa200 Pjptdsum Pjpjtmgr.emp_name

Pjproj.customer

Pjptdsum.project

Pjptdsum.pjt_entity

Pjacct.acct_type

Pjacct.sort_num

Pjptdsum.acct


this report:

Sort/Select Item Field Name Format / Possible Values Project Manager Pjpjtmgr.emp_name Valid Employee ID







92 Page

Units of Production Report (PA.210.00)

This report presents an analysis of actual vs. EAC (estimate at completion)

units of production.

Report Formats Report Name Master Table Default Sort Fields Standard Pa210 Pjptdsum Pjemploy.emp_name

Pjptdsum.project

Pjptdsum.pjt_entity

Pjptdsum.acct

Pjactsum.fsyear_num

Pjtran.fiscalno

Pjtran.trans_date


this report.

Sort/Select Item Field Name Format / Possible Values Project Manager Pjproj.manager1 Valid Employee ID






Report Information

Page 93

Transaction Transfer Messages Report (PA.220.00)

This report provides an audit trail of reclassified or transferred transactions

processed by Project Transaction Transfer (PA.PTT.00).

Report Formats Report Name Master Table Default Sort Fields Standard Pa220 Pjcommun @moduleandbatch


this report:

Sort/Select Item Field Name Format / Possible Values Message type Pjcommun.msg_type Valid Message type

Module Pjcommun.source_function Valid Module


94 Page

Week End Date Listing Report (PA.910.00)

This report shows the labor periods used in the Time and Expense for

Projects module.

Report Formats Report Name Master Table Default Sort Fields Standard Pa910 Pjweek Pjweek.period_num

Pjweek.week_num

Pjweek.we_date


this report:

Sort/Select Item Field Name Format / Possible Values Period Pjweek.period_num 200009

Report Information

Page 95


96 Page

Code File Report (PA.810.00)

This report generates a hardcopy listing of the valid codes for each code

type in the Code File table (PJCODE). The report, which is sorted by code

type, displays attributes about the code type such as its length, whether it

is user- or system-defined, and whether there are ancillary data fields

associated with the code values. Following the code type information is a

listing of all values defined for the code type, description, and ancillary

values, if present.

Report Formats Report Name Master Table Default Sort Fields Standard Pa810 Pjcode Pjcode.code_type

Pjcode.code_value


this report:

Sort/Select Item Field Name Format / Possible Values Code Type Pjcode.code_type Valid Code Type

Code Value Pjcode.code_value Valid Code Value

Code Value Description Pjcode.code_value_desc Valid Code Value Description

Report Information

Page 97

Code Type Report (PA.820.00)

This report lists all the information about the various code types in use

within Project Management and Accounting.

Report Formats Report Name Master Table Default Sort Fields Standard Pa820 Pjcontrl Pjcontrl.control_code


this report:

Sort/Select Item Field Name Format / Possible Values Control Type Pjcontrl.control_code Valid Control Code

Control Code ID Pjcontrl.control_code Valid Code ID

Code Description Pjcontrl.control_desc Valid Code Description


98 Page

ID Field Report (PA.830.00)

This report lists all the information about the various ID fields in use

within Project Management and Accounting.

Report Formats Report Name Master Table Default Sort Fields Standard Pa830 Pjcontrl @wtableid

Pjcontrl.control_code


this report:

Sort/Select Item Field Name Format / Possible Values Code Type Pjcontrl.control_type Valid Code Type

Code ID Pjcontrl.control_code Valid Code ID


Report Information

Page 99


100 Page

Control Parameters List Report (PA.840.00)

This report shows the entries in the control file (PJCONTRL). Many

system parameters, including those established in the various setup

screens, are stored in this table. Those few parameters that must be set up

directly are entered in Control Parameter Maintenance (PA.CNT.00).

Access to the screen and to this report is usually restricted to the system

administrator.

Report Formats Report Name Master Table Default Sort Fields Standard Pa840 Pjcontrl @controltypeandcode


this report:

Sort/Select Item Field Name Format / Possible Values Code Type Pjcontrl.control_type Valid Code Type

Code ID Pjcontrl.control_code Valid Code ID


Report Information

Page 101

Report Column Listing Report (PA.850.00)

This report shows the column definitions of the flexible column reports

Report Formats Report Name Master Table Default Sort Fields Standard Pa850 Pjrepcol Pjrepcol.report_code

Pjrepcol.column_nbr

Pjrepcol.acct

Pjrepcol.gl_acct


this report:

Sort/Select Item Field Name Format / Possible Values Report Code Pjrepcol.report_code Valid Report Code

Account Category Pjrepcol.acct Valid Account Category

Account Number Pjrepcol.gl_acct Valid Account Number


102 Page

Pjt GL Account Distribution Report (PA.900.00)

This report is a financial audit trail document that has been modified to include

project-task information. The report is sorted by system (Accounts Payable,

Accounts Receivable, etc.), batch number, and General Ledger account number,

and shows one line per General Ledger journal detail with its associated project-

task, if available.

Report Formats Report Name Master Table Default Sort Fields Standard Pa900 Gltran @modbatnbr

@acctsub

gltran.module

gltran.batnbr

gltran.acct

gltran.sub


this report.

Sort/Select Item Field Name Format / Possible Values Batch Number Gltran.batnbr Valid Batch Number

Account Number Gltran.acct Valid Account Number

Account Category Account.acct_cat Valid Account Category

Subaccount Number Gltran.sub Valid Subaccount Number

Project ID Gltran.projectid Valid Project ID

Task ID Gltran.taskid Valid Task ID

Transaction Date Gltran.trandate 09/27/00 or 09/27/2000

Report Information

Page 103

Job Summary Report (PA.300.00)

This report shows a summary of project and task labor, ODCs, indirect costs,

revenue, and fee (profit). Columns display prior years, current period, year-to-

date, project-to-date, EAC, backlog, and committed amounts. Committed costs

appear from subcontractors (in the Contract Management module), open

purchase orders, and labor (if entered in the Time and Expense for Projects

module).

Report Formats Report Name Master Table Default Sort Fields

0 Project at Target PA300a Pjvjobsummary Pjvjobsummary.project

Pjvjobsummary.column_nbr

Pjvjobsummary.sort_nbr

Pjvjobsummary.acct

0 Task at Target PA300b Pjvjobsummary Pjvjobsummary.project

Pjvjobsummary.task



Pjvjobsummary.acct

0 Project at Actual PA300c Pjvjobsummary Pjvjobsummary.project



Pjvjobsummary.acct

0 Task at Actual PA300d Pjvjobsummary Pjvjobsummary.project

Pjvjobsummary.task



Pjvjobsummary.acct

The following table shows fields typically used for Sort and Select parameters for

this report:

Sort/Select Item Field Name Format / Possible Values


104 Page

Labor Hours Detail (PA.310.00)

This report displays hours incurred for the project. It includes columns for

current period, year-to-date, and project-to-date.


Default Format Only PA310 Pjvjobdetailhrs Pjvjobdetailhrs.project

Pjvjobdetailhrs.pjt_entity

Pjvjobdetailhrs.sort_num

Pjvjobdetailhrs.acct

Pjvjobdetailhrs.code_value

Pjvjobdetailhrs.emp_name


this report:


Report Information

Page 105

Labor Hours and Cost Detail (PA.320.00)

This report displays labor hours and amounts incurred for the project. It provides

supporting detail for the total labor amounts that appear on the Job Summary

Reports (PA.300.00) and includes columns for current period, year-to-date, and

project-to-date.


Default Format Only PA320 Pjvjobdetailhrs Pjvjobdetailhrs.project

Pjvjobdetailhrs.pjt_entity

Pjvjobdetailhrs.acct

Pjvjobdetailhrs.code_value

Pjvjobdetailhrs.emp_name


this report:



106 Page

ODC Detail (PA.330.00)

This report provides supporting detail for the total ODC amounts that appear on

the Job Summary Reports (PA.300.00).


Default Format Only PA330 Pvjobdetailodc Pvjobdetailodc.project

Pvjobdetailodc.pjt_entity

Pvjobdetailodc.acct


this report:


Report Information

Page 107

Revenue Detail (PA.340.00)

This report provides supporting detail for the total revenue amounts that appear

on the Job Summary Reports (PA.300.00).


Default Format Only PA340 Pvjjobbilling Pvjjobbilling.project

Pvjjobbilling.pjt_entity

Pvjjobbilling.column_nbr

Pvjjobbilling.sort_num

@job_category

NOTE: The @ symbol indicates a formula field created in the Crystal Report

Writer. You cannot use formula fields in Sort or Select statements.


this report:



108 Page

Cost Summary (PA.350.00)

This report summarizes costs incurred by project. It displays labor, ODCs, and

indirect costs per a given period. You can define up to seven groups of cost

account categories.


0 Cost Summary at Target PA350A Pvjobcost Pvjobcost.project

Pjvjobcost.pjt_entity

0 Cost Summary at Actual PA350B Pvjobcost Pvjobcost.project

Pvjobcost.task


this report:


Report Information

Page 109

Revenue Summary (PA.360.00)

This report provides supporting detail for the calculation of the fee (profit)

amount that appears on the Job Summary Reports (PA.300.00). They display

labor, ODCs, indirect costs, revenue, and fee per a given period.


0 Project Revenue at Target PA360A Pjvjobsummary Pjvjobsummary.project

Pjvjobsummary.task

0 Project Revenue at Actual PA360B Pjvjobsummary Pjvobsummary.project


this report:



110 Page

Indirect Cost Analysis Report (PA.370.00)

This report summarizes indirect costs incurred by project. It displays labor,

ODCs, and indirect costs at both target and actual. You can define up to seven

groups of cost account categories.


Default format only PA370 Pjvjobcostactual Pjvjobcostactual.project

Pjvjobcostactual.task

Pjvjobcostactual.acct


this report:


Documents

Project Controller Report