[prev in list] [next in list] [prev in thread] [next in thread]
List: mifos-functional
Subject: Re: [Mifos-functional] Functional design
From: "Rijk, Bart de" <bart.de.rijk () logica ! com>
Date: 2009-04-21 10:01:14
Message-ID: FC86673B17FFA64099333F301ABA533E031F2FDF () nl-ex005 ! groupinfra ! com
[Download RAW message or body]
=
Hi Kay,
=
Thanks again for answers. My reactions are in line. Bart
From: Kay Chau [mailto:kchau@grameenfoundation.org] =
Sent: maandag 20 april 2009 20:11
To: Mifos functional discussions
Subject: Re: [Mifos-functional] Functional design
ofofflinecollectionsheet&collection sheet entry
=
[Bart de Rijk] What I need to know is what columns on fees, penalties,
A/C in the Collection Sheet are consistent with the A/C column in the
Collection Sheet Entry. For Collection Sheet Entry, you made clear that
we only need to capture the client/group-related fees & penalties within
the A/C field - NOT the loan- related fees/penalties as these are
covered by the collection amount. Is this also true for the Collection
Sheet itself; e.g. are the values in the fees, penalties columns in
Collection Sheet ONLY covering client/group-related fees & penalties, or
also covering fees and penalties for the loan product itself? If the
latter is true, then I'm afraid that loan officers will have a hard time
to calculate the client/group-specific part of fees & penalties out of
the overall figures. Furthermore, it would be great to know what column,
or total of columns in Collection Sheet is the exact counterpart of the
A/C column in Collection Sheet Entry. =
[Kay Chau] The first is true, the fees and penalties are listed
separately. I believe when this report is generated, all fees and
penalties due (whether it is fees due as part of a loan, or misc fees
due for the client) will be listed under "Other Collections" column and
will specify what the fee is for. For example, if a client had a misc
fee due of 4.0 with their Standard Client Loan (SCL), the Other Coll
column will list SCL:4.0 in that client row. Then, for the misc client
fee, it will list that separately in the same column. So fees/penalties
due with the loan will have the loan short name, and the other fees due
just for the client will be listed separately. Haven't fully tested
this so I will dig into this a little further =
[Bart de Rijk] Tx, please let me know your testing results. For
Collection Sheet Entry within Mifos Light, we then focus upon the
client/group-related fees and penalties, which can be derived from the
fees and penalties columns in Collection Sheet. Am I right to assume
that in Bulk Entry, we enter only one value per client regarding A/C -
e.g. an aggregation of all client/group related fees and penalties?
Hence, the guideline towards end users should be that they add up all
fees and collections which they've registrated in the Collection Sheet
under fees and collections (disregarding the Other Collections column as
this also lists loan-related fees which are irrelevant here) and assure
that value is in Collection Sheet Entry A/C field?
=
Finally, one practical question: when allowing multiple products per row
in the collection sheet entry, is there any maximum of products? If
there is, what's the maximum; is this the same as a maximum number of
products defined in Mifos in the first place? If there isn't, any
suggestions how we should design for this - the screen would need to be
horizontally scrollable, for example?[Kay Chau] I haven't tested this
myself but I don't believe there is a max - the collection sheet entry
will be able to scroll to the right as more products are there for each
client. How many different loans does each client typically have at a
time for the MFI in your scenario? =
[Bart de Rijk] I don't have data on the number of products per MFI or
per client. What I see in the Collection Sheet entry screen is that each
product will have its own column. So maybe customers have only three
products, but the MFI has a portfolio of 9 products, you'd see nine
columns and not three, if I'm right. Regarding Mifos Light, I'm afraid
we'll have to limit the number of loan product types per MFI within our
first release.
[Kay Chau] yes you're right - there would be 9 product columns
displayed, and so for the loan products that a client doesn't have, that
text box would not exist under those columns in that client row in the
collection sheet entry. =
[Bart de Rijk] Just learned that we've built it this way so no problem
here for Mifos Light.
=
Regards
Bart
=
Please help Logica to respect the environment by not printing this email /=
Pour contribuer comme Logica au respect de l'environnement, merci de ne pa=
s imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfe=
n Sie so Logica dabei die Umwelt zu schuetzen / Por favor ajude a Logica =
a respeitar o ambiente nao imprimindo este correio electronico.
This e-mail and any attachment is for authorised use by the intended recipi=
ent(s) only. It may contain proprietary material, confidential information =
and/or be subject to legal privilege. It should not be copied, disclosed to=
, retained or used by, any other party. If you are not an intended recipien=
t then please promptly delete this e-mail and any attachment and all copies=
and inform the sender. Thank you.
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:x="urn:schemas-microsoft-com:office:excel" \
xmlns:p="urn:schemas-microsoft-com:office:powerpoint" \
xmlns:a="urn:schemas-microsoft-com:office:access" \
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" \
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" \
xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" \
xmlns:b="urn:schemas-microsoft-com:office:publisher" \
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" \
xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" \
xmlns:odc="urn:schemas-microsoft-com:office:odc" \
xmlns:oa="urn:schemas-microsoft-com:office:activation" \
xmlns:html="http://www.w3.org/TR/REC-html40" \
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" \
xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" \
xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" \
xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" \
xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" \
xmlns:ds="http://www.w3.org/2000/09/xmldsig#" \
xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" \
xmlns:udc="http://schemas.microsoft.com/data/udc" \
xmlns:xsd="http://www.w3.org/2001/XMLSchema" \
xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" \
xmlns:ec="http://www.w3.org/2001/04/xmlenc#" \
xmlns:sp="http://schemas.microsoft.com/sharepoint/" \
xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" \
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \
xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" \
xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" \
xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" \
xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" \
xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" \
xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" \
xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" \
xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" \
xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" \
xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" \
xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" \
xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" \
xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" \
xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" \
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:691146905;
mso-list-type:hybrid;
mso-list-template-ids:-1822547504 1413138108 67698691 67698693 67698689 67698691 \
67698693 67698689 67698691 67698693;} @list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:20.25pt;
text-indent:-18.0pt;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Hi Kay,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks again for answers. My
reactions are in line. Bart<o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Kay Chau \
[mailto:kchau@grameenfoundation.org] <br> <b>Sent:</b> maandag 20 april 2009 \
20:11<br> <b>To:</b> Mifos functional discussions<br>
<b>Subject:</b> Re: [Mifos-functional] Functional design
ofofflinecollectionsheet&collection sheet entry<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:2.25pt'><span \
style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:2.25pt'><span style='color:#1F497D'> [Bart
de Rijk] What I need to know is what columns on fees, penalties, A/C in the
Collection Sheet are consistent with the A/C column in the Collection Sheet
Entry. For Collection Sheet Entry, you made clear that we only need to capture
the client/group-related fees & penalties within the A/C field – NOT
the loan- related fees/penalties as these are covered by the collection amount.
Is this also true for the Collection Sheet itself; e.g. are the values in the fees,
penalties columns in Collection Sheet ONLY covering client/group-related fees
& penalties, or also covering fees and penalties for the loan product
itself? If the latter is true, then I’m afraid that loan officers will
have a hard time to calculate the client/group-specific part of fees
& penalties out of the overall figures. Furthermore, it would be great to
know what column, or total of columns in Collection Sheet is the exact
counterpart of the A/C column in Collection Sheet Entry. <o:p></o:p></span></p>
<p class=MsoNormal><b><i><span style='color:#943634'>[Kay Chau] </span></i></b><span
style='color:#943634'>The first is true, the fees and penalties are listed
separately. I believe when this report is generated, all fees and
penalties due (whether it is fees due as part of a loan, or misc fees due for
the client) will be listed under “Other Collections” column and
will specify what the fee is for. For example, if a client had a misc fee
due of 4.0 with their Standard Client Loan (SCL), the Other Coll column will
list <b>SCL:4.0</b> in that client row. Then, for the misc client fee, it
will list that separately in the same column. So fees/penalties due with
the loan will have the loan short name, and the other fees due just for the
client will be listed separately. Haven’t fully tested this so I
will dig into this a little further <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>[Bart de Rijk] Tx, please let me
know your testing results. For Collection Sheet Entry within Mifos Light, we
then focus upon the client/group-related fees and penalties, which can be
derived from the fees and penalties columns in Collection Sheet. Am I right to
assume that in Bulk Entry, we enter only one value per client regarding A/C –
e.g. an aggregation of all client/group related fees and penalties? Hence, the
guideline towards end users should be that they add up all fees and collections
which they’ve registrated in the Collection Sheet under fees and
collections (disregarding the Other Collections column as this also lists \
loan-related fees which are irrelevant here) and assure that value is in Collection \
Sheet Entry A/C field?<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal>Finally, one practical question: when allowing multiple
products per row in the collection sheet entry, is there any maximum of
products? If there is, what’s the maximum; is this the same as a maximum
number of products defined in Mifos in the first place? If there isn’t,
any suggestions how we should design for this – the screen would need to
be horizontally scrollable, for example?<b><i><span style='color:#1F497D'>[Kay
Chau] </span></i></b><span style='color:#1F497D'> I haven’t
tested this myself but I don’t believe there is a max – the
collection sheet entry will be able to scroll to the right as more products are
there for each client. How many different loans does each client
typically have at a time for the MFI in your scenario? </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>[Bart de Rijk] I don’t
have data on the number of products per MFI or per client. What I see in the \
Collection Sheet entry screen is that each product will have its own column. So maybe
customers have only three products, but the MFI has a portfolio of 9 products,
you’d see nine columns and not three, if I’m right. Regarding Mifos
Light, I’m afraid we’ll have to limit the number of loan product
types per MFI within our first release.<o:p></o:p></span></p>
<p class=MsoNormal><b><i><span style='color:#943634'>[Kay Chau] </span></i></b><span
style='color:#943634'>yes you’re right – there would be 9 product
columns displayed, and so for the loan products that a client doesn’t
have, that text box would not exist under those columns in that client row in
the collection sheet entry. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New \
Roman","serif"'> <span style='color:#1F497D'>[Bart de Rijk] Just learned that \
we’ve built it this way so no problem here for Mifos \
Light.</span><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Regards<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><br>
Bart<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New \
Roman","serif"'><o:p> </o:p></span></p>
</div>
<br clear=all> Please help Logica to respect the environment by not printing this \
email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas \
imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so \
Logica dabei die Umwelt zu schuetzen / Por favor ajude a Logica a respeitar o \
ambiente não imprimindo este correio electrónico.
This e-mail and any attachment is for authorised use by the intended recipient(s) \
only. It may contain proprietary material, confidential information and/or be subject \
to legal privilege. It should not be copied, disclosed to, retained or used by, any \
other party. If you are not an intended recipient then please promptly delete this \
e-mail and any attachment and all copies and inform the sender. Thank you.
</body>
</html>
[Attachment #4 (--===============6776792519658819521==)]
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Mifos-functional mailing list
Mifos-functional@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-functional
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic