CAUAJM_E_10728 Failed to process an incoming AFM string - NOT_AUTHORIZED

Products

• Workload Automation Agent
• Autosys Workload Automation
• ESP dSeries Workload Automation - Business Agents (dSeries)
• ESP dSeries Workload Automation - Scheduler (dSeries)
• ESP dSeries Workload Automation - System Agent (dSeries)

Issue/Introduction

When running or monitoring SAP jobs (specifically BW process chains) using the Workload Automation Agent for SAP, the AutoSys scheduler logs report the following error:

CAUAJM_E_10728 Failed to process an incoming AFM string: [TIMESTAMP] [JOB_DETAILS] STATE UNKNOWN Status(Unknown) LStatus(RFC_READ_TABLE- JCoException: NOT_AUTHORIZED) Plugin(sap) User(WA_AGENT)

The job may remain in STARTING or RUNNING status in AutoSys, or it may transition to STATE UNKNOWN.

Environment

• Product: Workload Automation AE (AutoSys)
• Component: Workload Automation System Agent / SAP Plugin
• Integration: SAP BW / Process Chains
• Version: 24.x and above (or 12.x with SAP Plugin)

Cause

The SAP plugin uses the standard SAP function module RFC_READ_TABLE to query status tables, such as RSPCPROCESSLOG, for BW process chains. The error occurs because the SAP RFC user account configured in the agent lacks the necessary authorization objects to execute RFC_READ_TABLE or to read the specific target table.

 

Resolution

To resolve this issue, the SAP Basis team must grant the following authorizations to the RFC user account used by the Workload Automation Agent:

1. Authorization Object S_RFC
   Grant EXECUTE activity for the function group SDTX. This function group contains the RFC_READ_TABLE function module.

2. Authorization Object S_TABU_DIS or S_TABU_NAM
   Grant read access to the specific table used for monitoring. For BW Process Chains, this is typically:

• Table Name: RSPCPROCESSLOG
• Table Authorization Group (if using S_TABU_DIS): Ensure the group for RSPCPROCESSLOG is included.

Verification

1. After granting permissions, restart the failed job or wait for the next monitoring cycle.
2. Review the sap_communicator.log located in the agent's log directory. The JCoException: NOT_AUTHORIZED should no longer appear, and the job status should correctly reflect the state in SAP.

Additional Information

If the error persists, enable JCo tracing to identify the exact missing authorization object:

1. Open the agent's agentparm.txt file.
2. Add jco.trace_level=3 and jco.trace_path=/tmp (or a valid path).
3. Restart the agent and reproduce the error.
4. Review the generated .trc files for specific NOT_AUTHORIZED details.

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.