Report Assistant for Microsoft Dynamics SL Allocator Module

Transcription

1 Report Assistant for Microsoft Dynamics SL Allocator Module

2 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, addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, 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 (in the U.S. or Canada) or

3 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 Boolean 14 Sort Statements 15 Field 16 Sort Type 17 Sort Ascending 17 Page Break 17 Total Break 18 Possible Values Chart 21 Data Field Illustrations 23 Overview 24 Allocation Method Setup (PA.MET.00) 25 Allocation Method Setup (PA.MET.00) Customization Manager 27 Standard Rate Entry (PA.RAE.00) 28 Multi Level Rate Entry (AL.RAT.00) 30 Rate Type Definition (PA.RTM.00) 31 Rate Table Definition (AL.RTD.00) 32 Report Information 33 Overview 34 Allocation Methods Report - Screen PA Allocation Rates Report - Screen PA Allocation Methods XREF - Screen PA Rate Tables Listing - Screen PA Alloc. Proc./GL Posting Audit Screen PA Allocation Processor Messages - Screen PA Index 39

4

5 H O W T O U S E T H I S M A N U AL 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.

6 Report Assistant for Microsoft Dynamics SL Allocator Module Introduction Manual Sections 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 Allocator module. It may also be of use during creation or modification of reports in the Crystal Report writer. 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 Allocator module. For example, allocation method calculation type values, allocation basis 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 Allocator 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 Allocation Method Setup screen, the data entered in the Debit Company ID field is stored in the PjAlloc file, in a field named debit_cpnyid. The illustration with the Allocation Method Setup screen in this section includes a reference to the Debit Company ID field, noting the value for the field is stored in Pjalloc.debit_cpnyid. 2 Page

7 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 Allocator 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

8 Report Assistant for Microsoft Dynamics SL Allocator Module 4 Page

9 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.

10 Report Assistant for Microsoft Dynamics SL Allocator Module Overview Select Statements 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 rate table 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. 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 which 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

11 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 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

12 Report Assistant for Microsoft Dynamics SL Allocator 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 Rate Tables where rate table IDs begin with FP, the following statement could be used. Pjrate.rate_table_id Begins With FP 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 Rate Tables where the Rate Types are B through L, inclusive. Pjrate.rate_type_cd Between B,L And Note When using between, the report includes records matching the beginning and ending values entered (i.e., B and L 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 Allocation Methods that have CP in their ID. 8 Page

13 Sort and Select Statements pjalloc.alloc_method_cd Contains CP And Equal Use Equal for an exact match. In the following example, only data for Rate Table Bill will be included in the report. Pjrate.rate_table_id Equal Bill And Greater than Greater than is used to include records larger (higher) than the value entered. In the following example, only projects with a rate amount greater than $125 will be included in the report. (Also see Greater than or equal to below.) Pjrate.rate Greater than 125 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, rate amounts of $125 will be included in the report, along with rate amounts higher than $125. Pjrate.rate Greater than or equal to 125 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, rate IDs Bill, CP, and TM 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. Pjrate.rate_table_cd In Bill, CP, TM 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 rate tables for which no rate has been entered in the rate field. When using Is NULL, the Value field must be left blank. Pjrate.rate Is NULL And Page 9

14 Report Assistant for Microsoft Dynamics SL Allocator 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 rate tables for which a rate has been entered in the rate field. Pjrate.rate 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 Allocation Rate report will include rate amounts less than $200. Any rate amounts of $200 or more will not be included on the report. Pjrate.rate Less than 200 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, an Allocation Rate report will include rate amounts of $200 or less. Pjrate.rate Less than or equal to 200 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 Allocation Rates less than $200 or more than $1,000, the following statement would be used. Pjrate.rate Not between 200,1000 And Note When using Not Between, the report does not include records matching the beginning and ending values entered (i.e. Allocation tables with rate amounts of $200 or $1,000 will not be included in the report). 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 Allocations Method XFER (PA ), the following statement could be used. Note that any job with Environmental in the description will be excluded from the report. Pjproj.project_desc Not contains Environmental And 10 Page

15 Sort and Select Statements 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 start date is 1/1/00. Pjproj.start_date Not equal 1/1/00 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 start date is 1/1/00 or 12/30/00. Pjproj.start_date Not in 1/1/00,12/30/00 And Value The Value field is used to enter data that 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. 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. Page 11

16 Report Assistant for Microsoft Dynamics SL Allocator Module 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 Allocation Rates where the Rate Table begins with C (i.e. CP, CR, CE etc.) Pjrate.rate_type_cd Equal C? And A question mark (? ) is used when one character is being replaced. In the above example, Rate Tables with a Rate Table ID of COR 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 Rate Table IDs starting with C, regardless of the Rate Table ID length. Pjrate.rate_type_cd Equal C* And 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. Pjrate.effect_date Greater than 01/30/2001 And Pjrate.effect_date Less than 2/7/02 And Dashes and Other Special Characters Many fields in Microsoft Dynamics SL may contain dashes or other special characters which 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 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. 12 Page

17 Sort and Select Statements 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 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 in both fields, the report will include only transactions posted to If you then enter the following select statement in the Select tab, the report would be blank: Pjtran.fiscalno Equal 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. Pjtran.fiscalno Less than And Note that while fiscal periods are displayed in screens and reports as month and then year (i.e ), 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. Page 13

18 Report Assistant for Microsoft Dynamics SL Allocator Module 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 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 an Allocation Method with a Project Post of CO Pjalloc.alloc_method_cd Equal CP And Pjalloc.post_project Equal CO Or 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 even if the Allocation Method is not attached to the Post Project. Pjalloc.alloc_method_cd Equal CP And Pjalloc.post_project Equal CO Or 14 Page

19 Sort and Select Statements 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 an Allocation Methods XREF report showing Project ID CO123000, with a start date greater than 1/31/01, and a subaccount equal to CD Printing the Allocation Methods XREF report, using the following Select statements, would give you this information. Pjproj.project Equal CO And Pjproj.start_date Greater than 1/31/01 And Pjproj.gl_subacct Equal 01000CD00001 And 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. Page 15

20 Report Assistant for Microsoft Dynamics SL Allocator Module 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 Allocation Methods XREF report, Summary format, is designed to sort by Allocation Method number, Allocation Method and Project ID. If you want to sort the report by the Project Description instead of the Project ID, you would enter the following Sort statement. Field Sort Type Sort Ascending Page Break Total Break pjvpa430.alloc_method_num Group Field Checked Blank Checked pjvpa430.alloc_method_cd Group Field Checked Blank Checked pjvpa430.project_desc Group Field Checked Blank Checked FIGURE 1-6: SUMMARY ALLOCATION METHODS XREF REPORT WITH DEFAULT SORT 16 Page

21 Sort and Select Statements FIGURE 1-7: SUMMARY ALLOCATION METHODS XREF REPORT WITH SORT ON PROJECT DESCRIPTION HINT: Because the report s first sort is Allocation Method and second sort is Project ID, and you want to add the Project Description sort, entering the 1 st sort as the Allocation Method, 2 nd sort to be the Project Description, 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 Allocation Method per page. Page 17

22 Report Assistant for Microsoft Dynamics SL Allocator Module For example, let s say you want to print the Allocation Methods XREF report, and you want to sort by Allocation Method with a Page Break by Allocation Method. By entering the following Sort statement, Microsoft Dynamics SL would print one Allocation Method on the first page, the second Allocation Method on the next page, and so on. Figure 8 displays the Allocation Methods XREF with a Page Break by Allocation Method. Field Sort Type Sort Ascending Page Break Total Break pjvpa430.alloc_method_cd Group Field Checked Checked Checked FIGURE 1-8: ALLOCATION METHOD XREF WITH PAGE BREAK ON ALLOCATION METHOD 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 breaks included in the report. If the report is not written with a total break, the following message appears when you try to process a report with a Total Break. FIGURE 1-9: TOTAL BREAK MESSAGE 18 Page

23 Sort and Select Statements 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 1 st sort order. For example, the Allocation Methods XREF report currently prints documents in order by Allocation Method and then by Project ID. Figure 9 displays the standard Allocation Methods XREF report. By changing the sort to be first by Project Id, then by Project Description, and indicating a Total Break on both the Project Id and Project Description fields, the Allocation Methods XREF will now print as displayed in Figure 10. Field Sort Type Sort Ascending Page Break Total Break pjvpa430.project Group Checked Checked Checked pjvpa430.project_desc Group Checked Blank Checked 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: ALLOCATION METHODS XREF WITH DEFAULT SORT Page 19

24 Report Assistant for Microsoft Dynamics SL Allocator Module FIGURE 1-11: ALLOCATION METHODS XREF WITH SORT AND TOTAL BREAK ON PROJECT ID 20 Page

25 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 Date fields 01/05/2001 or 01/05/01 Period fields such as period-to-post, period-entered, etc. Fiscal Year fields 2001 Calculation Type Calculate & Hold CH Calculate & Post CP Subtotal & Hold SH Subtotal & Post SP Allocation Basis Amount Units Flat Amount A U F TABLE 1: ALLOCATOR POSSIBLE VALUES Page 21

26 Report Assistant for Microsoft Dynamics SL Allocator Module 22 Page

27 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 Allocator data entry and maintenance screen: their field names and the table and field where they are stored in the Microsoft Dynamics SL data files.

28 Report Assistant for Microsoft Dynamics SL Allocator Module Overview The information in this section contains a screen illustration of the data entry screens and most maintenance screens in the Allocator 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 data entry screens 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. 24 Page

29 Data Field Illustrations Allocation Method Setup (PA.MET.00) Page 25

30 Report Assistant for Microsoft Dynamics SL Allocator Module Pjcode.code_value Pjalloc.step_desc Pjalloc.end_acct Pjcode.code_value_desc Pjalloc.step_number Pjalloc.alloc_calc_type Pjalloc.begin_acct Pjalloc.begin_step Pjalloc.al_id10 Pjalloc.end_step Pjalloc.rate_type_cd Pjalloc.offset_project Pjalloc.offset_pjt_entity Pjalloc.offset_acct_cat Pjcode.data1 Pjalloc.debit_CpnyId Pjalloc.debit_gl_acct Pjalloc.debit_gl_subacct Pjalloc.credit_cpnyid Pjalloc.credit_gl_acct Pjalloc.credit_gl_subacct Pjalloc.emp_recap_sw Pjalloc.unit_post_sw Pjalloc.bill_post_sw Pjalloc.subacct_recap_sw Pjalloc.al_id05 Pjalloc.post_acct Pjalloc.post_pjt_entity Pjalloc.post_project Pjalloc.alloc_rate Pjalloc.alloc_basis 26 Page

31 Data Field Illustrations Allocation Method Setup (PA.MET.00) Customization Manager Pjalloc.al_id01 Pjalloc.al_id02 Pjalloc.al_id09 Pjalloc.al_id07 Pjalloc.al_id08 Pjalloc.al_id03 Pjalloc.al_id04 Pjalloc.al_id06 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 27

32 Report Assistant for Microsoft Dynamics SL Allocator Module Standard Rate Entry (PA.RAE.00) Note The table name of each field is consistent except for the numbers for each rate level in the PJRATE table. For example, all of the Exception Rates fields (Pjrate1) have a Rate_level field = 1. All of the Standard Rates fields (Pjrate2) have a Rate_level field = 2. The Default Rate fields (Pjrate0) have a Rate_level field = Page

33 Data Field Illustrations Pjcode.code_value_desc Pjcode.code_value_desc Pjrate0.effect_date Pjrate.rate_table_id Pjrate.rate_type_cd Pjrate0.rate Pjrate2.rate_key_value1 Pjrate2.effect_date Pjrtab.L1_rate_key1_cd Pjrate2.rate Pjrate1.rate_key_value1 Pjrate1.effect_date Pjrate1.rate Pjrate1.rate_key_value2 Page 29

34 Report Assistant for Microsoft Dynamics SL Allocator Module Multi Level Rate Entry (AL.RAT.00) Pjrate.rate_type_cd Pjrate.rate_table_id Pjcode.code_value_desc Pjcode.code_value_desc Pjrate.rate_level Pjrate.curyid Curncy.descr Pjrate.effect_date Pjrate.rate Pjrate.rate_key_value1 Pjrate.rate_key_value3 Pjrate.rate_key_value2 30 Page

35 Data Field Illustrations Rate Type Definition (PA.RTM.00) Pjcode.code_value Pjcode.code_value_desc Pjcode.data1 Page 31

36 Report Assistant for Microsoft Dynamics SL Allocator Module Rate Table Definition (AL.RTD.00) Pjrate.rate_table_id pjrate.rate_type_cd Pjrate.curyid Pjcontrl.control_desc Pjrtab.L1.rate_key1_cd Pjcode.code_value_desc Pjcode.code_value_desc Curncy.descr Pjrtab.L1.rate_key2_cd Pjcontrl.control_desc Pjrtab.L1.rate_key3_cd Pjcontrl.control_desc Pjcontrl.control_desc Pjrtab.L9.rate_key1_cd Pjcontrl.control_desc Pjrtab.L9.rate_key2_cd Pjcontrl.control_desc Pjrtab.L9.rate_key3_cd Note The name of each field is consistent except for the numbers for each level. For example, all of the fields for level 1 begin with L1 and all fields for level 9 begin with L9. 32 Page

37 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 Allocator module: master table, sort order, report name as stored in Crystal, sort/select field examples.

38 Report Assistant for Microsoft Dynamics SL Allocator Module Overview The information in this section lists each report in the Allocator 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. 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 the sections on Date Values, Dashes and Other Special Characters, and Fiscal Periods. 34 Page

39 Report Information Allocation Methods Report - Screen PA Report Formats Report Name Master Table Default Sort Fields Allocation Methods Report PA410 Pjalloc Pjalloc.alloc_method_cd Pjalloc.step_number The following table shows fields typically used for Sort/Select parameters for this report: Sort/Select Item Field Name Format / Possible Values Allocation Method Pjalloc.alloc_method_cd Valid Allocation Method Step Number Pjalloc.step_number Valid Step Number Calculation Type Pjalloc.calc_type CH Calculate & Hold CP Calculate & Post SH Subtotal & Hold SP Subtotal & Post Rate Type Pjalloc.rate_type_cd Valid Rate Type Allocation Rates Report - Screen PA Report Formats Report Name Master Table Default Sort Fields Allocation Rates Report PA420 Pjrate Pjrate.rate_table_id Pjrate.rate_type_cd Pjrate.rate_level Pjrate.rate_key_value1 Pjrate.rate_key_value2 Pjrate.rate_key_value3 Pjrate.effect_date The following table shows fields typically used for Sort/Select parameters for this report: Sort/Select Item Field Name Format / Possible Values Rate Table Pjrate.rate_table_id Valid Rate Table Rate Type Pjrate.rate_type_cd Valid Rate Type Rate Level Pjrate.rate_level 1, 2, 3, 4, 5, 6, 7, 8, 9 Rate Key Value 1 Pjrate.rate_key_value1 Valid Key 1 Value Rate Key Value 2 Pjrate.rate_key_value2 Valid Key 2 Value Rate Key Value 3 Pjrate.rate_key_value3 Valid Key 3 Value Effective Date Pjrate.effect_date 01/01/2000 or 01/01/00 Page 35

40 Report Assistant for Microsoft Dynamics SL Allocator Module Allocation Methods XREF - Screen PA Report Formats Report Name Master Table Default Sort Fields Allocation Methods XREF PA430 Pjproj Pjproj.alloc_method_cd Pjproj.project The following table shows fields typically used for Sort/Select parameters for this report: Sort/Select Item Field Name Format / Possible Values Allocation Method Pjproj.alloc_method_cd Valid Allocation Method Project ID Pjproj.project Valid Project ID Customer ID Pjproj.customer Valid Customer ID Rate Tables Listing - Screen PA Report Formats Report Name Master Table Default Sort Fields Rate Tables Listing PA440 Pjrtab Pjrtab.rate_table_id Pjrtab.rate_type_cd The following table shows fields typically used for Sort/Select parameters for this report: Sort/Select Item Field Name Format / Possible Values Rate Table ID Pjrtab.rate_table_id Valid Rate Table ID Rate Type Pjrtab.rate_type_cd Valid Rate Type 36 Page

41 Alloc. Proc./GL Posting Audit Screen PA Report Information Report Formats Report Name Master Table Default Sort Fields Allocation Processor Audit PA450a Pjallsrt Pjallsrt.alloc_batch Ppallsrt.project Pjallsrt.acct Pjallsrt.pjt_entity Pjallsrt.src_project Pjallsrt.src_acct_cat Pjallsrt.src_labor_class Pjallsrt.employee Pjallsrt.src_trans_date Allocation GL Posting Audit PA450b Pjallgl Pjallgl.alloc_batch Pjallgl.source_project Pjallgl.source_pjt_entity Pjallgl.project Pjallgl.pjt_entity Pjallgl.gl_acct Pjallgl.gl_subacct The following table shows fields typically used for Sort/Select parameters for this report: Sort/Select Item Field Name Format / Possible Values GL Batch Number Alloc_batch Valid Allocation Batch Number Allocation Processor Messages - Screen PA Report Formats Report Name Master Table Default Sort Fields Allocation Processor PA460 Messages NOTE: symbol indicates a formula field created in the Crystal Report Writer. You cannot use formula fields in Sort or Select statements. The following table shows fields typically used for Sort/Select parameters for this report: Sort/Select Item Field Name Format / Possible Values Created Date and Time Crtd_datetime Valid Allocation Batch Number Page 37

42

43 I N D E X

44 Report Assistant for Microsoft Dynamics SL Allocator Module No entries 40 Page