In general, there can be 2 reasons that the certain incoming IDOCs are not processed (having the status 51):
- Temporary inability to process the IDOC (e.g. the attempt to register the Time Effort while the Service Order is locked by another user),
- Other type of problem (e.g. invalid master data, invalid configuration, etc.).
To minimize the effort of monitoring the unprocessed IDOCs and minimize the impact of the temporary inability to process the IDOCs it is possible to schedule the periodic job, which makes the attempts to reprocess the IDOCs with the status 51. However, we should notice that:
- This approach makes sense only for the IDOCs having the status 51 because of temporary inability to be processed,
- For performance reasons the set of the IDOCs included in that process should be limited by date (e.g. current date or the IDOCs not older than 1 day).
Thereby launching this job does not mean, that the monitoring of the IDOCs is not needed – still it is.
The unprocessed incoming IDOCs (having the Status 51) can be reprocessed manually using the standard transaction BD87.
There is also a standard program RBDMANI2 performing the reprocessing. This program can be scheduled as the background job. The selection screen variant should be setup for that program. It can look like this:
Notice:
- Turn "Output List" off
- Include only the IDOCs with the Message Type = /PACG/ECM*
- Consider the IDOCs not older that the given amount of days.
As the job is to be run periodically, the "Created on" has to be determined dynamically". When saving the selection screen variant use the following:
(it is crucial to use Greater or Equal operator)
(then chose the expected age of the IDOC to be considered, e.g. created yesterday or later)
It is crucial that after choosing the selection screen variant we see Greater or Equal operator and really dynamic date calculation takes place (not the fixed one):
When setting up the job take care that you do it with the right SAP user (the same as configured in the Message Broker).
The sequence of activities to create such job could look like this:
Launch the transaction SM36.
Choose 
.
Choose Continue:
Provide the Job name:
Choose Continue:
Enter the program name, and the variant. Remember about choosing the right language (the documents in SAP will be created in that language):
Choose Continue:
Accept default proposal, choose Continue:
Choose periodic execution, choose Continue:
Choose expected frequency, if none of them satisfied you, choose "Other Periods":
Choose expected frequency, e.g. every 2 hours:
Accept the final confirmation:
Verify the job just created:
Deleting unneeded Logs
Once the FSM Cloud Connector IDOCs have been successfully processed or sent, the corresponding SLG1 Logs are not needed in the system any longer. It is up to the Administrator whether they will stay on the system or will be deleted with other Logs or will be deleted separately.
The transaction SLG2 can be used to delete the old Logs.
BE EXTREMELLY CAREFUL, NOT TO DELETE OTHER (NON FSM Cloud Connector) LOGS AND NOT TO DELETE THE LOGS WHICH ARE RELATIVELLY NEW (WHICH COULD BE HEPFUL FOR PROBLEMS DIAGNOSIS). BE EXTREMELLY CAREFUL TO PROVIDE THE CORRECT "OBJECT" AND "TO (DATE/TIME)" PARAMETERS. IF YOU MISUSE THIS TRANSACTION YOU CAN DELETE IMPORTANT DATA.
The following selection screen of SLG2 transaction could be used: