ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rishi Solanki <rishisolan...@gmail.com>
Subject Re: GST rates on the basis of product price or price range
Date Wed, 22 Aug 2018 17:59:22 GMT
I have now one question, weather you would like to model the min item price
and max item price. Or you are unable to fetch the data of product of
specific price range.
My answer intended to resolve the second problem which is fetching the
data. Also the HSN code is one categorization of products, but it might be
further categorized on the basis of price. Extending the entity should be
the last option to go with when we have alternate ways to handle, this also
means I'm not against the extending entity but it should be last option to
go with.

We can talk on more insights of problem you are facing.

Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co


On Wed, Aug 22, 2018 at 1:46 PM Vaibhav Jain <vaibhav.jain@hotwaxsystems.com>
wrote:

> Hello Rishi,
>
> I am working on the GST of India.
>
> One of the business rules of the GST is like:
> - Tax is applied on the basis of HSN code which is managed using
> ProductCategory entity
> - Same HSN code may have different GST rate on the basis of price
> - Goods of sale value not exceeding Rs. 1000 per piece would be taxed at 5%
> and the goods of sale value exceeding Rs. 1000 per piece would be taxed at
> 12%.
>
> As per the GST rules and existing data model price range should be
> maintained in *TaxAuthorityRateProduct* entity instead of using
> *ProductCategory* entity.
>
> One of the solutions is we can extend the *TaxAuthorityRateProduct* entity
> and introduce a new column *maxItemPrice. *Now, *minItemPrice* and*
> maxItemPrice *columns can be used to filter the records on the basis of the
> price range.
>
> Please suggest can we extend the entity or do we have any other/better
> solution to manage this scenario.
>
> Vaibhav Jain
> Sr. Enterprise Software Engineer
> HotWax Systems
> m: 782-834-1900 e: vaibhav.jain@hotwaxsystems.com
>
>
> On Tue, Aug 21, 2018 at 11:20 PM Rishi Solanki <rishisolankii@gmail.com>
> wrote:
>
> > Vaibhav,
> > Instead of trying to fetch product on field value, go for creating
> > categories for your need and make product members of them.
> > For example you may create categories 0-100, 101-200, 201-300 of type
> > OTHER_SEARCH type as many as you want. Finally associate the products
> with
> > desired categories. After that you fetching would be easy at code level.
> >
> > It will take time to setup but data fetching would be easy and
> configurable
> > easily (may be you can use some triggers to associate)
> >
> > --
> > Rishi Solanki
> > Sr Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> > www.hotwax.co
> >
> >
> > On Tue, Aug 21, 2018 at 2:42 PM Vaibhav Jain <
> > vaibhav.jain@hotwaxsystems.com>
> > wrote:
> >
> > > Hello all,
> > >
> > > *Business case:*
> > > Goods and Service Tax is India allow to apply different tax rates on
> > > the same product/product category on the basis of product
> > > price(transactional value).
> > >
> > > *Problem: In fetching data for a specific price range*
> > >
> > >    - In OFBiz the *TaxAuthorityRateProduct* entity is used to define
> the
> > >    tax rates for any product category.
> > >    - *TaxAuthorityRateProduct*.*minItemPrice* can be used to manage
> > >    different tax rates on the basis of the product price but it is
> > > difficult
> > >    to fetch the data on the basis of a specific price range using
> single
> > >    column(minItemPrice)
> > >
> > >
> > > Vaibhav Jain
> > > Sr. Enterprise Software Engineer
> > > HotWax Systems
> > > m: 782-834-1900 e: vaibhav.jain@hotwaxsystems.com
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message