SystemCopy EBP 3.0!

Dart, Jocelyn jocelyn.dart at sap.com
Tue Oct 22 05:39:32 EDT 2002


Hi Oliver,=20
Yes as Phil tells you your best bet now is probably to swap to a new
and completely separate number range in TST and use that from now on
to avoid any overlap with current numbers.  It really doesn't matter=20
what range you use so long as it is free from existing workflows=20
and of course obeys the namespace rules, i.e. starts with a 9.
Jocelyn
 
-----Original Message-----
From: Soady, Phil=20
Sent: Tuesday, 22 October 2002 2:44 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: SystemCopy EBP 3.0!
 
 
Dear Oliver,
with a 3 tier environment you can not test the transport process.
One of the main reasons of DEV TST PRD is to test that very fact.
 
So while having a TST and PRD is better than PRD only,
the only thing you are preventing is direct "OPEN HEART SURGERY".
You still have the "take this pill and lets hope there are no side =
effects" issue.
 
I am curious to know what industries survive an audit of such system =
practices. ?
It Must be ok in non business critical circumstances ?
Certainly not possible in many industries in business critical system =
environments.
Eg FDA bound companies would  expect issues with such a config.
 
The prefix numbers are used when creating TS and WS , Roles etc
 
So as long as the number range in TST(DEV) is currently higher than the =
all
objects in PRD, no drama expected. Otherwise you could overwrite an =
object.
Changing the Prefix in TST(DEV) is a way of starting again with a clean =
sheet.
 
Good Luck
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Queck, Oliver [mailto:Oliver.Queck at hp.com]=20
Sent: Monday, 21 October 2002 5:29 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: Re: SystemCopy EBP 3.0!
 
 
Dear Jocelyn,
 
thank you very much for your help again. Our customer has only one =
Testsystem and one Productionsystem. So I have to develop in the =
Testsystem. Before we went live in July 2002 I created the Workflows in =
both Systems (without transporting them from Test to Production)! But =
now we are live and I want to use the Transporting from SAP. How can I =
make shure, that this will work? Are the prefix-numbers important? And =
do I have to have different in the Test- and Productionsystem? In the =
moment both have 950 as the prefix-number.
 
Kind regards,
 
Oliver Queck.
 
-----Urspr=FCngliche Nachricht-----
Von: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Gesendet: Montag, 21. Oktober 2002 01:55
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: SystemCopy EBP 3.0!
 
 
Hi Oliver,
The only system that should have workflow prefix numbers is your =
DEVELOPMENT system where you develop your workflows. You don't need to =
configure prefix numbers at all for Test and Production systems. SWU3 =
clarifies that prefix numbers are only required in the workflow =
development environment. Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Queck, Oliver [mailto:Oliver.Queck at hp.com]
Sent: Friday, 18 October 2002 12:15 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: SystemCopy EBP 3.0!
 
 
Dear Workflowers,
 
we have made a SystemCopy of our EBP 3.0 System to get actual data =
again. My question is now, what I should do with the Prefix-Numbers of =
my own develped Workflows? Before teh SystemCopy the Prefix-Numbers =
where 910 in the Testsystem and 950 in the Productiv-System. Should I =
change it back to 910 in our new Testsystem and where could this be =
done? And does this effect the transport of my Workflows?
 
Kind regards,
 
Oliver Queck.
 


More information about the SAP-WUG mailing list