ALE IDOC Error Rmanagement

  • View
    98

  • Download
    9

Embed Size (px)

Text of ALE IDOC Error Rmanagement

Complete Guide to Learn ALE Error Handling Through Workflow and Implementation

Applies to:ECC 6.0.

SummaryThrough this document the reader will be able to get a detailed idea about the working of the Workflow whenever an error occurred in the ALE Idoc. The idoc at the receiving system will be validated and correspondingly a workflow will be triggered whenever there is an error occurred in the idoc. Authors: Abhijit Daptary, Sunil Ojha and Siddharth Samal

Company: Capgemini Consulting India Pvt. Ltd. Created on: 03 January 2008

Author BioAbhijit Daptary is presently working in Capgemini Consulting India Pvt. Ltd as a Consultant. He has experiences in ABAP, Workflow and XI. He has worked in different fields of and has handled various scenarios on Workflow and XI. Sunil Ojha is a XI certified workflow consultant. His current engagement is with Capgemini Consulting India Pvt. Ltd.

Siddharth Samal presently working in Capgemini Consulting India Pvt. Ltd as a Consultant. He has experiences in ABAP/Workflow.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 1

Complete Guide to Learn ALE Error Handling Through Workflow and Implementation

Table of ContentsALE Configuration...............................................................................................................................................3 Idoc Administrator ...........................................................................................................................................4 Receiver of Notifications .................................................................................................................................5 Application Processing Errors ............................................................................................................................7 Error Handling Through the Creation of Work Item............................................................................................7 Locating the Error Handling Task ...................................................................................................................8 Activating the Event Linkage...........................................................................................................................9 Assigning the Possible Agents........................................................................................................................9 Triggering IDOC Error Workflow with Custom Business Object.......................................................................10 Error Handling Through Triggering the Event in Process Code .......................................................................10 Flow of the Process in the Inbound System .....................................................................................................14 Diagram Describing the Flow of Process in Inbound System ..........................................................................17 Creation of the Workflow and Corresponding Linkage with Event ...................................................................17 Related Content................................................................................................................................................24 Disclaimer and Liability Notice..........................................................................................................................25

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 2

Complete Guide to Learn ALE Error Handling Through Workflow and Implementation

ALE ConfigurationThis section describes the configuration specific to ALE processing. There are five places in the message transmission process where something can go wrong in the transmission of a message with ALE: 1. Reading the outbound partner profile. 2. Sending the IDoc to the receiving system. 3. Reading the inbound partner profile. This may be a configuration problem or an invalid received IDoc (syntax error or invalid control information) 4. Calling the application function. 5. Posting the record to the receiving database. This is generally a logical error, involving a problem with configuration or with a process problem (such as a customer on credit hold). The first four possible errors are technical errors, involving the distribution of the IDoc without regard to its business contents. An error in posting the IDoc is a logical or functional error, involving a problem with the contents of the IDoc itself, rather than its transfer. We will normally send technical and functional error notifications to different people in an organization. We can configure Workflow error handling in each of these five error situations. This table lists the areas of Workflow configuration for each possible error situation: Error situation Reading the outbound partner profile Sending the IDoc to the receiving system Reading the inbound partner profile Calling the application function Posting the document to the database Workflow configuration needed to handle the error Maintain the IDoc Administrator on the sending system Define a Receiver of Notifications in the outbound partner profile Maintain the IDoc Administrator on the receiving system Define a Receiver of Notifications in the inbound partner profile Configure processing of the corresponding Workflow task

In each case, we can define one or more possible agents to execute the corresponding error-handling task. We can use any of the organizational objects to do this. That is, we can assign all of the members of an organizational unit, a position, or a job to the task, or we can assign a single user or person. The next sections describe these configurations in detail.

Idoc Administrator Receiver of Notification

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 3

Complete Guide to Learn ALE Error Handling Through Workflow and Implementation

Idoc Administrator Transaction: OYEA Men Path: SALE Error Handling IDoc Administration

The IDoc administrator, called the EDI Administrator in earlier versions, is the agent responsible for handling IDoc errors when no partner profile is available. We can set a single organizational unit, position, job, user, or person as the IDoc administrator. On the outbound system, this error generally indicates a misconfigured system, where a required partner profile is missing. On the inbound system, this error probably indicates that the system received an unexpected message type, or a message from an unknown partner. The administrator will typically fix the configuration error, and then submit the IDoc for reprocessing.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 4

Complete Guide to Learn ALE Error Handling Through Workflow and Implementation

The following table describes each of the error-related fields on this screen: Field Recipient type Description The type of organizational object used to identify the possible agents. This can be an organizational unit, a job, a position, a person, or a user. The organizational object (job, position, etc.) whose members we want to notify of an error. The maximum number of IDoc syntax error status records to write to the IDoc. If we select this checkbox, the system will not trigger error handling for errors involving the IDocs status records.

Identification Max number of syntax errors Suppress warnings for status processing

Note: You must maintain the IDoc administrator on each system involved in IDoc transfer. You cannot use CTS to transport the settings.

Receiver of Notifications A Receiver of Notifications is responsible for handling errors in using a partner profile. In this case, the partner profile exists, and the system can read it properly, but there is a problem in sending the IDoc (outbound) or passing it to the application (inbound). There are four places to define a receiver of notifications: The partner profile overview screen Individual partner profile entries for Message Control Individual partner profile entries for Outbound Parameters Individual partner profile entries for Inbound Parameters If an appropriate partner profile exists for the message, but it does not have an entry for the message type in question, then the system will notify the receiver of notifications listed on the overview screen. If the individual message type entry does exist, then the system will notify the receiver of notifications configured for that message type.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 5

Complete Guide to Learn ALE Error Handling Through Workflow and Implementation

To designate a receiver of notifications, use the partner profile maintenance transaction WE20, on the Post processing: permitted agent tab.

The following table describes each of the error-related fields on this screen: Field Typ Description The type of organizational object used to identify the possible agents. This can be an organizational unit, a job, a position, a person, or a user. The language to use for the message sent to the receiver. The organizational object (job, position, etc.) whose members we want to notify of an error.

Lang. ID

The screens for the individual message types (Message Control and In/Outbound Parameters) have the same fields.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 6

Complete Guide to Learn ALE Error Handling Through Workflow and Implementation

Application Processing ErrorsThere are two ways of processing an inbound idoc and corresponding two ways of