- customizing
Trant, David
David.Trant at andrew.com
Thu Oct 27 12:50:14 EDT 2005
You would not actually create copies of the same task in each system (in
your example, TS9010001 turning into T9020001). You would simply
transport the task and it would retain its name in all systems. The
prefix simply shows where it came from and has nothing to do with the
prefix of the system in which it now resides. The only reason to keep
separate prefixes in separate systems is to avoid conflict on that
fateful day on which you must make a change directly in a target system.
Let's say you used prefix 901 for all systems, and in development you
had created several objects: 9010001, 9010002, 9010003, etc. Now your
development system keeps track of where you are in this progression via
an index. Let's say the index is currently sitting at 12, meaning the
next object number to be assigned will be 9010012. Now let's say you
transported some, but not all of your objects to a target system. In
that system, the index sits at 1 and stays there because you're not
developing anything there. Let's say you transport the following:
9010003, 9010004 and 9010005. Now let's say there's an emergency and
your development system is down and your boss approves making a fix
directly in the target system -- a situation to generally be avoided at
all costs, but it could happen. Let's say your fix involves creating a
new object. Since the index sits at 1, that number assigned will be
9010001.
Now it's a few weeks later, and you've finally finished the development
that included objects 9010001 and 9010002. You transport them to your
target system and what happens? Your emergency fix gets wiped out when
object 9010001 gets replaced by the newly transported version! Had your
target system used a different prefix, then the emergency object would
have value, say, 9020001, and transporting 9010001 would have no effect.
I know it's a long-winded explanation, but hopefully it clears things
up. Bottom line: once you set all the prefixes, you can pretty much
forget about them and all objects in all systems will typically be
numbered with whatever prefix you choose for your development system,
901 in this case.
Good luck,
David
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Srinivasan Ramanan
Sent: Thursday, October 27, 2005 11:18 AM
To: sap-wug at mit.edu
Subject: RE: - customizing
Hi David,
Thank you very much for your lucid explation of every points relevant
for
customizing...
I infact used 901 for DEV system prefix...
Perfix System DEv class
901 S2E YEWF
After I transported to TST system which is in a different box,
I got the tasks and workflow templates created with the sames prefix
901...
If I understood correctly , I should have configured perfix for DEV tTST
and
PRD systems and transported it like this
901 S2E
902 S2C
903 F3C
In this case do you mean that task TS9010001 developed in DEV system
would
have been created as task TS9020001 in TST system and as task TS9030001
in
PRD system...
This is very much necessry becasue as you said in case of emergency
direct
maintenance development environment would not have the prefix number in
PRD
or TST system, if config is done only for DEV system ..
AM I correct in my ubderstanding ?
advance thanks for your confirmation on this.
regards
Srinivasan
>From: "Trant, David" <David.Trant at andrew.com>
>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: Thu, 27 Oct 2005 10:34:06 -0500
>
>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]
><< 01_WorkflowObjectNumberRangePrefixStrategy.doc >>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/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]
More information about the SAP-WUG
mailing list