, .

'�-TEMENOS
Learning Community

I
t
Core Banking
II
t
AA Technical Overview
;
;

I
:
0
Guide (R18) (English)
2019 Q2

<��- TEMENOS
 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Table of Contents
Table of Contents ............................................................................................................................... 2
History ............................................................................................................................................... 3
Lesson Name ............................................................................................ Error! Bookmark not defined.
Feature (Article) Name............................................................................................... Error! Bookmark not defined.
Overview ................................................................................................................ Error! Bookmark not defined.
Section Headings .................................................................................................... Error! Bookmark not defined.
Sample Bullets ........................................................................................................ Error! Bookmark not defined.
Sample Numbers .................................................................................................... Error! Bookmark not defined.
Sample Figure ......................................................................................................... Error! Bookmark not defined.
Sample Table .......................................................................................................... Error! Bookmark not defined.

Guide (R18) (English) 2019 Q2 2

 . $TEMENOS
Core Banking AA Technical Overview Learning Community

History
Author Version Release Date Comments

TLC CaTS 1.0 2-May-19 Initial document.

Guide (R18) (English) 2019 Q2 3

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Introduction
Your Course
Objective and Learning Outcomes
This course will allow you to describe and use the AA proofing and publishing. In particular, you will be able to
describe the working of the product tracker mechanism in AA, describe AA COB Services, describe the concept
behind simulation, differentiate simulations on an existing arrangement and a new simulated arrangement, identify
the applications behind the three stages of the simulation.

Timetable
Here's the timetable, we've just started on the introduction lesson, following this we'll cover, Product Tracker and
COB in AA and Simulation Engine.

Figure 1 Timetable

Proofing and Publishing

A Product in AA goes through three processes - Product designing, proofing, and publishing. Designing is the
Process of creating Products by attaching Product Conditions to the Properties. It is done using the Core Banking
Product Browser. When a product is designed, it has to undergo a Proofing process. Proofing validates that the
Product has been configured correctly without errors, and is ready for release. Proofing is the process that checks
whether the product is in sync with its hierarchy such as Parent and or the associated Product Group. After a
product is proofed, it is published. A published product is available in the Product Catalog. Once a product is
published into Product Catalog, it is available for sale. When a parent Product is proofed and published, these
functions are performed down the line to all the child Products under it. In this case it is not necessary to individually

Guide (R18) (English) 2019 Q2 4

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

proof and publish the child Products individually. New Arrangements can be created for a product published into
Product Catalog.

Products
We have seen how Product Designer allows you to create Products with their Properties and Conditions. The next
stage is the Proofing. At the proofing stage, we must set the available date of the product. This will allow us to
enter the product into the catalog in advance of it going on sale. Proofing validates that the product has been
configured correctly, and is ready for release. For example, proofing checks whether all mandatory properties have
been given conditions, there are no conflicts between those conditions, ensures that a currency condition exists for
each allowed currency for a product, ensures all mandatory properties have been included... Any errors generated
can be fixed by going back to the Product Designer, and then re-proofing the product. When the product is
published, it is entered into the Product Catalog. Arrangements can be created only for products that are available
in the product catalog. Once published, products can be modified at any time. Modification is done in the Product
Designer, using the same method as for creation. Modifications will only appear in the Product Catalog after the
proofing & publishing process is repeated.

Product Management

Proof
Create Proofed Publish Product
Product
Products Catalog

...•.
Designer
Fix

....
....
Modify ....
....
Product design :
. Operations

Figure 2 Products

Effective Dates
At the center of Proofing and Publishing is the application AA. PRODUCT.MANAGER. It has two dates associated with
a product. Available Date is the date from which the product is available for sale and not the date on which the
product was created. Arrangements for the product can be created only from the available date. Expiry Date is the
date from which the product will cease to exist and no Arrangements can be input for the Product. However,
existing Arrangements for the Product will continue. Some of the other important fields are: Product Error - Errors(if
any) during the Proofing process are updated in this multi-value set. This field will be cleared after the user resolves
the errors and publishes the product again. Product Version - The version that this product is running on. This field
is updated by the system and is incremented by 0.1 for every action that the user performs on the product.
Suggestion - This field contains suggestions on what should be done if an error occurs. It is a multi-value set and for
each error in the PRODUCT. ERROR, corresponding SUGGESTION is given to rectify the error. Process Method - This
field can accept 2 values "Online" or "Service". Input in this field determines whether the Proof and Publish process
is done "Online" or through a "Service" (BNK/AA.PUBLISH.SERVICE). Irrespective of whether the Proof and Publish

Guide (R18) (English) 2019 Q2 5

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

process is "online" or "service", the processing will always happen from Parent down to the Child. Process status -
This field will hold the status of the Proofing and Publishing process at any point in time. This information can also
be accessed by the user through the Enquiry "AA.PUBLISH.SERVICE.MONITOR".

Online
From the Product, Browser select the Manage Icon. Action should be set to Proof. Available Date sets the date on
which the Product becomes available for sale. Errors in proofing will be displayed. Once successfully Proofed the
product can then be Published. Set the Process Method to "Online".
Product Lines Product Groups Products

0
"'
Line LENDING SMALL BUSINESS. LOANS
� 0' 0 0
-,.,
ACCOUlffS ...J Group Product Effective
Lill ES.OF.CREDIT �0' � 0' �
� er
DEPOSITS � @' B.LOAtl.PAREIIT 02 SEP 2009
0 ITERNET.SERVICES � 0' MG=l,IORT AGE �@'
[;J
MALL.BU lllESS LOAll 02 SEP 2009
lEtlDIIIG � @' MORTGAGES � [!{
PERSOIIAL.LOAUS
�EJ;
OTHER � @' .... � [!I
PROXY. SERVICES � fif V MALL.BU INES .LOAI IS � @'

I Product Manager�LL.BUSINESS.L�Small Business Loan (Model Bank\Product ManagerlSMALL.BUSINESS.LOAN�mall Bl!Siness Loan (Model Bank R13)

GB Description * I Product Lifecycle Management GB Description * !Product Lifecycle Management

I Manage II Audit I J Manage 11 Audit I
Action r [t�one] r CanceLproof�.JProof r Publish Action
Available Date 122 MAR2013 22 MAR 2013 J22 MAR2013.

Ir-
Expiry Date
Ir-
Expiry Date
Online/Service r [None] Online jr Service 1
Online/Service C"' [None] Online \r service

�·
Product Error.1 Product Error.1
Suggestion.1 Suggestion.1
Product Version � Product Version �

---,,
Proof and Publish Monitor Proof and Publish Monitor

Product Small Business Loan

I I
Small Business Loan
I I
Product
Action Proof Statu� Completed Sucessrully Action Publish Statusj Completed Sucessfully
Available 22 MAR 2013 Available 22 /MR 2013 4
2

Figure 3 Online

Service
From the Product Browser select the Manage Icon. Action should be set to Proof. Available Date sets the date on
which the Product becomes available for sale.

Guide (R18) (English) 2019 Q2 6

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Errors in proofing will be displayed. Once successfully Proofed the product can then be Published. Set the Process
Method to "Service".
Product Lines Product Groups Products

ti
Line ◊ LENDING SMALL. BUSINESS. LOANS

...
-"
ACCOUl�TS � Gf Group 0 Product Effective 0
� 0' a
'-'
� �
I
DEPOSITS � � L.
LIN[S.OF.CR[DIT B.LOAN,PARfHT 02 SEP 2009
INTERNET.SERVICES � IEf MG;MORTGAGE � I!{ 'w SMALL.BUSINESS.LOAM 02 SEP 2009 � GI'�
� 0' wEJ
� I
,J

LEIIDING MORTGAGES � It{

Olli£R PERSONAL.LOANS � [if
r1
� � ,J

PROXY .SERVICE � L. V SMALL.BUSINESS.LOANS � � wEJ�

:::::..1

Product ManagedSMALL.BUSINESS.LOAN]small Business Loan Product Manager'SMALL.BUSINESS.LOA�Small. Business Loan

*�ucl Llfecycle Management 7 [i>r(xiii"ct Lifecycle lolanagement ---=i

Manage
Action r (None] r Cancel Proof r. Proof r Publis� Action r (None] r Cancel Proof r Proof r. Publisl
Available Date ._____, 05 AUG Available Date * 05 AUG 201()_] " 05 AUG '
Expiry Date Expiry Date
Online/Service r [None] r Online r. Service Online/Service r (None] r Online r. ServiQ.!
Product Error., Product Error.1
Suggestion., Suggestion.1
Product Version � Product Version J�J

Figure 4 Services

AA.PUBLISH.SERVICE
The enquiry AA.PUBLISH.SERVICE.MONITOR will track the status of the Proofing process at any point in time. This
enquiry refers to the field. "Process Status" in the application "AA.PRODUCT.MANAGER". When the " Process
Method" field in AA.PRODUCT.MA NAGER application is set to Service and authorised, the product is updated in the
list file. AA.PUBLISH.SERVICE.LIST.

Guide (R18) (English) 2019 Q2 7

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

The message from this file is processed by running the service BNK/AA. PUBLISH.SERVICE. Till the message is
processed completely the status is "PROCESS I NG".
P roduct Lines Product Groups Produ�ts

Line
ACCOLII ITS
0
� 12{ lJ
i-
LENDING
Group 0
7 SMALL. BUSINESS. LOANS
Product Effective 0
DEPOSITS � 8' u LIHES.0F.CREDIT � rg L.J � � SB.L0AI I.PARENT 02 SEP 2009 � rg a
IIITERNET.SERVIC ES � 0' L) MG:;M0RTGAGE � 12{ u SMALL.BUSIHESU0AI � 02 SEP 2009 � Hf �
LB 1DIHG � 8' u EJ MORTGAGES � 0' L,

OTHER � [!I ·w PERS0HAL .L0AI� � rg "w

PROXY.SERVIC ES � rg � SMALL.BUSIN[SS.LOAI IS � i!f L� ,:1.
L
L..

Product Manager fsMALL.BUS INESS . LOANismaU Business Loan

Manage Status Monitor

r [ None] r Cancel Proof r- Proof r Publish

SMALL.BUSINESS.LOAN
Action
Status Processing . . .
Available Date ., fo sA uc; 201G7 a 05 AUG Start Date End date Related Products Product Errors
Expiry Date
r ( None] r Online r- Service
05 AUG 201 0 View
Online / Service
Product Error.1
Suggestion.,
Product Version �

Figure 5 AA. PUBLISH.SERVICE

When the "Process Method" field in AA. PRODUCT.MANAGER application is set to Service and authorised, the
product is updated in the list file. AA. PU BL ISH.SERV ICE.L IST. The message from this file is processed by running the
service BNK/AA. PUBL ISH.SERV ICE. After the message is processed completely (i.e. the product is
proofed/published successfully) the status is changed to "COMPL ETED SUCCESSFULLY".
Product Lines Product Groups Products

Line 0 LENDING
ACC0Ut m � er '-" t� Group 0 Effective 0
DEPOSITS � !El' Lll l(S.0F.CREOIT � 0' ,,..
$8 .L0AN,PAR[I IT 02 SEP 2009 � 8' :.
lfff[RHIT.�ERVlm
L B 1DIHG
� g
� 12{ � !;]
MG=M0RT AGE
MORTGAGES
� g
� @'
L, MAU.. BUSll·IESS.L0At l 02 SEP 2009 � 8'li
OTHER � 0' PERS0UAL.L0AI I � Er
L..[3�·
.., L,
PROXY .SERVIC ES � g � ,.., , MALLBUSII I E S.LOm � &

Product Manager[s��-_BU� INES�_:_LOAN] small Bus iness Loan

• l§ducl Lifecycle Management J

Manage
Action r (None) r Cancel Prooi r. Proof r Publ isl
Available Date los AUG 20 1 0 j • 05 AUG
Expiry Date I I a
Status Monitor
SMALL BUSI NESS. LOAN
Online/Service r (None] r Online r. Service
Status Completed Sucessfu/ly
Pro uct Error.1
Start Date End date Related Products Product Errors
05 AUG 201 0
Suggestion.1
Product Version � View

Figure 6 AA. PUBLISH.SERVICE

Guide (R18) (English) 2019 Q2 8

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

The process of Proofing and Publishing are the same. The screen shot above shows the product publishing process
using the service. Product proofed using the service has to be published the same way, the same is true with respect
to on line Proofing and Publishing.
Product Lines Product Groups Products

,,.
Line () LENDING SMALL BUSINESS. LOANS
ACCOUtm � g Group () Product Hfective ()

=�
DEPOSITS � ei' Llt l (S.OF.CREDIT � � L ,,.. SB.LOAt �.llAR[l f f 0 2 S E P 200 9 � 13' �
ll ffERHIT. SERV IC ES � g MG,MORTGAG[ � (!I Ll MALl . BUS ll tESS.LOAI I 02 SEP 2009 � 0' �
L mDMG � 0' MORTGAGES � 0'
OTH(R � 0' u PER OHAL . LOAll � (3 ·�
PROXY . £RVIC ES � 0' � ,Y MALLBUSlt lESS.LOAI ! � 0' 1...(3 ,i

Product Manager �LL.BUS INESS . LOANjs mall Business Loan

!Product Lrfecycle Management ]

Manage
Action r [Hone] r Cancel Proo r Proo r. Publish
AVa ilable Date • [OS AUG 20 1 0 ! • 05 AU G
Expiry Date L_ j Status Monitor

Online/Service r [None] r Online r. Service SMALL. BUSI NESS. LOAN

Status Completed Sucess{ufly
Product Error. 1
Start Date End date Related Products Product Errors
Suggestion.1
Product Version � 05 AUG 201 0 View

Figure 7 AA. PUBLISH.SERVICE

Published Product
To see if the published product is available for sale, go to, User Menu -> Product Catalog. The Core Banking
PRODUCT Browser window opens. Select Retail Term Lending (description of Lending Product Line) -> Home Loan
(description of the product group you created) -> Home Loan (15 years fixed) (description of the 15 years fixed
home loan product you created) New icon to create an arrangement for this product. Now that you have proofed
and published your product, let us now try to create an arrangement. As you already know an arrangement is a
deal between the customer and the bank. Click on the new icon. The information about the product and its
constituent properties are stored in an application AA.PRODUCT.

Guide (R18) (English) 2019 Q2 9

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

It also gives the current status whether proofed or published, the available date and Last Published date.
AA. PRODUCT.CHILDREN stores a list of child products created under a particular parent.

� U?er ��nu
I> Customer
I> CRM

e T 2 4 Product cat.al og - Windows Internet Explorer

T24 PRODUCT Browser
=====-------------=-=IPJ ,xJ
,�
Prod u ct G r o u p s Products

Category Group I S m a l l Busi n ess L o a n s

i, Acco u n ts 0 Desc rlptfon
1> Bundles F u l ly N egotii,b le Lonn S i m u la te
1> Deposits Smi, 11 B usi ness Loan S i m ula te !

I "' Lendin!l I
ft I n te r n e t S e rv ices
Grp for Acti ivty API
Bask templ ate for ALERTS
Basic template for Tri,cking
Home Equity
Lines of Cred i t
Mortgages
► I
Personal Loans
! Sma l l Busi ness Loans
Basic templote for Work.shops
Lending
1> MOblle Serv ices
D Other Products
I> Proxy Services
I> Nonfinanclal

Figure 8 Published Product

Applications
Proofing
When a product is proofed, AA. PRODUCT. PROOF is updated. The final designed product information updated in
this application. It holds data that looks similar to that of the product designer.
A A . PRODUC T PROOF SMALL B U SINES S LOM 1·2D 1 0D 1
Property. 3 PRI NCI PAU NT
GB Desa-iption js ma ll Business L o a n I
Prd Property. 3 . 1 �ED . RATE
F u ll Desc jSm a ll Bu siness L o a n}
Product Group 1SMII. L L . BUSI NESS . L OA NS: Arr Link. 3 . 1 NON .TRACKI NG
P a rent Product ' S B . L OA N . PARE NT]
Property.4 PENAL TYi NTj
C u rrency. 1 US DJ US Dolla r
P roperty. 1 !ACCOU NT
Prd Property.4 . 1 I FLOATI NG . RATE
Prd Property . 1 . 1 � MIi. L L . BUSI NESS . LOAN Arr Link.4 . 1 1
NON .TRACKI NG
Arr L ink. 1 . 1 1 NO N . T RACKI NG
Property. 5 NEWARRFEE_j
Property.2 [ CO MMI T ME NT
Prd Property. 5 . 1 ILEVEL . FLAT
I Arr Link. 5 . 1
Prd Property.2 . 1 LOAN . REDRAW
A rr Link.2 . 1 !NON . T RACKI NG NON .TRACKI NG

Figure 9 Proofing

Guide (R18) ( Engl ish) 2019 Q2 10

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

The proofed product conditions are updated in a set of applications prefixed with AA.PRD.PRF. < PROPERTY.CLASS>.
When a product is proofed, a copy of the product conditions attached in the product is picked and records in
AA.PRD.PRF. < PROPERTY.CLASS> files are created depending on the appropriate property list of the product.
AA . PRD . PRF . TERM . AMOUNT · Defo u lt List
Id Desc ri ption
<J CH ILD1 -COMM ITMENT-USD- - 20090 1 0 7 Loan (Non Revolving)

AA . PRD . PRF . INTEREST · Default List

Id Desc ription
Q C H ILD 1 -P ENAL TY INT-U D - - 20090 1 0 7 Floating Rate
0..., CH ILD 1 -PRINC IPALINT-USD - - 20090 1 07 Periodic Rate with Margin

Figure 1 0 Proofing

AA. PRD. PRF .<PROPERTY.CLASS>

What you see here are proofed product conditions for the product CHILDl, for COMMITMENT, PRINCIPALINT, and
PENA LTYINT properties. Constituents of the ID are:
• Product name
• Property Name
• Currency (if Property Class is currency based)
• Effective period (example 1M we give in Product Designer for product conditions which are to be effective
on a future date)
• Condition Effective Date.

Publishing
When a product is published, the record from AA.PRODUCT.PROOF is deleted and AA.PRODUCT.CATALOG is
updated. It holds the final published product. It holds data that is similar to that of the product designer.

Property. 3 PRI NC I PALI NT

GB Descrip tion Smalt Business Loa n f
F u ll Desc Smalt Business Loan I
Prd Property. 3 . 1 FIXE D . RAT E

Pro duct Group SMALL , BUSI NESS . L OANS Arr Link. 3 . 1 NON .T RACKI NG !
Parent Product S B . LOAN . PARE NT s Property.4 PENALTYI NT
C u rrency. 1 � u: Dollar
Pro p erty. 1 ,ACCO U NTj
Prd Property .4 . 1 F L O� T ! !'J� . RAT§J
Ac,
P r d Pro p erty. 1 . 1 '"s.vALL , B U S I NESS . L OAN Arr Link.4 . 1 NON . T RACKI NG
Arr L i n k . 1 , 1 NON.TRACKI N G
,----
Property. 5 N E WARRF E E
Pro perty.2 co
,v.vn ME NT I Co
Prd Pro perty.2 . 1 L OAN . REDRAWi
Prd Property. 5 . 1 LEVE L . F LAT
Arr Link.2 . 1 NON .TRACKI N G
,----
Arr Link. 5 . 1 NON . T RA C Kl NG

Figure 1 1 Publishing

The published product conditions are updated in a set of applications prefixed with
AA.PRD.CAT.< PROPERTY.CLASS>. When a product is published, the records from AA.PRD.PRF.< PROPERTY.CLASS>
applications are deleted and records are created in a set of applications called AA.PRD.CAT.< PROPERTY.CLASS>.

Guide (R18) (English) 2019 Q2 11

 . Overview
Core Banking AA Technical . $ TEMENOS
Learn i ng Commun ity

When an arrangement is created for a product, the product conditions are fetched from these applications.
AA . PRO .C AT. TERM . AMOUNT · Default List

- Id
<-> C H ILD 1 -C OMM ITM ENT-USD- - 20090 1 0 7
Desc ri ption
Loan (Non Revolving)
A A . PRD . C AT. fNTEREST · Defa u l t List
Id Desc ription
<-> C H ILD 1 -P ENAL TY INT-USD - - 20090 1 0 7 F loating Rate
(\. C HILD 1 -PRINC IP AL l l-tl-USD · · 20090 1 0 7 Periodic Rate with Margin

Figure 12 Publishing

AA. PRO.CAT.< PROPERTY.CLASS>

What you see here are cataloged product conditions for the product CHILD1, for COMMITMENT, PRINCIPALINT,
and PENAL TYi NT properties.
�PRO . C AT. TERM . AMOUNT ! CH ILD1 - C O M M ITME NT- U S D--20090J I
GB D e s cription I Loan (Non Revolving) I �AA . PRO . CAT. INTEREST I C H I LD 1 - P R I N C I PALINT- U S D--200901 0�
Revolving � GB D e s cription I Periodic Rate with Margin I
Pr A ttri b u te , 1 I F U L L ' DI SB URSEMENT I
Day B a s i s [fil 366/ 365
Pr Value . 1 � Accru a l Rule IFI RST I l l�T ER
Pr Brk Res . 1 lovERRI DE I
B a la n ce C a le Typ e ID R . DAI LYI D a i ly D E B I T B a la n ce
Pr Brk Msg, 1 IAA . E CT , EQUA LI
Rate T i e r Typ e ls 1 N G L E I
D e fa u lt N e gotiable �
Nr A ttri bute . 1 IREVOLVI N GI
Periodic I nd e x . 1 �
Periodic Method . 1 I I NT E RP O LAT E I AA . PRO . C AT. INTEREST ! C H I LD 1 - P E NALTY I NT- U S D--200901 �
Nr O p tio n s , 1 . 1 I N O N - NEGOTIABLE I
Margin Typ e . 1 . 1 !single Margin l
Nr A ttri b u te . 2 I U P DATE . C OMMT . L I M I T I
Margin O p e r . 1 . 1 IA D DI G B D e s cri ption I Floating Rate l
N r O p ti o n s .2 . 1 I N O N - N E G OT I A B L E I
Margin Rate . 1 . 1 10 .2 51 Day B a s i s [g 366/366
D e fa u lt N e gotiable � A ccru a l Rule I F I RST I I NT E R
Nr A ttri b u te . 1 IP E RI O D I C . P E RI O DI B a la n ce C a le Typ e I D R . DA I LYI D a i ly D E B I T B a la n ce
Nr Options . 1 . 1 I NEGOTIABLE I Rate T i e r Typ e l s 1 N G L EI
Nr A ttri b u te .2 IMII.RGI N . RAT E I Floating I n d e x , 1 [TI L o a n B a s e Rate
Nr O p tio n s . 2 . 1 I NEGOTIABLE I Margin Typ e . 1 . 1 !s i n gle Ma rgi n l
Nr Typ e .2 . 1 IMII.XI MU MI Margin O p e r . 1 . 1 IADD I
Nr Value .2 . 1 1. 5 I Margin Rate . 1 . 1 l o . 5o l
Nr Mes s a ge , 2 , 1 lovERRI DE I T i e r Min Rate . 1 I 7 . oo l
Nr Typ e . 2 . 2 IMI N I MU MI T i e r Max Rate . 1 I 9 . oo l
Nr Value .2 ,2 I.1 I Default Negoti a b le �
Nr Me s s a ge .2 .2 lovERRI DE I Nr A ttri b u te . 1 I MII.RGI N . RATE I
Nr Options . 1 . 1 I N E G OT I A B L E I

Figure 13 AA. PRO. CA T. <PROPERTY. CLASS>

Product Manager and Effective Dates

At the center of Proofing and Publishing is the application AA. PRODUCT.MANAGER. It has two dates associated with
a product. Available Date is the date from which the product is available for sale and not the date on which the
product was created. Arrangements for the product can be created only from the available date. Expiry Date is the
date from which the product will cease to exist and no Arrangements can be input for the Product. However,
existing Arrangements for the Product will continue. Some of the other important fields are Product Error: Errors(if
any) during the Proofing process are updated in this multi-value set. This field will be cleared after the user resolves
the errors and publishes the product again. Product Version: The version that this product is running on. This field

Guide (R18) (English) 2019 Q2 12

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

is updated by the system and is incremented by 0.1 for every action that the user performs on the product.
Suggestion: This field contains suggestions on what should be done if an error occurs. It is a multi-value set and for
each error in the PRODUCT.ERROR, corresponding SUGGESTION is given to rectify the error. Process Method: This
field can accept 2 values "Online" or "Service". Input in this field determines whether the Proof and Publish process
is done "Online" or through a "Service" ( BNK/AA.PUBLISH.SERVICE). Irrespective of whether the Proof and Publish
process is "online" or "service", the processing will always happen from Parent down to the Child. Process status:
This field will hold the status of the Proofing and Publishing process at any point in time. This information can also
be accessed by the user through the Enquiry "AA.PUBLISH.SERVICE.MONITOR".

Guide (R18) (English) 2019 Q2 13

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Product Tracker and CO B in AA

Product Tracking
A product might undergo many changes after it has been published for the first time. Existing arrangement
conditions may have to be modified when a product is changed. How does Core Banking know about the product
changes and how does it track the changes for the existing product? The answer to these questions is a file called
AA.PRODUCT.TRACKER.CATALOG.

AA.PRODUCT.TRACKER.CATALOG
Every time a product is proofed or published, Core Banking tries to track the changes that have happened to the
product conditions using the AA.PRODUCT.TRACKER.CATALOG application. There are various criteria based on
which Core Banking decides if a product needs to be tracked or not. Products set to inheritance only are not tracked
but if this product is changed, then the affected child products are tracked. If it is the first publish event, then the
changes are not tracked. Classic products (i.e. standard non-AA Core Banking products like Accounts) are not
tracked.
Core Banking routines compare the old published property records with the new ones to find the changes. Core
Banking routines do the following actions. It first checks if the product is being published for the first time. If it is
not published for the first time, the product conditions are compared otherwise the tracking does not happen.
Negotiation fields are ignored. If the action if PROOF, the comparisons done are updated onto a file called
AA.PRODUCT.TRACKER.PROOF with the Product as ID. If the action is PUBLISH, the comparisons are not done. The
update is done onto a file called AA.PRODUCT.TRACKER.CATALOG and the AA.PRODUCT.TRACKER.PROOF record is
deleted. The record ID in both the applications AA.PRODUCT.TRACKER.PROOF and
AA.PRODUCT.TRACKER.CATALOG is the product ID.
Consider this product MORTGAGE.OFFER, the property NEWARRFEE is set to 500. Note the arrangement link for
the property is set to Tracking. Change the product condition for NEWARRFEE from ZERO.C HARGE to 250.
!,lore Actions ...

Conditions Arrangement link Effective Base Variation

-----i 500 I Tra ckln:; CJ
J liclXED. RATE.5" _J Non.trac�lnc: [ ==i Start

J J [_
c=I
Non.trac.king

MORTGAGE.OFFER ] Trackln1:

Prope1ty Conditions Calculation source Audit

C. ..
Conditions Arrangement Link Effec tive Base Variatio
!250 [ Tracking " r
F IXED.RAT E.7% 7 [Non.tracki� [_, [ Start L -=::l
L ..
'
'MORTGAGE.OFFE R ] I Non.track ing " I
1
MORTGAGE.O FFE R _] [±racking
_
", Lll ..
Figure 14 AA. PRODUCT. TRACKER. CA TA L OG

Guide (R18) (English) 2019 Q2 14

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Proof the product. After proofing the product and before publishing the product, record gets created in an
application called AA. PRODUCT.TRACKER. PROOF of the changes. If you notice, a product called MORTGAGE.OFFER
has been proofed and the record is created in AA. PRODUCT.TRACKER. PROOF as the condition for tracking property
NEWARRFEE has been changed.

Proof and Publish Moni tor

Product ortgage (Special Offer)
Action Proof Status Compl eted Sucessfully
Availabl e 22 /MR 20 1 3

AA. P RO D U CT.TRAC KER. P ROO F L

AA. PRODUCT.TRACKER. PROOF - Default List

Id Property ccy Reserved 1 0 Designer key Eff period
MORTGAGE.OFFER NEWARRFEE-USD 250- -20091 202

More Ac tio
AA. P RODUCT .TRACKER. P ROOF MORTGAGE. OFFER I (�odel Ban�)_

Property Ccy. I N E WARRFEE-USD

Desi gner Key. I . I
Eff Date . 1 . I 1 4 JUN 20 1 2
Property Ccy. 2 f_RJN� IPAL INT-U SO'.
Designer Key. 2 . 1 F ED.RAT E.7%-US D-20 00 0
Eff Da e . 2 . I !l ' JUN 20 2. � JUN 20 1 2

Figure 1 5 AA. PRODUCT. TRACKER.CA TA L OG

Now publish the product. Do a listing on AA. PRODUCT.TRACKER. PROOF, you will not find any entries here for the
published product. If the action is publish, then the product is not compared for changes, instead of the record from
AA. PRODUCT.TRACKER.PROOF is removed and entries are copied to AA.PRODUCT.TRACKER.CATALOG. Do a listing
on AA. PRODUCT.TRACKER.CATALOG to see the new entry for the re-published product.

Guide (R18) (English) 2019 Q2 15

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Remember, if a product is proofed or published for the second time, new records are created in both the
applications, otherwise the existing records are updated.
Proof and Pub li sh Monitor
Product Mortgage (Special Offer)
Action Pub! ish Status Completed Sucessfully
Available 22 MAR 20 1 3

Entries removed from

AA.PRODUCT.TRACKER.PROOF after t h e Product
AA. PRODUCT.TRACKER. PROOF L Is PUBLISHED

te %AA.PRODUCT.TRACKER.PROOF - Windows Internet Explorer

No data to display

Error message

.-.. m ra t:n
No rec o rds matc h e d the selec tion c ri teria
More Ac tions
AA. P RO DUCT. TRACKER. CATALOG MORTGAGE . OFFER iModel Bank)

1
Property Ccy. 1 N E WAR RFEE·USo'
Designer Key. 1 . I ,250--2009120
Eff Date. I . I fuuN 2012 1 4 JUN 201 2
Property Ccy. 2 !PR INCIPAL INT·U SO,
Designer Key. 2 . 1 �D.RATE.7%·USD-�
Eff Date . 2 . I [14i"uN 2012 14 JUN 20 1 2

Figure 16 AA. PRODUCT. TRACKER. CA TA L OG

Now you will see a few scenarios to understand AA. PRODUCT.TRACKER.CATALOG. What you see here is a product
condition called HELLOC attached to a property ACCOUNT. There are two product conditions for HELOC with two
different effective dates.

Guide (R18) (English) 2019 Q2 16

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

W h e n a p rod uct condition is back d ated (the date is ava i l a b l e as p a rt of the prod uct co n d ition's i d ) , t h e n t h e
effective d ate is Co re Ba n ki ng's c u rrent d a t e fo r the p rod uct. For a fut u re d ated prod u ct cond ition, t h e futu re d ate
is s pe cifi ed in t h e Effective date fo r the p rod uct .

I
Product Designer PERSONAL.LOAN-20000 1,0 1 I
Product Conditions
Product Group I P E R S O NAL.LOAN S I

r lr
Parent Product I P E R S O NAL. LOAN : PAR E N T I ACC O U N T
J Property Conditions
I Calculation Source 't..vaiabimy 1� Conditions
HELOC
Description Effectiue
Ho. �e Equtt:Y Line. of Credtt (31 07) 1 01 JAN· 2000 � !El'
Property Conditions Arrangement· Link HELOC I
Home Equtty Line of Credtt (31 07) 01 JAN 2009 �
,
�

IA c c o u N T I I H E Lo cj I N O N . T RACKI N G I

AA.PRODUCT.TRACKER.PROO_F I PERSONAL.LOAN I
Propei1y <;cy .1 jAC C O U N T I Effective Date for H ELOC-20000 1 0 1 1s 9 h

D�signer KeY,.1 .1 I H E LO C-20000 1 0 1 I JAN 2008- because the Core Banking

dote 9 1h JAN 2008

!
Eff Date.1 .1 jog -JAN zoos I

Designer Key.1 .2 I H E LO C-2oogo 1 0 1 I

I
Eff Date.1 .2 jo 1 JAN 2009 1

AA.PRODUCT.TRACKER.PROOF PERSONALLOAN.2W j I
Property Ccy.1 jACCO Utn j

Designer Key .1 .1 IHELO C.20000 1 0 1 j

Eff Date.1 .1 09 JAN 2008

Des· er Ke .1 .2 H E LO C.20000 1 0 1

E f f Date .1 .2 jo 1 JAN 2000 I

Figure 1 7 AA. PRODUCT. TRACKER.CATALOG

Let us create a n d atta ch a new p rod uct co n d ition ca l l ed S N K fo r the s a m e ACCO U NT p roperty. S N K has two
c o n d i t i o n s in t u r n . O n e is effective fro m 01-JAN -2000 a n d a n ot h e r effective fro m 0 1-JAN -2009 .

Guide (R18) (English) 2019 Q2 17

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

If you notice, the product condition is specified to an effective 1 month from the date of the arrangement. Let us
try to understand this better.
Product C onditi o n s

ACCOUNT
Conditions Description Effective
PCACCOUII T 0 1 User Loan (31 06) 09 JAN 2008
PERSOIIAL.LOAII Personal Loan (31 02) 01 JAN 2000
SMALL.BUSltlESS.LOAII Small Business Loan (31 01 ) 01 JAN 2000

I SIIK
SllK
Demo for Product Tracker
Demo for Product Tracker
01 JAN 2000
01 JAN 2009
1

I
Product Designer PERSONAL.LOAN-20000101 j

GB Description IPeisonal Loan!

Full Description IPeisonal Loa n!
Product Group IPERSONAL LOANsj
Parent Product IPERS ONALLOAN. PAR E N T!

r Property Conditions
J Calculation Source
II Avsilabllay
II Aucfrt
l
-
....J 1 month from the date of arrangement, Product
.. condition SNK will be applied
D,��-..._, - 1 ,�., CH_, •ive

I
!AC C OU N T! !H E LO Ci
jsNKI
I NON.T RAC KING I
jNON.T RACKING j r:iM7 I
Figure 18 AA. PRODUCT. TRACKER. CA TA L OG

Assume that today's date is 09-JAN-2008, the arrangement created today will also be of date 09-JAN-2008.
Property Ccy.70 !AC C O U N T I
Designer Key .70 .1 I H E LO C-20000 1 0 1 !
Eff Date .70 .1 I 09 JAN 2008 I
Property Product Condition Effective Period
Designer Key .70 .2 I H E LO C-20090 1 0 1 I
-
Eff Date .70 .2 io 1 JAN 2009 1
ACCOUNT H ELOC-20000 1 0 1 Designer Key.70 .3 i s N K-20000 1 0 1 I
ACCOUNT HELOC-20090 1 0 1 - Eff Period .70 .3 i1 M!
Eff Date.70 .3 I 09 JAN 2008 1
ACCOUNT SNK-20000 1 0 1 1M Designer Key .70 .4 i s N K-20090 1 0 1 i
ACCOUNT SNK-200901 0 1 1M
Eff Period .70 .4 I1 M!
Eff Date.70 .4 10 1 JAN 2009 1

Figure 19 AA. PRODUCT. TRACKER. CA TA L OG

If an arrangement is created today, what will be the case? There are two product conditions falling on the same
date, HELOC-20000101, and SNK-20000101. Both are back dated. In this case, HELOC-2000010 will be given priority
because SNK-20000101 is effective only from one month after the date of arrangement as you have specified in
your arrangement. Consider that today the date is 09-FEB-2008. Again there are two product conditions, HELOC-
2000010 and SNK-20000101. But only one product condition can be applied. This time SNK-20000101 will be used
because this condition would be applied one month after the date of the arrangement. What will be the condition
that will be applied on 01-JAN-2009? There are two product conditions, HELLOC-20090101, and SNK-20090101
available for today. Well, the condition that will be applied today on an arrangement will be SNK-20090101.
Because, on 09- FEB-2008, the product condition that was used was SNK-20000101. A new product condition has
been used. From SNK the product condition cannot change to HELLOC. So the product condition available with SNK,
that is, SNK-20090101 will be applied.

Guide (R18) (English) 2019 Q2 18

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

AA.ARR.PRODUCT.TRACKER
This service is used to track the product changes and apply the changes on to the arrangements. It refers to a file
called AA. PRODUCT.TRACKER.CATALOG to know the changes. When a new product condition is defined for
property or attributes values are changed within a product condition. If the property is set to TRACKING in the
product, the changes need to be tracked for the existing arrangements. The arrangement conditions for the
property (AA.ARR. < PROPERTY.CLASS> ) is not updated until the service AA.ARR. PRODUCT.TRACKER is run. This
service will update the arrangement condition record with the changed conditions. The service is automatically set
to start when the product is re-published but it will take some time for the arrangement conditions to be modified
as the service has to modify the conditions of each arrangement that is affected by the change in product condition.
When an activity is performed on an existing arrangement for the property, values of the attributes are merged
from the product condition. So, although the arrangement condition record is not immediately updated and
changes are reflected when the activity is performed.

I More Actions . . .
' BATCH BNK/ AA. ARR . PRODUCT.TRACKER (Model Bank)

Process Status 0 READY

Batch Envi ronment F FO REGROUND
Job Name . 1 AA.ARR. PRODU CT.TRACKE R!� Track Product changes
Frequency. 1 DI DAI LY
Job Status . 1 0 READY
Curr No 1,
Figure 20 AA.ARR. PRODUCT. TRACKER

Activity
AA.SCHEDULED.ACTIVITY
This file stores a list of activities that has been scheduled to run for an arrangement. The id of the record in this file
is the same as that of the arrangement id. What you see here is a sample record of arrangement AA170801NHHK.
The field ACTIVITY. NAME is used to specify the name of the activity that has to take place. The field LAST.DATE
specifies when this activity was run last. The field NEXT. DATE specifies when this activity will run next. The field
NEXT.RUN. DATE is the earliest date on which an activity is scheduled to run for an arrangement. This is the lowest
date among the NEXT. DATE fields .

Guide (R18) (English) 2019 Q2 19

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Remember, when ever AA.ARR. PRODUCT.TRACKER runs, it tracks the changes to a product and applies the changes
to the appropriate arrangements. It also updates AA.SCHEDUL ED.ACTIVITY file with the updated activity
information.

I More Actions ...

AA. SCH E' DULf O . ACTIVITY AA1 70801 NHHK (Modet- 6ank)

Activity Name . 1 LEN DJNG•MATU RE'.•ARRANGE MENT M a lJr Arran2�mem

Next Date. I �-1 M�R io�L. 21 R 2 Z.:
_
Activity Name . 2 lENOI NG. c MAK'EOUE-SCrl �DUlE
Last Date . 2 0 1 APR 2 0 7 01 APR 2 0 1
Next Date . 2 01 MAY l017 01 '!< 201 7
·- - - . •· ,... .. .
ActtvftY Name. 3 lEN
r_
OJ·- NG•MATU
• - --
R£·ARRANGE
• •
ME• - --
•PR •.NOTICE
• -
Prenotlc:e for aneement ,t unty
Next Date . 3 19 MAR 2022
Activity Name . 4 LE N DJNG-EVALUAT DORMANCY E.,,._lue e- Ocnn .:nq• Condi 1cn
Next Date .◄ 2 1 MAR 20.18. ., 1 MR 10 8
Act vfty Name . .5 lENOI NG._-AGE--OVEFlDU .E"" GRC l t iSTA·L �MENT
Lllist Date , 5 02 APR 201 7 02 APR 2 0 ' 7
Activity Name.6 lE N01NG·AGE-0VERDU E r 0E I NSTAL MENT Afe ln�tallment B ll D l,oquen )
Last Date .6 06 APR 20 l7
- --
06 ,,pp 1 1 7
ActM ty Name, 7 U'.NOING•ISSUE:.CHAS� .R-OV'EROUE ° DEL • 1NSTAllM ENT' l• �ue lnsta H ment Oel )nqut:nt C lla,er
L.a st Date . 7 07 APR 2017 07 Afl"R , 0 1 1
Next !;>ate . 7 �� APR 2017 1 ,.pp 0 7
Actfvfty Name . 8 lENOl G-AGE-OVE ROUE :;-NAS • j STALl M E r'
Next Date. a 3 1 MAY 201 7 3 1 MAY 101 7
Next Run Da te 2i APH 0'1 7, l t APR 0 1 i

Figure 21 AA.SCHEDULED.ACTIVITY

AA.N EXT.ACTIVITY
AA.N EXT.ACTIVITY file acts as a list file that cannot be directly accessed from Core Banking. It holds records that
have to be processed during COB. If you look at the records, the ids are of format <ARRANGEMENT.ID>-< DAT E>,
where the date is the NEXT.RUN. DATE value picked from AA.SCHEDUL ED.ACTIVITY. Basically what happens is that,
during COB, AA.SCHEDUL ED.ACTIVITY is not read, but AA. NEXT.ACTIVITY file is read. Consider the first record,
AA16113SG2 BN-20160423. If you look at the AA.SCHEDUL E D.ACTIVITY application for the arrangement, the
NEXT.RUN. DATE value is 23-APR-2016, that is why you have a record by id AA16113SG2 BN-20160423. When the
list file is picked for processing, all the records are selected and then a filter routine is called to filter the records to
be processed today if today's date is 09-FEB-08, then the activity scheduled on that date is processed, otherwise,
its skipped. If a record is processed today, the dates are cycled, AA.SCHEDUL ED.ACTIVITY is checked if there is any
other activity to be processed for another date, if yes, the AA.L ENDING. NEXT.ACTIVITY record is updated with the
next possible activity to be performed. In our scenario, there are no other activities for another date, in this case,
the old record in AA.L ENDING. NEXT.ACTIVITY for the arrangement is deleted and a new record with ID as that of
the arrangement id is created.

Guide (R18) (English) 2019 Q2 20

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

List files are available for different product lines like AA.L ENDING.NEXT.ACTIVITY, AA.DEPOSITS.NEXT.ACTIVITY.
\.Jelcome to H2 Shell 1 . 3 . 161 ( 2011 - 10 - 2 8 )
Exit 1•1ith Ctrl+C
Corm1ands a re case insensitive; SQL st atements end with · ; •
help or ? Di splay this help
l i st Toggle result list / sta c k t ra c e mode
max1·1idth Set maximum column 1·iidt h ( default i s 100 )
l autocommit E nable or disable a utocommit
history Sho1·1 the last 20 st atements
quit or exit Close the connection and exit

jsql > S E L ECT F ROM F BNK_AA_NEXT_ACTIVITY;

I STRRECORD ..,
. ifv ED M_o_
re_A_
._I ct_
lo_
n_
s_ _.!
. . .__"' �
RECIO
'M l 7080GSPV:i1- 20170421 I
? -r I I

iAA17080CNL3H - 20171219 I . . OGSPV 1 (Mo�el Bank)

IAA17080XDPFD - 20170329 I
1 AA17080TSNYS - 20170421 I Activity Name. 1 'L ENDING·MAT��E-ARRANGE�ENT,
I
Ma ure Arran�ment
AA170803\>JR9N - 20170404
AAl 7080U·JKHS - 20170329 I
1 Next Oate . 1 '2 1 MAR 2019 21 MAR 201 9

7080SRQ\•i8 - 20170421 I
Activity Name.2 µNC}lNG·CAN�EL•�R-R AN§�� E�l'; Cancel Arrangement
AAl
,AA170802FR F K - 20170421 I
j Last Oate.2 :Z�MA. � J.01_?_ 2a MAR 2017
jAAl 70808Nl•JSB - 20210319 I Activity Name.3 LENDING -MAKEDU E-SCHEDULE Scheduled Payment Oue
AA17080FTQ0J - 20170421 I Next Oate . 3 ' 2 1 APR 2017•
C �
21 APR 101 7
Activity Name.4 lENOING:CANCEL-AR!l;\NGEMENT-PRE.NOTICE: Prenotlf1catto n of Arraneement Cancelation
Last Date.4 :?6 MAR 2_01.7 26 MAR 201 7
Activity Name . 5 ,L ENDING-MATURE-ARRAN. G EM ENT-PRE.NOTICE Prenotice for Ammeement Mutunty
Next Oate . 5 (i9 M�R. 2019 19 MAR 201 9
Next Run Date 21 APR 2017. 21 APR 20 1 7

Figure 22 AA. NEXT.ACTIVITY

COB Records
There are two C O B records in the BATCH application: AA.SOD. PROC ESS and AA.EOD.PROCESS. Each of the BATCH
records is made up of few jobs. AA.SOD.PROCESS, this batch record is processed during the Start-of-Day stage of
COB (D250). AA.COB.PAY.IN.OUT, this job is out of scope for this course. AA.SERVICE.PROCESS, this is the actual
routine that reads AA.SC HEDUL E D.ACTIVITY file and processes the appropriate activities for the arrangement.
AA.EOD.PROC ESS, this batch record is processed during the End-of-Day stage of COB (S02 2).
AA.ARR.PRODUCT.TRACKER, this is the routine that you learned in the previous slides. This routine can run as a
service or a COB job. Its main job is to track a product for changes, AA.COB.PAY.IN.OUT, AA.SERVICE.PROC ESS. You
must notice that the batch jobs AA.COB.PAY.IN.OUT and AA.SE RVICE.PROCESS is executed twice during COB, once
during EOD and next during SOD as soon as the Core Banking date changes to the next working day.

AA.ACTIVITY.CLASS and COB

For an activity class, the ACTIVITY.TYPE filed is used to specify how an activity will be triggered. There are many
activity types available. You will now look into two types, SCHEDUL ED and SOD-PROCESS. SCHEDUL ED - When an
activity class is set to SCHEDULED it means that this activity can be executed as part of COB. This activity will be
executed during the batch process AA.EOD.PROCESS. SOD-PROCESS - When an activity class is set to SOD-PROCESS
it also specifies that this activity can be executed as part of COB but this activity will be executed during the batch
process AA.SOD.PROCESS. Field BATCH.NAME will be used when ACTIVITY.TYPE is set to SCHEDUL ED or SOD­
PROCESS, to specify the batch name in which the activity should be run along with a field called BATCH.SEQ that
determines when this activity will be run. Consider that ACTIVITY.TYPE is set to SCHEDULED, BATCH.NAME is set to
AA.EOD.PROCESS and BATCH.SEQ is set to 90 for an activity class called LENDING-AGE-OVERDUE.

Guide (R18) (English) 2019 Q2 21

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

This holds that the activity LENDING-AGE-OV ERDUE will be executed as part of batch process AA. EOD. PROCESS as
90th activity as the sequence number id 90. Temenos decides the sequence number for an activity.

I
ActMty Class LENDING-AGE-OVERDUE I Ac1Mty Class I ENDING-AGE- VEROUE I
GB Description !Ag e ove rd u e b i l ls!
GB Description ! Ag e ove rd u e b i l ls !
Full Description !Ag e ove r d u e b i l l !
! Ag e ove rd u e b i l l I
I Actions ]1 Type Batch Audit
Full Description

I Activity Type .1 I S C H E D U LE D I [ Actions Type _J B tell

Activity Type .2 I
I I B,tch llame Se<1uence
S E C O N DARY!

Activity Type .3 [ s o D- P R O C E S�
AA. E D D . P R O C E S S 90
I
Activity Type.4 N O R EVE R S E I AA. S O D . P R O C E S S 90

Figure 23 AA.ACTIVITY. CLASS and COB

Guide (R18) (English) 2019 Q2 22

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Simulation Engine
Simulation
Simulation refers to the ability to perform a single or a series of operations in the system and obtaining the outcome
without actually applying these changes to the LIVE system. The Simulation tool helps in decision making for the
customer. AA will now provide a mechanism where one can simulate a new arrangement or perform changes to an
existing arrangement. Consider that you have created a new product, so far, to test the product you have been
creating an actual arrangement. Using simulations you can simulate a new arrangement for a product.
You will now see a list of simulations that can be done on a new arrangement. One can simulate a new arrangement
for a newly created product. Simulate user activity on an existing arrangement. Negotiation rules are applied while
changing arrangement conditions. One can project a new maturity date and payment schedules. One can simulate
new arrangement for existing products with special negotiations for preferred customers.

Stages
Simulation runs in three stages. The first stage involves data capture, wherein the data required to perform a
simulation is captured. For example, assume that you wish to change the principal interest rate for an arrangement,
in this case, the data to be captured would be the new interest that you wish to apply. In the second we define a
record in AA.SIMULATION.RU NN ER, after this record, is authorized an OFS message is created in the file
AA.SIMULATION.SERVICE.LIST. The third stage would be to run the simulation, wherein the OFS message generated
in the second stage is executed by running a service. The actual simulation process happens when the service is
run. Note that once you have simulated and you find the changes satisfying, now you can apply the change on to
the LIVE record in case of an existing arrangement, or make it LIV E in case of a simulated new arrangement.

Data Capture
You will now learn about the first stage of simulation, that is, data capture. The data is captured from the user. The
captured data is stored in an application called AA.SIMULATION.CAPTURE. This application is similar to
AA.ARRANGEM ENT.ACTIVITY. Both the applications share the similar set of fields with very little variations. You will
now try to understand this application better.

Guide (R18) (English) 2019 Q2 23

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Applications
AA.SIM.< PROPERTY.CLASS>
The applications AA.SIM.< PROPERTY.CLASS> are similar to your AA.ARR.< PROPERTY.CLASS>. The former stores the
simulated arrangement conditions and the later stores arrangement conditions of a LIVE arrangement.
AA .SIM .PA YMEIH .SC HEDUL E • Oof,1u 11 Liu
Id Activity Ac tion BAse dAte
°
' t A A090070V I OL,REPAVM ENT .sC H EDULE- 20090 1 07. 1 LENDING-NEW- ARRANGEMENT UPDATE 07 JAN 2009

AA .S I M . PAY M E NT.S C H E D U LE
AA0900 740ZS6-REPAVM HIT . SCH EDULE- 10090 10 7. 1 LENDING-C HANGE. TERM-COMMITMENT CALCULATE 07 JAN 2009
._ A A0900 740ZS6-REPA VMEHT .SCH EOUL E- 20090 1 0 7. 2 LENDING-INCRE A�·COM/IIITMENT CALCULATE 07 JAN 2009
"._ A A0900 74VWOJ,REPAVMEIIT . SC H EDUL E- 20090 1 0 7. 1 LENDING- NEW- ARRANGEMENT UPDATE 07 JAN 2009
" AA09007C097W•REPAVM EUT .SC H EDULE· 20090 1 07. 1 LENDING- NEW- ARRANGEMENT UPDATE 07 JAN 2009
" A A0900 7F 3DC W•REPAVMEIH .SC H EOUL E · 20090 1 0 7. 1 LENDING-C HANGE•PENALTVINT CALCULATE 07 JAN 2009

A A .SIM .ltH £REST · Defau lt List

Id Activity Ac tion

"
r"I
AA090070V I OL-PEHALTYIHT- 20090 1 0 7. 1 LENDING-NEW-A RRANGEME NT UPDATE
AA . S I M . I NT E R EST AA090070V I OL-PRINCIPAlltH- 20090 1 0 7. 1 LE NDING-NEW- ARRANGEMENT UPDATE
AA0900 74VWDJ-P ENALTYltH· 20090 1 0 7. 1 LENDING-NEW-A RRANGEMENT UPDATE
AA0900 74 V WDJ•PRII l( IPALIHT- 20090 I O 7. I LENDING-NEW-ARRANGEME NT UPDATE
A A0900 7C097W-P EUALTYIIH- 20090 1 0 7. 1 LENDING-NEW-ARRANGEMENT UPDATE
AA0900 7C 09 7W-PRIHC IPALIHT- 20090 1 0 7. 1 LENDING-NEW-ARRANGEMENT UPDATE

Figure 24 AA.SIM. <PROPERTY. CLASS>

What you see here are sample records from AA.SIM.PAYMENT.SCHEDUL E and AA.SIM.INTER EST applications. If you
notice, the ids of these applications are similar to that of AA.ARR. < PROPERTY.CLASS> applications.

AA.ARRANGEMENT.ACTIVITY & AA.SIMULATION.CAPTURE

You will now compare AA.ARRANGEME NT.ACTIVITY and AA.SIMULATION.CAPTURE applications. You must be
aware by now that for an activity, the actions(on a property) defined in the AA.ACTIVITY.CLASS application of the
appropriate activity class is being triggered. When the activity LENDING-CHANGE-PENALTYINT is performed. The
difference between the actual and simulated activity is instead of AA.ARR.XXX application AA.SIM.XXX applications
are being updated for a simulated activity. From this, you must understand that a different set of applications are
being updated. Now, what happens to the action routines. Since we are only capturing data, at this point the action
routines will not be triggered. Basic validations will take place so that junk data is not captured. A new activity type
has been introduced for simulation called SIMULATION for the AA.ACTIVITY.CLASS application.

Guide (R18) (English) 2019 Q2 24

 . Overview
Core Banking AA Tech nical . $ TEMENOS
Lea rn i ng Commun ity

The purpose of this type is to specify that a particular activity class can be used only for simulation, this particular
activity cannot be made LIV E. This means that LENDING-CALCULATE-PAYOFF can be used only for simulation.

y I ss LENDING-CHANGE-INTEF. I
.__-=====--'

GB Description ,Change Interest calculation

Full Description :change Int erest calcu lation and recalculate P a ment Schedule.

r A c t i o ns

Property C lass
Typ e Lsat ch
Action
1 Audit7
Use r I n put
l:N1ER£ST UPDAll: YES
PAYME NT. SCHEDULE CALCULA1E 'YE S
ACTIVITY. RESTRICTION 1 EVALUA1E NO
ACTIVITY.CHARGES :cALCULA1E NO
ACTIVfrr.MESSAGING I SEND.MESSAGE NO

(R09 Model Bank)

GB Description Payo ff calcula te acti v i ty

F u ll D escri p tion Payoff C4 lcula te activity
Actions LJ Type Ba tch Audit
!A cti v i ty Typ e . 1 SI MU LAT I ON
Activity Typ e . 2 NO REVERSE
Activity Type . 3 USER
Figure 25 AA.ARRANGEMENT.ACTIVITY & AA.SIMULA TION. CAPTURE

AA.SI M U LATION.CAPTU RE
AUTO.RU N Field
There is a field called AUTO.R U N in the application AA.SIMULATION.CAPTURE. This field will be used in scenarios
where there is only a minimal change that a user wishes to simulate immediately after the data is captured. This
field can accept three values. SIMULATE - When this field is set to SIMULATE, on authorising the
AA.SIMULATION.CAPTURE record, the captured data will be simulated. EXECUTE - When this field is set to EXECUTE,
on authorising the AA.SIMULATION.CAPTURE record, it would execute the simulation (make the simulation LIVE),
provided a simulation of the captured data has been already performed.

Guide (R18) (English) 2019 Q2 25

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

DIRECT.EXECUTE - When the AUTO.RUN field is set to DIRECT. EXECUTE, the two steps of first simulating and then
executing the simulation is avoided. Instead, as soon as the data is captured and AA.SIMULATION.CAPTURE record
is authorised, the captured data is executed (made LIVE).
AA. IMULA TIO

Arrangemen t R ,,If Grrlfn

Activity DEPOSITT• .NEW•ARRANGEM£HT
Effective Date 05 JUL 20 1 0 5 UL 2 1 0
customer 100336 R U G I ng
Product 1
1D. 1 . SHORT. TERM, h r T rm 01r o 1
Currenc.y USD I OOll!lt
Channel
Arr Comp.my Code
Linked Activity
lnlttatlon Type. 1 USER
ReservedZ
Adj A.Ctlvi ty, I
Adj S ta tus. 1
Child Activ lty. 1
Orig Con tract Date
Master Aaa .. -
AAS IM1 0 t 86007HXBM5

Activity Class l oEPOS ITS- NEW-ARRAN GEMENTj

Property. 1 [C OMM ITMENT! Commi tmen t
Effective. 1
Field Nam e . 1 . 1
Field Valu e . 1 . 1 l 25T
Field Nam e . 1 . 2 !TERM
Field Value . 1 . 2 l 6M
Auto Run r. Ulone] r D1rect Execu te r Execu te r Si mula te I
Sim Run Ref ! AAS IMR1 0 1 8607HX8M6

Figure 26 AUTO. RUN Field

Related Activity
Consider a scenario, you wish to simulate a new arrangement, you also want to disburse the amount committed as
soon as an arrangement is simulated. In that case, AA allows you to attach an activity as a related activity. So, all
that you need to do is attach LENDING- DISBURSE-COMMITMENT (the activity of LENDING-DISBURSE­
T ERM.AMOUNT) as a related activity for LENDING-NEW-ARRANGEMENT. If this is done, then, every time the activity
LENDING-NEW-ARRANGEMENT is triggered, LENDING- DISBURSE-COMMITMENT (the activity of LENDING­
DISBURSE-TERM.AMOUNT) will also be triggered. A new field called RELATE D.ACTIVITY has been introduced. This
field is used to specify an activity that needs to be triggered automatically after the current simulated activity. The
activity specified using this field should be a valid entry in AA.ACTIVITY application. For an activity, there can be only
one related activity. RELATED.ACTIVITY field holds good only for simulations and not for LIVE arrangements.

Guide (R18) (English) 2019 Q2 26

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

What you see here is the AA.ACTIVITY record for LENDING-NEW-ARRANGEMENT, the field RELATED.ACTIVITY has
a value LENDING-DISBURSE-COMMITMENT. This means that LENDING-DISBURSE-COMMITMENT is the related
activity for LENDING-NEW-ARRANGEMENT, that is after the LENDING-NEW-ARRANGEMENT activity is completed,
LENDING-DISBURSEMENT-COMMITMENT will be triggered. You have been learning so far that activities are
instances of activity classes. The activities inherit their characteristics from the activity classes. Does this mean that
the activities that can be linked as related activities are controlled at the activity class level? Yes, it is. If you check
the AA.ACTIVITY.CLASS entry for LENDING-N EW-ARRANGEM E NT, you will notice that LENDING-DISBURSE­
T ERM.AMOUNT has been set in the field RELATE D.ACT.CLASS. This means that for an activity created for LENDING­
NEW-ARRANGEMENT activity class, only instances of LENDING-DISBURSE-TERM.AMOUNT can be added as a related
activity.

j AA Ac tivity LE NDING-NEW-ARRANG·! I�-----�

A A A ctivity Audit
--'--------------------- -----1
GB Description New Activity For Arrangement
Full Des c ription System Created]
Related Activity LENDING- DIS B URSE-COMMITME NT Dis burse A ctivity Fo( Commitment
System Activity YES

A A .AC TIVIT Y.CLAS -

LE NDING-NEW-ARRANGI
.. · - �----�

GB Description New arrangement

--,

! cteates ne� at tangement �i th the ptoduct

condi tions def ined in the associated ptoduct
'record.
Full Desc

Attribute. 1 v,
Activity Type. 1 • USER
Batch Name. 1
Batch Seq. 1
,..__-11>1 Relate d Act Class LE NDING- DISBURSE-TER/\1\. AMOUNT

Figure 27 Related Activity

Guide (R18) (English) 2019 Q2 27

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

AA will not allow you to attach activities apart from the ones defined in the activity class to be attached as a related
activity. An error would be generated on doing so.
A A .AC TIVITY.CLASS LENDING·NEW·A�N � �----�

GB Description
!C:ceates ne1o1 a:c:cangement 1o1ith the p:coduct

Full Desc
°"
! conditions detined in the associated p:coducc

Attribute. 1
I" ' V

A ctivity Type. 1
Batch Name. 1
Batch Seq . 1
1------------------
1 Related Act Class JLE NDING-DISB URSE-TERM. AMOUNT I

AA A \ivity LENDING-N EW-ARRANGI �---�

X Related Activity ACTIVITY DOE S NOT MATCH WITH RE L ATED ACTIVITY LE NDI NG- CEC REASE·TE R/1/'.. AMOUNT

AA Activity Audit
GB Description
�--==-- - - - - - - - --
• !New Activity For Arrangement
System Created

Full Des cription *

Attribute. 1 V

--------� Related Activity LENDING-DECREASE-COMMITMENT J Dec rease Activity For Commit ment

Figure 28 Related Activity

Guide (R18) (English) 2019 Q2 28

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

What you see here is a new simulated arrangement, the activity triggered here is LENDING- NEW-ARRANGEMENT.
If you look at the activity logs for this arrangement, there is a disbursal activity of COMMITMENT (LENDING­
DISBURSE-COMMITMENT) property has taken place.

as 07 JAN
Arrangement Overview
· (S"1 m u I ate d)
of 2009

A r r angeme nt : AA09007WLXMM Account : 4 37 1 8 • USO s,mulat,on: AASIMR090070 1 -I LZ 3-I

Painama City Pi odut l Personal lo-an Sirnu l•l ion P.- lod 07 JAN 2009 to 07 JAN 2009
Ai 1 •nr:c: meru D•1c 07 JAN 2009 Stahn Current
l�ew Ac tMty For
07 JAN 2009
f;mne.cmcnt
Arran1ement Conditions

A<(Olhl\ � U1t i,c SinmLlted Account Details

T i t le Per:;onal loan
f1fl:111C li\ l Ac e.aunt o.,te-s Simut.i1ed

Co111m i Hnon1 Si1111ul.litcd Summ 1, r y St.o1rl Obie 07 JAN 'l009

A mount 1 ,ro'.).00 Tc, m IY Co1multma nl ( l ohl) 1 ,00:,.0Q P,3yment st,ut

,. JAN 'l009
Date
Total Pr ncipi1t 1 ,00).0Q �
ti � P•ymcnt Oue 1• JAH 2009
07 JAN 20 10
Pen.- lt )' lnte1 c1t 0-,orduc S1,1lu1:
H.aturity Date
Loan Base R�te + .5%
matures V, 1 Years
Sintlc R-'tc V•rl•ble
P, tndp.t l h 1 1c, c\
Sine.le R.-tc Fixed 6.35% (Lo•n Int Rote • .25%)
Pcno\ tt )' lnt�1 01 1 Sfnau�tc-d Additional Details l.,;ctn.ity Lggj Bills Schedule
inc.lo R.&to V•rl•blo loi,n BMo Rate • ,5,%

j
Activity Loe
Pr fnclp"I IMcrc\ Simul.iitc-d
I 0411te Activity Typc Amount status
Smc.lo k"tc Flxod 6.35% (lo•n Int Rato • .25%)
No ActMtlos P<ooln&
Re1,.-ymen\
�c hedu1e
Sh•ut.ltcd r:n WI Dubu rsc ActMly For
l)(n 1000,00 Authorised
2009 Coomilm'11t
C omt,u,t
1,.86 OIJe \fl'eeklY Authorised
Rt!1J,\ y 1nent : Ne¥, Activity For Ar rartaemenl lite r

Figure 29 Related Activity

AA.SIMULATION.RUN N ER
You have just now learned how to do a data capture. The next step after data capture is to simulate the captured
data. The application AA.SIMULATION.RUNNER is used to simulate. A record in AA.SIMULATION.RUNNER is
automatically created on setting AUTO.RU N field to SIMULATE in the AA.SIMULATION.CAPTURE application.
Authorising the AA.SIMULATION.RUNNER record generates an OFS string for the SIMULATE or EXECUTE actions. If
the AUTO.RUN field was set to SIMULATE, it would generate an OFS string for simulation if AUTO.RUN field was set
to EXECUTE, the OFS string to actually execute the simulation would be generated. As we are in the simulation
stage, setting AUTO.RUN field to SIMULATE would suffice. If you plan to create AA.SIMULATION.RUNNER record
manually, then, during data capture, set AUTO.RUN field to blank and create a record in AA.SIMULATION.RUNNER
and specify the simulation capture reference manually. The OFS string is stored in the file
AA.SIMULATION.SERV ICE.LIST, from where it will be picked up by AA.SIMULATION.SERVICE for further processing.
What you see here is a sample AA.SIMULATION.RUNNER record. You will learn about certain fields of this record
that is vital for you to understand at this point of time. ARRANGEMENT.REF: This field is used to specify the
arrangement for which the simulation is to be executed. SIM.RUN. DATE, SIM. END. DATE : A Simulation is run for a
period. You can specify the period using the SIM.RUN.DATE and SIM. END.DATE fields. The former field is used to
specify the start date and the later field is used to specify the end date for the simulation. SIM.CAPTURE.REF: This
field is used to specify the simulation capture reference that has to be executed by this simulation runner record.

Guide (R18) (English) 2019 Q2 29

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Multiple simulations can be run using a single simulation runner record. You need to multi-value this field and
specify the simulation capture reference IDs.

AA . IMULATION .RUHN fR AASIMR0900704I.________,� ank)

G B Descripti o n A A SIM09007004QPMC R - 1 j
Arrangement Ref AA09007P90)0(j
Sim Currency USO Sim C a pt u re Ref. 1 1 A A SIM09007004N SX95

Sim Run Date

7
07 JA N. 2009 Sim C a p t u re Ref.2 ; AA SIM09007004NSX95

Sim E n d Dat e 0 7 JAN 2009 St atus )COMP LETED - S UCCESSFU L L Y 1

Sim U Dat e . 1 07 J A N 2009

U A ctivity. 1 . 1 LE N DING- U P DATE-C USTOMER !
U Run St age . 1 , 1 USERi
Ru n U Act. 1 . 1 YES
Sim C a pt u re Ref. 1 A A SIM09007004QPMC R I
Status C OMPLETE D - S UCCE S S FU L LY

Figure 30 AA.SIMULA TION. RUNNER

• S.ACTIVITY: This field is used to specify that a scheduled activity has been simulated.
• SIM.S. DATE: This field denotes the date on which a scheduled activity has been simulated.
• S.RU N. DATE: This field set to "SCHEDUL ED" specifies that it is a scheduled activity.
• U.ACTIVITY: This field can be used to specify a user activity to be simulated.
• SIM.U. DATE: This field denotes the date on which the user activity has been simulated.
• U.RUN.STAGE: This field denotes that this activity is a user activity. This field will be updated with a value
"USER".
• T.ACTIVITY: This field can be used to simulate transaction activities.
• SIM.T. DATE: This field denotes the date on which the transaction activity has been simulated.
• T.RUN.STAGE: This field will be updated with a value "TRANSACTION" to specify that it is a transaction
activity.

Guide (R18) (English) 2019 Q2 30

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

• STATUS: This field denotes the status of the simulation runner record. It can have three possible values as
follows: COM PLETED - SUCCESSFULLY, this denotes that it was a successful execution. COMPLETED - ERROR,
this denotes that runner is completed execution but with errors. Processing, this denotes that runner is still
running.
AA .SIMULATIOH .RUtlHER MSIMR0900 703Y
=7=Zd
� l�----�I

GB Description �--
- --
- - ­
rAASiM09007003Y7Z5J • 1
Arrangement Ref �0074VW�
.... - -.

06 CEC 2009
Sim Curren cy
:07 JAN 2009
Sim S Date. 1 18
Sim Run Date
p7 CEC �09j
S Activity. 1 18. 1 LE NDING-ISSUE.CHASER-O\/ERDUE"NAB
Sim E n d Date
S Run Stage. 1 18. 1 SCHE DULED!
>im > Uate. 1 14 J A N £\JU'l' I
Run S Act. 1 18, 1 'YE:s
07 JAN 2009
S Activity. 1 . 1 I LENDING:jssUEB ILL-REPAYMOO. SCHEDULPCONSTANT
Sim U Date. 1
S Run Stage. 1 . 1 � DUL_§]
U Activity. 1 , 1 LENDING-NEW-ARRANGEMENT
Run S Act. 1 . 1 �
S Activity. 1 .2 'LENDIN.G-M AKEDUE-REPAYMENT. SCHEDULE l U Run Stage, 1 . 1
Run U Act . 1 . 1
USER
YES
07 JAN 2009
S Run Stage.1 .2 SCHEouLE.o J
Run S Act. 1 .2 r'!Es Sim T Date. 1

f 1 5 JAN 20Q9
T Activity. 1 . 1 LE NDING- DlSBURSE-COMMITMENTj
Sim S Date.2
T Run Stage . 1 . 1 �ACTIO Nj
1 ,000
S Activity.2 . 1 LENDING-AGE-0\/E RDU E"GRC
T A m ount . 1 . 1
S Ru n Stage.2. 1 'SCHEDULE�
r Run T Act. 1 . 1 YES
Run S Act.2 . 1 'YES
Sim Capture Ref. 1 �ll\l\09007003Y7Z5J I
I Status
Sim S Dat e.3 j19 JAN 2009
COMPLETED - SUCCESSFU L LY
S Activity.3. 1 LENDIN G-AGE-0\/ERDUE"a::Ll
S Run Stage.3. 1 , SC HEDULED]
Run S Act.3 . 1 1YES
S i m S Date.4 �O JAN 2009
S Activity.4. 1 . LENDING- ISSUE.CHASER- 0\/ERDUE"CELl
S Run Stage.4. 1 fSC HE olill?)
Run S Act.4. 1 'YES
I

Figure 31 AA.SIMULA TION. RUNNER

• RUN.ACTIVITY: This field is used to specify if a user activity needs to be simulated or not. A value "YES"
denotes that the activity needs to be simulated, a value "NO" specifies that the activity should not be
simulated.
• EXECUTE.SIMULATION: This field allows the user to execute the simulation. On setting this field to YES will
make the simulated information to LIVE.

Guide (R18) (English) 2019 Q2 31

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Note that while simulation data capture phase, the action routines are not triggered, but during the simulate phase
and execute phase the action routines are triggered, the only difference being, data is not updated onto the
database during the simulate phase but data updates (make LIV E) takes place during the execute phase.

A A IMU TIOt -� 1 tffR MSIMR090070 3Y7 Z>; I.__________.I

Sim S Dat e. 1 18- �of etc-2009

t 1 1 8. 1
S A ctivty. LENDING-ISSUE.CHASER-O\1£ RDUE:NAB
S Run Stage . 1 18. 1 SCHEDU LED,
S Amount . 1 1 8. 1
Ru n S Act. 1 18. 1 YES
Reserved 16. 1 18. 1
Reserved 1 5 , 1 18. 1
Reser\l'ed 14. 1 1 8. 1
Reserved 13. 1 1 8. 1
Sim U Date. 1 - -- ---- - -
U Acth.ity. 1 , 1 LE NDING-NEW- ARRANGEMENT
U Run St age . 1 . 1 USE R
U Amo unt . 1 . 1
Ru n U Act. 1 . 1 YES V

Reserved 12, 1 . 1
Reserved 1 1 , 1 . 1
Sim T Date. 1 07 JAN 2009
i
T Activ ty. 1 , 1 ---- ·- MMITMENT
LENDING•0ISBUASE·CO
T Run St age , 1 . 1 TRA NSACTI ON 1
T Amount. 1 . 1 1 ,000
T Ovr Am ou n . 1 . 1
Ru n T Act. 1 , 1 YES V

Res erved 10, 1 . 1

Res erved 09 . 1 . 1
Execute Sim ulatio n @ [M n . ] 0 fo Q y
Figure 32 AA.SIMULA TION. RUNNER

Guide (R18) (English) 2019 Q2 32

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

AA.SCH EDU LED.ACTIVITY$SI M

The $ SIM file of AA.SCHEDUL ED.ACTIVITY application holds the scheduled activities generated for a simulation. The
records from this file are later moved to the AA.SCHEDUL ED.ACITIVITY's live file when the simulation is executed
(made live). What you see here is a list of the FBNK.AA.SCHEDUL ED.ACTIVITY $ SIM file and its contents.
s q > S E L E CT � FROM TAF J _VOC WH E RE RECI O = FBNK . AA . SCHEOUL E O . ACTIVITY SIM ;
RE CI O I STRRE CORO
I ORCL FIL ENAME I
ORCL OI CTNAME I I SBLOB I ISRIGHTJ U STI FI E O I I S REAOONLY I ASSOCIATED I
P OATEAL IAS
FB NK . AA . SCHEOUL E O . ACTIVITY$SIM I F AA s c h edu l ed act i vi t y? . . /bn k . data/aa/ FBNK_AA_
SCH E DU L E O_ACTIVITY#SIM? . . /bn k . di ct/F_AA_SCHE OU L E O__ACT I FBNK__AA_SCHEOULEO_AOOl I
D_F__AA_SCHEOUL EO__ACOOO I T I N I nul 1 I nul 1 I
nul l
(data i s parti al l y t ru n c ated)
(1 r ow , 16 ms )
s q l > S E L E CT RE CI O FR,_O M FBNK__AA_S CH E OU L E O__AOO l ;
RECI O �
15 08 39ZN B K%AASIMR15 08 3 5 G J 69HZ
15 08 3S698X%AASI MR15 08 3 5 G J 67 3L
1 5 08 3B B 4MHroAAS I MR1508 3 5 G J 6 388
1 5 08 3Q7 M4K9'oAASIMR15 08 3 5 G J 66 2 B
1 5 0 8 3 2 VB GS%AASI MR1 5 08 3 5 G J 67 B 4
1 5 0 8 3 H P B 7 X9'oAASIMR15 08 3 5 G J 64M5
Figure 3 3 AA.SCHEDULED.ACTIVITY$SIM

Points to Ponder
Certain points to remember. Overrides are accepted by default during the simulation. The
AA.SIMULATION.RUNNER record will hold complete information about the activities that have been performed on
executing the simulation. The same simulation runner record can be amended for further simulations. If ad-hoc
activities are to be added, the date on which the activity had to be run should be specified, also RUN.ACTIVITY field
should be set to YES.

AA.SIMULATION.RUN N ER - Authorise
On authorizing the AA.SIMULATION.RUNNER record, an OFS string is generated for the simulation in a file called
F<COMPANY MNEMONIC>.AA.SIMULATION.SERV ICE.LIST. The record id is of the format <Simulation Runner record
ID>.SIMULATE. What happens to this OFS string? Who processes it?

Guide (R18) (English) 2019 Q2 33

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

To process the OFS strings generated as a result of simulation you need to run a service called
AA.SIMULATION.SERVICE. AA.SIMULATION.SERVICE looks for the activation file AA.SIMULATION.SERVICE.LIST.
s q l > SEL E CT * FROM FBN K_AA_S I MULATION_OOO ;
RE CIO I STRRE CORD
SIMR1 5 11299688G 5 . SIMULATE I AASIMR15 11299688GS ~AASI M15 112P99687 00~2 0 1 5 04 2 2 ~AA .
RRANGEMENT . ACTIVITY , /I/PROCESS//0/ , //GB OOlOOOl///
(data i s parti al l y t r u n cated)
( 1 r ow , 16 ms ) �
sql >
SIM R 1 5 112 99688G5~AASIM 1 5 112 P996870()rv20150422~AA . ARRANGEMENT . ACTIVITY , /I/PROCES
SJ /0/ , / /GB0010001////l/AAS.IMR15 11299688G 5 , , ARRANGEMENT : 1: l="AA15 112 5GlS L " , ACTIVI
: l : l= " LE N DI NG - NEW-ARRANGEMENT" , EFFECTIVE . DATE : l : 1= " 201 5042 2 " , CUSTOM ER : 1 : 1= " 100
100 " , PRODUCT : l : l= " HELOC " , CURRENCY : l : l= " USD" , I NITIATION . TYPE : l : l= " USER " , PROPERTY :
l : l= " P RINCIPAL INT" , PROPE RTY : 2 : l= " SCHEDUL E " , EFFECTIVE : l : 1= " 202404 2 2 " , E FFECTIVE : 2 :
1= " 202404 2 2 " , FIELD . NAME : 1 : l=" P ERIODIC . RATE : 1 : 1 " , FIEL D . NAME : 1 : 2 = " I D . COMP . 6 : 1 : l" , F
IELO . NAME : l : 3= " IO . COMP . 6 " , FIEL O . NAM E : l : 4=" I D . COMP . 6 " , FIEL O . NAME : 2 : l= " PAYM ENT . TYP
E : l : 1" , F IELD . NAME : 2 : 2 = " PROPERTY : 1 : l" , F IELD . NAM E : 2 : 3 = " PROPERTY : 1 : 2 " , FIEL D . NAME : 2 :
= " DUE . FREQ : l : l" , FIELD . NAME : 2 : 5 = " DUE . FREQ : l : 2 " , FIELD . NAME : 2 : 6 = " P E RCENTAGE : l : l" , F
IELD . NAM E : 2 : 7= " P E RCENTAGE : 1 : 2 " , FIELD . NAME : 2 : 8 = " BILL S . COMBINED : l : l" , FIELD . NAM E : 2 :
9="0N . ACTIVITY : l : l." , FIELD . N AME : 2 : 10= "0N . ACTIVITY : 2 : l" , FIELD . NAME : 2 : ll="ON . ACTIVI
: 3 : 1" , FIELD . NAM E : 2 : l.2="0N . ACTIVITY : 4 : 1" , FIELD . NAM E : 2 : 1 3 = "0N . ACTIVITY : 5 : l" , FIEL
. NAME : 2 : 14="0N . ACTIVITY : 6 : l" , FIELD . NAME : 2 : 15 = "0N . ACTIVITY : 7 : l" , FIELD . NAM E : 2 : 16=
"ON . ACTIVITY : 8 : l " , F IELD . NAME : 2 : 17= "0N . ACTIVITY : 9 : l " , F IELD . NAM E : 2 : 18= " RECALCULATE
: 1 : l" , FIELD . NAME : 2 : 19= '' RECALCULATE : 2 : l" , FIELD . NAME : 2 : 20='' RECALCULATE : 3 : l" , FIELD .
NAME : 2 : 2 l= " RECALCULATE : 4 : l " , FI E L D . NAM E : 2 : 2 2 = " R ECALCULATE : 5 : l " , F IELD . NAM E : 2 : 2 3 = "
ECALCULATE : 6 : l" , FIELD . NAME : 2 : 24=" RECALCULATE : 7 : l" , FIELD . NAME : 2 : 2 5 = " RECALCULATE : 8
: l" , FIELO . NAME : 2 : 2 6= " RECALCULATE : 9 : l " , FIE L D . NAME : 2 : 2 7= " IO . COMP . 6 : l : l " , FI EL D . NAME
: 2 : 28= " I D . COMP . 6 " , FIELD . NAME : 2 : 2 9 = " I D . COMP . 6 " , FIEL D . VALUE : 1 : 1= " 0 . 84 2 " , FIELD . VALU
E : l : 2= " R ' _ ' ANNIVE R SARY + 9Y" , F IELD . VAL UE : l : 1 = " R ' ' _ ' ' ANNIVERSARY + 9Y" , FIELD . V,A.LU
E : 1 : 4 = " R ' ' _ ' ' ,ANNIVERSARY + 9Y" , FIELD . VALUE : 2 : l= "CONSTANT" , FIELD . VALUE : 2 : 2 = " ACCOU
NT" , F IELD . VALUE : 2 : 3 = " P RINCIPAL I NT " , F IELO . VALUE : 2 : 4=" e0Y elM eOW eOD eOF " , F I EL D .
ALUE : 2 : S = " eOY elM e OW eOD e0F" , FIELD . VALUE : 2 : 8= " YES " , FIELD . VALUE : 2 : 9 = " L E NDING- DI
SBURSE -COMMITME NT " , FIELD . VALUE : 2 : 10:: " L E N DING-CHANGE - SCHEDUL E " , FIELD . VALUE : 2 : ll= "
LENDING -CHANGE . TERM -COMMITME NT" , FIELD . VALUE : 2 : 12= " L E N DING-AUTO . DISBURSE -COMMITME
NT" , FIELD . VALUE : 2 : 1 3 = " LE N DING-C.HANGE - PRINCIPALINT " , FIELD . VALUE : 2 : 14= " LENDING-C.
NGE . CONDITIO N - PRINCIPAL I NT" , FIELD . VALUE : 2 : 1 5 = " LENDING-ADVANCE . RESET-PRINCIPAL I N
" , FIELD . VALUE : 2 : 16= " LE NDING-ADVANCE . CHANGE - P RINCIPALI NT " , FIELD . VALUE : 2 : 17= " LEN DI
NG-PERIODIC . RESET-PRINCIPAL INT" , FIELD . VALUE : 2 : 18= " PAYME NT" , FIEL D . VALUE : 2 : 19= " PA
�ENT" , F IELD . VALUE : 2 : 20=" PAYMENT" , FIELD . VALUE : 2 : 2l="PAYM E NT" , FIEL D . VALUE : 2 : 2 2= " P
E NT" FIEL D . VAL UE : 2 : 2 3 = " PAYM E NT" , FIELD . VALUE : 2 : 24=" PAYM E NT" , FIELD . VALUE : 2 : 2 5= " P
YMENT 1' , FIELD . VALUE : 2 : 26="PAYMENT" , FIELD . VALUE : 2 : 27= " R ' _ ' ANNIVE RSAR.Y + 9Y " , FIEL
. VALUE : 2 : 2 8 = " R ' ' _ ' ' ANNIVE RSARY + 9Y " , FIELD . VALUE : 2 : 2 9= " R ' ' _ ' ' ANNIVERSARY + 9Y" , S
IM . RU N . REF : l : l= " AASIMR151.1299688G 5 " , ~USER~LENDING - N EW- ARRANGEMENT
(1 row , 0 ms )

Figure 34 AA.SIMULA TION. RUNNER - Authorise

AA.SIMULATION .SERVICE
There is a service available in AA called AA.SIMULATION.SERVICE to process the simulation. This service does the
actual job of simulation and execution of the simulation. It stores the data in the required files, like the $ SIM files
eg. AA.ARR.TERM.AMOUNT $ SIM and F.SIMULATION.DETAILS, you will learn about these files a little later during
the course. it also updates the AA.SIMULATION.RUNNER record with the status of the simulation, like "COMPLETED
- SUCCESSFULLY" or "COMPL ETED - ERROR" etc. What you see here is the screenshot for the service, if you notice,
it is company specific. You can set the SERVICE.CONTROL field as a START or AUTO depending on how you wish to
run this service. It would be ideal to set it to AUTO and let this service run throughout the day. If you look at the
PGM. FILE entry for the service routine, the ADDITIONAL.INFO field has been set to . NTX. This again means that the
transaction management is not done by BATCH.J OB.CONTROL but by some other method. Here
OFS. BULK.MANAGER takes care of transaction management for this service.
ISA .S ERVIC E 1BN1<,1M.SIMULATI ON.SER\l I I I
�GM .FILE AA.SI MULATION SERVI!

Description. 1 I AA SIM I TYPE �

Work Profile . 1 I A A . SIMULATION. SERVICE I Simulati on Service
Use r IINPumE] INPUffiR .JOB.CONTROL
Service Control I START[ I Product §]

Activation File �
Figure 35 AA.SIMULA TION.SER VICE

Guide (R18) (English) 2019 Q2 34

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

On running the service, it picks records from the F<COMPANY M N EMONIC>.AA.SIMULATION.SERVICE.LIST file and
starts processing.
TSA .S ERVIC E I TSM I irsA .s rnv1c E I BNK/M.SIMULATION. SE R\

Description. 1 ITSM Record for running upgrad e as service I Description. 1 IAA SIM I
Work Profi le . 1 ITSMI W O RK L O A D PROFILE FOR TSM Work Profi le . 1 IA A , SIMULATION. SERVICE I Si m u lati on S e rvi c e
Use r IA UTH ORISERI AUTHORISER Use r IINPUTTERI I N P UTTER
Service C o ntrol I STA RT! Service C o ntrol ISTA RTI

Figure 36AA.SIMULA TION.SER VICE

Execute Simulation
When the simulation is being brought to live on executing the simulation (either using AA.SIMULATION.CAPTURE
application's AUTO.RUN field or AA.SIMULATION.RU NNER application's EXECUTE.SIMULATION field, an OFS record
with id <Simulation Runner record ID>.EXECUTE is created. Again, the service AA.SIMULATION.SERVICE is required
to process this OFS string. The F<COMPANY MNEMON IC>.AA.SIMULATION.SERVICE.LIST file is the list file for this
service. It is ideal to run this service continuously.

Arrangements
AA.ARRANGEM ENT.SIM
Intro: You might want to ask a question saying, where does the information related to simulated arrangement get
stored? Is there an application similar to AA.ARRANGEMENT or will the application AA.ARRA NGEMENT will be used
for simulations? What happens to the new arrangements being simulated? They cannot be stored in
AA.ARRA NGEMENT application because they are not LIVE arrangements. To answer all these questions, there is an
application called AA.ARRANGEM ENT.SIM that has been introduced to store details about arrangements that are
simulated, it can either be a new simulated arrangement or an activity simulated on an existing LIVE arrangement.
It holds data similar to that of AA.ARRANGEMENT application. Try and compare AA.ARRANGEMENT and
AA.ARRA NGEME NT.SIM, both the applications would store similar information.
- -- ...
AA .ARRAHGEM Elff M09007P90X><
-
[AA -ARRAHGEMEIH .SIM M0�007P90X>(l

Customer 100300 figuado C ustomer Agu ado

Currency USD US Do ll;;r C u rrency US Dollar
Arr Status AUTH Arr Status
Start Date 07 JAN 200� Start Date 07 JAN 2009i
Linked Appl. 1 ACCOUNT Linked Appl. 1 i A�CO UNTj
Linked Appl ld. 1 43m l Linked Appl ld. 1 143m,
Product Line LENDl � ij j Retail Term l e n ding Product Line �ENDING Ret ail Term Len ding
--- - -,
Product Group I PE RSONAL. LOANS I Per.;onal L o an: Product Group PE RSONAL.LOANS
- - Per.;on�l L o a ns
Product . 1 PERSONAL. LOAN Pe!"!onal Loan Product . 1 !PE RSONAL.LOAN Per.;on� l Loan
Prod E ff Date. 1 07 JAN �01) Prod E ff Dat e . 1 !07 JAN 2009 '
Property. 1 . 1 ACCOUNT Account Property. 1 . 1 ACC OUN] Account
Property. 1 .2 COMMITME� Commitment Property. 1 . 2 !£2._MM ITMENT l,;ommit men
Property. 1 . 3 PRINCIPAL INT j Principal Int ere-st Property. 1 .3 'PRINCIPAL INT' Pnnolpal In erest
Property. 1 . 4 PENALTYI NTj Penalty Interest Property. 1 . 4 I PENALTYINT Penalty Interest
1

Figure 37 AA.ARRANGEMENT.SIM

Guide (R18) (English) 2019 Q2 35

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

AA.ACTIVITY.HISTORY.SIM
You know by now that the application AA.ACTIVITY. HISTORY is used to store log about the list of activities that have
taken place on an arrangement. Likewise, to trace the information about the simulated activities that have
happened on an arrangement, you can refer to a new application called AA.ACTIVITY. HISTORY.SIM. If you look at
the AA.ACTIVITY. HISTORY.SIM record above, it holds the AA.SIMULATION.CAPTURE id instead of
AA.ARRANGEM ENT.ACTIVITY. It holds details about the simulated activity called LENDING-CHANGE-PRINCIPALINT
that has happened on the arrangement AA09007 P90XX.

A .A IVI AA09007P90>0<

Effective Date. 1 07 JAN 2009

Activity Ref. 1 . 1 A ASIM0900700 5F83 L3
Activity, 1 . 1 LENDING-CHANGE-PRINCIPALINT han e Acti 't For Ptin ipalint
System Date. 1 . 1 07 JAN 2009
Act Status. 1 . 1 1 AUTH
lnitiation. 1 . 1 USER
Activity ld. 1 LENDING-CHANGE-PRINCIPALINT han°e Activit r F . r Prinripalint
Act Date, 1 . 1 07 JAN 2009
Act Count. 1 . 1 1
Tot A ct C nt. 1 . 1 1
Figure 38 AA.ACTIVITY.HISTORY.SIM

$SIM Files
While you were learning about AA.SIMULATION.SERVICE, you would have come across a term called $ SIM and
F.SIMULATION. DETAILS. You will now learn about these files in detail.

Guide (R18) (English) 2019 Q2 36

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

The $ SIM is a new file type that has been introduced in Core Banking for simulation. As the name suggests, these
files are used to hold the simulated copy of a record.

fll . tHR AA.ARR.INTERES (RD9 Model Bank)

j

Description. 1 Arrangement Interest Prop '

Product AA
Suffixes. 1 $H IS

I
Suffix es.2 $NAU
Suffixes.3 $SIM
Fi le Typ e 2'
Fi le M o d u lo 17
Classifi c ati o n FI N

I s�S u b Product
Clear Files
I
MAINTE N A NCE

y
Cus Clear Fi les
Bran c h Fi le BAF
Re lat ed Fi le . 1 AA . P RO PE RlY.CL A S S !
Local Ref Mast e r A A . P RD. CES. I NTE RE ST
Sim Reqd Y
Figure 39 $SIM Files

What you see here is a list of the simulated records of TERM.AMOU NT property class. The id of these files would
be of the format <Arrangement ID>- < Property>- < Effective Date>. < Sequence Number>% <AA.SIMULATION.RUNNER
Id>. When a simulation is performed, the simulated data for a property is stored in these files. This is a sample
FILE.CONTROL record for the application AA.ARR.INTEREST that is used to hold the arrangement conditions for
INTEREST property class. A new suffix $ SIM has been included for this application wherein the simulated
information for INTEREST property class will be stored.

ACTIVITY. PRESENTATION
You know that all the simulated arrangement conditions are stored in an application called
AA.ARR. < PROPERTY.CLASS>. When you define product conditions for ACTIVITY.PRESENTATION property class for
your product, you create versions for applications that are prefixed with AA.ARR. < PROPERTY.CLASS>.

Guide (R18) (English) 2019 Q2 37

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

Does this hold good for simulations? As you recall, the simulated arrangement conditions are stored in an
application prefixed with AA.SIM.< PROPERTY.CLASS>.
Least Specific Most Specific

Property Class Property Activity

Figure 40 ACTIVITY. PRESENTA TION

A new set of fields have been introduced for ACTIVITY.PRESE NTATION property class, where in you can attach
versions at all the levels like property class, property and activity like before for simulations. The only difference
being that the versions will be those that have been created for AA.SIM.< PROPERTY.CLASS> applications.

[A A . PRO . D ES . AC TIV ITY . PRES ENTATION PERSO MAL. LOAN-20081 2Q

G B Description P e rs o n a l L o a n Prese n ta ti o n
Property C lass . 1 TIRM. AMO U NTj T e rm .£I. m o u n t
Class Ve rs i o n . 1 AA .ARR. T E RM . A MOUNT ,AA . S I MPL Ej T e rm A m o u n t
Class S i m Ve r . 1 IAA . SI M . T E RM.A.MO U NT , AA . S I MPLE Term Amount

P ro p e rty. 5 PRI N C I PA L I NT Principal I nte re s t

Prop Ve rs i o n . 5 IAA .A RR . I NTEREST , AA . P ERI OD I C 1 P e r i o d i c Rate
Prop S i m Ver . 5 'AA . SI M . I NT E REST,AA . F I XE D Ra te

A cti v i ty I d . 1 1 L E N D I N G - N E W-ARRANGEMENTl N ew Activ i ty F o r Arrange m e n t

A ct Property. 1 1 . 1 RE PAYMENT . S.C H E D U L E , Repayment Schedule
A ct Vers i o n . 1 1 . 1 AA . A RR. PAYME NT . SC H E D U L E , AA . SI MP L E Re p aym e n ts
A ct Sim Ver . 1 1 . 1 AA . S I M . PAYMENT . SC H E D U L E ,_!�.A . SI MP L E Repaym e n ts

Figure 4 1 ACTIVITY. PRESENTA TION

What you see here is a sample ACTIVITY.PRESENTATION product condition by name ACTPRESENT. There are
versions attached at the property class level, property level and activity level using the field CLASS.VERSION,
PROP.VERSION and ACT.V ERSION. Simultaneously you can also define versions to be triggered for simulations at all
the three levels using the fields CLASS.SIM.VER, PROP.SIM.V ER, ACT.SIM.VER. (CLASS.SIM.VER for the property
class, PROP.SIM.V ER for the property and ACT.SIM.V ER for the activity). At this point of time you would also like to
know about a routine called AA.ARR.FETCH.PRESENTATION.DETAILS. This routine is actually responsible for loading
versions for simulation. When there is no version defined for simulation at the ACTIVITY.PRESENTATION product
condition level, then it by default invokes the application screen. For example, if a version has not been defined for
T ERM.AMOUNT property class for a simulation(at the product condition for ACTIVITY.PRESENTATION), then this
routine will invoke the default application screen line AA.SIM.TERM.AMOUNT.

Guide (R18) (English) 2019 Q2 38

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

SIM.READ
You will now learn about a new routine called SIM.READ designed to read simulated records. There are many files
being updated during a simulation like the $ SIM files, the AA.SIM.XXX files and F.SIMULATION.DETAILS. SIM.READ
is responsible for fetching the record from the appropriate file. You will now see how this routine works. This routine
is responsible for fetching the simulated version of a record. It does the following:
• Checks if there is a $ SIM file for the record
• If yes
■ It checks if the simulation record exists
• If yes, it reads from the simulated record
• If not, it reads from F.SIMULATION.DETAILS
• If the routine is not able to find a simulation record in both the $ SIM files and F.SIMULATION.DETAILS, it
reads from the LIVE file by calling F.READ.

I_AA.SIM.COMMON
A new insert file has been introduced for Simulations. It holds simulation related to common variables. Few
variables are listed below.

Variable P u rpose
aaSimCaptu re flag for simu lation captu re mode
aaSim Ref AA. S I M U LAT I O N . RU N N ER I d

Figure 4 2 /_AA.SIM. COMMON

Row 1 - aaSimCapture is used to hold the flag for simulation capture. Row 2 - aaSimRef is used to hold the
AA.SIMULATION.RUNNER ID.

CFS.BULK.MANAGER
There is a small change that has been done to OFS.BULK.MANAGER for simulation purpose. OFS.BULK.MANAGER
will check if the incoming request is a simulated request. If yes, an after the image of the transaction is captured.
The current transaction is aborted. Finally a call to LOAD.SIMULATION.UPDATES are made within a transaction
block.

Guide (R18) (English) 2019 Q2 39

 . Overview
Core Banking AA Technical . $ TEMENOS
Learning Community

AA.SIMULATION.MONITOR
You can monitor simulations using an enquiry called AA.SIMULATION.MONITOR. The enquiry would tell you the
status of any simulation. What you see here are two simulations, wherein one is successful and the other is not.
m o re oeti ons
Sim Ru n n e r Status Find I
clear s e le ction

Simu la1ion equals I

NO .SORT .OPTION equalsI lvJI I I
GB00 1 0001 : AA, SIMULATI O N . M O N ITOR

Simulation St atus Simulation Status

AASIMR0 900704P 1 LWY
�I I
AASIM RO 900706 20T7B
s ta t u s c o mp l e te d - su cc e ssru llY
_______________________�
A r r "nge ment AA09007K K 1 59
I I� I St.\tUS Completed - Er ror
A, r ange ment AA09007K K1 59
Run Date 07 JAN 2009 Run Oclte 07 JAN 2009
End D"te 07 JAN 20 10 End Date 07 JAN 2009
A tivity C h a nge Activity For Principalint Ac tivit y De c rease Activity For Co m mit ment

Figure 43 AA.SIMULA TION. MONITOR

•••♦

Guide (R18) (English) 2019 Q2 40