Skip to Content

S/4HANA 1709 - ECC6 EHP6 non-unicode 1 step conversion

Hey guru's,

When I was planning upgrade/migration/move projects towards S/4HANA 1610 it was possible to go from a non-unicode directly to S/4 in 1 step which greatly improved the go-live time.

Now I was reading through the 1709 conversion guide and it mentioned that coming from a non-unicode system you had to perform 2 steps for a migration. So first step towards a supported unicode system and second step towards 1709.

So my question is: is this correct? and if it is, are there plans to create the same functionality for 1709 as there were for 1610 in regards to 1 step conversion?

thanks in advance!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Oct 03, 2017 at 10:43 AM

    You are confusing two topics:

    One-step migration (unicode conversion, upgrade and database migration) is available for migration to HANA database (and not S/4)

    For conversion to S/4HANA it was always required to perform the Unicode conversion as a prerequisite. This is because the target NetWeaver release for S/4 system is 7.5 which is only available in Unicode.

    (source: https://news.sap.com/from-sap-erp-6-0-to-sap-s4hana-in-four-steps/)

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 05, 2017 at 08:57 AM

    Hi Jonathan,

    regarding the second question you raised:

    There are no plans to change the current process that Unicode is a prerequisite for the S/4HANA conversion. By the way the same is valid if customers want to go for SAP ERP 6.0 EhP8.

    Best regards,

    Nils Buerckel

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 16 at 12:05 PM

    Hi Jonathan,
    in case you want to combine the two steps (Unicode conversion and S/4HANA conversion) into one technical downtime you could take advantage of the Minimized Downtime Service provided by SAP Consulting. See SAP note 693168 for details.

    Kind regards,
    Ronald

    Add comment
    10|10000 characters needed characters exceeded