Skip to main content
Question

Change in ActualShipDate format in Dispatch advice messages following IFS Cloud 25R2 migration

  • Jul 20, 2026 2:14 PM UTC
  • 2 replies
  • 49 views
Sidekick (Customer)
Forum|alt.badge.img+1

Hello everyone,

We recently migrated to IFS Cloud 25R2 (SU6) and noticed a change in the format of the "ActualShipDate" field in the Dispatch Advice messages (DESADV) we send.

Before migration:
"ActualShipDate": "2026-07-17T16:04:55" (local timestamp, no timezone indicator)

Since the migration to 25R2:
"ActualShipDate": "2026-07-20T10:29:20Z" (UTC timestamp, with "Z" suffix)

 

This is causing issues on the receiving side, which expects the previous format without the UTC indicator.

Has anyone else run into this on Dispatch Advice (DESADV), or on other outbound messages? Is this an intentional/documented change, and if so, is there a way to keep the previous format?

For reference, we have also opened an official support case on this topic: CS0542209.

Thanks in advance for any insight!

 

Soumia

2 replies

Do Gooder (Customer)
  • mfersoz
  • Do Gooder (Customer)
  • Nov 3, 2026 5:12 PM UTC

Hi Soumia,

Have you received any response or found a solution to this issue? We’re experiencing the same problem with our outbound EDI messages after upgrading to 26R1.

Thanks!

 

william.klotz
Superhero (Customer)
Forum|alt.badge.img+21
  • william.klotz
  • Superhero (Customer)
  • Nov 3, 2026 8:43 PM UTC

Hi Soumia,

 

We are in the process of testing 26.1.4 release after upgrading our CFG and UAT environments from 24.2.6 release.  We have noticed a similar issue in the 855 and 856 documents both of which include date and time stamp values.  

 

Have you found a way of suppressing the UTC timestamp?

We are considering having our EDI partner updating the mappings to account for the UTC timestamp but being able to suppress the UTC timestamp would allow our outbound EDI documents to flow without change.

 

Regards,

William

Terms & ConditionsAccessibility statement