top of page
Search

Writing and Testing OFS Strings in Temenos T24

Writer: Josef Mayrhofer
Josef Mayrhofer
1 day ago
3 min read

Open Financial Services (OFS) is the language T24 uses to communicate with itself and the outside world. You can send a transaction in the OFS format to T24 and receive the response in the same standardized OFS format. In this blog, we will explore how to create an OFS string and test the posting of a transaction.


OFS Transaction Request Format


To perform the write action in the T24 Database, we use a transaction request. Examples include creating a new CUSTOMER, editing existing customer fields, and making payments. All these actions change the T24 DB.  We can use the format to post any transaction. VERSION.NAME/FUNCTION/PROCESS.TYPE/GTS/NO.OF.AUTH,T24SIGNONNAME/PASSWORD,RECORD.ID,MESSAGE.DATA


  • VERSION.NAME: This is the instance of the Application name, like CUSTOMER, ACCOUNT, for which we are creating a record


  • FUNCTION: Functions in OFS indicate values like INPUT(I), Verify(V), Authorise(A), Reverse(R), Delete(D).


  • PROCESS.TYPE: The value is either PROCESS for all functions or VALIDATE for validating the data record's correctness and checking for issues.


  • GTS: This is for overrides and error checks. The value passed in the OFS string takes precedence over the value in the version.


Value

Operation

Null

Error - reject the record 

Override – approve automatically 

1

Error – INAU file with status HOLD

Override – approve automatically 

2

Error - reject the record  

Override – INAU file with status HOLD

3

Error - INAU file with status HOLD Override – INAU file with status HOLD

4

Write all transactions into the INAU file

with status HOLD


  • NO.OF.AUTH: Indicates the number of authorizers required for this transaction. Usually, for all financial transactions, the value will be 1 or more.


  • T24SIGNONNAME/PASSWORD: Valid T24 User and Password for the transaction


  • RECORD.ID : Application record ID for which we are modifying; for newly creating records, this will be blank and auto-created when the transaction is posted


  • MESSAGE.DATA: Contains T24 Field names and values we are passing.


Testing the OFS Transaction Request


There are multiple ways to test an OFS string. For example, we can use IRIS, SOAP, Classic, or any other interface. No matter the option, the OFS String format remains the same.


We can execute tRun tSS GCS: This opens the path to post the OFS. We simply need to enter the OFS string we formed.


Below is an example of posting a new customer creation:


Request:


CUSTOMER,INP/I/PROCESS/0/0,INPUTT/123456,,NAME.1=ANYNAME,CATEGORY=1001:1:1,ACCOUNT.TITLE.1=NEWACCOUNT:1:1,SHORT.TITLE=NEWYORK:1:1,POSITION.TYPE=TR:1:1,CURRENCY=USD:1:1,CURRENCY.MARKET=1:1:1,ACCOUNT.OFFICER=1:1:1,

(All the mandatory fields in the same way)


Response:


100300//1,NAME.1=ANYNAME,CATEGORY=1001:1:1,ACCOUNT.TITLE.1=NEW ACCOUNT:1:1,SHORT.TITLE=NEWYORK:1:1,POSITION.TYPE=TR:1:1,CURRENCY=USD:1:1,CURRENCY.MARKET=1:1:1,ACCOUNT.OFFICER=1:1:1,

(All the fields), Audit fields


The first field indicates the newly created record ID; the second is for a unique transaction identifier. If we pass any unique ID in the OFS Request, it will appear here. The third field indicates the success indicator, followed by complete record details and an audit field.


Value

Indicator

 1

SUCCESS

-1

FAILURE, check details in ORD

-2

OVERRIDE, check details in ORD

-3

T24 is offline


OFS.REQUEST.DETAIL (ORD) is the application where we can track all the OFS records. This needs to be enabled in OFS.SOURCE. The ORD will contain the Msg In field, which stores the OFS REQUEST, and the Msg Out field, which stores the RESPONSE. It has the Application and status fields that stores if the transaction is validated or an error. We can easily track all our OFS requests here.


Enquiry Request OFS Format


In order to perform the read action from the T24 Database, we use an enquiry request. Like fetching the account balance and customer data. All these actions read the T24 DB.  We can use the format to get details from T24 via Enquiries.


 ENQUIRY.SELECT, T24SIGNONNAME/PASSWORD,ENQUIRY.NAME,SELECTION.CRITERIA


  • This is the fixed keyword that we need to use for the Enquiry Request


T24SIGNONNAME/PASSWORD:

  • Valid T24 User and Password for the enquiry


ENQUIRY.NAME,SELECTION.CRITERIA:

  • We need to provide Enquiry Name, fields, and its values for filtering


Testing the Enquiry Request

We can execute tRun tSS GCS and the OFS string we formed. This is a similar procedure to that of a transaction request.


 ENQUIRY.SELECT,,INPUTT/654321,%CUSTOMER, CUSTOMER.NO:EQ=100300

  • This gives the response


HEADER DETAILS: CUSTOMER FIELD NAMES, FIELD LABELS: CUSTOMER FIELD VALUES


Once we test a single OFS string, we can use the same with different data for all the other OFS postings.


If you are looking for T24 OFS-related testing or training requirements, feel free to contact us at Performetriks today. Our experts would be happy to assist you along your journey.

Happy Performance Engineering!

Comments

bottom of page