Standard inbound processing:

The IDoc is treated like an IDoc which was sent by an external system. The IDoc is first saved in the database, then the corresponding control records are compared with the inbound partner profiles and finally the business process determined using the process code is triggered (see Inbound Processing).

Inbound function module (inbound processing using ALE):

The IDoc is first saved in the database and can then be forwarded directly to the specified function module. The function module can be run in debugging mode. If the function module calls a transaction, it can be processed in the background, foreground or in the foreground from the point at which an error is found. To do so, however, the ABAP command CALL TRANSACTION must use the import parameter INPUT_METHOD, in conjunction with MODE. Otherwise, the transaction is always processed in the background.

Inbound file:

Generate or extend a sequential inbound file: The IDoc is first saved in the database with status “68” (“error, no further processing”) and then in a file. Specify the name explicitly. The system proposes a name determined from the test port of the IDoc administration. If you select Start IDoc inbound processing immediately, the file is processed immediately and then deleted if processing was successful. This mode corresponds exactly to standard IDoc inbound processing. If further processing is not started immediately, the file is kept and can be used for additional test purposes.

You can write the test IDoc more than once in the file and thus also send them for inbound processing more than once (repetition factor).