How to solve SAP data errors
This article focuses on "how to solve SAP data errors". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to solve SAP data errors.
For the inter-company procurement business, many projects enable STO, and when the shipper's company Billing accounts, the SAP system automatically triggers the buyer's Invocie through IDoc. This is a common practice for inter-company procurement business scenarios in SAP project practice. The A project in which the author works is no exception.
The IDoc of the SAP standard is supported for this scenario.
Generally speaking, the Message Type of IDoc is INVOIC01, and Message Type is INVOIC.
The following picture shows: IDoc 0000000000210045
In the morning, I received a report from the customer that a certain STO document was successfully created by Billing and output by Billing, but no Invoice document was found.
The author checked the output of Billing, found IDoc, and looked at its data and status.
The system indicates that there is a problem with the data fragment E1EDK04 Z8 in IDoc.
The Z8 here comes from the output tax code in the output tax (MWST) price data maintained in VK11.
The configuration of the OBCD transaction code does not have the output tax code Z8 related configuration, which is the root cause.
The solution is to maintain the configuration related to output tax code Z8 into the system.
After the OBCD is maintained, output the billing again, and the triggered IDoc is successfully posted, as shown below:
At this point, I believe you have a deeper understanding of "how to solve SAP data errors". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!
