Create workflow based on IDOC orders

Create workflow based on IDOC orders

We create Sales Orders from customer EDI data. When this happens, we want to send a message/workitem to the Customer Service Department letting them know an order has been created. Customer service also manually creates sales order at which time we do not want to generate any type notification. I have created a workflow based on BUS2032 - ALECREATED. However, a workitem is generated all the time (manually created and EDI created). How can I create a workflow based on the successful processing of the idoc (IDOCORDERS)?


    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I am unable to tell you exactly what happened but I suggest you investigate the following:

1. Check (if you already have then check again to be sure) that the Workflow Event Linkage is only activated for BUS2032.ALECREATED and BUS2032.CREATED.
2. Activate the WF Event Log and create a Sales Order manually (not using EDI). Which event is being raised? I did this in my system (R/3 release 4.6C) and only event BUS2032.CREATED was raised. The WF Event Log can be switched on/off using transaction SWELS
3. If the event BUS2032.ALECREATED was being raised then you can either:
- Debug the transaction to see why that event is being raised
- Log an OSS with SAP


This was first published in April 2002