Understanding Service Error Management

If you are using service error recovery functionality, you can use the Service Error Recovery program (P0045) to determine whether the data being sent by your business service was delivered successfully. If the data was not delivered, the system stores the data, along with an error message detailing the reason that the data was not delivered, in the Services Error Recovery table (F0045). The system recovers the errors for a service in sequential order, and each error record in the F0045 is identified by a unique key. Each F0045 record includes:

• The method name, such as processProcurement.

• The service XML.

• The transaction type, which can be manual or auto.

• Reprocess information, which the system uses to determine how many times the record has been reprocessed.

  The system uses this information so that the service can be consumed until it succeeds, or until a maximum reprocessing count is reached. When the maximum reprocessing count is reached, the system makes the record inactive.

Because different business transaction information and errors are stored, the transaction key is saved as generic text, in a concatenated format. For example, a procurement transaction key is stored as DOCO|DCTO|KCOO|SFXO. The action code for the transaction is also stored in the F0045. Action codes include:

• 1: Add

• 2: Change

• 3: Delete

The description of the error, user-reserved fields, and audit information is also stored in the F0045 table.

You can review these error messages to determine whether issues with your system or process exist, or whether issues with the receiving system exist. You can also attempt to resend the data until the data is delivered successfully.