Академический Документы
Профессиональный Документы
Культура Документы
Report Generator
User Guide
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.
Table of Contents
Introduction .......................................................................................................................................... 3
Creating a Report - REPGEN.CREATE .............................................................................................. 4
Data file Selection and Output ......................................................................................................... 5
Sort order and Data output format ................................................................................................... 8
Replace data from another file ....................................................................................................... 10
Fixed headers................................................................................................................................. 11
Totals.............................................................................................................................................. 12
Data fields in headers..................................................................................................................... 13
Footer text ...................................................................................................................................... 14
Blank lines ...................................................................................................................................... 15
Decisions........................................................................................................................................ 16
Groups............................................................................................................................................ 17
Building the Executable - REPGEN.SOURCE .................................................................................. 19
Producing the Sort file - REPGEN.SORT .......................................................................................... 19
Producing the Report - REPGEN.OUTPUT....................................................................................... 21
Executing Reports in End-Of-Day (Batch) Process........................................................................... 23
Introduction
The Report Generator utility provides a mechanism for defining and producing ad-hoc reports, which
can be run on-line or within the Close of Business Batch process.
Initially when a new report is created or an existing report is being amended, stages 1, 2, 3 and 4 must
be executed in sequence. However, once the report has been defined and tested only stages 3 and 4
need to be executed.
The details defined here control features such as which data files are used for selection, the sort
sequence of the records, column positions and totals etc, as shown in the screenshot below.
The following sections briefly describe some of the main features and parameters that are used in
creating a report. More detailed explanation of the parameters and other advanced features can be
found in the HELPTEXT documentation.
READ.FILE
Defines the file to be selected e.g. ACCOUNT. This field is multi-valued to allow data to be extracted
and combined from multiple data files.
FL.FIELD.NO to FL.REL.NEXT
This associated set of fields defines the selection criteria to be used for the selection of data records
from the file. In the example, only those ACCOUNT records, which have a CUSTOMER number are
selected i.e. Customer accounts.
DEFINE.MNEMONIC to TEXT
This set of fields defines the data to be extracted and displayed. DEFINE.MNEMONIC associates an
alias or mnemonic name to the actual data record field number specified in field MNEMON.FIELD This
name can then be used to refer to the relevant field elsewhere in the definition i.e. when defining
decisions, calculations etc.
The field DISPLAY.TYPE controls how the field is to be displayed, i.e. every line, header, footer etc.
The example shown uses the value 2 to specify every line. If this field is blank, the data will not be
displayed.
The field COLUMN has been left blank so that the report generator will automatically space the columns
i.e. length of previous field plus one space character. If a column number is specified here then
manual calculations will have to be done to determine the exact column positions for the display of
data.
In the example the file is type 2 (numeric keys) and modulo 11 (11 * 2k=22k approx. size).
From the result of this calculation, determine the next nearest Prime Number and use this as the
modulo.
KEY.TYPE
This field defines the output sequence of the data field specified in MNEMON.FIELD including control of
totals and page breaks.
In the example a value of 1 specifies that this field will be used as part of the sort sequence.
If this is the only mnemonic in the whole report definition, which has a key.type of 1, then it will
become the primary sort key. A secondary sort key can be established by setting the key.type to 1 on
another mnemonic definition. The sort order will then be in the order in which the mnemonics have
been defined.
Note: a mnemonic that is used for sorting does not necessarily have to be displayed.
SPECIAL.MASK
Defines the output format for the data field i.e. Left, Right justification, special masks, date formatting
etc.
The example R###### shows that the customer number is to be right justified in a field width of 6
characters.
A special feature of this field is that if the name of a mnemonic, which is referencing a currency field, is
entered here, the report generator will format the data according to the number of decimals in the
currency table.
MODIFICATION
Defines special functions to be performed on the data. The REPLACE function used in the example
allows the retrieval of a data field from another file. The data field specified in MNEMON.FIELD must be
the record key to the other file.
MODIF.FILE
Specifies the name of the other data file from which the information is to be extracted from. In the
example this is the CUSTOMER file.
MODIF.FIELD
Defines which data field (number) is to be returned from the record extracted from the other file. In the
example this is field 2 (SHORT.NAME) from the CUSTOMER record.
Fixed headers
The screen shown below shows how column headers can be defined for the report. Up to 4 lines of
heading can be defined.
The header definition fields are divided into 40 character blocks e.g. HDR.1.001.040 represents line
header 1 character positions 1 to 40.
The field SPECIAL.HEADING controls whether the standard 3 lines of T24 headings are printed on the
top of each report page.
Setting this field to STANDARD specifies the printing of the standard header. If it is left blank then it
suppresses the printing of headings and end of group/report messages.
Totals
The screenshot below shows how totals can be defined in the report. The example totals the
working balance for all accounts and displays the total per currency.
DISPLAY.TYPE
Set to value 3 (line+total) for WBAL (working balance) mnemonic to display the data field on every line
and to keep running total.
If this is set to value 4 then the data field is not displayed but only totalled. The total will be displayed
in the total line.
KEY.TYPE
Set to value 2 (total by change) or 4 (total and paging by change) to produce a sub-total whenever the
value of the field changes.
In the example for CURR mnemonic it is set to 2 to produce a sub-total whenever the currency
changes. The sub-total is reset after display. A value of 4 has the same function except that it
performs a page break.
Note it is important to sort the output according to the field being displayed in the header.
KEY.TYPE
Set to value 1 (sequence control) to sort output according to this field e.g. currency.
DISPLAY.TYPE
Set to value 1 (header) instead of 2 (line) to display the currency as part of a header line.
Footer text
The screenshot below shows how text can be displayed as part of total lines. In the example the text
“TOTAL FOR” and the relevant currency is displayed as part of the sub-total for each currency.
DISPLAY.TYPE
Value set to 6 (Footer) for CURR.FTR mnemonic to display the data field defined in MNEMON.FIELD in
a total line only.
TEXT
Contains the fixed text that is to appear as part of the total line. In the screenshot above this is set to
“TOTAL FOR”
Also, note that the DISPLAY.TYPE on the WBAL mnemonic (working balance) is set to value 4 (total
only), i.e. this field is not displayed but only totalled. This has been used instead of display type 3 (line
and total) to prevent the footer text from being printed on the next line after the sub-total. Another
mnemonic is defined to print the working balance on every line.
Blank lines
Blank lines can be inserted in the report for headers, totals and detail lines by setting the following
fields to the appropriate values.
ADD.BLANK.LINE
ADD.TOT.BLANK.LINE
EMPTY.LINE.WANTED
Decisions
The screen shown below shows how decisions can be defined and used to control the conditional
printing of data. In the example the text “YES” is printed beside any working balance field, which has a
posting restriction defined on the ACCOUNT record i.e. field POSTING.RESTRICT on the ACCOUNT
record contains a numeric code.
DECISION.NAME to REL.NEXT.FD
This set of fields associates a name to the decision and defines the actual conditions, which will
evaluate to true or false.
In the example the name of the decision is POSTING.RESTRICTION and it compares the value of the
data field mnemonic POSTR to null (“”) i.e. the decision is true if POSTR is not equal to null. More
complicated decisions can be specified by expanding the sub-values and using the logical operators
AND/OR (in field REL.NEXT.FD) to group the conditions.
To print the text YES for only those Accounts, which have a posting restriction, the decision defined
above is linked to the mnemonic (DISP.YES), which prints the text via the following parameter fields.
MNEMON.FIELD to MODIF.FIELD
This is set to value FIELD.DECISION to indicate that this mnemonic (DISP.YES) will have the value
defined in field MNEMOM.FIELD (“YES”) if the associated decision specified in field MODIF.FIELD
(POSTING.RESTRICTION) is true.
Groups
The Group facility within the Report Generator allows a single report definition to be sub-divided into
sections. The sub-division is performed according to decisions linked to each group (section). In the
example shown below, the report on the ACCOUNT file is divided into two sections, Customer
Accounts and Internal Accounts.
GROUP
The number identifying the Group is set-up in fields GROUP.TITLE to MNEMON.SEQU. In the example
groups 1 and 2 have been defined.
GROUP.TITLE
Title to be printed at the beginning of the group.
GH1.001..040 to GH4.121..132
GROUP.DEC.NAME
Name of the decision that is to be used to control the selection of records, which will appear in the
group. In the example the first group is linked to the decision CUSTOMER.ACCT and the second
group is linked to INTERNAL.ACCT.
The field NEW.PAGE.FOR.GROUP can be used to force a page break when a new group starts. And
the field RESET.PAGE.NO allows the page numbering to be reset to one for the start of each group.
To create the source code, invoke the application REPGEN.SOURCE. This will prompt for the name
of the report and display the time of the last compile with a prompt to continue or not.
IMPORTANT NOTE:
If the report definition (REPGEN.CREATE) has been modified after the REPGEN.SORT and
REPGEN.OUTPUT stages have already been run, then to pick up the new changes you must logout
and log back in to T24 before running the REPGEN.SOURCE application. Otherwise, the old version
of the report will be executed.
The work file is only created on the first execution of the report, subsequent executions will clear the
work file prior to populating it with data records.
The application must be run in Verify mode, see for example of input screen.
The application must be run in ‘V’erify mode, see the screenshot below for an example of an input
screen.
For further details of creating BATCH processes see the System Administration guide on ‘Batch
Processing’.