Question About Prefix Numbers

Tue Jan 21 14:01:32 EST 2014

I finally got back around to working on this again.  I created a new task today by selecting "create task" from the new activity step in the workflow definition.  This time I did get the "901" prefix.  So it does appear that it was some kind of buffering issue.  I think I should be good now going forward to get "901" tasks.

Although I do think there is some credence to what Rick said below.  When the system was still generating "900" prefix numbers, it was skipping over numbers that were already in use.  One would hope that the system would be smart enough to check to see if a newly generated number was already in use before assigning it again!

Loren

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Rick Bakker
Sent: Sunday, January 19, 2014 4:02 PM
To: SAP Workflow Users' Group
Subject: Re: Question About Prefix Numbers

Hello,

I'm afraid I have to disagree. As Loren has already discovered, SAP is smart enough to not re-use existing task/workflow numbers.

regards
Rick Bakker

On Sat, Jan 18, 2014 at 8:56 AM, Keohan, Susan - 1140 - MITLL <keohan at ll.mit.edu<mailto:keohan at ll.mit.edu>> wrote:
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> [mailto: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:
[cid:image001.png at 01CF16B1.492ECCA0]

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

[cid:image002.png at 01CF16B1.492ECCA0]

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:

[cid:image003.png at 01CF16B1.492ECCA0]

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

[cid:image004.png at 01CF16B1.492ECCA0]

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> [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

[cid:image005.gif at 01CF16B1.492ECCA0]"Bratzler, Loren" ---01/17/2014 01:24:47 PM---Sheldon, Thanks for the quick reply.

From: "Bratzler, Loren" <loren.bratzler at nscorp.com<mailto:loren.bratzler at nscorp.com>>
To: "SAP Workflow Users' Group" <sap-wug at mit.edu<mailto: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<mailto: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> [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

[cid:image005.gif at 01CF16B1.492ECCA0]"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" <loren.bratzler at nscorp.com<mailto:loren.bratzler at nscorp.com>>
To: "sap-wug at mit.edu<mailto:sap-wug at mit.edu>" <sap-wug at mit.edu<mailto: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<mailto: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:

[cid:image006.png at 01CF16B1.492ECCA0]

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

[cid:image007.jpg at 01CF16B1.492ECCA0]

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

[cid:image008.png at 01CF16B1.492ECCA0]

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:image009.png at 01CF16B1.492ECCA0]

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<tel:540-524-3072>
Email: loren.bratzler at nscorp.com<mailto:loren.bratzler at nscorp.com>_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto: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/20140121/4f67ff1a/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 32223 bytes
Desc: image001.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0007.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 66694 bytes
Desc: image002.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0008.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 26819 bytes
Desc: image003.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0009.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 38406 bytes
Desc: image004.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0010.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.gif
Type: image/gif
Size: 105 bytes
Desc: image005.gif
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 11464 bytes
Desc: image006.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0011.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 34041 bytes
Desc: image007.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0001.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 32331 bytes
Desc: image008.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0012.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 9346 bytes
Desc: image009.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140121/4f67ff1a/attachment-0013.png