API PRO - Crystal Reports Manual · 1 1 About the manual The purpose of this manual is to give a description of the Crystal Reports template printouts available in API PRO and to

API PRO - Crystal Reports

Manual

API Maintenance Systems A/S

Roskildevej 342 B, st.

DK-2630 Taastrup

Denmark

Tel. +45 4348 9900

Fax. +45 4348 9901

Web: www.apipro.com

Manual Revision: 12th

February 2014

Product Version: API PRO 8

Language: English

Contents

1 ABOUT THE MANUAL ................................................................................................................................................... 1

2 INTRODUCTION ............................................................................................................................................................. 2

2.1 WHEN API PRO DATABASE CHANGES .............................................................................................................................. 3 2.2 WHEN CHANGING THE XML FILE ..................................................................................................................................... 3

2.2.1 When adding new tables ......................................................................................................................................... 3 2.2.2 When removing tables ............................................................................................................................................ 3 2.2.3 Changing table names ............................................................................................................................................ 3 2.2.4 Adding fields to an existing table ............................................................................................................................ 3 2.2.5 Changing field name in an existing table ................................................................................................................ 4 2.2.6 Logical fields in XML-based reports ....................................................................................................................... 5

3 INSTALLATION .............................................................................................................................................................. 6

4 GENERAL LAYOUT ....................................................................................................................................................... 9

4.1 SECTIONS ........................................................................................................................................................................ 9 4.1.1 Sections expert ....................................................................................................................................................... 9

4.2 SUB REPORTS .................................................................................................................................................................. 9 4.3 INSERTING PICTURES...................................................................................................................................................... 10 4.4 STANDARD TEMPLATE CRSTD5COL.RPT .......................................................................................................................... 10

4.4.1 Table structure .................................................................................................................................................... 10 4.4.2 Sub reports .......................................................................................................................................................... 10

5 FUNCTIONALITY ......................................................................................................................................................... 12

5.1 LABEL PRINTS ............................................................................................................................................................... 12 5.1.1 Add the barcode ................................................................................................................................................... 12

5.2 CHANGE THE LOGOTYPE IN HEADER ............................................................................................................................... 13 5.3 Z TABLES ...................................................................................................................................................................... 13 5.4 CHANGE LOG ................................................................................................................................................................. 13 5.5 LOCK POSITION AND SIZE ............................................................................................................................................... 14 5.6 REPORT‟S EXPORT ......................................................................................................................................................... 16

6 CRYSTAL REPORTS TEMPLATE PRINTOUTS ....................................................................................................... 18

6.1 BARCODE ACCOUNT ...................................................................................................................................................... 18 6.1.1 Table structure .................................................................................................................................................... 19

6.2 BARCODE MAINTENANCE OBJ........................................................................................................................................ 19 6.2.1 Table structure .................................................................................................................................................... 19

6.3 BARCODE SPARE/PURCH./DEL. ...................................................................................................................................... 19 6.3.1 Table structure .................................................................................................................................................... 20 6.3.2 Special fields ....................................................................................................................................................... 21 6.3.3 Sub reports .......................................................................................................................................................... 21

6.4 BARCODE STOCK CONTROL ........................................................................................................................................... 21 6.4.1 Table structure .................................................................................................................................................... 22

6.5 BARCODE STOCK ........................................................................................................................................................... 22 6.5.1 Table structure .................................................................................................................................................... 23

6.6 BARCODE TOOL............................................................................................................................................................. 23 6.6.1 Table structure .................................................................................................................................................... 24

6.7 BARCODE USER ............................................................................................................................................................. 24 6.7.1 Table structure .................................................................................................................................................... 25

6.8 BARCODE WORK SUPPLIER ............................................................................................................................................ 25 6.8.1 Table structure .................................................................................................................................................... 26

6.9 BUDGET REPORT FOR PROJECT....................................................................................................................................... 26 6.9.1 Table structure .................................................................................................................................................... 27 6.9.2 Special fields ....................................................................................................................................................... 27 6.9.3 Sub reports .......................................................................................................................................................... 28

6.10 CALIBRATION ........................................................................................................................................................... 29 6.10.1 Table structure ................................................................................................................................................ 29 6.10.2 Sub reports ...................................................................................................................................................... 30

6.11 GOODS RECEIPT NOTE .............................................................................................................................................. 30

6.11.1 Table structure ................................................................................................................................................ 31 6.11.2 Sub reports ...................................................................................................................................................... 31 6.11.3 Special fields ................................................................................................................................................... 31

6.12 WORK HISTORY JOBCARD ......................................................................................................................................... 31 6.12.1 Table structure ................................................................................................................................................ 32 6.12.2 Sub reports ...................................................................................................................................................... 33 6.12.3 Special fields ................................................................................................................................................... 33

6.13 INSPECTION REGISTRATION ....................................................................................................................................... 36 6.13.1 Table structure ................................................................................................................................................ 36 6.13.2 Sub reports ...................................................................................................................................................... 37

6.14 INSPECTION LIST ....................................................................................................................................................... 38 6.14.1 Table structure ................................................................................................................................................ 38 6.14.2 Sub reports ...................................................................................................................................................... 39

6.15 PURCHASE REQUEST HEADER.................................................................................................................................... 40 6.15.1 Table structure ................................................................................................................................................ 40 6.15.2 Sub reports ...................................................................................................................................................... 40

6.16 PURCHASE REQUEST LINE ......................................................................................................................................... 41 6.16.1 Table structure ................................................................................................................................................ 41 6.16.2 Sub reports ...................................................................................................................................................... 41

6.17 SERVICE INVOICE ...................................................................................................................................................... 42 6.17.1 Table structure ................................................................................................................................................ 42 6.17.2 Sub reports ...................................................................................................................................................... 42

6.18 INVOICE.................................................................................................................................................................... 43 6.18.1 Table structure ................................................................................................................................................ 43 6.18.2 Sub reports ...................................................................................................................................................... 43

6.19 LOG CHANGES DATA SHEET ...................................................................................................................................... 45 6.19.1 Table structure ................................................................................................................................................ 45

6.20 WO ACCUM. LIST ..................................................................................................................................................... 46 6.20.1 Table structure ................................................................................................................................................ 46

6.21 WO ACCUM. DETAILED LIST ..................................................................................................................................... 46 6.21.1 Table structure ................................................................................................................................................ 47

6.22 MAINT. OBJ. DATA SHEET ......................................................................................................................................... 47 6.22.1 Table structure ................................................................................................................................................ 48 6.22.2 Sub reports ...................................................................................................................................................... 48

6.23 PROJECT TREE LIST ................................................................................................................................................... 49 6.23.1 Table structure ................................................................................................................................................ 49 6.23.2 Table structure ................................................................................................................................................ 50 6.23.3 Sub reports ...................................................................................................................................................... 50

6.24 PURCHASE ENQUIRY ................................................................................................................................................. 51 6.24.1 Table structure ................................................................................................................................................ 51

6.25 PURCHASE ORDER .................................................................................................................................................... 52 6.25.1 Table structure ................................................................................................................................................ 52 6.25.2 Sub reports ...................................................................................................................................................... 53 6.25.3 Special fields ................................................................................................................................................... 53

6.26 PURCHASE ORDER REMINDER ................................................................................................................................... 54 6.26.1 Table structure ................................................................................................................................................ 55 6.26.2 Sub reports ...................................................................................................................................................... 55

6.27 SPARE PART DATA SHEET ......................................................................................................................................... 56 6.27.1 Table structure ................................................................................................................................................ 56 6.27.2 Sub reports ...................................................................................................................................................... 57

6.28 WORK ORDER JOB CARD ........................................................................................................................................... 58 6.28.1 Table structure ................................................................................................................................................ 58 6.28.2 Sub reports ...................................................................................................................................................... 59 6.28.3 Special fields ................................................................................................................................................... 60

6.29 PICKING LIST ............................................................................................................................................................ 62 6.29.1 Table structure ................................................................................................................................................ 62 6.29.2 Sub reports ...................................................................................................................................................... 63

6.30 PICKING LIST REMOVAL NOTE .................................................................................................................................. 64 6.30.1 Table structure ................................................................................................................................................ 64

6.31 FINANCIAL TRANSACTION REPORT ............................................................................................................................. 64 6.31.1 Table structure ................................................................................................................................................ 65

6.31.2 Sub reports ...................................................................................................................................................... 65 6.31.3 Special fields ................................................................................................................................................... 66

6.32 WORK HISTORY, CR DESIGN ...................................................................................................................................... 67 6.32.1 Table structure ................................................................................................................................................ 67 6.32.2 Sub reports ...................................................................................................................................................... 68 6.32.3 Special fields ................................................................................................................................................... 68

6.33 NOTIFICATION CARD ................................................................................................................................................. 69 6.33.1 Table structure ................................................................................................................................................ 69 6.33.2 Sub reports ...................................................................................................................................................... 70

6.34 NOTIFICATION LIST ................................................................................................................................................... 70 6.34.1 Table structure ................................................................................................................................................ 71

6.35 SHIFT HISTORY REPORT ............................................................................................................................................. 71 6.35.1 Table structure ................................................................................................................................................ 72

6.36 STOCK VALUE LIST ................................................................................................................................................... 72 6.36.1 Table structure ................................................................................................................................................ 73 6.36.2 Sub reports ...................................................................................................................................................... 73

6.37 ABC ANALYSIS ........................................................................................................................................................ 73 6.37.1 Table structure ................................................................................................................................................ 74

6.38 STOCK CONTROL DATA ............................................................................................................................................. 74 6.38.1 Table structure ................................................................................................................................................ 74

6.39 STOCK INVENTORY TURNOVER.................................................................................................................................. 75 6.39.1 Table structure ................................................................................................................................................ 75 6.39.2 Special fields ................................................................................................................................................... 75

6.40 NON-MOVING STOCK ITEMS ...................................................................................................................................... 76 6.40.1 Table structure ................................................................................................................................................ 76 6.40.2 Special fields ................................................................................................................................................... 76

6.41 SPARE PART LIST ...................................................................................................................................................... 77 6.41.1 Table structure ................................................................................................................................................ 77

6.42 STOCK REPORT, STOCK BELOW MINIMUM ................................................................................................................. 78 6.42.1 Table structure ................................................................................................................................................ 78 6.42.2 Special fields ................................................................................................................................................... 78

6.43 PRICE LIST ................................................................................................................................................................ 79 6.43.1 Table structure ................................................................................................................................................ 79 6.43.2 Special fields ................................................................................................................................................... 80

6.44 STOCK TAKING, RESULT LIST .................................................................................................................................... 80 6.44.1 Table structure ................................................................................................................................................ 80

6.45 STOCK TAKING LIST .................................................................................................................................................. 81 6.45.1 Table structure ................................................................................................................................................ 81 6.45.2 Special fields ................................................................................................................................................... 81

6.46 RESERVATION SURVEY ............................................................................................................................................. 81 6.46.1 Table structure ................................................................................................................................................ 82

6.47 STOCK TRANSACTION REPORT .................................................................................................................................. 82 6.47.1 Table structure ................................................................................................................................................ 82 6.47.2 Special fields ................................................................................................................................................... 83

6.48 PROJECT REPORT ...................................................................................................................................................... 83 6.48.1 Table structure ................................................................................................................................................ 84

6.49 PROJECT REPORT, PURCHASES................................................................................................................................... 84 6.49.1 Table structure ................................................................................................................................................ 84 6.49.2 Sub reports ...................................................................................................................................................... 85

6.50 PROJECT REPORT, CRITICAL CONDITIONS .................................................................................................................. 85 6.50.1 Table structure ................................................................................................................................................ 85

6.51 PLANNED/USED COST REPORT, ACCOUNT .................................................................................................................. 85 6.51.1 Table structure ................................................................................................................................................ 86

6.52 PLANNED/USED COST REPORT, PROJECT .................................................................................................................... 86 6.52.1 Table structure ................................................................................................................................................ 86

6.53 PLANNED/USED COST REPORT, WORK ORDER ............................................................................................................ 87 6.53.1 Table structure ................................................................................................................................................ 87

6.54 MTBF/MTTR REPORT.............................................................................................................................................. 87 6.54.1 Table structure ................................................................................................................................................ 88 6.54.2 Sub reports ...................................................................................................................................................... 88

6.55 STATISTICS – TOP LISTS ............................................................................................................................................ 88

6.55.1 Table structure ................................................................................................................................................ 88 6.56 WORK SUPPLIER HOUR REPORT ................................................................................................................................ 88

6.56.1 Table structure ................................................................................................................................................ 89 6.57 NOT DELIVERED ORDERS .......................................................................................................................................... 89

6.57.1 Table structure ................................................................................................................................................ 89 6.57.2 Sub reports ...................................................................................................................................................... 90

6.58 NOT INVOICED ORDERS............................................................................................................................................. 90 6.58.1 Table structure ................................................................................................................................................ 90 6.58.2 Sub reports ...................................................................................................................................................... 91

6.59 AGREEMENT REPORT ................................................................................................................................................ 91 6.59.1 Table structure ................................................................................................................................................ 91

6.60 PURCHASE ORDER LIST ............................................................................................................................................. 92 6.60.1 Table structure ................................................................................................................................................ 92 6.60.2 Sub reports ...................................................................................................................................................... 93

6.61 PURCHASE INVOICE SURVEY ..................................................................................................................................... 93 6.61.1 Table structure ................................................................................................................................................ 93

6.62 PURCHASE ORDER STATUS LIST ................................................................................................................................ 93 6.62.1 Table structure ................................................................................................................................................ 94 6.62.2 Sub reports ...................................................................................................................................................... 94

6.63 SUPPLIER PERFORMANCE .......................................................................................................................................... 94 6.63.1 Table structure ................................................................................................................................................ 95

6.64 PURCHASE & REMOVAL ANALYSIS ............................................................................................................................ 95 6.64.1 Table structure ................................................................................................................................................ 96 6.64.2 Sub reports ...................................................................................................................................................... 96

6.65 PURCHASE ACCUM, SUPPLIER REPORT ....................................................................................................................... 96 6.65.1 Table structure ................................................................................................................................................ 96

6.66 PURCHASE ACCUM, SUPPLIER LINES REPORT ............................................................................................................. 96 6.66.1 Table structure ................................................................................................................................................ 97

6.67 BALANCE REPORT..................................................................................................................................................... 97 6.67.1 Table structure ................................................................................................................................................ 97

6.68 BUDGET REPORT ....................................................................................................................................................... 97 6.68.1 Table structure ................................................................................................................................................ 98

6.69 WORK ORDER AVAILABILITY REPORT ....................................................................................................................... 98 6.69.1 Table structure ................................................................................................................................................ 99

6.70 USER PERMISSION REPORT ........................................................................................................................................ 99 6.70.1 Table structure ................................................................................................................................................ 99

6.71 JOBMONITOR LIST ................................................................................................................................................... 100 6.71.1 Table structure .............................................................................................................................................. 100

6.72 WORK SUPPLIER CALENDAR FOR WORK ORDER ...................................................................................................... 100 6.72.1 Table structure .............................................................................................................................................. 100

6.73 CALIBRATION HISTORY ........................................................................................................................................... 101 6.73.1 Table structure .............................................................................................................................................. 101

6.74 PLANT STRUCTURE ................................................................................................................................................. 101 6.74.1 Table structure .............................................................................................................................................. 102

6.75 WORK ORDER SURVEY ........................................................................................................................................... 102 6.75.1 Table structure .............................................................................................................................................. 103

6.76 PM WORK ORDER YEAR PLAN ................................................................................................................................ 103 6.76.1 Table structure .............................................................................................................................................. 103

6.77 INSPECTION BARCODE ............................................................................................................................................. 104 6.77.1 Table structure .............................................................................................................................................. 104

6.78 WORK INSTRUCTION ............................................................................................................................................... 104 6.78.1 Table structure .............................................................................................................................................. 105

7 ODBC-BASED CRYSTAL REPORTS ......................................................................................................................... 105

7.1 REPORT PROPERTIES .................................................................................................................................................... 105 7.2 PORTABILITY............................................................................................................................................................... 106 7.3 LOGICAL FIELDS IN ODBC-BASED REPORTS.................................................................................................................. 107

1

1 About the manual

The purpose of this manual is to give a description of the Crystal Reports template printouts available in API PRO and to provide recommendations on the creation of ODBC-based Crystal Reports which are supposed to be viewed in API PRO. This will make it

easier for you to update or change the printouts to fit your needs.

The manual starts with a short introduction and thereafter the chapter Installation comes where information about how to make the

Crystal Reports print outs available is presented.

In Chapter 4 the general layout of an .rpt file is presented.

In Chapter 5 certain functionality is described.

In Chapter 6 all report templates are presented. They are shown in an alphabetical order, with the name of the report as a starting

point. For each report you will learn:

- The name of the report

- The name of the related .rpt file

- The name of the XML file (the data source)

- Where the report is called from

- What an example report looks like

- What tables you can use in the report in question and the table links

- Sub reports available in the report

- Special fields used in the report

API PRO 2 Crystal Reports manual

2 Introduction

The Crystal Reports printouts described in this manual all use an XML file as data source. This XML file is created automatically when running the report from within API PRO. The XML files can be found in your directory for temporary files.

All Crystal Reports template printouts can be found at /WORK/CRPRINT/TEMPLATE. The reports used when running API PRO

are the ones that are saved directly in the CRPRINT directory.

The reports are available as .rpt files. By editing these files you can design your own customized reports.

View the image below to see how the report – in the example below the Job Card - is created when the print option is selected

somewhere in API PRO.

Work order API000528 is displayed in the „Planned work order‟ program. The <Job card> button is pressed and the „Select

interface‟ window is shown. The Crystal Reports interface is chosen.

A “temporary” XML file with information about the API000528 work order is created. The XML file is saved in your directory for

temporary files and the reason why it is called “temporary” is that the next time a job card is printed this XML file will be over

3

written by the new XML file.

The Crystal Reports runtime starts up. The report – in our example the Job Card – gets its design from the Crystal Reports .rpt file

– crjobcar.rpt which can be found in the CRPRINT directory in the WORK directory - and its data from the newly created XML

file.

The report is displayed in the Crystal Report runtime Viewer.

ODBC-based Crystal Reports created by users, can be accessed in API PRO via Crystal Reports program (please, see the

Users' guide for further details about Crystal Reports API PRO window).

2.1 When API PRO database changes

When a new version or a service pack of API PRO is released and it includes a change of the database structure, the

standard Crystal Reports templates are delivered updated. In order to update customized templates, follow the

instructions below.

1) Switch off the parameter 'Auto-delete temp data file' in the Basic configuration.

2) Delete all XML files created for the report in the temporary directory. 3) Run the report (ignore all error messages given by Crystal Reports), which will create an XML file with the proper

structure.

4) Open the report template in the Crystal Reports developer and choose Database - Verify Database. You will be asked, which file to use for the verification - point the XML file just created in the temporary directory.

5) Confirm the update of all changed tables when asked and map the fields when asked; save the report template.

2.2 When changing the XML file

2.2.1 When adding new tables

When a new table is added to the XML file the table has to be added to the report, from the Database Expert. Note that Crystal

Reports sometimes suggests its own table linking. When this happens the links have to be updated after the new table is added.

2.2.2 When removing tables

When a table is removed from an XML file an error message will show when running the report, saying “Table can not be found”.

The report can not be displayed. When opening the report in Crystal Reports the following message is displayed:

Click „Yes‟ to remove it from the report. If the report contains fields from the table then these will be removed from the report.

2.2.3 Changing table names

It gives a problem when the existing XML contains tables which are not available in the new XML. You have to remove the old table and then add the new. The problem with this is that there is no mapping so all fields that are used from the old table will

disappear from the report and you have to add them all again.

2.2.4 Adding fields to an existing table

When running the report from within Crystal Reports you will get a message for each updated field. For each added field you get:


2.2.5 Changing field name in an existing table

If a field name has changed you have to map the new named field with the old field.

The Unmapped fields list (upper left) shows the unmapped report fields for which the program detects a change in the active

database. The Unmapped fields list (upper right) shows the unmapped database fields for which the program detects a change.

When the Match Type check box is selected, the Unmapped fields list (upper right) shows only the names of unmapped database

fields that are of the same type as the field selected in the Unmapped fields list (upper left). When the Match Type check box is not

selected, the Unmapped fields list (upper right) shows all unmapped database fields, regardless of the field type.

Click <Map> to map the report field selected in the Unmapped fields list (upper left) to the database field selected in the

Unmapped fields list (upper right).The Mapped fields list (lower left) displays the names of mapped report fields. When you map

report fields, those fields appear in this list. The Mapped fields list (lower right) shows the mapped database fields. When you map

5

database fields, those fields appear in this list.

2.2.6 Logical fields in XML-based reports

Logical fields represented in the 'Yes/No' format are shown translated to Windows language, not to the current language of API

PRO. In some languages, the translated 'Yes' is shown for False and the translated 'No' is shown for True (the problem is known for

Polish, there might be other languages where the values formatted as „Yes/No‟ change to opposite).

To solve this, the data generation program adds a character copy of each logical field to a report database with the values 'Yes' or

'No' translated to the API PRO current language depending on the value of the original logical field. E.g., the character field

work_order.fixed_interval_tr is created for the logical field work_order.fixed_interval and is assigned the translated 'Yes'

if work_order.fixed_interval = true and the translated 'No' if work_order.fixed_interval = false. The field

z_work_order.z_fixed_interval_tr is also created and has the same value as z_work_order.z_fixed_interval. The translated texts 'Yes' and 'No' are included to the table Z_TEXTS as well to be used in formulae when needed.


3 Installation

All the Crystal Reports templates have an interface record. They are available via the Special Interfaces. The interfaces are called:

Interface key Interface name

CR V7 Barcode Account Barcode Account

CR V7 Barcode MaintObj Barcode Maintenance Obj.

CR V7 Barcode SP-PO-DEL Barcode Spare/Purch./Del.

CR V7 Barcode StockCont. Barcode Stock Control

CR V7 Barcode Stock Barcode Stock

CR V7 Barcode Tool Barcode Tool

CR V7 Barcode User Barcode User

CR V7 Barcode WorkSupp Barcode Work Supplier

CR V7 Budget Report Budget report

CR V7 Calibration Calibration

CR V7 Goods Receipt Note Goods Receipt Note

CR V7 History Jobcard Work History jobcard

CR V7 Inspection Reg Inspection Registration

CR V7 Inspection Inspection

CR V7 IntRequestHead Purchase Request header

CR V7 IntRequestLine Purchase Request Line

CR V7 Customer Invoice Service Invoice

CR V7 Invoice Invoice

CR V7 Log Changes Card Log Changes Data Sheet

CR V7 Jobaccumulation WO accum. list

CR V7 Jobacc. Detail WO accum. detailed list

CR V7 MaintObj Card Maint.Obj. Data Sheet

CR V7 Project Tree Project tree list

CR V7 Purchase Confirm Purchase Confirmation

CR V7 Purchase Enquiry Purchase Enquiry

CR V7 Purchase Order Purchase order

CR V7 Purchase Reminder Purchase Order Reminder

CR V7 Spare part Card Spare part Data Sheet

CR V7 Work Order Jobcard Work Order Jobcard

CR V7 picklist Picking list

CR V7 Pick removal note Picking list removal note

CR V7 Financial report Financial transaction report

CR V7 Work History Work history, CR design

CR V7 Stock report 1 Stock value list

CR V7 Stock report 2 ABC Analysis

CR V7 Stock report 3 Stock control data

7

CR V7 Stock report 4 Stock inventory turnover

CR V7 Stock report 5 Non-moving stock items

CR V7 Stock report 6 Spare part list

CR V7 Stock below min. Stock report, stock below minimum

CR V7 Stock report 8 Price list

CR V7 Stock taking res. Stock taking, result list

CR V7 Stock report 10 Stock taking list

CR V7 Stock report 11 Reservation survey

CR V7 Stock trans. Stock transaction report

CR V7 Project report Project report

CR V7 Project purchase Project report, purchases

CR V7 Crit. cond. Project report, critical conditions

CR V7 WO report 1 Planned/used cost report, account

CR V7 WO report 2 Planned/used cost report, project

CR V7 WO report 3 Planned/used cost report, work order

CR V7 WO report 4 MTBF/MTTR report

CR V7 WO report 5 Statistics - top lists

CR V7 WO report 6 Work supplier hour report

CR V7 PO report 2 Not delivered orders

CR V7 PO report 3 Not invoiced orders

CR V7 PO report 4 Agreement report

CR V7 PO report 5 Purchase order list

CR V7 PO report 6 Purchase invoice survey

CR V7 PO report 7 Purchase order status list

CR V7 PO report 8 Supplier performance

CR V7 PO report 9 Purchase & removal analysis

CR V7 PO accum 1 Purchase accum, supplier report

CR V7 PO accum 2 Purchase accum, supplier lines report

CR V7 Balance report Balance report

CR V7 Budget report Budget report

CR V7 Plant explorer Plant explorer report

CR V7 WO availability Work order availability report

CR V7 User permission User permission report

CR V7 Jobmonitor Jobmonitor list

CR V7 WS Calendar Work supplier calendar for work order

CR V7 Calibration history Calibration history

CR V7 Plant structure Plant structure

CR V7 Work order survey Work order survey

CR V7 Year Plan PM Work Order Year Plan

These interfaces can be enabled by entering „Yes‟ in the field Records used. You can enable different types of the same report.


If you create another interface record with the same type, it should have the prefix „CR‟.

When you print the report you will then get a question about which of the reports you want to print.

If you want to make changes in the standard designs, you can edit the .rpt files which are used to configure the printout designs.

The default .rpt files for the different printouts can be found in the Reports section of this manual.

9

4 General Layout

In this chapter the general layouts of a Crystal Reports print out will be presented. A print out is divided into different sections which are presented in the section „Sections‟.

4.1 Sections

Each .rpt file is divided into sections in order to be able to manage the data. The following sections are available:

- Report header

- Page header

- Details

- Report footer

- Page footer

You can among other things insert, delete, move, merge, split, hide, suppress sections so that the report gets the design of your choice. When creating a new report the following sections will by default be available:

4.1.1 Sections expert

The section expert, which can be found in the Report menu, should be used when making formatting changes that affect entire

sections of the report.

4.2 Sub reports

A sub report is a report within a report. The process for creating a sub report is similar to the process of creating a regular report. A

sub report can have most of the characteristics of a report, including its own record selection criteria. The only differences between

a sub report and a primary report are that a sub report:

- Is inserted as an object into a primary report; it cannot stand on its own (although a sub report can be saved as a primary report).

- Can be placed in any report section and the entire sub report will print in that section.


Cannot contain another sub report.

- Does not have Page Header or Page Footer sections.

For each report described in this manual, the available sub reports are presented and described. The sub reports cannot be found as

reports, because they are part of the main report. By right clicking on the sub report, you can, if wanted, save the sub report as an

.rpt file.

4.3 Inserting pictures

Report could include pictures of formats (bmp, tiff, jpeg, png).

To insert picture in report:

1. Insert -> OLE Object.

2. Select radio Create New and choose Bitmap Image.

3. Put on target section.

4. To configure file path open Format Graphic in pop up menu of created object, choose Picture tab and in Graphic Location

formula print path to picture or data source field with path.

5. To configure Suppress for unsupported formats: in open Format Graphic in pop up menu of created object choose

Common tab check Suppress and in formula type:

if InStr('bmp,tiff,jpg,jpe,jif,jpeg,jfif,png', Right({Drawing_Spare_part.File_name}, (Length

({Drawing_Spare_part.File_name}) - InStrRev({Drawing_Spare_part.File_name}, '.'))),1) > 0 then false else true

4.4 Standard template crstd5col.rpt The new, first introduced in Open.7, CR reports with similar simple layout use the standard template crstd5col.rpt, where general

layouts are combined, one of which is chosen by the parameters set in the report procedure and passed to the report template in the table Report_information. The data for the reports based on crstd5col.rpt is structurally standardized and saved in the table

Report_data.

4.4.1 Table structure

Report_data

Report_information

API_System

Z_*

The table Report_information includes details shown in a report or used for the decision on the report layout:

cFilterText the report selection criteria

cReportName the title of the report

cSubtotalTitle the title of the sub total values section cTotalTitle the title of the total values section

cUndefinedText text to be shown in numeric fields if data value is undefined, for example: 'N/A'

iNumFields the number of numeric fields in the report

iReportDetail the detail level of the report

iSectionFields based on the value of this field, the section header and the section footer are shown/suppressed

iSumFields based on the value of this field, the section footer is shown/suppressed

iTextFields the number of text fields in the report

lNotes logical field based on whose value the printout of notes is switched on/off

lSubTotals logical field, indicating whether the sub total values section is included/excluded

lTotals logical field, indicating whether the total values section is included/excluded

4.4.2 Sub reports

In each particular report, only one of all sub reports defined in the template crstd5col.rpt is shown. The choice among the sub

reports is made based on the values of the fields Report_information.iNumFields, Report_information.iTextFields and

Report_information.iReportDetail. For example, the sub report 'Sub Sum only + 4 (also 3, 2, 1)' is shown if

Report_information.iReportDetail = 1 (Only sum) and Report_information.iNumFields is any value in the interval from

11

1 to 4 (the report includes 1 to 4 figures for each report unit - maintenance object, spare part, transaction etc).

Sub report name Description Sub Sum only + 4 (also 3, 2, 1) 'Only sum' report with 1 to 4 figures per a report unit and total

section.

Sub normal 1 + 6 'Normal' report with 1 text value and 6 figures per a report unit,

subtotal and total sections.

Sub Normal 2 + 0 Normal' report with 2 text values per a report unit. Sub Normal 2 + 3 (also 2+2) 'Normal' report with 2 text values and 2 to 3 figures per a report

unit, subtotal and total sections.

Sub Normal 3 + 3 (also 3+2 and 3+1) 'Normal' report with 3 text values and 1 to 3 figures per a report


Sub Normal 4 + 2 (also 4+1) 'Normal' report with 4 text values and 1 to 2 figures per a report


Sub Normal 2 + 6 (2 rows) 'Normal' report with 2 text values and 6 figures output in two rows

per a report unit, subtotal and total sections.

Sub Normal 2 + 4 'Normal' report with 2 text values and 4 figures per a report unit,

subtotal and total sections.

Sub Normal 6 + 6 (2 rows), also ">3"+">3" 'Normal' report with 4 to 6 text values and 4 to 6 figures, output in

two rows per a report unit, subtotal and total sections.

Sub Normal 2 + 1 'Normal' report with 2 text values and 1 figure, subtotal and total

sections.

Text and numeric values for the sub reports are calculated in the report procedures and saved in the fields of the table Report_data.


5 Functionality

In this chapter functionality requiring some extra description is presented.

5.1 Label prints

The Mailing Labels Report Creation Wizard, which can be reached from the Start page, lets you create a report

that is formatted to print on any size label. The Label screen can be used to select a commercial label type, or

you can define your own layout of rows and columns for any multi-column style report.

The following is the default setup for the labels available from API PRO:

If you want to change some of the settings you need to create a new report and run the wizard again.

5.1.1 Add the barcode

The barcode have to be added to the report with help of a formula, namely:

'*' + cstr({table.field}, 0,'') + '*'

The formula converts the barcode to a string (characters), sets the number of decimals to 0 and removes the thousand separator.

Example: This is the formula added to the Label Account report:

'*' + cstr({account.Account_barcode }, 0,'') + '*'

13

5.2 Change the logotype in header

To change the logotype in all your reports you need to save the logotype image to be used as cr-icon.jpg in the

image directory. In table API_system (which is available in all reports) there is a field called CR-Icon. This

contains the full path to this image. In the Format editor for the default logotype, the Graphic Location points

at this path.

Note that as default the scaling is set to 10%. By changing this percentage you can get the image size wanted.

5.3 Z tables

All reports contain Z_tables. These tables store the labels for the data fields available in the report. All labels should be taken from these tables, because that makes them translatable.

The table Z_TEXTS contains labels for a report which are not available in any of the other Z_tables.

5.4 Change log

Each report has a change log where all changes made to the report after it was initially created are recorded with date, initials of the

person who made the change and a short comment. This can be found at:


File Summary Info

In the „Comments‟ field the change log can be found.

5.5 Lock position and size

Position and size can be locked on all objects part of the report, for example fields and graphics. This has been done on most of the

sub reports in the reports to prevent them from being moved around by mistake. If wanting to change the size or position of a

locked object, simply mark the object and enter its format Editor:

15

In the Format Editor you can easily lock and un-lock the object.


5.6 Report’s Export

When the export of any standard report is done to MS Excel, some columns and rows might be exported narrow. This is the

specifics of Crystal Reports export. A vertical or horizontal gap between a report field edge and the edge of a report section or a

gap between fields is interpreted as an empty row or column as high/wide as the gap in the report. It is not recommended that such

gaps are removed, especially horizontal gaps between fields. If field values next to each other were as wide as the field sizes and

there were no gap between the fields, this would look like one field.

As a workaround for the correct cells alignment the following export approach could be used:

Choose "Data only" in format options list

17

Select all desired check-boxes and click “Ok”.

As you can see from example, all rows look well formatted.


6 Crystal Reports Template Printouts

In this chapter the „API PRO – Crystal Reports‟ template reports available will be shortly described. The following information can be found about each report:

- The name of the report

- The name of the related Crystal Reports .rpt-file

- The name of the XML file

- Where the report is Called

- What an example report looks like

- Structure of the data

- What sub reports are available

6.1 Barcode Account

Report name: Account label print

Report type: Barcode Account

Crystal report file: crbarac.rpt

XML file: crbarac.xml

Called from: Special – Label print – Account – Print

Example report:

19


Account

Api_system

Z_*

6.2 Barcode Maintenance Obj.

Report name: Maint. Obj. label print

Report type: Barcode Maintenance Object

Crystal report file: crbarmo.rpt

XML file: CrBarMo.xml

Called from: Special – Label print – Maintenance object – Print

Example report:


Maintenance_object

Api_system

Z_*

6.3 Barcode Spare/Purch./Del.

Report name: Barcode Spare/Purch./Del.

Report type: Barcode Print Spare


Crystal report file: crbartmp.rpt

XML file: crbartmp.xml

Called from: Purchase – Delivery Registration – Options – Barcode print

Purchase – Purchase ordering – Options – Barcode print Basic – Basic data for stock - Spare part – Options - Barcode print

Special – Label print – Stock control – Spare print

Example report:


For the type SP (see the description of the types below):

Spare_part (SP_key, Supplier_key)

+ Stock_control

+ Stock

+ SP_supplier_combination (SP_key, Supplier_key)

A_arguments API_system

Z_*

For the types POSP and POSC (see the description of the types below):

Purchase_order_line

+ Spare_part

+ SP_supplier_combination

+ Stock_control

+ Stock

A_arguments

API_system Z_*

21

6.3.2 Special fields

In the table A_arguments the field „Type‟ is available. The type can be:

SP

Applies when the report is called from

Basic – Basic data for stock - Spare part – Options - Barcode print

Special – Label print – Stock control – Spare print

A spare part key, name and the barcode of the spare part are displayed. When a spare part is kept in several stocks, the table

stock_control contains the first found record of the stock the spare part can be located in.

POSP


Purchase – Delivery Registration – Options – Barcode print

Purchase – Purchase ordering – Options – Barcode print

and the parameter „Print only barcodes for spares on stock‟ is set to „No‟.

A Spare part key, name and the barcode of the spare part are displayed. When a spare part is kept in several stocks, the table

stock_control contains the first found record of the stock the spare part can be located in.

POSC


Purchase – Delivery Registration – Options – Barcode print

Purchase – Purchase ordering – Options – Barcode print

and the parameter „Print only barcodes for spares on stock‟ is set to „Yes‟.

A spare part key, the stock key, the location and the barcode of the stock control record are displayed.

6.3.3 Sub reports

Sub report name Description

SubPOLine This sub report will be shown when a_arguments.type is POSP or

POSC. The information is taken from purchase order line.

SubNoPOLine This sub report will be shown when a_arguments.type is SP. The

information is taken from the table spare_part.

6.4 Barcode Stock Control

Report name: Label Stock Control

Report type: Barcode Print

Crystal report file: crbar.rpt

XML file: CrBar.xml

Called from: Special – Label print – Stock Control – Print

Basic – Stock Control Data – Barcode print

Example report:



Stock_Control

+ Spare_part (SP_key)


+ Contact-SP_supplier_combination (Contact_Person_key)

+ Stock (Stock_key)

+ Address-Stock-Delivery (Delivery_Location_key)

+ Address-Stock-Invoice (Invoice_Location_key) + Contact-Stock (Contact_Person_key)

Api_system

Z_*

6.5 Barcode Stock

Report name: Stock label print

Report type: Barcode Stock

Crystal report file: crbarst.rpt

XML file: CrBarSt.xml

Called from: Special – Label print – Stock – Print

Example report:

23


Stock

+ Address-Stock-Delivery (Delivery_location_Key)

+ Address-Stock-Invoice (Invoice_location_Key)

+ Contact-Stock (Contact_Person_key)

Api_System

Z_*

6.6 Barcode Tool

Report name: Label Tool

Report type: Barcode Print Tool

Crystal report file: crbarto.rpt

XML file: CrBarTo.xml

Called from: Special – Label print - Tool

Example report:



Tool

+ Maintenance_object (MO_key)


+ Stock (Stock_key)

Api_system

Z_*

6.7 Barcode User

Report name: User label print

Report type: Barcode User

Crystal report file: crbarus.rpt

XML file: CrBarUs.xml

Called from: Special – Label print – User – Print

Example report:

25


Users

+ Contact-Users (Contact_Person_key)

+ Address-Users (Location_key)

Api_system

Z_*

6.8 Barcode Work Supplier

Report name: Work Supplier label print

Report type: Barcode Print Work Supplier

Crystal report file: crbarws.rpt

XML file: CrBarWs.xml

Called from: Special – Label print – Work supplier – Print

Example report:



Work_supplier

+ Contact-Work_supplier (Contact_Person_key) + Address-Work_supplier (Location_key)

Api_system

Z_*

6.9 Budget Report for Project

Report name: Budget report

Report type: Budget Report

Crystal report file: crbudrpt.rpt

XML file: crbudrpt.xml

Called from: Maintenance – Project – Project – Options – Budget – Print

Example report:

27


Project

+ Project_budget (Project_key)

+ Work_history (WO_key)

+ Work_order (WO_key)

A_Arguments

Api_system

Z_*


In A_Arguments the field rpt_type is available. Depending on what budget report is chosen in the screen below, this field will get a

value of 1, 2 or 3.

Internal/external work: 1

Stock/other materials: 2

All: 3


6.9.3 Sub reports


SUB Work This sub report will be shown when rpt_type = 1. It displays the

planned and used costs for internal and external work for the

current project.

SUB Material This sub report will be shown when rpt_type = 2. It displays the

planned and used costs for Stock material and other material for the current project.

SUB Total This sub report will be shown when rpt_type = 3. It displays the

total planned and used costs for the current project.

29

6.10 Calibration

Report name: Calibration job

Report type: Calibration

Crystal report file: crcaljob.rpt

XML file: crcaljob.xml

Called from: Special – Calibration – Calibration accumulation – Print sel.

Example report:


Maintenance_object

+ Calibration_activity (MO_key)

+ Calibration_time (MO_key)


+ Drawing_Maintenance_object (MO_key)

+ Note_Maintenance_object (MO_key)

+ Position (Pos_key)

+ Spare_part_Maintenance_object (MO_key)

+ Stock (Stock_key)

+ Technical_data_MO (MO_key)

+ Work_history (MO_key)

Drawing_Calibration

Drawing_Calibration_cali_setup

Motree (MO_key)


A_arguments

Api_system

Z_*

6.10.2 Sub reports

Sub report Description

SUB Tree Shows the tree structure for the maintenance object.

SUB TechData Shows all technical data attached to the Maintenance object and also technical

data to related TI (if available)

SUB Drawing MO Shows all documents attached to the Maintenance object.

SUB Drawing calibration Shows all the documents attached to the calibration in question.

SUB Drawing Setup Shows all the documents attached to the calibration setup/control setup in

question.

SUB Activities Shows all calibration activities related to the maintenance object.

6.11 Goods Receipt Note

Report name: Goods receipt note

Report type: GRN

Crystal report file: crgrn.rpt

XML file: crgrn.xml

Called from: Purchase - Delivery registration – GRN

Example report:

GRN only include transactions in date interval a_fromdate to a_todate. These dates are displayed in the upper right corner of the

report.

31


The same table structure as Purchase Order.

6.11.2 Sub reports


SUB PO Lines Displays all the purchase order lines which have a delivery status.

SUB HeaderNote Displays the External Header Note, if available, of the Purchase

order.

SUB FooterNote Displays the External Footer Note, if available, of the Purchase

order.


In the report several amount fields are used. The amount fields which end with _C are amounts calculated on the Purchase order

currency. The other amount fields are calculated on the system currency.

Note also that in the amount fields the discount is taken in account.

6.12 Work History Jobcard

Report name: Work History Card

Report type: Work History

Crystal report file: crhiscar.rpt

XML file: crhiscar.xml

Called from: Maintenance – Job history – Work order history data - Job card


Example report:


Work_history



+ wo-on-same-mo (MO_key)

+ Work_supplier-Responsible (work_supplier_key) + Error_code1 (Code1_key)

+ Error_code2 (Code2_key)


+ Account (Account_key)

+ Transactions_WS (WO_key)

+ Work_supplier_TR (Work_supplier_key)

+ Transactions_SP (WO_key)

+ Users_Ordered_by (Ordered_by)

+ Planned_Worksupp (WO_key)

+ work_supplier_planned_WS (work_supplier_key)

+ Planned_Spares (WO_key)

+ Spare_part (SP_key) + Stock_control (Stock_key, SP_key)

+ Work_order_work_note (WO_key)

+ Work_note (Work_note_key)

+ WN_SP_combination (Work_note_key)

+ Cost_type (Cost_type_key)

+ Jobstatus (JobstatusNo)

+ Jobcode (Jobcode_key)

+ Project (Project_key)

+ Inspection_rounds (Round_key)

+ inspection_header (Round_key)

+ Inspection_code (Inspection_code_key) + Inspection_maintenance_object (Mo_key)

+ Inspection_spare_part (SP_key)

+ Inspection_Counter (Counter_key)

+ Inspection_Work_note (Work_note_key)

+ Notification (WO_key)

+ Technical_ID (TI_key)

33

Notification_posmo

Work_supplier-Current-planned

A_arguments

Z_*

6.12.2 Sub reports


SUB Tree Shows the tree structure for the maintenance object of the work

history.

SUB Main Instruction Shows the Main instruction of the work history. If there is no

Main instruction available, the whole section is suppressed.

SUB Instruction Shows all the attached work instructions. If there are no

instructions available, the whole section is suppressed.

SUB SafetyNote Shows the Safety note linked to the Maintenance Object or

Position on the work history. If there is no safety note present, it

searches up in the tree, until it finds one. If there is no Safety note

available, the whole section is suppressed.

SUB Planned Spares Shows all planned spare parts on the work history. If there are no

planned spare parts, the whole section is suppressed.

SUB Planned WS

Shows all planned work suppliers on the work history. If there are

no planned work suppliers, the whole section is suppressed.

SUB Used Spares Shows all used spare parts on the work history. If there are no

used spare parts, the whole section is suppressed.

SUB Used Hours Shows all used work supplier hours on the work history. If there

are no used work supplier hours, the whole section is suppressed.

SUB DrawingWO

Shows all documents (drawings) on the work history. If there are

no documents the whole section is suppressed.

SUB DrawingMO Shows all documents (drawings) on the maintenance object of the

work history. If there are no documents the whole section is

suppressed.

SUB TechData

Shows all technical data related to the maintenance object and the

Technical ID on the work history. If there are no technical data,

the whole section is suppressed.

SUB TechData POS Shows all technical data related to the position on the work history. If there are no technical data, the whole section is

suppressed.

SUB wo-on-same-mo Shows history work orders on the same maintenance object as on

the history job card printed. This section is suppressed if the

option 'Print list showing work orders with same Maint. Obj.' is

not chosen in the work history job card dialog.

SUB Note Shows the note available on the work history.


Unit

First_found_stock_key


First_found_location

First_found_stock_control_barcode

These tables you will see if there were spare parts planned.

List_planned_WS

List_planned_WS is available in the work_order table. This field presents all planned work suppliers in a comma separated list.

ExtworkPlanned

ExtworkUsed

IntworkPlanned

IntworkUsed

ServicesPlanned

ServicesUsed

MaterialPlanned

MaterialUsed

StockMaterialPlanned

StockMaterialUsed

TotalPlanned

TotalUsed

These fields are available in the work_order table. They present planned and used costs of a work order split into different groups.

Please, refer to the description of the tab Costs of the program Work order in the User‟s Guide for details.

CPPhone

CPMobile_phone

CPFax

CPEmail

These fields are available in the tables work_supplier_current_planned, work_supplier_planned_WS, Work_supplier_Responsible

and Work_supplier_TR. They contain contact information of the contact person related to a work supplier.

Formula ‘Priority’

if {work_order.Priority_key} = '1' then {work_order.Priority_key} + ' !' else {work_order.Priority_key}

This formula makes it possible to highlight the highest priority. Depending on what priorities you use you need to update the

formula so that it affects the priority of your choice. In the default formula, priority „1‟ is highlighted with a „!‟ and it is also

written in red. The colour of the text is defined in the Font section of the Format editor for the field.

Formula ‘JobCardPerWS’

When the option „Print job card per work supplier‟ in the Maintenance Configuration program is set to „Yes‟ then it is possible to

print one job card for each planned work supplier. The Work supplier which the job card is printed for is defined in this field. The

field is available in the header of the report.

Formula ‘MOcard’

If the print option „Print machine card‟ is chosen then the Machine card will be printed immediately after the job card. To be aware of this extra printout the field „MOcard‟ is added to the report. The field „MOcard prints Machine card is printed when the print

option is set to „Yes‟.

Formula ‘SafetyNoteExist’

35

When a safety note is printed on the Job card then this is extra highlighted in the beginning of the job card. The field

„SafetyNoteExist‟ prints Safety Note exists when a safety note is available.


6.13 Inspection Registration

Report name: Inspection registration

Report type: Inspection Registration

Crystal report file: crinsreg.rpt

XML file: crinsreg.xml

Called from: Inspection – Inspection feedback by round – Options – Print registration

Example report:


The report is based on the following structure. The field displayed in the parenthesis is the link to which the table is linked.

Inspection_header

+ Work_supplier(Work_supplier_key)





+ Inspection_code (Inspection_code_key)

Api_system

Z_*

37

Note that table Inspection_rounds contains the „point_name‟ and also the registered values. All the registered values have a field

name which begins with ‟reg_‟.

6.13.2 Sub reports


SUB Registrations Shows all the registrations made for the each point of the round.


6.14 Inspection list

Report name: Inspection list printout

Report type: Inspection List

Crystal report file: crinsp.rpt

XML file: crinsp.xml

Called from: Inspection – Inspection accumulation – tool button 'Print'

Example report:


inspection_header + Note_inspection_header (barcode value)

+ inspection_rounds (Round_key)




+ Inspection_code (Inspection_code_Key)

+ Counter (Counter_key)

A_Argument

API_System

Z_*

39

Note that table Inspection_point has been removed. Instead the field „point_name‟ has been added to the table inspection_rounds.

6.14.2 Sub reports


SUB Points Displays the points filtered for.


6.15 Purchase Request Header

Report name: Purchase Request Header

Report type: Purchase Request Header

Crystal report file: crreqhd.rpt

XML file: crreqhd.xml

Called from: Purchase – Internal purchase request header – Options – Print

Example report:


Purchase_internal_request_header

+ Note_RH (PO_req_header_key)

+ Users (Uuser_id)

+ Purchase_internal_request (PO_req_header_key)

+ Note_RL (PO_int_req_key)

Api_system

A_argument

Z_*

6.15.2 Sub reports


SUB Note Presents the notes available on the internal purchase request. The

note types available are Internal note (Type: 1), External note

(Type: 2) and Rejection note (Type: 3).

SUB Lines Presents the lines of the internal spare part request.

41

6.16 Purchase Request Line

Report name: Internal Purchase Request

Report type: Purchase Int. Req.

Crystal report file: crintpur.rpt

XML file: crintpur.xml

Called from: Purchase – Internal purchase request – Print

Example report:


Purchase_internal_request

+ Note (PO_int_req_key)

Api_system

Z_*

6.16.2 Sub reports


SUB Note Presents the notes available on the internal purchase request. The

note types available are Default note (Type: 1), External note

(Type: 2) and Rejection note (Type: 3).


6.17 Service Invoice

Report name: Invoice Sales

Report type: Invoice Sales

Crystal report file: crinv_sa.rpt

XML file: crinv_sa.xml

Called from: Maintenance – Service – Customer invoice – Print Invoice

Example report:


Invoice_sales

+ Invoice_line_sales (Invoice_sales_key)

+ Work supplier (Work_Supplier_Key) + Note (Invoice_sales_key)

+ Customer (Customer_key)

+ Contact_person (Contact_Person_key)

+ Address_invoice (Invoice_Location_key)

Api_system

Z_*

6.17.2 Sub reports


SUB Notes Displays the Notes, if available, of the Sales invoice. The note

types available are Internal note (Type: 1) and External note

(Type: 2).

SUB Lines Displays all the invoice lines of the sales invoice. A line can be a

work order, a spare part or a work supplier.

43

6.18 Invoice

Report name: Invoice

Report type: Invoice

Crystal report file: crininfo.rpt

XML file: crininfo.xml

Called from: Purchase – Invoice registration – Print inv.

Example report:


Invoice + invoice_line (invoice_key)

+ IN_Transaction (Invoice_key)

+ TR_Purchase_order_line (PO_key, PO_line)

+ PL_Purchase_order (PO_key)

+ Supplier (Supplier_key)

+ Account_combination (Invoice_key)

API_System

A_argument

Z_*

6.18.2 Sub reports


SUB Lines Presents the lines of the invoice.


SubExtraCosts Shows the transactions related to the extra costs of the invoice.

45

6.19 Log Changes Data Sheet

Report name: Data sheet

Report type: Key change log

Crystal report file: crlogcrd.rpt

XML file: crlogcrd.xml

Called from: Log browsers

Example report:


Maintenance_object

+ ttTable(Table for which is log report)

+ ttLogs (Log entries for reported key (barcode) value)

+ ttFields (Changed fields for every log entries) Api_System

Z_*


6.20 WO Accum. List

Report name: Work order accumulation

Report type: Work Order List

Crystal report file: crjobacc.rpt

XML file: crjobacc.xml

Called from: Maintenance – Work order accumulation – Print – Simple list all work orders

Example report:


Work_order + Maitenance_object (MO_key)


Api_system

Z_*

6.21 WO Accum. Detailed List

Report name: Work order accumulation

Report type: Work Order detailed list

Crystal report file: crjobacd.rpt

XML file: crjobacd.xml

Called from: Maintenance – Work order accumulation – Print – Detailed list all work orders

Example report:

47


Work_order

+ Maitenance_object (MO_key)


+ Planned_Spares(wo_key)

+Spare_part(sp_key)

+Stock_control(stock_key, sp_key)

+Planned_worksupp(wo_key)

+Work_supplier_planned_WS(work_supplier_key)

Api_system

Z_*

6.22 Maint. Obj. Data Sheet


Report type: MO Data Sheet

Crystal report file: crmocard.rpt

XML file: CrMOcard.xml

Called from: Basic - Plant documentation – Maintenance object – Machine card

Example report:



Maintenance_object

+ Drawing_Maintenance_object (MO_key)


+ Note_Maintenance_object (MO_key)


+ Spare_part_Maintenance_object (MO_key)

+ Stock (Stock_key)

+ Technical_data_MO (MO_key)

+ Work_history (MO_key)

Motree (MO_key)

API_System

Z_*

6.22.2 Sub reports


SUB Tree Shows the tree structure for the maintenance object.

SUB Techdata Shows all technical data attached to the MO, either directly or via the Technical ID.

SUB SP Shows all spare parts attached to the MO, either directly or via Technical ID.

SUB Drawings Shows all drawings attached to the MO, either directly or via Technical ID.

SUB Workhistory Shows all work orders done on the MO.

49

6.23 Project Tree List

Report name: Project Explorer

Report type: Project Tree List

Crystal report file: crpjwo.rpt

XML file: crpjwo.xml

Called from: Maintenance – Project – Project explorer - Print

Example report:


Project_tree

+ Project (Project key)


+ Maintenance_object_WH (MO_key)


+ Maintenance_object_WO (MO_key)

A_Arguments

Api_system

Z_*

Purchase Confirmation Report name: Purchase order confirmation

Report type: PO-CONF

Crystal report file: cr-conf.rpt

XML file: cr-conf.xml

Called from: Purchase – Purchase ordering – PO-print – toggle box 'Confirmation'

Example report:



The same table structure as Purchase Order.

6.23.3 Sub reports


SUB POLines Displays all the purchase order lines of the purchase order.


order.


order.

51

6.24 Purchase Enquiry

Report name: Purchase Enquiry

Report type: Purchase Enquiry

Crystal report file: crenq.rpt

XML file: crenq.xml

Called from: Purchase – Purchase Enquiry – Enq. Print

Example report:


Purchase_enquiry


+ CP_Supplier (contact_person_key)

+ Location_Delivery (Delivery_location_key)

+ Location_Invoice (Invoice_location_key)

+ Location_Order (Order_location_key)

+ Location_Payment (Payment_location_key)

+ Contact_person (Contact_person_key)

+ Users_enquiry_by (Enquiry_by)

+ Purchase_enquiry_line (Enquiry_key)

Api_System

Z_*

Note that the notes are available as fields in the Purchase_enquiry table and the Purchase_enquiry_line table. The contact

information of the contact person related to an „Enquiry by‟ user is available in the fields CPemail, CPFax, CPMobile_phone and

CPPhone of Users_enquiry_by table.


6.25 Purchase Order

Report name: Purchase order

Report type: Purchase Order

Crystal report file: cr-po.rpt

XML file: cr-po.xml

Called from: Purchase – Purchase Ordering – PO-print

Example report:


Purchase_order

+ PO-Debit_account (Account_key)

+ PO-Credit_account (Credit_account_key)

+ Contact-PO (Contact_person_key)

+ Address-PO-Del (Delivery_location_key)

+ Address-PO-Inv (Invoice_location_key)

+ Address-PO-Ord (Order_location_key)

+ Address-PO-Pay (Payment_location_key)

+ Users (Order_by)

+ Delivery_header (PO_key)

+ Extra_cost_transactions (PO_key)


+ SU-Account (Account_key)

53

+ SU-Currency (Currency_key)

+ SU-Del_condition (Del_condition_key)

+ SU-Pay_condition (Pay_condition_key)

+ SU-Ship_condition (Ship_condition_key)

+ Supplier_Code (Supplier_code_key)

+ Supplier_Group (Supplier_group_key)

+ Currency (Currency_key)

+ Del_condition (Del_condition_key)

+ Pay_condition (Pay_condition_key)

+ Ship_condition (Ship_condition_key)

+ Site (Site_key)

+ Company (PO_key)

+ Purchase_order_line (PO_key)


+ Technical_data-SP (SP_key)


+ Work_supplier (Work_supplier_key)




+ PL-Account (Account_key)

+ PL-Cost_type (Cost_type_key)

+ PL-Cost_purpose (Cost_purpose_key)

+ Stock (Stock_key)

+ Stock_control (SP_key, Stock_key)

+ Unit-table (Unit_key)


+ Agreement (Agreement_key)

+ Manufacturer (Manufacturer_key)

+ Transactions (PO_key, PO_line)

+ Purchase_internal_request (PO_key, PO_line)

+ Purchase_internal_request_header (PO_req_hdr_key)

A_Argument

API_System

Z_*

Note that the notes are available as fields in the Purchase_order, Purchase_order_line and Spare_part tables.

6.25.2 Sub reports


SUB POLines Displays all the purchase order lines of the purchase order.


order.


order.


Formula ‘Barcode’ The purchase order barcode in the printable format.

Formula ‘Draft’

The formula checks whether the draft of a purchase order was chosen when printing. If so, it returns the line „DRAFT‟, which can

be printed at the title of the purchase order printout.


Formula ‘ExpDelivery’

The expected delivery date without the time part.

Formula ‘OrderDate’

The order date without the time part.

Formula ‘OrderedBy’

The name of the API PRO user specified in the field „PO ordered by‟ of a purchase order. If the user name is blank or such a user

does not exist in the system, the value of the field „PO ordered by‟ is returned.

Formula ‘LineAmount’ (sub report ‘SUB POLines’) The purchase order line quantity multiplied by the unit price, with the discount taken into account.

Formula ‘LineAmountCurrency’ (sub report ‘SUB POLines’) The purchase order line quantity multiplied by the unit price in the supplier‟s currency, with the discount taken into account.

Formula ‘LineBarcode’ (sub report ‘SUB POLines’) The purchase order line barcode in the printable format.

Formula ‘SP, WS’ (sub report ‘SUB POLines’) Not only can a spare part be registered as a purchase order line, but also a work supplier. The formula returns the proper key for

each purchase order line – a spare part key or a work supplier key.

Formula ‘SpareHeader’ (sub report ‘SUB POLines’) Used in the report header as the label of the column where combined information is shown - the supplier‟s spare part number, the

system spare part number and the spare part name.

Formula ‘TotalAmount’ (sub report ‘SUB POLines’)

The value of all purchase order lines of a Purchase order.

Formula ‘TotalAmountCurrency’ (sub report ‘SUB POLines’) The value of all purchase order lines of a Purchase order in the supplier‟s currency.

Formula ‘Unit’ (sub report ‘SUB POLines’)

The formula checks the purchase order line unit. A blank unit is considered to be „Hours‟. If a unit is not specified in a purchase

order line, the formula returns „Hours‟.

6.26 Purchase Order Reminder

Report name: Delivery Reminder

Report type: Purchase Reminder

Crystal report file: crporem.rpt

XML file: crporem.xml

Called from: Purchase – Purchase Reports – Purchase reminder reports

Purchase – Purchase ordering – Options – Delivery reminder

Example report:

Delivery reminder only prints purchase order lines with status <> 'F' (Not finished lines).

55


The same table structure as Purchase order.

6.26.2 Sub reports


SUB POLines Displays all the purchase order lines with status <> 'F' of the

purchase order. These are the not finished delivered lines.


order.


order.


6.27 Spare Part Data Sheet


Report type: SP Data Sheet

Crystal report file: crspcard.rpt

XML file: CrSPcard.xml

Called from: Basic – Basic data for stock – Spare part – Spare card

Example report:


Spare_part

+ Account(Account_key) + Default_Supplier(Supplier_key)

+ Drawing_Spare_part(SP_key)

+ Maintenance_object(SP_MO_combination.MO_key)

57

+ Manufacturer(SP_Manuf_combination.Manufacture_key)

+ Note_Spare_part(SP_key)

+ RepairItems(Maintanance.SP_key)

+ SP_code(SP_key)

+ SP_Group(SP_key)

+ SP_Manuf_combination(SP_key)

+ SP_MO_combination(SP_key)

+ SP_SP_combination(SP_key)

+ Included_Spares (SP_key)

+ SP_supplier_combination(SP_key) + Stock(Stock_control.Stock_key)

+ Stock_Control(SP_key)

+ Supplier(SP_supplier_combination.Supplier_key)

+ Technical_data_SP(SP_key)

Api_System

Z_*

6.27.2 Sub reports


SUB SP_TD_1 Shows all technical data attached to the SP.

SUB SP_Supplier Shows all combinations of suppliers and SP.

SUB SP_SP Shows all combinations of SP and SP.

SUB SP_MO Shows all MO where included SP.

SUB Repair Shows all MO where SP_key equals and Stock_key <> “”.

SUB Stock Shows stock control

SUB SP_Manuf. Shows all combinations of Manufacturer and SP.

SUB Note Shows all combinations of Note and SP.

SUB SP_doc Shows all combinations of Drawings and SP.


6.28 Work Order Job Card

Report name: Job card

Report type: Work Order

Crystal report file: crjobcar.rpt

XML file: crjobcar.xml

Called from: Maintenance – Job ordering – Job card

Maintenance – Work order – Job card

Maintenance – Work order accumulation – Print

Maintenance – Job feedback by work order – Job card

Example report:


Work_order



+ wo-on-same-mo (MO_key)

+ Work_supplier-Responsible (work_supplier_key)





59

+ Transactions_WS (WO_key)

+ Work_supplier_TR (Work_supplier_key)

+ Transactions_SP (WO_key)

+ Users_Ordered_by (Ordered_by)

+ Planned_Worksupp (WO_key)

+ work_supplier_planned_WS (work_supplier_key)

+ Planned_Spares (WO_key)


+ Stock_control (Stock_key, SP_key)

+ Work_order_work_note (WO_key) + Work_note (Work_note_key)

+ WN_SP_combination (Work_note_key)

+ Cost_type (Cost_type_key)


+ Jobcode (Jobcode_key)



+ inspection_header (Round_key)

+ Inspection_code (Inspection_code_key)

+ Inspection_maintenance_object (Mo_key)

+ Inspection_spare_part (SP_key) + Inspection_Counter (Counter_key)

+ Inspection_Work_note (Work_note_key)

+ Notification (WO_key)


Notification_posmo

Work_supplier-Current-planned

A_arguments

Z_*

6.28.2 Sub reports


SUB Tree Shows the tree structure for the maintenance object of the work

order.

SUB Main Instruction Shows the Main instruction of the work order. If there is no Main

instruction available, the whole section is suppressed.

SUB Instruction Shows all the attached work instructions. The Main Instruction is

written in bold. If there are no instructions available, the whole

section is suppressed.

SUB SafetyNote Shows the Safety note linked to the Maintenance Object or

Position on the work order. If there is no safety note present, it

searches up in the tree, until it finds one. If there is no Safety note

available, the whole section is suppressed.

SUB Planned SP Shows all planned spare parts on the work order. If there are no planned spare parts, the whole section is suppressed.

SUB Planned WS

Shows all planned work suppliers on the work order. If there are

no planned work suppliers, the whole section is suppressed.

SUB DrawingWO

Shows all documents (drawings) on the work order. If there are no

documents the whole section is suppressed.

SUB DrawingMO Shows all documents (drawings) on the maintenance object of the

work order. If there are no documents the whole section is

suppressed.


SUB TechData

Shows all technical data related to the maintenance object and the

Technical ID on the work order. If there are no technical data, the

whole section is suppressed.

SUB TechData POS Shows all technical data related to the position on the work order.

If there are no technical data, the whole section is suppressed.

SUB Note Shows the notes available on the work order. The note types

available are Plan note (Type: 1), History note (Type: 2),

Rejection note (Type: 3), Internal customer note (Type: 4) and

External customer note (Type: 5).

SUB wo_on_same_mo Shows all active work orders available on the same maintenance

object as on the job card printed. This section is suppressed if the option 'Print list showing work orders with same Maint. Obj.' is

not chosen in the work history job card dialog.

Sub Inspection Shows information on registered inspection activities related to

the Work order.


Unit

First_found_stock_key

First_found_location

First_found_stock_control_barcode

These tables you will see if there were spare parts planned.

List_planned_WS

List_planned_WS is available in the work_order table. This field presents all planned work suppliers in a comma separated list.

ExtworkPlanned

ExtworkUsed

IntworkPlanned

IntworkUsed

ServicesPlanned

ServicesUsed

MaterialPlanned

MaterialUsed

StockMaterialPlanned

StockMaterialUsed

TotalPlanned

TotalUsed

These fields are available in the work_order table. They present planned and used costs of a work order split into different groups.

Please, refer to the description of the tab Costs of the program Work order in the User‟s Guide for details.

CPPhone

CPMobile_phone

CPFax

61

CPEmail

These fields are available in the tables work_supplier_current_planned, work_supplier_planned_WS, Work_supplier_Responsible

and Work_supplier_TR. They contain contact information of the contact person related to a work supplier.

Formula ‘Priority’

if {work_order.Priority_key} = '1' then {work_order.Priority_key} + ' !' else {work_order.Priority_key}

This formula makes it possible to highlight the highest priority. Depending on what priorities you use you need to update the formula so that it affects the priority of your choice. In the default formula, priority „1‟ is highlighted with a „!‟ and it is also

written in red. The colour of the text is defined in the Font section of the Format editor for the field.

Formula ‘JobCardPerWS’

When the option „Print job card per work supplier‟ in the Maintenance Configuration program is set to „Yes‟ then it is possible to

print one job card for each planned work supplier. The Work supplier which the job card is printed for is defined in this field. The

field is available in the header of the report.

Formula ‘MOcard’

If the print option „Print machine card‟ is chosen then the Machine card will be printed immediately after the job card. To be aware

of this extra printout the field „MOcard‟ is added to the report. The field „MOcard prints Machine card is printed when the print

option is set to „Yes‟.

Formula ‘SafetyNoteExist’

When a safety note is printed on the Job card then this is extra highlighted in the beginning of the job card. The field

„SafetyNoteExist‟ prints Safety Note exists when a safety note is available.


6.29 Picking List

Report name: Picking list

Report type: Picking list

Crystal report file: crpcklst.rpt

XML file: crpick.xml

Called from: Stock – Picking list – Print

Example report:


Picking_list_header

+ Users-PL_by (Picking_list_by)

+ Note-PL-header (Picking_list_key) + Picking_list_line (Picking_list_key)


+ Transactions (Picking_list_key, SP_key)


+ Supplying_stock (SP_key)

+ Receiving_stock (SP_key, Stock_key)

+ Note-PL-line (Pick_line)

+ Purchase_internal_request (Picking_list_key, Pick_line)

+ Purchase_internal_request_header (PO_req_hdr_key)

+ Users-PR (Uuser_ID)

+ Stock (Stock_key)

+ Delivery_address (Delivery_location_key) + Invoice_address (Invoice_location_key)

+ Contact_person (Contact_person_key)

+ Site (Site_key)

+ Site_Company (Site_key)

+ Site_Company_Root (Site_key)

A_arguments

API_System

Z_*

63

6.29.2 Sub reports


SUB Lines Shows the lines available on the picking list


6.30 Picking List Removal Note

Report name: Picking list removal note

Report type: Pick removal note

Crystal report file: crpckrem.rpt

XML file: crpick.xml

Called from: Stock – Picking list – Register – Update – Update picked stocks and keep unfinished lines open

Example report:


Uses the same tables as Picking list.

6.31 Financial transaction report

Report name: Financial transaction report

Report type: Financial

Crystal report file: crecorap.rpt

XML file: crecorap.xml

Called from: Basic – Financial reporting – Financial transaction report

Example report:

65


Transtemp – temporary table with the selection from

transactions

+ spare_part (sp_key = the_key)

+ stock (stock_key = the_key)

+ account (account_key = the_key)

+ cost_type (cost_type_key = the_key)

+ work_order (wo_key = the_key)

+ work_history (wo_key = the_key)

+ purchase_order (po_key = the_key)

+ supplier (supplier_key = the_key)

+ maintenance_object (mo_key = the_key)

+ position (pos_key = the_key)

+ work_supplier (work_supplier_key = the_key)

+ agreement (agreement_key = the_key)

+ cost_purpose (cost_purpose_key = the_key)

Filter_Temp - temporary table with text about selection criteria applied; the text is shown at the top of the report's pages

API_system

Z_*

6.31.2 Sub reports



Sub Sum Only The layout applied if 'Only sum' report is chosen.

Sub Normal The layout applied if 'Normal' or 'Detailed' report is chosen.

Sub Main Account The layout applied if 'Normal' Main debit account report is

chosen.

Sub Main Account Detail The layout applied if 'Detailed' Main debit account report is

chosen.

Sub Main Account Sum Only The layout applied if 'Only sum' Main debit account report is chosen.


Field transtemp.the_key

The field contains the values of field by which the report is grouped. The report grouping depends on the value chosen in 'Type'

combo box when the user defines filter criteria of the report.

Field transtemp.quantity

For work order point of view the value is taken from 'wo_quantity' field of transtemp table, for stock point of view the value is

taken from 'quantity' field of transtemp table.

67

6.32 Work history, CR design

Report name: History

Report type: Work history report

Crystal report file: crhistrp.rpt

XML file: crhistrp.xml

Called from: Maintenance – Job history – History on-line

Maintenance – Job history – Work order history data – Work order key point&shoot button - Report

Example report:


history_data – temporary table with the selection from

+Notification (WO_key)

work_history

+ transactions (wo_key)

+ spare_part (sp_key)

+ note (relate_key = wo_key)


+ position (pos_key = the_key)

+ maintenance_object (mo_key = the_key)

+ account (account_key = the_key)

+ cost_type (cost_type_key = the_key)

+ cost_purpose (cost_purpose_key = the_key)

+ technical_id (TI_key = the_key)

+ mo_code (mo_code_key = the_key)

+ mo_group (mo_group_key = the_key)

+ work_supplier (work_supplier = the_key)

history_labels - temporary table with text about selection criteria applied; the text is shown at the top of the report's pages

API_system

Z_*

6.32.2 Sub reports


SubWOSU Presents transactions per work supplier related to the work

order. This sub report is suppressed when 'Only sum' detail level

is chosen.

SubWOSP Presents transactions per spare part related to the work order.

This sub report is suppressed when 'Only sum' detail level is

chosen.


Field history_data.the_key

The field contains the values of field by which the report is grouped. The report grouping depends on the value chosen in 'Job

history report' combo box when the user defines filter criteria of the report.

Running total fields

Running total fields are used for calculating sums grouped by history_data.the_key and total report sums. There are separated sums

for work suppliers, spare parts, internal resources and external resources. In order to perform this separation the following

conditions are applied in running total fields:

not ({history_data.tr_work_supplier_key} = '') - transactions related to work suppliers

{history_data.tr_work_supplier_key} = '' - transactions related to spares

{history_data.external_resource} – transactions related to external work resources

not ({history_data.external_resource}) – transactions related to internal work resources

The combinations of these conditions are used to calculate different total fields. For example, running total field RSubTotalHours:

Sum of history_data.quantity grouped by history_data.the_key satisfying the condition:

not ({history_data.tr_work_supplier_key} = '')

The value of history_data.quantity is interpreted as the quantity of worked hours if tr_work_supplier_key is not empty. This formula calculates the total worked hours for each group. E.g., if the report is grouped by position, RsubtotalHours accumulates

hours related to a particular position.

Formula fields

These fields use running total fields either to combine separated sums or to display sums in a proper format (zero instead of a blank

69

value or accumulated value if non-zero).

6.33 Notification Card

Report name: Notification card

Report type: Notification card

Crystal report file: crntfcard.rpt

XML file: crntfcard.xml

Called from: Maintenance – Shift log book – Notification – Notification card

Example report:


Notification

+ Shift_responsibility_area (Shift_resp_area_key)

+ Shift_log (shift_log_key)

+ Shift_type (shift_type_key)

+ Shift_responsibility_area (Shift_resp_area_key)

+ Notification_type (notification_type_key)


+ Maintenance_object (Mo_key)

+ Work_supplier (work_supplier_key)

+ Contact_person (contact_person_key)


+ Priority (priority_key)

+ Work_order (wo_key)


+ Work_history (wo_key)


+ Users (via ordered_by)

API_System

MoTree - Plant structure

Position - From first position on Maintenance object

Z_*

6.33.2 Sub reports


SubTree Shows the tree structure for the maintenance object.

SubDrawingNTF Shows the list of all documents attached to Notification.

SubDrawingWO Shows the list of all documents attached to a work order, which

is related to Notification.

SubDrawingWH Shows the list of all documents attached to a registered work

order, which is related to a Notification.

SubTechDataMO Shows the technical data on the maintenance object, related to a

Notification.

SubTechDataPos Shows technical data on the position, related to a Notification.

SubNote Shows the notes attached to a notification.

6.34 Notification list

Report name: List of Notifications

Report type: NTFList

Crystal report file: crntflist.rpt

XML file: crntflist.xml

Called from: Maintenance – Shift log book – Notification monitor – Print

Example report:

71


ttNotification – temporary table

+ Shift_log (Shift_log_key)

+ shift_type (shift_type_key)

+ ShiftRespArea_shiftlog (Shift_resp_area_key)

+ notification_type (notification_type_key)



+ Work_supplier_Resp (work_supplier_key)

+ Work_supplier_Resp_CP (contact_person_key)


+ work_history (wo_key)


+ work_order (wo_key)

+ Jobstatus_WO (JobstatusNo)

+ ShiftRespArea_notification (Shift_resp_area_key)

ttReportInfo

Api_system Z_*

6.35 Shift history report

Report name: Shift history report

Report type: ShiftLog

Crystal report file: crshiftlog.rpt

XML file: crshiftlog.xml

Called from: Maintenance – Shift log book – Notification monitor – History report


Maintenance – Shift log book – Shift history - Print

Example report:


ttNotification – temporary table

+ Shift_log (Shift_log_key)

+ shift_type (shift_type_key)

+ ShiftRespArea_shiftlog (Shift_resp_area_key)

+ notification_type (notification_type_key)



+ Work_supplier_Resp (work_supplier_key)

+ Work_supplier_Resp_CP (contact_person_key)


+ work_history (wo_key)


+ work_order (wo_key)

+ Jobstatus_WO (JobstatusNo)

+ ShiftRespArea_notification (Shift_resp_area_key)

ttReportInfo

Api_system

Z_*

6.36 Stock Value List

Report name: Stock value list

73

Report type: Stock_report_1

Crystal report file: crstockval.rpt

XML file: crstockval.xml

Called from: Stock - Stock control reports - Stock value list

Example report:


Report_data + Stock (Stock_key)

+ Spare_part (Sp_key)

+ SP_code (Sp_code_key)

+ SP_group (SP_group_key)

Report_information

API_System

Z_*

6.36.2 Sub reports


SubCompressed Shows the list of stocks without details on stored spares.

SubNormal Shows the list of stored spares for every stock with their

quantity, price and value.

6.37 ABC Analysis

Report name: ABC Analysis


Crystal report file: crabc.rpt

XML file: crabc.xml

Called from: Stock - Stock control reports - ABC Analysis

Example report:



Report_data

Report_information

API_System

Z_*

The structure of the table Report_information is the same as in the standard template crstd5col.rpt.

6.38 Stock Control Data

Report name: Stock control data


Crystal report file: crstockdata.rpt

XML file: crstockdata.xml

Called from: Stock - Stock control reports - Stock control data list

Example report:


Report_data

+ Stock_control (Stock_key,SP_key)

+ Stock (Stock_key) + Spare_part (SP_key)

Report_information

API_System

Z_*

75

Table Report_information has the same structure as in crstd5col.rpt. See details in section 'Standard template crstd5col.rpt'.

6.39 Stock Inventory Turnover

Report name: Stock inventory turnover


Crystal report file: crinvturn.rpt

XML file: crinvturn.xml

Called from: Stock - Stock control reports – Inventory turnover report

Example report:


Report_data

Report_information

API_System

Z_*


Report_data.section_key Stock key.

Report_data.section_name

Stock name.

Report_data.text_column_1

Spare part key in 'Normal' report, stock key in 'Compressed' report.


Spare part name in 'Normal' report, stock name in 'Compressed' report.

Report_data.numeric_column_1


Removal quantity.


Average quantity.


Inventory turnover.


Subtotal turnover for all spare parts of a stock (in 'Normal' report).


Total turnover for all stocks in the report interval.


6.40 Non-moving Stock Items

Report name: Stock without removals


Crystal report file: crstocknoremoval.rpt

XML file: crstocknoremoval.xml

Called from: Stock - Stock control reports - Non-moving stock items

Example report:


Report_data


+ Stock_control_location (SP_key,Stock_key,Stock_location_key)

+ Stock (Stock_key)

+ Spare_part (SP_key) Report_information

API_System

Z_*


Report_data.stock_key

77

Stock key

Report_data.stock_name

Stock name

Report_data.sp_key

Type number

Report_data.sp_name

Name

Report_data.Stock_location_key Location

Report_data. unit

Unit

Report_data.quantity_physical

Phys. quantity

Report_data. StocknoRemovalValue

Value


6.41 Spare Part List

Report name: Spare struct. For Maint. Obj.


Crystal report file: crsplist.rpt

XML file: crsplist.xml

Called from: Stock - Stock control reports - Spare part lists

Example report:


Report_data




+ sp_supplier_combination


+ Stock

Report_information

API_System

Z_*


6.42 Stock Report, Stock Below Minimum

Report name: Stock report, stock below minimum


Crystal report file: stockbelowmin.rpt

XML file: stockbelowmin.xml

Called from: Stock - Stock control reports - Spares/stock below minimum

Example report:


Report_data

+ SP_Code (SP_code_key)


+ Stock (stock_key)

+ Spare_part (sp_key)

+ Sp_group (sp_group_key) Report_information

API_System

Z_*


Report_data.section_key

Stock key or Supplier key depending on the selected parameter

Report_data.section_name

Stock name or Supplier name depending on the selected parameter

Report_data. sp_key

SP key

Report_data. sp_name

SP name

Report_data. sp_code_key

SP code key

79

Report_data. sp_group_key

SP group key

Report_data. stock_key

Stock key

Report_data. supplier_key

Supplier key

Report_data. stock_location_key

Location

Report_data.max_Quantity

Max quantity

Report_data. Quantity_at_disp

Quantity for use

Report_data. Quantity_physical

Phys. quantity

Report_data. min_Quantity

Min quantity

Report_data. Quantity_ordered

Ordered quantity


6.43 Price List

Report name: Price list


Crystal report file: crpricelist.rpt

XML file: crpricelist.xml

Called from: Stock - Stock control reports – Price list

Example report:


Report_data


+ Stock_control


+ Stock

+ Default_Supplier ()

+ SP_code

+ SP_Group

+ Account

+ Cost_type

Report_information

API_System

Z_*


Report_data. sp_key

Type number

Report_data. sp_name

Name

Report_data. purchase_price

Purchase price

Report_data.profit

Profit rate

Report_data.sales_price

Sales price


6.44 Stock Taking, Result List

Report name: Stock taking, result list


Crystal report file: crstocktakingresult.rpt

XML file: crstocktakingresult.xml

Called from: Stock - Register stock taking list - OK - Print res.

Example report:


Report_data


+ Stock (Stock_key) + Stock_control (Stock_key,SP_key)

+ Stock_inventory (Inventory_no,Stock_key,stock_location_key,SP_key)

+ Stock_inventory (Inventory_no,Stock_key,location,SP_key)

Report_information

API_System

Z_*

81


6.45 Stock taking list

Report name: Stock taking list


Crystal report file: crstocktaking.rpt

XML file: crstocktaking.xml

Called from: Stock – Stock taking list

Example report:


Report_data

Report_information

API_System

Z_*


Report_data.InvLocation Location.

Report_data.CntLocation

The list of alternative locations.


6.46 Reservation Survey

Report name: Reservation survey


Crystal report file: crreservsurvey.rpt

XML file: crreservsurvey.xml

Called from: Stock - Stock control reports - Reservation survey

Example report:



Report_data



+ Stock (stock_key)

+ work_order (WO_key)

+ Jobstatus_WO (LanguageKey)

+ Jobstatus_WH (LanguageKey) + work_history (WO_key)

Report_information

API_System

Z_*


6.47 Stock Transaction Report

Report name: Stock transaction report


Crystal report file: crstocktrans.rpt

XML file: crstocktrans.xml

Called from: Stock - Stock control reports - Stock transaction report

Example report:


Report_data

83

Report_information

API_System

Z_*


Report_data.text_column_1 For 'Normal' and 'Only sum' reports – transaction date.


For 'Normal' and 'Only sum' reports – transaction type.


For 'Normal' and 'Only sum' reports – quantity.

Report_data.numeric_column_2 For 'Normal' and 'Only sum' reports – transaction amount.

Report_data.section_key, Report_data.section_name

Dependent on the report type chosen.

For 'Spare part type number interval' – spare part key, spare part name.

For 'Stock interval' – stock key, stock name.

For 'Account interval' – credit account key, credit account name.

For 'Work order number interval' – work order key, work order name.

For 'Purchase order key interval' – purchase order key, purchase name.

For 'Supplier interval' – supplier key, supplier name.

Report_data.text_column_3, Report_data. text_column_4

Used in 'Normal' and 'Only sum' reports, dependent on the report type chosen.

For 'Spare part type number interval' – stock key, text_column_4 is not used.

For 'Stock interval' – spare part key, work order key.

For 'Account interval' – spare part key, stock key.

For 'Work order number interval' – spare part key, stock key.

For 'Purchase order key interval' – spare part key, stock key.

For 'Supplier interval' – spare part key, stock key.

Report_data.DetailedField1, Report_data.DetailedField2, Report_data.DetailedField3, Report_data.DetailedField4,

Report_data.DetailedField7

Used in 'Detailed' report, dependent on the report type.

For 'Spare part type number interval' – stock key, DetailedField2 is not used, credit account key, supplier key, purchase order key.

For 'Stock interval' – spare part key, work order key, credit account key, supplier key, purchase order key.

For 'Account interval' – spare part key, stock key, work order key, supplier key, purchase order key.

For 'Work order number interval' – spare part key, stock key, credit account key, supplier key, purchase order key.

For 'Purchase order key interval' – spare part key, stock key, credit account key, supplier key, work order key.

For 'Supplier interval' – spare part key, stock key, credit account key, work order key, purchase order key.


6.48 Project Report

Report name: Project report

Report type: Project_report_1

Crystal report file: crpj.rpt

XML file: crpj.xml

Called from: Maintenance – Project – Project report


Example report:


Report_data


+ Purchase_order (PO_key)

+ Purchase_order_line (PO_key,po_line)

Report_information

API_System

Z_*


6.49 Project Report, Purchases

Report name: Purchase report


Crystal report file: crstd5col.rpt

XML file: crstd5col.xml

Called from: Maintenance – Project – Purchase report

Example report:


See section 'Standard template crstd5col.rpt'.

85

6.49.2 Sub reports


6.50 Project Report, Critical Conditions

Report name: Critical condition report


Crystal report file: crcritcond.rpt

XML file: crcritcond.xml

Called from: Maintenance – Project – Project – Crit. Cond.

Example report:


Report_data



Report_information

API_System

Z_*


6.51 Planned/used Cost Report, Account

Report name: Planned/used cost report, account

Report type: Work_order_report_1

Crystal report file: crcostac.rpt

XML file: crcostac.xml

Called from: Maintenance – Planned/used cost report – Account interval

Example report:



Report_data

+Work_order (WO_key)

+Work_history (WO_key)

+Account (Account_key)

Report_information

API_System Z_*


6.52 Planned/used Cost Report, Project

Report name: Planned/used cost report, project


Crystal report file: crcostpj.rpt

XML file: crcostpj.xml

Called from: Maintenance – Planned/used cost report – Project interval

Example report:


Report_data



+ Project (Project_key) Report_information

API_System

Z_*


87

6.53 Planned/used Cost Report, Work Order

Report name: Planned/used cost report, work order


Crystal report file: crcostwo.rpt

XML file: crcostwo.xml

Called from: Maintenance – Planned/used cost report – Work order number interval

Example report:


Report_data



Report_information

API_System Z_*


6.54 MTBF/MTTR Report

Report name: MTBF/MTTR report




Called from: Maintenance – Job history – MTBF/MTTR report

Example report:




6.54.2 Sub reports


6.55 Statistics – Top Lists

Report name: Statistics – top lists


Crystal report file: crhisttop.rpt

XML file: crhisttop.xml

Called from: Maintenance – Job history – Statistics-top lists

Example report:


Report_data

+Maintenance_object (MO_key)

Report _information

API_System

Z_*


6.56 Work Supplier Hour Report

Report name: Work supplier hour report


Crystal report file: wshour.rpt

XML file: wshour.xml

Called from: Maintenance – Job history – Work supplier hour report

Example report:

89


Report_data

Report_information

API_System

Z_*


6.57 Not Delivered Orders

Report name: Not delivered orders

Report type: po_report_2

Crystal report file: po_line_info.rpt

XML file: po_line_info.xml

Called from: Purchase - Purchase reports - Not delivered orders

Example report:


Purchase_order

+ Purchase_order_line

+ Spare_part

+ PL_Account

+ PL_Cost_type

+ PL_Cost_purpose

+ Unit_table + Work_supplier

+ PO_Debit_Account


+ PO_Credit_Account

+ Users

+ Supplier

+ SU_Account

+ SU_Currency

+ Currency

+ Site

Report_information

API_System Z_*


6.57.2 Sub reports


Sub POLine Shows purchase order lines.

Sub PO header per order date This sub report is suppressed in this report. It is used in

Purchase Order List report.

6.58 Not Invoiced Orders

Report name: Not invoiced orders




Called from: Purchase - Purchase reports - Not invoiced orders

Example report:


Purchase_order


+ Spare_part + PL_Account

+ PL_Cost_type

+ PL_Cost_purpose

91

+ Unit_table

+ Work_supplier

+ PO_Debit_Account

+ PO_Credit_Account

+ Users

+ Supplier

+ SU_Account

+ SU_Currency

+ Currency

+ Site

Report_information

API_System

Z_*


6.58.2 Sub reports



Sub PO header per order date This sub report is suppressed in this report. It is used in

Purchase Order List report.

6.59 Agreement Report

Report name: Agreement report


Crystal report file: cragreement.rpt

XML file: cragreement.xml

Called from: Purchase – Agreement – Report

Example report:


Agreement

+ Note_Agreement

Purchase_order_line

Report_information

API_System

Z_*



6.60 Purchase Order List

Report name: Purchase order list




Called from: Purchase - Purchase reports – Purchase order list

Example report:


Purchase_order


+ Spare_part

+ PL_Account

+ PL_Cost_type

+ PL_Cost_purpose + Unit_table

+ Work_supplier

+ PO_Debit_Account

+ PO_Credit_Account

+ Users

+ Supplier

+ SU_Account

+ SU_Currency

+ Currency

+ Site

Report_information

API_System

Z_*


93

6.60.2 Sub reports


Sub POLine Not used in this report.

Sub PO header per order date Shows purchase orders.

6.61 Purchase Invoice Survey

Report name: Purchase invoice survey


Crystal report file: invoice_info.rpt

XML file: invoice_info.xml

Called from: Purchase - Purchase reports – Purchase invoice survey

Example report:


Report_data

+ Invoice

+ Supplier

Report_information

API_System

Z_*


6.62 Purchase Order Status List

Report name: Purchase order status list




Called from: Purchase - Purchase reports – Purchase order status

Example report:



Purchase_order


+ Spare_part

+ PL_Account

+ PL_Cost_type

+ PL_Cost_purpose

+ Unit_table + Work_supplier

+ PO_Debit_Account

+ PO_Credit_Account

+ Users

+ Supplier

+ SU_Account

+ SU_Currency

+ Currency

+ Site

Report_information API_System

Z_*


6.62.2 Sub reports



Sub PO header per order date Not used in this report.

6.63 Supplier Performance

Report name: Supplier performance


Crystal report file: supplier_performance.rpt

XML file: supplier_performance.xml

Called from: Purchase - Purchase reports – Supplier performance

95

Example report:


Report_data Report_information

API_System

Z_*


6.64 Purchase & Removal Analysis

Report name: Purchase – top list

Report type: PO_report_9



Called from: Purchase – Purchase reports – Purchase & removal analysis

Example report:




6.64.2 Sub reports


6.65 Purchase Accum, Supplier Report

Report name: Purchase accumulation

Report type: po_accumulation_1

Crystal report file: crpuraccsu.rpt

XML file: crpuraccsu.xml

Called from: Purchase – Accumulation of purchase need – Print – Supplier information

Example report:


Report_data

+ Supplier (supplier_key)


Z_*


6.66 Purchase Accum, Supplier Lines Report

Report name: Purchase accumulation lines for supplier

Report type: po_accumulation_2

Crystal report file: crpuraccsulines.rpt

XML file: crpuraccsulines.xml

Called from: Purchase – Accumulation of purchase need – Print – Accumulated lines for supplier

Example report:

97


Report_data


+ Spare_part (sp_key)

+ Purchase_internal_request (po_int_req_key)

+ Unit (unit)

Report_information API_System Z_*


6.67 Balance Report

Report name: Balance report

Report type: account_report_1

Crystal report file: craccbal.rpt

XML file: craccbal.xml

Called from: Basic - Financial reporting - Balance report

Example report:


Report_data

+ Account_main (Account_key)


Report_information

API_System Z_*


6.68 Budget Report

Report name: Budget report

Report type: account_report_2


Crystal report file: craccbud.rpt

XML file: craccbud.xml

Called from: Basic - Financial reporting - Budget report

Example report:


Report_data

+ Account_main (Account_key)


Report_information

API_System

Z_*


6.69 Work Order Availability Report

Report name: Work order availability report

Report type: wo_availability

Crystal report file: crwoavail.rpt

XML file: crwoavail.xml

Called from: Maintenance – Work order accumulation – Options – Total availability report

Example report:

99


Report_data

+ Work_order (WO_key) Report_information

API_System

Z_*


6.70 User Permission Report

Report name: User permissions

Report type: user_report_2

Crystal report file: userperm.rpt

XML file: userperm.xml

Called from: System - User - Permission report

Example report:


Report_data (user_permissions)

+ Users

Report_information

API_System

Z_*



6.71 Jobmonitor List

Report name: Jobmonitor

Report type: jobmonitor

Crystal report file: jobmonitor.rpt

XML file: jobmonitor.xml

Called from: Maintenance – Job monitor – Print

Example report:


Report_data

Work_order

Maintenance_object

Position

Report_information

API_System

Z_*


6.72 Work Supplier Calendar for Work Order

Report name: Work supplier calendar for work order

Report type: wscalendar

Crystal report file: wscalendar.rpt

XML file: wscalendar.xml

Called from: Maintenance – Work order – Options – Calendar... (this option is available when Planning module is not

installed) – Print

Example report:


Report_data

Report_information

API_System

Z_*


101

6.73 Calibration History

Report name: Calibration history

Report type: calibration_report_1

Crystal report file: calhist.rpt

XML file: calhist.xml

Called from: Special – Calibration – Calibration measurements – History

Example report:


Calibration_activity

+ Calibration_history

Report_information

API_System

Z_*


6.74 Plant Structure

Report name: Plant structure

Report type: posmo_report_1

Crystal report file: posmotree.rpt

XML file: posmotree.xml

Called from: Basic – Information searching – Plant explorer – Print

Example report:



TreeList


+ Maintenance_object (Mo_key) + Work_order (WO_key)


+ Drawing (Drawing_key)


+ Inspection_points (point_key)

+ Notification (notification_key)

Report_information

API_System

Z_*


6.75 Work Order Survey

Report name: Work order survey

Report type: jobsurvey

Crystal report file: jobsurv.rpt

XML file: crjobsurv.xml

Called from: Maintenance – Work order survey –Print

Example report:

103


Report_data

Report_information

API_System

Project_WH

Project_WO

Work_history

Work_order

Work_supplier

Z_*


6.76 PM Work Order Year Plan

Report name: Yearplan

Report type: yearplan

Crystal report file: yearplan.rpt

XML file: yearplan.xml

Called from: Maintenance – Work order Year plan – Print

Example report:


Report_data

Week_numbers

Yearplan_options


Z_*



6.77 Inspection barcode

Report name: Inspection

Report type: barcode

Crystal report file: crbarinsp.rpt

XML file: crbarinsp.xml

Called from: Inspection – Inspection round setup – Barcode (select line)

Example report:


Inspection_header

Inspection_points

Inspection_rounds

Maintenance_object

API_System

Z_*

6.78 Work instruction

Report name: WI card

Report type: Work instruction

Crystal report file: crwicard.rpt

XML file: crwicard.xml

Called from: Basic – Basic data for maintenance – Work instruction

Example report:

105


Drawing_work_note

MO_group

Note_work_note

Spare_part

WN_MO_group_combination

WN_SP_Combination

Work_note

Work_note_combination

Work_note_combination_work_note

Work_note_Replaced Work_supplier

API_System

Z_*

7 ODBC-based Crystal Reports

7.1 Report properties

To be properly accessed in API PRO, ODBC-based Crystal Reports files should meet a number of requirements.

1. There are not any current connections in the rpt-file.

To check this, choose Database - Log On or Off Server… menu item and expand Current Connections node. If there are any

connections, press <Log Off> button for each active connection until you do not have any items under Current Connections.

Next time you choose this menu, you will have … no items found.

2. Use DSN Default Properties is set to False.

To check this value, you should choose Database – Set Datasource Location… menu item. This parameter is seen under Properties node of your report data source, as shown in the picture below. If the parameter is set to True, right-click the mouse on

it, choose Edit and put False instead.


7.2 Portability

It is possible to use a report file on different PCs.

The Override database name field should be filled in when creating a record in Crystal Reports browser on the PC a report was

copied to.

For example: A report file is created on PC1, using DSN DSN1, and then copied to PC2, where DSN2 is used to connect to the API PRO database named API3. To be able to view this report on PC2, a record should be created on PC2 for this report, and the

database name API3 should be entered.

107

7.3 Logical fields in ODBC-based reports Logical fields represented in the 'Yes/No' format are shown translated to Windows language, not to the current language of API

PRO. In some languages, the translated 'Yes' is shown for False and the translated 'No' is shown for True (the problem is known for

Polish, there might be other languages where the values formatted as „Yes/No‟ change to opposite).

To solve this, change the format of all logical fields included in your ODBC based report: select a field in the CR Developer layout

and choose the menu Format – Format field. Add the „Display String‟ formula:

If { < logical-field > } then

< Yes-phrase-in-your-language >

Else < No-phrase-in-your-language >

In the picture below, you can see an example of a formula for displaying the value of the field account.budget_account in German.

Documents

API PRO - Crystal Reports Manual · 1 1 About the manual The purpose of this manual is to give a description of the Crystal Reports template printouts available in API PRO and to