ALE Inbound Error Handling

[Former Member]

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

[Former Member]

You need to check if workflow customization (Xn SWU3 )is complete. Further, check Xn We40 to seeif error processing codes are assigned to WF Task.

If this is done then these tasks will be started in case of any error with your IDoc and a message will be sent to your SAP Inbox.

Thanks,

Ram

[Former Member]

Hi Ram

Thank you very much...for your immediate reply..I have gone through the transactions which you listed....

Verifying Workflow customization is fine.

And other transaction has given me these details

EDIC 2 TS74508411 Outbound, incomplete conversion

EDII 2 TS00008068 Inbound, error message with IDoc

EDIL 2 TS70008373 Error message w/o IDoc (status report)

EDIM 2 TS30000020 Error Message Without IDoc

EDIN 2 TS70008037 Display MC document (outbound w/o IDoc)

EDIO 2 TS00007989 Outbound, error handling with IDoc

EDIP 2 TS60001307 Outbound, error message with IDoc packet

EDIS 3 EDI_STAPRC

EDIX 2 TS00008070 Outbound, syntax error in IDoc

EDIY 2 TS00008074 Inbound, syntax error in IDoc

The above codes are enough to complete the process?

Do i need to assign tasks to permitted agents and work items?

Please explain the entire process in detail if possible?

If user is notified by an email if error comes? then can he able to correct the idoc and reprocess it? What i mean can he able to execute the workitem which takes user to idoc list or?

Thanks in advance

Suresh

[Former Member]

Hi Ram

Did i give right information?

Could anybody please throw light on this topic..Need to provide the solution in error handling...

Regards

Suresh

[Former Member]

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.

[Former Member]

Hi Ram

Thanks a lot for detailed reply.

I will start configuring as specified below...

Once again thanks for your time.

Regards

Suresh

[Former Member]

Hi

I have tried by giving user name in post processing agent in partner profiles as well as idoc administrator and verified workflow customization.

I have set up ALE for sending vendor master data. I have not maintained ALE settings in proper way to get outbound error. I got 29 ALE service error. BUT i didn't get any notification. I wanted to get an mail in inbox for the outbound error.

Could any body help me to get the solution.

Regards

Suresh

[Former Member]

You need to find the problem now.

In Workflow -->Development --> Utilities >Events>Event Trace --> Event Q Browser

You can also make event trace on.

Check the IDOC related Event Linkages ( Should be Active )

Then Process the IDOCs to generate errors and then see if events are appearing on EVENT Q BROWSER

event should be something like IDOCAPPL.errorconditionreached.

Within that you can also check if a receiver ( Should be the task ) was found.

You should also check that the tasks that is configured to send messages are classified as general task.

See the agent assignment from above toolbar( Xn PFTC ).

In case an organisation assignemnt is made ( instead of general task ) then you need to include the user-id in that organisation.

If you can just find whether the event is getting triggerd and a receiver is found or not ...rest will be easy ...

Thanks,

Ram