Cancelled Jobs

[Former Member]

Hi,

A job SAP_SRT_REORG_LOG_TRACE is getting cancelled.

It was scheduled by a user with ddic authorizations.

We need to delete the job but its when we try to view the released or planned or active or ready job list in sm37

the SAP_SRT_REORG_LOG_TRACE is not present there.But its getting cancelled always.

Kindly suggest a way to delete this job

Regards,

Muthuvairavan.

[JPReyes · Accepted solution]

SAP_SRT_REORG_LOG_TRACE is created by job SAP_SOAP_RUNTIME_MANAGEMENT and that's why you can't see the released job on SM37.

I don't think you want to remove SAP_SOAP_RUNTIME_MANAGEMENT, so you better check why SAP_SRT_REORG_LOG_TRACE is getting cancelled, I'll start by checking the following,

Assign the role "SAP_BC_WEBSERVICE_ADMIN" to the user under which the batch job "SAP_SRT_REORG_LOG_TRACE" should run.

Read SAP Notes,

Note 1043195 - Configuration of the Web service runtime

Note 1120534 - WS Patch collection (1) for WS tracing and alerting

Regards

Juan

[former_member252257 · Accepted solution]

I change user in job SAP_SOAP_RUNTIME_MANAGEMENT and in SAP_SRT_REORG_LOG_TRACE the user was changes automaticaly.

Maybe if you delete job SAP_SOAP_RUNTIME_MANAGEMENT the SAP_SRT_REORG_LOG_TRACE is removed also.

[saurabh_kumar27]

SAP_SRT_REORG_LOG_TRACE is created by job SAP_SOAP_RUNTIME_MANAGEMENT ( program RSWSMANAGEMENT )

and that's why you can't see the released job on SM37.

Also the job SAP_SRT_REORG_LOG_TRACE is obsolete now ( in 2021 ) and it is only executed if there is some really old data in table SRT_MONILOG_DATA. The job is NOT created / executed by SAP_SOAP_RUNTIME_MANAGEMENT if there is no data in this table. So you have 2 options here .

1. Do a one time data deletion from table SRT_MONILOG_DATA using SE14 and then this job will no longer be created .

2. Find an id ( like a FF or DDIC id ) in your system which has S_WS_LGTRC SPAN / ACTIVITY 65 access and just run the program RSWSMANAGEMENT once - that will delete the old data from table table SRT_MONILOG_DATA and then in future the regular job SAP_SOAP_RUNTIME_MANAGEMENT will not create this job anymore .

[Former Member]

Hi Juan,

Thanks for the solution.

The corresponding user had access in both 000 and 750 client.

In 000 he didnt schedule the SAP_SOAP_RUNTIME_MANAGEMENT.

He had done it in 750 client in which he didnt have the authorization which you specified.

The Issue is now resolved.

Thanks,

Muthuvairavan.