T24 FIELD FORMATS

All T24 applications have an associated record in the table

STANDARD.SELECTION. The record contains a list of all the field names and
associated properties.

The field is defined by:

Name
Type
Field No (Column Number)
Validation Program (For Input)
Conversion
Display Format
Alternate Index
Index File (Disabled)
Index Nulls (Include Nulls in Index?)
Single or Multi-value
Language Field (Is the field to be translated?)
Generated by T24 or Manual entry
System Conversion Type (unknown)
Related File

The most important properties are:

1. The Name is 35 character alphanumeric.

2. The Type specifies the usage if the Field No property and it is used by the enquiry
system to determine what type of selection is to be made. The values allowed are:

C - Concatfile containing list of keys to the main datafile. Note, wherever

possible build an ALTERNATE INDEX for the data field instead of using a
concatfile.

D - Data field on the record.

I – Indicates a dictionary I-type field. This is virtual field and can contain
infobasic code to lookup or calculate a value.

R - Info/Basic routine to perform the selection and return the list of keys. This
should only be used for NOFILE type Enquiries.

J - Field join specification. Allows selection to be performed on data in related

files - see SYS.FIELD.NO for specification syntax.

S - Selection prompt for enquiry. An item can be supplied which does not
refer to a true field in the enquiry and will not be used in the actual selection
of the file. These items can be referenced by enquiry selection routines or can
be used to pass constant information to an enquiry. Any item passesd to
enquiry in the selection criteria can be extracted and be processed as any other
field.

P - A pseudonym for an existing field. This type may be used if an existing

field name is amended, the previous name should be defined as type P, the
FIELD.NO should be set to the new name. This will then ensure that exsiting
enquiries and versions still recognize the old name. A pseudonym will assume
all the attributes of the field it is linked to in FIELD.NAME Note: All fields
specified as D or I will be created as field descriptors in the Dictionary file.

3. The Field No property contains either a field or column number or may contain a
routine or basic code as dictated by the type above.

4. The validation program used for validation of the field input. These are referred to
commonly with T24 as IN2 routines. The routine is specified as IN2xxxx where xxxx
is a valid IN2 suffix, i.e CUS, AMT etc. The remaining portion of the 'T' parameter
can be specified by using '&' as a field mark separator and a ']' as a value mark
separator.

Example: IN2AMT&- would allow the input of negative amounts.

5. Conversion may contain a standard jBASIC conversion. See the jBASIC manual
for details of OCONV formats that are permitted.

6. Display format contains the field length and alignment.

IN2 ROUTINES

Introduction
This section describes the standard 'IN2' sections and their use of other 'T' table
parameters. Field N refers to the field in the dynamic array stored in the T()
parameter.

Alphanumeric
IN2A

Allows alpha-numeric input. Only the following characters will be accepted:

'A...Z', 'a...z', '0...9', space or '!"#$%&'()*+,-./[\]:;<=>?@^'

IN2AA

Allows the same characters as IN2A but the first character of the input string must be
'A...Z' or 'a...z'.

IN2AAA

Allows input strings containing 'A...Z' or 'a...z' only.

IN2S

Allows input of SWIFT characters. Only the following characters will be accepted:
'A...Z', '0...9', space or '()' +, -, '.
This character is not allowed to be first '-’

IN2SS

Allows the same character, as IN2S, but the first character of the input string must be
'A...Z'.

IN2SSS

Allows input strings containing 'A...Z' only.

Amounts
IN2 (no suffix)

This routine handles one of three types of editing:

• Simple numeric input.
• Input within a specified range.
• Input matching a value in a specified table.

Figure 1 - IN2 Routine Table

IN2AMT

This routine accepts input of an amount and can edit the input to have the number of
decimal places defined for a specified currency. The currency can be defined directly
in the 'T' table element or implicitly by reference to the value in another field, multi-
value or sub-value in R.NEW. The reference to another field can be dynamically
linked with the respective multi-value and/or sub-value of an association of multi-
values and/or sub-values.

Input can be abbreviated by using 'T' and 'M' to express thousands and millions. Such
input will be expanded to the normal figure representation. The field will be
redisplayed using a mask inserting commas (or periods) at each thousand. Field 2 of
the 'T' table element defines the editing:

Figure 2 - IN2AMT Routine Table

IN2CCYDEC

This routine will accept a currency and an amount. The amount may have any
number of decimals up to the number defined in field 2,2 of the T table. The currency
must exist as a valid currency on the CURRENCY table.

Input can be abbreviated using 'H', 'T', 'M' and 'B' to express Hundreds, Thousands,
Millions and Billions. Such input will be expanded to normal figure representation.
If the number of decimal places is less than that of the currency then COM1 will be
formatted to the number of decimal places for that currency.

The field will be redisplayed with a space after the currency code and the numbers
with commas after each thousand.

Figure 3 - IN2CCYDEC Routine Table

IN2DEC

This routine will accept an amount figure with a maximum and minimum number of
decimal places defined in the 'T' table. Input may be abbreviated using 'H', 'T', 'M'
and 'B' to express Hundreds, Thousands, Millions or Billions. Such input will be
expanded to normal figure representation.

The field will be redisplayed using a mask inserting commas at each thousand.

Figure 4 - IN2DEC Routine Table

Dates
IN2D

Will accept input in any of several valid date formats. The date input will be
expanded to the full date YYYYMMDD and displayed as DD MMM YYYY. Dates
with two figure years will be assumed to be from 1950 to 2049 inclusive unless field 2
of the 'T' table element is set to '1000' when the date will be treated as prior to 1950.
Input must be in the format DD{MM{YY{YY{}}} or MM{DD{YY{YY}}}
depending on the date format set for the user, or may be in the internal eight numeric
format of YYYYMMDD.

If the month or year is not supplied, they will be defaulted to those of the current bank
date. The month may be input as the 3-character abbreviation defined for the language
of the user.

All dates will be converted to an internal format of YYYYMMDD (which is returned

in COMI).

IN2.ACCD

This routine will edit input, which is a combination of account number and date. See
IN2ACC and IN2D.

IN2.CCYD

This routine will edit input, which is a combination of currency and date. See
IN2CCY and IN2D.

IN2.D

This routine will edit input, which is a combination of numeric characters and date.
See IN2ACC and IN2.

IN2.YM

This routine is similar to IN2.D except that the date is in YYYYMM format. See
IN2ACC and IN2YM.

IN2FQU

This routine will accept a frequency consisting of a start date and a period code. The
date may be any valid date as for IN2D. If no date is entered, advancing the current
bank date to the next period date will generate a date.

The frequency code may be one of the following:

 Figure 5 - IN2FQU Frequency Codes

IN2YM

This routine handles date in the same way as IN2D except that days are not allowed.
The input is converted into YYYYMM internal format.

Tables
Account Numbers

IN2ACC

Input must be a valid account number, i.e. as defined by the account mask and check-
digit defined on the COMPANY record. Input of an account mnemonic will also be
accepted and converted to the account number.

IN2ALL

This routine will accept input of all types of account numbers. It combines the
functions of IN2ACC, IN2INT and IN2ANT.

IN2ANT

Input of an account number as for IN2ACC or of an internal account number will be

accepted.

IN2INT

The input must be a valid internal account number (6-12 alphanumeric characters).

Currency

IN2CCY

The input must be a valid ISO currency code. A numeric currency code will also be
accepted and will be converted to the ISO code.

Charges, Commissions and Tax

IN2CHG

Validates charge, commission or tax code. In order to obtain the relevant enrichment,
this routine should be called from within CHECK.FIELD. The enrichment is returned
in COMI.ENRI.

Field 2 of the 'T' table defines which of the tables to validate against:
 Figure 6 - IN2CHG Routine Table

These three values may be used in any combination separated by value marks, e.g. if
one wishes to validate against the CHARGE and TAX tables only then field 2 of the
'T' table would be 'CHG':VM:'TAX'.

Company

IN2COM

Input must be in valid company code format.

Customer

IN2CUS

Input must be a valid customer number, i.e. 1 - 10 numeric. Input of a customer

mnemonic will also be accepted and converted to the customer number.

Programs

IN2PG

This routine validates the program name input. If an abbreviated program name is
entered it is converted to its full program name and checked to ensure it is defined on
the PGM.FILE. This routine does not allow the input of program names set-up as
versions, i.e. program names that contain a ','.

IN2PV

This routine performs the same validation as IN2PG but allows input of program
names defined as versions.

IN2API

This IN2 routine allows the input to be:

1. A Subroutine - if it is defined in PGM.FILE as a S type program.

2. A Script – if it exists in SCRIPT.DESIGNER .
3. An Enquiry - if it exists in ENQUIRY .
4. And a Crystal Report - if it exists in REPORT.CONTROL .

Unless it is a Subroutine, input has to be both type and name of the api call i.e. Scripts
should be prefixed with SPT, Crystal reports with RPT and Enquiries with ENQ.

Type and name should be separated by a space.

E.g.: ENQ ENQ.SEL.FIELDS

Note: If the input needs to be restricted to Subroutine names only, then specify
T(Z)<2> = ‘SUB_ONLY’.

Rate
IN2R

This routine allows the input of up to 12 numeric characters with a maximum of 8

digits before the decimal place and a maximum of 6 decimal places. However if the
EXTENDED.PREC is turned on in the SPF table, SYSTEM record, this routine
allows the input of up to 15 numeric characters with a maximum of 8 digits before the
decimal place and a maximum of 9 decimal places.

Generic
IN2MNE

This routine edits the input to be a valid mnemonic string. The input may only
contain '0...9', 'A...Z' or '.'.

IN2ANY

Allows input of any character.

To find:
IN2.ALLACCVAL$$NOCHANGE

This is a variation on routines IN2PLANT and IN2.MCPLINT. IN2PLANT does not

handle the Mnemonic part e.g. USD100001001\BNK and IN2.MCPLINT does not
handle customer accounts.

IN2PLANT

Accepts input of an account number validated as per IN2ANT or a P&L Category

code in the format PLNNNN, where NNNN is in the range 50000 to 69999.

IN2.MCPLINT

Accepts input of internal accounts and P&L Category codes for multi-company
installations. P&L is in the format PLNNNN, where NNNN is in the range 50000 to
69999. The company mnemonic suffix will be checked as valid against the system
and the user’s profile.

IN2.CUST.BIC

Accepts valid customer number, customer mnemonic, a valid BIC code or free format
text.

IN2PLANT

Accepts input of an account number validated as per IN2ANT or a P&L Category

code in the format PLNNNN, where NNNN is in the range 50000 to 69999.

IN2SEC

Accepts valid Security Number or Mnemonic. Validates input against

SECURITY.MASTER table or alternate index if defined on the SC.PARAMETER
table, ALT.USER.INDEX field.

IN2NOMAMT

This extends IN2AMT allowing 6 decimal places rather than just 3. It can also accept
a Security Number to validate against SECURITY.MASTER and in turn return and
validate the trading units against the input. The currency ISO code validation has been
removed.

IN2PRICE

<define, based on user amount format and extended precision>

IN2BMT

<define, based on currency and amount>

IN2TIME

Accepts input of time and can validate for seconds, 12 or 24 hour with AM/PM suffix
if required. <S – seconds, H – 12 hour with AM/PM, HS – 12 hour with AM/PM and
seconds>

IN2SW

Extend SWIFT IN2S to allow for leading minus as part of SWIFT 97.

IN2SWI

Extend IN2SW to allow leading spaces in Customer and to permit & and /.

IN2DAO

Accepts and validates input against the table DEPT.ACCT.OFFICER.

ASCII TABLES
ASCII.VAL.TABLE

The ASCII.VAL.TABLE is used to define which ASCII characters may be used for
validation against any 'IN2' routine defined on the ASCII.VALUES table. The 'IN2'
routines are used to validate the entry to particular fields.
 Figure 4 – ASCII.VAL.TABLE record

The format of the ASCII.VAL.TABLE allows any combination of ranges or single

values of ASCII codes to be defined.

Care should be taken when modifying the values allowed by the system, particularly
when using SWIFT type fields, as this may cause unexpected results by allowing non-
standard characters to be entered.

ASCII.VALUES

The ASCII.VALUEStable is used to define ASCII value codes and ranges that may be
used by particular IN2 routines that validate entry to particular fields.
 Figure 5 – ASCII.VALUES record for IN2 routines

Standard tables are provided for each IN2 routine but there is also the provision for
user-definable tables at a language and application level. Therefore different tables
may be set up for particular languages and applications. The application level
definitions may be further subdivided into different tables for different languages.

See the relevant help text for ASCII.VAL.TABLE, which is where the actual ranges
and values are defined.