on 05-22-2010 12:59 PM
HI all,
I have defined internal number range for general task list & equipment task list.When I am creating general task first time ,system is giving one group no.Second time suppose I have keyed the t-code IA05 for general task list to create some general task list , but due to some reasons I come out from the transaction .Again when I am entering into the same t-code system is giving another group no.Suppose first time group no is 1, second time it is 2 which is not created just tried to create. third time system should give me group no as 2 only as I have not saved data in sencond time .But it is giving no 3 instead of 2.Why it is skipping? can anyone please tell me ? Also when I am creating any equipment task list that time also group no for general task list is skipping though I have defined different number range.
Please share your valuable thoughts where I need to do the settings?
rgds
rajib
Rajib,
This is because the Number within the number range has been used but however not created. This is due to buffering of the number ranges for the object. Using Transaction SNRO, Check and adjust the buffer ranges for the object. Removal of buffering would help in skipping of the numbers , but be aware that it would take a little bit longer to create the record.
Regards
Narasimhan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Narasimhan,
I have read a lot of your valuable replies in this forum...I appreicate your knowledge depth about SAP......
Below one is for the reply you posted ...
U mentioned about Buffering of the number's which is a std in SAP.......I am stuck at a point that if the number range buffers for Tasklist, which occurs if we didnt save and just come out of the transaction screen, why doesnt it do the same in case of equipment creation.
In case of equipment creation, if we come out without saving , the next time system will asign the number 1 greater than the last created one.
Please explain this discrepancy....
Hi,
Different transactions have been designed in different ways depending upon the the unique needs of that particular object.
If you look at the Task list transaction, the moment you hit enter and pass the initial create screen, you would notice that the Next number has already been assigned to this particular transaction and you would see this number being populated on the screen object.This is generally called "Early Number assignment". Hence this number has already been used, but not created and hence due to buffering when you choose create the Next number is picked up.
If you look at the Equipment Transaction, The moment you hit enter and pass the initial screen, in case of internal number assignment for the Equipment category, A temporary number has been assigned to the object and Not the Next available number as per the sequence. In this case he next available number is only picked up when you hit "SAVE".Hence the "Next" number has NOT already been identified/used and not created and hence due to this when you complete the save for the next equipment transaction the latest number from the Application server would be picked up from its buffer.
The early and late allocation of number ranges, coupled with buffering for internal number ranges in the application serve plays a part in determining what would be the next available Number for the object.
Regards
Narasimhan
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.