Deal Slips

TEMENOS EDUCATION CENTRE

Warning: This document, is protected by copyright law and international treaties. 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 Unauthorized
reproduction
reproduc tion or distribution of this presentation
presentation or any portion of it, may result in severe civil and
criminal penalties,
Copyright
Copyri ght © 2004unde
penalties, and will be prosecuted to the maximum extent possible under
TEME
TEMENOS NOS HOLDINGS
HOLDINGS NV
r applicable law.”
Information in this document is subject to change without notice.

1
 Agenda

• What is a Deal Slip?

• St
Stag
ages
es du
duri
ring
ng wh
whic
ich
h a Dea
Deall Sli
Slip
p can
can be pr
prod
oduc
uced
ed..
• Deal Slip Flow
• De
Deal
al Sli
Slips
ps and
and the
the DE
DEAL
AL.S
.SLI
LIP.
P.FO
FORM
RMAT
AT App
Applilica
cati
tion
on
• Dea
eall Sli
Slip
ps an
and th
the ENQ
ENQUI
UIRY
RY Ap
Appl
plic
ica
ati
tio
on
What is a Deal Slip?

Confirmation slip that can be generated for any transaction in T24 at

any stage

Usually printed and handed over to the customer across the table
When can T24 produce a deal slip

Deal slips can be produced during the following stages

• I  –  Input
•  A  –  Authorise
• C  –  Copy
• R  –  Reverse
• D  –  Delete
• H  –  History Restore
• FINISH  –  this key word is application specific and might not work
for all applications, currently only TELLER uses this
Deal Slips using DEAL.SLIP.FORMAT Application

 Application’s VERSION

DEAL.SLIP.FORMAT

REPORT.CONTROL

DE.FORM.TYPE

PRINTER.ID
PRINTER.ID Application

The PRINTER.ID application is used to define valid printers on

the system. This application translates a logical printer name to
the actual physical printer defined at the Operating System level.
DE.FORM.TYPE Application

This table defines the width and depth of each printed form
(page layout). The printer to be used is also defined here.
REPORT.CONTROL Application
DEAL.SLIP.FORMAT Application

• Used to define the layout of the deal slip

• Similar to the ENQUIRY application
Example 1

When a new customer is created a deal slip in the following

format needs to be generated and printed and handed over to
the customer.
New Client form 1500
-----------------------

Client Name : ZAN TRADING CO.

Short Name : ZAN TRADING CO.
 Address : P.O.BOX 1456
RIYADH 11431
Sector Code : 3100 MANUFACTURING & PROCESSING
Industry : 100 COMMERCIAL
Target : 2 CORPORATE BANKING
Nationality: SA Saudi Arabia
Residence : SA Saudi Arabia
Geo Block: SAUDI
Status Code: 5 SPECIAL ATTENTION
Language : GB English
 Analysis

Most of the details are picked up from the CUSTOMER application, but
the value “GB” is the MNEMONIC field from the LANGUAGE
application. Similarly, GEOGRAPHIC.BLOCK (Geo Block) is a field in
the COUNTRY application. Thus information must be picked up from
three different application rather than one.
Solution 1

Defining the layout of the deal slip using the DEAL.SLIP.FORMAT

application.

CUSTOMER is the main file and the others

mentioned COUNTRY and LANGUAGE
have their Ids are a field in the CUSTOMER
file.
Solution 1 Contd.

Free text is entered within quotes.

5,3 and 5,4 represents column 5

in the 3rd and 4th lines

10R – a maximum of 10 characters

to be displayed and RIGHT
 justified

NAME.1 is a field in CUSTOMER

that needs to be displayed.
Solution 1 Contd.

Here the keyword ENRICHMENT

means that the field’s enrichment
is displayed rather than the value
of the field.
Solution 1 Contd.
Solution 1 Contd.

 Accessing fields from other

files (not the main file) Here
GEOGRAPHIC.BLOCK is a
field in the COUNTRY file.
Solution 1 Contd.

The user can either print the deal

slip when triggered or just choose to
send it to HOLD. If this prompt is
not entered, the deal slip is printed
without asking for the users
approval.
VERSION Application

Three fields in this application have to be set up as shown below.

D.SLIP.FORMAT
D.SLIP.FUNCTION
D.SLIP.TRIGGER
ENQUIRY Application

• Can be used to generate deal slips

• Used only on DESKTOP
• Unlike DEAL.SLIP.FORMAT, ENQUIRY can only access
information from the LIVE, NAU and HIS file and not from the
current transaction
Deal Slips using ENQUIRY Application

 Application’s VERSION

ENQUIRY

ENQUIRY.REPORT

REPORT.CONTROL

DE.FORM.TYPE

PRINTER.ID
Example 2

The bank wants a report of all customers belonging to particular SECTOR

in the following format when a customer record is authorised..

Customer Information

Customer No Mnemonic Short Name Nationality AC Officer Ind Sector 

Xxxxxx xxxxxxxxx xxxxxxxxxxxx xxxx xxxxxxxxx xxx xxxxxx

Xxxxxx xxxxxxxxx xxxxxxxxxxxx xxxx xxxxxxxxx xxx xxxxxx

Xxxxxx xxxxxxxxx xxxxxxxxxxxx xxxx xxxxxxxxx xxx xxxxxx

Solution 2 (Define the layout of the enquiry)

CUSTOMER is the file from which

data will be picked up and
displayed. User can select which
SECTOR to display.

CUS.NO is a user define name,

@ID is the actual field from
CUSTOMER. Data will be
displayed in the 3rd column. A
maximum of 10 characters, LEFT
 justified.
Solution 2
ENQUIRY.REPORT Application

 A valid ENQUIRY record

must be specified. If a
selection criteria is need
for the ENQUIRY that
can be specified here.

The REPORT.CONTROL id to be
used when the ENQUIRY is printed.
Changes to VERSION Application

Instead of a DEAL.SLIP.FORMAT record, the ENQUIRY record

must be specified in the D.SLIP.FORMAT field. The other two
fields can be set up the same way as when the
DEAL.SLIP.FORMAT application is used.

 A valid ENQUIRY record

must be specified here if
the ENQUIRY application
is used to print deal slips
 Additional Information – Setting up a HOTKEY

 A HOT KEY can be set up in the TERMINAL application. There

is a field called PRT HOTKEY. A single function key can be set
as the HOT KEY or a set of characters e.g. SLIP. If this is set up
and the user set the D.SLIP.TRIGGER to ‘RQ’, the user has to
manually trigger the printing of the deal slip by pressing the HOT
KEY. This facility works only on the DESKTOP (GUI mode).

The hotkey can be one key or a

set of keystrokes
Summary

• A deal slip can be produced using the DEAL.SLIP.FORMAT or the

ENQUIRY application.
• It must be attached to the VERSION record and a function/ trigger
can be set depending on when the user would like the deal slip to be
printed.
• A PRINTER.ID record must be attached to the DE.FORM.TYPE
record, which in turn is attached to the REPORT.CONTROL record
(if ENQUIRY application is used, an ENQUIRY.REPORT record
must be set up). The DEAL.SLIP.FORMAT record has the
REPORT.CONTROL id and thus printing is taken care via this set
up.
• All deal slips are stored in &HOLD& and a report of the deal slip
produced is held in HOLD.CONTROL