Migrating from AFS to S/4HANA Fashion
Migrating from AFS to S/4HANA Fashion
PUBLIC
Speakers 2018
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
Roadmap
Transferring Data Directly to SAP S/4HANA from SAP Source System
Further Development
Closing
Summary
Helpful Documentation and Information
Roadmap
Transferring Data Directly to SAP S/4HANA from SAP Source System
Further Development
Closing
Summary
Helpful Documentation and Information
System platform
A complete technical in-place conversion of an existing SAP
conversion ERP software system in SAP Business Suite to SAP S/4HANA
SAP ERP SAP S/4HANA
(Tool: Software Update Manager)
system
Adoption of new innovations at your speed
New implementation/reimplementation
New Reengineering and process simplification based on latest innovations
SAP S/4HANA Implementing innovative business processes with preconfigured
with data migration
Reengineering
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC SAP Community blog: How to find my path to SAP S/4HANA 8
Transition to SAP S/4HANA
Different approaches to move to SAP S/4HANA
New implementation/reimplementation
New Reengineering and process simplification based on latest innovations
SAP S/4HANA Implementing innovative business processes with preconfigured
with data migration
Reengineering
Cloud
**
Migration Object Modeler
*Available for On-Premise as of 1709 FPS01, planned for Cloud **Available for On-Premise as of 1610 FPS02
Design functionality to easily integrate custom objects and enhancements into the migration project
Integration of newly created objects:
– Custom objects
– SAP standard objects that are not yet in the scope of the SAP S/4HANA Migration Cockpit
Customer-specific enhancements (e.g. add new fields) to SAP standard objects delivered with the
SAP S/4HANA Migration Cockpit
Easily adjust source structure
Use Standard APIs or code your function module
Map structure and fields
Available for SAP S/4HANA On-Premise
Access via transaction LTMOM
Transfer Data Directly from SAP Source System (planned - see section Roadmap)
access source system database directly (ABAP-based SAP source systems only)
transfer data from SAP source system to target SAP S/4HANA system
supports data migration scenarios from other applications, e.g. from SAP Apparel and Footwear (AFS) to S/4
Fashion and Vertical Business
Source System Identify migration objects Enter data in the template Transfer data to SAP
SAP or non-SAP relevant for project file S/4HANA
On-Premise
Roadmap
Transferring Data Directly to SAP S/4HANA from SAP Source System
Further Development
Closing
Summary
Helpful Documentation and Information
Motivation
Amount of records and size of file is limited for XML files
Large tables need to be split by creating several spreadsheets
Filling of XML templates with multiple tabs can lead to inconsistencies
Technology
Secondary database connection must be available
Staging tables: created natively in the schema of SAP HANA database
Separate staging table for each source structure of a migration object
Benefits
Safer – Faster – Easier
Source System Create database connection Staging tables are created Transfer data from staging
SAP or non-SAP to SAP HANA DB automatically tables to SAP S/4HANA
On-Premise
Access migration cockpit Identify migration objects Fill staging tables by using
in SAP S/4HANA relevant for project SAP or external tools
Available for SAP S/4HANA and planned for SAP S/4HANA Cloud
Used to transfer large volumes of data
Staging tables can be filled by SAP tools or external ETL tools (Extract, Transfer, Load)
ODBC
SAP S/4HANA On-Premise
or separate SAP HANA box* SAP S/4HANA On-Premise
Legacy System
Application Tables
Application Data
* Separate SAP HANA database schema is required, can also be on SAP S/4HANA target system
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC ** Prerequisite: established secondary database connection 21
SAP S/4HANA Migration Cockpit - Transfer Data Using Staging Tables
System Setup (Cloud – planned for 1811) Cloud
SAP S/4HANA
SAP HANA DB schema
Migration Cockpit
ODBC SCP
Application Data
► Separate SAP HANA database schema is required
Staging tables will be created natively in the schema of the SAP HANA database depending on the
selected database connection.
For each source structure of a migration object, a separate staging table will be generated.
Staging tables must be filled by customer using extraction tools from SAP or from a third party.
Screen for preview on table structure and records with different statuses (unprocessed, processed, error)
Migration Cockpit driven data operations for staging tables
Delete selected records
Delete all records
Reset status
(to unprocessed)
Start synchronization
(e.g. after changes done
in migration object modeler)
Freeze triggers prevent that during the transfer of data changes can be done on any data in the staging
table
If freeze triggers are set, you will see this message on the Migration Object Screen in the Migration Cockpit:
On the database, you can see three triggers for each staging table:
If you want to insert data in the staging table, when the freeze triggers are set, you will get the following
database error:
Parallelization
It is possible to transfer multiple staging tables in
parallel
Roadmap
Transferring Data Directly to SAP S/4HANA from SAP Source System
Further Development
Closing
Summary
Helpful Documentation and Information
Source System Connect to source system using Migration cockpit accesses the
ABAP-based SAP System RFC connection relevant source system tables based
on the specified migration objects
On-Premise
Access migration cockpit Identify migration objects Transfer data directly from
in SAP S/4HANA relevant for project source system to SAP S/4HANA
SAP S/4HANA Migration Cockpit – Transfer Data Directly from SAP Source System
The cockpit guides you through the various steps of the data migration, but you can also flexibly choose
which steps you want to do next (select, simulate, migrate).
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 36
SAP S/4HANA Migration Cockpit
Transfer Data Directly from SAP Source System (planned 1809 FPS01)
You can maintain value mappings to transform values from the source system to the target system.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 37
SAP S/4HANA Migration Cockpit
Further Development
SAP S/4HANA Migration Cockpit – Outlook
Recent innovations 2018 – Planned innovations 2019 – Product direction 2020 – Product vision
Data Provisioning Data Provisioning Data Provisioning Enhanced Content Upgrade Functionality
On-Premise: Staging area between SAP Cloud: Staging area between SAP or Direct extraction from SAP source to merge modified migration objects with
or non-SAP source and SAP S/4HANA non-SAP source and SAP S/4HANA – Data extraction from SAP source updates on predefined migration objects
target system target system – Direct data transfer to SAP S/4HANA
target without interim files or staging
– Staging area must be filled by – Staging area must be filled by Analyses
– Enhance preconfigured content for data Analyze migration data in SAP source
customer using extraction tools from customer using extraction tools from migration from SAP Business Suite to
SAP or third party SAP or third party SAP S/4HANA systems
Automated field extension of migration Migration Object Modeler for direct data Data Quality
Data Migration Status app for SAP
objects via extension framework extraction from SAP source Plausibility checks on imported data
S/4HANA Cloud 1805 to validate uploaded Extension of filter criteria for data selection
data for specific migration objects Allow users to enhance existing migration Data Cleansing
objects
Migration Object Modeler for file and Allow users to create own migration objects
staging Business data migration from SAP Apparel and
Test/Simulation functionality for file and Footwear (SAP AFS) to SAP S/4HANA for
staging migration objects fashion
Key AFS wholesale components
Improved usability of modeler
– Master data
– Open transaction data
Migration content can be transferred
between systems (quality to production) Automated Validation
Automated validation of migration results
Auditable Solution
Provide information for an audit
This is the current state of planning and may be changed by SAP at any time.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 40
Agenda
Roadmap
Transferring Data to SAP S/4HANA via Direct Access with FIORI UI
Further Development
Closing
Summary
Helpful Documentation and Information
On-Premise
Cloud On-Premise
Link to list of
object
openSAP Course SAP Best Practices Explorer SAP Activate Roadmap Viewer
Data Migration to SAP S/4HANA [Link] [Link]
[Link] Data Migration from File (BH5): iewer/
[Link]
Data Migration from Staging (2Q2):
[Link]
Collection of all SAP Pre-filled migration Central Notes for Lists all changes in
Notes and most of the templates w/ sample Migration Cockpit the current, previous,
KBAs belonging to data and PDF that Tool and upcoming next
CA-GTF-MIG explains the data release
[Link]
[Link]/community
See all SAP TechEd blog posts
DAT266 – Explore How to Use Next-Generation Data Management Tools for Data Migration
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Legend: New objects in SAP S/4HANA Cloud 1808 Available Migration Objects S4H Cloud 1808 56
Preconfigured Business Objects (On-Premise 1809) – Part 1
Migration of Master and Transactional Data
Activity Price (restricted) Customer material Maintenance item
Activity Type Equipment Maintenance plan
Bank Equipment task list Master inspection characteristics
Bank account balance Exchange rate Material
Batch (if Batch is unique at material level) FI – Accounts payable open item Material BOM
Batch (if Batch is unique at plant level) FI – Accounts receivable open item Material classification
Cash memo record FI – G/L account balance and open/line item Material consumption
Characteristic Fixed asset (incl. balances and transactions) Material – extend existing record by new org level
Class Functional location Material inspection setting
Condition contract Functional location task list Material inventory balance
Consent G/L account Material long text
Cost center General task list Material trade classification
Customer Inspection method Pricing condition (general)
Customer (deprecated) Inspection plan Pricing condition (purchasing)
Customer - extend existing record by new org levels Internal order (restricted) Pricing condition (sales)
Customer - extend existing record by new org levels
Legal transaction Production version
(deprecated)
The On premise – Enterprise Management scope view is a template only to be used in an on-premise system.
For some migration objects there are additions to the migration cockpit object name. These additions include "restricted" and "deprecated”. Restricted means that not all fields and structures of the relevant business
processes are covered by this migration object, deprecated means that there is a newer version of this migration object available. Deprecated objects will be deleted after a couple of releases. Make sure you always read
the migration object documentation for these objects carefully.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Legend: New objects in SAP S/4HANA 1809 Available Migration Objects S4H OP 1809 57
Preconfigured Business Objects (On-Premise 1809) – Part 2
Migration of Master and Transactional Data
Profit center Supplier – extend existing record by new org levels (deprecated)
Purchase order (only open PO) Work center
Purchase scheduling agreement VC – Variant configuration profile
Purchasing contract Work center
Purchasing info record- extend existing record
Purchasing info record with conditions
QM/PM catalog code group/code
QM selected set
QM selected set code
Routing
Sales contract
Sales order (only open SO)
Software/Hardware constraint
Source list
Supplier
Supplier (deprecated)
Supplier – extend existing record by new org levels
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Legend: New objects in SAP S/4HANA 1809 58