Software Update Manager starts the finance (FI) uptime data conversion on temporary (TMP) system in all productive clients. In case of conversion issues, Software Update Manager will stop and display a respective error. Errors need to be analyzed and solved on the TMP system in the respective client with user DDIC. DDIC user requires authorization for object FINS_MIG, which typically already assigned. Errors can also be accepted, if the root cause is known and any follow-up issues and activities are clarified. This acceptance status can be transported using transport request and therefore included into the Software Update Manager procedure.
After the error handling, the procedure can be continued from the Software Update Manager user interface. To detect unexpected changes, Software Update Manager tracks table accesses on tables not related to finance conversion during the phase. Typically, the downtime optimized conversion approach is not applied to systems without business data, like development systems, as their downtime is not that relevant. In case downtime-optimized conversion is applied to a system in which there are no conversion activities due to missing data (for example, on a development system), a message is displayed: A4 EFINS_FI_MIG 632 Nothing to do. To start and monitor uptime conversion activities, use transaction FINS_MIG_STATUS.
Note
Accepting FI Uptime Conversion Errors
The acceptance of issues can be put into a transport request. You would typically do this in the first run and provide the transport for later runs. Use SAP Reference IMG activity Transport Accepted Error Messages. This starts report FINS_MASS_DATA_MONITOR_MSG_TRA. This report allows you to select errors on step level, for example step R21. The transport is created at the end of the conversion run.
As mentioned, Software Update Manager tracks table accesses on tables of the TMP instance that are not related to finance conversion and stops on error if an unexpected access happens.
123456789Checks after phase RUN_SMIG_MMIMUT_TRC_EVA were negative!
Last error code set:
Single errors (code <= 8) found in logfile 'PHASE_RUN.ELG'
ERROR:
Batchjob RSUPG_SMIG_ILLACCESS_ST05 failed.
The following errors were detected in the log files:
# /usr/sap/DEV/SUM/abap/log/SMIG_MMIMUT_TRC_EVA.DEV:
...
A2EESMIG 327 Illegal write access on table "E070C"If you cannot find the reason for the table access, you may create an incident.