Diagnosis
You execute transaction SPUMG for the preparation of a Unicodeconversion. According to SPUMGs status tables you execute SPUMG for thefirst time in that system.
During startup of SPUMG a check was executed which found data in some ofthe Unicode conversion control tables. In general this must not happenif SPUMG is started for the first time. To avoid possible datacorruption during Unicode conversion you should read through thismessage and decide whether to reset SPUMG or not.
Possible reasons for the existing records are:
You started SPUMG some time ago or long time ago on a low supportpackage level and imported new basis support packages meanwhile. It isnow possible that the new check found old or outdated information in theUnicode conversion control tables.
Data have been transferred from other systems, e.g. by transport requestor by a so called TWIN transport.
In general the preparation for a Unicode conversion needs to be done ineach system individually. Data must not be taken over from othersystems.
In case of a TWIN procedure: the TWIN system has to be on the same SPlevels (basis and application) as the original system in which the dataare taken over. Otherwise inconsistencies might occur in the originalsystem after data have been taken over.
Data have been delivered by support package or have been imported duringsystem installation.

Procedure
After confirmation of this message you will be asked for the deletion ofthe Unicode conversion control tables.

• If you agree, SPUMG will be reset and the preparation for the Unicode
conversion can be started from scratch.

• If you don't agree you can continue with the first steps of the Unicode
conversion preparation. When proceeding with SPUMG you should check indetail that there are not out dated data stored in the Unicodeconversion control tables, e.g. the Export Control Table, the SPUMGLanguage List and the SPUMG work lists.