SAP Connector > Part VI: Data Integration Using IDocs > IDoc mapplets > Outbound mapplet

Outbound mapplet

You can capture changes to the master data or transactional data in the SAP application database in real time.
When data in the application database changes, the SAP system creates IDocs to capture the changes and sends the IDocs to Data Integration. You can use the IDoc Reader connection to read the IDoc message in real time as they are generated by the SAP system.
If the Secure Agent is not running when the SAP system sends outbound IDocs, the Secure Agent does not receive the IDocs. However, the SAP system stores the outbound IDocs in EDI tables, which are a staging area for guaranteed message delivery. You can configure the SAP system to resend the IDocs by configuring the tRFC port used to communicate with the Secure Agent. When you configure the port, you can enable background processes in SAP that try to resend the IDocs to the Secure Agent a set number of times.
To generate the outbound mapplet to read IDoc messages from SAP system, use the IDoc Interpreter when you import the IDoc metadata. Import the outbound mapplet to Data Integration and configure an outbound mapping.

Outbound mapplet ports

An outbound IDoc mapplet contains predefined ports. You cannot edit the ports.
The following table describes the mapplet ports:
Port Name
Basic IDoc Type
Basic IDoc type name.
Basic IDoc type defines the structure of an IDoc. Each basic type describes standard IDoc segments, format of data fields, and size. Basic type contains all the standard fields that are necessary for carrying out a business transaction.
Extended IDoc Type
Extended IDoc type name.
IDoc extension is extension of basic type and contains additional custom IDoc segments and fields that are not available in the standard basic type.
IDoc message data.
Unique message number of the IDoc.

Target object for outbound mapplet error output

You can configure an outbound IDoc mapping to write IDocs that are not valid to a relational or flat file target. To write IDocs that are not valid to a relational or flat file target, connect the IDoc_Interpreter_Error_Output_Group port in the outbound mapplet to a relational or flat file target object. You must also configure the error log type session property in the Schedule page.