- customizing

Trant, David David.Trant at andrew.com
Thu Oct 27 11:34:06 EDT 2005


I thought the customer namespace had to start with 9.  I recommend this
to avoid conflict with standard delivered workflow definitions.  Here, I
chose to assign a different prefix to each system, development, Q/A, and
production, on the outside chance someone had to go in someday on an
emergency basis and do something directly in a target system.  Also, by
having all prefixes defined in all systems, should your organization
refresh development or test systems periodically from production, you
automatically inherit the correct prefix without having to go back in
and change it.  The one additional step required during a refresh is to
reset the number range index.  This isn't strictly necessary since SAP
is smart enough to bypass numbers that are already in use, but it proved
less confusing for the overall community to preserve continuity.

Attached is a document explaining our strategy in case you're
interested.

Also, you should never use $TMP unless you truly have no intention of
ever transporting your development.  I seem to recall that there are
even some issues with truly local objects not always behaving nicely
without a proper development class assignment in 4.x systems (this turns
into 'package' in newer systems).

Enjoy,
David

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Srinivasan Ramanan
Sent: Tuesday, October 25, 2005 9:01 AM
To: sap-wug at mit.edu
Subject: RE: - customizing

Thank you Keith....

SRamanan


>From: "Gardiner, Keith (CIS)" <Keith.Gardiner at capita.co.uk>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: RE: - customizing
>Date: Tue, 25 Oct 2005 14:51:24 +0100
>
>Sorry having read your query again, I would go for B.
>
>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
>Of Gardiner, Keith (CIS)
>Sent: 25 October 2005 14:48
>To: SAP Workflow Users' Group
>Subject: RE: - customizing
>
>You only need a prefix number where you are developing Workflows, tasks
>and rules. So you shouldn't require this to be set up in QA or Prod. If
>you are developing workflows on different dev clients then each will
>need a unique prefix number.
>
>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
>Of Srinivasan Ramanan
>Sent: 25 October 2005 14:06
>To: SAP-WUG at mit.edu
>Subject: - customizing
>
>Dear WUG,
>I need a recommendation for this :
>DEV system has a prefix number for standard object types as 201 set in
>customizing with $TMP as development class ..
>SAP recoomends that I should different prefix numbers in different
>sysems ...
>in SAP's words
>***************
>Recommendation
>
>Select a unique prefix number in your customer number range for each
>system and each client.
>***************
>What you advise ?...
>
>a. use 301 and 401 for TST and PRD systems with $TMP as development
>calss
>
>                  OR
>b. use 201 in DEV system and attache it to transportable development
>class and transport to other systems ?
>
>I am not really sure what is best case scenario...
>
>thanks for your help in advance
>
>regards
>SRamanan
>
>_________________________________________________________________
>FREE pop-up blocking with the new MSN Toolbar - get it now!
>http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>This email has been scanned for all viruses by the MessageLabs SkyScan
>service.
>
>***********************************************************************
*
>**********
>This email and any files transmitted with it are confidential, and may
>be subject to legal privilege, and are intended solely for the use of
>the individual or entity to whom they are addressed.
>If you have received this email in error or think you may have done so,
>you may not peruse, use, disseminate, distribute or copy this message.
>Please notify the sender immediately and delete the original e-mail
from
>your system.
>
>Computer viruses can be transmitted by e-mail. Recipients should check
>this e-mail for the presence of viruses. The Capita Group and its
>subsidiaries accept no liability for any damage caused by any virus
>transmitted by this e-mail.
>***********************************************************************
*
>***********
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>This email has been scanned for all viruses by the MessageLabs SkyScan
>service.
>
>***********************************************************************
***********
>This email and any files transmitted with it are confidential, and may
be 
>subject to legal privilege, and are intended solely for the use of the 
>individual or entity to whom they are addressed.
>If you have received this email in error or think you may have done so,
you 
>may not peruse, use, disseminate, distribute or copy this message.
Please 
>notify the sender immediately and delete the original e-mail from your 
>system.
>
>Computer viruses can be transmitted by e-mail. Recipients should check
this 
>e-mail for the presence of viruses. The Capita Group and its
subsidiaries 
>accept no liability for any damage caused by any virus transmitted by
this 
>e-mail.
>***********************************************************************
************
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's
FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 01_Workflow Object Number Range Prefix Strategy.doc
Type: application/msword
Size: 36352 bytes
Desc: 01_Workflow Object Number Range Prefix Strategy.doc
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20051027/012417bd/attachment.doc


More information about the SAP-WUG mailing list