SAP S4 HANA RFC Spoke 'Look Up Invoices by Date' action errorIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The SAP S4 HANA RFC Spoke errors occur when testing using flows with error message 'Error while parsing Json to JCo. Root Cause: Cannot convert value '09/01/2025' from type java.lang.String to type DATE field LOW in record BAPI_INCINV_ENTRY_DATE_RA' appears when testing the 'Look Up Invoices by Date' action. The mid-server jar files (sapjco3.dll / sapjco3.jar) were initially missing but were manually added. However, the issue persisted even after verifying the jar files were present on the mid server. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Yokohama Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The root cause was a mismatch in date formatting between the ServiceNow instance and the SAP system. The ServiceNow instance was configured to use 'MM/dd/yyyy' via the 'glide.sys.date_format' property, while the SAP system expected dates in a different format. Since the date is passed to SAP in the instance's display format, this mismatch leads to the SAP RFC conversion error.error at the Step 2 - Ping and Query SAP [Script]Error: Error while parsing Json to JCo. Root Cause: Cannot convert the value '10/01/2025' from type java.lang.String to type DATE at field LOW (ad_hoc:Flow Designer; line 13),Detail: Error while parsing Json to JCo. Root Cause: Cannot convert the value '10/01/2025' from type java.lang.String to type DATE at field LOW This mismatch caused errors during RFC communication, as the date values could not be converted properly. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Update the system property 'glide.sys.date_format' in the ServiceNow instance to 'yyyy-MM-dd' to ensure dates are formatted correctly for SAP. This can be done by navigating to the property record: https://<instancename>.service-now.com/nav_to.do?uri=sys_properties.do?sys_id=24de57037f000001002b3574b0ad5187 and saving the record. 2. After updating the date format, perform a test run of the 'Look Up Invoices by Date' action to verify the steps to resolution. If preferred, alternatively update the script in the 'Look Up Invoices by Date' action to explicitly format dates, as tested successfully on the sub-prod instance.