Scribd Logo
Upload

Welcome to Scribd!

  • 6 views

    Group5 SAP Conversion

    Uploaded by

    ipinnguyen2003

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Group5 SAP Conversion

    Uploaded by

    ipinnguyen2003
    6 views14 pages

    Original Title

    Group5_SAP_Conversion

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    6 views14 pages

    Group5 SAP Conversion

    Uploaded by

    ipinnguyen2003

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 14

    Group 5

    SAP S/4HANA
    System Conversion

    1
    Group 5

    Agenda
    Introduction
    S/4HANA System Conversion Overview
    Conversion Phases
    Pros and Cons

    2
    S/4HANA Transition Options
    System Conversion (Brown Field)

    Existing SAP ERP customer converts an ECC


    system to SAP S/4HANA Cloud Private Edition
    or (if they wish to keep their ERP landscape
    on-premise) SAP S/4HANA

    Implement (Greenfield)

    New SAP ERP customer implements


    new S/4 HANA system

    Selective Data Trasition (Landscape transformation)

    Existing SAP ERP customer with one or more ECC


    systems transforms fully or selective data into the same
    apply for system conversion

    3
    S/4HANA System Conversion

    System Conversion (Brown field)

    Key Highlight
    Convert an existing SAP ECC 6.0 System entirely into S/4 HANA system
    Migrate without re-implementation
    Entire system along with historical data is migrated

    Reuse existing implementation, customizations, custom objects Minimal business disruption


    Add innovations in future (New Fiori apps, AI/ ML, LoB etc.)
    Review customization and code
    Suitable for On-premise, hosting, private cloud target environments

    4
    S/4HANA Conversion Paths

    Note:
    The figure (at the point where
    the figure was created) contains
    as well SAP S/4HANA releases
    which are planned to be
    available in future.
    This cannot be considered as
    binding information, it displays
    more the logic of the transition
    paths.

    5
    System Conversion - Requirements
    Source system Pre-requisites for single step System not meeting any pre-requisite may
    need a multi-step upgrade and conversion
    Should be ECC 6.0 EhP 0 to 8
    Older version to be upgraded to ECC 6 EhPx

    Only ABAP Stack supported


    Dual stack system (ABAP + Java) should be split
    Should be Unicode

    Unicode Conversion should be performed


    Any DB — Check supported source DB versions

    OS/DB platforms may need to be upgraded or


    Check unsupported OS platforms
    migratedto PAM supported releases

    6
    One step vs Two step Conversion to S/4 HANA
    One step conversion can be done where source ECC system meets all the pre-requisites

    Unicode S/4HANA
    ABAP Stack

    Two step conversion will be required if source ECC system does not meet any of the technical pre-requisites

    R/3 or ECC 6.0

    7
    SAP S/4HANA CONVERSION PHASES

    8
    SAP S/4HANA CONVERSION PHASES
    1. Planning
    • Use the Roadmap Viewer
    • SAP Readiness Check for SAP S/4HANA

    2. System Requirements
    You need to be aware of system requirements, start
    releases, conversion paths, and data volume.

    3. Maintenance Planner
    You need to run the maintenance planner tool
    as a first step in the conversion process. It
    checks your components, add-ons, and
    business functions to ensure compatibility with
    SAP S/4HANA and also creates the stack file
    used for the actual conversion process (done
    by the Software Update Manager tool)
    9
    SAP S/4HANA CONVERSION PHASES
    4. Simplification Item-Check
    These checks identify important steps you need to
    take to make sure that your system can technically
    be converted and that your business processes can
    start running directly after the conversion process
    has been completed

    5. Custom Code Migration


    The custom code migration tool checks your custom
    code against a list of simplifications developed for SAP
    S/4HANA.

    6. Cross-application preparation activities


    In addition to the general preparation steps
    described above, you also need to do some
    cross-application preparations.
    10
    SAP S/4HANA CONVERSION PHASES

    7. Application-specific preparation activities


    In addition to the cross-application preparations, you
    may also need to do some application-specific
    preparatory steps. These steps and their
    documentation are partly provided by the pre-checks
    and the custom code checks.

    11
    SAP S/4HANA CONVERSION PHASES
    1. Software Update Manager (SUM)
    The SUM does the database migration (if
    required), the actual software update, and the data
    conversion.

    2. Cross-application follow-on activities Other manual cross-


    application activities may also be required.

    3. Application-specific follow-on activities


    These steps and their documentation are provided by the pre-
    checks and the custom code checks, which provide the list of
    simplification items relevant for your specific systems.

    12
    System Conversion Pros & Cons
    S/4HANA System Conversion

    Pros Cons
    Technical Pre—requisites are critical
    Quicker transition to 8/4 HANA
    Housekeeping required for risk reduction
    Minimal business disruption
    Custom code & interface adaptation is key
    Retain entire historical data
    Process re-engineering is difficult
    Prepare phased innovations
    Downtime depending on DB size and complexity
    No external data loading or cleansing
    Multiple iterations may be required

    13
    Thank You
    For Listening

    You might also like