The root cause of GetWorkOrdersSteplet : Unparseable date: "..."

[former_member603102]

Hi Experts,

My system:

SAPWorkManager 6.4

SMP: 3.0.14.8

I have gotten the error "Unparseable date" when getting WOs from SAP to Agentry client.

Following the log: I debugged into /SMERP/CL_PM_WORKORDER_DO and the field "GLTRP" returned the correct date and also checked in javacode that converting the data of this field is correct. So I think this issue didn't related to abap or java code.

The current solution: restart server as expert's advice.

https://answers.sap.com/questions/376556/sap-work-manager-64-getworkorderssteplet-unparseab.html

but they don't mention about the root cause of this issue.

Could you advise us for avoiding this issue in the future.

Many Thanks.

Ravi

[former_member353725]

The cause of this problem is in changing the structure of tables AFKO, AUFK or AFIH. For example, some Z fields have been added into include structure.

Class /SMERP/CL_PM_WORKORDER_DO does the select from these tables to prepare the Header structure.

At the same time Work Manager is seemed to be caching the header's structure. So even when the actual structure has changed, Work Manager is still trying to parse the Header looking at old structure.

To fix this you can restart the Work Manager Agentry application. No need of restarting whole SMP server.

Still the question, is there any standard solution coming or not. Till then we'll be facing the issue every time AFKO's structure changes. Happily it's not the often event.

Best regards, Anton

[former_member194451]

Hi Ravi,

Without more information, it is not possible to find way to avoid the issue in the future.

How often is the problem happened? Do you have use case that you could reproduce the issue consistently?

Regards,

Chung Yu

SAP Product Support