Customizing in test systems (was: Performance (killer?))

[Nobles, Diane]

If I cannot get them to open up the clients, is there a workaround!!!
 
Diane H. Nobles
Northrop Grumman-Naptheon
SDE PM Team
(757) 380-7250
 
 
-----Original Message-----
From: Pokraka, Michael [mailto:michael.pokraka at kcc.com]
Sent: Wednesday, August 21, 2002 1:53 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Customising in test systems (was: Performance (killer?))
 
 
Hi Diane,
Assuming you have no reasonable test data in your dev client, basis should
open the test client on the dev system.
It can (should) be opened only for client-dependent objects, not for
client-independent objects. Also, it can/should be opened but transports
disallowed. If you have view access to SSC4, you'll see what I mean (if you
have more than view access, be _VERY_ careful).
 
Cheers
Mike
 
-----Original Message-----
From: Nobles, Diane [mailto:nobles_dh at naptheon.com]
Sent: 21 August 2002 18:26
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Performance (killer?)
 
 
Good afternoon Jocelyn, maybe you can help me or anyone else.  I am getting
pretty drastic here.  I am trying to create conditions for my workflow.  I
created them in DVN100, which is our ABAP development client, (the only
client where I can do any workflow definitions, object creations - anything
that needs transporting).  All other clients, including the Development
clients, (DVN010, 020, 030, etc., ) have been closed to creation of anything
that creates a transport.  Unfortunately this also takes away the capability
to create conditions in the client where the config. and data resides
(DVN030).  I have ask BASIS to open up the client, but they are hesitate,
because of the concerns of opening up the other clients in our process,
i.e., TSN and PRD during the transfer/transport of Workflow.  Question!
This is my first time developing in 4.6c environment.  Can I infact develop
a full workflow with conditions and transport the workflow into TSN and PRD
with these clients closed, i.e, is all WF stuff transportable???  Please
help!!!
 
 
Diane H. Nobles
Northrop Grumman-Naptheon
SDE PM Team
(757) 380-7250
 
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Wednesday, August 21, 2002 1:42 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Performance (killer?)
 
 
Just FYI for everyone's benefit ...
 
If you are using SAP Basis 4.6C or above (whether using R/3, EBP, CRM, APO,
whatever)
definitely try and use start conditions for this sort of situation, i.e.
stopping
unnecessary workflows from being created.
 
Only if you really can't formulate a start condition would you bother with a
check function module.  Reasons being:
 
* Start conditions are logical expressions that can be easily viewed,
understood
and if necessary changed by business analysts not just techos, and best of
all by
non-workflow people too - i.e. high visibility, easy access,  reduced
confusion
 
* Start conditions allow you to do amazingly complex logical expressions
complete
with parentheses, logical or/and/not, existence checks on objects etc. in a
lot less
time than it would take you to create an equivalent check function module
 
* Start conditions let you include anything in the event container including
attributes
linked to the event object
 
* Start conditions use a pre-built check function module that SAP looks
after and
is therefore reliable, well-forumlated, robust, covered under your
maintenance agreement, etc.
 
* Start conditions are easy to change because they are configuration not
programming
 
Since start conditions have been made available I haven't had to build my
own check function module
once in a 4.6C or above system.
 
For people in earlier releases, add it to the list of reasons for why you
should upgrade. :-)
 
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: Verlaat, Robert [mailto:Robert.Verlaat at PWN.NL]
Sent: Tuesday, 20 August 2002 10:36 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Performance (killer?)
 
 
Hello,
 
 
 
I'am interested in what the system load would be when I trigger 1 Workflow
about 500 times a day, using a condition as the first step, the workflow
will "really" start about 10 times a day.
 
Would this be a performance killer for the system and should I define a new
Starting event (or use ABAP)? Or isn't it such a big problem because only 1
check has to be made? (check: if field x = 99999 end WF, else continue WF)
 
 
 
Thanks,
 
 
 
Robert
 
 
 
____________________________________________________________________________
_________________
This outbound message from KPN has been checked for all known viruses by KPN
IV-Scan, powered by MessageLabs.
 
Bezoek de Website van PWN: http://www.pwn.nl/
____________________________________________________________________________
_________________
 
----------------------------------------------------------------------------
--
This e-mail is intended for the use of the addressee(s) only and may contain
privileged, confidential, or proprietary information that is exempt from
disclosure under law.  If you have received this message in error, please
inform us promptly by reply e-mail, then delete the e-mail and destroy any
printed copy.   Thank you.
 
 ===========================================================================
==