Open Financial Service (OFS)

OFS is a standard module within T24

Interactions with T24 is driven through OFS

OFS is message driven, it works on a
request-response based system

Native way to represent requests to execute T24 transactions, enquiries or routines

The OFS module provides the infrastructure necessary to process the OFS messages.

Type of OFS requests

Transaction Request
(create, modify or delete a record in any application in T24)

Enquiry Request
(queries data from T24)

OFS Message Format

Native OFS format - comma delimited

Browser XML - used by Temenos Browser

Transaction Request

Operation

APPLICATION NAME

Options

VERSION NAME / FUNCTION / PROCESS TYPE / GTS CONTROL VALUE / NO OF AUTHORISERS / OFS ACTION

User Information

SIGN-ON NAME / PASSWORD / COMPANY CODE

Transaction ID

Transaction id used for the record used in the transaction
May also contain an optional message id (Mandatory for A, D, S functions)

Message Data

Data required to create or update the transaction

Enquiry Request

ENQUIRY.SELECT

User Information

Enquiry Name

Must always be ENQUIRY.SELECT

SIGN-ON NAME / PASSWORD / COMPANY CODE

Name of the valid T24 enquiry that will run

Message Data

The message data portions of the enquiry message structure contains the selection criteria passed to the enquiry

Inter application calls

Synchronous - OFS.CALL.BULK.MANAGER

Asynchronous - OFS.POST.MESSAGE

Call a T24 API named OFS.POST.MESSAGE and pass it the OFS message.


This API is asynchronous, which means that your code or application cannot expect an instantaneous response. On a positive note your code or application need not wait for the OFS message to be executed either.

Call a T24 API named OFS.CALL.BULK.MANAGER and pass it the OFS message to update the other application.


This is a synchronous process, so therefore the routine or application that called OFS.CALL.BULK.MANAGER has to wait till it receives a response.

OFS Logging

Standard logging - like &COMO&

OFS.REQUEST.DETAIL (commonly called as ORD)

SPF [SYSTEM]

OFS.SOURCE [TRG.TELNET]

Log File Dir [MYLOG]

Log Detail Level

Maint Msg Dets - This can contain value Y or blank. Y indicates that the ORD has been activated.

Det Prefix - ORD is a common application used by all the OFS Source records to log information.

Int Log File [Yes]

Status

RECEIVED - message has been received by OFS but not processed nor validated

VALIDATED - message has been validated

PROCESSED - message has been processed

ERROR - message resulted in an error

None

Except

Full

Open

OFS Trigger Routines

Where

Trigger routines attached to OFS.SOURCE at specified trigger points

Who

Launched by core OFS routines during the life cycle of a message

What

Convert or map message format , update local application, populate queue

OFS.ONLINE.MANAGER

INITIAL.ROUTINE

IN.MSG.RTN

MSG.PRE.RTN

MSG.POST.RTN

OUT.MSG.RTN

CLOSE.ROUTINE

OFS.QUEUE.MANAGER

QUEUE.INIT.RTN

IN.DIR.RTN

IN.MSG.RTN

MSG.PRE.RTN

MSG.POST.RTN

OUT.MSG.RTN

QUEUE.CLOSE.RTN

OFS.BULK.MANAGER

IN.MSG.RTN

MSG.PRE.RTN

MSG.POST.RTN

OUT.MSG.RTN

The routine specified here will be executed just BEFORE a message is processed by OFS

Typically such a routine could convert or map the data received into the required OFS message format

Common variables will not be accessible to these routine

This routine is executed in both the batch and telnet modes

The routine specified here will be executed AFTER each message has been processed but prior to sending back to it’s origin.

This helps convert the message from OFS to external format

The Common variables not available

This routine is also common to batch and telnet modes

This routine is called by the OFS.REQUEST.MANAGER just prior to the message been processed but after the IN.MSG.RTN has been triggered

The Common variables are available at this stage

This routine does not allow you to alter the message

It is typically used to update local applications

This routine is called by the OFS.REQUEST.MANAGER just AFTER the message been processed but before the OUT.MSG.RTN is called

The Common variables are available at this stage

This routine does not allow you to alter the message

It is typically used to update local applications

This routine is executed when the input directory defined in IN.QUEUE.DIR is empty, i.e. there are no messages to process.

Typically such a routine could be used to populate the input directory with OFS messages derived from a third party source.

This routine is triggered when the Queue Manager service is started

This routine is triggered when the Queue Manager service is closed

OFS XML REPORT

  1. ENQUIRY.REPORT
  1. ENQUIRY
  1. REPORT.CONTROL
  1. DE.FORM.TYPE
  1. PRINTER.ID
  1. A non-hashed file
  1. REPORT.TRANSFORM