Scribd
Upload
19 views

Versions

This document provides an overview of the VERSION application in T24 Technical Training. VERSION allows users to create customized screens for input, display, and authorization. It can also be used to automate data replacement on records. Local subroutines can add additional validation. The document describes how to create and customize versions, including using multiple tabs. It also explains how to add fields and text, control data manipulation, and define validation and processing subroutines for a version. Version control allows grouping versions and controlling field attributes based on conditions.

Uploaded by

james kimemia
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
19 views

Versions

This document provides an overview of the VERSION application in T24 Technical Training. VERSION allows users to create customized screens for input, display, and authorization. It can also be used to automate data replacement on records. Local subroutines can add additional validation. The document describes how to create and customize versions, including using multiple tabs. It also explains how to add fields and text, control data manipulation, and define validation and processing subroutines for a version. Version control allows grouping versions and controlling field attributes based on conditions.

Uploaded by

james kimemia
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 21

T24 Technical Training

LEVEL - LEARNER
Introduction

VERSION is a standard GLOBUS application that allows users to create customized


screens for input, authorization, display etc. It may also be used where the replacement
of data on records needs to be automated. It is also possible to add local sub-routines
that can be used for field, input and authorization validation. These small programs will
allow even greater customization of GLOBUS by the user
Objectives

 To understand Version in T24

 To understand creation of version

 To know multi tabs in versions

 To know different routines used with versions


Version - Purpose

T24
APPLICATION

USER DESIGNED USER DESIGNED


SCREEN LAYOUT REPORT
 Allow users to create customized screens for input.
 Allow field contents to be defaulted automatically.
 Add local sub-routines that can be used for field, input and authorization
validation
Version – ID Format

FORMAT
» APPLICATION,VERSION IDENTITY

EXAMPLES
» CUSTOMER,1
» CUSTOMER,ABC
» CUSTOMER,AAA999
» CUSTOMER,SMITH
» CUSTOMER,SPECIA
Version Layout
Version Screen Definition

 PRINT.ONLY
No longer used

 RECORDS.PER.PAGE
Only “1” supported by Desktop
Allows multiple records on one page
e.g. CURRENCY,RATES

 FIELDS.PER.LINE
1
Multi
Version Screen Definition
LANGUAGE.CODE
 Allows screen text in multiple languages.
 Order of languages input on field language code defines the
order of language text in text fields
Example:
4.1 English 4.2 French
17.1.1 Name 17.1.2 Nom

HEADERS
 Screen title
 Two lines of text
 Font of text can be changed using Desktop
Version Adding Fields and Text

FIELD.NO
 Field number or field name
 Specific multi-values: i.e local reference fields
 To add text or blank lines enter ‘*’

COLUMN
 Starting position on the line.

EXPANSION
 Allows user to restrict expansion of multi-value fields
Version Adding Fields and Text

TEXT.CHAR.MAX
 Field description length (1-39 characters)

TEXT FIELDS
 Field label text
 Sub values for different languages

ENRICHM.CHAR
 Number of characters of enrichment to be displayed
Version Multiple Pages/Tabs

ASSOC.VERSION
 Allows data to be split across different screens, i.e. deal details,
settlement instructions, audit information

 Screens accessed by tabs/labels similar to Excel sheets in a


workbook.

 Master Version is the Version to use for input, child Version(s)


input in field ASSOC.VERSION.

 Tab detail for master Version entered in field 69


Version Multiple Pages/Tabs
Version Additional Control

 NO.OF.AUTH
Allows a different number of authorisers than default from
company record

 NOINPUT.FIELD
Prevents input to data fields.

 NOCHANGE.FIELD
Prevents users changing values after authorization.

 REKEY.FIELD.NO
Forces re-input of a field at authorisation
Version Data Manipulation

Multi-value set in fields below three fields allow automatic field


content to be defaulted

 AUTOM.FIELD.NO
Field to be controlled.

 AUT.OLD.CONTENT
Old value to be changed or blank for default input on a new
record.

 AUT.NEW.CONTENT
New value to be swapped for old value or default if field above is
blank
Subroutines

VALIDATION.RTN
This field, together with VALIDATION.FLD, allows definition of
subroutines to be executed when validating the contents of fields
within an application.

INPUT.ROUTINE
The subroutine will be executed at the unauthorized stage of
transaction processing, as the final stage before updating
unauthorized files

AUTH.ROUTINE
The subroutine will be executed at the authorization stage of
transaction processing, as the final stage before updating
authorized files.
Version.control

 This application allows users to group VERSION records and to control


field attributes based on conditions.
 The user will be able to use these features with the VERSION
application.
 VERSION.CONTROL is an addition to VERSION application.
 It does not replace the VERSION application
Version.control

 One VERSION.CONTROL can be linked to multiple VERSIONs.


 The field VERSION.TYPE can be used to link the VERSION to the
VERSION.CONTROL.
 The VERSION.TYPE forms part of the id of the VERSION.CONTROL.
 The other part of the VERSION.CONTROL record is the application name
(e.g. ACCOUNT,CUSTOMER, etc).
Version Control
Version Control
 In the example, the id of the VERSION.CONTROL is ACCOUNT,SAV,
where, ‘SAV’ is the version type.

 This allows the user to group the VERSION.

 In this case all saving accounts version can be grouped.

 Hence the routines can be attached at one place, namely the


VERSION.CONTROL application.

 If the routines exist in VERSION.CONTROL and VERSION, then the


routines in VERSION will be used.
Questions

© Cognizant 2015
20
You have successfully completed

T24 Overview

© Cognizant, 2015

You might also like