Question About Prefix Numbers

[Sheldon Oxenberg]

Hi Loren,

Yes, you are creating yourself a big problem here by configuring the same
Prefix number 900.
You should always configure a new unused (never before used) Prefix number
when you create a new Development System and/or Client.
You should maintain a list of used Prefix numbers in your SAP Landscape,
and never reuse a Prefix number, even if you remove a System/Client.

For example, you could configure your Prefix number for your new Client as
follows:

Prefix no. = 901
SAP System = ED3
Client = 100


Regards.

SHELDON OXENBERG
Professional, Solution Management
Technical Architect/SAP Business Workflow
CSC




From:	"Bratzler, Loren" <loren.bratzler at nscorp.com>
To:	"sap-wug at mit.edu" <sap-wug at mit.edu>
Date:	01/17/2014 12:35 PM
Subject:	Question About Prefix Numbers
Sent by:	sap-wug-bounces at mit.edu



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:



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



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




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:




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
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/3ddeffdf/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/3ddeffdf/attachment-0004.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 14386967.gif
Type: image/gif
Size: 11464 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/3ddeffdf/attachment-0005.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 14040565.jpg
Type: image/jpeg
Size: 34041 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/3ddeffdf/attachment-0001.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 14059809.gif
Type: image/gif
Size: 32331 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/3ddeffdf/attachment-0006.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 14782974.gif
Type: image/gif
Size: 9346 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/3ddeffdf/attachment-0007.gif