Question About Prefix Numbers

[Bratzler, Loren]

Our Basis team recently converted our Development environment from client 300 to client 100.

Today, for the first time since this change was made, I needed to create a new standard task.  So I defined the task and when I went to save it, I got an error message telling me the prefixes had not been defined in the client I was working in.  So I went out to SWU3 and sure enough, the "Maintain Prefix Numbers" under definition environment had a red X:

[cid:image001.png at 01CF137E.EFC5FA10]

So I launched the activity and I saw that there was an entry for the old 300 client in the table:

[cid:image004.jpg at 01CF1380.2AB6ABF0]

I then edited the entry (deleted and re-created it) for the new client 100:

[cid:image005.png at 01CF137F.4BC2DDB0]


I then went back to my new standard task and when I clicked "save", it assigned a task number successfully.  The problem is, I was expecting to get a task number up in the 400 range based on the last time I had to create a new task.  But the task number that got created was 90000015:

[cid:image006.png at 01CF137F.4BC2DDB0]


I checked our QA and production systems and we do not already have a standard task 90000015 so I don't think this newly generated task number is going to cause a problem.  However, I am concerned about what is going to happen when I create my next task.  Will it assign 90000016?  We do already have a task with that number.  Is the system going to be smart enough to find the next available number that has not already been used?  Or have I created myself a big problem here by changing that prefix entry?

Loren Bratzler
Norfolk Southern Corporation
110 Franklin Road SE
Roanoke, VA  24042-0060

Phone: 540-524-3072
Email: loren.bratzler at nscorp.com<mailto:loren.bratzler at nscorp.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/d62c9671/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11464 bytes
Desc: image001.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/d62c9671/attachment-0003.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 32331 bytes
Desc: image005.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/d62c9671/attachment-0004.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 9346 bytes
Desc: image006.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/d62c9671/attachment-0005.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 34041 bytes
Desc: image004.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/d62c9671/attachment-0001.jpg