Question About Prefix Numbers

Fri Jan 17 16:56:59 EST 2014

That might be a buffer thing.   Try running SWU_OBUF (or waiting until Monday) and see if it resolves itself.

Cheers,
Sue

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Bratzler, Loren
Sent: Friday, January 17, 2014 3:40 PM
To: 'SAP Workflow Users' Group'
Subject: RE: Question About Prefix Numbers

Another update:

I found that if I create the new task directly in PFTC, I do get the “901” prefix:

But if I create the task from within the workflow “Activity” step, I am getting the old “900” prefix:

Loren 

From: Bratzler, Loren 
Sent: Friday, January 17, 2014 2:32 PM
To: SAP Workflow Users' Group
Subject: RE: Question About Prefix Numbers

I have created the new prefix as “901” for ED3-100:

But, when I create another new task, I am still getting a task number with “900” as the prefix:

Again, this new task number 90000021, does not yet exist in our system.

Loren 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Sheldon Oxenberg
Sent: Friday, January 17, 2014 1:43 PM
To: SAP Workflow Users' Group
Subject: RE: Question About Prefix Numbers

Loren,

The entry is client specific.
If you are in client 100, then the prefix configuration only needs to have the Client 100 entry:   Prefix no. = 901 / SAP System = ED3 / Client = 100.

If you no longer have a client 300, then you do not need to restore the old prefix configuration "900" that points to ED3-300, but you should 'retire' prefix no. 900, and make a note that prefix no. 900 should never be used again in the prefix configuration in your SAP Landscape.

If you do still have a client 300, then when you are in client 300, the prefix configuration should remain:  Prefix no. = 900 / SAP System = ED3 / Client = 300.

Regards.

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

Inactive hide details for "Bratzler, Loren" ---01/17/2014 01:24:47 PM---Sheldon, Thanks for the quick reply."Bratzler, Loren" ---01/17/2014 01:24:47 PM---Sheldon, Thanks for the quick reply.

From: "Bratzler, Loren" <loren.bratzler at nscorp.com>
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date: 01/17/2014 01:24 PM
Subject: RE: Question About Prefix Numbers
Sent by: sap-wug-bounces at mit.edu

  _____  

Sheldon,

Thanks for the quick reply.

So should I also restore the entry back for the old “900” prefix that points to our old client ED3-300 ?

Loren 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Sheldon Oxenberg
Sent: Friday, January 17, 2014 12:53 PM
To: SAP Workflow Users' Group
Subject: Re: Question About Prefix Numbers

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

Inactive hide details for "Bratzler, Loren" ---01/17/2014 12:35:47 PM---Our Basis team recently converted our Development envir"Bratzler, Loren" ---01/17/2014 12:35:47 PM---Our Basis team recently converted our Development environment from client 300 to client 100. Today,

From: "Bratzler, Loren" < <mailto:loren.bratzler at nscorp.com> loren.bratzler at nscorp.com>
To: " <mailto:sap-wug at mit.edu> sap-wug at mit.edu" < <mailto:sap-wug at mit.edu> sap-wug at mit.edu>
Date: 01/17/2014 12:35 PM
Subject: Question About Prefix Numbers
Sent by:  <mailto:sap-wug-bounces at mit.edu> 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:  <mailto:loren.bratzler at nscorp.com> loren.bratzler at nscorp.com_______________________________________________
SAP-WUG mailing list
 <mailto:SAP-WUG at mit.edu> SAP-WUG at mit.edu
 <http://mailman.mit.edu/mailman/listinfo/sap-wug> http://mailman.mit.edu/mailman/listinfo/sap-wug_______________________________________________
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/da1f7188/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 32223 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0007.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 66694 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0008.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 26819 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0009.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 38406 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0010.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11464 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0011.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 34041 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0001.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 32331 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0012.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 9346 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0013.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5398 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/da1f7188/attachment-0001.bin