OFS is a standard module within T24

Transaction Request
(create, modify or delete a record in any application in T24)
Interactions with T24 is driven through OFS
Type of OFS requests
Enquiry Request
Open Financial Service (OFS) OFS is message driven, it works on a (queries data from T24)
request-response based system

Native way to represent requests to execute T24

transactions, enquiries or routines Native OFS format - comma delimited

OFS Message Format

The OFS module provides the infrastructure Browser XML - used by Temenos Browser
necessary to process the OFS messages.

Operation APPLICATION NAME

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

User Information SIGN-ON NAME / PASSWORD / COMPANY CODE

Transaction id used for the record used in the transaction

Transaction ID May also contain an optional message id (Mandatory for A, D, S
functions)

Message Data Data required to create or update the transaction

ENQUIRY.SELECT Must always be ENQUIRY.SELECT

Enquiry Request
User Information SIGN-ON NAME / PASSWORD / COMPANY CODE

Enquiry Name Name of the valid T24 enquiry that will run

The message data portions of the enquiry message

Message Data structure contains the selection criteria passed to
the enquiry

Call a T24 API named OFS.CALL.BULK.MANAGER and pass it the OFS message to update the other application.
Synchronous - OFS.CALL.BULK.MANAGER
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.

Inter application calls

Call a T24 API named OFS.POST.MESSAGE and pass it the OFS message.
Asynchronous - OFS.POST.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.

SPF [SYSTEM] Int Log File [Yes]

Standard logging - like &COMO& None

Log File Dir [MYLOG] Except

OFS.SOURCE [TRG.TELNET]
OFS Logging Full
Log Detail Level
Open

OFS.REQUEST.DETAIL Maint Msg Dets - This can contain value Y or blank. Y indicates that the ORD has been activated.
(commonly called as ORD)

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

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

Where
Trigger routines attached to OFS.SOURCE at specified trigger points

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

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

What

INITIAL.ROUTINE 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
OFS.ONLINE.MANAGER IN.MSG.RTN
Common variables will not be accessible to these routine

This routine is executed in both the batch and telnet modes

MSG.PRE.RTN

MSG.POST.RTN

The routine specified here will be executed AFTER each message has been processed but prior to sending back to it’s origin.
OUT.MSG.RTN
This helps convert the message from OFS to external format

The Common variables not available

CLOSE.ROUTINE
This routine is also common to batch and telnet modes

QUEUE.INIT.RTN
This routine is triggered when the Queue Manager service is started

This routine is executed when the input directory defined in IN.QUEUE.DIR is empty ,
i.e. there are no messages to process.
OFS.QUEUE.MANAGER
IN.DIR.RTN Typically such a routine could be used to populate the input directory with OFS
IN.MSG.RTN messages derived from a third party source.

MSG.PRE.RTN

MSG.POST.RTN

OUT.MSG.RTN

This routine is triggered when the Queue Manager service is closed

QUEUE.CLOSE.RTN

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

IN.MSG.RTN
The Common variables are available at this stage

OFS.BULK.MANAGER This routine does not allow you to alter the message
MSG.PRE.RTN 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 calle
MSG.POST.RTN
The Common variables are available at this stage

OUT.MSG.RTN
This routine does not allow you to alter the message

It is typically used to update local applications

1. ENQUIRY.REPORT

2. ENQUIRY

OFS XML REPORT 3. REPORT.CONTROL

4. DE.FORM.TYPE

5. PRINTER.ID

6. A non-hashed file

7. REPORT.TRANSFORM