From the point when an IDoc has been passed to the SAP system to the point when it is created in the database, errors are logged in the EDFI2 table (file log). A workflow message is also generated to inform the EDI administrator.
•
After an IDoc is created, errors are logged in the IDoc's status record, and problems are reported via workflow.
•
The system performs some basic integrity checks on the IDoc. After the basic checks, the control information is matched against a partner profile. If a partner profile is not found, the IDoc gets a status code of 56 (IDoc with Errors Added), and a workflow message is sent to the EDI administrator.
•
After an IDoc is created, a syntax check is done, the IDoc goes through version change, and
conversion occurs. If an error is found, the IDoc gets a status code of 60 (Error during Syntax Check of IDoc Inbound). A workflow message is sent to the responsible person (as identified in the partner profile).
•
Up to this point, any errors discovered in the system are categorized as ALE/EDI interface errors.
•
The IDoc is then passed to the posting module. If the posting module returns an error, the IDoc gets a status code of 51 (Application Document Not Posted). A workflow message is sent to the responsible person (as identified in the partner profile). There are several reasons for failure of an application document, but in most cases, the problem is with the data.
•
Determining the Success of an Inbound Process
Errors can occur at several points in the inbound process, as noted earlier in the chapter. Your objective is to receive a success message; knowing the measure of success will help you achieve that objective.
When an incoming IDoc is successfully posted, it gets a status code of 53 (Application Document Posted).
The Troubleshooting Guide for Inbound Errors
The best approach for troubleshooting an inbound process is to check the SAP Inbox first. If there is no error message, check the IDoc list for any problems.
The flowcharts in Figures 12.12 through 12.18 will help you with the troubleshooting process. The charts depict the process in logical sequence, tell you which log to monitor, and help you determine the correct point of restart.
You always start at the top of the flowchart in Figure 12.12 and then navigate quickly to the cause of problem, using the decision boxes. Figure 12.12 shows you the steps for locating problems when the inbound process is started, but an IDoc is not present. If an IDoc was created, use Figure 12.13 to branch to the next figure that corresponds to the IDoc status. Figure 12.14 helps you resolve IDocs stuck in status 50. This is mainly due to a configuration error.
Determining the Success of an Inbound Process
Figure 12.12: Troubleshooting inbound errorserrors in triggering the inbound process
Figure 12.13: Troubleshooting inbound errorsbranching to the troubleshooting chart based on IDoc status Determining the Success of an Inbound Process
Figure 12.14: Troubleshooting inbound errorsIDoc status 50
Figure 12.15 describes the troubleshooting process for the most common errors found in inbound IDocsthe application errors. Refer to the next section, "Resolving Application Errors," for details on how to resolve the errors. Figure 12.16 shows you the possible cause of errors in the ALE/EDI layer, which results in an IDoc becoming stuck in status 56. Figure 12.17 helps you debug the cause for syntax errors in an incoming IDoc.
Figure 12.18 helps you locate the reason for the IDoc in status 64. This is usually a configuration error in the partner profile, but if the partner profile configuration is correct, it indicates a severe error or another problem that might have been fixed by SAP. You need to consult OSS, the SAP online service system, in this case.
Note The set of Figures 12.12 through 12.18 should be viewed as one logical figure.
Figure 12.15: Troubleshooting inbound errors IDoc status 51
Determining the Success of an Inbound Process
Figure 12.16: Troubleshooting inbound errorsIDoc status 56
Figure 12.17: Troubleshooting inbound errorsIDoc status 60
Figure 12.18: Troubleshooting inbound errorsIDoc status 64
Determining the Success of an Inbound Process
Resolving Application Errors
Application errors are by far the most common errors in an inbound process. Because data originates outside the system, you might always have data−related problems to resolve. Problems within SAP will eventually cease as you find fixes or make appropriate changes. The following tips can help you resolve application errors.
Execute failed processes in foreground mode. If the posting program in SAP uses call transaction, you can restart the process in foreground mode and step through each screen until you find the problem. To see whether your posting program uses call transaction, execute transaction BD51.
Entries with a value of 1 or 2 use call transaction.
•
Edit failed IDocs. Editing a failed IDoc is a quick fix for data−related problems. For example, if your vendor sends in a wrong material number, you can change the value in the IDoc. You can then restart the process, and the document should post. SAP makes a backup copy of the original IDoc and assigns it a status of 70 (Original of an IDoc that was Edited). You should not use this technique as a permanent fix, however, because doing so addresses only the symptoms, not the cause of the problem.
•