MII scheduled jobs hanging until manual restart

[Former Member]

Hi Experts,

We have Schedule jobs maintained in MII landscape and they are in pending state for a long time until we restart it manually. We found an SAP note 1759717 and tried implementing the same. However we are still facing the same issue even after implementing the note.

As per note we have to increase two parameter values in config tool but they did not mentioned how much the values should be increased. The current values for these parameters are 60 and 30.

We have increased these values to 90 and 45, but still we are facing the same issue.

Could you please help us in resolving the issue.

Regards,

Shanthi

[abhinaste]

Hi Shanthi,

To track the timings you can create one custom table. and further you can put logic to insert start time before the BAPI call action and then again the end time after the BAPI call action. By this you can trace the actual time taken by the BAPI to execute.

Also there are some ways to trace the BAPI execution timings from the NetWeaver as well.

Regards,

Abhijeet

[Former Member]

Hi Neha,

Yes, it is processing BAPI to send back the data to ECC.

Could you please provide few alternatives for debugging further more that helps in fixing the issue.

Thanks,

Shanthi

[Former Member]

Hi Shanthi ,

When you say job performs an update back to SAP system ,is it processing BAPI ? Sending back any data to ECC?

As for debugging further more you insert some details like transaction start timestamp and end timestamp into table or write it into text file.

If its processing a query ,then you could check on if the query is taking time .

Thanks,

Neha

[Former Member]

Hi Abhijeet/Neha,

Thanks for your response.

@Abhijeet: There is no connectivity to any third party and there is no complex logic.

@Neha: The purpose of the job is to update the data in SAP System. We have checked the log viewer and are unable to find any logs recorded related to it.

The job that is scheduled is processing successfully and that we are able to see in the history tab. As the job is scheduled for small intervals of time it is showing the status as pending but that is not the problem. The actual problem is that the job is hanging until we restart it manually in the morning.

Could you please provide an alternative for this.

Your response is much appreciated.

Thanks in advance,

Shanthi

[Former Member]

Hi Shanthi,

What type of function is performed in this schedule job?

Did you check the nw logs when the failure happens?

If the data exchange is failed somewhere or if the transaction are going into run time errors then that would cause uncertainty on the transaction side.

Thanks,

Neha

[abhinaste]

Are there any heavy jobs ? like having complex logic and having connectivity to some third parties etc ?

Regards,

Abhijeet