WebSphere Adapter for SAP Software

Detecting errors during outbound processing

To detect errors such as invalid data or invalid state that occur during outbound processing, you set up business-object application-specific data.

Before you begin

Make sure you have determined which errors you want to detect.

About this task

During outbound processing, the adapter can automatically detect errors generated by the SAP Jco interface. To detect other types of errors returned by the RFC interface (for example, to be able to validate the data that is returned) you must define values for application-specific data (metadata) at the business-object level.

To set up the business-level metadata to detect errors, use the following procedure.

How to perform this task

  1. Identify the parameters that define RFC error codes and their possible values.
  2. Add the application-specific information for ErrorParameter, ErrorCode, and ErrorDetail to the business object.
    • ErrorParameter is the XPATH to the property that returns the error codes.
    • ErrorCode contains all possible values (for example, E, ERROR, and NODATA) returned in the property referred to by ErrorParameter.
    • ErrorDetail is the XPATH to the property that contains details about the error.

    If the values defined in the ErrorCode property match the error parameter values after RFC executes the call, an error message with detailed information is generated. The detail is derived from the ErrorDetail property.

    Error handling application-specific information must be manually maintained. You can use the Business Object Designer to add the application-specific information.

Result

Your top-level business object contains properties that enable it to detect RFC errors.

Terms of use |

Last updated: Mon 30 Oct 2006 03:34:56

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)