Hie Hiep,
Am 02.11.2013 16:11, schrieb Hiep Lq:
>
> Hi Thomas.
> I success test as your guideline.
> many thanks. can you share me "how to make account dimension?"
I am in the process of implementing this. In three months I can tell you
if all of my thoughts do work. Today please decide carefully yourself
which of my words you trust. :-)
I used the "UserElement1" facility for that. There are different types
of accounting dimensions. Every one has its own specialities. I tried to
research that and up to now I collected the results (in german) on
http://wiki.idempiere.org/de/Buchf%C3%BChrungsdimensionen
I would like if someone would translate that to english and extend it. I
am sure I did not get all accounting consequences of every kind of
dimension.
The first and best dimension to do your own extensions is the "Activity"
because it has not much specialties implemented. I got this
recommendation from Carlos so you can see it as a good rule. ;-)
In my case I had already used Activities and needed a second one. I
choosed UserElement1 for that. Partly I choosed it because there are no
specialties at all and (I have to admit) partly because it was just an
interesting challenge to implement it this way...
For the UserElement1 to work you have to do in short four things:
* Activate the Dimension and connect it with a primary key field (e.g.
"HIEP_Loans_ID") of your table.
* Change the type of the UserElement1_ID column in the accounting fact
table (and views) to "table" and create a reference to your HIEP_Loan
table. (this makes reports look better)
* Create a HIEP_Loans_ID column in every document type you want to use
(invoice, payment, etc.)
* Take care that the HIEP_Loans_ID column in the documents are filled.
The last part is the hardest and might need coding. Many documents are
created from processes and you have no influence on every field. If you
create a Payment from a BankStatement where you have already an
Reference to an Invoice there is a process that creates the Payment from
the Invoice. This process does not copy the UserElement1.
I have to change that. I am not sure if this should be called a bug in
the core or if my use case is so special that I just have to write my
own processes for that.
Depending on your accounting report needs it can be important or not to
have the value copied. I need to copy it because for calculation of
interest I need the date of the payment not of the invoice.
I hope this thoughts help you. I would be glad to go on further on a
wiki page with that to collect all thoughts about the problem and create
a helpful document for others.
> HI Armenrz.
> I also like your method. I want confirm a bit about step.
>
> 1. make a invoice + payment as Thomas method
> 2. immediately make and complete a invoice with a payment schedule. and
> tracking payment for this invoice.
>
>
> On Saturday, November 2, 2013 4:33:28 PM UTC+7, armenrz wrote:
>
> You can also raise an invoice with payment schedule, let's say, with
> monthly schedule.
> The aging report is clever enough to separate all the due dates.
I thought about this first. My problem with this approach is that you
can not change the invcoice document later. E.g. you can not raise later
the loaned sum (but have to create a new document). And you can not
assign interests. You have to create also a new document for interest.
But if your loan contract sais that you do not pay the interest in one
turn (but included in your "fixed size" monthly payment) it will be not
so easy to assign and follow your payments.
So this approach may be a second way or good for a combination but this
needs some more thoughts.
(Sorry if I did not get the correct english business terms...) ;)
> Best regards,
>
> Armen Rizal
>
Goodwill.co.id <
http://Goodwill.co.id>
> <
https://groups.google.com/groups/opt_out>.
mit freundlichen Gr��en,
Thomas Bayen