Logical Errors in the Application 

The errors described in the application refer to the receipt (input) of an IDoc in the SAP system. The IDoc to be transferred is generated in the application when it is output. Errors caused as a result of missing or incorrect customizing settings for this connection are, therefore, reported directly in the SAP system, e.g. when the transfer order is generated or the reference number is released.

The following errors can occur in the application when an IDoc is received in the SAP system.:

Missing or incorrect customizing settings in the SAP system

The IDoc received cannot be processed in the SAP system as certain data in the IDoc are not maintained in the system, e.g. a movement type that is not defined in the SAP system is transferred with a goods movement reported by the external system. The appropriate customizing settings must be made in the case of these errors. Posting of the IDoc in error can then be activated. The IDoc can be posted either from the inbox of an appropriate user or via the report RBDMANIN which is scheduled as a periodic job or which can be started directly via the WM menu Environment ® External systems ® ALE functions ® Periodic processing ® Process ALE outbound IDocs.

Furthermore, it is not possible to process the IDoc if the IDoc data does not correspond to the customizing settings, e.g. the goods movement reported by the external system is to be confirmed directly. Immediate confirmation is, however, not possible with the movement type for this goods movement. The customizing settings must, in this case, first be adapted before posting of the IDoc in error can be activated from the inbox of an appropriate user or via the report RBDMANIN.

Missing or data in error in the IDoc

If the data in the received IDoc is incomplete, the user must decide whether the IDoc in error is to be sent again or whether it is possible or even practical to correct it in the SAP system. Corrections can be made directly to the IDoc or, in the case of certain IDocs, posting can be carried out by means of a dialog and the data thus corrected directly in the SAP transaction. Corrections to the IDoc can, in principle, be made via the IDoc editor. This should, however, only be used in exceptional cases. When postings are made by means of a dialog, corrections to the data are only possible when the inventory is reported (IDoc WMIVID01).

As with the errors in the customizing settings, the IDoc in error can be posted from the inbox of an appropriate user or via the report RBDMANIN.

Errors caused by blocked objects

Problems are often encountered in the SAP system if the user wishes to block individual objects. If an attempt to access an SAP object results in a conflict, processing will be aborted and a message output to indicate the blocked object. This error is treated in the same way as all other errors that occur when an IDoc is being processed. No response is, however, required from the user in order to rectify the error. The problem will be solved automatically when the IDoc is processed again at some later point in time. The background processing function (periodic job) of the report is thus an effective tool for posting the IDocs. Using the parameter ‘Error status’ of this report, posting can be restricted for certain errors by means of an error message identification; in this case only for the error messages of a blocking error.

Important information in the inbox

A work item is created and placed in the inboxes of the appropriate uses for all of the errors described. The work items are also used for a number of important messages which are either sent directly by the external system or generated internally in the application when the IDoc is being processed. These work items are not used to enable processing of the IDoc to be reinitiated from the inbox. They are used to inform the user of a conflict or to pass on an important message from the external system to the SAP system. This message is transferred to the SAP system via the IDoc WMINID01. An internal message is issued, for example, if an attempt is made to confirm a transfer order or storage unit that has already been confirmed. This means that confirmation is no longer possible. This must be reported to the appropriate person as confirmation can usually only be carried out by the external system.

The work item for these messages must not be processed in the same way as the other errors in the inbox but must be completed.