Skip to Content
0

MII scheduled jobs hanging until manual restart

Nov 08, 2016 at 07:04 AM

204

avatar image

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

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

Abhijeet Naste Nov 17, 2016 at 10:38 AM
0

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

Regards,

Abhijeet

Share
10 |10000 characters needed characters left characters exceeded
Neha Kshirsagar
Nov 22, 2016 at 03:51 AM
0

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

Share
10 |10000 characters needed characters left characters exceeded
Shanthi Priya Srirambhatla Nov 22, 2016 at 06:22 AM
0

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

Share
10 |10000 characters needed characters left characters exceeded
Neha Kshirsagar
Nov 23, 2016 at 11:19 AM
0

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

Share
10 |10000 characters needed characters left characters exceeded
Shanthi Priya Srirambhatla Nov 28, 2016 at 05:44 AM
0

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

Share
10 |10000 characters needed characters left characters exceeded
Abhijeet Naste Jan 04, 2017 at 01:26 PM
0

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

Share
10 |10000 characters needed characters left characters exceeded