SAP ABAP Agent not showing Workprocess metric

Products

• DX SaaS

Issue/Introduction

SAP ABAP Agent not showing Workprocess metric, the agent logs is showing:

[ERROR] [IntroscopeAgent.sap-abap] com.sap.conn.jco.JCoRuntimeException: Field 'v' is not a member of record 'TABLES'
[ERROR] [IntroscopeAgent.sap-abap] Failed to create WorkProcessBean
java.lang.NumberFormatException: For input string: ""
    at java.base/java.lang.NumberFormatException.forInputString(Unknown Source)
    at java.base/java.lang.Integer.parseInt(Unknown Source)
    at java.base/java.lang.Integer.parseInt(Unknown Source)
    at com.ca.apm.agent.extension.sap.abap.workprocess.InvWorkProcesses.extractNumber(InvWorkProcesses.java:208)
    at com.ca.apm.agent.extension.sap.abap.workprocess.InvWorkProcesses.createWorkProcessBean(InvWorkProcesses.java:154)
    at com.ca.apm.agent.extension.sap.abap.workprocess.InvWorkProcesses.buildWPOutput(InvWorkProcesses.java:132)
    at com.ca.apm.agent.extension.sap.abap.workprocess.InvWorkProcesses.execute(InvWorkProcesses.java:61)
    at com.ca.apm.agent.extension.sap.abap.workprocess.MwWorkProcesses.fetchAndPublish(MwWorkProcesses.java:81)
    at com.ca.apm.agent.extension.sap.abap.workprocess.MwWorkProcesses.doWork(MwWorkProcesses.java:70)
    at com.ca.apm.agent.extension.sap.abap.publish.SAPMonitorWorker.monitorMetrix(SAPMonitorWorker.java:131)
    at com.ca.apm.agent.extension.sap.abap.publish.SAPMonitorWorker.run(SAPMonitorWorker.java:90)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
    at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.base/java.lang.Thread.run(Unknown Source)

Environment

Agent Release 23.12.1.14 (Build 990014)

Resolution

A fix has been delivered for this behavior, please get in touch with Broadcom Support through https://support.broadcom.com/ and ask for this fix.