Ideas

Constraints or Validation checks at Database Level to avoid data related issue

Need to release constraints or validation checks at Database Level (Oracle & SQL) to avoid data related issue which are yet to be identified and also to prevent future issues.

For example:

1- DC getting tagged twice in Sales Invoice / Transfer Out

2- POS GR document getting tagged twice in Sales Return

3- POS GR receive records status is getting updated even though its corresponding entry is not yet done.

4- POS GRC quantity population is not correct at times, need to impose check to validate Send = Receive + Damage + Shot / Excess 

5- Authorisation details validation along with transaction record status.  

Similar to this other points which are identified at DB level.

 

 

  • Product Team
  • Jun 27 2016
  • Likely to implement
POS
  • Attach files
Note : Do not post a lengthy title for an Idea. Post your Idea clearly supported by Screenshots, Examples and Case Studies (if possible).