Progress of ERPNext version 3

Hi everyone,

Our work on ERPNext version 3 is going at a steady pace. Since we are practically rewriting the code of ERPNext, we are taking this opportunity to make our architecture (wnframework) much stronger, faster and more secure. We hope to make ERPNext more scalable as well.

Consequently, the estimated date to its release will have to be extended to January 2013. Therefore, the revamped Production module will also get delayed, as it will be shipped with the new version.

In the meantime, we can take some time out and make small changes in the existing production system, to make it easier for you. Please raise any concerns on the forum, and we will try to implement them in the existing system, if it is feasible to implement it in a short time. Also, we will keep working on bug reports on priority.

Thanks for all your support. We will keep you updated on our progress.

Regards,
Anand Doshi.


You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.
To post to this group, send email to er...@googlegroups.com.
To unsubscribe from this group, send email to erpnext-developer-forum+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Anand,

Great to hear about the progress of Ver 3.0, I would like to bring to your notice that currently apart from the manufacturing module there are some major things which are missing in the accounts module as well.

I would try to explain it here as to what problems we are facing in taking our accounting from Tally to ERPNEXT.

  • The P/L and B/S is not possible for a period like if someone wants a financial statement from 01-Apr to 25-Jun then this is not possible, I think a system should be robust enough to provide any kind of reporting and should not be limited by date ranges.
  • Now since we are trying to match our accounts to the ones in tally we are facing some problems like:
    • If we find a difference in B/S’s group then we have to go to either trial balance or the export multiple g/l to get the balances of all the accounts under that group
    • Like we had a difference of Rs 80 in a group “Accounts Receivable” in B/S of May-2011 now to find the difference we have to export the whole group for that month which is very tedious and time consuming.
    • The solution for such things can be that we could have links in B/S or P/L for the groups, if we click the group it would give the balances for the accounts under it. Now again if the accounts are further clicked in the report we could get the ledger of that account with date range as option.
    • Currently there is no system in ERPNEXT to check the account balances of a group’s constituents on  the screen and exporting, I think, is a much more time consuming process.

I think the above are the points which come to my mind at the moment apart from the ones which are under discussion. Do let me know if the suggestions w.r.t B/S & P/L are even implementable or not.


On Monday, September 10, 2012 9:28:01 PM UTC+5:30, Anand Doshi wrote:
Hi everyone,



Our work on ERPNext version 3 is going at a steady pace. Since we are practically rewriting the code of ERPNext, we are taking this opportunity to make our architecture (wnframework) much stronger, faster and more secure. We hope to make ERPNext more scalable as well.



Consequently, the estimated date to its release will have to be extended to January 2013. Therefore, the revamped Production module will also get delayed, as it will be shipped with the new version.



In the meantime, we can take some time out and make small changes in the existing production system, to make it easier for you. Please raise any concerns on the forum, and we will try to implement them in the existing system, if it is feasible to implement it in a short time. Also, we will keep working on bug reports on priority.



Thanks for all your support. We will keep you updated on our progress.



Regards,

Anand Doshi.



You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.

To post to this group, send email to er...@googlegroups.com.

To unsubscribe from this group, send email to erpnext-developer-forum+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/erpnext-developer-forum/-/FTBLqin3I4MJ.

For more options, visit https://groups.google.com/groups/opt_out.

 

 

Hey Rushabh & Anand


For below mentioned 4 points by Aditya, point no 2 & 3 are very much required by pepole who are habituated to use tally. Same feedback I have received from Spectra Technovision when I showed the account module to their Account and Finance Head.

If we can incorporate this it would step forward in comparison with Tally.

Regards
Viral Dhruv

---------- Forwarded message ----------
From: Addy <ad...@gmail.com>
Date: Tue, Sep 11, 2012 at 10:57 AM
Subject: [erpnext-user-forum] Re: Progress of ERPNext version 3
To: er...@googlegroups.com
Cc: "er...@googlegroups.com" <er...@googlegroups.com>


Hi Anand,

Great to hear about the progress of Ver 3.0, I would like to bring to your notice that currently apart from the manufacturing module there are some major things which are missing in the accounts module as well.

I would try to explain it here as to what problems we are facing in taking our accounting from Tally to ERPNEXT.
  • The P/L and B/S is not possible for a period like if someone wants a financial statement from 01-Apr to 25-Jun then this is not possible, I think a system should be robust enough to provide any kind of reporting and should not be limited by date ranges.
  • Now since we are trying to match our accounts to the ones in tally we are facing some problems like:
    • If we find a difference in B/S's group then we have to go to either trial balance or the export multiple g/l to get the balances of all the accounts under that group
    • Like we had a difference of Rs 80 in a group "Accounts Receivable" in B/S of May-2011 now to find the difference we have to export the whole group for that month which is very tedious and time consuming.
    • The solution for such things can be that we could have links in B/S or P/L for the groups, if we click the group it would give the balances for the accounts under it. Now again if the accounts are further clicked in the report we could get the ledger of that account with date range as option.
    • Currently there is no system in ERPNEXT to check the account balances of a group's constituents on the screen and exporting, I think, is a much more time consuming process.

I think the above are the points which come to my mind at the moment apart from the ones which are under discussion. Do let me know if the suggestions w.r.t B/S & P/L are even implementable or not.


On Monday, September 10, 2012 9:28:01 PM UTC+5:30, Anand Doshi wrote:
Hi everyone,

Our work on ERPNext version 3 is going at a steady pace. Since we are practically rewriting the code of ERPNext, we are taking this opportunity to make our architecture (wnframework) much stronger, faster and more secure. We hope to make ERPNext more scalable as well.

Consequently, the estimated date to its release will have to be extended to January 2013. Therefore, the revamped Production module will also get delayed, as it will be shipped with the new version.

In the meantime, we can take some time out and make small changes in the existing production system, to make it easier for you. Please raise any concerns on the forum, and we will try to implement them in the existing system, if it is feasible to implement it in a short time. Also, we will keep working on bug reports on priority.

Thanks for all your support. We will keep you updated on our progress.

Regards,
Anand Doshi.


I second Addy, much needed P&L and BS changes...currently using tally alongside for these reasons.


On Monday, September 10, 2012 9:28:01 PM UTC+5:30, Anand Doshi wrote:
Hi everyone,

Our work on ERPNext version 3 is going at a steady pace. Since we are practically rewriting the code of ERPNext, we are taking this opportunity to make our architecture (wnframework) much stronger, faster and more secure. We hope to make ERPNext more scalable as well.

Consequently, the estimated date to its release will have to be extended to January 2013. Therefore, the revamped Production module will also get delayed, as it will be shipped with the new version.

In the meantime, we can take some time out and make small changes in the existing production system, to make it easier for you. Please raise any concerns on the forum, and we will try to implement them in the existing system, if it is feasible to implement it in a short time. Also, we will keep working on bug reports on priority.

Thanks for all your support. We will keep you updated on our progress.

Regards,
Anand Doshi.

Hi Aditya,

Thank you for giving such valuable suggestions.

We already started working on this, will let you know when developed. We are expecting to complete it by weekend.

Regards,
Nabin Hait



On Wed, Sep 12, 2012 at 10:23 AM, Sonal <so…@gmail.com> wrote:

I second Addy, much needed P&L and BS changes...currently using tally alongside for these reasons.


On Monday, September 10, 2012 9:28:01 PM UTC+5:30, Anand Doshi wrote:
Hi everyone,

Our work on ERPNext version 3 is going at a steady pace. Since we are practically rewriting the code of ERPNext, we are taking this opportunity to make our architecture (wnframework) much stronger, faster and more secure. We hope to make ERPNext more scalable as well.

Consequently, the estimated date to its release will have to be extended to January 2013. Therefore, the revamped Production module will also get delayed, as it will be shipped with the new version.

In the meantime, we can take some time out and make small changes in the existing production system, to make it easier for you. Please raise any concerns on the forum, and we will try to implement them in the existing system, if it is feasible to implement it in a short time. Also, we will keep working on bug reports on priority.

Thanks for all your support. We will keep you updated on our progress.

Regards,
Anand Doshi.