Hi Bjørn,

You cannot change the open date without the ETA date changing.  This is part of the normal business object logic which the imports process call.

The ETA is driven (normally) by the contract and always uses the open date as the start point.  If you change the open date, the ETA is changed accordingly.

Hi Phil

That is understandable. But we can enter a revised ETA, and these are what I try to update by said import: 

Hi Bjørn,

Your question was how to change the open date without changing the ETA dates, not how to import ETA dates.

In any case, still the point is if you change the open date without supplying new ETA dates in the import, the ETA dates are recalculated according to the SLA of the application setup workflow (service)] or contract.

However, if you set up something like:

This allowed the date from the ETA_DT column in my import to update the ARRIVAL ETA.  I have not gone through to see what the other ETA dates are represented by.

My import contained Open_DT of 17-12-2024 and ETA_DT of 24-12-2024, the results were:

Hi Bjørn,

Ok, I worked out the following for the different dates in the SLA/Notes:

Result:

Hi Phil

I apologize for being a bit unclear in my initial description. But you completely understand what I want to do. And I confirm that the import you use do what we set out to do. Thank you!

This:

Produces this:

And of course: if I leave the ETA dates blank, the contract SLA will update these dates. So all good!