IDoc Base - Database Tables used to store IDocs and related information |
| Last edited: 1999-07-18 18:18 +0200 |
All inbound and outbound Docs are stored in EDID4 |
All IDoc, whether sent or received are stored in the table EDID4. The corresponding control file header goes 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 customzing, where rules are defined which tell how the IDocs are to be processed. |
Outbound customizing agrees how data is electronically exchanged |
For outbound processing, the customzing mainly sets the media to
transport the data to its receiver, eg. an operating system file, automated FTP, XML or
EDIFACT transmission via a broker/converter and the internet direct remote function call
The mean of transport depends on the receiving partner, the IDoc type and message type
(context). So you may determine to send the same data as a file to your vendor and via FTP to your remote plant. Also you may decide to exchange purchase data with a vendor via FTP but send payment notes to the same vendor in a file. |
Inbound customzing determines the processing function module |
For inbound processing, the partner profile customizing will mainly determine a function module from the function pool, which is written to process an IDoc of the respective type. |
Reinventing the wheelI |
Of course, as IDocs are nothing than structured file data, you could always process it directly with an ABAP. This is certainly the quick and dirty solution, bypassing all the internal check and processing mechanism. We will not deal here, how to reinvent the wheel, see preamble. |
Customzing TA: WEDI |
To do this customizing setting, check with transaction WEDI and see the points, dealing with ports, partner profiles, and all under IDoc development. |
Links to pictures:
