Forward Error Handling
Contents |
Sybase Support Portal SAP PartnerEdge SAP Training & Certification Shop SAP Service Marketplace sap forward error handling feh SAP Store Analytics Content and Collaboration Customer Relationship Mgmt Data
Sap Pi Error Handling
Management Enterprise Management Financial Management Human Capital Management Product Lifecycle Mgmt Supplier Relationship Mgmt Supply Chain Management Technology Platform Additional Information Technology Platform SAP NetWeaver 7.3 Creating and Configuring Service Providers and Service Consumers Creating and Configuring Service Providers and Service Consumers Supported Standards Authorizations Providing a Web Service Working with SOA Manager Working with ABAP Proxies Consuming a Web Service Publishing a Web Service Managing the Web Service Runtime Web Service Logging and Tracing Protocols Querying the Payload Activating Extended XML Handling Accessing the Message ID Idempotent Web Services Implementing Idempotent Web Services Forward Error Handling Point-to-point Communication for Asynchronous Services WS_HEADER Download Print Fullscreen Select language: de - Deutsch en - English Forward Error Handling Use Forward Error Handling (FEH) is a functionality provided by the ABAP runtime. You can use it when implementing service providers. It allows the processing of errors detected on the provider side when performing asynchronous service communication. Asynchronous communication implies that the receiver of a service request can receive a service call and detect errors, processing them after the sending application's session has ended. In contrast to synchronous communication, in asynchronous communication if the receiver returns the errors immediately, neither the sending application session nor the user of that consumer application is readily available to take care of timely error removal. This may be evident if the service is anyway uni-directional, because no “rejection message” is foreseen in
Community team. Close Getting Started Store Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Spaces Browse Pages Labels Space Operations Quick Search Help Online Help Keyboard Shortcuts Feed Builder What’s new About Confluence Attachments (0) Page History Restrictions https://help.sap.com/saphelp_nw73/helpdata/en/cd/798aa3c7754c61b2f2d50ea7b66aac/content.htm Page Information Link to this Page… View in Hierarchy View Source Export to PDF Export to Word Process Integration … Process Orchestration - Process Integration - Exchange Infrastructure Step-by-Step Guides Step-by-Step Guides - Alerts and Monitoring Forward Error Handling (FEH) https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=228196517 Skip to end of metadata Created by Tobias Trapp, last modified by Kenny Scott on Mar 01, 2011 Go to start of metadata Forward Error Handling means that the user of an Enterprise Service can “fire” a message and then go on. This concept is equivalent with the concept of “loose coupling” explained in the SAP Guidelines for Best Built Applications: “The receiving system must not send an error to the calling system if that error could be handled closer to the receiving system“. It is explained in detail in Error and Conflict Handler . forward_error_handling xi_stepbystep_alerts_monitoring Overview Content Tools Add-ons Pages Labels Space Operations Follow SCN Contact Us SAP Help Portal Privacy Terms of Use Legal Disclosure Copyright
and Conflict Handler (ECH). Asynchronous communication implies that the service consumer cannot react immediately to error messages returned by the provider. Delegating error removal back to the consumer is often inefficient or inappropriate. http://help.sap-ag.de/erp_hcm_ias_2013_01/helpdata/de/62/1100bafd8443b0b6927adf3f6d72fa/content.htm?fullscreen=true If the service is uni-directional (inbound notification and information services), no response message is foreseen in the consumer-provider interaction. If the service is bi-directional (request-confirmation or query-response pattern) it often makes sense for the provider to resolve errors and conflicts on the provider side, without returning an error message to the consumer. Examples : The error is temporary and would disappear automatically if the message were to error handling be processed again at a later point in time. For example, the object to be changed is temporarily locked by another user, or another message needs to be processed first. If a product is not available, the service provider might want to respond with an alternative offer in order to retain the customer. Using the standard messaging channel to communicate errors back to the sender and ask for forward error handling clarification would take too long – it would be more helpful to use the phone or another synchronous medium. The ECH Framework is available in the SAP back-end system. Errors that are handed over to the ECH Framework typically occur during data conversion or business logic processing. ECH enables administrators or even business users on the provider side to follow up on error messages. In SAP Business Suite 7, you can usetransaction ECH_MONI_SEL to search for and access error cases. You can also access this transaction from the SAP Easy Access menu by choosing Cross-Application Components --> Error and Conflict Handler . The resolution process depends on the type of error. An error may be resolved automatically, resolved manually, or rejected and delegated back to the consumer. Automatic Resolution : The system retries processing or automatically rejects the request . Manual Resolution : An administrator or business user corrects the error (for example, by correcting the request, correcting Customizing settings, or entering transaction data), and restarts processing. If an error cannot be resolved by the provider, the user can call the sender and ask for the request to be corrected. The ECH Framework classifies errors into error categories. Examples include: Conflict, restart not possible Authoriza