Change an existing workflow

Wed Jan 2 17:03:37 EST 2008

Hello Joe,

Sorry for the confusion. Here is the spiel. The original workflow was
triggered by an event IDOCFINISHED after the sales order or debit memo
was created. The workflow output text for sales orders was correct but
for debit memos the output text was place values instead of the debit
memo number. After implementing 2 OSS notes on recommendation from SAP,
a debit memo business object (BUS2096) had to be introduced into the
workflow to separate data which was sales order (BUS2032) and that which
was a  debit memo (BUS2096) . A condition TRUE/FALSE has been set up in
the workflow to distinguish between the sales order and the debit memo.
The condition was failing because the debit memo was not being read so I
thought that I had to instantiate the business object BUS2096 into the
workflow but I already have a workflow container element which is
importing the debit memo from that business object(BUS2096) so that is
why I am querying if it is really necessary. If it is necessary I will
follow your recommendation of using BO system.

Thanks for replying 

David.

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Joe_Toledo at capgroup.com
Sent: Wednesday, January 02, 2008 4:46 PM
To: SAP Workflow Users' Group
Cc: sap-wug at mit.edu; sap-wug-bounces at mit.edu
Subject: RE: Change an existing workflow

Hi there David, 

I was just going on the assumption that you are trying to introduce a
new business object into you workflow based on the statement "This
condition requires a TRUE/FALSE decision to be made on the basis of new
business object."   The examples below show you how to instantiate a
business object, which means that you will have access to its attributes
from the workflow. 

The method "GenericInstantiate" found in BOR SYSTEM allows you to
instantiate a BOR, but you still have to bind the key and the type to
this method in order for it to generate (instantiate) the BOR, which is
being done in the examples below. 

Do you know if the "new business object" is of the type as the business
object being used within your workflow?   Why do you feel you need to
have a "new business object?"   

Perhaps you could clarify your requirement a bit further.   Sounds like
maybe we're caught up in terminology. 

Regards, 

Joe Toledo <mailto:Joe_Toledo at capgroup.com>  | The Capital Group
Companies
Location: IRV | Extension: 55417 | Outside: 949-975-5417
E-mail: joat at capgroup.com
[ Mailing: 15261 Laguna Canyon Rd.
<http://maps.yahoo.com/py/maps.py?BFCat=&Pyt=Tmap&newFL=Use+Address+Belo
w&addr=15261+Laguna+Canyon+Rd.&csz=92618&Country=us&Get%A0Map=Get+Map>
LC1-2B Irvine, CA 92618 USA ]

<david.s.dittmer at accenture.com> 

Sent by: sap-wug-bounces at mit.edu 

01/02/2008 01:12 PM 

Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To

<sap-wug at mit.edu> 

cc

Subject

RE: Change an existing workflow

Hello Joe, 
Please clarify the statement 'not one of the existing defined BORs in
your WF' . I have used a sub-type of the BOR for the object type as an
import parameter. If I understand your statement correctly this would
mean that the BOR is already known to the WF and there would be no need
to instantiate it, right. 

Thanks for your contribution. 

David 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Joe_Toledo at capgroup.com
Sent: Wednesday, January 02, 2008 3:53 PM
To: SAP Workflow Users' Group
Cc: sap-wug at mit.edu; sap-wug-bounces at mit.edu
Subject: RE: Change an existing workflow 

Hi there David, 

If the BOR you are trying to include in your WF is not one of the
existing defined BORs in your WF, you will need to create logic to
instantiate it.  Below is a sample code of how to "instantiate a
business object" and assign it to a WF container element, which is being
called from a method or from an attribute of an existing BOR available
in the WF. 

Below is an example of how to do either. 

Good luck! 

======================================================== 

begin_method zcreateuserobj changing container. 
DATA: 
      actualprocessor TYPE wfsyst-act_agent, 
      usr01object TYPE swc_object, 
      usr01key LIKE usr01-bname. 

swc_get_element container 'ActualProcessor' actualprocessor. 
usr01key = actualprocessor+2(12). 
swc_create_object usr01object 'USR01' usr01key. 
swc_set_element container 'USR01Object' usr01object. 
end_method. 

========================================================= 

GET_PROPERTY ZESSREQUESTOROBJ CHANGING CONTAINER.         

DATA: l_requser LIKE sy-uname,                             
     lv_object         TYPE swc_object,                   
     lv_objkey         LIKE swotobjid-objkey,             
     lv_objtype        LIKE swotobjid-objtype.           

* 
*  Any logic to define Object Key 
* 

lv_objkey = sy-uname.                                   

swc_create_object lv_object 'USR01' lv_objkey.   

* 
*  May want to include logic is object is non-existant here 
*             

SWC_SET_ELEMENT CONTAINER 'ZESSRequestorObj' lv_object.   
END_PROPERTY.     

Joe Toledo <mailto:Joe_Toledo at capgroup.com>  | The Capital Group
Companies
Location: IRV | Extension: 55417 | Outside: 949-975-5417
E-mail: joat at capgroup.com
[ Mailing: 15261 Laguna Canyon Rd.
<http://maps.yahoo.com/py/maps.py?BFCat=&Pyt=Tmap&newFL=Use+Address+Belo
w&addr=15261+Laguna+Canyon+Rd.&csz=92618&Country=us&Get%A0Map=Get+Map>
LC1-2B Irvine, CA 92618 USA ]

<david.s.dittmer at accenture.com> 

Sent by: sap-wug-bounces at mit.edu 

01/01/2008 04:54 PM 

Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To

<sap-wug at mit.edu> 

cc

Subject

RE: Change an existing workflow

Hello, 
All this has been done but the issue is that a new business object is
not being read by the workflow. >From reading this website it is called
the instantiation of the new business object. Please advise how is the
best way to do this. 

Thank you 

David. 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of ASSY, SOSTHENE
Sent: Monday, December 31, 2007 12:56 PM
To: SAP Workflow Users' Group
Subject: RE: Change an existing workflow 

If you want to change an existing workflow, please follow this procedure
: 

*	In your Dev environment, create a copy of your existing workflow
giving a new name 
*	Do your modification 
*	Activate it and do your test 
*	Desactivate the old one 
*	Transport your change request into production.

Happy New year 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of david.s.dittmer at accenture.com
Sent: Monday, December 31, 2007 5:26 AM
To: sap-wug at mit.edu
Subject: Change an existing workflow 

Hello workflow gurus, 
I am new to workflow and have been asked to change an existing workflow
by adding a condition. This condition requires a TRUE/FALSE decision to
be made on the basis of new business object. Please advise if it is
necessary to instantiate this new business object using business object
SYSTEM or can one just reference the new business object in the workflow
container as an import. I have researched some SAP designed workflows
and they follow the approach of adding a new business object to the
workflow container as an import but I need confirmation. Thanks
__.____._ 

David. 

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited. 

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is
prohibited._______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080102/befe818c/attachment.htm