Monitoring the Download 

Once data is forwarded to the optimization system, you can monitor how IDocs are created and transferred with the following functions:

You can select all IDocs transferred to the ALE layer according to various criteria and control the data sent.

You can use this function to check whether the transactional RFC actually transferred data to the target system.

With this function module you can monitor the entries to check if there were any problems during the transmission of the IDocs to the logical system. You can check the results in two tables: IDOC_QUEUE and TRFC_QUEUE and determine which of these two tables should be returned. You can define the maximum number of entries per table to avoid receiving very large quantities of data at once. You can also limit the choice of IDocs for a logical system by setting date and time restrictions.

If an IDoc in the IDoc queue has one of the following statuses, the entries are transmitted to the external system. If it has any other status, a transactional RFC is sent. It is not enough to check only the IDoc Queue because although an IDoc may have been created correctly, a problem could have occurred during transmission. Transmission problems are checked in table TRFC Queue

IDoc Queue

Status

Description

Possible reason for error

30

ale_ready_for_dispatching

Report RSEOUT00 for this IDoc has not yet been started
Error/termination when calling up RSEOUT00

29

ale_service_error_out

ALE service error. Check partner agreement

20

edi_triggering_error

 

26

edi_idoc_syntax_error_out

IDoc structure error

02

edi_file_error

Error occurred while writing file. This error occurs only when using a file port

 

TRFC Queue

Status

Description

RECORDED

The LUW was recorded and should be executed

EXECUTED

The LUW was executed. The entry will be deleted

CPICERR

Communication error or ABAP/4 error in LUW

SYSFAIL

Runtime error or error message during execution of LUW

MAILED

CMC sent

READ

CMC transmitted to R/3 successfully

SEND

LUW being sent

For further information regarding the function module, see the function module interface and its online documentation.

For more detailed information, refer to the Implementation Guide.

(Cross-Application Components ® Distribution (ALE) ® Basic Configuration)