on 02-09-2016 7:39 AM
Dear experts,
In our system, we observed few TO's for group (LT0E) are created with number greater than TO for individual issue against delivery.
Please refer below screenshot
Cl. | WhN | TO Number | MvT | MTy | S | Created | Time | Group | TR Number | PostChNo | Document | C | Conf.Date |
108 | 101 | 339490 | 641 | 601 | A | 1/31/2016 | 1:17:51 PM | 0000621446 | 0 | 0 | 0080577576 | X | 1/31/2016 |
108 | 101 | 339558 | - | 850 | A | 1/31/2016 | 2:56:18 AM | 0000621446 | 0 | 0 | X | 1/31/2016 |
For e.g. TO 339558 is created (against group) earlier but number is greater than TO 339490 (against individual issue) which is created later.
Have you faced any issue similar to this. Also I would like to know does system keep buffer number range and skips number if TO creation screen is accessed but TO is not created (like material or quant)
Waiting for your reply.
Best Regards,
Munawwar
How many application servers do you have in your system landscape?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Each application server has its own memory.
if user on application server 1 is creating a document then the number is taken from the number range. Usually the number range is buffered, which means 1 number is taken directly, the other numbers stay in the memory.
If another document is created from a user on server 2 then the system takes the next buffer interval from number range and adds it into its memory.
Then the numbers are taken from the memory until they are all eaten, and this is application server specific. If most users where active in application server 1, then this server had already several times retrieved a new buffer interval while in application server 2 the numbers from the first access where still in memory. If then a user at server 2 creates a new document it will be as in your screenshots, a smaller number will appear later than a higher number.
you can only avoid this by changing the buffers of the number range to 1, which means that your system needs to access the database more often and this costs performance.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.