Steps for ALE/EDI error handling using workflow

Hi
I need to handle errors in outbound IDoc generation using workflow. Can you please let me know the steps to be used for this. Step-by-step answer would be appreciated.
Thanks

Seetha,
I have this already..
IDOCPACKET
Object type                         IDPKWMMBXY
End event                           MASSINPUTFINISHED
IDOC
Object type                         IDOCWMMBXY
Start event                         INPUTERROROCCURRED
End event                           INPUTFINISHED
Application object
Object type                         BUS2017
Start event

Similar Messages

OUTBOUND- ERROR HANDLING USING WORKFLOW

Hi Gurus,
Can any one tell me about workflow & how to do error handling using WORKFLOW in OUTBOUND IDOC.Below are the points , Please check it & send me reply.
1.Value not found for Custom IDoc fields.
2. Partner Profile not maintained correctly.
3. Syntax error in IDoc.
4. IDoc ready for dispatch (ALE Service).
Regards,
Chiranjeevi.

Hi,
FOr most of your requirements, there is already std. SAP IDOC error Single-step tasks.
Have a look at WE46 transaction.
Also, if you go to SWO1 and search with "IDOC*", you will get all the BO's even.
It's pretty straightfwd. Also, in Partner Profiles, WE20, for each of the IDOC type, there is one "Post.Processing AGent", whom if you set up correctly, will be the person receiving this Errored IDOC mails.
Hope this helps
venu

Task ALE/EDI: Error handl cannot be started immediately

When an IDOC is being created in SAP(3.1I) from an external system(Gentran GIS), it is added with errors status 56. The error text states as 'Task ALE/EDI: Error handl cannot be started immediately
'The task ALE/EDI: Error handl (no. TS00008068) cannot be started immediately by user GIS'.
Can anyone advise where the user 'GIS' need to be added to avoid getting that IDOC error

Hi Bhaskara,
This can be caused by several issues:
1. The user GIS has NO authorization to run workflows or to run this specific workflow task (TS00008068).
2. The user GIS has NO authorization to run function module EDI_ROLE_FOR_PROCESSING (or when running this function module it will return data in the ACTOR_TAB, which means that the workflow cannot be started by default users).
3. Within the partnerprofile (transaction WE20) at the specific inbound parameters for the message on the tab "Post processing: permitted agent) an agent has been defined that will not resolve to the user GIS (and therefore this user is NOT allowed to do post processing).
Most likely issue 3 is here at hand. If this is the case, REMOVE the entry for the agent (or consider to setup an organisational unit/work center and make GIS a member).
The error, by the way, is an inbound processing error. It is possible that in the ALE layer something has not been defined properly.
Within the partnerprofile (transaction WE20) at the specific inbound parameters for the message on the tab "Inbound options" and double-click on the entered Process code.
You must now check the entries here.
Example:
If you use an own function module (named in the Identification field) you must set the radio buttons to Processing with ALE service AND Processing by function module. The little button behind the identification field will show some details.
At least the detail fields (on tab IDoc) Object type, Start event and End event must be filled.
Default values for these are: IDOCAPPL (=Object type), INPUTERROROCCURRED (=Start event) and ERRORPROCESSCOMPLETD (=End event).
Of course within ALE you can define different types of process codes (what you like most for your specific handling).
Hope this helps you a bit on your way.
Regards,
Rob.

IDoc error handling using workflows

Hi,
I have a requirement to generate IDocs in the Source system and process them in the target system. The IDoc message type is HRMD_ABA. And I am using standard processes to generate them and post them using PFAL and RBDAPP01 program respectively.
All this is working fine. But now I need to include error handling in the source and the target systems which would send mails to a User's Outlook mailbox whenever there is an error. I mean to say, we need more functionality than just monitor them through WE05 transaction.
Can any one tell me how this can be achieved. I have been looking into the program RSEIDOCA which would send workflows to SAP Inbox, but I need to send it to Outlook Inbox.
And I have heard that there is a workflow process which would help me to do this.
All your answers would be highly appreciated.
Thank you in advance,
Sid.

Hi,
First Step:
You have to maintain the e-mail-address in SU01 for required users.
Second Step:
SCOT Configuration
Third Step:
Depends on your SAP Version do configuration SWNADMIN
Or excuting the report RSWUWFML2 as the background job.
Thanks and Regards,
Prabhakar Dharmala

IDOC Error handling using workflow for Inbound process.

I have a custom idoc which I am processing using a custom inbound function module with the help of a custom process code. I have made the config in BD51/bd67/We42/We57and doing the coding in the inbound function module to handle workflow. But i am still unable to get the workflow item in my inbox. I have set my userid in the partner profile as the agent to receieve the workflow.
Is there any other config that needs to be done vis-a-vis workflow ? like..assignement of some standard task,etc etc ? The message type I am using for the IDoc is zWMMBXY .
Pls advice..thanks

Seetha,
I have this already..
IDOCPACKET
Object type                         IDPKWMMBXY
End event                           MASSINPUTFINISHED
IDOC
Object type                         IDOCWMMBXY
Start event                         INPUTERROROCCURRED
End event                           INPUTFINISHED
Application object
Object type                         BUS2017
Start event

ALE Inbound Error Handling

Hi
Here I have problem in setting up Error handling in outbound/inbound processing of Idocs in ALE....
Can any one please explain how to do it....
My requirement is, if ever idoc goes in to error then the user has to be intimated by mail in SAP Inbox.As per my knowledge it can be done through partner profile...if specify user name in partner profiles/post processing agent place.
My doubt is will it be same in outbound/Inbound?
Do i need to do anything other than specifying usernames in partner profiles?
What is the use of Idoc Administrator?
Please explain how to do that....
Awaiting your valuable answers...
Thanks
Suresh
Message was edited by: Suresh Babu Mannem

I think you also need to specify the "post processing agent" in your Partner profile - Message Type.
Check WE20.
In case you don't want to use organizational assignment then leave the task as it is as general task.
So only the user specified in "post processing agent" will be taken into consideration.
Here are the steps that you need to do for a complete error handling procedure ( but you can avoid organizational assignment if you just need to use User Name as receipient ):
I've taken it from F1 help on error handling:
Error Handling
In this section, you can make the settings for error handling:
Create organizational units and assign standard tasks
Maintain EDI administration ( Idoc administrator section on Xn OYEA or We40 )
Maintain error process code ( Xn OYEA or We40 )
Further you can check it using Verification Processing on OYEA / WE40 .
Errors are processed in the system in which the error occurred.
You can repost IDocs that were not posted (with status 51) using program RBDMANIN.
Requirements
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
Activities
Create organizational units and assign standard tasks
Maintain EDI administration
Maintain error process code
If you used EDI communication in an earlier version, you can check the assignment of error process codes to the standard tasks.
Check names of the employees responsible in the partner profiles.

About ale error handling in workflow?

Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phani

Hi Srikanth,
follw the steps it will helpful u,
Pre-requisites.
It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc.
Description
Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow.
Steps:-
1.     Create custom BOR object with the events, Start and Stop event
2.     Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
3.     Creation of Function Module and attachment with the Process Code
4.     Create the settings for the Inbound Process of the Idoc through the Process Code.
Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1.
Enter a name for the Object type and click CREATE button for creating the custom BOR object.
Enter the details required for creating the BOR objects...
Create the Key fields and events of the BOR object.
For creating the Key fields place the cursor on the Key fields and Click on the Create Button
Create events for triggering the workflow and stopping the workflow.
For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
Create two events.
Enter the event name description etc and proceed further to create it.
Similarly create another event for ending the Workflow in the similar manner like that created earlier.
Now, Generate the BOR object through the generate button
Release the EVENTS and subsequently release the BOR object.
After the creation of BOR object
Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
Execute the transaction SWDD.
Click on the CREATE button for creating the workflow for error handling.
Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
Activate the Workflow and test it whether it is working as per the requirement.
After the successful completion it is required to attach the workflow with the event.
Go to the Header section (Denoted by CAP).
Go to the Start Events TAB.
Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
Enter here the BOR object that has been created and give the name of event created for starting the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Generate the binding and click OK button to save the binding.
Click on Activate / deactivate button for activating the linkage.
After the successful linkage the following sign will appear on the workflow.....
This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered.
After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code.
Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this.
In that function module do the required validation and whenever the validation fails set a standard parameter WORKFLOW_RESULT to 9999 from within the function module, otherwise normally proceed to set the status to 53.
After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
The process code is being created through the transaction WE42
Go to the change mode and click the New Entries button for creating new process code.
Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
The details for the of the Process Code after clicking the identification button will be
Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20.
Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters.
Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type.
Enter the process code for the corresponding message type.
Click SAVE button for saving the changes.
Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
Regards,
Phani.

Step by Step documents for Process Chain Error Handling with Screen Shots

Hi
Is anybody having Step By Step Documents for Process Chain Error Handling with Screen Shots ?. Please forward it to me to my e-mail [email protected] . I will reward points to u immediately.
bye
Aamira Khan

Hi,
You can find lots of topic related to process chain issues in SDN.Please make a search in SDN.
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_library&query=process+chain&adv=true&sdn_author_name=&sdn_updated_on_comparator=ge&sdn_updated_on=&sortby=cm_rnd_rankvalue
Regards.

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

[svn:fx-trunk] 10891: Fix for ASDoc throws error when using getter methods for pseudo-inheritance of static constants

Revision: 10891
Author:   [email protected]
Date:     2009-10-06 09:46:47 -0700 (Tue, 06 Oct 2009)
Log Message:
Fix for ASDoc throws error when using getter methods for pseudo-inheritance of static constants
QE notes: None.
Doc notes: None
Bugs: SDK-22676
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22676
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocUtil.java

Have you tried using com.adobe.air.crypto.EncryptionKeyGenerator instead?

ALE Error Handling with Workflow

Hi All,
I have some issues with using workflows with idocs:
In our process codes , the business object , start event for error handling and success event has been configured.
Now if the workflow_result is 0 then success event is triggered and if workflow_result = 99999 then start event is triggered.
I have two qquestons:
1. How are these events triggered as I did not find any code in the F.M> to triggerethem.
2. What is the purpose of End event.
Apart from this , is there any area where workflows can be used with IDOCS.
Thanks and Regards
Aman

Hi,
In case I am creating a custom F.M. to process idoc data then I can use the F>M> to create the event.
However In case the standard F.M. is being used and workflow_result is set to 9999 in it and I have consigured the start event to it,in that case I will not be able to use thie F.M> to trigger the workflow.
Thanks and Regards
Aman

Steps for ale idoc creation?

Hi,
I want the complete process of ale idoc generation.
my maild id is [email protected]
Thank You.
From:
Mohammed Moid Ahmed

Hi
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Reward points if useful
Regards
Anji

Error handling using BPM

hi all
I would like to do an error handling scenario using BPM in XI. As i haven't done it before, can somebody give me links to good blogs and materials in this regards.
Thanks
Sumayya

HI,
Check the below links
monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
Also see the below BPM related links
check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193124e
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Many other examples can be found under the following link at help.sap.com
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
And some weblogs
https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
/people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
/people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
Also have a look at these seminars,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
Regards
Chilla

IDoc error handling via WorkFlow. What is missing?

Hi All,
My problem is when an error occured I don't receive anything in the Workplace.
I did the following:
When I created the process code I gave an object type(based on IDOCAPPL) for the function module's IDoc part. For the start event I gave the INPUTERROROCCURED event and for the end event the INPUTFINISHED.
I created a standard task where the triggering event is the object type->inputerroroccured and the terminating event is object type->inputfinished and the object method is the object type->inputforeground. I use a standard role with a "Z" function module to determine the agent.
I tested the role with an IDoc number and it worked. It gave me back a position where is my userid is the only id. The concistency check shows me 2 red line: the missing IDoc Packet section (I think it's not needed) and at the Role assignment (I think it's good so I don't understand this).
So, Do you have any idea what is wrong?
Thanks for your help in advance.
Regards,
Gyula

Hi Gyula
Can you tell how you are actually raising that event .?
I assume that you have created a process code and attached it to some function module and therein wherever you are getting error(when you want to trigger workflow) you are raising an event for your object type and its event .
Since i cant check out your code , it guess you can try setting your task as General Task first to just get sure whether the event linkage is active for event or not and your workflow if at all is really getting triggered or not . If these things work fine with out then certainly your role determination function module needs to be checked.
Kind Regards
Shovit

General Error Handling - use of FEH (PPO/ECH)

We are investigating the usage of Forward Error Handling, known with SAP as PPO (Post Processing) and ECH (Error Capture Handler) to be able to re-process errors (automatically or manually) from incoming messages.
I am interested in talking with anyone who has implemented this. General questions are:
- how have you found it to work in real life?
- configuration/set-up straight-forward?
- what scenarios have used it in?
- incorporated into your custom services?
But am interested in any comments.
I am posting this within the PI forum as it ties into the fact we async scenarios inbound to SAP, typically from our PI system, and when those scenarios encounter an error we are looking for a way to have a business/end user - friendly interface for reprocessing the error. Implementing a proxy scenario, and thus having the errors show within sxmb_moni/sxi_monitor, is probably not going to work for us - too technical. I am also aware of an add-on, AIF I believe, but our company is not interested in installing that.
There are 4 blogs out there that I am aware of - 2 from Tobias and 2 from Michal. Very informative. I am finding some config not as ours though. Am really interested in anyone has really implemented and used this in a prod environment.
Regards,
Keith

I think I am exactly at the same position as you in figuring out the usage of FEH in an environment. I just completed a small document (for internal purpose) that I prepared gathering all the information from those blogs, SCN and TechEd. Here are my 2 cents:
>>- how have you found it to work in real life?
We haven't implemented it yet. But we believe it will be quite useful in handling business specific errors. We are trying to find out if it can be merged with the existing BPEM infrastructure to generate BPEM cases.
>>- configuration/set-up straight-forward?
Yes, the blogs should be quite useful to provide this information.
>>- what scenarios have used it in?
Most importantly it will be used for standard service implementation where we consume enterprise services from ES workplace. These services have FEH capability built in (they have FEH method implemented within). The scenarios are of course inbound abap proxy.
>>- incorporated into your custom services?
We are still in design phase. But if you ask me about it, i would say yes you can and I think you should use it for custom ones as well.
Kind regards,
Prateek Raj Srivastava

Steps for ALE/EDI error handling using workflow

Similar Messages

Maybe you are looking for