Notification created on date ERDAT

[Former Member]

Hello,

When I check table QMEL for ERDAT (Created on), the newer notification shows older dates than the older notification.

e.g.

Notification ...... ERDAT (created on)

200000131 ..... 12.07.2009

200000134 ..... 14.07.2009

200000138 ..... 14.07.2009

200000140 ..... 12.07.2009

200000141 ..... 12.07.2009

We have internal numbering for our notification with early number assignment set in config.

Why such behaviour?

regards

Edited by: hemant adep on Aug 31, 2009 2:47 PM

[Former Member]

Hi,

i think you activated early number allocation Indicator that means the notification to be assigned a number when the create function is first called, and not after saved.

for example, that anybady given the number of a notification to somone reporting the notification on the telephone or somewhere else , without having to save it first. However, it can also mean that not all numbers assigned are present in the database. you can track it by QM 10

i think this may solve your query

Cheers,

[Former Member]

Hi,

I know the functionality of 'Early allocation'.

But why the date 'Created on - ERDAT' is getting affected. Latest notification should have the latest date and not the older date.

regards

[Former Member]

HI,

You mean to say, after saving of current notification system proposes back date ?

[Former Member]

Got the answer.

There were two servers in production. The number range for notification has buffer of 10 numbers. So for 1st server 20001001 to 20001010 are reserved. and for 2nd server 20001011 to 20001020 are reserved. So today if I create notification in server 1, it will have number 20001001 and date say 25.6.2010. Tomorrow I create in server 2, so it will have number 20001011 with date 26.6.2010.

Then if I create notification on 27.6.2010 in server 1, it will have number 20001002.

This looks like this in table QMEL-

QMNUM - - - - ERDAT

20001001 - - 25.6.2010

20001011 - - 26.6.2010

20001002 - - 27.6.2010

User has no control to login in any particular server. The server gets selected as per the auto load bance logic.

This made all confusion.