Triggering an event in Update task

Thu Feb 9 03:13:45 EST 2006

Hi Mike,

Will u pls. explain a bit more, regarding how to call  - based on
ZBUSnnnn.ZTRIGGERCRM?

We are planning for event queue in target system i.e. in ISU, in that
case, whether it will be ok to use event triggering from CRM system in
update task and use queue in ISU for distributing load ?

Regards,
Akshay

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Thursday, February 09, 2006 1:03 PM
To: SAP Workflow Users' Group
Subject: RE: Triggering an event in Update task

If a robust solution is of concern, you can raise an event locally
instead. Trigger a WF which calls a task based on ZBUSnnnn.ZTRIGGERCRM
that does the RFC. I've done this often it's more load overall, BUT a WF
error is easier to spot and restart than a failed RFC call tucked away
in an update task. If needed, you can use the event queue to spread the
load over time.

Cheers
Mike

akshay.bhagwat at wipro.com wrote:
>
> Hi Jocelyn,
>
> Thanks a lot for your prompt inputs...
>
> Just one more thing Jocelyn.. Will it increase any load on update task

> or any other implications on update task because of this (calling of
> event and placing commit on ISU system) in update task - as there are
> going to be considerable number of contracts that will be created
> during data migration from legacy to CRM system.
>
> In case of option of pre-condition for workflow step for unlocking of
> contract in CRM it is not possible as, I will have to again place an
> RFC call back to CRM system.
>
> Thanks again...
>
> Regards,
> Akshay
>
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf Of Dart, Jocelyn
> Sent: Thursday, February 09, 2006 11:45 AM
> To: SAP Workflow Users' Group
> Subject: RE: Triggering an event in Update task
>
>
> Hi Akshay,
>
> You would usually call SWE_EVENT_CREATE_IN_UPD_TASK in the update task

> - the purpose is to ensure the workflow event only happens if and when

> the commit happens.  i.e. that the event is not raised if the
> transaction fails or the user cancels.
>
> However it calling SWE_EVENT_CREATE (with your remote system
> destination) in the update task should do for your purpose as well.
>
> You could also use the equivalent method in CL_SWF_EVT_EVENT if you
> are on 6.40 or above.
>
> An alternative might be to use a pre-condition on your workflow step
> to only continue if the contract is unlocked.
>
> Regards,
> Jocelyn Dart
> Senior Consultant
> SAP Australia Pty Ltd.
> Level 1/168 Walker St.
> North Sydney
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com <http://www.sap.com/>
>
> The information contained in or attached to this electronic
> transmission is confidential and may be legally privileged. It is
> intended only for the person or entity to which it is addressed. If
> you are not the intended recipient, you are hereby notified that any
> distribution, copying, review, retransmission, dissemination or other
> use of this electronic transmission or the information contained in it

> is strictly prohibited. If you have received this electronic
> transmission in error, please immediately contact the sender to
> arrange for the return of the original documents.
>
> Electronic transmission cannot be guaranteed to be secure and
> accordingly, the sender does not accept liability for any such data
> corruption, interception, unauthorized amendment, viruses, delays or
> the consequences thereof.
>
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the
> sender is authorized to state them to be the views of SAP AG or any of

> its subsidiaries. SAP AG, its subsidiaries, and their directors,
> officers and employees make no representation nor accept any liability

> for the accuracy or completeness of the views or information contained

> herein. Please be aware that the furnishing of any pricing
> information/ business proposal herein is indicative only, is subject
> to change and shall not be construed as an offer or as constituting a
> binding agreement on the part of SAP AG or any of its subsidiaries to
> enter into any relationship, unless otherwise expressly stated.
>
>
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf Of akshay.bhagwat at wipro.com
> Sent: Thursday, 09 February 2006 4:41 PM
> To: sap-wug at mit.edu
> Subject: Triggering an event in Update task
>
>
> Hi All,
>
> Let me first explain the scenario. We have 2 systems, one is SAP CRM
> and another is SAP-ISU.
> While creating a contract in CRM, We have to trigger the event in ISU
> system and start workflow in ISU system.
> Once the workflow is started in ISU, it has some steps, which in turn
> has to update the status for line items of this contract in CRM system

> ( which we are creating in CRM )
>
> Now here we are facing problem of Contract being locked while workflow

> from ISU tries to update line items of this contract.
> I was thinking of two options of avoiding this locking:
> 1 . Creating an event in update task of CRM, so as to make sure that
> it will be triggered at the latest point of saving the contract.( This

> will require rfc call for Event_create at ISU system's destination ,
> in CRM system's update task.) 2. Put the requested start step in ISU
> workflow with some delay say 1 min. , so that till this time, in CRM,
> contract is saved and not in edit mode.
>
> Pls. suggest which option we can opt for?
>
> 3. Another point clarification needed that , is the purpose of calling

> SWE_EVENT_CREATE in Update task F.M. just to prolong the triggering at

> the latest point in a particular transaction? (In other words, can I
> use it just for prolonging the event triggering?)
>
> Thanks in advance.
>
> Regards,
> Akshay
>
>
> The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of the
> addressee(s) and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately and destroy all copies of this message and any
attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of
viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
>
>
>
>
> The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of the
> addressee(s) and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately and destroy all copies of this message and any
attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of
viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com_______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com