SAPAbapProgramming

When R/3 processes an IDoc via the standard inbound or outbound
mechanism, the IDoc is stored in the tables. The control record goes to
table EDIDC and the data goes to table EDID4.

All IDoc, whether sent or received are stored in the table
EDID4. The corresponding control file header go into EDIDC.
There are standard programs who read and write the data
to and from the IDoc base. These programs and transaction
are heavily dependent on the customizing, where rules are
defined which tell how the IDocs are to be processed.

Of course, as IDocs are nothing than structured ASCII data,
you could always process them directly with an ABAP. This is
certainly the quick and dirty solution, bypassing all the
internal check and processing mechanism. To do this customizing setting, check with transaction WEDI and see the points, dealing with ports, partner profiles, and
all under IDoc development.

Trackback URI | Comments RSS