2010 Dec 20 10:14 AM
In our project client have a new requirement which does not meet through standard process.
The requirement is
A customer want to out sort all those documents at billing level which does not meet specific criteria.
In project we are using price class (which is Residential or No-Residential) and rate category which is also (Residential and Non-Residential ) combination to bill the customer
if Customer Installation is assigned to Residential Class but the device which is assigned to installation have price class as a Non-Residential. then while creating Billing By *EASIBI or EAMABI * system will Outsort the document.
**Actual Client Query is as below-
The requirement is that user will be not able to assign (manually) for example non residential service charge when rate category is residential.
Issue 2 - there were a lot of cases found with this type of error and validation is NEEDED. Please evaluate both and prepare specs with solution.
Any suggestion helps a lot.
2010 Dec 20 5:35 PM
There is no easy way to do this as standard system does not differentiate residential vs non-residential. You will have to store that in some custom table or come up with a naming convention that will differentiate them(for instance, all residential rate categories start with R).
You can also keep a valid set of combinations in a custom table (this rate category is valid for this charge or something like that). But having a consistent way of knowing what is residential and what is not is essential for the programmer to code for it and the most effective way of achieving that is using a naming convention that has a logic to it.
2010 Dec 20 5:35 PM
There is no easy way to do this as standard system does not differentiate residential vs non-residential. You will have to store that in some custom table or come up with a naming convention that will differentiate them(for instance, all residential rate categories start with R).
You can also keep a valid set of combinations in a custom table (this rate category is valid for this charge or something like that). But having a consistent way of knowing what is residential and what is not is essential for the programmer to code for it and the most effective way of achieving that is using a naming convention that has a logic to it.