Scribd
Upload
520 views

AA Arrangement Notes

The document discusses the AA module in T24 which provides a flexible framework for creating banking products using reusable components. It describes the different types of categories used like product lines, groups, and products which are defined by Temenos or users. Products are constructed by combining various components. The document also covers the product lifecycle including proofing, publishing, and arrangements which are instances of products for customers. Activities on arrangements are defined by activity classes.

Uploaded by

Priyanka Raut
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
520 views

AA Arrangement Notes

The document discusses the AA module in T24 which provides a flexible framework for creating banking products using reusable components. It describes the different types of categories used like product lines, groups, and products which are defined by Temenos or users. Products are constructed by combining various components. The document also covers the product lifecycle including proofing, publishing, and arrangements which are instances of products for customers. Activities on arrangements are defined by activity classes.

Uploaded by

Priyanka Raut
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

AA ARRANGEMENT NOTES

AA module provides a flexible framework that allows a number of t24 modules to be


created.

AA provides a business component based architecture for management of products.

Users can create their own products by using components provided by temenos, these
components can be reused.

TYPES OF CATEGORIES

� PRODUCT LINES -temenos defined

� PRODUCT GROUPS -user defined

� PRODUCTS -user defined

� PROPERTY CLASS -temenos defined

� PROPERTY -user defined

� PROPERTY CONDITION -user defined

� ACTIVITY CLASS -Temenos defined

1. PRODUCT LINES ->defined by temenos

Example: Lending, Internet services, Accounts, deposits, Product Bundle

Lending->Mortgages[legal agreement] (Product grp)->one year mortgage,5 year


mortgage(products)

2. PRODUCT GROUPS -> Defined by user

Ex: Types of account

3. PRODUCTS -> Defined by user

Each product is constructed by combining the various available, reusable components

Ex: Different interest rates

4. COMPONENTS ->Every component has its own attributes and actions defined by
temenos, User activities are constructed by linking actions from multiple
components Ex: Interest,charges, Term amount

Examples: Customer , Account, Limit, Accounting

Consider that a vehicle is a product and transmission, engine, wheel, body are the
components� Similarly term amount, payment schedule, interest , charges are the
components of different banking products

Some of the products are displayed below which are then offered to customers

PRODUCT LINES AND PROPERTY CLASSES

PROPERTY CLASSES ->Component having attributes and actions is called property class
Property classes are defined by temenos

Eg: ACCOUNT

Product lines and property class relationship:-

Product lines are Loans , Deposits and accounts

Property classes in Loans are :Interests, Term amounts and charges

PROPERTY ->Named instance of property class

Users can create new properties based on existing property classes

Consider a car has wheel as a component but it will have types like front wheel and
rear wheel which has different attributes, but they belong to same property class
wheel

Similarly ,for a banking product-Lending product , interest is a property class and


Principal interest and penalty interest are different properties

PRODUCT CONDITION ->set of rules set for a property class.

-Defines default values for its attributes and certain other conditions

- For properties created we must assign some product condition to it

Example: Interest is a property class we can set product condition as fixed rate
set to some specific value

PROOFING AND PUBLISHING

PROOFING AND PUBLISHING why it is needed?

A product must be proofed and published before it becomes ready for use, this can
be done using Product Manager.

Proofing ->proofing validates that product has been configured correctly

Proofing also ensures whether all mandatory properties have been given conditions,
fixing any errors which are generated by product designer while creating product

Publishing ->When product is published it is entered into product catalog which is


used to create further arrangements

ARRANGMENT

Arrangement is an instance of a product for a customer example if a product is sold


to a customer then it becomes an arrangement with the customer.

Ex: arrangement of personal loan with customer(term amount and interest charges are
negotiated)

Product conditions can be negotiated according to cust if allowed

Format of arrangement ID is AAACTYYDDDxxxxx

AAACT arrangement architecture activity


YYDDD Year and date of input in julian date format

Xxxxx System generated unique identifier

FLOW OF ID CREATION

Arrangment activity id created->Arrangment id created->Account record for the id


created

ACTIVITY

-Every operation on an arrangement is an activity

-Activity class defines behavior

-Activities can be created by user /T24 automatically generates by itself

-AA.ACTIVITY.HISTORY -activities generated during both online and cob are stored in
this

Examples of activities-> Reset arrangement, resume arrangement, close arrangement,


Change branch

REVERSE AND REPLAY

Mostly accounting entries are passed f

You might also like