<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE>.hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
<META content="MSHTML 6.00.6000.16809" name=GENERATOR></HEAD>
<BODY class=hmmessage>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff>Hi Tor, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff>It's all about tracking the real business process.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff>You should be able to take your existing workflow templates and
use them as subflows of your super process. That's exactly what I
have done on site and it worked fine... </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff>E.g. Super process C starts by calling the workflow template
for process A as a subflow .... then calls a step to have someone create the
next form, then call process B's workflow template to process the second form.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff>Hope that helps... </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=349115603-24022009><FONT face=Arial
color=#0000ff>Jocelyn</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Tor Magne
Refsland<BR><B>Sent:</B> Monday, 23 February 2009 3:13 AM<BR><B>To:</B> SAP WUG
list<BR><B>Subject:</B> [LIKELY JUNK]RE: [LIKELY JUNK]Starting a HCM process
from within an existing HCMprocess<BR></FONT><BR></DIV>
<DIV></DIV>Hi Jocelyn,<BR><BR>I have some questions regarding possible option
1.<BR><BR>I do understand that creating one big process containing all the forms
and connected to one big wf template is the best solution.<BR><BR>- However, I
am wondering if it is it possible to have 2 processes, Process A and Process B,
connected to the same workflow, where the WF passes fields from a form in
Process A to a form in Process B?<BR><BR>The reason why I ask, is that we have
several different processes today with their own WFs.<BR><BR>In some scenarios
process B should be extending the previous process (process A). It would be
easier to connect both existing processes to a WF, compared to making one big
Process.<BR><BR>- What is the main benefit of having a subworkflow or a local
workflow ? Would it be benefitial to use that in my scenario ?<BR><BR>Thanks in
advance.<BR><BR>Best regards,<BR><BR>Tor<BR>
<HR id=stopSpelling>
Subject: RE: [LIKELY JUNK]Starting a HCM process from within an existing HCM
process<BR>Date: Fri, 20 Feb 2009 06:49:17 +0800<BR>From:
jocelyn.dart@sap.com<BR>To: sap-wug@mit.edu<BR><BR>
<STYLE>.ExternalClass .EC_hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
.ExternalClass BODY.EC_hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>Hi Tor, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>Possible options are:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>1. Create a process Z_PROCESS_C which covers all possible forms of
the business scenario - remember you don't have to use EVERY form in every
process instance - the workflow controls when and who gets to start the new
form.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>In this case you would include a checkbox or similar on your form
to indicate if the extra form is required. This is the best approach as
you can pass fields between forms, and you can represent the super process with
it's own workflow template - even use subflows to share the common parts of the
processing. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>2. Use the Links (i.e. the Link List) to call the web dynpro
application to start the new process - but of course you won't be able to
pass any fields across to the new form. The advantage of this is that the
second form is brought up immediately in a second window but you break the
tracking of the process as there is no relationship between the first and second
forms or their processes. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>3. Use a button on the form to set a hidden field and use the
hidden field in a Generic Service to raise a workflow event to trigger the new
process - the first step of which is to bring the form in the UWL to the person
who pressed the button.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>But be careful of LUW issues - you may need to wait for them to
Send the current form before the event can be triggered. But you break the
tracking of the process as there is no relationship between the first and second
forms or their processes. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>4. Use JavaScripts on the form to build a more sophisticated URL
to call the new process - this is possible but requires some good JavaScript
knowledge. Again the form would be brought up immediately but you break
the tracking process, and would realistically only be able to pass *very*
limited information to the new form. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>Option 1 is the best practice recommended approach - as this gives
you proper tracking across the ENTIRE process - regardless of which forms are
included. Remember form scenarios are independent objects can be
included in multiple HCM processes. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>Hope that helps. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=EC_272163822-19022009><FONT face=Arial
color=#0000ff>Jocelyn</FONT></SPAN></DIV><BR>
<DIV class=EC_OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Tor Magne
Refsland<BR><B>Sent:</B> Thursday, 19 February 2009 8:27 PM<BR><B>To:</B> SAP
WUG list<BR><B>Subject:</B> [LIKELY JUNK]Starting a HCM process from within an
existing HCM process<BR></FONT><BR></DIV>
<DIV></DIV>Dear experts,<BR> <BR>I am using HCM processeses in SAP, where I
have connected several forms to one process, which again is connected to a
workflow. This basically means that I am passing fieldvalues from one form to
another using workflow. <BR> <BR>Case:<BR>------<BR>I am using t-code
HRASR_DT<BR> <BR>Let us say I have process Z_PROCESS_A, which contains form
ZFA1, ZFA2 and ZFA3.<BR>I also have another process called Z_PROCESS_B, which
contains for ZFB1 and ZFB2.<BR> <BR>Related to this subject I have several
questions:<BR> <BR>I want a link/button in form ZFA3, which will start form
ZFB1(in process z_process_b) and pass on the same field values from previous
form.<BR><BR>My question are:<BR>--------------<BR>1. <BR>"Is it possible to
make a button/link in a PDF form, which can take you directly to another form in
another process, and bring the field-values to the new
form?"<BR> <BR>2.<BR>"Is there any way to start a HCM process from within
another HCM process?"<BR> <BR>Restrictions:<BR>------------<BR>Since we are
in the last phase of the project, I am not permitted to do any changes in the
XML configuration for UWL. <BR> <BR> <BR>Thanks in advance.<BR>Best
regards,<BR>Tor<BR><BR><BR>
<HR>
Connect to the next generation of MSN Messenger <A
href="http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline">Get
it now! </A><BR>
<HR>
See all the ways you can stay connected <A
href="http://www.microsoft.com/windows/windowslive/default.aspx" target=_new>to
friends and family</A> </BODY></HTML>