&1: Dates/times were changed by up to &2 seconds

What causes this issue?

When transaction data was uploaded from the SCM database to liveCache
the start or end dates/times of individual activities from the old
release could not be adopted without modification. The order itself was
created in liveCache. Its structures such as BOMs and plan remain the
same. It may be the case that the date/time for the entire order has
changed as a result of the change to dates/times. This means that the
upgrade has resulted in changes being made to the dates/times of the
order specified above. As a result, the order has different dates/times
in the SCM system than in the connected OLTP system.
It is assumed that the difference in dates/times was caused by
sequence-dependent setup activities.
In the case of a sequence-dependent setup, the activities for a resource
must be ordered in a predecessor-successor sequence. This
predecessor-successor sequence is used to determine the duration of each
setup activity from the setup matrix. The predecessor-successor sequence
is not always unique and can therefore change during the upgrade. As a
result, setup activities get different durations and therefore different
start or end dates/times. These changes to dates/ times can affect
adjacent activities. For more details, see SAP Note 519146 which
contains an explanation of the same problem in conjunction with the
planning version copy.
It is to be expected that the changes to dates/times described above
occur mainly in planned orders and manufacturing orders in the SCM
application Production Planning and Detailed Scheduling (PP/DS).

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

The differences in dates/times cannot be avoided. In particular,
repeating the entire upload will not improve the situation. The
responsible users should check the situation of the dates/times of the
order <ZH>after</> the upload and reschedule it in the SCM system or
retransfer it from the connected OLTP system to the SCM system. (If you
do not retransfer the order, it will have different dates/times in the
SCM system than in the connected OLTP system.)
You can use report RCIFORDT to transfer selected in-house production
orders from the connected SAP R/3 system (see also SAP Note 627630).
The retransfer from the OLTP system that you thereby trigger should then
result in the reconciliation of the dates/times, if the automatic
retransfer is active in the SCM system. This is described in SAP Note
423636. The SCM system is dominant in determining the dates/ times.
This means that the retransfer from the OLTP system does not necessarily
create the order with the old OLTP date/time.
The business consequences of this issue are, in particular, not serious
if:
The difference in dates/times is only a few seconds
The order concerned lies in the future, for example, outside the
planning time fence. In this case it is likely that the order will be
rescheduled in any case when regular planning such as optimization and
detailed planning, and the production planning run, take place.
The order lies in the past. The dates/times for the order are adjusted
to the actual data during the next confirmation.
In the old release, the end time of the order was &V3&. After the
upgrade, the end time of the order is &V4&.
Start or end date/times of individual activities, receipts, or issues
were changed by up to &V2& seconds.
For a detailed analysis you can run program
<DS:REPN./SAPAPO/OM_UPGR_COMPARE_TIME>/sapapo/om_upgr_compare_time.</>

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.