We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE: [sap-abap] Workflow Didn't Get Triggered

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from MASchumacher on Nov 14 at 8:14 AM
Is it a true workflow or the Vistex status changes? For a SAP wf usually there is a linkage defined via SWETYPV and the application issues this event to start the associated wf. Transaction SWELS can be used to turn on/off the event trace so you can see when an event is issued and if a receiver (wf) was started. Tcode SWEL is used to display the traces after it has been activated. Only activate trace on non-production systems. Your business object (BO) for the events is "/IRM/GCR". Workflows can be started directly with code bypassing the events but that is not the typical way.

We are currently upgrading Vistex and the functional guys told me some about what they are calling workflow but it sounded more like status management to progress the claim. Sorry I can't help with that if that's what you are using.

Margaret Schumacher

---------------Original Message---------------
From: urvashisharma1
Sent: Thursday, November 14, 2013 4:20 AM
Subject: Workflow Didn't Get Triggered

I am creating a new Claim from claim workbench, t-code /irm/gcrm, it gets generated, but the attached workflow didn't get triggered? Can someone please explain to me the process, how to proceed to find the root cause

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2013 Ziff Davis, Inc. and message author.
Ziff Davis, Inc. 28 E 28th Street New York, NY 10016
MASchumacher  

achievements
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Have a technical question? Need to find IT solutions? Ask your peers in the Toolbox for IT community.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language