Ideas

Standardize POS Document Series definition

In POS if month and year is not prefixed or suffixed with the document series logic , at times it is very difficult to identify the reason for duplicate number generation. In order the issue please check the below scenarios:

Case 1 : (Prefix) BILL /  (Running Number) 0001 / (Calander YR) 2015 interval is monthly

  • POS Installation is done in the month of Jan for 2015
  • Thus the 1st bill generated would be as BILL/00001/2015
  • Now in the month of Feb the number would be again BILL/00001/2015

Case 2 : (Prefix) BILL /  (Running Number) 0001 / (Calander YR) 2015 interval is yearly

  • POS Installation is done in the month of Jan for 2015
  • Thus the 1st bill generated would be as BILL/00001/2015
  • Now in the month of April the number would be again BILL/00001/2015

Thus it is mandatory to add Month / Year parameter to the doc series to identify the correct Bill No pertaining to the financial year or month. Day prefix would be required only if DAY wise internal is configured and that can be left open depending upon whether user wants to configure it or not.

Along with this if option is provided to tag Site CUID it will help to distinguish same number generated from two Sites. 

 

  • Harsh Nahata
  • Nov 9 2015
  • Released
POS
Released Version [For Internal use] 11.110.0-1.110.0
  • Jul 8, 2016

    Admin response

    Thanks for the idea, your suggested feature has been released. Date lierals tagging have now been made mandatory depending upon reset interval, to maintain unique document numbering. Also a new literal have been introduced, i.e. MM for month; which will reflect month in numeric. 

    Keep sharing your ideas.

  • Attach files
  • Guest commented
    April 15, 2016 13:06

    In V10 there was a Provision to attach Account Period in Suffix but couldn't able to tag this in V11

  • Guest commented
    April 15, 2016 13:05

    Additional to CUID if SHORT CODE is provided it is also usable

     

Note : Do not post a lengthy title for an Idea. Post your Idea clearly supported by Screenshots, Examples and Case Studies (if possible).