Work-Package - 03 - May 2019

10Steps2S4: Logistic preparation activities
WorkPackage 03
Phased approach (1/2)
WP 1 WP 2 WP 3 WP 4 WP 5
Date April 30, 2019 May 6, 2019 May 7, 2019 May 8, 2019 May 9, 2019
2.30 PM (SGT) 12.30 PM (SGT) 12:30 PM (SGT) 12:30 PM (SGT) 12:30 PM (SGT)
Objective Kick-off call Prepare Phase Prepare Phase Prepare Phase Technical Conversion
(Logistics) (Finance) with SUM (DMO)
Content / Tasks • Overview • Readiness Check • Business Partner • Finance preparation • Start system
• Convert or re- • Maintenance Planner concept • Consistency checks conversion
implement • ATC - Custom Code • Customer Vendor • Reconciliation • Complete uptime
• How to get there • Conflicting Business Integration (CVI) • Period-end closing phases
• System environment Functions • MATNR Extension activities • Execute full
• Conflicting Add-ons • MRP Area • Document posting downtime
• Pre-checks with SIC data • Post-activities
Duration roll-out session 1,5 hour 2 hours 2 hours 1,5 hours 2 hours
Partner additional effort 1 hour (team preparation) 3 – 4 hours 4 – 5 hours 2 – 3 hours 2 days (duration)
Partner Resources Architects Basis Consultant Application Consultant Application Consultant Basis Consultant
required Team Leader Developer (analysis only) (logistic area) (finance area)
© 2019 SAP SE or an SAP affiliate company. All rights reserved. 2

Phased approach (2/2)
WP 6 WP 7 WP 8 WP 9 WP 10
Date May 13, 2019 May 14, 2019 May 15, 2019 May 16, 2019 May 17, 2019
12:30 PM (SGT) 12:30 PM (SGT) 12:30 PM (SGT) 12:30 PM (SGT) 12:30 PM (SGT)
Objective Finance Conversion Post ConversionActivities Gateway & Fiori Additional post conversion Review & Feedback
Configuration topics
Content / Tasks • Post technical • Output Management • Configuration of • Fiori specialties • Project Experience
conversion tasks • PP/DS embedded Front-end • Web Assistant • Feedback
• Customizing/Data • Convert Architecture server • Secure communication • Q&A
Model impact • Activation and • Expose system to the
changes configuration of FIORI internet
• Credit Launchpad • Custom code fixes
Management • Activation and
configuration of FIORI
applications
Duration roll-out 2 hours 1,5 hours 1,5 hours 1,5 hours 2 hours
session
Partner additional effort 5 – 6 hours 3 – 4 hours 5 – 6 hours 3 – 4 hours 1 hour
Partner Resources Application Consultant Application Consultant Basis Consultant Basis Consultant All Team
required (Finance area) Basis Consultant Application Consultant Developer
(testing)

Content:
• Review of previous work-package
• Logistic preparation activities
• Business Partners with Customer Vendor Integration

• Storage Location MRP
• Material Number Field Length Extension
• International Trade / Settlement Processing
• Closure and Call to Action!

Review of previous work-package
Review of previous work-package
Connect to the landscape

SAP Readiness Check
Maintenance Planner
Custom Code checks
Pre checks with Simplification Item-Check

Connect to the landscape
S/4HANA
Terminal Server Application Server
1 LNX
3
SAP ERP 6.0 Ehp6 SAP HANA 2.0 SP03
Windows 2012
SQL Server 2012
2
S/4HANA Adobe
Custom Code Check Document Services
ATC
Communication
SAP Readiness Check
1. Prepare source system

– Minimum release: SAP ERP 6.x EhP0 on any database
– Help portal: https://help.sap.com/viewer/p/SAP_READINESS_CHECK
– SAP Readiness Check tool preparation note: SAP Note 2290622
2. Execute program SAP Readiness Check

– Via your local SAP Solution Manager system (recommended)
– Via our direct cloud upload
3. Explore results to start Conversion project

– Recommendations dashboard per system, sent via email as url link
– Engage SAP Digital Business Services or your preferred implementation partner

Maintenance Planner
NOTE: NO activities! Already executed as part of 10Steps2S4, XML file available
Ø The Planning tool (successor for MOpz)

for update, upgrade, migration, conversion, installation
http://apps.support.sap.com/sap/support/mp
Ø Preparations for Conversion: Check and Plan
Ø Checking Source System

concerning AddOns, Business Functions, Industry Solutions
License for SAP S/4HANA not required for check
Ø Planning for Conversion

Provides Software Archives & Stack.xml
Backend and Frontend Server (FIORI) are considered
Ø Un-installation of AddOns can be planned now;

3rd Party AddOns may have to be checked separately

Custom Code checks
Remote checks with ATC
Already done in 10Steps2S4
1) Setup remote ATC in central system and Central Check System (SAP_BASIS 7.53)
implement the SAP Note 2436688 ABAP Test Cockpit (ATC)
Simplification
2) Download the newest version of the DB
Simplification Database from SAP RFC RFC RFC
Service Marketplace (SAP Note
2241080)
3) Install the Simplification Database on the Checked Checked Checked

central check system (transaction SYCM) System A System B System C
(>=7.00) (>=7.00) (>=7.00)
Customer Customer Customer
4) Run ATC with check variant Code Code Code
S4HANA_READINESS_REMOTE
Remote Stubs
5) Analyze the ATC result list

Find more about Technical setup of remoteATC
in the SAP community

Pre checks
with Simplification Item-Check
Preparation phase Realization phase
Maintenance Software Update AAppppliccaatioonnssppeeccifficc

System requirements Pre-Checks CCuusstoommccooddeepprreeppaarraatioonn
planner Manager (SUM) foolooww--uuppaaccttivvitieess
Pre-checks are shipped as SAP Notes to customers that plan to convert to SAP S/4HANA. Pre-Checks
Pre-checks are executed on the (SAP Business Suite) start system (preparation phase)
to determine relevant Simplification Items.
Pre-Checks are executed again as step in the Software Update Manager (SUM). In case
dedicated Simplification Items require mandatory preparation steps the conversion procedure can stop to ensure a consistent system
conversion.
Customer-specific Simplification List

Pre-Check S-Item Title Area Relevancy Business Impact Note
The pre-check framework will be COST ELEMENTS FIN - Controlling 2270419
delivered via one SAP Note and all Pre-Check Currencies in Universal Journal FIN - General 2344012
coded pre-check classes will be Report Business Partner Approach Master Data 2265093
delivered with one TCI Note
(Transport-Based Correction … … …
Instructions)
Logistic preparation activities
Ø Business Partners with Customer Vendor Integration
Ø Storage Location MRP
Ø Material Number Field Length Extension
Agenda
§ S/4HANA & CVI – Context and Motivation

§ CVI Business Impact
§ CVI process & HOW TO Convert in Different S/4HANA Transition Scenarios (Greenfield vs. Conversion)
§ Impact on Custom Code and Interfaces
§ Impact on Surrounding Systems
§ Lessons Learned
§ CVI Conversion Approach and Consideration
§ Additional Features and Information

Agenda

§ CVI process & How to Convert in Different S/4HANA Transition Scenarios (Greenfield vs. Conversion)
§ Lessons Learned

S/4HANA & CVI – Context and motivation
Customer/Vendor Object Model Limitations

– Only one single address
– No relation between a vendor and a customer for the same real world entity (no role concept)
– No person object available
– No time-dependency
Business Partner – SAP Strategic Object Model

– General data are shared across different roles
– Different Business Partner Categories – Organization, Person, Group
– One business partner could perform multiple roles, e.g., customer and vendor (supplier)
– One business partner could have multiple addresses
– Addresses, bank data, relationships can be maintained time-dependent
– Relationships between Business Partners (“Is Contact Person For”, “Is Service Provider For”, “Is Responsible
Employee For”)
– Provide harmonized architecture

S/4HANA & CVI – Context and motivation
Business Partner Concept Usage

In ECC
– SAP Collections Management (FSCM-COL)
– SAP Credit Management (FSCM-CR)
– SAP Treasury and Risk Management (TRM)
– Loans Management (FS-CML)
–…
§ In New Strategic Applications
– CRM
– SCM
– SRM
– GTS
– Industries: Banking, Public Sector, …
Customer/Vendor Integration (CVI) component ensures the synchronization between the Business Partner
object and the customer/vendor objects.
S/4HANA Business Partner Master Data
Company Code data

Sales Area. data
CCeenntrtraalDDaatata*
CVI Complex Interface Maintenance Process

Business
Customer Vendor
Partner
Business Partner creation is the first step in the creation of

Customers and Suppliers.
Customer / Vendor
BP APIs Data Buffer
Get Technically, the Customer-Vendor-Integration (CVI) takes care of

the general Business Partner data as well as the Customer and
Supplier specific data.
SAVE CVI
Outbound
Partially, the data of the Business Partner and

Customer/Supplier are redundant to provide consistent process
information for all ERP applications which do not use BP.
Customer Vendor
APIs APIs
While saving all Business Partner and Customer/Supplier data

are updated.
Distribution of Business Partner is provided by Idocs/SOA

Services using Data Replication Framework (DRF).
Business CVI Link Customer Vendor
Partner Tables (Supplier)

Customer Vendor Integration
Data Model
Purchase
Sales Order Order
I_Customer I_Supplier
I_BusinessPartner
KNA1 CVI_CUST_LINK BUT000 CVI_VEND_LINK LFA1

Simplified Business Partner Data Model
Business Partner Data Supplier(Vendor) Data Address Data
Business
Central Data GeneralData Address
Partner
Roles CompanyCode
Organization Data Phone
Person Bank Details Purchasing

Org. Data Fax
Group Identification
Numbers Email
Customer Data
Tax Numbers
URL
Industry GeneralData
Sectors
Company Code
Relationships Data
Sales
Contact
Org. Data
Partners
Address
Address
Usages
ERP
Vendors
ERP
Customers

Agenda

§ CVI process & How to Convert in the Different S/4HANA Transition Scenarios (Greenfield vs. Conversion)
§ Lessons Learned

CVI Business Impact in S/4HANA On-Premise
– Only SAP Business Suite customer with C/V integration in place can move to SAP S/4HANA, on-
premise edition. All the customers, vendors and their contact person have to be converted to Business
Partners (BP) in ERP system before starting the S/4HANA conversion processes.
– Transaction code, BP, is the single point of entry to create, edit, and display master data for business
partners.
– In S/4HANA all the previous ECC transactions, reports, conditions records, forms, etc. which use
customer or vendor number as input fields will expect the customer or vendor number regardless of
whether the linked BP has the same customer/vendor number or different. In other words, even if a new BP
number is assigned to the customer or the vendor, the ECC customer or vendor number still has to be
entered.
– Only those customer/vendor creation BAPI calling CVI functions CVI_EI_INBOUND_MAIN can be used.
– Vendor in ERP is called Supplier in S/4HANA.
– CVI is not mandatory for SAP Simple Finance or S/4HANA Finance On-Premise.

Cross Topic – Customer Vendor Integration
Obsolete Transactions
With S/4HANA, a business partner is mandatory for every customer or vendor. Therefore, customer or vendor
master have to be maintained as business partner and the following transactions could no longer be used:
Activity Transaction
Create Customer XD01 (complete)
VD01 (sales)
FD01 (accounting)
Change Customer XD02 (complete)
VD02 (sales) Transaction BP
FD02 (accounting) Fiori Apps
Display Customer XD03 (complete)
VD03 (sales)
FD03 (accounting)
Create Vendor XK01 (complete)
MK01 (procurement)
FK01 (accounting)
Change Vendor XK02 (complete)
MK02 (procurement)
FK02 (accounting)
Display Vendor XK03 (complete)
MK03 (procurement)
FK03 (accounting)

Cross Topic – Customer Vendor Integration
New Fioris
New Fiori apps for customer and vendor master creation and change are provided.

S/4HANA Business Partner Approach: Related Topics Customer and Vendor
§ SD/Customer
▫ SD Partner Functions can be still used and is part of the BP transaction - folder Sales and Distribution
▫ Customer account group can be changed in the Business Partner(BP) transaction
§ S/4 Prospect to customer
▫ Create BP with Role Prospect(BUP002) – No KNA1created
▫ Change Role from Prospect to Customer( e.g.FLCU01)
§ Hierarchies
▫ The already in ERP available hierarchies can be used
- Customer Hierarchy
- Vendor Hierarchy
§ Mass maintenance
▫ Mass Transactions(XD99, XK99 and MASS)
▫ Mass maintenance Fiori App – Customer Master Mass Maintenance; Mass Maintenance, Supplier Master tiles

Agenda
§ S/4HANA & CVI – Context and motivation

§ CVI process & HOW TO convert in different S/4HANA transition scenarios (greenfield vs. conversion)
§ Impact on custom code and interfaces
§ Impact on surrounding systems
§ Lessons Learned

CVI process scenarios (in context of S/4HANA implementation)
S/4HANA
BP update
Implementation Scenarios
Data Services Customer

Cloud & OP Webservice CVI Vendors
Greenfield BP Contacts
LSMW Synchronization
S/4HANA IDOC (KN*, LF*)
Manual
CVI Configuration
ERP S/4HANA
Customer
ECC to Customer BP
CVI CVI Vendors
S/4HANA Vendors BP (Create, Contacts
Conversion Contacts Conversion Change) Synchronization
(KN*, LF*)
Preparation Synchronization Conversion Post Processing / Test

CVI Process
§ CVI Process in S/4HANA On-Premise

– Before you execute the conversion SAP recommends to archive the customer/vendor with the deletion flag
Any customers, vendors and assigned contacts with the deletion flag but not archived need to be
converted to BP.
– SAP recommends to keep the customer/vendor number the same when converting to business partners.
Precondition
– ERP release level needs to be at SAP ERP 6.0, EhP 0-8.
If your system is at EhP 0 to 4 and the vendor contact person is used, apply Note 2383051 – Development
of vendor contact person mapping to business partner.
– Skill set required

▫ Functional and customizing knowledge of customer/vendor and BP master data.
▫ Business process knowledge is required for BP number rangedetermination.

CVI Conversion for S/4HANA On-Premise & Greenfield
Handover from
Select
Synchronization
- CVI enhancements - Activate BF - Pre-Check Activate
Cockpit Test
- CVI Configuration - Check Customizing - SUM BP->Cust/Vendor
Completion Check
Consultants are involved in the transformation activities
Application contacts are involved in the transformation activities Note: Best Practice
configuration parameters
Greenfield implementation - Only Post Processing/Test step is required, are shown in J61. If a
follow Best Practice Building Block J61– Use link to get the latest version. project is not based on
https://support.sap.com/content/dam/SAAP/Sol_Pack/Library/Configuration/J61_S4HANAX_BB_ConfigGuide_EN_XX.docx
Best Practice, use those
ERP S/4 HANA configuration parameters
as reference only.

CVI Conversion - Preparation
Handover from
Select
Synchronization
- CVI enhancements - Activate BF - Pre-Check Activate
Cockpit Test
- CVI Configuration - Check Customizing - SUM BP->Cust/Vendor
Completion Check
Task:
• Check and integrate Customer/Vendor enhancements
• Activate Business Function CA_BP_SOA
• CVI customizing, check customizing, and trigger necessary changes
• Define Number Assignments according
to the S/4 conversion guide chapter “Introduce Business Partner App roach (CVI)”
• Maintain BP mapping customizing and run check report
• Check and cleanup customer/vendor data
ERP S/4 HANA

CVI Conversion – Preparation: Step 1
Archive Data with Deletion Flag - Optional
§ Archive customer/vendor data with deletion flag
Before you execute the transformation for all customer/vendor data without restrictions SAP recommends to
archive the customer/vendor with the deletion flag.
Also customer/vendors with deletion flag which are not archived must be transferred.
§ Archiving Customer Data Procedure available here.
§ Archiving Vendor Data Procedure available here.
Note: Archiving is an optional step. It could be skipped if no added value is provided by the process. Archiving
could simplify CVI conversion if customer or vendor objects’ settings were removed from the IMG, e.g., obsolete
number range. The customers and vendors with deletion flags could be converted to BPs.

Download SAP Reports and Check/Integrate Enhancement
– Download check reports: (These reports will be used in Step 6)
▫ Note 2216176 - Precheck report from business partner (report PRECHECK_UPGRADATION_REPORT)

▫ Note 1623677 - BP_CVI: Check report for checking CVI Customizing (report CVI_FS_CHECK_CUSTOMIZING)
▫ Note 974504 - Inconsistencies in link tables of master data sync. (report ZCUSTOMER_LINK_CHECK_REPORT)
▫ Note 2399368 - Excel upload option in MDS_LOAD_COCKPIT (allow customer/vendor selection upload from Excel for BP
conversion)
– Check and Integrate Customer/Vendor Enhancement

See SAP Notes 2309153 and 2295823
The notes explain how to make customer enhancements to the customer/vendor integration, (integrating
additional customer/vendor fields in the business partner and using CVI synchronization to update them in the
customer/vendor).

Business Function Activation
Activate Business Functions

– CA_SUPPLIER_SOA
– CA_BP_SOA
Switch 'VENDOR_SFWS_SC1' and switch 'VENDOR_SFWS_SC2' have to be active for the vendor
contact person data to be synchronized with BP contact persons data and make sure that they have
“Global status” as On.
See SAP Note 1454441 - Development of contact person for vendors.
–

Customizing Tasks
Customizing Tasks
1. Activate the PPO Request for the synchronization
object Business Partner
Cross-Application Components -> Master Data Synchronization ->
IMG Path Synchronization Control -> Synchronization Control-> Activate PPO
Requests for Platform Objects in the Dialog
2. Active Synchronization between

Customer/Vendor and BP is active
IMG Path Synchronization Control -> Synchronization Control-> Activate
Synchronization Options
3. Active Creation of Post processing Orders (PPO)

for component AP-MD
Cross-Application Components -> General Application Functions ->
IMG Path Postprocessing Office -> Business Processes->Activate Creation of
Postprocessing Orders

Customizing Tasks - continued
Customizing Tasks – Number Range Recommendation

4. If Customer and Vendor number ranges are not 4. The business partner number ranges could be the
overlapping same as the customer and vendor number
ranges.
5. If Customer and Vendor number ranges are 5. Maintain the business partner number range in
overlapping such a way that the most numbers from customer
or vendor stay unchanged.

Customer BP
External External
Account Number /Interna BP /Interna
Group Name Range From To l Grouping Name NR From To l
0001 Sold-to party 01 100000 199999 Ext C001 Sold-to party B1 100000 199999 Ext
YB01 Sold-to party (ext. number) 01 100000 199999 Ext C002 Sold-to party (ext. number) B1 100000 199999 Ext
YBAC Customer (affiliated company) Y4 400000 499999 Ext C003 Customer (affiliated company B4 400000 499999 Ext
YBEC Export Customers 01 100000 199999 Ext C004 Export Customers B1 100000 199999 Ext
YBOC CPD Customer (external no.) XX A ZZZZZZZZZZ Ext C005 CPD Customer (external no.) AB A ZZZZZZZZZZ Ext
YBPC Dummy customer XX A ZZZZZZZZZZ Ext C006 Dummy customer AB A ZZZZZZZZZZ Ext
YBVC Vendor 02 200000 299999 Ext C007 Vendor B2 200000 299999 Ext
Vendor BP
Account Number External/ BP External/
Group Name Range From To Internal Grouping Name NR From To Internal
YB01 Domestic Vendor Y3 300000 399999 Ext YB01 Domestic Vendor B3 300000 399999 Ext
YBAC Vendor (affiliated companies) Y4 400000 499999 Ext ZBAC Vendor (affiliated companies) B5 500000 599999 Int
YBIV Foreign Vendor Y3 300000 399999 Ext YBIV Foreign Vendor B3 300000 399999 Ext
YBOV CPD Vendor (ext.no.assignmen. XX A ZZZZZZZZZ ZExt ZBOV CPD Vendor (ext.no.assignmen. B6 600000 699999 Int
YBTR Commercial traveller XX A ZZZZZZZZZ ZExt YBTR Commercial traveller AB A ZZZZZZZZZ ZExt


6. continued
Access and check the customer number range transaction by choosing the following navigation option:
Logistics - General -> Business Partner -> Customers
IMG Path ->Control-> Define and Assign Customer Number
Ranges
Access and check the vendor number range transaction by choosing the following navigation option:
Logistics - General -> Business Partner -> Vendor
IMG Path ->Control-> Define Number Ranges for Vendor Master
Records
Access the business partner number range transaction by choosing the following navigation option:
Cross-Application Components -> SAP Business
IMG Path Partner -> Business Partner->Basic Settings->Number
Ranges and Groupings -> Define Number
Ranges/Define Groupings and Assign Number Ranges

6. Continued
Define contact person BP number range – Very Important Step

CVI conversion report MDS_LOAD_COCKPIT will assign an internal BP number to contact person
during conversion. The internal number range is the number range assigned to the internal standard
grouping. If assigned internal number range overlaps with the targeted customer or vendor number
ranges, the number range for contact person has to be changed to a new range outside the targeted
BP numbers for the customers and vendors.
The overlap of the contact person number with its associated Business Partner numbers could cause
error – R11124 “Business partner with GUID xxxxxxxxxxxxxxxxxxxx does not exist”.

7. The following BAdIs are provided for CVI data assignment.

You can implement customer-specific mapping like Form of Address from Customer/Vendor to BP via
the available BAdIs. Here it would be also possible to create a BP in different category e.g. person
instead organization. In this case you have to deactivate the BAdI Enhancement implementation
CVI_MAP_TITLE_DIRECT and activate the implementation CVI_MAP_BP_CATEGORY via IMG. The
implementation is already available.
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> BAdI Definition
IMG Path Business Partner Settings ->Business Add-Ins (BAdIs)
a. BAdI: Data Assignment BP <-> Customer/Vendor/Contact Person a. CVI_CUSTOM_MAPPER
b. BAdI: Data Assignment of Bank Details BP -> Customer/Vendor b. CVI_MAP_BANKDETAILS
c. BAdI: Data Assignment of Payment Cards BP <-> Customer c. CVI_MAP_CREDIT_CARDS
d. BAdI: Data Assignment of Form of Address from Customer/Vendor to BP d. CVI_MAP_TITLE
e. BAdI: Defaults for Creating Data from BP to Customer/Vendor e. CVI_DEFAULT_VALUES
For BP/customer/vendor table fields extension, see SAP Note

2309153 - BP_CVI: Guide for customer enhancements in CVI (customer/vendor integration) in S4HANA releases
2295823 - BP_CVI: Transfer of customer / vendor fields to the business partner - template source code
Mapping Tasks
Mapping Tasks IMG Path
Customer/Vendor Integration -> Business Partner Settings -> Settings for
Customer Customer Integration -> Define BP Role for Direction Customer to BP
1. BP roles are assigned to account groups
Vendor IMG Path …-> Settings for Vendor Integration -> Define BP Role for Direction Vendor to BP
for customer and vendor
For customer enter BP Roles FLCU00
(company data) and FLCU01 (sales
data).
For vendor enter FLVN00 (company
data) FLVN01 (Purchasing data)

IMG Path Customer/Vendor Integration -> Business Partner Settings -> Settings for
Customer Customer Integration -> Field Assignment for Customer Integration ->
Assign Keys ->Define Number Assignment for Direction Customer to BP
2. For every customer/vendor account …-> Settings for Vendor Integration -> Field Assignment for Vendor Integration
Vendor -> Assign Keys ->Define Number Assignment for Direction Vendor to BP
group a BP Grouping must be available IMG Path
NOTE: The screenshot field values in this

document are for reference ONLY

Mapping Tasks - continued
Mapping Tasks
3. Attribute value mapping must be maintained and must
equal for every existing customer instance
For Contact Person
a. Activate Assignment of Contact Persons
b. Assign Department Numbers for Contact Person
c. Assign Functions of Contact Person
d. Assign Authority of Contact Person
e. Assign VIP Indicator for Contact Person
For Customer Attributes:

a. Assign Marital Statuses
b. Assign Legal Form to Legal Status
c. Assign Payment Cards
d. Assign Industries

Run CVI Customizing Check Report
CVI Customizing Check Report

1. Transaction Code - CVI_FS_CHECK_CUST
Report - CVI_FS_CHECK_CUSTOMIZING
The report is provided in SAP Note: 1623677 -
BP_CVI: Check report for checking CVI
Customizing
The report checks the customizing in both
directions: Customer/Vendor to BP and BP to
Customer/Vendor Customization. The latter is
done in S/4HANA in post processing or a
greenfield implementation.
The report checks the customizing

▫ Preparation Step 4-1, 4-2, 4-3 above
▫ Preparation Step 5-1, 5-2

Run Mapping Check Report
3. Run Transaction code - CVI_PRECHECK_UPGRADE or Check the top 4 checkboxes to run the
report PRECHECK_UPGRADATION_REPORT provided in Precheck report. The button 3 boxes are
SAP Note 2216176 - Precheck report from business partner automatically checked by the system, and
to ensure all the necessary CVI mappings are done. have not impact to the check report.
The following are checked before converting the

customer/vendor to BP:
▫ BP roles are assigned to account groups, Step 5-1above
▫ Every account group BP grouping must be available, Step 5-2
▫ Customer value mapping, Step 5-3
▫ Vendor value mapping, Step 5-4
▫ CVI Mapping and Contact Person Mapping checkboxes are checked
by default. They are used after BP conversion to check if all
customers/vendors/contact person are converted.

Run Mapping Check Report - continued
3. Continued
Run T-code CVI_PRECHECK_UPGRADE
report PRECHECK_UPGRADATION_REPORT
▫ Double click the red light to see the detailed messages.
Proceed to CVI Synchronization after all errors are

resolved.

CVI Conversion – Preparation
Alternative to Manual Configuration
A guided approach for CVI conversion is possible with the application of the following notes.
1. 2336018 - BP S4HANA : Suppress Mandatory BP field groups checks via MDS_LOAD_COCKPIT

transaction
2. 2345087 - BP_BAP: Missing values in required entry fields cause posting termination in mass processing
3. 2344034 - S/4HANA Automation for Master Data Migration

CVI Conversion - Synchronization
Handover from
Select
- Implement Pre-Checks Check CVI/BP Synchronisation - Pre-Check Activate

Test
- Activate BF Customizing Cockpit - SUM BP->Cust/Vendor
ERP S/4 HANA

CVI Conversion – Synchronization Steps
1. Run report MDS_LOAD_COCKPIT

It creates a corresponding SAP business
partner for the customer, vendor and contact
data for general data, addresses, role data,
bank details.
2. Double click the desired synchronization
Process
Customer Business Partner or
Vendor Business Partner
3. Filtered the customer/vendor by account group
or customer/vendor numbers. To facilitate error
analysis, run small batch initially, e.g., select 10
to 50 customers or vendors.
4. Execute the report (F8)

CVI Conversion – Synchronization Steps (continued)
5. To resolve the error, select the monitor tab, and

click the Call PPO icon
6. PPO screen is displayed with the master data

error list
7. You could resolve the master data error from

the PPO screen or fix the error outside PPO,
see Synchronization Cockpit help document for
more information.
8. Correct all master data errors to complete the

customers/vendors/contact person conversion.
9. Run T-code CVI_PRECHECK_UPGRADE

report PRECHECK_UPGRADATION_REPORT to check the
completion of the conversion.
▫ Execute the report with the default selections. (bottom 3
checkboxes)
▫ CVI Mapping checks if all the customers/vendors are converted to
BP, i.e., the number of entries in table
CVI_CUST_LINK/CVI_VEND_LINK equals KNA1/LFA1).
▫ Contact Person Mapping checks if all contact persons have been
converted to BP, i.e., CVI_CUST_CT_LINK and
CVI_VEND_CT_LINK must contain the same number of entries
as contact table KNVK with the condition KNVK with where
condition KUNNR <> SPACE and KNVK with where condition
LIFNR <> SPACE.
▫ If there are inconsistencies in link table, check SAP Note 974504 -

Inconsistencies in link tables of master data sync.

9. Continued
T-code CVI_PRECHECK_UPGRADE
Report PRECHECK_UPGRADATION_REPORT
results
▫ Double click to see the detailed messages.
Resolve the errors and run report MDS_LOAD_COCKPIT

until all customers/vendors/contact person are converted
to BP.

CVI Conversion – ERP to S/4HANA Conversion
Handover from
Select

Test
Task:
• ERP to S/4HANA technical conversionprocess
must be executed
according to the
S/4 Conversion guide
The Conversion step to be executed by the technical team is part
of the system conversion from the ERP system to S/4HANA On-
Premise. No additional CVI action is required during this process.
ERP S/4 HANA

CVI Conversion – Post Processing
Handover from
Select

Test
Task:
• Activation of
direction BP ->Customer /Vendor
• BP and Customer/Vendor Customizing must be consistent
including field attributes
For Post Processing tasks, follow Best Practice Building Block

J61 from Section 3.4.19. Configure the system accordingly if it
is not already done. Follow the link to get the latest version.
Note: Best Practice
are shown in J61. If a
project is not based on
Best Practice, use those
ERP S/4 HANA as reference only.

S/4HANA CVI Transformation
How much time will that require?
§ Total transformation time
– The total CVI transformation time depends on different factors, such as

- BP/CVI/Pre-Check Know-How
- Customer/Vendor/BP number ranges complexity
- Customizing consistency between BP and Customer/Vendor including field attributes
- Customer/Vendor/Business Partner Data consistency and quality
This can be a very long process if the master data needs cleansing, e.g., updating phone numbers/email address, tax code, etc. could be
very time consuming
- Customer/Vendor Enhancements (Extensions)
- Data volume

Agenda

§ Lessons Learned

Impact on Custom Code and Interfaces
– There is no impact on custom code - no custom code call to old transaction need to be adapted, they are
automatically re-directed.
– The ECC corresponding customer/vendor master data table fields are populated in S/4HANA via BP to
Customer/Vendor CVI.
– Any interface for creating/updating customer or vendor master data has to call CVI_EI_INBOUND_MAIN.
– OData API Service (SAP API Hub) is available for create, read, update, and delete Business Partners,
Suppliers, and Customers in SAP S/4HANA system. Delete the Suppliers and Customers here means
marking them for deletion.

S/4HANA Business Partner Approach: Public Interfaces
§ Public and supported CVI/BP Interfaces

– Migration Note 2287723
▫ SAP Migration Cockpit
▫ SAP Rapid Data Migration (Data Services)
▫ Legacy System Migration Workbench (LSMW) is not supported anymore in S/4HANA
– Creation of Business Partner with Customer and Supplier Roles Note 2417298
▫ IDOCS
- CREMAS
- DEBMAS
▫ Webservice
- BusinessPartnerSUITEBulkReplicateRequest
- BusinessPartnerRelationshipSUITEBulkReplicateRequest
▫ API see above Note
– Data Model mapping and related services see attachments of Note 2221398

Agenda

§ Lessons Learned
§ Q&A

Impact on Surrounding Systems
§ The following interfaces for business partners still work in S/4HANA side-by-side implementation
– CIF interface for business partner, e.g., SCM-EWM, TM
– Middleware for BP synchronization, e.g., CRM
– BW report on customers and vendors
Note: DO NOT use RFC_CVI_EI_INBOUND_MAIN for replicating BP to S/4HANA system, instead use the
tools provided in SAP Note 2417298, see next page.

Agenda

§ Lessons Learned
§ Q&A

Lessons Learned Overview
– General learnings
▫ Until today every conversion had its own challenges concerning customer data
▫ Business Partner and technical expertise required
▫ Conversion Guide, Simplification List, Enhancement cookbook should be known
▫ Number Range assignment is veryimportant
▫ BP/CVI enhancement can be complex andtime-consuming
▫ Start CVI conversion test run in a sandbox with production data as early as possible.
▫ Always have the latest version of SAP Note "2211312" and "2216176“
▫ Business Functions 'VENDOR_SFWS_SC1' and switch 'VENDOR_SFWS_SC2' should have the global status as “On”
after activation

Agenda

§ CVI process – How to Convert in the Different S/4HANA Transition Scenarios (Greenfield vs. Conversion)
§ Lessons Learned

CVI Conversion Approach and Consideration
CVI Conversion Approach Targets
Ø No downtime
Ø Not in a critical path in the S/4HANA conversion process
Ø No last minute surprise in effort or time
Example of Low Impact CVI ConversionApproach
1. Perform CVI conversion in a sandbox with production data at early stage of the S/4HANA project.
Identify all data errors before the production CVI conversion and decide the error resolution.
Certain master data errors may need custom program to make corrections. If the errors have no impact on
the business process, workaround measures could be implemented via configuration to relax the data
validation.
2. Assess the CVI conversion processing time from test results of sandbox
If the required conversion time is long and likely to impact the S/4HANA conversion schedule, the CVI
conversion could be done in advance according to the steps below.

CVI Conversion Approach and Consideration
Example of Low Impact CVI Conversion Approach - continued
a. Configure CVI in ECC system for the synchronization for the customer/vendor-to-BP direction ONLY in the
production environment.
b. Complete the CVI conversion process preferably during a low system usage time.
c. The users will continue to use the ECC customer/vendor maintenance transaction to create the
customer/vendor master data before the S/4HANA conversion, and the CVI will create the business partners
in background.
d. Lock the BP transaction in the ECC system to prevent usage of BP transaction before converting the ERP
system to S/4HANA.
e. Convert the ERP system to S/4HANA.
f. Activate the CVI in the BP-to-Customer/Vendor direction in the S/4HANA system. BP and Customer/Vendor
Customizing must be consistent including field attributes

Agenda

§ CVI process – How to Convert in the Different S/4HANA Transition Scenarios (Greenfield vs. Conversion)
§ Lessons Learned

Additional Features and Information
1. Customer Classification is available as of S/4HANA 1610, and 1511

FPS02 with Note 2326148 application.
2. Contact Person could be created via CoPilot and Quickview "Create

Contact"
3. Consumer conversion from ERP to S/4HANA is possible
4. One-time-customers/one-time-suppliers conversion from ERP to

S/4HANA is possible

Other simplifications
Storage Location MRP (context)
Business Context
» In SAP ERP, storage locations can be excluded from MRP planning or they can be planned separately from other
storage locations. In the latter case a reorder point procedure with maximum lot size is used which triggers transport
reservations to fill up the storage location.
» MRP areas cover the very same business requirements. Materials with MRP-area-specific MRP type 'ND' (no MRP)
can be used instead of materials with a storage location excluded from MRP. Materials with MRP-area-specific MRP
type 'VB' (reorder point planning) can be used instead of materials with separately planned storage locations.
» The storage location functionality is a subset of the MRP areas capabilities.
Impacted processes
» Storage Location MRP is not available in SAP S/4HANA, on-premise edition 1511. Planning on MRP area level has
to be used instead.
Refer SAP Note 2268045 - S4TWL - Storage Location MRP

Plan to Product – Storage Location MRP
SAP ERP 6.0 SAP S/4HANA

Storage Location MRP (actions)
Required actions
» Conversion Pre-Checks raise an error if storage location MRP is used in the source ERP system.
» Run report MRP_AREA_STORAGE_LOC_MIGRATION if the pre-checks detect that storage location MRP is used.
» The report first checks some prerequisites like MRP types, lot-sizing procedures, and MRP areas in
customizing. If the required customizing entries are missing, you have to create them manually. Follow the
instructions provided by the report.
» If all prerequisites are fulfilled, then the report generates material master records for planning on MRP area
level using the storage location material records. After the report was performed, planning is done on MRP area
level, also if MRP is performed on the start release.
Refer SAP Note 2216528 - Pre-upgrade check for storage location migration report

Material Number Field Length Extension (context)
Refer SAP Note 2267140 - S4TWL - Material Number Field Length Extension

Material Number Field Length Extension (impact)
Impact on custom code

» Pre-check executed with program MFLE_CLS4H_CHECKS_CC from
note 2216958 that is included in the preparation steps you
will have to execute during this work package.

International Trade Management
SAP Condition Contract Settlement

SAP S/4HANA Sales: solution simplification
• Business Partner approach replaces ERP SD customer master (SAP Note2265093).
• S/4HANA Finance Credit Management replaces ERP SD Credit Management (SAP Note 2270544)
• S/4HANA International Trade Management functionality replaces ERP SD Foreign Trade (SD-FT) (SAP Note
2223144)
• Migration of Financial Documents from SD-FT to Trade Finance in Treasury and Risk Management SAP Note
2520879
• SAP Condition Contract Settlement replaces ERP SD Rebates (SD-BIL-RB) (SAP Note 2267377)
• SAP Revenue Accounting replaces ERP SD Revenue Recognition (SD-BIL-RR) (SAP Note 2267342)
• Optional: SAP S/4HANA new Output Management (SAP Note 2228611)
• SAP S/4HANA Analytics approach – ODATA and Open CDS view replaces ERP LIS/ODP (SAP Note
2228056)
• Pricing data model changes (SAP Note 2267442)

• Custom code check for deprecated SD transactions and BAPIs (SAP Note 2228098)
• Optimize parallel execution of conversion reports for SD, reduce downtime (SAP Note2353814)
• SAP C/4HANA and SAP S/4HANA offer a holistic customer experience.

SAP ERP Foreign Trade is being replaced in S/4HANA
Foreign trade functionality (SAP components: SD-FT and MM-FT) has not been carried forward
natively in SAP S/4HANA Enterprise but is being replaced by new functionality.
The foreign trade functionality of SAP ERP included the following areas:
• Intrastat
• Preference Handling
• Documentary Payment (e.g. letter of credit) *
• Export Compliance
Customers previously using SAP ERP Foreign Trade will now have options to enable needed
functionality as they transition to an S/4HANAenvironment:
1. SAP S/4HANA for international trade (on-premise or cloud edition)
2. SAP Global Trade Services (can be used on-premise, HEC, or PMC) **
* Documentary Payment (e.g. letter of credit) functionality is planned be handled via SAP Treasury Management.
** Under discussion: S/4HANA customer may use SAP GTS Preference Management with S/4HANA EMlicense.
SAP S/4HANA International Trade & Letter of Credit
Letter of Credit (advanced function*)

Accounting of Letter of Credit
• SWIFT Integration
• Presentations (including master data for presentations)
FINANCIAL RISK
MANAGEMENT* • Payments
• Conditions (Interests and Fees)
Products* • Integration to Credit and Market Risk Analyzers
• Integration to Credit Lines / Facilities
Letter of Credit (basic function) Classification and reclassification for

functional parity to ERP SD-FT Letter of Credit: • Commodity Codes
Basic master data for Letter of Credit • Intrastat Service Codes
• Letter of Credit master data document management • Legal Control Attributes
• Nominal amount • Customer Tariff Numbers New 1809
INTERNATIONAL • Integrated with sales processing • Load data from external data provider for commodity codes New 1809
TRADE • Assign a letter of credit as payment guarantee to sales Intrastat reporting for 26 countries
MANAGEMENT documents Embargo
Enterprise • Block sales and delivery documents if not complied with terms • Export, based on sales order and outbound delivery
Management in letter of credit • Import, based on purchase order New 1809

• Risk check decisions
• Recheck, release or reject the blocked documents Legal control
• SAP ERP data can be migrated to SAP S/4HANA • Export, based on sales order and outbound delivery
• Import, based on purchase order New 1809
• Manage legal control rules for white-and blacklisting
Integration with SAP GTS
• Broader international trade function via native integration with
SAP GTS**
Preference management – side by side using SAP Global Trade Services

Condition contract settlement by settlement management
SAP S/4HANA settlement management (SAP Note 2481672)

uses Central Contract Administration as the single point of entry for contract data and contract related conditions for
• Full support of business volume related scenarios
• Calendar based settlement
• Accrual conditions can be defined independent from settlement conditions
• Intuitive data entry of settlement information with full transparence of involveddocuments
Monitor Create Source

Create Condition Condition Doc. /Biz Create Monitor
Contract Contract Volume Settlement Settlement Doc.

Closure and Call to action
The system landscape for 10Steps2S4
The source system

SAP ECC 6.0 EhP 6
SID: K<XX> (e.g. K01)
Main usage: your Business System to

be converted to S/4HANA
Activities:
• Business Partner customization
• Customer Vendor Integration
• Storage locations for MRP
• Checks for long MATNR

Call to action
• Review this presentation (published in JAM group)
• Execute the activity document for

• Customer Vendor Integration
• Business Partners approach
• Storage locations MRP
• Collaborate using JAM in case of issues or doubts

Q&A
Ask your questions
via Chat or
via Phone:
• Unmute your line with *6
• Ask your question verbally

Thank you.
Contact information:
SAP 10Steps2S4 Team
JAM JAM: 10Steps2S4 APJ - MAY 2019
Mail: [email protected]

Work-Package - 03 - May 2019

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Work-Package - 03 - May 2019

Uploaded by

Document Information

Original Title

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

Work-Package - 03 - May 2019

Uploaded by

Copyright:

Available Formats

10Steps2S4: Logistic preparation activities

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 2

Partner additional effort 5 – 6 hours 3 – 4 hours 5 – 6 hours 3 – 4 hours 1 hour

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 3

• Review of previous work-package

• Logistic preparation activities

• Business Partners with Customer Vendor Integration

• International Trade / Settlement Processing

• Closure and Call to Action!

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

Connect to the landscape

Custom Code checks

Pre checks with Simplification Item-Check

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

1. Prepare source system

2. Execute program SAP Readiness Check

3. Explore results to start Conversion project

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

Ø The Planning tool (successor for MOpz)

Ø Preparations for Conversion: Check and Plan

Ø Checking Source System

Ø Planning for Conversion

Ø Un-installation of AddOns can be planned now;

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

3) Install the Simplification Database on the Checked Checked Checked

5) Analyze the ATC result list

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

Preparation phase Realization phase

Maintenance Software Update AAppppliccaatioonnssppeeccifficc

Customer-specific Simplification List

§ S/4HANA & CVI – Context and Motivation

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

§ S/4HANA & CVI – Context and Motivation

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

Customer/Vendor Object Model Limitations

Business Partner – SAP Strategic Object Model

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

Business Partner Concept Usage

Company Code data

CVI Complex Interface Maintenance Process

Business Partner creation is the first step in the creation of

Get Technically, the Customer-Vendor-Integration (CVI) takes care of

Partially, the data of the Business Partner and

While saving all Business Partner and Customer/Supplier data

Distribution of Business Partner is provided by Idocs/SOA

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

KNA1 CVI_CUST_LINK BUT000 CVI_VEND_LINK LFA1

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

Person Bank Details Purchasing

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

§ S/4HANA & CVI – Context and Motivation

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

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

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

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

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

§ S/4HANA & CVI – Context and motivation

§ Archiving Customer Data Procedure available here.

§ Archiving Vendor Data Procedure available here.