[LIKELY JUNK]RE: [LIKELY JUNK]Starting a HCM process from within an existing HCMprocess

Mon Feb 23 23:06:06 EST 2009

Hi Tor, 

It's all about tracking the real business process.  

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...  

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. 

Hope that helps... 
Regards,
Jocelyn

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Tor Magne Refsland
Sent: Monday, 23 February 2009 3:13 AM
To: SAP WUG list
Subject: [LIKELY JUNK]RE: [LIKELY JUNK]Starting a HCM process from
within an existing HCMprocess

Hi Jocelyn,

I have some questions regarding possible option 1.

I do understand that creating one big process containing all the forms
and connected to one big wf template is the best solution.

- 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?

The reason why I ask, is that we have several different processes today
with their own WFs.

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.

- What is the main benefit of having a subworkflow or a local workflow ?
Would it be benefitial to use that in my scenario ?

Thanks in advance.

Best regards,

Tor

________________________________

Subject: RE: [LIKELY JUNK]Starting a HCM process from within an existing
HCM process
Date: Fri, 20 Feb 2009 06:49:17 +0800
From: jocelyn.dart at sap.com
To: sap-wug at mit.edu

Hi Tor, 

Possible options are:

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.
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.  

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. 

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.
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. 

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. 

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. 

Hope that helps. 
Regards,
Jocelyn

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Tor Magne Refsland
Sent: Thursday, 19 February 2009 8:27 PM
To: SAP WUG list
Subject: [LIKELY JUNK]Starting a HCM process from within an existing HCM
process

Dear experts,

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. 

Case:
------
I am using t-code HRASR_DT

Let us say I have process Z_PROCESS_A, which contains form ZFA1, ZFA2
and ZFA3.
I also have another process called Z_PROCESS_B, which contains for ZFB1
and ZFB2.

Related to this subject I have several questions:

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.

My question are:
--------------
1. 
"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?"

2.
"Is there any way to start a HCM process from within another HCM
process?"

Restrictions:
------------
Since we are in the last phase of the project, I am not permitted to do
any changes in the XML configuration for UWL. 

Thanks in advance.
Best regards,
Tor

________________________________

Connect to the next generation of MSN Messenger  Get it now!
<http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&sou
rce=wlmailtagline> 

________________________________

See all the ways you can stay connected to friends and family
<http://www.microsoft.com/windows/windowslive/default.aspx>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090224/49191f29/attachment.htm