QM notification doc range issue-QM11-Range is not in seq with creation date

[srinivas_s7]

Hello Experts,

I have a strange ,yet intresting issue

Issue :This is in regards to issue with quality notification number getting recycling(I.e the range is not in sequence with the creation dates)

That is for example in PRD (Production)

Transaction Code QM11:There are the list of notification when the notification numbers(second column) is checked with created on column, the notification numbers are not in sequence with creation date

Example:2XXXXX57 is created as on 05/05/2011,while the notification 2XXXXXX60 is created as on 18/04/2011.So the number range is not in sequence as with creation dateAs checked in the PRD system,

we have irregular notification numbers created with different creation dates

So following the checks made the possible reasons

recent Server changes(Production),checked for any recent client copy or the updates

found that we have recently moved transports as in May 2011,there are no TR related to QM doc ranges

Also when checked the Dumps in the PRD ,found dumps SAPSQL_ARRAY_INSERT_DUPREC,so we are currently workiing on this dump issue,as it may linked with document number range issue of quality notifications

Any other checks ,if missing please share your valuable inputs so as to recitfy the sameAlso there is a related note which is being refered

[former_member207800 · Accepted solution]

I think you are asking the buffer of number range of quality notification.

Check SAP note 62077 - Info: Internal number assignment is not continuous

https://websmp130.sap-ag.de/sap(bD1rbyZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=62077

(SAP support portal account is needed)

QMEL_NR is the notification number range.

Regards

Luke

[srinivas_s7 · Accepted solution]

Dear Luke,

Thanks for the reply

As described in my previous post,the issue is not with the buffering(Missing notification numbers)

Actually the problem is with the sequence of the notifcation numbers being created as with reference to creation date

That is

Say

04/01/2011-Notification number is 1XXXX45

04/02/2011-Notification number is 1XXXX46

04/03/2011-Notification number is 1XXXX47

04/05/2011-Notification number is 1XXXX10

as with the above example ,we can say from 01 Apr to 03 Apr the sequence is from 1XXXX45 to 1XXXX47,but on 05 Apr the sequence is broken the notification number returned to 1XXXX10,which should have been 1XXXX48.

note :1XXXX10 before 04/05/2011 there was no notification created by this number.Moslty the number was buffered ,and was missed earlier,now those number are coming back in the existing sequence ,thus making it as irregular sequence

Hope the hope is clear to you

thanks for your help

RK

[former_member42743 · Accepted solution]

Buffeting of numbers is by server as well. If you have multiple servers, a segment of numbers is assigned to each server separately. So server A might have numbers 1-10, server B, 11-20, server C, 21-30. Users can be assigned to servers in a number of ways. Some user groups maybe assigned to a specific server, ( not unusual for FI folks). In other cases, users are simply assigned to the least used server when they log in. Usually most systems have a mix of dedicated servers and general use servers.

If most of the folks creating notifications are usually assigned to the same one or two servers, then your notifications will remain in a reasonable order. But let's say someone n FI decides to create a notification from the FI server. That server may have a really out of date set of numbers since it would be rare for an FI person to create a notification. It might still have numbers in it's buffer down at say 5-10 while the other servers have run through their numbers and got new sets of number ranges. So the other two servers might now be assigned numbers 45-50 and 51-55. In addtion if servers get rebooted they get new number ranges and the old unsed ones in their buffer are lost.

I'm not sure this is exactly your issue, but it is another example that you can't have any expectation of sequential numbers in most SAP objects as this process is used across most of SAP objects that use number ranges.

FF

[srinivas_s7 · Accepted solution]

Dear FF,

thanks for the response

Still not able to find the core reason of the above issue...

Any further inputs are appreciated

thanks,

Rajan

[former_member207800]

Missing notification number is occurred by buffer.

If you set "No buffer" for notification number, no more missing.

Regards

Luke