Reports > Reports 

This function is used to release the printing of a standard report from the software, by authorizing the entry of setup values, then releasing the launch of the print module (DLL Crystal Reports ™).

This function operates in a classic fashion with a left list presenting the report list, and a right-hand part that makes it possible to enter the print setups and to start the print.

It should be noted that the printing of a report can be released in two other ways :

  • from the menu Print/group. In this case, the report to be printed is directly chosen from the report list of the corresponding group.
  • from the object management, by using the functions File / Print or File / List (this supposes that the reports are assigned to the buttons : the function object customization is used to do this, and a dedicated function makes it possible to define the default values dependent on the context.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

Once the report code has been selected, the following elements need to be entered :

  • the report setups, in a grid whose lines are dependent on the report.
  • the destination of the print, if any (or the detailed definition of the issue).
  • additional layout setups (which can be predefined if a destination has been chosen).

Close

 

Fields

The following fields are present on this tab :

Block number 1

It defines the report code to be printed.

  • field RPTDES

Enter the description of the relevant record.

This long description is used as a title in screens and reports.

Grid Parameters

  • No. (field PARNUM)

 

  • Parameter title (field PARDES)

It specifies the name of the parameter to be entered.

  • Parameter type (field DEBFIN)

 

  • First value (field VALEUR1)

This grid makes it possible to assign the parameters necessary to print the report. These parameters can have the following characteristics :

*  they can be of the start/end type (two values to enter) or of a unique type (a single value)

*  they can be according to the cases, chosen from a selection window, or entered as a local menu (choose from a list : in this case, the start of the title can be entered, for instance Y for Yes)

*one of the parameters (predefined in the report) normally entered in the form of a range can be further broken down into several ranges. This is useful when a report must be printed, and that a large number of pages exist given the volume that will be generated (in general, this is a question that needs to be asked for reports that exceed 10,000 pages since Crystal Reports does not manage this volume of pagination well). In this case, it is better to define intermediate ranges to "sub-divide" the report. It is the case for instance for the General Ledger (GLGRP) report that can be sub-divided by account. If the sub-division of a report has been defined in the parameter in question (a column exists for that purpose in the report dictionary), a right click gives access, via the Sub-division choice, to an intermediate range entry window. The result of the print request will therefore be a chain of several reports ranging from the start of the first intermediate range, the first intermediate range of the second, etc..... up to the end of range of the last.

  • Final value (field VALEUR2)

 

Report destination

This field defines the destination of the calculated report. The destination types are the following:

Preview

The flow generated in a format compatible with a display (text, PDF, RTF, Word...) is displayed in a window that opens on the user workstation. This print is formatted by Crystal Reports either on the user workstation, or via a print server.

Printer

In that case, Crystal Reports uses either a local printer, or a printer that can be accessed from a print server.

Message

Crystal Reports creates a file containing the message in a format such as PDF, text, RTF, Word. This message is used as the attachment of an email sent via the Workflow engine.

File

Crystal Reports creates a file containing the message in a format such as PDF, text, RTF, Word, which is stored on the disk.

ZPL printer

The flow is controlled by a specific formatting program associated with the report and defined by a dedicated setup. This flow can be sent directly on a local printer, on a printer accessible from the print server, or stored in a file.

Archiving

Crystal Reports creates a file containing the message in a format such as PDF, text, RTF, Word. This file is addressed to a EDM system for archiving, via the EDM standard connector.

  • Deferred (field IMPDIF)

This box is displayed only : it is checked if the printing has been requested in deferred mode via the corresponding button. It can be checked if the report is defined as being printable in deferred mode only.

Characteristics of departure

  • Output type (field IMPRIME)

This field defines the type of issue associated with the report. It can take the following values:

  • Preview in this case, a Crystal Reports window will open to display on the screen the print output. It is then possible to send it from the local workstation to a printer, or to a file with various formats.
  • Printer in this case, the entry of a printer network path will be required. This printer can be a Windows printer accessible over the local network from the current workstation, or a printer accessible from the print server. In the case where a local printer is used, the network name of the printer can be entered directly in the corresponding column, or the printer can be selected from the selection window (if this selection is not performed by the time the print is launched, the print window will open automatically). But it is also possible to use a print server accessible via the network (this supposes that a print server has been installed). In this case, the network name of the printer and the name or the server are required (in the form of a network server name, followed by a service number if it is not the same : It must be separated from the server by a colon. This will give, for example, a syntax of the type myserver.adonix :1802).
  • a message : in this case, it passes locally via Crystal Reports and by the MAPI interface to the default e-mail system of the user, in order to send a message with the report attached. The recipients of the e-mail, the format of the attachment and the text of the e-mail must then be entered. The possible formats are mentioned in a list defined by the local menu 91, and they include among others office formats (data processing and spreadsheet), generic formats ((HTML, ascii, PDF) and a format specific to Crystal Reports.
  • a file : A file is then created in an accessible directory on the network from the client workstation. The same format entry as before is required, then a name for the file to be created, in a directory that can be chosen from the normal Windows selection window.
  • the printer / file : this defines a print file. Usually created with the extension prn, these files are an exact image of the data sent to the printer, but stored on the hard disk (the format depends on the printer driver being used). This allows, for voluminous prints that will be outsourced, the sending of the file to be printed by the outsource supplier using the suitable driver. The printing of such a file can then be done directly using the Windows commandtypefile.prn>\\server\printer (if file.prnis the resulting file and \\server\printer is the network address of the printer). The name of the file to be created is entered in the file section that follows.
  • Server (field SERVEUR)

This field, assigned if the print is not started as preview, makes it possible to define the print server to be used to launch a report.

  • Printer (field IMPRIMANTE)

This field is used to define the network name of the printer to which the report is sent.

  • File (field FICHIER)

If the file path is not expressed in absolute terms, an attempt is made to generate the file in the C:\temp folder first, if it exists, otherwise in C:\, or else in the client installation directory if the server is not assigned. If the server is assigned, the file will be generated in the client installation directory.

Block number 5

  • Orientation (field PRTORIENT)

 

  • Copies (field NBRCPY)

In case of a printer output, enter a default value for the number of copies to be made.

  • Assembled copies (field ASSCPY)

If several copies are required and the check box Assembled copies is selected, the pages are assembled before the copy is printed. Otherwise, each page is repeated.

For instance, for the printing of two copies of three pages :

  • if this box is selected, the page order will be 1, 2, 3, 1, 2, 3.
  • if this box is not selected, the page order will be 1, 1, 2, 2, 3, 3.

Block number 6

  • Format (field FMTFIC)

It defines the possible formats via the local menu 91. These formats include among others office formats (data processing and spreadsheet), generic formats ((HTML, ascii, PDF) and a format specific to Crystal Reports.

  • Pages (field PAGDEB)

This is used to restrict the pages to be printed between two numbers (if no value is set, all the pages of the report are printed).

  • field PAGFIN

 

Block number 7

  • Paper size (field FORPAP)

 

When the report can be used in several languages, the language to be used is defined here.

Close

 

Other conditions

In the case of sub-divided prints :

  • *in preview, the preview screen will open as many times as there are print sub-divisions, the print window will open once the final sub-division preview window has opened.
  • in printing to file (choose Printer/file), the files are named from the name of the given file, followed by a consecutive number of 2 digits. For instance, if the file myfile.prn is defined, the generation will create the files myfile01.prn, myfile02.prn, …

The file help is active in print management. This makes it possible to call up a help defining what the report and the setup list are waiting for. It should be noted that this help exists only for certain reports (those where additional explications are considered necessary).

Batch task

This function can be run in batch mode, but no dedicated standard task is delivered to run it.

Specific Buttons

launches the print directly, either on the print server, or on the client workstation.

If the print is launched on the customer workstation, the icon representing a working print is then present at the bottom of the screen : a double-clic on this icon is used to open the print management window, which is lists the print in process, the number of records selected and read, etc. At this stage, it is possible to change the server of which the list of prints has to be viewed, delete a print, change the priorities and update the display. It should be noted that this window can also be opened from the general menu, via the choice File / Printer management
 

is used to save the setup values entered, by giving a name to the memo. Remembering that the memo STD, if it exists, is automatically recalled when a print is launched.

makes it possible to recall a memo by giving its code.

Allows the deletion of an existing memo.

The following fields are included on the window opened through this button :

Hourly constraints

This code defines the hourly constraints to be applied to restrict the launching dates and times of a print.

  • field HORDES

Title associated to the previous code.

Block number 2

  • Deferred print (field DIFFERE)

If this box is checked, a deferred print is requested.

  • Date (field DIFDAT)

This is used to define the date and time to start the print. A planning restriction (displayed in the Hourly constraints section) can prohibit the entry of some dates or times.

  • Time (field DIFTIM)

 

Close

allows the deferring of the print launch. This assumes that printing is always carried out on a print server printer. An additional entry window opens then to confirm that the print has indeed been deferred and to display the required additional setups.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

This task should be activated from the XXXX folder.

An attempt has been made to launch a batch print in a folder other than the current folder.

You do not have access to this report.

The report in question cannot be printed by the current user (for instance, because the report is protected by an access code).

You do not have access rights for this company.

The report in question manages access restrictions for certain companies or sites and, taking into account the setup values entered (for instance those of SOCDEB type - company range - or SITDEB - site range - that can be defined), no data can ever be printed.

You do not have rights for this group of sites

The report in question manages access restrictions for certain companies or sites and, taking into account the setup values entered (for instance those of SOCDEB type - company range - or SITDEB - site range - that can be defined), no data can ever be printed.

Warning! you do not have access rights for the sites XXX YYY.

The report in question manages access restrictions for certain companies or sites and, taking into account the setup values entered, the data for certain sites will not be printed. In this case, it is a warning message (because certain data can be printed all the same).

No preview in batch

An attempt has been made to launch in batch mode a preview of a report.

Server not defined

An attempt has been made to launch a print in batch mode without giving the print server name.

Report that cannot be directly carried out

The report requested can only be executed from within a series of programs (in general because a preliminary process is necessary). A check box defines this in the report dictionary.

Incorrect value

A non-conforming setup value has been entered.

Value too small

The second range value for an interval is inferior to the first

Other messages

It should be noted that other error messages linked to the entered setups can be displayed, for instance Incorrect period.

Tables used

SEEREFERTTO Refer to documentation Implementation