As the experience with IDocs increases, the abbreviated element names will become more familiar and their meaning will unfold – even without the documentation constantly at hand.Īn IDoc can exist in different forms, but usually an IDoc can be found as database entry in an SAP system, where the following tables are being used: EDIDC, EDID4, EDIDS. One will not be able to understand them without a supporting document that explains what these abbreviations mean. Unlike other XML-based standards, Universal Business Language (UBL) for example, IDocs use short and at first sight, incomprehensible element names. In order to be able to read the contents of an IDoc, the first step is to understand its structure. These predefined IDocs may not fully satisfy all requirements, in which case new IDoc types can be created, exactly meeting specific customer requirements. The SAP ERP system delivers a wide range of predefined IDoc base types, which can be used for data exchange. Other examples include dynamic data records such as timesheets, orders or invoices. This data might originate from systems containing master data such as debtor data, creditor data, material master records etc. Using IDocs, a third-party system is able to export and import data from and to an SAP ERP system. As the word intermediate suggests, it is an intermediate format, for the data exchange with an SAP ERP system.
IDoc is the short form of Intermediate Document.
0 kommentar(er)
