Open Financial Service

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 HEADQUARTERS SA Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent possible under applicable law.” Information in this
document is subject to change without notice
Programme Objectives

At the end of the programme you should be able to

▪ State the need for OFS

▪ List the different OFS modes and context in which they are used
▪ Describe the OFS message syntax
▪ Create OFS requests

Slide 3
Session 1- Objectives

At the end of this session you should be able to

▪ Appreciate the need for OFS

▪ Describe the message syntax for commonly used OFS messages
▪ Write OFS requests

Slide 4
What is OFS?

▪ Module in T24
▪ Only standard gateway to T24
▪ Every single interaction with T24 is driven through OFS.
▪ Works based on a request – response based system
▪ Enables III party systems to post requests and obtain responses

Slide 5
What is the need for OFS?

Data ware house

T24

Swift interface
OFS

ATM

T24 Browser

Slide 6
Message Syntax

▪ Transaction Request
▪ Enquiry Request

Slide 7
OFS Message Formats

▪ Native OFS format

▪ XML format

Slide 8
Transaction Request - Sample

ACCOUNT,SAMPLE/I/PROCESS//2,
INPUTT/123456,34567,CUSTOMER=100724,CATEGORY=1001,CURRENCY=USD

▪ Request specifies application, function, fields and values

▪ Should contain values for all mandatory fields.
▪ OFS transaction requests cannot be used to update live files (similar to
user input).
▪ Simple comma delimited format
▪ Some message parts further subdivided using slashes

Slide 9
Syntax diagram explained

ENQUIRY. User Enquiry Message

, , , ,
SELECT Information Name Data

Message portion Message Repetition

delimters

Slide 10
Transaction Request - Message Syntax

Operation Options User Transaction Message

, , , ,
Information ID Data

▪ Operation
▪ Contains the name of APPLICATION.
▪ Example: ACCOUNT.
▪ Options
▪ Comprises of VERSION-NAME/FUNCTION/PROCESS TYPE
/ GTS.CONTROL value/NO.OF.AUTHORISERS.
▪ Example : TRG/I/VALIDATE//2
▪ User Information
▪ Comprises of SignOnName/Password/Company code
▪ E.g INPUTT/123456/GB0010001

Slide 11 11
Transaction Request - Message Syntax cont…

Operation Options User Transaction Message

, , , ,
Information ID Data

▪ Transaction ID
▪ Contains transaction id of the record used in the transaction.
▪ Eg: 20548
▪ Mandatory for See , Authorize , Delete & Print functions.
▪ May also contain an optional message id.
Eg: 20548/20081010001
▪ Message Data
▪ Contains the data required to create or update the transaction.
▪ Eg: CUSTOMER=100297,CATEGORY=1001,CURRENCY=USD
▪ Eg: CUSTOMER :1:1=100297

Slide 12 12
Transaction Request - Examples

Request to Input
ACCOUNT,/I/PROCESS,
INPUTT/123456,34567,CUSTOMER=100724,CATEGORY=1001,CURRENCY=USD

Request to Authorise
ACCOUNT,/A,INPUTT/123456,34567

Slide 13
Workshop 1.1

▪ Write a OFS message to input a SECTOR record with id 1200

▪ Write a OFS message to authorise this SECTOR.

▪ Write a OFS message to input a new ABBREVIATION called UL for listing the
USER records.

▪ Write a OFS message to input a CUSTOMER record in T24. Use zero

authorisers in your message

Slide 14 14
ENQUIRY REQUEST

Slide 16
Enquiry request – Message Syntax

ENQUIRY. User Enquiry Message

, , , ,
SELECT Information Name Data

Slide 17 17
Enquiry request – Message Syntax cont…

ENQUIRY. User Enquiry Message

, , , ,
SELECT Information Name Data

▪ ENQUIRY.SELECT
▪ Must always be ENQUIRY.SELECT.
▪ Name of the application that is used to run queries and return the data.
▪ USER INFORMATION
▪ Same as that in the transaction type request.
▪ ENQUIRY.NAME
▪ Name of the T24 Enquiry that will be run.
▪ Must be a valid TEMENOS T24 enquiry (i.e. must be found in the ENQUIRY
application of TEMENOS T24).

Slide 18 18
Enquiry request – Message Syntax cont…

ENQUIRY. User Enquiry Message

, , , ,
SELECT Information Name Data

▪ MESSAGE DATA
▪ The message data portion of the enquiry message structure contains the
selection criteria passed to the enquiry.
▪ The message data portion of the message can be repeated for each
selection criteria separated by a comma (,).
▪ This is optional depending on the Enquiry

Slide 19 19
Enquiry Request - Examples

Without criteria i.e. message data portion

ENQUIRY.SELECT,,INPUTT/654321,%ACCOUNT

With criteria
ENQUIRY.SELECT,,INPUTT/654321,%ACCOUNT,
ACCOUNT.NUMBER:EQ=11109

Slide 20 20
Workshop 1.2 – Enquiry Type Messages

▪ Write an Enquiry type request to find the list of INDUSTRY records

found in yourT24 area

▪ Write an Enquiry type request to find the current day’s balance

summary of an ACCOUNT (say for example 29987). (TIP: Use the
enquiry ACCT.BAL.TODAY)

Slide 21 21
Quiz – State True or False

▪ OFS ‘understands’ messages in the OFS format only

▪ You can use comma versions in a message
▪ You cannot use zero authorised versions in a message
▪ You must specify the transaction id in a message that authorises a
transaction
▪ OFS message to run an enquiry starts with ENQUIRY
▪ You may specify the dynamic selection criteria for an enquiry in the
message data

Slide 23
Important Points

▪ Common OFS message types

▪ Transaction message
▪ Enquiry message
▪ Transaction message parts
▪ Operation
▪ Options
▪ User information
▪ Transaction Id
▪ Message Data
▪ You cannot use comma versions in a OFS request
▪ Enquiry request
▪ Always starts with ENQUIRY.SELECT
▪ Does not contain options
▪ May pass criteria also

Slide 25
Summary

You should now be able to

▪ Appreciate the need for OFS

▪ Describe the message syntax for commonly used OFS messages
▪ Write OFS requests

Slide 26