Release Notes

Accounting
Version 4.6

st
Document GA Date 31 March, 2016
st
Document Date 31 March, 2016
Document version 1.0

PROPRIETARY NOTICE

This document contains confidential information, which may include trade secrets and business information.
Recipient acknowledges that this information has been developed by Multifonds as valuable trade secrets. All
information contained herein shall remain exclusive property of Multifonds and shall be disclosed to only persons who
have a need to know. Recipient agrees not to copy or reproduce in any form any information supplied herein without
prior written permission from an authorized representative of Multifonds. Recipient further agrees to provide security
for this document to a reasonable degree so that unauthorized disclosure is prevented.

Copyright © 2016 Multifonds, a Temenos Company, as an unpublished work. All rights reserved.

Oracle is a registered trademark of Oracle Corporation.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
Linux is the registered trademark of Linus Torvalds.
UNIX is the registered trademark of The Open Group in the US and other countries.
 Release Notes

Contents
1. Introduction ....................................................................................................................... 7
2. What is New? .................................................................................................................... 8
2.1. New Features of Fund Accounting (FA) ....................................................................... 8

2.1.1. Accounting and Ledger Entries ............................................................................................. 8

2.1.1.1. Working Calendar Day and Night Management – Legal Holiday Modification ............ 8

2.1.1.2. Half Automatic Settlement CH Entries and PL Account Description ............................ 9

2.1.1.3. Performance Fee – Hurdle Variable Rate.................................................................... 10

2.1.1.4. Performance Fee: ACT/360 in Composite Benchmark and Variable and Spread with
Rounding Logic ................................................................................................................................ 10

2.1.2. Charges................................................................................................................................ 11

2.1.2.1. Performance Fees Enhancements .............................................................................. 11

2.1.3. Financial Instruments and Transaction Processing ............................................................. 12

2.1.3.1. SEC Fee Rounding Logic .............................................................................................. 12

2.1.3.2. 99 Contract Limitation for Swaps ................................................................................ 13

2.1.4. Fund Structures ................................................................................................................... 14

2.1.4.1. Auto Refresh Pooling Prices ........................................................................................ 14

2.1.5. Infocenter............................................................................................................................ 15

2.1.5.1. Positional Cash-flow .................................................................................................... 15

2.1.6. Interface .............................................................................................................................. 16

2.1.6.1. Dirty Price by Interface ............................................................................................... 16

2.1.7. NAV Processing and Reporting ........................................................................................... 17

2.1.7.1. Print Server for SDEGA53 ............................................................................................ 17

2.1.7.2. Specific Calendar Enhancement.................................................................................. 17

2.1.8. Non NAV Reporting Views and Extracts.............................................................................. 18

2.1.8.1. 30 Day SEC Yield Process............................................................................................. 18

2.1.8.2. Distribution Report ..................................................................................................... 19

Page |1
 Release Notes

2.1.8.3. BI PUB Report Generation Enhancements .................................................................. 20

2.1.8.4. CCP Field for Clearing .................................................................................................. 21

2.1.9. Other ................................................................................................................................... 22

2.1.9.1. FX Rate Group FFX Interpolation ................................................................................ 22

2.1.10. Static Data ........................................................................................................................... 22

2.1.10.1. WEM Adjustments By Group Screen .......................................................................... 22

2.1.11. Valuation and Accounting Methodologies.......................................................................... 23

2.1.11.1. Coupon Encaisse and LD LC BW and BC ...................................................................... 23

2.1.11.2. Yield Amortization with Fees Inclusion ....................................................................... 24

2.2. New Features of BI Pub Report ..................................................................................25

2.2.1. NAV Processing and Reporting ........................................................................................... 25

2.2.1.1. Bond Analysis Report ................................................................................................. 25

2.2.1.2. Price Audit Report ....................................................................................................... 26

2.2.1.3. Bond Analysis Report ................................................................................................. 27

2.2.1.4. Price Audit Report ....................................................................................................... 28

2.2.2. Non NAV Reporting Views and Extracts.............................................................................. 29

2.2.2.1. BI PUB Report Generation Enhancements .................................................................. 29

2.2.2.2. Distribution Report ..................................................................................................... 30

2.3. New Features of Workflow Exception Manager (WEM) ...............................................32

2.3.1. Workflow and Exception Manager ..................................................................................... 32

2.3.1.1. Control on Bond Interest vs General Ledger............................................................... 32

2.3.1.2. WEM Share Class Variation Comparison .................................................................... 33

2.3.1.3. Control 3163 Changes in Relation to Multiple Exceptions and the Check on Unofficial
NAV’s 34

2.3.1.4. WEM STP Processing O/U NAV ................................................................................... 35

2.3.1.5. WEM Exception KPIs with Extended Detail................................................................. 35

2.3.1.6. Additional Fields in WEM Reconciliation .................................................................... 36

Page |2
 Release Notes

2.3.1.7. New WEM Tax Figure Controls for TIS, IP and IG ........................................................ 37

2.3.1.8. AMS Warnings in WEM ............................................................................................... 37

2.3.1.9. Extension of WEM Audit Trial Tables .......................................................................... 38

2.3.1.10. Control on Bond Interest vs General Ledger............................................................... 39

3. Enhancements .................................................................................................................41
3.1. Enhancements of Fund Accounting (FA) .....................................................................41

3.1.1. Charges................................................................................................................................ 41

3.1.1.1. Automatic Foreign Fee Payment................................................................................. 41

3.1.1.2. Amount Type 48 and 49 with Calc. Code 01 ............................................................... 41

3.1.2. NAV Processing and Reporting ........................................................................................... 42

3.1.2.1. Cross Rate for MCMC Funds ....................................................................................... 42

3.1.3. Other ................................................................................................................................... 43

3.1.3.1. Prisma Fund Code ....................................................................................................... 43

3.1.3.2. Fee Suffix 4 for Monthly Funds ................................................................................... 43

3.1.3.3. Rebate Fee by Specific Management Company.......................................................... 44

3.1.1. Price and Other Market Data .............................................................................................. 45

3.1.1.1. Auto Refresh Forward FX ............................................................................................ 45

3.1.2. Valuation and Accounting Methodologies.......................................................................... 46

3.1.2.1. Collateral Management Enhancement ....................................................................... 46

3.1.2.2. Negative Interest......................................................................................................... 46

3.1.2.3. Swap IR9 OIS ............................................................................................................... 48

3.2. Enhancements of Workflow Exception Manager (WEM) .............................................49

3.2.1. Workflow and Exception Manager ..................................................................................... 49

3.2.1.1. Amendment of WEM Rule 3157 ................................................................................. 49

4. Corrected Problems .........................................................................................................50
4.1. List of Corrected Problems for Accounting ..................................................................50

4.1.1. Accounting and Ledger Entries ........................................................................................... 50

Page |3
 Release Notes

4.1.2. Charges................................................................................................................................ 53

4.1.3. Corporate Actions ............................................................................................................... 53

4.1.4. Equalization and Tax ........................................................................................................... 54

4.1.5. Financial Instruments and Transaction Processing ............................................................. 56

4.1.6. Infocenter............................................................................................................................ 61

4.1.7. Interfaces ............................................................................................................................ 63

4.1.8. NAV Processing and Reporting ........................................................................................... 65

4.1.9. Non NAV Reporting, Views and Extracts............................................................................. 69

4.1.10. Others.................................................................................................................................. 73

4.1.11. Price and Other Market Data .............................................................................................. 76

4.1.12. Static Data ........................................................................................................................... 77

4.1.13. Workflow and Exception Manager ..................................................................................... 78

5. Known Issues and Resolution ........................................................................................82
5.1. List of Accounting Known Issues.................................................................................82

Page |4
 Release Notes

Contacting Multifonds
You can access the Multifonds website at http://www.multifonds.com. From this website, you
can obtain information about the company, its products, corporate offices, special events, and
career opportunities.
Address: 7, Rue des Primeurs L-2361 Strassen
Telephone: +352 264 421 1
Fax: +352 264 421 44

Customer support
You can obtain technical or functional support by contacting Multifonds using your JIRA Login
credentials.

To expedite your inquiry, please see “Before Contacting Multifonds” below on this page.

Support by telephone or email

Multifonds has introduced the ability to raise a JIRA as a specific Functional or Technical issue.
This will enable your issue to be routed to the correct teams within Multifonds, ensuring it is
dealt with efficiently.

JIRA is the sole tool used to raise and follow up issues with Multifonds. All software and
technical issues should be raised to Multifonds via JIRA, e-mails will not be responded to.

Before contacting Multifonds

Have the following information available so that Customer Support can begin working on your
issue immediately:
 Product information

o Product name

o Product version (release number)

License number and password (trial or permanent)

 Operating system and environment information

o Machine type, Operating System type, version, and service pack

o System hardware configuration

Page |5
 Release Notes

Related software (database, application) including type, version, and service pack or
maintenance level

Sequence of events leading to the problem

Configuration options that you used

 Messages received (and the time and date that you received them)

o Product error messages

o Messages from the operating system, such as file system full

o Messages from related software

Page |6
 Release Notes

1. Introduction
Multifonds is releasing version 4.6 of Accounting product.

This Release Notes document provides information about new features, enhancements added,
list of issues fixed and known issues in this version.

Following are the sections available:

 What’s New?
 Enhancements
 Corrected Issues
 Known Issues and Resolution

Page |7
 Release Notes

2. What is New?
This section briefly describes the new features that are developed and are available in the
Release 4.6 of Multifonds products. In this document, the new features are grouped based on
the Multifonds products and are provided in separate sections.

This version incorporates new features since the 4.5.1 release of Multifonds products.

2.1. New Features of Fund Accounting (FA)

The new features that are developed for the Release 4.6 Fund Accounting (FA) product are
listed as tables below:
2.1.1. Accounting and Ledger Entries
The new features that are developed for the Functional Area ‘Accounting and Ledger Entries’
are listed below:
2.1.1.1. Working Calendar Day and Night Management – Legal Holiday Modification

JIRA Reference MFONDS-2291

URL for Feature Demo MFONDS-2291/Feature Video

URL for Test

MFONDS-2291/Test Cases
Performed

Functional Area Accounting and Ledger Entries

Impacted N/A
Functionalities

Business Reason This development is to link the functionality to the legal holiday by currency
instead of the legal holiday by quotation place.
It’s not going to impact other functionalities like value date for Italian market
and NAV projected. A new field at fund level will be added in the screen
FDPTF02. This new field will allow the user to apply or not the legal holiday
defined in FDFER02 by fund with the different MF existing functionality as well
as this new development linked to the working days management.
There are few functionalities linked to FDFER02 screen that are currently
applicable to all the funds by default. But the client doesn’t want to consider
any holidays for those functionalities. So at present they have not listed any
holidays and the screen is blank.
This field will allow user to decide/control whether this fund should consider the
holiday’s listed in FDFER02 screen or not.
Other functionalities linked to the screen FDFER02 will work as currently
(value date by stock market when “working days” is ticked, the calc payment

Page |8
 Release Notes

date calculation for swaps, settlement of fees recorded In Shareholder Activity

etc.
) when the fund will be setup with the new field “Legal holiday by currency” at
Y at fund level.

Description New value "A" was added to the list of values for the field "Working days mgt"
and a new parameter "Legal holidays by currency" flag is made available at
Fund level.
The "Legal holidays by currency" flag supports values 'Y' and 'N'. If set to "Y",
the system considers the legal holidays for the fund defined for the trade
currency in the screen FDFER02 (Static Data > Legal holidays > By currency).
If the flag is set to "N", the existing functionality takes over and the system
considers the legal holidays for the fund defined for the quotation place in the
screen PRCAL01 (Static Data > Legal holidays > Quotation Place Calendar).

2.1.1.2. Half Automatic Settlement CH Entries and PL Account Description

JIRA Reference MFONDS-2299

URL for Feature Demo MFONDS-2299/Feature Video

URL for Test

MFONDS-2299Test Cases
Performed

Functional Area Accounting and Ledger Entries

Impacted N/A
Functionalities

Business Reason Currently, there is no description of the fee in the screen FDPRM05. Fees
have to be checked one by one with the button ‘DEAL’ which is time
consuming for funds with respect to parameterization with a lot of fees.

Description The development creates a new column ‘Transaction Description’ in the

screen FDPRM05. This development is applicable only for “CH Entries”.
This development is going to work with all types of funds and irrespective of
the auto charge parameterization = Y or N at fund master.

Page |9
 Release Notes

2.1.1.3. Performance Fee – Hurdle Variable Rate

JIRA Reference MFONDS-2303

URL for Feature Demo N/A

URL for Test

MFONDS-2303/Test Cases
Performed

Functional Area Accounting and Ledger Entries

Impacted N/A
Functionalities

Business Reason This development is to change the logic of the calculation of benchmark
performance in case of hurdle with variable rate.

Description Currently, variable rates are applied everyday on the number of days since the
beginning of the period.

2.1.1.4. Performance Fee: ACT/360 in Composite Benchmark and Variable and Spread
with Rounding Logic

JIRA Reference MFONDS-1999

URL for Feature Demo MFONDS-1999/Feature Video

URL for Test

MFONDS-1999/Test Cases
Performed

Functional Area Accounting and Ledger Entries

Impacted N/A
Functionalities

Business Reason The business reason for this development is on performance fees and are
described below:
 This development is to make composite benchmark calculation for
Hurdle Fixed and Hurdle Variable rates with ACT/360 usance code.
 The rounding of different data with respect to the set up defined in
fields “Decimal places for CRP/PF accrual”, “Decimal places for
reference NAV” and “Decimal places for Gross NAV” to allow for
accurate performance fee calculation.
 Flat method with variable rate for composite benchmark
 Adjustment on subscription in share class model

P a g e | 10
 Release Notes

 Logic of flag “Payment ref ccy” unticked.

Description Currently, composite benchmark calculation for Hurdle Fixed and variable
rates only work with ACT/ACT usance code.
The column BMK_Price shows benchmark performance instead of benchmark
price and columns for crystallization and cumulative crystallization are not
available in QRY_V_PERF_FEE table.

2.1.2. Charges
The new features that are developed for the Functional Area ‘Charges’ are listed below:
2.1.2.1. Performance Fees Enhancements

JIRA Reference MFONDS-2315

URL for Feature MFONDS-2315/Feature Video

Demo

URL for Test

MFONDS-2315/Test Cases
Performed

Functional Area Charges

Impacted N/A
Functionalities

Business Reason Performance fee is a charge payable to Fund managers for their efforts invested
in good performance of the funds.
Performance fees can be calculated using with 5 different methods:
1. HWM only
2. HWM Relative Index
3. HWM Benchmark Index
4. HWM Hurdle variable
5. HWM Hurdle variable with cumul du hurdle
The development is to add new attributes which have to be used in conjunction
with existing functionality to enhance the existing Performance Fees functionality
to cater the client’s requirements.

Description Following parameters are newly developed as part of Performance Fees

enhancements:
1. Two intermediate values referred to as Cumulative Dividend and Reset

P a g e | 11
 Release Notes

HWM/Hurdle is developed and play pivotal role in further calculations.

2. Dividend scenarios are managed in all the five models by creating a new
parameter ‘0003- Dividend Adjustment’, which drives the specific
methodology of calculation of Adjusted Dividend used subsequently in the
existing code.
3. Capping implies fixing the maximum limit of performance and variants of
same are available in Multifonds. However a new variant is required for
capping the Performance Fees. A new parameter ‘0006 – HWM/Hurdle
Cap’ for Fee Capping basis is developed.
4. A new parameter ‘0007- Reset NAV > Hurdle’ is developed to work
exclusively with method ‘HWM Hurdle variable’. This parameter controls
the specific reset calculation exclusive to method ‘HWM Hurdle variable’.
5. A new generic parameter ‘0005 – Adjustment on Gross Performance
Fees’ is developed to work with method ‘HWM Hurdle variable’.
6. A new column ‘Crystallization’ is added in the PERFORMANCE FEE
DATA ADJUST – FDPFA01 screen to initialize the performance fee set
up for existing fund if existing funds have historical crystallization amount
in reference currency.

2.1.3. Financial Instruments and Transaction Processing

The new features that are developed for the Functional Area ‘Financial Instruments and
Transaction Processing’ are listed below:
2.1.3.1. SEC Fee Rounding Logic

JIRA Reference MFONDS-2285

URL for Feature MFONDS-2285/Feature Video

Demo

URL for Test

MFONDS-2285/Test Cases
Performed

Functional Area Financial Instruments and Transaction Processing.

Impacted N/A
Functionalities

Business Reason The development is to have the correct rounding logic on SEC fees when
processing sale transactions.

Description The rounding logic is:

P a g e | 12
 Release Notes

“In calculating the new fee for a transaction, the sale or principal amount of the
transaction is multiplied by the fee rate, which will be truncated at the seventh
place after the decimal point. The resulting figure should then be truncated at the
fifth place after the decimal point and rounded up to the next cent (if there is any
remainder then it should always round up).”
The following transaction types are considered:
 Sale of equity security (Op Code 201)
 Sale of equity call option (Op Code 306)
 Sale of equity put option (Op Code 306)
 Exercise of equity put option (Op Code 331/201)
 Assignment of equity putcall option (Op Code 306)
 Short Sale of equity security (Op Code 219)
A new field ‘Type of tax amount or %’ is included as another option for SEC fee
rounding calculation in FDCOM01 screen.
A new fee code ‘20 – Percent with Round up’ for BO is parameterized in
CMESS table.

2.1.3.2. 99 Contract Limitation for Swaps

JIRA Reference MFONDS-2312

URL for Feature N/A

Demo

URL for Test

N/A
Performed

Functional Area Financial Instruments and Transaction Processing.

Impacted N/A
Functionalities

Business Reason This development is to increase the number of swap contracts which is allowed to
be processed into a single fund with the same maturity date and currency (fund
leg currency).
Currently, only 100 swap contracts are processed into a single fund with the same
maturity date and currency (fund leg currency).
New field ‘Sub type’ will be automatically managed by the system both via
interface and manually.

Description Currently, only 100 Swap contracts can be processed into a single fund with the

P a g e | 13
 Release Notes

same maturity date and currency (fund leg currency). The current limit number for
suffix is from 00 to 99.
101 swap transactions with the same maturity date and currency (fund leg
currency). In the accounting entries of the swap contract, the suffix is associated
to the off balance account.

2.1.4. Fund Structures

The new feature that is developed for the Functional Area ‘Fund Structures’ is listed below:
2.1.4.1. Auto Refresh Pooling Prices

JIRA Reference MFONDS-2314

URL for Feature MFONDS-2314/Feature Video

Demo

URL for Test

MFONDS-2314/Test Cases
Performed

Functional Area Fund Structures

Impacted N/A
Functionalities

Business Reason The development is to have the possibility to run the Sub Fund NAV without the
Pool NAV confirmation in the screen ‘Pool Price Historical - FDPOL01’.
Currently when the user wants to run a Sub Fund NAV, the user has to run the
Pool NAV first and confirms the NAV prices in FDPOL01.

Description A new check box ‘Auto save Pool price’ is added to the Application Parameters
(FDPRM01) screen to enable the Auto Refresh Pooling Prices functionality.
Since there is a Pool NAV price available, the system will take it by default for the
Sub Fund NAV simulation. The price date to be used by the sub fund is the same
as the accounting date. If several pools are available, then all NAV prices are
required to run the Sub Fund NAV.
However if there is no existing pool price for the expected date, the system
displays an error message when user simulates the Sub Fund NAV.

P a g e | 14
 Release Notes

2.1.5. Infocenter
The new feature that is developed for the Functional Area ‘Infocenter’ is listed below:
2.1.5.1. Positional Cash-flow

JIRA Reference MFONDS-2005

URL for Feature Demo N/A

URL for Test Cases MFONDS-2005/Test Cases

Functional Area Infocenter

Impacted CNMO
Functionalities

Business Reason This development is to extract the IDS feed. Only one unique positional cash-
flow projection per lot from IC table as on fund accounting date based on
available security position as of when security lot/holding position is changed
on trade date basis. Every positional cash-flow will be tagged with last
transactional entry number and fund entry number that will help the integration
to extract the latest positional cash-flow for each security lot.
If there are multiple purchases and multiple sales transactions are accounted
on any given lot then with NAV export to IC process, every positional cash-flow
associated to available position after every transaction will be exported to
AMS_CASH_FLOW_PROJECTION_LOT table tagged with “transaction entry
number” in a new field which will be added in cash-flow projection table. If
there is no change in security lot/holding position then there will be no new
positional cash-flow projection data need to be exported. YD1 process
changes the security position so new revised positional cash-flow will be
generated afterYD1 followed by CP% process and every positional cash-flow
will be tagged with latest entry number of transaction which would represent
the cash-flow on security position after every transaction on security lot.

Description Currently the cash-flow projection by lot is generating the positional cash-flow
data in AMS_CASH_FLOW_PROJECTION_LOT table after every transaction
on given lot on same fund accounting date.

P a g e | 15
 Release Notes

2.1.6. Interface
The new feature that is developed for the Functional Area ‘Interface’ is listed below:
2.1.6.1. Dirty Price by Interface

JIRA Reference MFONDS-2294

URL for Feature Demo MFONDS-2294/Feature Video

URL for Test Cases MFONDS-2294/Test Cases

Functional Area Interface

Impacted N/A
Functionalities

Business Reason This development is meant for managing accrued interests differently for dirty
price.
The accrued interests on bonds are not managed on the same way in case of
dirty price in the different client locations principally due to the inclusion or
exclusion of the accrued interest in the fiscal figures calculation.

Description A new flag named "Dirty price management" is introduced at Fund level to
support this functionality. This flag has the following list of values: 'Y', 'N' and
'E'.
"Dirty price management" is set to 'Y' - When user books a trade by Interface,
this setup will give the possibility to not receive any purchase/sold interest
amount within the flat file for dirty bonds and Purchased/sold interests is
calculated as per security master definition. Application automatically
calculates the purchased/sold interest while booking the transaction. In other
words, user can leave the Interest position blank in the interface file and still be
able to load the transaction without any error.
"Dirty price management" is set to 'N' - No purchased/sold interests or any
accrued interests are calculated for all manual deals. System populates
Purchase/Sold interest as "0" when flag is set to "N". Same logic applies for
interfaced transactions. However, if in case user inserts a value for
purchase/sale interest in the interface file, system will take the value into
consideration.

P a g e | 16
 Release Notes

2.1.7. NAV Processing and Reporting

The new features that are developed for the Functional Area ‘NAV Processing and Reporting’
are listed below:
2.1.7.1. Print Server for SDEGA53

JIRA Reference MFONDS-2295

URL for Feature Demo MFONDS-2295/Feature Video

URL for Test

MFONDS-2295/Test Cases
Performed

Functional Area NAV Processing and Reporting.

Impacted N/A
Functionalities

Business Reason This development is to enhance the print server functionality, in order to make
it compatible with the report SDEGA53. Currently, we are only able to print this
report via the Print Equalization but not with the Print Server.

Description The development allows the user to generate the SDEGA53 report via Print
Server.

2.1.7.2. Specific Calendar Enhancement

JIRA Reference MFONDS-2298

URL for Feature Demo N/A

URL for Test

MFONDS-2298/Test Cases
Performed

Functional Area NAV Processing and Reporting.

Impacted N/A
Functionalities

Business Reason The aim of this development is to map specific Legal Holidays of a country to a
specific calendar. The funds are going to follow a calendar but the fund
manager is outside that country and could have different holidays. Therefore,
the existing calendar is going to be enhanced by adapting the O and P type
projected NAV to look at the holidays of the countries parameterized in
FDFER01 (Holidays by Country) and in field ‘Country’s fund for holidays’ in
screen FDNAV52 (Fund Master – Button Calendar).

P a g e | 17
 Release Notes

Description This calendar cannot be used when there is an exception of legal holidays for a
specific Fund because it will impact all other Funds with the same country
holidays Set Up. For example, 500 German projected funds are already linked
to the legal German calendar. Now we have this projected fund F00510 that
needs to follow the French calendar, if we add the 14th of July to legal holiday
it will impact the 500 other German projected funds hence we need to
parameterize this French legal Holidays to the requested specific calendar.
Basically, the aim is to keep the Calendar by Country and to include specific
days of exception for predefined funds.

2.1.8. Non NAV Reporting Views and Extracts

The new features that are developed for the Functional Area ‘Non NAV Reporting Views and
Extracts’ are listed below:
2.1.8.1. 30 Day SEC Yield Process

JIRA Reference MFONDS-2122

URL for Feature Demo MFONDS-2122/Feature Video

URL for Test

MFONDS-2122/Test Cases
Performed

Functional Area Non NAV Reporting, Views and Extracts.

Impacted N/A
Functionalities

Business Reason The development is to create a new process for the scheduler that will run the
30 Day SEC yield process.

Description A new process ‘SY01 (SEC Yield Process)’ is created. The process can
manage the following:
 The process can be run through submit once
 The process can be scheduled
 The process can be linked to a WEM step
 The process can be triggered through a loader
If run through submit once or the By Group screen in WEM, the process can
run for multiple funds in parallel. There will be a successful status and a failed
status for the process.
When the process runs the dates, then by default will be based on the Fund

P a g e | 18
 Release Notes

Accounting Date (FAD) of the fund.

‘To Date’ = FAD
‘From Date’ = FAD – 29 calendar days
The new process is added to the Process Sequence screen. All the processes
are linked the Process group ‘PGN2’ which is turn linked to NAV step.

2.1.8.2. Distribution Report

JIRA Reference MFONDS-2284

URL for Feature Demo N/A

URL for Test

MFONDS-2284/Test Cases
Performed

Functional Area Non NAV Reporting, Views and Extracts.

Impacted N/A
Functionalities

Business Reason The development is to create a new BI PUB Distribution report, which will
display fund and class level details of accounts to be included in the
distribution factor calculation.
The report will also provide a means of projecting an estimated distribution for
tax purposes, including the ability to include manual adjustments.

Description The Distribution report will run for all multiclass setups except for a fund with
multiclass = 0.
A new field ‘Distribution Projection’ is added in the Multiclass Account Links
screen. The sections to be entered in the field and the impact are given below:
 If set to ST – the short term gain/loss account balance will be taken as
is in the distribution projection.
 If set to LT – the long term gain/loss account balance will be taken as
is in the distribution projection.
 If set to IY – the income account will be taken as is in the distribution
projection.
 If set to YP – the income will be projected using prior year information
in the calculation.
 If set to IP – the income will be projected using current delta.
 If set to N or Blank – the account will not be considered for the
distribution projection.

P a g e | 19
 Release Notes

 If set to DS – include account as distribution on short term gain/loss

report.
 If set to DL – include account as distribution on long term gain/loss
report.
 If set to DI – include account as distribution on income report.
A new screen ‘Manual Entry – FDDIS02’ is developed for allowing users to
enter manual entries for the Distribution report. Following fields are available:
1. Fund
2. Fund Description
3. Class
4. Line Item Description
5. Section
6. Amount
7. Effective Date
8. Include
9. Distribution Date

2.1.8.3. BI PUB Report Generation Enhancements

JIRA Reference MFONDS-2286

URL for Feature Demo MFONDS-2286/Feature Video

URL for Test

MFONDS-2286/Test Cases
Performed

Functional Area Non NAV Reporting, Views and Extracts.

Impacted N/A
Functionalities

Business Reason The development is to enrich the ways and methods of generating or
distributing BI PUB reports in Multifonds.

Description The new development includes the following:

 A check box ‘Single Output File’ is included to combine all reports in
a report set into a single PDF and also selection for each report is
included to consolidate the report for all funds in a NAV Group into a
single output PDF.
 A check box ‘Single Output File’ is included to combine all reports in

P a g e | 20
 Release Notes

a report set into a single PDF.

 A new button ‘Holidays’ is added in the Schedule Reports (FDBIR16)
screen to link a holiday schedule to a report job. The new button
allows the user to link country holidays (more than one).
 A new button ‘File Name’ is added to have the ability to select the
naming convention of a file.
A new Process ‘BI Process’ is created for linking a process to a WEM step to
launch a report set or job. A new button ‘Linked BI Process’ is added to the
Report Job Schedule screen when set to ‘Single Job’. A BI process can be
added to multiple single jobs.

2.1.8.4. CCP Field for Clearing

JIRA Reference MFONDS-2311

URL for Feature Demo MFONDS-2311/Feature Video

URL for Test

MFONDS-2311/Test Cases
Performed

Functional Area Non NAV Reporting, Views and Extracts.

Impacted N/A
Functionalities

Business Reason The reason behind this development is to add a new field named ‘CCP’ in the
IRS screen FDSWI02.

Description This development is to add a new field named ‘CCP’ in the IRS screen
FDSWI02. Data will come from Central Register.
- It will be available in the control file for interface loading.
- It will be reflected in table for FDSWI02 and in infocenter for reporting.

P a g e | 21
 Release Notes

2.1.9. Other
The new features that are developed for the Functional Area ‘Other’ are listed below:
2.1.9.1. FX Rate Group FFX Interpolation

JIRA Reference MFONDS-2307

URL for Feature Demo MFONDS-2307/Feature Video

URL for Test

MFONDS-2307/Test Cases
Performed

Functional Area Other

Impacted N/A
Functionalities

Business Reason For the FFX interpolation functionality, users request to take the valuation FX
rate group (NAV exchange rate group) to do the calculation instead of the
transaction FX rate group.
This development is applicable to all FX valuation method, including FX
valuation method 6 and 8 and RB and RC nav type. This is also applicable to
both fund level and class level forward FX contracts and it will work fine with
the field “Auto refresh forward FX” in fund master no matter whether it is
checked or not.

Description Currently, the forward FX interpolation functionality is taking the transaction

rate group (Group exch. Rate MF) specified in fund master for calculation.

2.1.10. Static Data

The new features that are developed for the Functional Area ‘Static Data’ are listed below:
2.1.10.1. WEM Adjustments By Group Screen

JIRA Reference MFONDS-2310

URL for Feature Demo N/A

URL for Test MFONDS-2310/Test Cases

Performed

Functional Area Static Data

Impacted N/A
Functionalities

P a g e | 22
 Release Notes

Business Reason The business reason behind this development is, for the step NAV validation
which has spec. reset rights, is for the fact that once this step has been passed
only senior users will be able to reset the checklist of the funds as fund price
would have published already. This works fine, but the other funds which have
only reached a lower step, are impacted as the user cannot reset this step
anymore.

Description This development includes the following adjustments:

 Reset in By Group screen which is going to be linked on fund wise
status and not as family status.
 Excel export in By Group screen to cover all steps.
 To delete the old family-fund link, once a fund gets deleted from the
family.

2.1.11. Valuation and Accounting Methodologies

The new feature that is developed for the Functional Area ‘Valuation and Accounting
Methodologies’ is listed below:
2.1.11.1. Coupon Encaisse and LD LC BW and BC

JIRA Reference MFONDS-2290

URL for Feature Demo MFONDS-2290/Feature Video

URL for Test

MFONDS-2290/Test Cases
Performed

Functional Area Valuation and Accounting Methodologies

Impacted N/A
Functionalities

Business Reason During the clients migration project, funds defined with ‘coupon encaisse’ are
not managed correctly for following instruments:
 Security lending with cash / Repo (mise en pension) = LC
 Security borrowing with cash / reversed repo (prise en pension) = BC
 security lending (prêt de titres) = LD
 security borrowing (emprunt de titres) = BW
The method ‘coupon encaisse’ or ‘coupon couru’ is a rule defined in the fund
prospectus. The rule is applied on all instrument with securities with the notion
of interest accruals within the fund:

P a g e | 23
 Release Notes

 the book cost

 market value
 unrealized
 realized
For coupon encaisse: the interest accruals should be included
For coupon couru: the interest accruals are not included.
The NAV code 90M is currently applied on BO remaining position. It will be
extended to LD and LC positions to reflect correctly the interest accruals for
the fiscal taxes figures (TIS, IP)
This development is meant for the ‘coupon encaisse’ method to be applied and
to reflect correctly on the reports SDNAV97, SDNAV78, SDNAV70, SDCOL04
and tables POT; JTITR; MVT; NAV_ARC_RES_UNIT, ESTI_CAL ,
ESTI_CAL_HISTO, ESTI_CAL_HISTO_POOL.

Description Interest accruals will be included in the book cost, market value, and
unrealized, and realized.
This logic will be applied to BO, LD, LC, BW and BC position.

2.1.11.2. Yield Amortization with Fees Inclusion

JIRA Reference MFONDS-2306

URL for Feature Demo MFONDS-2306/Feature Video

URL for Test

MFONDS-2306/Test Cases
Performed

Functional Area Valuation and Accounting Methodologies

Impacted N/A
Functionalities

Business Reason To comply with IAS and IFRS rules, held to maturity assets are initially
measured at fair value including the transaction cost, and then subsequently
measured at amortised cost. Therefore, the costs of assets must include the
transaction cost which effectively gets charged off over the life of the asset.
This development is to support such handling of transaction cost when
calculating effective interest Rate and linear amortisation.

Description Current functionality of NY02 and Y002 allows capitalization of expenses in

accounting entry, but yield is calculated excluding the capitalized expenses
from bond cost. This result in amortization of clean price excluding capitalized
expenses and hence not in line with fair value.

P a g e | 24
 Release Notes

2.2. New Features of BI Pub Report

The new features that are developed for the Release 4.6 BI Pub Report product are listed below:

2.2.1. NAV Processing and Reporting

The new features that are developed for the Functional Area ‘Accounting and Ledger Entries’
are listed below:
2.2.1.1. Bond Analysis Report

JIRA Reference MFONDS-2288

URL for Feature Demo MFONDS-2288/Feature Video

URL for Test

MFONDS-2288/Test Cases
Performed

Functional Area NAV Processing and Reporting

Impacted N/A
Functionalities

Business Reason The development is to create a new BI PUB Bond Analysis report, which
displays securities from FDTRS02 screen.

Description The Bond Analysis report includes securities as displayed in the core reports
such as ‘SDWAM01 - Weighted Average Days to Maturity (WAM)’ and
‘SDRDT07 - Detailed Inventory – Modified Duration’.
The report also includes more information such as ratings and modified
duration.
The Bond Analysis report is processed based on the following parameters:
1. NAV Group
2. Fund
3. Manager
4. Rating Agency 1
5. Rating Agency 2
6. Rate Scale
7. Filters
a. GTI
b. Rating Agency, Rating
8. Primary Subtotal
a. None (Default)

P a g e | 25
 Release Notes

b. Manager
c. Increment
9. Secondary Subtotal
a. GTI
b. Issuer
c. Rating 1
d. Rating 2
10. Sort by:
a. Security Description, Lot Number
b. DTM

2.2.1.2. Price Audit Report

JIRA Reference MFONDS-2283

URL for Feature Demo MFONDS-2283/Feature Video

URL for Test

MFONDS-2283/Test Cases
Performed

Functional Area NAV Processing and Reporting.

Impacted N/A
Functionalities

Business Reason The development is to create a new BI PUB Price Review/Audit report, which
contains all the data points of the data model.

Description Currently, users can review several Price reports. These reports contain
multiple data points and can be run from the FDSEC10 or FDSEC50 screens.
The Price Audit report is processed based on the following parameters:
1. NAV Group
2. Fund
3. Manager
4. Fields used as Filters:
a. Price type (M,B,O), All is the default
b. GTI
5. Sort by fields:
a. GTI

P a g e | 26
 Release Notes

b. Security ID
c. Exception Message
6. Accounting Date
7. Exception Only (Y,N)
8. All Funds in NAV Group (Y,N)

2.2.1.3. Bond Analysis Report

JIRA Reference MFONDS-2288

URL for Feature Demo MFONDS-2288/Feature Video

URL for Test

MFONDS-2288/Test Cases
Performed

Functional Area NAV Processing and Reporting.

Impacted N/A
Functionalities

Business Reason The development is to create a new BI PUB Bond Analysis report, which
displays securities from FDTRS02 screen.

Description The Bond Analysis report includes securities as displayed in the core reports
such as ‘SDWAM01 - Weighted Average Days to Maturity (WAM)’ and
‘SDRDT07 - Detailed Inventory – Modified Duration’.
The report also includes more information such as ratings and modified
duration.
The Bond Analysis report is processed based on the following parameters:
11. NAV Group
12. Fund
13. Manager
14. Rating Agency 1
15. Rating Agency 2
16. Rate Scale
17. Filters
a. GTI
b. Rating Agency, Rating
18. Primary Subtotal

P a g e | 27
 Release Notes

a. None (Default)
b. Manager
c. Increment
19. Secondary Subtotal
a. GTI
b. Issuer
c. Rating 1
d. Rating 2
20. Sort by:
a. Security Description, Lot Number
b. DTM

2.2.1.4. Price Audit Report

JIRA Reference MFONDS-2283

URL for Feature Demo MFONDS-2283/Feature Video

URL for Test

MFONDS-2283/Test Cases
Performed

Functional Area NAV Processing and Reporting.

Impacted N/A
Functionalities

Business Reason The development is to create a new BI PUB Price Review/Audit report, which
contains all the data points of the data model.

Description Currently, users can review several Price reports. These reports contain
multiple data points and can be run from the FDSEC10 or FDSEC50 screens.
The Price Audit report is processed based on the following parameters:
9. NAV Group
10. Fund
11. Manager
12. Fields used as Filters:
a. Price type (M,B,O), All is the default
b. GTI
13. Sort by fields:

P a g e | 28
 Release Notes

a. GTI
b. Security ID
c. Exception Message
14. Accounting Date
15. Exception Only (Y,N)
16. All Funds in NAV Group (Y,N)

2.2.2. Non NAV Reporting Views and Extracts

The new features that are developed for the Functional Area ‘Non NAV Reporting Views and
Extracts’ are listed below:
2.2.2.1. BI PUB Report Generation Enhancements

JIRA Reference MFONDS-2286

URL for Feature Demo MFONDS-2286/Feature Video

URL for Test

MFONDS-2286/Test Cases
Performed

Functional Area Non NAV Reporting, Views and Extracts.

Impacted N/A
Functionalities

Business Reason The development is to enrich the ways and methods of generating or
distributing BI PUB reports in Multifonds.

Description The new development includes the following:

 An option ‘All Funds in NAV Group’ selection for each report is
included to consolidate the report for all funds in a NAV Group into a
single output (PDF and Excel).
 A check box ‘Single Output File’ is included to combine all reports in
a report set into a single PDF or Excel.
 A new button ‘Holidays’ is added in the Schedule Reports (FDBIR16)
screen to link a holiday schedule to a report job. The new button
allows the user to link country holidays (more than one).
 A new button ‘File Name’ is added to have the ability to select the
naming convention of a file.
 A new Process ‘BI Process’ is created for linking a process to a WEM
step to launch a report set or job. A new button ‘Linked BI Process’ is

P a g e | 29
 Release Notes

added to the Report Job Schedule screen when set to ‘Single Job’. A
BI process can be added to multiple single jobs.
 A new section ‘Report Specific option’ is created under the ‘Run
Reports’ and ‘Define Report Sets’ screen.
 A new loader allows users to create a report set. The loader always
creates a GROUP level.

2.2.2.2. Distribution Report

JIRA Reference MFONDS-2284

URL for Feature Demo N/A

URL for Test

MFONDS-2284/Test Cases
Performed

Functional Area Non NAV Reporting, Views and Extracts.

Impacted N/A
Functionalities

Business Reason The development is to create a new BI PUB Distribution report, which will
display fund and class level details of accounts to be included in the
distribution factor calculation.
The report will also provide a means of projecting an estimated distribution for
tax purposes, including the ability to include manual adjustments.

Description The Distribution report will run for all multiclass setups except for a fund with
multiclass = 0.
A new field ‘Distribution Projection’ is added in the Multiclass Account Links
screen. The sections to be entered in the field and the impact are given below:
 If set to ST – the short term gain/loss account balance will be taken as
is in the distribution projection.
 If set to LT – the long term gain/loss account balance will be taken as
is in the distribution projection.
 If set to IY – the income account will be taken as is in the distribution
projection.
 If set to YP – the income will be projected using prior year information
in the calculation.
 If set to IP – the income will be projected using current delta.
 If set to N or Blank – the account will not be considered for the

P a g e | 30
 Release Notes

distribution projection.
 If set to DS – include account as distribution on short term gain/loss
report.
 If set to DL – include account as distribution on long term gain/loss
report.
 If set to DI – include account as distribution on income report.
A new screen ‘Manual Entry – FDISTR’ is developed for allowing users to
enter manual entries for the Distribution report. Following fields are available:
10. Fund
11. Fund Description
12. Class
13. Line Item Description
14. Section
15. Amount
16. Effective Date
17. Include
18. Distribution Date

P a g e | 31
 Release Notes

2.3. New Features of Workflow Exception Manager (WEM)

The new features that are developed for the Release 4.6 Workflow Exception Manager (WEM)
product are listed below:
2.3.1. Workflow and Exception Manager
The new features that are developed for the Functional Area ‘Workflow and Exception Manager’
are listed below:
2.3.1.1. Control on Bond Interest vs General Ledger

JIRA Reference MFONDS-2287

URL for Feature Demo MFONDS-2287/Feature Video

URL for Test Cases MFONDS-2287/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason The development is to create a new control that will compare the interest on
bonds in the sub ledger vs. the accounts on the general ledger.

Description A new table ‘RAPPORT’ referred as INB (Interest Bonds) is created in the
CMESS table.
A new control ‘3090 – Check Bond Interest vs Ledger’ is created in FDMUT01
screen. Interest Accounts are linked to RAPPORT code ‘INB’. Control is setup
and fund or NAV group is linked.
The new control will drill down to the SDNAU00 report. The WEM exception
occurs when there is mismatch in bond interest amount with general ledger
amount.
 Interest on Bonds: Value from the 900 report
 General Ledger: Value from Account Positions

P a g e | 32
 Release Notes

2.3.1.2. WEM Share Class Variation Comparison

JIRA Reference MFONDS-2317

URL for Feature Demo MFONDS-2317/Feature Video

URL for Test Cases MFONDS-2317/Test Cases

MFONDS-2317/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason The development is to create a new control ‘3257 - Share class variation
comparison’, which calculates the daily percentage variation by class for each
share class of a fund and then compares each share variation with each other.
Precisely, variation in the per unit net asset value for each share-class is to be
compared over previous day and then such variation is compared with other
share classes.

Description The new control ‘3257 - Share class variation comparison’ is added to the
CMESS Message table. The following columns are parametrized for the new
control in the Threshold (FDNAV42) screen: NAV Group, Fund, GTI/Share
Type, Amount/Var% or Var. %High and Effective Date.
The new control takes place during the relevant ‘PG’ process. The control runs
during NAV process and linked to NAV Simulation process in the related PG
process.
The control works with absolute values, hence a threshold covers a range from
-0,01 to +0,01.
The exception information for this new control contains the below information
besides the existing standard information:
 Share Class ID of the first Share class.
 Calculated Unrounded Share value of the first Share class per Date J.
 Calculated Unrounded Share value of the first Share class per Date J-
1.
 Percentage Variation of the first Share class.
 Share Class ID of the second Share class.
 Calculated Unrounded Share value of the second Share class per
Date J.
 Calculated Unrounded Share value of the second Share class per

P a g e | 33
 Release Notes

Date J-1.
 Percentage Variation of the second Share class.
 Threshold
 Exception Result

2.3.1.3. Control 3163 Changes in Relation to Multiple Exceptions and the Check on
Unofficial NAV’s

JIRA Reference MFONDS-2318

URL for Feature Demo N/A

URL for Test Cases MFONDS-2318/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason The development is to establish a control which is tracking changes to the
fields “TIS Available” and “In scope FOF/Grandfathered” in the Security
Master Data (FDSEC01) Sub Menu “Text”.
The existing control ‘3163’ displays exceptions separately for every change
processed in between the last official NAV and the current NAV in the WEM
exceptions screen. The main gap is that the control 3163 is showing every
single detail change processed between two NAVs, as a separate breach, in
the exceptions in WEM. Means, 10 changes of the same field in FDSEC01 will
create 10 breaches in the WEM Exceptions menu, as per current functionality.

Description The control 3163 is changed to display only one exception in WEM irrespective
of number the changes made in fields of FDSEC01 screen. That is, when the
field “TIS available” is displaying ‘N’ for the current NAV, but showed ‘Y’ at the
last official NAV, the control 3163 displays a single breach only , even the “TIS
available” status have been altered several times in between those two NAVs.
The control always compares the current NAV (official or unofficial) against the
latest available official NAV only. In case the latest 2 NAVs were both
unofficial, the control checks the current unofficial NAV against the latest
previous official NAV available; not against the previous NAV which was
unofficial.
The control shall be attachable to the Simulation or Accounting step as
required.

P a g e | 34
 Release Notes

2.3.1.4. WEM STP Processing O/U NAV

JIRA Reference MFONDS-2319

URL for Feature Demo MFONDS-2319/Feature Video

URL for Test Cases MFONDS-2319/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason In MFGI, while processing the O/U NAV checklist with optional steps in the By
Group screen, the process will not continue automatically with the next step
once no action/control has been linked and once previous step finishes without
exception. Reason for that is, the optional steps are not functionally linked.
The development is provide the possibility to automate O NAV and U NAV
checklist with optional steps and to increase therefore the STP rate for a WEM
client using O/U NAV steps within WEM workflow.

Description The development amends an optional checklist to work in the same way as a
non-optional checklist, therefore the next step continues automatically as per
existing functionality of a non-optional checklist, once no action/control is
linked to the step and the previous step is finished successfully.
WEM considers the related setup of the steps in regards of the O or U NAV
type, in order to distinguish and considers the next step to be opened. A step
without action/control, which is called Auto Step, opens and starts
automatically once the previous step is successful and has reached the
minimum status on fund level in the BY Group screen.

2.3.1.5. WEM Exception KPIs with Extended Detail

JIRA Reference MFONDS-2320

URL for Feature Demo MFONDS-2320/Feature Video

URL for Test Cases MFONDS-2320/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason The development is to provide the feasibility to view the exception details in

P a g e | 35
 Release Notes

the KPI screen as displayed currently in the Exception screen.

Description A new tab ‘Extended Details’ is added in the KPI screen to facilitate the user
to view the detailed part of the break as displayed in the Exception screen.
Also, a new parameter ‘Include Detail in Excel’ is made available when
generating the report in the KPI screen.

2.3.1.6. Additional Fields in WEM Reconciliation

JIRA Reference MFONDS-2323

URL for Feature Demo N/A

URL for Test Cases MFONDS-2323/Test Cases

MFONDS-2323/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason In case there are multiple entries submitted via the TA Loader File for a
dedicated Share Class ISIN on a dedicated Accounting date, the control ‘5002’
will consider only the most recent load for the TA reconciliation.
The development is to have the flexibility of submitting multiple entries via the
TA Loader file for each Accounting date.

Description Two new columns named “IMPORT_DATE” and “INSERTED_BY” are added
to the existing tables ‘AMS.MIG_RECONCIL_TA’ and
‘AMS.RECONCIL_TA_EXT’. The IMPORT_DATE column reflects the time
stamp of the actual loading of the TA Loader file and the INSERTED_BY
column reflects the user who has submitted the file.
The new columns distinguish and monitor multiple loads processed for the
same Accounting date and are populated automatically with the relevant time
stamp and user information on every load. Every Load generates a new entry
into the AMS.MIG_RECONCIL_TA and AMS.RECONCIL_TA_EXT tables.
The new columns are established for auditing purposes only, as the enhanced
functionality shall allow multiple loads/Acc Date.

P a g e | 36
 Release Notes

2.3.1.7. New WEM Tax Figure Controls for TIS, IP and IG

JIRA Reference MFONDS-2324

URL for Feature Demo N/A

URL for Test Cases MFONDS-2324/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason The development is to create three new controls in WEM tax figures as the
existing controls are not accurately applicable for all funds. For certain funds, it
is necessary to apply the threshold on the absolute difference instead of the
percentage variation and these controls apply absolute value.

Description All three controls are calculated on tax figure per share value:
1. Control 8031 TIS (absolute value)
2. Control 8032 IP (absolute value)
3. Control 8033 IG (absolute value)
The new controls compare an absolute value deviation between Last O NAV
vs Current O NAV / nr. of days. The threshold is an absolute value and it is
defined for all 3 new controls in the field ‘VAR%/High/Per share check’.
If for all three new controls, erroneously both fields ‘Amount/Var%/Nbr Days’
and ‘Var.%High/Per share check’ are populated, then the control checks only
on the threshold defined in the field ‘Var.%High/Per share check’. The other
field is neglected.
The control raises an exception based on the value defined in field
‘Var.%High/Per share check’. If the there is no threshold defined in the field
‘Var.%High/Per share check’, then the control will not raise an exception.

2.3.1.8. AMS Warnings in WEM

JIRA Reference MFONDS-2325

URL for Feature Demo N/A

URL for Test Cases MFONDS-2325/Test Cases

Functional Area Workflow and Exception Manager

P a g e | 37
 Release Notes

Impacted N/A
Functionalities

Business Reason The development is to display warnings in WEM:

1. If NAV Validation and Confirmation is rerun if the Infocenter and Print
server have been validated already.
2. If there are transactions after NAV Accounting.

Description A warning message gets displayed in WEM at NAV Validation and

Confirmation. If there is no NAV Simulation and Accounting, and only NAV
Validation and Confirmation is reset & rerun, then MF core warning message is
brought to WEM. The display of warning message is added to the following
screens in WEM: Checklist, By Group and By Stream.
A new control ‘3023 – Check if there were new transactions after NAV
Accounting’ is added in WEM. This new control is added to a step before
Change Accounting Date step to ensure that there were no additional bookings
just before FAD change. The new control is linked to a new CL step that is
followed by the date change step, linked to AC process.
The control verifies the ‘Last Accounting’ field on fund parameter to raise an
exception when there is a transaction after NAV Accounting. The new control
breaks only once even if there are several transactions booked between NAV
Accounting and FAD change step. In the exception details it will give the
service code and the entry number of the last transaction.

2.3.1.9. Extension of WEM Audit Trial Tables

JIRA Reference MFONDS-2326

URL for Feature Demo N/A

URL for Test Cases MFONDS-2326/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason The development is to create new Back tables for the live screen
‘EMF.EM_MODEL’ and ‘EMF.EM_FAMILY_NAVGRP’, and the tables are to
referred as ‘EMF.EM_MODEL_BACK’ &
‘EMF.EM_FAMILY_NAVGRP_BACK’.

Description The new tables consist of following fields:

P a g e | 38
 Release Notes

 MODEL_ID/FAMILY_ID
 NAME/NAV_GROUP
 DESCRIPTION
 DCREATED
 CREATED_BY
 UPDTAED
 UPDATED_BY
 DELETE_DATE
 DELETE_BY
The original creation of a new model is displayed in the fields ‘DCREATED’
and ‘CREATED_BY’ in EMF.EM_MODEL_BACK table. The original creation
of a new Family - NAV Group link is recorded in the fields ‘DCREATED’ and
‘CREATED_BY in EMF.EM_FAMILY_NAVGRP_BACK table.
The existing table ‘EMF.EM_ACTION_BACK’ is enhanced to record the
original creation of a new Action in the fields ‘DCREATED’ and
‘CREATED_BY’. Changes on existing Actions are recorded in the fields
‘DUPDATED’ and ‘UPDATED_BY’. The fields ‘ARCHIVE_DATE’ and
‘ARCHIVE_USER’ are renamed to ‘DELETE_DATE’ and ‘DELETED_BY’. The
complete deletion of a Control shall be recorded in the fields DELETE_DATE
and DELETED_BY.

2.3.1.10. Control on Bond Interest vs General Ledger

JIRA Reference MFONDS-2287

URL for Feature Demo MFONDS-2287/Feature Video

URL for Test Cases MFONDS-2287/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Business Reason The development is to create a new control that will compare the interest on
bonds in the sub ledger vs. the accounts on the general ledger.

Description A new table ‘RAPPORT’ referred as INB (Interest Bonds) is created in the
CMESS table.
A new control ‘3090 – Check Bond Interest vs Ledger’ is created in FDMUT01
screen. Interest Accounts are linked to RAPPORT code ‘INB’. Control is setup

P a g e | 39
 Release Notes

and fund or NAV group is linked.

The new control will drill down to the SDNAU00 report. The WEM exception
occurs when there is mismatch in bond interest amount with general ledger
amount.
 Interest on Bonds: Value from the 900 report
 General Ledger: Value from Account Positions

P a g e | 40
 Release Notes

3. Enhancements
This section briefly describes the product feature enhancements made in this release. Separate
sections provide the details of the enhancements for each Multifonds product.

3.1. Enhancements of Fund Accounting (FA)

The enhancements made for the Release 4.6 Fund Accounting (FA) product are listed below:

3.1.1. Charges
The enhancements made for the Functional Area ‘Charges’ are listed below:
3.1.1.1. Automatic Foreign Fee Payment

JIRA Reference MFONDS-2292

URL for Feature Demo MFONDS-2292/Feature Video

URL for Test Cases MFONDS-2292/Test Cases

Functional Area Charges

Impacted N/A
Functionalities

Existing Functionality This enhancement is for “Auto NAV 4” functionality to allow accurate automatic
fee payment for a foreign currency fee. The logic of method code 21 fee
payment is to retrieve the “frozen” asset side accrual expressed in foreign
currency as of last NAV of previous period and apply the trade date exchange
rate (or latest exch. Rate stored in MF prior to fee payment Trade date) to
calculate the fund currency P&L side fee amount.
This enhancement will be built with suffix fee field on “Auto NAV 4” + method
code 21 will be built with “suffix fee” been selected/unselected.

Enhancement Currently, the application does not have the below functionalities.
 Automatic fee payment with method code 21.
 Settlement with ‘suffix fee’ is not accurate.

3.1.1.2. Amount Type 48 and 49 with Calc. Code 01

JIRA Reference MFONDS-2297

URL for Feature Demo MFONDS-2297/Feature Video

URL for Test Cases MFONDS-2297/Test Cases

P a g e | 41
 Release Notes

Functional Area Charges

Impacted N/A
Functionalities

Existing Functionality Currently, it is not possible to link amount types 48 and 49 and calc. code 01 in
the screen FDFPR11 (Fees parameters). Amount types 48 and 49 have been
limited to calc. code 02.

Enhancement This enhancement is for the amount types 48 and 49 which is used to manage
the calculation of rebate fees. The main objective is to have the fees amount
calculated before the sub-total NAV. The sub-total NAV is used for calculating
other management fees so the rebate must be included in the sub-total NAV to
avoid any impact.

3.1.2. NAV Processing and Reporting

The enhancements made for the Functional Area ‘NAV Processing and Reporting’ are listed
below:
3.1.2.1. Cross Rate for MCMC Funds

JIRA Reference MFONDS-2308

URL for Feature Demo MFONDS-2308/Feature Video

URL for Test Cases MFONDS-2308/Test Cases

Functional Area NAV processing and reporting

Impacted N/A
Functionalities

Existing Functionality Each FX group can be defined in two levels. Namely the Fund level
(maintained in screen: FDCHS05) and the global level (maintained in screen:
FDMON05). Rates belong to same group can be different depends on the
level.

Enhancement MCMC fund stands for “Multi Class Multi Currency”. The funds which are
MCMC contain Multiple Class and Multiple Currency for each class. Currently,
there are a few funds that have been setup with multi-class multi-currency
structure in Multifonds. For these funds, after calculating the NAV, bid and
offer price in fund base currency, there is an additional step to apply the spot
FX rate to convert the 3 prices from fund base currency to class currency.
Meanwhile, the application allows users to input a fund level spot FX rate for
valuation. This enhancement is to sort out the compatibility issue for the two
functionalities.

P a g e | 42
 Release Notes

3.1.3. Other
The enhancements made for the Functional Area ‘Other’ are listed below:
3.1.3.1. Prisma Fund Code

JIRA Reference MFONDS-2296

URL for Feature Demo MFONDS-2296/Feature Video

URL for Test Cases MFONDS-2296/Test Cases

Functional Area Other

Impacted N/A
Functionalities

Existing Functionality Currently when the user extracts the Prisma file, the system adds one “0” zero
to the initial fund code.
So when the user inserts 7 numbers, in the extract it becomes 8 (7 numbers +
the additional hardcoded “0”).
This is causing 2 inconveniences in the application, and those are:
 Code becomes wrong because of the additional 0
 Field after the fund code is in wrong position and it is necessary to do
manual adjustment

Enhancement This enhancement is to ensure that 7 digits are correctly extracted. This is
going to apply to all Prisma reporting.
If the user inserts less than 7 digits, then at extraction step, application will add
the appropriate number of “0” so that in the Prisma extraction, it displays 7
digits.

3.1.3.2. Fee Suffix 4 for Monthly Funds

JIRA Reference MFONDS-2300

URL for Feature Demo MFONDS-2300/Feature Video

URL for Test Cases MFONDS-2300/Test Cases

Functional Area Other

Impacted N/A
Functionalities

Existing Functionality Currently there are 3 different suffixes in the application, and those are:

P a g e | 43
 Release Notes

 P&L account suffix 0: daily accrual of the fees (NA entry)

 P&L account suffix 1: fee payment (CH entry)
 P&L account suffix 2: settlement of the fee payment (SE entry)

Enhancement A new suffix has been introduced i.e., 4 for monthly funds for reporting
purpose.
Suffix 4 is introduced for Actual fee settlement in order to not offset suffix
1(replace suffix 1 entry with suffix 4 so as to maintain balance is suffix 1 for
reporting purposes).

3.1.3.3. Rebate Fee by Specific Management Company

JIRA Reference MFONDS-2301

URL for Feature Demo MFONDS-2301/Feature Video

URL for Test Cases MFONDS-2301/Test Cases

MFONDS-2301/Test Cases

Functional Area Other

Impacted N/A
Functionalities

Existing Functionality Currently there are few limitations in the use of rebate fees and those are:
 Rebate fees are booked on a unique account that doesn’t allow to
distinguish rebate fees by management company
 It’s not possible to settle rebate fees with different frequency
accordingly to the management company
Currently, the system includes all the management companies under the same
amount type regardless of the frequency.

Enhancement This enhancement is to manage rebate fees by management company. The

payment frequency is not the same for all companies, some management
companies pay the fees monthly and others pay the fees quarterly.
With this enhancement the enable user will be able to do the following
 distinguish the rebate fees by management company
 settle rebate fees with different frequency according to the
management company

P a g e | 44
 Release Notes

3.1.1. Price and Other Market Data

The enhancements made for the Functional Area ‘Price and Other Market Data’ are listed below:
3.1.1.1. Auto Refresh Forward FX

JIRA Reference MFONDS-2322

URL for Feature Demo MFONDS-2322/Feature Video

URL for Test Cases MFONDS-2322Test Cases

Functional Area Price and Other Market Data

Impacted N/A
Functionalities

Existing Functionality Currently, it is only possible to flag or unflag the parameter ‘Auto. refresh
forward FX’.
If the screen ‘FDTAU02’ (for funds with FX valuation method i.e. 4 or 7) is filled
with the needed information, the FDFEX04 screen will be filled automatically
when a NAV simulation was run. In this case it is not necessary to go into
screen FDFEX04 and process and validate the calculated forward rates for
“D”. When also the screen FDTAU02 is not filled, the system picks
automatically the spot rates and uses these rates for the FDFEX04 screen.
Also in this case it is not necessary to process and validate the forward rate as
the ‘Auto refresh forward FX’ parameter is available.
The requirement is to enhance the parameter ‘Auto. refresh forward FX’ in the
application parameter as well as in the fund details.

Enhancement Auto Refresh Forward FX field has been enhanced with values is 0, 1 and 2,
Functionality is describes as below
 When FDTAU02 screen is filled with necessary details, the FDFEX04
screen will get filled automatically with Forward rates for “D”.
 When also the screen FDTAU02 is not filled, the system picks
automatically the spot rates and uses these rates for the FDFEX04
screen.
By entering the value ‘2’, the new functionality is activated and that is:
 When FDTAU02 screen is filled with necessary details, the FDFEX04
screen will get filled automatically with Forward rates for “D” and in
addition if rates are missing in FDTAU02, the system will still break the
NAV with the existing error message “904 exchange error……Access
PtF2’.

P a g e | 45
 Release Notes

3.1.2. Valuation and Accounting Methodologies

The enhancements made for the Functional Area ‘Valuation and Accounting Methodologies’ are
listed below:
3.1.2.1. Collateral Management Enhancement

JIRA Reference MFONDS-2293

URL for Feature Demo MFONDS-2393/Feature Video

URL for Test Cases MFONDS-2293/Test Cases

Functional Area Valuation and Accounting Methodologies

Impacted N/A
Functionalities

Existing Functionality Currently with the collateral module user can manage all type of collateral
exchanges related to the lifecycle of OTC or cleared derivatives transactions.
The user can reflect all types of collateral and their position update, cash or
noncash, whether received or pledged, for all derivatives and OTC
instruments. User can valuate non cash collateral and track re-invested
collateral.

Enhancement This enhancement is to generate accounting entries regarding the collateral

contracts based on securities.
Also this is to change the account linked with cash collateral pledged operation
codes OPR and OPD.

3.1.2.2. Negative Interest

JIRA Reference MFONDS-2302

URL for Feature Demo MFONDS-2302/Feature Video

URL for Test Cases MFONDS-2302/Test Cases

Functional Area Valuation and Accounting Methodologies

Impacted N/A
Functionalities

Existing Functionality Currently the application manages negative interests for the below list of items:
 Time deposit (op codes 040, 060)
 Repo Deposit (op codes 043)

P a g e | 46
 Release Notes

 Swap Deposit (op codes 047)

 Call Deposit (op codes 041, 061)
 Repo Loan (op codes 045)
 Loan (op codes 065, M%)

Enhancement The following enhancements are going to be covered with respect to negative
interest.
Asset class in scope for negative interest enhancement are:
 Variable rate bonds (income type 2, 3, 4, 8, 9)
 TCN (old and new)
 ABS/MBS
 Cash accounts
 Variable rates deposit
 Swaps
 EQS/CFD
Events in scope:
 Define/input negative interest rate curves
 Purchase/sell
 Accruals (fix and variable rates)
 Interest payment (whether intermediary or at maturity)
 Repayment (deposit)
Valuation methods in scope are:
 Mark to market
 Linear amortization (Lx typemethods)

P a g e | 47
 Release Notes

3.1.2.3. Swap IR9 OIS

JIRA Reference MFONDS-2289

URL for Feature Demo MFONDS-2289/Feature Video

URL for Test Cases N/A

Functional Area Valuation and Accounting Methodologies

Impacted N/A
Functionalities

Existing Functionality Currently,

1. OIS rate management does not take into account the weekend and
market legal holidays, and the compounding is applied including
weekends and holidays.
2. Accrual method ‘obligataire’ on variable rate: compounding interest
and average interest.

Enhancement With this development:

1. OIS rate management will take in account the weekend and market
legal holidays, and the compounding is NOT applied on weekends and
holidays.
2. Method ‘obligataire’: This method will apply to interest accruals
valuation. Interest will start on Value date + 1 / start on following day
and with rate as of value date.

P a g e | 48
 Release Notes

3.2. Enhancements of Workflow Exception Manager (WEM)

The enhancements made for the Release 4.6 WEM product are listed below:

3.2.1. Workflow and Exception Manager

The enhancements made for the Functional Area ‘Workflow and Exception Manager’ are listed
below:
3.2.1.1. Amendment of WEM Rule 3157

JIRA Reference MFONDS-2215

URL for Feature Demo MFONDS-2215/Feature Video

URL for Test Cases MFONDS-2215/Test Cases

Functional Area Workflow and Exception Manager

Impacted N/A
Functionalities

Existing Functionality The requirement is to enhance the existing WEM rule ‘3157’ for additional op
code i.e. Op Code ‘072’.

Enhancement The control ‘3157’ is compatible with op code 070 and 078, and ensures that a
dividend and I-Reminder are not booked twice, i.e. for target funds, it might
happen that the tax components are not clear at the time of the distribution,
and so a regular dividend (op. code 070 or 078) is first booked, and then later
on (when tax information is obtained) reversed and replaced with a
corresponding I-reminder.
The control - 3157 is amended to additionally check on op code 072.
System raises an exception break for the fund when the control detects a
dividend (booked with op code 072) and one or multiple I-Reminder have been
booked for the same ex-date (i.e. Trade date). The Exception result field
displays the message “Both Dividend and I-Reminder exists with validated
status for the same Fund, Security and Trade Date” in case of OP code 072.

P a g e | 49
 Release Notes

4. Corrected Problems
This sections describes the issues reported in earlier releases of the Multifonds products and
have been corrected in this release.

4.1. List of Corrected Problems for Accounting

Below table lists all the issues reported for the Accounting product.
4.1.1. Accounting and Ledger Entries
The issues reported for the Functional Area, ‘Accounting and Ledger Entries’ are listed below:

1. MFONDS-1819
JIRA Reference

URL for Test Performed MFONDS-1819/Test Cases

Functional Area Accounting and Ledger Entries

Issue Description When executing the Yearend Closing process in FDRPS02 screen,
the ‘Select All’ check box is not getting selected automatically
through the process in the following: Report, Cambio, Security,
Equalization, US book cost, AGS, and Tax Year columns. User is
forced to select the check box manually.

2. MFONDS-2166
JIRA Reference

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description Option Exercise Trade issues:

1. When exercising an option, if the user navigates to the
Trade screen and yet to complete the transaction, the
underlying trade is still processed even if the option is not
exercised.
2. Unable to cancel underlying trade due to Cancelled option.

3. MFONDS-2172
JIRA Reference

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description An issue regarding the fee code 74/75. The rounding amount has
been posted with fee code 74. The “Stockex / forex” parameter is N
at fund master so system should not use the fee code 74/75
instead it should use fee code 99.

P a g e | 50
 Release Notes

4.
JIRA Reference MFONDS-2174

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description After creating a sale on a USD asset, the cost relief is incorrect.
System seems to be using GL movement in CAD and converting
using historical exchange rate available.

5.
JIRA Reference MFONDS-2177

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description Issues regarding the booking of Coupon on Zero Position on trade
date basis.
1. The coupon generated on zero position security is hitting
directly the cash account and not generating the SE
(settlement) entries which are causing the integration
failure for downstream feed.
2. The coupon generated on zero position security does not
populate the FVA tag.

6.
JIRA Reference MFONDS-2345

URL for Test Performed MFONDS-2345/Test Cases

Functional Area Accounting and Ledger Entries

Issue Description An issue is encountered in the Half Automatic Settlement screen

and report, on a fund which has thousands of cfd’s. When the
settlement of thousands of cfd’s closures is reversed in the normal
way via 'settled' in the Half Automatic screen, most of the
settlement reversals are incorrectly done.
7.
JIRA Reference MFONDS-2420

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description Issue with CO entry with Cambio F. The accounting entry with
realized P/L has unbalanced entry.

P a g e | 51
 Release Notes

8.
JIRA Reference MFONDS-2210

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description Different netting behavior when the check box" Split Int" is selected
in FDPTF02 screen.

9.
JIRA Reference MFONDS-2441

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description WEM: Control 3137 is considering the outstanding transactions for
the calculation.

10.
JIRA Reference MFONDS-2453

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description When booking an IRA or IRB for a performance swap, the realised
amount booked in fee code IH, is split between IH and another fee
code (blank) - management of cambio.

11.
JIRA Reference MFONDS-2533

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description When the new forms timer functionality is turned on, it causes
slowness when opening screens with the edit or view button.

12.
JIRA Reference MFONDS-2537

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

Issue Description Field unit amount in FDCOU09 screen is showing as asterisk.

13.
JIRA Reference MFONDS-2557

URL for Test Performed N/A

Functional Area Accounting and Ledger Entries

P a g e | 52
 Release Notes

Issue Description Reversals are missing from the cash movements report
(SDCPT06).

4.1.2. Charges
The issues that are reported for the Functional Area, ‘Charges’ are listed below:

14.
JIRA Reference MFONDS-2534

URL for Test Performed N/A

Functional Area Charges

Issue Description This issue is related to rights on deals in FDFPR11 screen. User is
able to add/edit with the read access.

4.1.3. Corporate Actions

The issues that are reported for the Functional Area, ‘Corporate Actions’ are listed below:

15.
JIRA Reference MFONDS-2170

URL for Test Performed N/A

Functional Area Corporate Actions

Issue Description An issue with unique lot ID functionality where system is not
assigning the contract number on security resulting out of
corporate action.
16.
JIRA Reference MFONDS-2457

URL for Test Performed N/A

Functional Area Corporate Actions

Issue Description Error message is prompted when a new fund is added to a new
charge ID.

17.
JIRA Reference MFONDS-2554

URL for Test Performed N/A

P a g e | 53
 Release Notes

Functional Area Corporate Actions

Issue Description There is an issue while booking a dividend with an Op.code EK4
dividend half income, the net dividend amount underneath is
constantly changing while tabbing down in the taxation fields of the
mask.

4.1.4. Equalization and Tax

The issue that is reported for the Functional Area, ‘Equalization and Tax’ is listed below:

18. MFONDS-2423
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

Issue Description Following issues are identified in the SFC equalization for year-end
process:
1. Carry forward RNI excluded the category 'Other RNI'.
2. RNI per share is not the same in SDEGA01 and FDACT04.
3. Not able to verify the split of subscription/redemption
amount after running year end process.

19. MFONDS-2213
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

Issue Description When the fund has a target fund in its positions, then the
FDEGA10 values are not correct anymore.

20. MFONDS-2437
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

Issue Description Current year distribution is not included in SDEGA14 report

21. MFONDS-2438
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

P a g e | 54
 Release Notes

Issue Description The content of the Warning message which is displayed for the
Immobilien tax is wrong.

22. MFONDS-2466
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

Issue Description The account balances and equalization are incorrect in SDEGA28 /
SDEGA09.

23. MFONDS-2535
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

Issue Description Realized AG2 not correct in case of a target fund sale (fee code
SU).

24. MFONDS-2536
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

Issue Description At the last day of the year end, after simulation and accounting
THE FIGURES IN THE SDEGA35 are not correct.

25. MFONDS-2541
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

Issue Description Rebooking, after reminders are accounted, lead to wrong

accounting entries of the rebooked target fund.

26. MFONDS-2550
JIRA Reference

URL for Test Performed N/A

Functional Area Equalization and Tax

Issue Description Distributed of prior year is not displayed in SDEGA10 report.

P a g e | 55
 Release Notes

4.1.5. Financial Instruments and Transaction Processing

The issue reported for the Functional Area, ‘Financial Instruments and Transaction Processing’
is listed below:

27.
JIRA Reference MFONDS-1822

URL for Test Performed MFONDS-1822/Test Cases

Functional Area Financial Instruments and Transaction Processing

Issue Description NAV Simulation error - The system is blocking the NAV Simulation
of Fund holding assets tagged with FVA tag N/A, where Y002
valuation method is applied. With Y002 method, there is no
unrealized booking so system should not check the NAV code 919
and allow simulation; even 919 NAV code is not setup in the NAV
Code Parameterization screen.

28.
JIRA Reference MFONDS-2321

URL for Test Performed MFONDS-2321/Test Cases

Functional Area Financial Instruments and Transaction Processing

Issue Description The Exit button in the Shareholder Dividend screen seems to be
not working.

29.
JIRA Reference MFONDS-1900

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Duplicate lot numbers are created from security, which is created
from corporate action.

30.
JIRA Reference MFONDS-1901

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description The fields

'DWH.AMS_NAV_ARC_OUT_COUP_DIV.A_TAX_WITHHELD' &
'DWH.AMS_NAV_ARC_OUT_COUP_DIV.A_TAX_WITHHELD_PT
F' are not populated in the infocenter
'DWH.AMS_NAV_ARC_SDPRM07' table.

P a g e | 56
 Release Notes

31.
JIRA Reference MFONDS-2167

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description System is wrongly allocating the sale quantity across lots under
HIFO method when trades are coming through XIP.

32.
JIRA Reference MFONDS-2168

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description When a security is rolled to its maturity date with the redemption %
in security master set to 100 on the same date, an error message
'BO Accounting Error-Phase PARAMETERS CONTROLAccount
Amount required for code 206' is displayed.

33.
JIRA Reference MFONDS-2173

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description When trying to run the EOD NAV an oracle error message 'NAV
Accounting Failure - ORA-06502: PL/SQL: numeric or value error
12169' is displayed.

34.
JIRA Reference MFONDS-2175

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description In the existing Industry ID (FDIND01) screen under security master,
the system is correctly validating the input of 'Indust Code' that
matches with Branch and 'Ind Id', but the same validation is not
working other way around when user try to update the "Ind Id" field
which has "Indust Code" already linked to it.

35.
JIRA Reference MFONDS-2176

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description When a payup (Op Code: 115) transaction is populated on a

P a g e | 57
 Release Notes

foreign asset, the system is calculating unbalanced transaction

entries.

36.
JIRA Reference MFONDS-2205

URL for Test Performed MFONDS-2205/Test Cases

Functional Area Financial Instruments and Transaction Processing

Issue Description A soft error 'no settled position for the value date entered' is
displayed for a particular fund when the position that is to sell is
settled.

37.
JIRA Reference MFONDS-2440

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Accounting entries for 20A transaction are incorrect for foreign
currency securities as the fund currency cost to be delivered is
incorrect due to rounding limitation on the average FX rate used.

38.
JIRA Reference MFONDS-2445

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Client requires the possibility to access the interest calculation
method '7' for US bonds (cusance).

39.
JIRA Reference MFONDS-2455

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Irrelevant warning message for FS & FX Trade is displayed in the
Detailed Interface Journal (RINTF3A2) report.

40. MFONDS-2458
JIRA Reference

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description When booking a capstock and tabbing through the fields, the cursor
gets stuck in the Exchange Rate field.

P a g e | 58
 Release Notes

41.
JIRA Reference MFONDS-2392

URL for Test Performed MFONDS-2392/Test Cases

Functional Area Financial Instruments and Transaction Processing

Issue Description Reports 'SDCOU05' and 'SDCOU06' are blank and not capturing
settled dividends and coupons information when generated.

42.
JIRA Reference MFONDS-2472

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description When there is a pay down effective date fall in between trade date
and value date for MBS trade, it is causing the issue of incorrect
gross amount in MFFA Front End.

43.
JIRA Reference MFONDS-2474

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Error is encountered when reversing the option close transaction.

44.
JIRA Reference MFONDS-2475

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Issue regarding Security Borrowing with cash for French funds.
45.
JIRA Reference MFONDS-2551

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Fee code 99 not triggered for Cambio C funds.

46.
JIRA Reference MFONDS-2565

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Issue with booking option transactions on two segment funds
screens FDOPT03 and FDNEC02. while interfacing - two openings

P a g e | 59
 Release Notes

and wrong link of the second transaction Master-Segment,\ manual

booking - two openings on the Master fund instead of one opening
and one continuation.

47.
JIRA Reference MFONDS-2566

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description Issue when processing options transactions

Issue is with the processing options. The “accounting finished”
message is there but when checked in the list of option trades and
pricing screen the options are not available.

48.
JIRA Reference MFONDS-2571

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description The lending repayment, through the screen FDBOU10, of the
complete position doesn’t work.

49.
JIRA Reference MFONDS-2578

URL for Test Performed N/A

Functional Area Financial Instruments and Transaction Processing

Issue Description When processing a partial or full swap termination, an error occurs
unless you enter value date and ccy next to fees.

P a g e | 60
 Release Notes

4.1.6. Infocenter
The issues that are reported for the Functional Area, ‘Infocenter’ are listed below:

50. MFONDS-1827
JIRA Reference

URL for Test Performed MFONDS-1827/Test Cases

Functional Area Infocenter

Issue Description In AMS_HIS_PTF_VAL table, the column 'A_PNL_MARKET_LCY'

is reporting wrong value for some assets. The issue is occurring
only on Blended Payment Bond assets purchased at price of
100.00.

51.
JIRA Reference MFONDS-1896

URL for Test Performed N/A

Functional Area Infocenter

Issue Description Transaction movements are getting exported/duplicated to

AMS_CASH_MVT_NEW table with every NAV export run on same
Fund Accounting date (FAD).

52.
JIRA Reference MFONDS-2162

URL for Test Performed N/A

Functional Area Infocenter

Issue Description An issue in ‘A_INTEREST’ field in ‘AMS_MVT’ &

‘AMS_HIS_PTF_VAL’ tables where the system is populating wrong
interest amount when interest amount is manually forced at the
time of trade booking.

53.
JIRA Reference MFONDS-2163

URL for Test Performed N/A

Functional Area Infocenter

Issue Description Coupon reversal is not getting displayed in movement in

‘AMS_ACC_POS_NEW’ table whereas same movement is
accounted correctly in ‘AMS_CASH_MVT_NEW’ table, and thus
causing mismatch in ending balance between movement and
position table.

P a g e | 61
 Release Notes

54.
JIRA Reference MFONDS-2169

URL for Test Performed N/A

Functional Area Infocenter

Issue Description Paydowns and settlements are missing in

'AMS_CASH_MVT_NEW' table when user manually generates
settlements on paydown and coupon.

55.
JIRA Reference MFONDS-2178

URL for Test Performed N/A

Functional Area Infocenter

Issue Description An issue in A_ACCRUED_INTEREST field in AMS_HIS_PTF_VAL

table where system is not accruing the interest after complete sale.

56.
JIRA Reference MFONDS-2365

URL for Test Performed MFONDS-2365/Test Cases

Functional Area Infocenter

Issue Description When a Shareholder Dividend is reversed, the time-stamp is not

getting updated in the MFFA front-end as well as in the database
tables that store the shareholder dividend information.

57.
JIRA Reference MFONDS-2447

URL for Test Performed N/A

Functional Area Infocenter

Issue Description NAV validation - Export to Infocenter database performance issue.

P a g e | 62
 Release Notes

4.1.7. Interfaces
The issues that are reported for the Functional Area, ‘Interfaces’ are listed below:

58.
JIRA Reference MFONDS-1809

URL for Test Performed N/A

Functional Area Interfaces

Issue Description When user loads positions into MF on bonds in GA migration

context, it is expected to populate the Carrying Value field, but for
some positions on bonds, the Carrying Value field remains 0, which
is not correct.

59.
JIRA Reference MFONDS-2164

URL for Test Performed N/A

Functional Area Interfaces

Issue Description When a security transaction is loaded into MF without mandatory

program level 'UDF', the system is not using default program level
of 'NOTRQ' on transaction.

60.
JIRA Reference MFONDS-2359

URL for Test Performed MFONDS-2359/Test Cases

Functional Area Interfaces

Issue Description TCN transaction when booked via Interface gets accounted even
with wrong calculation code. But when booked manually, a
blocking error message is getting displayed stating the use of
wrong calculation code.

61.
JIRA Reference MFONDS-2450

URL for Test Performed N/A

Functional Area Interfaces

Issue Description Issue on booking a subscription/redemption via Interface on

Automatic Pooling fund. The subscription/redemption when booked
automatically, the increase/decrease is not working properly.

P a g e | 63
 Release Notes

62.
JIRA Reference MFONDS-2538

URL for Test Performed N/A

Functional Area Interfaces

Issue Description While indicating an operation code in the interface data file for fee
payment, with specific funds, the file is injecting payments for fees
no longer belonging to the fund indicated in the file. Instead, it
takes only the first in order of the parameterized fees in the
FINTF23 screen (for operation code equivalences) even if the fee
is not linked to the fund.
This issue is for many funds and fee payments and the operational
risk is high.

63.
JIRA Reference MFONDS-2573

URL for Test Performed N/A

Functional Area Interfaces

Issue Description Multifonds 4.0 does not populate D_ACC in

AMS_DEAL_CALL_DEPOSIT_CHANGES for Call Deposit
Increases and Decreases (Op Code 068/069) when entered by
interface.

64.
JIRA Reference MFONDS-2580

URL for Test Performed N/A

Functional Area Interfaces

Issue Description IR8 and IR9 interface and manual is having refresh issues.

P a g e | 64
 Release Notes

4.1.8. NAV Processing and Reporting

The issues that are reported for the Functional Area, ‘NAV Processing and Reporting’ are listed below:

65.
JIRA Reference MFONDS-1895

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description The Rate of Return (ROR) for FOF is not calculated correctly in
FDROR01 screen.

66.
JIRA Reference MFONDS-1902

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description When CP2 process is run multiple times on same fund accounting
date, trace mode error message “Erreur: User-Defined
ExceptionReport already exported for the date p_Nptf ,load
impossible” is populated.

67.
JIRA Reference MFONDS-2360

URL for Test Performed MFONDS-2360/Test Cases

Functional Area NAV Processing and Reporting

Issue Description An error is triggered when trying to validate OSAP fund, "Valuation
Process Failure - ORA-06502: PL/SQL: numeric or value error:
number precision too large".

68.
JIRA Reference MFONDS-2417

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Duplicate entries in the MVT table for two different NAV dates.

69.
JIRA Reference MFONDS-2421

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Oracle error is displayed when printing reports 'SHJNA01 &
SHJNA02' in German.

P a g e | 65
 Release Notes

70.
JIRA Reference MFONDS-2427

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Realised gain/loss values from SDTOF06/SDTOF08 are not

populated in the TOFA - Consolidated Gains and Losses report
(SDTOF10).

71.
JIRA Reference MFONDS-2547

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Issue with generating SDSEC05 report for specific security and
dates - shows only one fund not all of the one which have this
holding. Also while selecting security with no other parameters, an
Oracle error message comes up.

72.
JIRA Reference MFONDS-2548

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description issue with data display on report SDEGA49 (accounts duplicated
and incorrectly shown YE date)

73.
JIRA Reference MFONDS-2439

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description The SDNAC07 report shows previous NAV per share for all share
classes, the same figure (e.g. share class I1) and therefore an
incorrect %-variation.

74.
JIRA Reference MFONDS-2452

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Issue with TAFO selection process. In TAFO selection process, the
MFFA application still recognizing the original cost price instead of
the amended cost price.

P a g e | 66
 Release Notes

75.
JIRA Reference MFONDS-2454

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Issue with Fully Cyclical Fees:

1. NAV Simulation error is encountered for the cyclical fees
'UB ORA-06502: PL/SQL: numeric or value error:
associative array key violates its type constraints
Book_Ap7_Fees_Amount'.
2. There is no calculation sheet which shows the fee
computation to validate the results.

76.
JIRA Reference MFONDS-2465

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Issue with Shariah language in reports. Even though the GL
description is in the Sharia language, when the report is generated,
the description automatically changes to 'English'.

77.
JIRA Reference MFONDS-2469

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description User is unable to validate numbers displayed in the ‘Non-Default

Movement' column of SDTOF10 report.

78.
JIRA Reference MFONDS-2540

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Wrong process status displayed in WEM

Different screens in WEM are showing the fund status. Once the
first step has been triggered in WEM the fund status should turn
from ‘Not started’ into ‘On going’. This is working fine if there are
not process failures in the current step. If the step fails due to
process failure then the fund status is wrongly shown ‘Not started’
instead of ‘Failed’.

P a g e | 67
 Release Notes

79.
JIRA Reference MFONDS-1540

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Description of the accounts is cut because it's too long report
SDNAV25.

80.
JIRA Reference MFONDS-2553

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Query on auto saving of pool price in MLP structure

81.
JIRA Reference MFONDS-2555

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description The user is able to generate the reports with no issue in the
production database (v4.10), however for the same fund in the UAT
database (v4.5) there is no data.

82.
JIRA Reference MFONDS-2556

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description Records are picked up and are being duplicated in the totals report.
83.
JIRA Reference MFONDS-2569

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description In MLP back value fund, you cannot simulate the B NAV of fund
when Pool share class price is changed.

84.
JIRA Reference MFONDS-2572

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

P a g e | 68
 Release Notes

Issue Description In MLP back value fund, you cannot simulate the B NAV of fund
when Pool share class price is changed.

85.
JIRA Reference MFONDS-2577

URL for Test Performed N/A

Functional Area NAV Processing and Reporting

Issue Description On Mondays, it’s not possible to process the Official NA process on
OOLP. It is possible when you remove the calendar for the NA
processes.

4.1.9. Non NAV Reporting, Views and Extracts

The issues reported for the Functional Area, ‘Non NAV Reporting, Views and Extracts’ are listed below:

86.
JIRA Reference MFONDS-2304

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Issues identified in BI Pub reports:

1. NAVHST is not picking up the dates defined on the
FDBIR10 screen.
2. LEDCAS cannot be run via the FDBIR14 screen
3. OPNINT is not displaying all fields from the data model set.
87.
JIRA Reference MFONDS-2333

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Multiple Issues when creating a report set in BI PUB:

1. An Oracle Exception error is displayed when NAVCTL
report is generated.
2. Cursor rapidly scrolls records when deleting or selecting a
set.
3. Issue in copying report set.

P a g e | 69
 Release Notes

88.
JIRA Reference MFONDS-2309

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Issue with BI PUB after patch application. All default settings in
FDBIR10 screen are erased after a patch upgrade.

89.
JIRA Reference MFONDS-2313

URL for Test Performed MFONDS-2313/Test Cases

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Securities are getting displayed in LEDAMO report even when the
valuation method is set to C. It is expected that any securities with
valuation method set to C (no valuation) will not be displayed in the
report.

90.
JIRA Reference MFONDS-2316

URL for Test Performed MFONDS-2316/Test Cases

Functional Area Non NAV Reporting, Views and Extracts

Issue Description The date format for the M2MRPT Excel report is incorrect. Also the
TAXLOT ID column is incorrect.

91.
JIRA Reference MFONDS-2327

URL for Test Performed MFONDS-2327/Test Cases

Functional Area Non NAV Reporting, Views and Extracts

Issue Description There is an issue printing the LEDDIV report when the reversal flag
input parameter is set to Y and fund has no reversals.

92.
JIRA Reference MFONDS-2331

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Issues with Market to Market (M2M) report with multiple lots such
as incorrect trade date, incorrect % change and layout issue.

P a g e | 70
 Release Notes

93.
JIRA Reference MFONDS-2332

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Issue with control 3190 and valuation method 'C'. The control is
breaking even when valuation method is set to C (no valuation).

94.
JIRA Reference MFONDS-2334

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Issue with WEM drilldown which is causing the WEM application to
freeze. User unable to proceed and needs to exit the application.

95.
JIRA Reference MFONDS-2335

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description BI PUB report Issues:

1. PRJCAS report cannot be run via the FDBIR14 screen,
2. LEDBRO report cannot be run via the FDBIR14 screen.

96.
JIRA Reference MFONDS-2340

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description If user deletes a report set using the Clear Values button, the
existing report sets too get deleted.

97.
JIRA Reference MFONDS-2341

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Issues with Amort Ledger (LEDAMO) BI PUB report.

98.
JIRA Reference MFONDS-2342

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

P a g e | 71
 Release Notes

Issue Description Issue with SECPNL report and dividends when multiple lots are
held.

99.
JIRA Reference MFONDS-2343

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Issue with LSTGLT report when run by entries by date for the
Subtotal By field.

100.
JIRA Reference MFONDS-1811

URL for Test Performed MFONDS-1811/Test Cases

Functional Area Non NAV Reporting, Views and Extracts

Issue Description The field "RENDEMENT" is not populated in

AMS.ESTI_CAL_HISTO table.

101.
JIRA Reference MFONDS-2422

URL for Test Performed MFONDS-2422/Test Cases

Functional Area Non NAV Reporting, Views and Extracts

Issue Description For funds holding positions of a fixed income securities, the Marked
to Market report (M2MRPT) is not generating and an Oracle error
'Error: ORA-01476: divisor is equal to zero' is displayed.

102.
JIRA Reference MFONDS-2464

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description The duplication of data is occurring in the master fund when a CO
entry is reversed in a segment fund of a master structure and is
then replicated in the master.

103.
JIRA Reference MFONDS-2471

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Issue with depobank export.

P a g e | 72
 Release Notes

104.
JIRA Reference MFONDS-2575

URL for Test Performed N/A

Functional Area Non NAV Reporting, Views and Extracts

Issue Description Incorrect accounting date is shown in the D_ACC column of the
infocentre table AMS_DEAL_SWAP_REMB when a swap
termination is reversed.

4.1.10. Others
The issues that are reported for the Functional Area, ‘Others’ are listed below:

105.
JIRA Reference MFONDS-1899

URL for Test Performed N/A

Functional Area Other

Issue Description When calculating the price on a Blended Payment bond, the
principal payment at the end is using the difference between the
amount paid and the original issue capital instead of the factored
issue capital as of date of inquiry.

106.
JIRA Reference MFONDS-2165

URL for Test Performed N/A

Functional Area Other

Issue Description System is taking the 'Year to Date Income' account amounts and
applying the most recent income statement rate to the total amount
in order to crystallize 'Quarter End Income' accounts instead of
quarter end income statement rate.

107.
JIRA Reference MFONDS-2171

URL for Test Performed N/A

Functional Area Other

Issue Description An issue in UDF Transaction screen where the system allows
storing the UDF in Transaction screen but it does not roll back the
changes if transaction is aborted due to system session time out.

P a g e | 73
 Release Notes

These UDF values are stored with blank contract and entry number
and get copied over to next transaction causing the wrong UDF
tagged with following transaction and UDF with blank contract and
entry number are exported to IC tables resulting integration failure
during downstream feed.

108.
JIRA Reference MFONDS-2391

URL for Test Performed MFONDS-2391/Test Cases

Functional Area Other

Issue Description An issue with frequency codes on calendar at fund master level, as
the codes are getting disappeared fully for all the French Back
Value funds since MFFA upgrade to version 4.20.

109.
JIRA Reference MFONDS-2418

URL for Test Performed N/A

Functional Area Other

Issue Description WEM: Drilldown access is only possible with password for each
rule and screen in the report.

110.
JIRA Reference MFONDS-2429

URL for Test Performed N/A

Functional Area Other

Issue Description An error message is getting displayed in the Half Automatic

Settlement screen due to a long description in CO entries.

111.
JIRA Reference MFONDS-2446

URL for Test Performed N/A

Functional Area Other

Issue Description An issue related to SFC distribution. The quantity displayed in the
Distribution screen is not correct when it is a back date distribution.

112.
JIRA Reference MFONDS-2449

URL for Test Performed N/A

Functional Area Other

Issue Description Issue with the security borrowing with cash at the maturity date.

P a g e | 74
 Release Notes

The repayment fails when done through automatically, and when

through manually, a blocking error message is displayed.

113.
JIRA Reference MFONDS-2456

URL for Test Performed N/A

Functional Area Other

Issue Description Performance and locking issue in MFFA v4.5 release.

114. MFONDS-2459
JIRA Reference

URL for Test Performed N/A

Functional Area Other

Issue Description An error is prompted when the user tries to login to MFFE (SUP
FRONTEND).

115. MFONDS-2467
JIRA Reference

URL for Test Performed N/A

Functional Area Other

Issue Description When trying to exit the screen ‘FDOPT01’ by pressing the keys
ALT + A and then E, the application freezes and the session needs
to be restarted.

116. MFONDS-2477
JIRA Reference

URL for Test Performed N/A

Functional Area Other

Issue Description Wrong date format in the WEM Variance View screen.

117. MFONDS-2542
JIRA Reference

URL for Test Performed N/A

Functional Area Other

Issue Description When the user triggers physical exercise for FX option, user fail to
change the corrsp. Sale.

118. MFONDS-2558
JIRA Reference

URL for Test Performed N/A

Functional Area Other

P a g e | 75
 Release Notes

Issue Description Issue with parameter copy function in report configuration screen.

119.
JIRA Reference MFONDS-2570

URL for Test Performed N/A

Functional Area Other

Issue Description Audit trail report is not displaying the new value.

120.
JIRA Reference MFONDS-2579

URL for Test Performed N/A

Functional Area Other

Issue Description In “Maturity Automatic Manual” screen FDMAU01, there are two
functionalities which are not meeting the expectations.
1) The user has the right and access to add or delete the
configuration even there is no right assigned through the screen
“Right on deal” FDDEO01.
2) The user is able to view and delete the funds which are not
being assigned to this user through the screen “right on fund”
FDDVF01

4.1.11. Price and Other Market Data

The issue that is reported for the Functional Area, ‘Price and Other Market Data’ is listed below:

121.
JIRA Reference MFONDS-1898

URL for Test Performed N/A

Functional Area Price and Other Market Data

Issue Description While calculating interest on a Blended Payment bond, the interest
is calculated incorrectly.

P a g e | 76
 Release Notes

4.1.12. Static Data

The issue that is reported for the Functional Area, ‘Static Data’ is listed below:

122. MFONDS-2385
JIRA Reference

URL for Test Performed MFONDS-2385/Test Cases

Functional Area Static Data

Issue Description Fund is not rolling to the date set in the Calendar with the AC
process date roll.

123. MFONDS-2424
JIRA Reference

URL for Test Performed N/A

Functional Area Static Data

Issue Description Following issues are identified:

 When Maker removes the value from the “long description,
input value” column in the UDF security (FDSEC56)
screen, the 'Outstanding' button is automatically disabled.
 Maker is not able to exit the Security Creation (FDSEC01)
screen, when Maker removes the value from 'GRP UDF'
field.

124. MFONDS-2428
JIRA Reference

URL for Test Performed N/A

Functional Area Static Data

Issue Description Issue with fund equivalents as the equivalent mapping is not
working.

125. MFONDS-2552
JIRA Reference

URL for Test Performed N/A

Functional Area Static Data

Issue Description User is getting the error in Share value screen, if share values are
more than three.

126. MFONDS-2559
JIRA Reference

URL for Test Performed N/A

Functional Area Static Data

P a g e | 77
 Release Notes

Issue Description The sub menu ‘High low price’ (menu path: Sec. -> High low price)
is not visible while defining a profile via the screen FDPROF1.

127. MFONDS-2567
JIRA Reference

URL for Test Performed N/A

Functional Area Static Data

Issue Description Rights to 'Rights on Tool' cannot be given at User Group level.

128. MFONDS-2568
JIRA Reference

URL for Test Performed N/A

Functional Area Static Data

Issue Description When same maker updates the details in FDPTF13 for say 3
different funds, once checker authorised , all 3 funds are getting
accounted at the same time.

129. MFONDS-2581
JIRA Reference

URL for Test Performed N/A

Functional Area Static Data

Issue Description There are two issues which are explained below:
1. When user edits the effective period in scale , upon authorized, it
does not get reflected in FDFPR14 charge scale
2. When 1 fund is deleted and few funds are added to the existing
nav charge. Upon authorizing, an oracle error occurs.

4.1.13. Workflow and Exception Manager

The issue that is reported for the Functional Area, ‘Workflow and Exception Management’ is listed below:

130. MFONDS-2413
JIRA Reference

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description 'Savepoint' error is received in two funds after the last release.

131. MFONDS-2419
JIRA Reference

URL for Test Performed N/A

P a g e | 78
 Release Notes

Functional Area Workflow and Exception Manager

Issue Description WEM control 3123 is not taking the latest NAV price for the
calculation of Swing price.

132. MFONDS-2436
JIRA Reference

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description WEM: Control 3177 - No Exception for a specific case, when the
coupon is booked and is in outstanding status.

133. MFONDS-2448
JIRA Reference

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description WEM: Control 3141 - Wrong calculation of previous NAVs within
the Variance View screen.

134. MFONDS-2460
JIRA Reference

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description WEM control 3125 is checking the currency used in the FX/FS
transaction and raises a break if the currency does not match
either with fund or share class currency. The exception item
displays wrong text instead of the currency and unnecessary fields
are also getting displayed.

135. MFONDS-2461
JIRA Reference

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description After giving rights to Drill Down menu, the user is not able to view
the FDSEC10 screen.

136. MFONDS-2470
JIRA Reference

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description Performance issue in NAV PG group when processing through

WEM.

P a g e | 79
 Release Notes

137.
JIRA Reference MFONDS-2476

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description The issue is that the 3175 rule is not recognizing the first Official
NAV after year-end and so considers the Account Balance instead
of the Daily Variation.

138.
JIRA Reference MFONDS-2539

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description Post validation of exceptions in Step Accounting, the step

Accounting remains in status On Going instead of Success. Also
processing of validation is not possible.

139.
JIRA Reference MFONDS-2549

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description WEM control 3030 is not working in FoF structure.

140.
JIRA Reference MFONDS-1494

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description WEM control 3175 causing process failure with the following error
message:
NAV Exception Monitor Failed – Nav Control 3175: Zero Divisor
Error for group 3175
141.
JIRA Reference MFONDS-2574

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description QWM user definable control not working correctly if greater and
less are used in the same control sequence

P a g e | 80
 Release Notes

142.
JIRA Reference MFONDS-2576

URL for Test Performed N/A

Functional Area Workflow and Exception Manager

Issue Description It is not possible to unconfirm a Fund, after the Fund was
confirmed in WEM, prior to be delinked the from the WEM
Scheduler process group, the Fund was originally linked to.

P a g e | 81
 Release Notes

5. Known Issues and Resolution

Issues which exist in the Multifonds release version 4.6 and will be resolved in the future
releases are considered as Known Issues.

For each of these issues, a workaround Resolution is identified. This section lists the known
issues and the workaround Resolution developed for the issues.

Below is the given list of issues that occur in this release. Use the suggested workaround
provided in the table to resolve each issue (if applicable to your environment)

Issues are grouped based on the Multifonds products.

5.1. List of Accounting Known Issues

There is no known issue for this release.

P a g e | 82