IDoc is the SAP format in which data pertaining to business transactions gets exchanged. SAP end users and consultants specializing in supplier relationship management (SRM), procurement, and even application development are frequently exposed to IDocs, which can pose all kinds of technical problems for end users.Recently, we’ve received a lot of expert tips that can help you solve IDoc problems.
For example, here’s a way to send advanced vendor details using IDoc that can help you when you need to go beyond sending address details to a trading partner. If that tip isn’t enough, ask our resident SRM expert, Sachin Sethi, follow-up questions.
Some of you have been wondering how to generate an IDoc after you delete a purchase order. There is a way to do this, but it may well be illegal because of regulatory and compliance laws, so proceed with caution. By the way, this tip illustrates why business managers should carefully train SAP end users on the risk management implications of altering business documents.
Another common query is how to find user exits in idoc_input_orders. Resident SAP NetWeaver expert Axel Angeli explains how to do this, and also addresses the issue of user exits in IDoc with a detailed code sample.
Finally, the issue of data error tables is foundational for IDoc users. Axel explains how to populate error tables automatically from IDoc.
Demir Barlas, Site Editor