We're creating business partners in CRM. For that, we've configured 'grouping' field to be available at partner creation view at webUI, so users may be able to select the desired partner number range (internal).
After they select the desired numbering 'grouping', and press <enter> key, a number is automatically assigned to current business partner, that was not yet saved at database. Then, if they press 'cancel' button , and repeat the process all over again, a new number (one more that previous one) is assigned to new business partner in memory.
By doing that many times a day, it will cause several gaps (number leaps) in partner numeration. In previous versions, with BP t-code, we could de-activate number buffering at t-code SNRO to maintan number consistency, but in these new environemnt that is no more a solution.
Did anyone dealed with this situation? If so, did you get a solution/workaround for that?
Thanks in advance.