T24 Enquiries – R14 H-1

T24 Enquiries – R14 H-2

 Reports are a crucial aspect of any business for analysis and future business
predictions

ENQUIRY is a T24 application which allows you to create user defined reports that
fetch and display data as per the requirements of the user.

An enquiry is a query that is executed to fetch data from the database and display the
results in a user defined format

T24 Enquiries – R14 H-3

 T24 is made up of different applications like CUSTOMER , ACCOUNT ,
FUNDS.TRANSFER etc. An application validates and stores the data that is input.

To view data from an application , you can do a LIST (L) of all the records. You can also
view a particular record, if you know the record ID using the SEE (S) function. The
LONG LIST (L L) function display all the fields from STANDARD.SELECTION. User can
retrieve required records by entering a SELECTION criteria

However you may use the ENQUIRY application to create reports in user defined
formats

T24 Enquiries – R14 H-4

 ENQ is the command to launch an enquiry. It internally executes ENQUIRY.SELECT
which provides the user with a Selection Criterion Screen. Based on the selection
criterion specified dynamically by the user in the Selection Criterion Screen, the
enquiry fetches the desired records which match the condition (as shown in snapshot
2)

System defined enquiries start with a %, or have a “–”

Eg: %CUSTOMER, %ACCOUNT, %FUNDS.TRANSFER, %LD.LOANS.AND.DEPOSITS,
CURRENCY-LIST, CATEGORY-LIST.
These enquiries should not be amended.

T24 Enquiries – R14 H-5

T24 Enquiries – R14 H-6
T24 Enquiries – R14 H-7
 This task teaches you to create a simple enquiry. The requirement for the task
is as follows,

The enquiry is based on the CUSTOMER application . The fields to be part of

your enquiry are - @ID, MNEMONIC, SECTOR, NATIONALITY and RESIDENCE .

Note: When discussing the use of fields in the ENQUIRY application, only
RELEVANT fields are discussed and displayed in the screenshots.

T24 Enquiries – R14 H-8

 To create an enquiry in T24, create a record in the ENQUIRY application. The ID for
your enquiry can be any meaningful alphanumeric text. The only special character
allowed is ‘.’

Before designing an enquiry, decide on the page layout. Does your report have a
header? How many lines can be displayed per page of the report? The first field
PAGE.SIZE allows you to do this. Specify the number of lines for the header and
number of lines for the body of the report separated by a comma. In this example
four lines are allocated for the header and twenty lines are allocated for the report.

Enquiries are created to query and fetch data from tables. Specify the
table/application to be queried in the field FILE.NAME. In the example the enquiry is
created for the CUSTOMER application.

T24 Enquiries – R14 H-9

 Specify the Header Information as shown.

HEADER – Give the heading to be displayed with (Colum,Row) number. Multiple

headings should be specified as sub-values of HEADER not multi-values. Multi-values
are used for headings in a foreign language.

T24 Enquiries – R14 H-10

 Each column in the report is a field from the application (i.e., table).

Specify the position where the field will be displayed. The first field @ID is displayed
in column one. If COLUMN is left blank, the column will not be displayed as part of
the report.

Note: Columns must always be specified in the correct order, meaning from left to
right. The ENQUIRY application cannot display the output correctly if the columns are
all mixed up.

FIELD.NAME is an associated multi value set. Multi-value the field FIELD.NAME to

specify the other fields.

Value for the LENGTH.MASK field is defaulted by T24. You can adjust the length and
justification of the field using the LENGTH.MASK field . Also the value in the field
SINGLE.MULTI is defaulted by T24 depending on the nature of the field. This field can
hold the value S or M.

T24 Enquiries – R14 H-11

 Execute the enquiry to view the output. Use the command ENQ followed by the enquiry
(name) ID in the command line. ENQ is the abbreviation for ENQUIRY.SELECT application.
Data from the fields given in the enquiry will be displayed in columns for all the records in the
application
You may also specify conditions at runtime in an enquiry. Based on the values given by the
user, the enquiry will filter the records and only fetch those which satisfy the condition Eg –
Display data only for customers belonging to Sector 1001
When you execute the enquiry, a Dynamic Selection Criteria box appears. This allows you to
specify run time selection criteria on any field of the application the enquiry is based on. You
may specify one or more condition in the selection criteria box to filter out specific records
from the application. The format of the criteria is <Fieldname> <Logical Operand> <Value>.
Multiple conditions are combined using AND . Then click on the Find button to execute your
enquiry.

You will see that you can specify a selection criteria on any field of the CUSTOMER application
(STANDARD.SELECTION)
Another way of specifying the selection criteria at runtime is while executing the enquiry
itself. ENQ CUST.ADDRESS.ENQ SECTOR EQ 1001. Here the selection criteria is appended
along with the execution request. You can use the following command to use the last
specified condition, ENQ CUST.ADDRESS.ENQ LAST. The keyword word “LAST” instructs the
system to use the last selection criteria used. Note: The Selection criteria is cached by T24 in
the file F.ENQUIRY.SELECT.
The enquiry result may consist of more than one page of results depending upon the number

T24 Enquiries – R14 H-12

 of records selected and the page size of the enquiry. You can use the Previous Page and the Next Page
buttons to navigate between the pages.

T24 Enquiries – R14 H-12

 To display user defined headings

FIELD.LBL - Header for a field is specified in FIELD.LBL . Header for the @ID field is
specified in FIELD.LBL as ‘Customer Code’ . If this field is left blank, value in
FIELD.NAME field will be defaulted.

Authorise your enquiry record and execute to view the results. Ensure that you
specify COLUMN value for all the fields.

T24 Enquiries – R14 H-13

T24 Enquiries – R14 H-14
 This task teaches you to specify fixed selections and dynamic selection criteria
in enquiries. Consider a scenario where a bank decides to provide an offer for
the US customers who belong to a particular SECTOR .The SECTOR is specified
at run time. How will you create an enquiry for the given requirement?

T24 Enquiries – R14 H-15

 You need to design a report which only displays information of customers whose
nationality is US. Since this requirement is fixed, specify it in FIXED.SELECTION field.
More than one fixed condition can be specified, if required. A logical AND is
performed between the multiple conditions. The condition specified in fixed
selection will be executed first and always before dynamic selection. It first filters
records with nationality equal to US, and then applies the dynamic conditions
specified at runtime on these filtered records. User cannot modify the fixed condition
during execution.

The format of FIXED.SELECTION is FIELD.NAME <space>operand <space> value. The

required condition for this example is ‘NATIONALITY EQ US', where NATIONALITY is a
field name and EQ is the operand. The fixed selections are always executed first,
before the dynamic run time selection criteria that is entered.

To make SECTOR as a mandatory dynamic selection criteria input, use the field
SELECTION.FLDS. To change the label of the field that is displayed in the dynamic
selection criteria, use SEL.LABEL. This multi-value set also allows you to restrict the
operands displayed in the dynamic selection criteria using the SEL.FLD.OPER
(Selection Field Operand). Multiple operands can be provided in this field ,delimited
by space. Set the field REQUIRED.SEL to Y to make the field mandatory at runtime.
The enquiry cannot be executed till a value is provided for SECTOR in the dynamic
selection criteria box.

You will notice that only the specified fields are displayed during run-time in the

T24 Enquiries – R14 H-16

 dynamic selection criteria box ( and all the fields from STANDARD.SELECTION are not displayed)

T24 Enquiries – R14 H-16

 Usage of brackets to OR conditions in ENQUIRY. By default all the conditions that are
given in the selection box are AND conditions. To give an OR condition use the open
bracket facility in the enquiry

T24 Enquiries – R14 H-17

 You may often need to specify multiple conditions in the enquiry that you create. How
do you link these conditions together? The multiple conditions can be grouped using
the relational operators , ‘AND’ or ‘OR’.

The dynamic conditions of your enquiry NATIONALITY is US or RESIDENCE is PA

How do you join the two dynamic conditions? This is specified in the field called
REL.NEXT.FIELD. The REL.NEXT.FIELD provides two options namely AND , OR. Dynamic
Selection Fields form a multi value set. By default all the dynamic selection conditions
work with the AND operator. However you may also use the OR operand to group the
dynamic selection conditions.
Specify the other required fields and authorise the enquiry record.
Output
1. When you launch the enquiry, a Selection Criteria box is displayed. User can enter
values for RESIDENCE and NATIONALITY at run time. Enter the values for these
fields and execute the enquiry to view the output.
2. You can see the sample output of your enquiry. Customer 100329 is displayed in
output although nationality is not US because the residence is PA

T24 Enquiries – R14 H-18

T24 Enquiries – R14 H-19
 To sort records in the descending order of their MNEMONIC, USE the field
FIXED.SORT field in the ENQUIRY application

FIXED.SORT- This field is used to specify fixed sorts for enquiry. Specify the name of
the field that has to be sorted. By default the system sorts in ascending order. To sort
the records in descending order specify DSND along with the field name.

Authorise the enquiry and execute.

Note More than one value for SECTOR can be specified using a single fixed selection
condition. When more than one value is specified for the same field, T24, performs a
logical OR between the values

Also, the relational operator between the fields NATIONALITY and RESIDENCE is AND.
The AND operator is applied by default hence there is no need to use the
OPEN.BRACKET field and REL.NEXT.FIELD

T24 Enquiries – R14 H-20

 Specify the LENGTH.MASK for WORKING.BALANCE as 19R,2 (to display
WORKING.BALANCE with two decimal places)

T24 Enquiries – R14 H-21

T24 Enquiries – R14 H-22
T24 Enquiries – R14 H-23
 The following is a USER specific EB.SELECTION.FAVOURITES record with the ID
defined in the format ENQUIRY*USER.ID, where ENQUIRY is a valid T24 enquiry.

Specify the required selection criteria and the Name for your favourite in this record.
In the above illustration (SECTOR 2001 GBP) and (SECTOR 3503 GBP) are the 2
named favourites.

T24 Enquiries – R14 H-24

 The user can also create favourites when an ENQUIRY is launched.

Launch the CUST.ADDRESS.ENQ. Enter the desired Industry into the Industry drop
down.

Click on the ‘Add Favourite’ image. Enter a Label in the prompt (eg Health Care
Industry)

Click OK. The new favourite reflects on the screen.

T24 Enquiries – R14 H-25

 A system wide favourite can be created with Record ID as valid T24 Enquiry Name
without attaching a USER id to it. Eg. ACCT.BAL.TODAY.
Now what is the difference between a User specific favaourite and a system wide
favourite ?

The system wide favourite is available for all T24 users who launch that specific
enquiry whereas a User specific favourite appears only for that specific user and not
for others.

In the above screenshot when AUTHORISER launches the ACCT.BAL.TODAY enquiry

both the system wide as well as the user specific favourite are displayed

A user specific favourite can be deleted by clicking on the favourite image shown with
a (-) sign. A system wide favourite cannot be deleted by a normal user.

T24 Enquiries – R14 H-26

 Can you view the details of a customer from an enquiry based on the ACCOUNT
application?

The user should be given a link to drilldown to the customer information. This link
should be specified in the enquiry that is based on the ACCOUNT application.

In T24 you can navigate from one enquiry to another

The process of linking two or more enquiries is known as drilldowns

T24 Enquiries – R14 H-27

T24 Enquiries – R14 H-28
 The parent Enquiry is based on the ACCOUNT application. Specify the field name &
field value for the fields - @ID,CUSTOMER.NO,CATEGORY,CURRENCY &
WORKING.BALANCE.

Note : The field name of the CUSTOMER field is ACCUST.NO

T24 Enquiries – R14 H-29

 Next you will create the child enquiry which is for CUSTOMER application. Specify the
following fields –@ID, MNEMONIC,SHORT.NAME & NATIONALITY. Ensure that you
specify the value for COLUMN field. Authorize the child Enquiry.

T24 Enquiries – R14 H-30

 You have now created the parent enquiry and the child enquiry. Now you will learn
how to invoke the child enquiry from the parent enquiry. Amend the parent enquiry
as stated .To enable drilldown feature use the field ENQUIRY.NAME .

ENQUIRY.NAME – Specify the ID of the child Enquiry that has to be invoked.

SEL.CRIT – The specific customer record is chosen based on the customer id in the
parent enquiry. The customer id acts as a link between these two enquiries. The
FIELD.NAME for Customer ID field is ACCUST.NO . The Customer ID is passed from
the parent enquiry to the child enquiry. The criteria is @ID EQ ACCUST.NO, where
@ID is the field in child enquiry and ACCUST.NO is the CUSTOMER field defined in this
parent enquiry. Hence, the child enquiry will be invoked with the criteria, @ID EQ the
value for Customer ID available in the parent enquiry.

LABEL.FIELD- Here you will specify the field which is used to invoke the child enquiry.
The field ACCUST.NO is the field name for CUSTOMER.NO field. The value two(2) is
defaulted by T24. It denotes the column position of the field in this Enquiry.

NEXT.DESC – Specify the hyperlink to invoke the child Enquiry. Authorize the Enquiry.

T24 Enquiries – R14 H-31

 When you launch the parent enquiry, you will see the output looks different. The
account details are displayed in each row but at the end of every row there is a
hyperlink. Use the link to launch the child enquiry.

The child enquiry displays the specific customer as the value of the field ACCUST.NO
is passed from the parent enquiry to the child enquiry.

T24 Enquiries – R14 H-32

 You can link enquiries using the drill down facility. Can you link an enquiry to a
version? For example, if a bank clerk is looking at an enquiry output based on the
CUSTOMER application, he must be able to click on a hyperlink that allows him to
create an ACCOUNT record for a particular customer. This is known as Context Based
Workflow in T24.You can also invoke versions from your enquiry. This section teaches
you how to create Context Based Workflows.

The requirement of the task is as follows:

1. Create an Enquiry based on the CUSTOMER application and display the following
fields @ID, and SHORT.NAME.

2. Create a version based on the ACCOUNT application and display the following
fields CUSTOMER, CATEGORY, MNEMONIC, CURRENCY & ACCOUNT.TITLE.

3. Using this Enquiry invoke a Version that creates an Account. The Customer Number
and Short Name must be defaulted into the version

T24 Enquiries – R14 H-33

T24 Enquiries – R14 H-34
 The task requires that values from the enquiry to be passed to the fields in the
version. The values for the fields ID and ACCOUNT.TITLE is passed to the version from
the enquiry. Therefore these fields will be populated automatically once you launch
this version.

AUTOM.FIELD.NO – In this field you specify the field name for which you want to
default the values.
AUT.NEW.CONTENT – The field AUT.NEW.CONTENT holds the value to be defaulted.
Here as you are passing the value from the enquiry, specify the content in the
following format APPLICATIONNAME>FIELDNAME.

T24 Enquiries – R14 H-35

 How do you make an Enquiry invoke an application or a version?

ENQUIRY.NAME – In this field you can specify an enquiry or an application name that
will be invoked next. You can specify the function followed by the application name.
To invoke an application in SEE mode you can append the function ‘S’ along with the
application. As you are going to invoke a version that will create customer accounts,
specify ACCOUNT,TRG.VERSION1 I F3. ACCOUNT,TRG.VERSION1 is the version to be
invoked. F3 is specified for auto-id generation.

SEL.CRIT - The format is Application name>Field name. Field name should be defined
in this enquiry. In this field you will mention CUSTOMER > CUSTOMER.NUMBER ,
where CUSTOMER.NUMBER is the field name for @ID field in this Enquiry. The values
of @ID and SHORT.NAME from the CUSTOMER record will be defaulted in the field
CUSTOMER and ACCOUNT.TITLE.1 in the version

T24 Enquiries – R14 H-36

 1. Launch the parent Enquiry, you can see a link ‘Open Account’ . When you click on
the hyper link the enquiry invokes the version in turn.

2. As soon as the version is invoked , it creates a new account for the customer. The
ID and SHORT.NAME for the customer is passed to the version from the parent
enquiry.

T24 Enquiries – R14 H-37

 1. Note: The ACCOUNT ID can either be the DEBIT.ACCT.NO or the CREDIT.ACCT.NO
in the FUNDS.TRANSFER transaction. Use Open Bracket feature with
REL.NEXT.FLD as “OR”

T24 Enquiries – R14 H-38

 1. False
2. False
3. False
4. True
5. ENQ ENQNAME LAST

T24 Enquiries – R14 H-39

T24 Enquiries – R14 H-40