OpenSAP s4h11 Week 02 All Slides

Week 2: Converting Finance and Business Partner
Unit 1: Changes in the System Landscape

Changes in the System Landscape
SAP S/4HANA – High-level stack architecture
Web SAP Fiori Client /

Logical view packaged app
On-Premise
SAP Web Dispatcher
▪ Launchpad / SAP Fiori SAP Fiori Shell

(Classic UI apps consist of SAPGUI for SAP Classic SAP Fiori SAP Fiori
HTML and ABAP Web Dynpro apps) Search
UI Apps Apps Launchpad
SAP Gateway
▪ Application Engines SAP S/4HANA ABAP

Transaction Logic Analytics Enterprise Search
CDS View
▪ Data Structures SAP HANA
(Compatibility provided through Core
Database Tables
Data Services)
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2
User experience for SAP S/4HANA – SAP Fiori design evolution
Shell header
Me-Area Anchor bar navigation Revised launching notification and Me-Area Notifications
Replacing former shell header Replacing group menu viewports and CoPilot window. Provides navigation Shown in separate viewport that opens on
menu. Shows recent activities now menu when app is launched by clicking title clicking repective icon in shell header
Links
Option to show apps
as links in a tile group
Me-Area Notifications
Workspace
SAP S/4HANA architecture and components – Front-end server deployment options
Embedded deployment Central Hub deployment SAP Fiori Cloud deployment

of SAP Gateway of SAP Gateway
Fiori Launchpad Content

Fiori Launchpad Content Fiori Launchpad Content SAP Fiori
SAP Fiori SAP Fiori UI Add-Ons
UI Add-Ons UI Add-Ons
SAP Gateway SAP Gateway Cloud Connector
SAP S/4HANA ABAP Option 1 – Embedded Option 2 – Central Hub
SAP S/4HANA ABAP SAP Gateway SAP Gateway
SAP S/4HANA ABAP

SAP S/4HANA ABAP

SAP S/4HANA – SAP Fiori access
▪ Client Access Web App Desktop SAP

(HTML5) Browser Business
(HTML5) Client
▪ External Access
Reverse SAP Web
Connectivity Proxy
VPN
Dispatcher
▪ SAP S/4HANA 1709 SAP Fiori Launchpad Content IDP

Front-End and Back-End Authentication
Authentication and SAP Fiori UI Mechanisms
Authorizations X.509
SAP Gateway Certificate
SAP SSO2
SAML 2.0
SAP S/4HANA
Version interoperability for SAP S/4HANA
S/4HANA S/4HANA S/4HANA S/4HANA … …

On-Premise
In conjunction with 1511 1610 1709 … …
SAP RTC 2015 7.50 7.50 7.50

NetWeaver
Systems
EP, BW, PI RTC 2013 7.40 7.40 7.40
in the
following
RTC 2012 7.31 7.31 7.31
versions
SAP Note 2251604 Version Interoperability between SAP S/4HANA On-Premise Edition and SAP NetWeaver Systems
Switch framework (always on / always off / customer switchable)
In SAP S/4HANA business functions can have the following status:

▪ always_on
▪ customer_switchable
▪ always_off
Start Release Target Release

(SAP Business Suite) (SAP S/4HANA 1709)
Status Status Conversion New Status Remarks
ON always_off NO – SAP Note 2240359 On roadmap
OFF always_on YES ON SAP Note 2240360
ON customer_switchable YES ON
OFF customer_switchable YES OFF

Output management for SAP S/4HANA
Business Applications
Business Application
▪ Need a solution for all output-related tasks
Output Control SAP S/4HANA output management

▪ Offers a unified solution (UI, configuration, processing) Output Control
▪ Exposes the low-level functionality to its consumers
Output
Output
Technology Parameter
Request
Determination
▪ Document creation via Adobe Document Services
▪ Document output via print queue, SAPconnect,
communication arrangement Technology
Document Document
Creation Output

This is the current state of planning and may be changed by SAP at any time
Miscellaneous changes for SAP S/4HANA
▪ Clients 001 and 066 are no longer required and not delivered (SAP Note 1749142)
▪ SAP Developer Keys (SSCR) are no longer required (SAP Note 2309060)
▪ SAP Best Practices client copy setup and configuration (SAP Note 2573352)

SAP S/4HANA multi-client configuration for SAP Fiori
▪ One-to-one mapping per client on both front-end and back-end systems

▪ Use same client number on both front-end and back-end systems to avoid mapping client setting
in Web dispatcher configuration
SAP Business SAP Fiori SAP S/4HANA SAP Fiori

Suite Front-End Server ABAP Front-End Server
Client 100 (Config) Client 100 (Config) Client 100
Client 200 (Dev) Client 200 (Dev) Client 200
Client 300 (Unit Test) Client 400 Client 300 (Unit Test) Client 300
https://blogs.sap.com/2016/10/11/configure-fiori-multi-clients/
This is the current state of planning and may be changed by SAP at any time
SAP CoPilot architectural overview
Required Components
▪ SAP Cloud Platform Web via
SAP Fiori Client
▪ Configured SAP Fiori 2.0 launchpad
Only applicable to
On-Premise beta customers in
SAP Cloud Platform the SAP CoPilot
Skill Builder beta
Cloud Remote AML 2.0
SAP CoPilot program
Connector Identity Provider
SAP Web Dispatcher

▪ SAP Web Dispatcher 7.53 patch 30
Front-End Server
or higher
SAP Fiori Local SAML 2.0 OData
▪ Cloud Connector 2.11.03 with Applications Identity Provider Services
Principal Propagation
▪ SAP NetWeaver 7.52 SP1 or higher SAP S/4HANA
SAP Business Suite
…
(ERP, SRM)
▪ SAP NetWeaver 7.51 SP6 or higher
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Unit 2: Essential Changes in Finance
Essential Changes in Finance
Introduction
“You should know the main changes in Finance

before you start system conversion!”
▪ A conversion to SAP S/4HANA is not only a technical upgrade. It includes functional changes.
▪ No system is impacted by all simplifications. Experience shows approx. 30-40 items are relevant.
▪ Consider the top simplifications in your project plan and plan in enough time for business to discuss them.
▪ Few items incur bigger impact, but might imply significant changes to business processes.
▪ Many items can and should be addressed in an early phase of a conversion project.
SAP S/4HANA Simplification Item Catalog https://launchpad.support.sap.com/#/sic/ and simplification list as PDF https://help.sap.com/s4hana
New data architecture: simplified data model in SAP S/4HANA
SAP Business Suite
This is a schematic representation, not all tables are shown

DATA CONVERSION DURING SUM FOLLOW-UP CONVERSION OF ACCOUNTING
SAP S/4HANA
MLDOC
MLDOC
CCS
SIMPLE DATA MODEL PRINCIPLE OF ONE

▪ Only main tables remain ▪ One universal journal in Finance
▪ No redundancies, no aggregates, no indices ▪ Only one material valuation application: material ledger
▪ Real-time integration, automatically reconciled ▪ Important for a conversion: consistent data
The new finance architecture in SAP S/4HANA: universal journal – Impacts for a conversion
G/L Customizing (Ledgers) General Ledger Profitability

Currency configuration Account-based CO-PA
Profit Amount Amount Amount Operating Market
Ledger Company Account … … in universal journal
migrated without changes Center 1 2 3 Concern Segment
Subsequent Universal Journal Append

Introduction:
Account/ Balancing
- Additional Ledgers Amount Amount Amount Fixed Coding Market Customer SAP Note
Ledger Company Cost Profit Material
1 2 3 Asset Block Segment Fields … 2160045
- Document Splitting Element Center
FI-documents for CO Management Accounting Asset Accounting Material Ledger Material ledger for
Secondary cost elements material valuation
Controlling Cost Amount Amount Coding Fixed
are G/L accounts … Company … Company Material …
Area Element 1 2 Block Asset
New Asset Accounting

One line item table with full detail for all applications – for instant insight & easy extensibility
Data stored only once: no more reconciliation needed – by design

Compatibility views for non-disruptiveness
▪ Read access from custom ABAP programs or reports to prior tables will work as before:*
Custom program or Totals,
Select Redirect Compatibility Views Read Universal Journal
report Indices,… ACDOCA
▪ Non-actuals are still stored in COEP and COS*_BAK:

ACDOCA
Custom program or
Select COEP Redirect V_COEP_VIEW
report or SE16
COEP
V_FAGLFLEXA_ORI
Select FAGLFLEXA
▪ Views for original content (V_*_ORI)
V_COEP_ORI COEP
▪ Back-up tables for totals tables and index tables (*_BCK,*_BAK) GLT0_BCK
COSP_BAK
▪ BSEG is still used to keep e.g. prima nota (Document Entry view) BSEG
SAP Note 2408083 – FAQ: Data Model of S/4HANA Finance Data Migration *check limitations e.g. in material ledger for actual costing
Material ledger and new asset accounting
Local GAAP
US GAAP
xxx xxx xxx
€ $¥
IFRS
Material Ledger Actual Costing in Material Ledger New Asset Accounting

▪ Mandatory for valuated stock ▪ Optional ▪ Mandatory
▪ Up to 3 parallel currencies ▪ Fundamental changes in actual costing ▪ Available in SAP ERP 6.0 EHP 7
▪ Prices and stock values are automatically ▪ Redesign of costing steps at period end ▪ Accounts or ledger approach
translated into parallel currencies ▪ Migration during conversion ▪ Simplified chart of depreciation
▪ Activation and migration during conversion ▪ SAP Note 2354768 ▪ Activation and migration during conversion
▪ SAP Note 2352383 and 2332591 ▪ SAP Note 2270388 and 2368280

Credit management, cash management, and trade finance
SAP Credit Management (FSCM) New SAP Cash Management Trade Finance
▪ Credit management FI-AR not available ▪ Classic cash management not available ▪ SD Foreign Trade not available
▪ Migration to SAP Credit Management ▪ Bank Account Management Lite available ▪ Letter of credit available in trade finance in
FIN-FSCM-CR during migration ▪ Migration of house bank accounts during Treasury and Risk Management (TRM)
▪ Basic version available conversion ▪ Integrated with SAP S/4HANA Sales
▪ SAP Note 2270544 ▪ Activation of new cash management after ▪ Migration during conversion
conversion ▪ SAP Note 2267310
▪ SAP Note 2270400 and 2165520

Real estate, revenue accounting, and business partners
Flexible Real Estate Management Revenue Accounting and Reporting Business Partners
▪ Classic Real Estate not available ▪ Revenue recognition in SD not available ▪ Customer/vendor integration mandatory
▪ Migration from classic Real Estate to ▪ Required for Accounting Standard IFRS15 ▪ Migration before conversion
flexible Real Estate Management (RE-FX) ▪ SAP Revenue Accounting and Reporting
before conversion (RAR) add-on in ERP and SAP S/4HANA
▪ Not a simple technical conversion ▪ Migration before conversion
▪ SAP Note 2270550 ▪ SAP Note 2267342

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: Conversion of Accounting – Overview and
Preparation Phase
Conversion of Accounting – Overview and Preparation Phase
Conversion guides for SAP S/4HANA
Preparation Phase Realization Phase

Cross-application & application- Follow-
SUM
specific preparation activities On
Finance Finance
Links to documentation
Preparation activities
SAP Note 2332030
Follow-on activities
Converting Accounting Components to SAP S/4HANA
Conversion Guide for SAP S/4HANA
Conversion Guides
▪ Conversion Guide for SAP S/4HANA on SAP Help
▪ Converting Accounting Components to SAP S/4HANA
▪ SAP Credit Management
▪ SAP Cash Management
▪ Migrating to New Asset Accounting (FI-AA (New)) on SAP Help

Overview of activities in finance and in the preparation phase

Application-
System Maintenance Custom Code Software Update
SI-Checks Specific Follow-
Requirements Planner Migration Manager (SUM)
On Activities
Cross-application & application-specific Database migration Finance

preparation activities Software update Conversion of Accounting
Finance to SAP S/4HANA**
Data conversion
Preparation
Identify and and Migration
Customizing pre- Finance
review relevant Customer/vendor Prepare Asset of Customizing
checks and adapt
simplification integration Accounting*
settings if needed Backup tables
items Data Migration
Compatibility views
Check
Period-end Document your Archive data you Activities After
consistency and
closing activities posting data no longer need Migration
reconcile data
*Enterprise Extension EA-FIN: SAP Notes 965032 and 1121965 **aka Finance Migration (named Migration to SAP S/4HANA
Alternative fiscal year variant for parallel valuation: SAP Note 2220152 Finance before SPS3 of SAP S/4HANA 1610)
Consistency checks
Conversion of Accounting
Target System
Customizing checks
Simplification item Analyze transactional data

check
Data migration checks
SAP S/4HANA
SUM Phase Follow-On Uptime

Start System
Uptime Downtime
Simplification item check /SDF/RC_START_CHECK (SAP Note 2245333 for messages and possible solutions)
Pre-check of Customizing for Asset Accounting RASFIN_MIGR_PRECHECK (check also SAP Note 2618023)
Consistency checks of transactional data & totals
ERP 6.0x
t
Overview: 3 phases of accounting conversion
Preparation
Software Update Activities After
and Migration Data Migration
Manager (SUM) Migration
of Customizing
ERP 6.0x SAP S/4HANA

Downtime Uptime
No postings allowed
Migration completed
▪ All the migration activities and documentation in the IMG
▪ Perform activities in the right sequence
▪ Do not skip any Customizing activities
▪ Finance migration has to be executed for each client
▪ All company codes are migrated (SAP Note 2522155 for Company Code Specific Conversion with SAP LT)
▪ Mark company codes as template to disable checks with FINSC_CO_CD_TEMPLATE: SAP Note 2159452
▪ Conversion from start release SAP Simple Finance, SAP S/4HANA Finance, or SAP S/4HANA 1511: SAP Note 2450377
Preparation and migration of Customizing: 10 steps
Preparation
Activities After
Migration
of Customizing
1. Check 3. Preparations 4. Preparations 5. Preparations

2. Set number of
customizing and migration of and migration of and migration of
jobs in mass data
settings prior to Customizing for Customizing for Customizing for
framework
migration general ledger accrual engine Asset Accounting
9. Preparations for 10. Preparations

6. Preparations 7. Preparations
8. Preparation for migration of and migration of
and migration of and migration of
migration of house financial Customizing for
Customizing for Customizing for
bank accounts documents to credit
Controlling material ledger
trade finance management

DEMO – Preparations and migration of Customizing
D E MO

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: Conversion of Accounting – Realization Phase
Conversion of Accounting – Realization Phase
Data migration steps 1 to 4
Preparation
Activities After
Migration
of Customizing
Data Migration
1. Regenerate 3. Display Status 4. Start and

2. Analyze 5. Migrate General
CDS Views and of Transactional Monitor Data
Transactional Data Ledger Allocations
Field Mapping Data Analysis Migration
10. Complete
7. Migration of
Migration of
6. Migrate House Financial 8. Migrate Credit 9. Set Migration to
Financial
Banks Accounts Documents to Management Completed
Documents to
Trade Finance
Trade Finance

Data migration monitor
Data Migration Monitor FINS_MIG_STATUS

GCC Check Consistency of G/L Accounts and Cost Elements
GCM G/L Account and Cost Element Merge
DAA Default Assignment for Cost Elements
R21 Reconcile Transactional Data
ENR Enrich Transactional Data
R22 Check Enrichment of Transactional Data
MUJ Data Migration into Unified Journal: Line Items
R23 Check Migration of Journal Entry
Start and Monitor Migration M10 Migrate Material Ledger
M20 Check ML Master Data
▪ Main transaction for data migration
M11 Migrate ML Order History
▪ Executes the data migration M21 Check ML Production Order & Purchase History
▪ Ensures the right sequence of migration activities DLT Data Migration ACDOCA – Deltas
▪ Overview of all performed migration runs R24 Check Migration of Balances
▪ Repeats and resets migration activities AFA Initial Depreciation Calculation

R25 Check Initial Depreciation

DEMO – Start data migration
D E MO

Data migration steps 5 to 10
Preparation
Activities After
Migration
of Customizing
Data Migration
1. Regenerate 3. Display Status 4. Start and

2. Analyze 5. Migrate General
CDS Views and of Transactional Monitor Data
Transactional Data Ledger Allocations
Field Mapping Data Analysis Migration
7. Migrate
9. Reconcile and
6. Migrate House Financial 8. Migrate Credit 10. Set Migration
Compare Migrated
Bank Accounts Documents to Management to Completed
Data
Trade Finance

Activities after data migration
Preparation
Activities After
Migration
of Customizing
Activities after Migration
1. Transfer 3. Fill the 5. Manual

2. Fill Due Dates 4. Enrich Balance
Application Offsetting Account Activities for Trade
in FI Documents Carryforward
Indexes in FI Documents Finance
10. Implement
6. Manual 8. Deactivate 9. Delete Records
7. Migrate Accrual New
Activities for Credit Reconciliation from Obsolete
Engine Data Functionalities in
Management Ledger Tables*
SAP S/4HANA
*SAP Note 2190137: FINS_MIG_OBSOLETE_DB_DEL

DEMO – Complete data migration
D E MO

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 5: Data Model for Business Partner
Data Model for Business Partner
New data model – Motivation
 In SAP S/4HANA, Business Partner is the leading object and single entry point to maintain
business partner, customer and supplier master data. 
ERP SAP S/4HANA
Specific applications (RE-FX, FSCM-

Specific applications (RE-FX,
FSCM-…, TRM, …), industries
BP …, TRM, …), industries
Embedded EWM
SAP S/4HANA for customer

management
SD – Sales Customer SAP Credit Management BP
(FIN-FSCM-CR)
SD – Sales Customer
MM – Purchasing Vendor MM – Purchasing Vendor

New data model – Categories
Natural Person Organization Group

▪ Private Person ▪ Company, Subsidiary ▪ Household, Joint Residence
▪ Personal Data ▪ Company Data ▪ Group Data
 First Name/Last Name, Academic  Name, Legal Form, Industry etc.  Name, Group Type etc.
Title, Date of Birth, etc.

New data model – Roles
Contact Person Vendor
Connector Prospect
Agency Employee
… General Customer
Business
Partner

New data model – Relationships
Business partners can be linked via

relationships
▪ Predefined relationship categories
▪ Possible to create own relationship categories
▪ Time-dependent
▪ Display of relationships as list/hierarchy/network
Has Contact Person

BP BP
Org. Is Contact Person for Pers.
(Z) Has Agent (Z’) Is Agent for
BP
Org.

New data model – Categories, roles, and relationships
(Role Grouping)
Business Partner BP General Customer Customer
Category Address Shipping Condition Payment Terms
Organization Payment Data Incoterms Reconciliation
Company Account
5437865678
Relationship Client Sales Area Company Code
Ms Miller
Is Contact Person for
Company
BP General Contact
Business Partner Name Person
Ms Miller Category Address Correspondence
Language
14356 Person
Client Client

New data model – Categories, roles, and relationships in transaction BP

New data model – Customer/vendor integration (CVI)
Example: Customer Creation Company Code Data

Central Data
Central Data Sales Area Data
A business partner is always created when a CVI Complex Interface
customer or supplier is created.
Business Partner Customer Vendor
The complex interface of the CVI (customer/vendor
integration) contains business partner-specific data Customer / Vendor
as well as customer and vendor-specific data. BP APIs
Data Buffer
Get
The data of the business partner and customer/vendor
is partially redundant (BUT000 against KNA1 & LFA1 SAVE CVI
data). For instance ‘Name and Address-specific Outbound
attributes’ are available in both persistencies.
Customer or vendor-specific data is routed through Customer APIs Vendor APIs
the customer/vendor-specific interface and mixed up
with the business partner central data.
On commit, the business partner and
corresponding customer and/or vendor and CVI Business CVI Link Customer Vendor
link tables are maintained/created. Partner Tables (Supplier)

New data model – Customer/vendor integration (CVI) – Synchronization
Company Code Data ERP Synchronization SAP S/4HANA

Central Data Sales Area Data
(Conversion) Synchronization
CVI Complex Interface
Business Partner Customer Vendor
BP APIs
Customer / Vendor Leading Background Leading Background
Data Buffer Object Object Object Object
Get
SAVE CVI
Outbound Customer Customer
Business Business
Partner Partner
Customer APIs Vendor APIs
Vendor Vendor
Business CVI Link Customer Vendor

Partner Tables (Supplier)

New data model – Numbering
Specific applications (RE-FX, FSCM-…,

TRM, …), industries
Embedded EWM
SD – Sales SAP S/4HANA for customer management MM – Purchasing

SAP Credit Management
(FIN-FSCM-CR)
Master data maintenance in SAP S/4HANA
(BP, customer, vendor)
Business Partner
456
The specific tables
Customer 123 Supplier 789
for customer data
(KNA1) and vendor
data (LFA1) remain
available and are not
impacted.
KNA1 CVI_CUST_LINK BUT000 CVI_VEND_LINK LFA1
Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 6: Customer/Vendor Integration and
Synchronization
Customer/Vendor Integration and Synchronization
Customer/vendor integration in transition scenarios
SAP S/4HANA
BP Upload
Migration Cockpit
IMPLEMENTATION SCENARIOS
Customers
Data Services CVI
Greenfield Vendors
Web Service BP Contacts
SAP S/4HANA Synchronization
LSMW
(KN*, LF*)
IDocs
Manual
CVI Configuration
ERP SAP S/4HANA
Customers
ERP to Customers BP
CVI CVI Vendors
SAP S/4HANA Vendors BP Create
Contacts
Contacts Mass Sync. Change Synchronization
Conversion (KN*, LF*)
Preparation Synchronization Conversion Post-Processing / Test

Mass synchronization in ERP: MDS_LOAD_COCKPIT
ERP SAP S/4HANA

Clean up PPO!
Tasks: Activate
Customer CVI: Customer Customer
▪ Data Cleansing CVI BP
Supplier C/V  Supplier BP Supplier
▪ Setup BP Mass Synch. Update
Create
Contact (MDS_LOAD_COCKPIT) Contact Change Contact
▪ Test Runs (Sandboxes)
Remaining time to
Preparation Synchronization Conversion + Go-Live
SAP S/4HANA

Mass synchronization in ERP: MDS_LOAD_COCKPIT

Data cleansing
SAP S/4HANA
New Checks, e.g. Changed Assignments, e.g.
▪ Postal Codes ▪ Tax Codes
▪ E-Mail Addresses Customers
BP Upload CVI Vendors
▪ Bank ID, Accounts BP
Contacts
(KN*, LF*)
All current
checks and
ERP assignment SAP S/4HANA
New New Changed Changed rules
check check assignment check
rules Customers
BP CVI Vendors
CVI Mass Create
Contacts
Synch. Change
(KN*, LF*)
Start Mass Synch.

Set up BP Customizing and master data synchronization (CVI)
Set Up Business Partner Set Up Master Data Synchronization (CVI)
Relationships

Steps after SAP S/4HANA conversion
ERP SAP S/4HANA
CVI: Tests, e.g. Check + Clean up PPO!

BP  C/V field attributes
CVI Customer
active
n/a BP
Add. steps, e.g. Create Supplier
Change Contact
HCM-Sync-Rep.
Conversion Post Conv. Go-Live

Set up BP Customizing and master data synchronization (CVI)
▪ BP setup
▪ Set up CVI (master data synchronization)
▪ Accelerators:
 Data quality check report (sample coding)
 Excel file to sort out number ranges
 SAP standard reports
▪ Experiences, How-tos
▪ Important SAP Notes

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 7: Tips and Tricks for Business Partner
Synchronization
Tips and Tricks for Business Partner Synchronization
Team setup
BP Team Functional Teams
ECC Financials
Mapping
Conversion
Sales
Procurement
SAP S/4HANA
HR

Time frame
As early as possible Activated CVI can run in parallel for long time Critical paths
▪ At beginning of S/4 project (C/V  BP) ▪ Data cleansing
▪ At the point an S/4 project is ▪ Takes pressure out of the project schedule ▪ Number ranges
planned ▪ Master data quality is the main reason for
delay at BP conversion
ERP SAP S/4HANA
Activate Customer Customer

CVI: CVI BP BP
ERP (production system) C/V  Supplier Create Supplier
BP
Mass Synch. Update
Change
Contact Contact
Remaining time to
Synchronization Conversion + Go-Live
SAP S/4HANA
Sandboxes as
copy of ERP CVI-Test CVI-Test CVI OK CVI OK
(S/4 Conversion) (S/4 Conversion) S/4 Conversion S/4 Conversion

Sandbox conversion
Number of sandbox
conversions Production
dependent on:
Copy
▪ Complexity
Sandbox Sandbox Sandbox Development Quality
▪ Amount of data
V1.0 V2.0 V3.0
▪ Data quality
...
Cutover Plan Cutover Plan Cutover Plan Cutover Plan Cutover Plan
for BP for BP for BP for BP for BP
Creation Refine Refine Refine Refine
Time

CVI mass synchronization in ERP business downtime
ERP
Technically possible in parallel to daily business but
▪ recommended in business downtime (at least downtime Activate
for respective master data changes) CVI: CVI
C/V 
BP Mass Synch.
Reasons (MDS_LOAD_COCKPIT)
▪ Performance: number of parallel task vs business
processes
▪ Recommended to stop C/V/CP/BP* interfaces: creation Synchronization
of BP might trigger change pointers
▪ Numbering  certain temporary setup might be required
to gain respective BP numbers
* C – Customer, V- Vendor, BP – Business Partner

Data model BP – Numbers at Business Partner and Customer/Supplier
Sales Purchase
Order Order
Customer 123 I_Supplier

Supplier 456
Business Partner 789
KNA1 CVI_CUST_LINK BUT000 CVI_VEND_LINK

CVI_VEND_LINK LFA1
Example: numbering in ERP and SAP S/4HANA
Variant 1
Keep the same Business Partner number for Customer/Supplier and Contact Person
 Prerequisite: No overlaps
ERP (before conversion) SAP S/4HANA (after conversion)

Direction Customer/Supplier  BP Direction BP  Customer/Supplier
Customer 12345 BP 12345 BP 12345 Customer 12345
Supplier 56789 BP 56789 BP 56789 Supplier 56789

Variant 2
New BP numbers  different numbers for BP and Customer/Supplier/Contact Person

Customer 12345 BP 1001456 BP 1001456 Customer 12345
Supplier 56789 BP 1001457 BP 1001457 Supplier 56789

Variant 3
Merge Customer and Supplier
▪ Same BP and Customer number  Customer no. is leading in ECC

KNA1 KNA1
Customer 12345 Customer 12345
External number Internal number
BP 12345 BP 12345
LFA1 LFA1
BUT000 BUT000
Supplier 56789 Supplier 56789

Variant 4
Merge Customer and Supplier
▪ Different numbers for BP and Customer/Supplier/Contact Person

KNA1 KNA1
Customer 12345 Customer 12345
External number Internal number
BP 1001456 BP 1001456
LFA1 LFA1
BUT000 BUT000
Supplier 56789 Supplier 56789

Thank you.
open@sap.com
Follow all of SAP

warranty.

OpenSAP s4h11 Week 02 All Slides

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenSAP s4h11 Week 02 All Slides

Uploaded by

Copyright:

Available Formats

Week 2: Converting Finance and Business Partner

Unit 1: Changes in the System Landscape

Web SAP Fiori Client /

▪ Launchpad / SAP Fiori SAP Fiori Shell

▪ Application Engines SAP S/4HANA ABAP

Embedded deployment Central Hub deployment SAP Fiori Cloud deployment

Fiori Launchpad Content

SAP S/4HANA ABAP Option 1 – Embedded Option 2 – Central Hub

SAP S/4HANA ABAP SAP Gateway SAP Gateway

SAP S/4HANA ABAP

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

▪ Client Access Web App Desktop SAP

▪ SAP S/4HANA 1709 SAP Fiori Launchpad Content IDP

S/4HANA S/4HANA S/4HANA S/4HANA … …

SAP RTC 2015 7.50 7.50 7.50

In SAP S/4HANA business functions can have the following status:

Start Release Target Release

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Output Control SAP S/4HANA output management

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

▪ One-to-one mapping per client on both front-end and back-end systems

SAP Business SAP Fiori SAP S/4HANA SAP Fiori

Client 100 (Config) Client 100 (Config) Client 100

Client 200 (Dev) Client 200 (Dev) Client 200

SAP Web Dispatcher

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

“You should know the main changes in Finance

This is a schematic representation, not all tables are shown

SIMPLE DATA MODEL PRINCIPLE OF ONE

G/L Customizing (Ledgers) General Ledger Profitability

Subsequent Universal Journal Append

New Asset Accounting

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

▪ Non-actuals are still stored in COEP and COS*_BAK:

Material Ledger Actual Costing in Material Ledger New Asset Accounting

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

Preparation Phase Realization Phase

Conversion Guide for SAP S/4HANA

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Preparation Phase Realization Phase

Cross-application & application-specific Database migration Finance

Simplification item Analyze transactional data

SUM Phase Follow-On Uptime

Preparation Phase Realization Phase

ERP 6.0x SAP S/4HANA

1. Check 3. Preparations 4. Preparations 5. Preparations

9. Preparations for 10. Preparations

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

1. Regenerate 3. Display Status 4. Start and

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Data Migration Monitor FINS_MIG_STATUS

▪ Repeats and resets migration activities AFA Initial Depreciation Calculation

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

1. Regenerate 3. Display Status 4. Start and

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Activities after Migration

1. Transfer 3. Fill the 5. Manual