Activity Mapping
The Activity Mapping Property Class provides a link between financial transactions initiated in Temenos Transact outside of the AA module and the activity that has to be processed against the arrangement. Customer initiated or scheduled debits and credits or facility request on an arrangement are accomplished through Temenos Transact applications such as FUNDS.TRANSFER, TELLER, CLEARING, etc. In order for the proper allocation rules to be used, each Temenos Transact transaction has to result in a specific activity, which gets triggered through AA.ARRANGEMENT.ACTIVITY application. This mapping can be done through Activity Mapping. For non-financial transactions facility (Service) request, the qualified events are not mapped with corresponding activity (both one-to-one or default activity) and the corresponding request is ignored.
Product Lines
The following Product Lines use the Activity Mapping Property Class:
- Accounts
- Agent
- Asset Finance
- Bundle
- Deposits
- External Accounts
- Facility
- Lending
- Rewards
- Safe Deposit Box
Property Class Type
The Activity Mapping Property Class uses the following Property Class types:
- Dated
- Merging
- Tracking Only
- Enable External Financial
- Enabled For Memo
Publishing - Merging Property Conditions
With standard business Property Classes (example: Interest), a defined property defined for a child product overrides a defined property specified for a parent product. The ACTIVITY.MAPPING property allows merging of conditions between the child and parent products at the time of publishing.
When published, the Activity Mapping Property Class is merged with the published parent definition as follows:
- The parent record is taken as the base record.
- Property definitions in the child record overrides the parent record definition, if already defined.
- Child property definitions that do not appear in the parent record can be added to the base record.
Property Type
The Activity Mapping Property Class is associated with the Product Only Property Type. The users can create and maintain properties.
Balance Prefix and Suffix
Activity Mapping Property Class does not hold any balances due to which there is no associated Balance Prefix.
Attributes
The following are the attributes of Activity Mapping Property Class.
Action
The Action field links AA to the other applications. When an external (non-AA) application raises a debit or credit movement to an arrangement account, this needs to be translated to an activity on the arrangement. The transaction code of the underlying entry is checked and the associated TXN.ACTIVITY is used. If the transaction code is not specified, the DEFAULT CR ACTIVITY or DEFAULT.DB.ACTIVITY is used based on the sign of the movement. This field is part of a multi-value set with TXN.ACTIVITY. The selected value needs to have a valid record in TRANSACTION.
Activity
This activity performed against an arrangement when a movement with the associated transaction code is posted from an external application to an arrangement account. This field is part of a multi-value set with TRANSACTION. The selected value has to have a valid record in AA.ACTIVITY. The underlying AA.ACTIVITY.CLASS has to be defined with an ACTIVITY.TYPE of Accounting.
Default Credit
The Default Credit field indicates the default AA activity to be used for AA credit transactions. The selected value has to have a valid record in AA.ACTIVITY and activity type has to be set to ACCOUNTING.
Def Cr Service Group
The Def Cr Service Group field indicates the service group associated with the corresponding default credit activity. The selected value needs to have a valid entry in the AA.SERVICE virtual table and must non-negotiable at arrangement level.
Default Debit
The Default Debit field indicates the default AA activity to be used for AA debit transactions. The selected value needs to have a valid record in AA.ACTIVITY and activity type has to be set to ‘Accounting’.
Def Db Service Group
The Def Db Service Group field indicates the service group associated with the corresponding default debit activity. The selected value has to have a valid entry in the AA.SERVICE virtual table.
Txn Service Group
It indicates the service group of the transaction activity. The selected value needs to have a valid entry in the AA.SERVICE virtual table.
Default Event Activity
The Default Event Activity field indicates the activity name that can be triggered when the corresponding external application event is qualified for this arrangement account which does not have a one to one mapping. The selected value needs to have a valid entry in the AA.ACTIVITY table and the corresponding activity class has to be <Product Line>-RECORD.EVENT-ARRANGEMENT. This field is mandatory if the Facility property is added into the product.
Default Event Service
The Default Event Service field indicates the service group of the default event activity. The selected value has to have a valid entry in the AA.SERVICE virtual table.
Event Ref
This field links AA to the other applications. When non-financial action (facility or service request) is made to the non-AA application then the corresponding action is qualified by the TEC framework. Once the event is qualified, then the event is processed through the corresponding arrangement activity mapped to this event reference. The selected value needs to have a valid entry in the TEC.ITEMS table and the reference needs to be classified as SERVICE.
Event Activity
The activity name that can be triggered when the corresponding external application event is qualified for this arrangement account. The selected value has to have a valid entry in the AA.ACTIVITY table. The corresponding activity class has to be in the <Product Line>-RECORD.EVENT-ARRANGEMENT format.
Event Service Group
It indicates the service group of the event activity. The selected value has to have a valid entry in the AA.SERVICE virtual table.
Linking Non-AA Transactions to Property Activities
The method of paying in and out of an arrangement is to debit or credit the related Temenos Transact account through any Temenos Transact application that allows specification of an account number.
Disbursement of a loan arrangement can be a debit through any of the following:
- FUNDS.TRANSFER application
- A debit made through the TELLER application
- ATM
Repayment method can be a credit through the FUNDS.TRANSFER or TELLER application. Payment can be generated as a manual transaction or scheduled activity (example: a standing order or cash pool sweep).
When a movement is posted to the related Temenos Transact account, the system determines the activity to perform against the arrangement based on the transaction code of the accounting movement.
The Accounting property allows a transaction code to be linked to a specific AA.ACTIVITY.
For example, the transaction code 408 being posted across an arrangement has to result in the LENDING-DISBURSE-ARRANGEMENT activity being generated.
Default debit and credit activities can be defined and used when a specific transaction code in an accounting entry is not found in the Accounting property.
Only a limited list of activities can be specified for the DEFAULT.CR.ACTIVITY, DEFAULT.DR.ACTIVITY and TXN.ACTIVITY. These are indicated by the TYPE in the AA.ACTIVITY.CLASS that underlies the AA.ACTIVITY record.
To specify the activity, the following TYPE definition must be present in AA.ACTIVITY.CLASS:
- TXN.ACTIVITY – DEBIT or CREDIT
- DEFAULT.DR.ACTIVITY – DEBIT
- DEFAULT.CR.ACTIVITY – CREDIT
Disbursal of an Arrangement Loan
Funds are disbursed for an arrangement using existing Temenos Transact applications as described earlier in this section. A disbursal for a loan is a debit to the arrangement account and has to be mapped using the transaction code and TXN.ACTIVITY or DEFAULT.DR.ACTIVITY.
Repayment of an Arrangement Loan
Funds are repaid for an arrangement using existing Temenos Transact applications as described earlier in this section. A repayment for a loan is a credit to the arrangement account and has to be mapped using the TRANSACTION code and TX.ACTIVITY or DEFAULT.CR.ACTIVITY.
Restriction Availability per Product
Activity Mapping Property Class provides a link between external (non-AA) applications and arrangement activities. So far, any financial transaction that involves arrangement account results in an AA activity in the arrangement account. This mapping of a transaction code in financial event to an AA activity is done through the Activity Mapping Property Class, that is, the definition of which activity is to be triggered in AA account if a debit or credit with a particular transaction code is performed.
The Activity Mapping Property Class allows the definition of the activity that is to be triggered when a non-financial transaction is done on an arrangement account through a non-AA or an external application. It also defines the service to which the activity belongs.
|
Field |
Description |
|---|---|
| Event |
|
| Event Activity |
|
| Event Service |
|
Whenever an Activity is triggered with a service associated to it, the service information is passed to activity restriction for validation. This is done for both financial and non-financial activities.
Add Activity Mapping Property to Existing Arrangements
The financial institutions can add the Activity Mapping property to the existing arrangements of the Multi-Currency Accounts product line using the Add New Property, New Prop Avl, and New Prop Avl Date fields in AA.PRODUCT.MANAGER.
Read Add New Property for more information on the configuration.
Periodic Attribute Classes
There are no periodic attribute classes associated with Activity Mapping Property Class.
Actions
The Activity Mapping Property Class supports the following actions:
| Action Name | Description |
|---|---|
| UPDATE | The UPDATE action is used to apply product level Activity Mapping definition to an arrangement contract and is initiated as part of the New-Arrangement and Update-Activity.Mapping activities. |
Accounting Events
The Activity Mapping property does not perform any actions that generate accounting events.
Limits Interaction
The Activity Mapping property does not perform any actions that impact on the Limits system.
In this topic