report assistant for microsoft dynamics™ sl -...
TRANSCRIPT
Report Assistant for
Microsoft Dynamics™ SL Project Controller Module
PPM6-PPC0-RA00000
RPMN-PPC0-RA00650 Last Revision: March 14, 2006
PPM6-PPC0-RA00000 RPMN-PPC0-RA00650 Last Revision: March 14, 2006
Disclaimer This document may contain technical inaccuracies or typographical errors. Any documentation with respect to Microsoft Business Solutions products is provided for information purposes only and does not extend or modify the limited warranty extended to the licensee of Microsoft Dynamics™ SL software products. The names of companies, products, people, and/or data used in window illustrations and sample output are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. The forms and policies presented in this manual may not be the most current available. Please contact the Training Group at Microsoft Business Solutions for the most up-to-date information. This manual has been developed for Microsoft Dynamics™ SL 6.5.
Copyright Manual copyright © 2006 Microsoft Corporation. All rights reserved. Your right to copy this documentation is limited by copyright law and the terms of the software license agreement. As the software licensee, you may make a reasonable number of copies or printouts for your own use. Making unauthorized copies, adaptations, compilations, or derivative works for commercial distribution is prohibited and constitutes a punishable violation of the law.
Trademark Microsoft, ActiveX, Excel, FRx, FrontPage, MapPoint, Outlook, SharePoint, Visual Basic, Visual Studio, Windows, Windows NT 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. Crystal Reports is a registered trademark of Business Objects SA. 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.
Table of Contents How to use this Manual 1
Introduction 2 Manual Sections 2
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 Charge Entry (PA.CHG.00) 26 Project Maintenance (PA.PRJ.00) 27 Project Maintenance – Task Tab (PA.PRJ.00) 28 Project Maintenance - Task Tab (PA.PRJ.00) – Customization Mode 29 Project Maintenance - Additional Info Tab (PA.PRJ.00) 30 Project Maintenance – Additional Info Tab (PA.PRJ.00) – Customization Mode 31 Billing Information Maintenance (BI.BMM.00) 32 Percent Complete and Revenue Recognition Setup (PA.PCM.00) 33 Address Maintenance (PA.ADR.00) 34 Contract Value and Revenue Information (PA.PRJ.04) 35 Budget Entry (PA.PRJ.03) 36 Budget Maintenance (PA.BSM.00) 37 Budget By Period (PA.BSM.01) 38 EAC By Period (PA.BSM.01) 39 Employee and Resource Maintenance (PA.EMP.00) 40 Employee and Resource Maintenance (PA.EMP.00) – Customization Manager 41 Project Employee Maintenance-Employees by Project (PA.PEM.00) 42 Project Employee Maintenance (PA.EMP.00) – Customization Manager 43
Project Employee Maintenance - Projects by Employee (PA.PEM.00)44 Project Employee Maintenance (PA.EMP.00) – Customization Manager 45 Project Net Profit (PA.PNR.00) – Amounts 46 Project Net Profit (PA.PNR.00) – Units 47 Task Net Profit (PA.PND.00) - Amounts 48 Task Net Profit (PA.PND.00) - Units 49 Project Summary Inquiry (PA.PSI.00) - Amounts 50 Project Summary Inquiry (PA.PSI.00) - Units 51 Transaction Detail Inquiry (PA.TRD.00) 52 Transaction Detail Inquiry (PA.TRD.00) – Customization Manager 53 Commitment Detail Inquiry (PA.CMD.00) 54 Commitment Detail Inquiry (PA.CMD.00) – Customization Manager 55 Account Category Maintenance (PA.ACC.00) 56 Account Category Maintenance – ID Fields (PA.ACC.00 57 Account Category Maintenance (PA.ACC.00) – Customization Manager 58 Account Category Maintenance-GL Cross-Reference (PA.ACC.00) 59 Code File Maintenance (PA.CFM.00) 60 Equipment/Resource Maintenance (PA.EQU.00) 61 Equipment/Resource Maintenance (PA.EQU.00) – Customization Manager 62 Equipment/Resource Maintenance-Additional Info (PA.EQU.00) 63 Equipment/Resource Maintenance (PA.EQU.00) – Customization Manager 64 Equipment Rate Maintenance (PA.ERM.00) 65 Equipment Rate Maintenance (PA.ERM.00) – Customization Manager66 Fiscal Period Maintenance (PA.FPM.00) 67 Flexible Report Column Maintenance (PA.RPC.00) 68 Message Text Maintenance (PA.MSG.00) 69 Site Maintenance (PA.SIT.00) 70
Report Information 71
Overview 72 Project Profile - Screen PA.010.00 73 Tasks Report - Screen PA.020.00 73 Budget Reports - Screen PA.030.00 74 Account Category Maintenance – Screen PA.040.00 74 Employee Report – Screen PA.050.00 75 Project Charges Summary/Detail – Screen PA.060.00 75 Transaction List By Batch – Screen PA.070.00 76 Account Category/GL Account XREF - Screen PA.080.00 76 Project Task Summary - Screen PA.100.00 77 Project AR Aging/Recap Report - Screen PA.110.00 77 Project Profitability Report - Screen PA.120.00 78 Project Billing Analysis - Screen PA.130.00 79
Project Task Analysis - Screen PA.140.00 79 Project Transactions - Screen PA.150.00 80 Project Cost Analysis - Screen PA.160.00 80 Project List - Screen PA.170.00 81 Revenue & Billing Status Rpt – Screen PA.180.00 81 Billing Worksheet by Task/Project – Screen PA.190.00 82 Budget vs Actual Amounts/Units – Screen PA.200.00 83 Units of Production Report - Screen PA.210.00 83 Transaction Transfer Messages Report - Screen PA.220.00 84 Week Ending List - Screen PA.910.00 84 Code File Report - Screen PA.810.00 85 Code Type Report - Screen PA.820.00 85 ID Field Report - Screen PA.830.00 85 Control Parameters List - Screen PA.840.00 86 Report Column Listing - Screen PA.850.00 86 Pjt GL Account Distribution - Screen PA.900.00 86
Index 89
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.
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
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.
2 Page
How to Use This Manual
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.
Page 3
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
4 Page
S O R T A N D S E L E C T S TAT E M E N T S
What you will learn in this section: 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
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.
6 Page
Sort and Select Statements
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.
Page 7
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
FIGURE 1-2: SELECT TAB
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.
Field Operator Value Boolean Pjproj.project Contains 123 And
8 Page
Sort and Select Statements
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
Page 9
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
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).
10 Page
Sort and Select Statements
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.
Page 11
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
FIGURE 1-3: SELECT TAB
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
12 Page
Sort and Select Statements
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
Page 13
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
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.
FIGURE 1-4: SELECT TAB
14 Page
Sort and Select Statements
• 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
Page 15
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
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.
16 Page
Sort and Select Statements
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
Page 17
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
FIGURE 1-7: SUMMARY PROJECT LIST REPORT WITH SORT ON PROJECT MANAGER NAME
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.
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
18 Page
Sort and Select Statements
FIGURE 1-8: PROJECT LIST WITH A PAGE BREAK BY PROJECT ID
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-9: 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
Page 19
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
CAUTION: The Total Break does not always work properly therefore you should review the report carefully if you have selected a Total Break.
FIGURE 1-10: PROJECT PROFILE WITH DEFAULT SORT
FIGURE 1-11: PROJECT PROFILE WITH SORT AND TOTAL BREAK ON PROJECT ID
20 Page
Sort and Select Statements
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
Page 21
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
22 Page
D ATA F I E L D I L L U S T R AT I O N S
What you will learn in this section: 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.
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
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).
24 Page
Data Field Illustrations
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.
Page 25
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Project Charge Entry (PA.CHG.00)
Pjchargd.acct
Pjchargd.gl_subacct
Pjchargh.batch_amountPjchargh.batch_bal
Pjchargd.voucher_line
Pjchargd.gl_acct
Pjchargd.voucher_num
Pjchargh.batch_id
Pjchargd.project
Pjchargh.rate_type_cd Pjchargh.last_detail_num Pjchargh.system_cd
Pjchargd.employee
Pjchargd.auto_recalc_sw
Pjchargd.cpnyid
Pjchargd.pjt_entity
Pjchargd.trans_date
Pjchargd.tr_comment
Pjchargd.bill_batch_id
Pjchargd.tr_id04
Pjchargd.tr_id05
Pjchargd.equip_id
Pjchargd.data1
Pjchargh.fiscalno
Pjchargh.batch_desc1
Pjchargd.units Pjchargd.tr_id02
Pjchargd.amount
Pjchargd.unit_of_measure
Pjchargh.batch_type Pjchargh.rate_table_id Pjchargh.batch_status
Pjchargd.vendor_num
Pjchargd.tr_id01
Pjchargd.tr_id03
Pjchargd.tr_id08
26 Page
Data Field Illustrations
Project Maintenance (PA.PRJ.00)
Pjproj.project
Pjproj.project_desc
Pjproj.CpnyId
Company.cpnyname
Pjproj.start_date
Pjproj.end_date
Pjproj.contract
Pjproj.purchase_order_num
Pjproj.contract_type
Pjprojex.rev_type Pjproj.bf_values_switch
Pjproj.gl_subacct
Subacct.descr
Pjproj.status_pa
Pjproj.status_ap
Pjproj.status_po Pjproj.status_ar Pjproj.status_gl
Pjproj.manager1
Prjmgr.name
Pjproj.manager2
Pjproj.customer
Customer.name
Pjproj.billcuryid
Currncy.descr
Pjproj.alloc_method_cd
Pjproj.rate_table_id
Pjproj.labor_gl_acct
Pjprojex.rate_table_labor Pjproj.status_lb Pjproj.status_in
Prjsuper.name
Curryrttp.descr Pjcode.code_value_desc
Pjproj.status_19
Pjproj.billratetypeid
Pjproj.billcuryfixedrate
Pjcode.code_value_desc
Pjcode.code_value_desc Pjproj.status_18
Page 27
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Project Maintenance – Task Tab (PA.PRJ.00)
Pjpent.pjt_entity
Pjpent.pjt_entity_desc
Pjpent.contract_type
Pjpent.manager1
Pjemploy2.emp_name
Pjpent.pe_id01
Pjpent.pe_id02
Pjpent.pe_id05
Pjpent.pe_id03
Pjpent.pe_id08
Pjpent.pe_id09
Pjpent.status_pa Pjpent.status_ap
Pjpent.status_ar
Pjpent.status_gl
Pjpent.status_po
Pjpent.status_lb
Pjpent.status_in
Pjpent.start_date
Pjpent.end_date
Pjpent.fips_num
Pjpentex.pe _id12 Pjpentex.pe_id13 Pjpentex.pe_id14
Pjpentex.pe_id23
Pjpent.status_08
Pjpent.labor_class_cd
Pjpent.pe_id36
Pjpent.pe_id35
28 Page
Data Field Illustrations
Project Maintenance - Task Tab (PA.PRJ.00) – Customization Mode
Pjpent.pe_id04
Pjpent.pe_id06
Pjpent.pe_id07
Pjpent.pe_id10
Pjpentex.pe_id21
Pjpentex.pe_id22
Pjpentex.pe_id25
Pjpent.MSPInterface
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.
Page 29
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Project Maintenance - Additional Info Tab (PA.PRJ.00)
Pjproj.ShiptoId
Pjproj.pm_id02
Pjproj.pm_id04
Pjprojex.pm_id14
Pjprojex.pm_id15
Pjprojex.work_location
Pjprojex.work_comp_cd
Pjcode.code_value_desc
Pjproj.Curyid
Currncy.descr
Pjproj.probability
Pjproj.pm_id01
30 Page
Data Field Illustrations
Project Maintenance – Additional Info Tab (PA.PRJ.00) – Customization Mode
P jpro j.pm _id03
P jpro j.pm _id05
P jpro j.pm _id09
P jpro jex .pm _id12
P jpro j.pm _id06
P jpro j.pm _id07
P jpro j.pm _id08
P jpro jex .pm _id11
P jpro jex .pm _id13
P jpro jex .pm _id22
P jp ro jex .pm _id30
P jpro jex .pm _id20
P jpro jex .pm _id25
P jpro jex .pm _id26
P jpro jex .pm _id27
P jpro jex .pm _id28
P jpro jex .pm _id29
P jpro jex .pm _id24
P jpro jex .pm _id21
P jpro jex .pm _id23
P jpro jex .pm _id16 P jpro jex .pm _id10
P jp ro jex .pm _id19 P jp ro jex .pm _id17
P jpro jex .pm _id18
P jpro j.pm _id40
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.
Page 31
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Billing Information Maintenance (BI.BMM.00)
Pjbill.project
Projdesc.bw_desc
Pjbill.project_billwith
Pjbill.inv_format_cd
Pjbill.inv_attach_cd
Pjbill.date_print_cd
Pjbill.copy_num
Pjbill.last_bill_date
Pjbill.bill_type_cd
Pjbill.retention_method
Pjbill.retention_percent
Pjbill.billings_cycle_cd
Pjbill.pb_id20
Pjbill.approval_sw Pjbill.approver Pjbill.biller Pjbill.pb_id13 Names.biller
Prjdesc.pj_desc
Pjcode.code_value_desc
Pjcode.code_value_desc
Pjcode.code_value_desc
Pjcode.code_value_desc
Names.approver
Pjcode.code_value_desc
Note Billing Information Maintenance (BI.BMM.00) is a screen associated with the Flexible Billings module that can be accessed from Project Maintenance (PA.PRJ.00).
32 Page
Data Field Illustrations
Percent Complete and Revenue Recognition Setup (PA.PCM.00)
Pjprojex.project Pjproj.project_desc Pjprojex.rev_type
Rrflags.task_flag
Pjprojex.entered_pc
Pjprojex.pm_id24
Pjprojex.revision_datePjpentex.pj_entity
Pjpent.pjt_entity_desc
Pjpentex.entered_pc
Pjpentex.revision_date
Pjpentex.pe_id20 Pjpentex.pe_id24
Rrflags.units_flag
Rrflags.tasksubacct_flag
Rrflags.rracct_type
Page 33
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Address Maintenance (PA.ADR.00)
Pjaddr.comp_name
Pjcode.code_value_desc
Pjaddr.addr_type_cd
Pjaddr.addr_key
Pjaddr.addr2
Pjaddr.email Pjaddr.country
Pjaddr.fax
Pjaddr.phone
Pjaddr.state
Pjaddr.zip
Pjaddr.city
Pjaddr.addr1
Pjaddr.individual
Pjaddr.title
34 Page
Data Field Illustrations
Contract Value and Revenue Information (PA.PRJ.04)
Pjptdrv.eac_units
Pjptdrv.eac_amount
Pjptdrcv.eac_units
Pjptdcv.eac_amount
Note This screen displays both the amount and units for the Contract Value and Revenue Budget at the project level. Data is obtained from PJPTDROL (Project Rollup Table) based on the Contract Value and Revenue account categories. The Account categories used for Contract Value and Revenue are entered in Project Controller Setup (PA.SET.00).
Page 35
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Budget Entry (PA.PRJ.03)
Pjptdsum.pjt_entity
Pjptdsum.acct
Pjptdsum.total_budget_units
Pjptdsum.rate
Pjptdsum.total_budget_amount
36 Page
Data Field Illustrations
Budget Maintenance (PA.BSM.00)
Pjpent.project
Pjpent.pjt_entity
Pjproj.project_desc
Pjpent.pjt_entity_desc
Pjptdsum.acct
Pjptdsum.total_budget_units Pjptdsum.rate Pjptdsum.total_budget_amount Pjptdsum.eac_units
Pjptdsum.eac_amount
Pjacct.acct_desc
Page 37
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Budget By Period (PA.BSM.01)
Pjptdsum.project Pjptdsum.pjt_entity Pjtddsum.acct Pjbudsum.fsyear_num
Pjbudsum.lupd_datetime
Pjbudsum.units_01
Pjbudsum.amount_01
Pjbudsum.units_09
Pjbudsum.amount_09
Pjbudsum.total_units Pjbudsum.total_amount
Note The name of each field is consistent except for the numbers always equal the period. For example, all of the fields for period 1 end with 01 and all fields for period 9 end with 09.
Note Both Budget By Period and EAC By Period records are maintained in PJBUDSUM. The PlanNbr field is the distinguishing field between the two types of records. EAC By Period records are identified when a value exists in PlanNbr.
38 Page
Data Field Illustrations
EAC By Period (PA.BSM.01)
Pjptdsum.project Pjptdsum.pjt_entity Pjtddsum.acct Pjbudsum.fsyear_num
Pjbudsum.lupd_datetime
Pjbudsum.units_01
Pjbudsum.amount_01
Pjbudsum.units_09
Pjbudsum.amount_09
Pjbudsum.total_units Pjbudsum.total_amount
Note The name of each field is consistent except for the numbers always equal the period. For example, all of the fields for period 1 end with 01 and all fields for period 9 end with 09.
Note Both Budget By Period and EAC By Period records are maintained in PJBUDSUM. The PlanNbr field is the distinguishing field between the two types of records. EAC By Period records are identified when a value exists in PlanNbr.
Page 39
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Employee and Resource Maintenance (PA.EMP.00) Pjemploy.employee
Mgr1.name
Pjemploy.emp_status
Pjemploy.emp_type_cd
Pjemploy.date_hired
Pjemploy.CpnyId
Pjemploy.gl_subacct
Subacct.descr
Pjemploy.em_id01
Pjemploy.em_id02 Pjemploy.emp_id03
Pjemploy.emp_id07
Cmpny.name
Pjemploy.date_terminated
Pjemploy.manager2
Pjemploy.manager1
Mgr2.name
Pjemploy.emp_name
Pjemploy.emp_id06
Pjemploy.stdday Pjemploy.stdweek
Pjemploy.subcontractor
Pjemploy. exp_approval_max
Pjemploy.user_id
Pjemploy.MSPType
Pjemploy.placeholder
Pjemploy.em_id25
Pjemploy.em_id24
Pjemploy.em_id23
Pjemploy.em_id22
Pjemploy.em_id22
40 Page
Data Field Illustrations
Employee and Resource Maintenance (PA.EMP.00) – Customization Manager
Pjemploy.emp_id08Pjemploy.emp_id04
Pjemploy.emp_id10Pjemploy.emp_id05
Pjemploy.emp_id09
Pjemploy.MSPInterface
Pjemploy.MSPData
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.
Page 41
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Project Employee Maintenance-Employees by Project (PA.PEM.00) Pjproj.project
Pjproj.project_desc
Pjproj.status_19
Pjprojem.employee
Pjemploy.emp_name
42 Page
Data Field Illustrations
Project Employee Maintenance (PA.EMP.00) – Customization Manager
Pjprojem.pv_id08
Pjprojem.pv_id02
Pjprojem.pv_id10
Pjprojem.pv_id05 Pjprojem.pv_id09
Pjprojem.pv_id01
Pjprojem.pv_id03
Pjprojem.pv_id04
Pjprojem.pv_id06
Pjprojem.pv_id07
Pjemploy.MSPInterface
Pjemploy.MSPResuid
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.
Page 43
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Project Employee Maintenance - Projects by Employee (PA.PEM.00)
Pjprojem.project
Pjproj.project_desc
Pjprojem.employee
Pjemploy.emp_name
44 Page
Data Field Illustrations
Project Employee Maintenance (PA.EMP.00) – Customization Manager
Pjprojem.pv_id08
Pjprojem.pv_id02
Pjprojem.pv_id10
Pjprojem.pv_id05 Pjprojem.pv_id09
Pjprojem.pv_id01
Pjprojem.pv_id03
Pjprojem.pv_id04
Pjprojem.pv_id06
Pjprojem.pv_id07
Pjemploy.MSPInterface
Pjemploy.MSPResuid
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.
Page 45
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Project Net Profit (PA.PNR.00) – Amounts
Pjproj.project Pjproj.project_desc Variable
Pjptdrol.acct
Pjactrol.amount_mtd
Calculated
Calculated
Pjptdrol.com_amount
Pjptdrol.eac_amount
Calculated
Pjptdrol.total_budget_amount
Calculated
Period.fiscalno Screendata.rollupprojects
Note The value displayed in Pjactrol.amount_mtd depends on the Period field. For example, when displaying information for 01-2000, the value maintained in Pjactrol.amount_01 for fiscal year (fsyear_num) 2000 will be shown. If displaying information for 12-2000, the value maintained in Pjactrol.amount_12 for fiscal year (fsyear_num) 2000 will be shown.
46 Page
Data Field Illustrations
Project Net Profit (PA.PNR.00) – Units
Pjproj.project
Pjproj.project_desc Variable
Pjptdrol.acct
Pjactrol.units_mtd
Calculated
Calculated
Pjptdrol.com_units Pjptdrol.eac_units
Calculated
Pjptdrol.total_budget_units
Calculated
Screendata.rollupprojects Period.fiscalno
Note The value displayed in Pjactrol.units_mtd depends on the Period field. For example, when displaying information for 01-2000, the value maintained in Pjactrol.units_01 for fiscal year (fsyear_num) 2000 will be shown. If displaying information for 12-2000, the value maintained in Pjactrol.units_12 for fiscal year (fsyear_num) 2000 will be shown.
Page 47
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Task Net Profit (PA.PND.00) - Amounts
Pjpent.project Pjproj.project_desc
Pjpent.pjt_entity
Pjpent.pjt_entity_desc
Pjactsum.acct Pjactsum.pjt_entity
Pjacct.acct_type
Pjactsum.amount_mtd
Calculated Pjptdsum.com_amount
Calculated
Pjptdsum.eac_amount
Calculated
Pjptdsum.total_budget_amount Calculated
Variable Variable Variable
Variable
Period.fiscalno
Pjpent.pjt_entity_desc
Note The name of Pjcomsum.amount_mtd and Pjactsum.amount_mtd is based on Period.fiscalno. For example, if 01-2000 is entered, the values for Pjcomsum.amount_01 and Pjactsum.amount_01 are displayed.
48 Page
Data Field Illustrations
Task Net Profit (PA.PND.00) - Units
Pjpent.project Pjproj.project_desc
Pjpent.pjt_entity
Pjpent.pjt_entity_desc
Pjactsum.acct
Pjactsum.pjt_entity
Pjacct.acct_type
Pjactsum.units_mtd
Pjptdsum.act_units
Pjptdsum.com_units
Calculated
Pjptdsum.eac_units
Calculated
Pjptdsum.total_budget_units Calculated
Variable
Variable Variable Variable
Period.fiscalno
Pjpent.pjt_entity_desc
Note The name of Pjcomsum.units_mtd and Pjactsum.units_mtd is based on Period.fiscalno. For example, if 01-2000 is entered, the values for Pjcomsum.units_01 and Pjactsum.units_01 are displayed.
Page 49
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Project Summary Inquiry (PA.PSI.00) - Amounts
Pjproj.project
Pjproj.project_desc
Pjpent.pjt_entity
Pjacct.acct
Pjpent.pjt_entity_desc
Calculated
Calculated
Calculated
Variable
Pjactsum.amount_mtd or Pjcomsum.amount_mtd
Pjbudsum.amount_mtd
Calculated
Calculated
Calculated
Pjptdsum.act_amount
Pjptdsum.com_amount
Pjptdsum.total_budget_amount
Variable
Variable
Fsyear.fiscalyr
Note The name of Pjactsum.amount_mtd, Pjcomsum.amount_mtd, Pjbudsum.amount_mtd is based on Fsyear.fiscalno and Period detail. For example, if 2000 is entered and Period is 01, the values for Pjactsum.amount_01, Pjcomsum.amount_01 and Pjbudsum.amount_01 are displayed.
50 Page
Data Field Illustrations
Project Summary Inquiry (PA.PSI.00) - Units
Pjproj.project
Pjproj.project_desc
Pjpent.pjt_entity
Pjacct.acct
Pjpent.pjt_entity_desc
Calculated
Calculated
Calculated
Variable
Pjactsum.units_mtd or Pjcomsum.units_mtd
Pjbudsum.units_mtd
Calculated
Calculated Calculated
Pjptdsum.act_units
Pjptdsum.com_units
Pjptdsum.total_budget_units
Variable
Variable
Fsyear.fiscalyr
Note The name of Pjactsum.amount_mtd, Pjcomsum.amount_mtd, Pjbudsum.amount_mtd is based on Fsyear.fiscalno and Period detail. For example, if 2000 is entered and Period is 01, the values for Pjactsum.amount_01, Pjcomsum.amount_01 and Pjbudsum.amount_01 are displayed.
Page 51
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Transaction Detail Inquiry (PA.TRD.00)
Pjtran.project
Pjtran.pjt_entity
Pjproj.project_desc Pjpent.pjt_entity_desc
Pjtran.acct
Pjacct.acct_desc
Pjtran.fiscalno
Pjtran.trans_date
Pjtran.amount
Pjtran.tr_id02
Pjtran.tr_comment
Pjtran.tr_id05
Pjtran.CpnyId
Empinfo.name
Pjtran.units Pjtran.vendor_num
Pjtran.tr_id04
Pjtran.tr_id08
Pjtran.batch_type
Pjtran.system_cd
Pjtran.tr_status
Pjtran.gl_subacct
Pjtranex.lotsernbr
Pjtran.pjt_entity Pjtranex.siteid Pjtran.alloc_flag
Pjtran.voucher_line
Pjtran.acct
Pjtran.batch_id
Pjtranex.whseloc
Pjtranex.invtid
Pjtran.gl_acct
Veninfo.name
Pjtran.tr_id01
Pjtran.tr_id03
Period.fiscalno
Variable
Invinfo.descr
Pjtran.curyratetype Pjtran.curyid Pjtran.curytranamt
Pjtran.voucher_num
52 Page
Data Field Illustrations
Transaction Detail Inquiry (PA.TRD.00) – Customization Manager
Pjtran.tr_id09
Pjtran.tr_id10
Pjtran.tr_id06 Pjtran.tr_id07
Pjtran.tr_id14
Pjtran.tr_id11
Pjtran.tr_id13
Pjtran.tr_id12
Pjtran.tr_id15
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.
Page 53
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Commitment Detail Inquiry (PA.CMD.00) Pjcomdet.pjt_entity
Pjcomdet.acct
Pjpent.pjt_entity_desc Pjacct.acct_desc
Pjcomdet.amount Pjcomdet.CpnyId
Pjcomdet.units
Pjcomdet.system_cd Pjcomdet.cd_id04
Pjcomdet.part_number
Inventory.descr
Pjcomdet.voucher_num
Pjcomdet.request_date
Pjcomdet.gl_subacct
Pjcomdet.batch_id
Pjcomdet.voucher_line
Pjcomdet.cd_id06
Pjcomdet.cd_id08 Pjcomdet.acct
Pjcomdet.vendor_num Calculated Pjcomdet.gl_acct
Vendor.name
Pjcomdet.promise_date
Pjcomdet.tr_comment
Pjcomdet.cd_id03
Pjcomdet.cd_id05
Pjcomdet.pjt_entity
Pjcomdet.cd_id01
Calculated
Pjproj.project_desc Pjcomdet.po_date
Pjcomdet.batch_type
Pjcomdet.project
Pjcomdet.purchase_order_num
54 Page
Data Field Illustrations
Commitment Detail Inquiry (PA.CMD.00) – Customization Manager
Pjcomdet.cd_id07
Pjcomdet.cd_id09
Pjcomdet.cd_id02
Pjcomdet.cd_id10
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.
Page 55
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Account Category Maintenance (PA.ACC.00)
Pjacct.acct Pjacct.acct_desc
Pjacct.acct_group_cd
Pjacct.acct_type
Pjcode.code_value_desc
Pjacct.sort_num
Pjacct.acct_status
Pjacct.ca_id03 Slstaxcat.descr
Pjacct.id1_sw
Pjacct.id2_sw
Pjacct.id3_sw
Pjacct.id4_sw
Pjacct.id5_sw
Pjacct.ca_id20
56 Page
Data Field Illustrations
Account Category Maintenance – ID Fields (PA.ACC.00
Pjacct.ca_id02
Page 57
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Account Category Maintenance (PA.ACC.00) – Customization Manager
Pjacct.ca_id05
Pjacct.ca_id06 Pjacct.ca_id07
Pjacct.ca_id08
Pjacct.ca_id09 Pjacct.ca_id10
Pjacct.ca_id03
Pjacct.ca_id04
Pjacct.ca_id02 Pjacct.ca_id01
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.
58 Page
Data Field Illustrations
Account Category Maintenance-GL Cross-Reference (PA.ACC.00)
Account.acct
Account.descr
Account.accttype
Page 59
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Code File Maintenance (PA.CFM.00)
Pjcontrl.control_code Pjcontrl.control_data Pjcontrl.control_desc
Pjcontrl.control_data
Pjcode.code_value
Pjcode.code_value_desc
Pjcode.data1
Pjcode.data2
Pjcode.data3
Pjcode.data4
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.
60 Page
Data Field Illustrations
Equipment/Resource Maintenance (PA.EQU.00)
Pjequip.equip_id
Pjequip.equip_desc Pjequip.status Pjcode.code_value_desc
Pjequip.equip_type
Pjequip.CpnyId Cmpny.name
Pjequip.gl_subacct
Subacct.descr
Pjequip.project_costbasis
Pjproj.project_desc
Pjequip.er_id01 Pjequip.er_id05 Pjequip.er_id05
Page 61
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Equipment/Resource Maintenance (PA.EQU.00) – Customization Manager
Pjequip.er_id06
Pjequip.er_id08
Pjequip.er_id02
Pjequip.er_id09
Pjequip.er_id10
Pjequip.er_id03
Pjequip.er_id05
Pjequip.er_id04
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.
62 Page
Data Field Illustrations
Equipment/Resource Maintenance-Additional Info (PA.EQU.00)
Pjequip.eq_id01 Pjequip.eq_id02
Pjequip.eq_id03
Pjequip.eq_id05
Page 63
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Equipment/Resource Maintenance (PA.EQU.00) – Customization Manager
Pjequip.eq_id04 Pjequip.eq_id13
Pjequip.eq_id06
Pjequip.eq_id07 Pjequip.eq_id15
Pjequip.eq_id14
Pjequip.eq_id09
Pjequip.eq_id08 Pjequip.eq_id16
Pjequip.eq_id17
Pjequip.eq_id18
Pjequip.eq_id20
Pjequip.eq_id19
Pjequip.eq_id10
Pjequip.eq_id12
Pjequip.eq_id11
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.
64 Page
Data Field Illustrations
Equipment Rate Maintenance (PA.ERM.00)
Pjequip.equip_id Pjequip.equip_desc
Pjeqrate.project
Pjproj.project_desc
Pjeqrate.effect_date
Pjeqrate.unit_of_measure
Pjeqrate.rate1
Pjeqrate.rate2
Pjeqrate.rate3
Page 65
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Equipment Rate Maintenance (PA.ERM.00) – Customization Manager
Pjeqrate.ec_id10
Pjeqrate.ec_id09
Pjeqrate.ec_id08
Pjeqrate.ec_id07
Pjeqrate.ec_id06
Pjeqrate.ec_id05
Pjeqrate.ec_id04
Pjeqrate.ec_id03
Pjeqrate.ec_id02
Pjeqrate.ec_id01
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.
66 Page
Data Field Illustrations
Fiscal Period Maintenance (PA.FPM.00)
Pjfiscal.fiscalno Pjfiscal.start_date
Pjfiscal.end_date
Pjfiscal.comment
Page 67
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Flexible Report Column Maintenance (PA.RPC.00)
Pjrepcol.report_code Pjrepcol.column.nbr
Pjrepcol.acct
Pjrepcol.gl_acct
Pjrepcol.desc1
68 Page
Data Field Illustrations
Message Text Maintenance (PA.MSG.00)
Pjtext.msg_num
Pjtext.category_cd
Pjcode.code_value_desc
Pjtext.flag1
Pjtext.msg_text
Page 69
Pjsite.terminalcode Pjsite.terminalname Pjsite.emailaddress
Pjsite.password Pjsite.type_site
cs™ SL – Project Controller Module Report Assistant for Microsoft Dynami
Site Maintenance (PA.SIT.00)
70 Page
R E P O R T I N F O R M AT I O N
What you will learn in this section: 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.
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
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.
72 Page
Report Information
Project Profile - Screen PA.010.00 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
Tasks Report - Screen PA.020.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa020 Pjpro Pjproj.project
Pjpent.pjt_entity 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 Contract Number Pjproj.contract Valid Contract Number
Page 73
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Budget Reports - Screen PA.030.00 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
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 Contract Number Pjproj.contract Valid Contract Number Account Category Pjptdsum.acct Valid Account Category
Account Category Maintenance – Screen PA.040.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa040 Pjacct Pjacct.acct
The following table shows fields typically used for Sort/Select parameters for 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
74 Page
Report Information
Employee Report – Screen PA.050.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa050 Pjemploy Pjemploy.emp_name
Pjemploy.employee The following table shows fields typically used for Sort/Select parameters for 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
Project Charges Summary/Detail – Screen PA.060.00 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 The following table shows fields typically used for Sort/Select parameters for 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
Page 75
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Transaction List By Batch – Screen PA.070.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa070 Pjtran Pjtran.fiscalno
Pjtran.system_cd Pjtran.batch_id Pjtran.detail_num
The following table shows fields typically used for Sort/Select parameters for 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
Account Category/GL Account XREF - Screen PA.080.00 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 The following table shows fields typically used for Sort/Select parameters for 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
76 Page
Report Information
Project Task Summary - Screen PA.100.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
The following table shows fields typically used for Sort/Select parameters for 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 Account Category Pjptdsum.acct Valid Account Category
Project AR Aging/Recap Report - Screen PA.110.00 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
Page 77
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
The following table shows fields typically used for Sort/Select parameters for 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 Customer Name Customer.name Valid Customer Name 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
Project Profitability Report - Screen PA.120.00 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
The following table shows fields typically used for Sort/Select parameters for 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 Employee Name Pjemploy.emp_name Valid Employee Name Customer ID Pjproj.customer Valid Customer ID Customer Name Customer.name Valid Customer Name Project ID Pjactsum.project Valid Project ID Task ID Pjactsum_pjt_entity Valid Task ID
78 Page
Report Information
Project Billing Analysis - Screen PA.130.00 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
The following table shows fields typically used for Sort/Select parameters for this report.
Sort/Select Item Field Name Format / Possible Values Subaccount Pjproj.gl_subacct Valid Subaccount Number Account Category Pjptdsum.acct Valid Account Category Project Manager Pjproj.manager1 Valid Employee ID Employee Name Pjemploy.emp_name Valid Employee Name Project ID Pjptdsum.project Valid Project ID Task ID Pjptdsum.pjt_entity Valid Task ID
Project Task Analysis - Screen PA.140.00 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
The following table shows fields typically used for Sort/Select parameters for this report.
Sort/Select Item Field Name Format / Possible Values Subaccount Pjproj.gl_subacct Valid Subaccount Number Account Category Pjptdsum.acct Valid Account Category Project Manager Pjproj.manager1 Valid Employee ID Employee Name Pjemploy.emp_name Valid Employee Name Project ID Pjptdsum.project Valid Project ID Task ID Pjptdsum.pjt_entity Valid Task ID
Page 79
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Project Transactions - Screen PA.150.00 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
The following table shows fields typically used for Sort/Select parameters for 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
Project Cost Analysis - Screen PA.160.00 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
The following table shows fields typically used for Sort/Select parameters for this report:
Sort/Select Item Field Name Format / Possible Values Project Manager Pjproj.manager1 Valid Employee ID Project ID Pjptdsum.project Valid Project ID Task ID Pjptdsum.pjt_entity Valid Task ID Account Category Pjptdsum.acct Valid Account Category Subaccount Pjproj.gl_subacct Valid Subaccount Number
80 Page
Report Information
Project List - Screen PA.170.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa170 Pjproj Pjproj.project
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 Contract Number Pjproj.contract Valid Contract Number Account Category Pjptdsum.acct Valid Account Category
Revenue & Billing Status Rpt – Screen PA.180.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa180 Pjptdrol Pjproj.gl_subacct
@managernameandnum @contracttypeandproject @acctsort
The following table shows fields typically used for Sort/Select parameters for this report:
Sort/Select Item Field Name Format / Possible Values Subaccount Pjproj.gl_subacct Valid Subaccount Number Account Category Pjptdrol.acct Valid Account Category Project Manager Pjproj.manager1 Valid Employee ID Contract Type Pjproj.contract_type CP, CPFF, CPIA, FP, FPCS,
FPE,FPTM, INTR, TM, TMR, UP Project ID Pjptdrol.project Valid Project ID
Page 81
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Billing Worksheet by Task/Project – Screen PA.190.00 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. 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 Task ID Pjactsum.pjt_entity Valid Task ID Account Category Pjactsum.acct Valid Account Category Project Manager Pjproj.manager1 Valid Employee ID Subaccount Pjproj.gl_subacct Valid Subaccount Number
82 Page
Report Information
Budget vs Actual Amounts/Units – Screen PA.200.00 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
The following table shows fields typically used for Sort/Select parameters for this report:
Sort/Select Item Field Name Format / Possible Values Project Manager Pjpjtmgr.emp_name Valid Employee ID Project ID Pjptdsum.project Valid Project ID Task ID Pjptdsum.pjt_entity Valid Task ID Account Category Pjptdsum.acct Valid Account Category Subaccount Pjproj.gl_subacct Valid Subaccount Number Customer ID Pjproj.customer Valid Customer ID
Units of Production Report - Screen PA.210.00 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
Page 83
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
The following table shows fields typically used for Sort/Select parameters for this report:
Sort/Select Item Field Name Format / Possible Values Project Manager Pjproj.manager1 Valid Employee ID Project ID Pjptdsum.project Valid Project ID Task ID Pjptdsum.pjt_entity Valid Task ID Account Category Pjptdsum.acct Valid Account Category Subaccount Pjproj.gl_subacct Valid Subaccount Number Customer ID Pjproj.customer Valid Customer ID
Transaction Transfer Messages Report - Screen PA.220.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa220 Pjcommun @moduleandbatch
The following table shows fields typically used for Sort/Select parameters for this report:
Sort/Select Item Field Name Format / Possible Values Message type Pjcommun.msg_type Valid Message type Module Pjcommun.source_function Valid Module
Week Ending List - Screen PA.910.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa910 Pjweek Pjweek.period_num
Pjweek.week_num Pjweek.we_date
The following table shows fields typically used for Sort/Select parameters for this report:
Sort/Select Item Field Name Format / Possible Values Period Pjweek.period_num 200009
84 Page
Report Information
Code File Report - Screen PA.810.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa810 Pjcode Pjcode.code_type
Pjcode.code_value The following table shows fields typically used for Sort/Select parameters for 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
Code Type Report - Screen PA.820.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa820 Pjcontrl Pjcontrl.control_code
The following table shows fields typically used for Sort/Select parameters for 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
ID Field Report - Screen PA.830.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa830 Pjcontrl @wtableid
Pjcontrl.control_code The following table shows fields typically used for Sort/Select parameters for 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 Code Description Pjcontrl.control_desc Valid Code Description
Page 85
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
Control Parameters List - Screen PA.840.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa840 Pjcontrl @controltypeandcode
The following table shows fields typically used for Sort/Select parameters for 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 Code Description Pjcontrl.control_desc Valid Code Description
Report Column Listing - Screen PA.850.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa850 Pjrepcol Pjrepcol.report_code
Pjrepcol.column_nbr Pjrepcol.acct Pjrepcol.gl_acct
The following table shows fields typically used for Sort/Select parameters for 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
Pjt GL Account Distribution - Screen PA.900.00 Report Formats Report Name Master Table Default Sort Fields Standard Pa900 Gltran @modbatnbr
@acctsub gltran.module gltran.batnbr gltran.acct gltran.sub
86 Page
Report Information
The following table shows fields typically used for Sort/Select parameters for 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
Page 87
I N D E X
Report Assistant for Microsoft Dynamics™ SL – Project Controller Module
No entries
90 Page