SAP jobs get stuck in a running state.
Article ID: 234418
Updated On:
Products
Issue/Introduction
SAP jobs get stuck in a running state. The jobs complete in SAP but stay running in Autosys. Agent needs to be restarted to correct the issue and sometime it works and sometimes it does not work.
Environment
Release : 12.0
Component : CA Workload Automation Agent for SAP
Cause
No RFC authorization for function module BAPI_XBP_JOB_STATUS_GET was granted to SAP user.
In sap_communicator.log, it's noticed that calling an SAP API to check status fails with "No RFC authorization for function module BAPI_XBP_JOB_STATUS_GET" as shown below:
02/08/2022 00:00:12.345-0500 1 main.Execution:5645466028514519099.CybSAPConnectionParameters.getComDest[:556] - CybSAPConnectionParameters getComDest() return value >>QAAUTOSYS:100:EN:AUTSYSQ100
02/08/2022 00:00:12.345-0500 1 main.Execution:5645466028514519099.CybSAPJobManager.requestProcessedNotify[:1239] - Monitor failed, notifying state unknown...
02/08/2022 00:00:12.345-0500 4 main.Execution:5645466028514519099.CybSAPResponseQueue.b[:240] -
################## REPLY 60788.2722291_1/WAAE_WF0.1/MAIN
* VERB : STATE
* SUBVERB : UNKNOWN
* RESIDUAL : Status(Unknown) LStatus(BAPI_XBP_JOB_STATUS_GET- JCoException: No RFC authorization for function module BAPI_XBP_JOB_STATUS_GET.)
Resolution
Granting SAP user AUTSYSQGR100 appropriate authorization resolved the issue.
Reference:
Set Up SAP Authorizations
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-agent-for-sap/12-0/configuring/set-up-sap-authorizations.html#concept.dita_71b1b4a8f87536bdf243556d9b2947bf4b12ed90_AuthorizationforExtendingXBPFunctionality
Feedback
