On a high level the idea is appealing, but I'm not exactly sure how this would turn up in implementation. I can see the JIRA is still empty, so perhaps the best time to vote on this is when looking at the specifics.
More specifically, I would like to understand _how_ will you limit the capability, what does the setting on party level translate to? And where is that information stored? I think all of those seem like important decisions. On Fri, May 4, 2018 at 4:03 PM, Rishi Solanki <rishisolan...@gmail.com> wrote: > Thanks Sharan for the exact use case I was looking for. > > +1 for the overall proposal. > > Rishi Solanki > Sr Manager, Enterprise Software Development > HotWax Systems Pvt. Ltd. > Direct: +91-9893287847 > http://www.hotwaxsystems.com > www.hotwax.co > > On Thu, May 3, 2018 at 2:43 PM, Sharan Foga <sha...@apache.org> wrote: > >> >> >> On 2018/05/03 06:40:43, Rishi Solanki <rishisolan...@gmail.com> wrote: >> > Hi Aman, >> > +1 for making it configurable. >> > >> > By PartyAcctgPreference.enableAccounting flag you mean for an OFBiz >> > instance if flag is enable then for that company/organization accounting >> > transactions recorded otherwise not. That also mean, for an instance we >> may >> > record the accounting transaction for one organization and do not record >> > accounting transaction for other organization. >> > >> > This is something I couldn't imagine in real world business scenario. >> >> Hi Rishi >> >> Something I've come across quite a few times is this. >> >> Imagine the case where you have several companies recording transactions >> then one stops trading temporarily or permanently, becomes insolvent or >> merges with another one, which means that from a specific date you don’t >> want it any new transactions recorded a against it. >> >> The existing transactions that have been processed are still valid in the >> previous company party and you will probably want to report on them from a >> historic perspective – but you would want to stop any new transactions >> being posted to that previous company. >> >> Thanks >> Sharan >> >> So >> > big +1 for making it configurable but not sure about weather we should go >> > for PartyAcctgPreference or may consider SystemProperty for that. >> > >> > Looking for others input, BTW, no objection on using PartyAcctgPreference >> > but thinking if it is useful to add checks/efforts for organizations over >> > same instance. >> > >> > >> > >> > Rishi Solanki >> > Sr Manager, Enterprise Software Development >> > HotWax Systems Pvt. Ltd. >> > Direct: +91-9893287847 >> > http://www.hotwaxsystems.com >> > www.hotwax.co >> > >> > On Thu, May 3, 2018 at 11:41 AM, Aman Agrawal < >> > aman.agra...@hotwaxsystems.com> wrote: >> > >> > > Hello, >> > > >> > > In current flow, if we want to disable the accounting then we need to >> > > disable the set of seca's. We don't have any configurable setting to >> > > disable accounting. >> > > So, I have a proposal to make accounting transaction entries >> configurable. >> > > We can manage this by adding a new field 'enableAccounting' in the >> > > 'PartyAcctgPreference' entity. Accounting transaction entries will be >> > > entertained accordingly. >> > > >> > > Thanks and regards, >> > > *Aman Agrawal* >> > > Sr. Enterprise Software Engineer >> > > www.hotwaxsystems.com >> > > www.hotwax.co >> > > >> > >>
