2 WF questions

[Krishna M.P.]

Hi Tony,
 
In my opinion, writing a Function module to evaluate all the conditions and
values to get the desired result and implementing it in the  background
step is much better. The advantage is that maintenance personnel can easily
test the function module, method, task and workflow independently.
 
The function module also can be implemented in the Virtual attribute if you
desire not to implement in the background step in your workflow.
In any case if you have more constants to process then better maintain a
table, if you have more dynamic variables then no choice you have to code.
 
Hope this helps.
 
Thanks,
Krishna
Email: Krishna.Pottabatula at exxonmobil.com
 
 
 
 
 
 
 
 
                    "Roehlen, Peter"
                    <PRoehlen at powercor.c      To:     SAP-WUG at MITVMA.MIT.EDU
                    om.au>                    cc:
                    Sent by: SAP              Subject:     Re: 2 WF questions
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
 
                    04/16/02 11:16 PM
                    Please respond to
                    "SAP Workflow Users'
                    Group"
 
 
 
 
 
Hello Anthony,
 
I'll have a stab at answering your questions:
 
1) You should create each container that you need to access in the
sub-workflow and set the 'Importing' attribute to true (and the 'Mandatory'
attribute if appropriate.)  The individual container(s) are passed via the
binding from the workflow to the sub-workflow.
 
2) Your consideration for future supportability is laudable.  Without
seeing
the full details of your specific WF diagram I can't make suggestions for
improving the logic using standard workflow steps.  However, if the logic
is
very complicated, you may wish to consider creating a simple indicator-type
virtual attribute for the relevant business object type.  Your logic can be
programmed using ABAP code and the attribute resolved to True 'X' or False
'
'.  Then your workflow template can test the attribute using a simple
Condition and have Yes / No outcomes.
 
Regards
 
Peter Roehlen
Powercor Australia Ltd
(03) 9683 4807
0409 950 263
 
 
-----Original Message-----
From: Hoodak, Anthony J. [mailto:AHoodak at Gleason.com]
Sent: Wednesday, 17 April 2002 04:06
To: SAP-WUG at MITVMA.MIT.EDU
Subject: 2 WF questions
 
 
Greetings -
 
I have two questions:
 
1. If from a primary WF I call a sub workflow process, what (if anything)
do
I need to do special to ensure that the contents of the WF container are
passed to the sub WF container?
 
2. I have a situation where I need to evaluate several potential values
(that come from a field assigned to a business object) and only allow
certain values to be acted on. Currently, I am using a Loop While object to
accomplish this. The only issue is, I have many values to evaluate and as a
result, the WF diagram is extremely complicated (I am concerned about
anyone
that may have to come after me and perform maintnenance). Is this the only
means that I have at my disposal with which to accomplish this task, or is
there a better approach that I might not be aware of.
 
We are using 4.5B
 
Thanks in advance!
 
Tony
 
 
**********************************************************************
Powercor Australia Ltd. This email and any file attachments are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email in
error please tell us immediately by return email and delete the
document.
**********************************************************************