Data Loading...
S4Hana BP Conversion Flipbook PDF
S4Hana BP Conversion
1,343 Views
417 Downloads
FLIP PDF 1.88MB
SAP S/4HANA - Business Partner & Customer Vendor Integration Chelliah Soundar SAP S/4HANA RIG July 2018
PUBLIC
Disclaimer 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 noninfringement. 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.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Agenda § Business Partner & Customer Vendor Integration – BP & CVI in S/4HANA – Introduction – CVI Conversion process – Impact on Custom Code and Interfaces – Lessons Learned – CVI Conversion Approach and Recommendation – Additional Information
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
3
Agenda
§ Business Partner & Customer Vendor Integration – BP & CVI in S/4HANA – Introduction – CVI Conversion Process – Impact on Custom Code and Interfaces – Lessons Learned – CVI Conversion Approach and Recommendation – Additional Information
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
S/4HANA - Business Partner
Harmonized architecture across applications
Strategic object model in SAP S/4HANA
BP Categories – Organization, Person, Group
Relationships between BPs (“Is Contact Person For”, “Is Service Provider For”
Business Partner
Multiple roles such as customer, vendor
Multiple addresses
General data shared across different roles
Time dependent addresses, bank data, relationships
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
5
S/4HANA – Customer Vendor Integration (CVI) – CVI must be implemented for using Business Partner as the leading object in S/4HANA – SAP supports the conversion of existing ERP Customers and Vendors to Business Partner using guided procedures and reports prior to system conversion – CVI ensures that Customer and Vendor tables (KNxx / LFxx) are updated automatically after a BP is created/changed in S/4HANA – The CVI component ensures the synchronization between the Business Partner object and the Customer/Vendor objects in S/4HANA
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
6
S/4HANA – CVI Process Company Code data Sales Area. data Central CentralData* Data
Maintenance Process
CVI Complex Interface
Business Partner
Vendor
Customer
Business Partner creation is the first step in the creation of Customers and Suppliers. Customer / Vendor Data Buffer
BP APIs
Technically, the Customer-Vendor-Integration (CVI) takes care of the general Business Partner data as well as the Customer and Supplier specific data.
Get
CVI
SAVE
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 APIs
Vendor 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 Partner
CVI Link Tables
Customer
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Vendor (Supplier)
7
Simplified Business Partner Data Model Vendor Data
Business Partner Data Business Partner Organization
Address Data
Central Data
General Data
Roles
Company Code Data
Phone
Purchasing Org. Data
Fax
Person
Bank Details
Group
Identification Numbers
Customer Data
Tax Numbers
Address
Email URL
General Data
Industry Sectors
Company Code Data
Relationships Contact Partners
Sales Org. Data
Address Address Usages ERP Vendors ERP Customers
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
BP & CVI in S/4HANA – Business Impact
SAP ERP
CVI Implementation
Convert Data
Continue to use Customer / Vendor transactions
SAP S/4HANA Use of BP transaction is not recommended
Only transaction BP is used
Transactions VA01, ME21N, etc will still require customer / vendor numbers
XD01, XD02, etc.
Customer
Leading Object Vendor Contact Person
BP
Business Partner XK01, XK02, etc. Roles Customer Vendor Contact Person
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
BP & CVI in S/4HANA – Business Impact § ERP transactions that are no longer available or redirected to transaction BP: – FD01, FD02, FD03, FD05, FD06 FK01, FK02, FK03, FK05, FK06 MAP1, MAP2, MAP3 MK01, MK02, MK03, MK05, MK06, MK12, MK18, MK19 V-03, V-04, V-05, V-06, V-07, V-08, V-09, V-11, V+21, V+22, V+23 VAP1, VAP2, VAP3 VD01, VD02, VD03, VD05, VD06 XD01, XD02, XD03, XD05, XD06, XD07 XK01, XK02, XK03, XK05, XK06, XK07
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Agenda
§ Business Partner & Customer Vendor Integration – BP & CVI in S/4HANA – Introduction – CVI Conversion Process – Impact on Custom Code and Interfaces – Lessons Learned – CVI Conversion Approach and Recommendation – Additional Information
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
CVI Conversion Process Preparation
- Activate BF - CVI Configuration
Synchronization
- Pre-check reports
- Synchronization Cockpit - Completion Check
Post Processing / Test
Conversion
- Pre-Check - SUM
- Activate BP->Cust/Vendor
Test
Precondition: ERP release level needs to be at SAP ERP 6.0, EhP 0-8. Consultants are involved in the transformation activities
Application contacts are involved in the transformation activities
Greenfield implementation - Only Post Processing/Test step is required, follow Best Practice Building Block J61 ERP © 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
S/4 HANA
If your system is at EhP 0 4 and vendor contact person is used, apply SAP Note 2383051 – Development of vendor contact person mapping to business partner Note: Best Practice configuration parameters are shown in J61. If a project is not based on Best Practice, use those configuration parameters as reference only. 12
CVI Conversion - Preparation Synchronization
Preparation
- Activate BF - CVI Configuration
- Pre-check Reports
- Synchronization Cockpit - Completion Check
Conversion
- Pre-Check - SUM
Post Processing / Test
- Activate BP->Cust/Vendor
Test
Task: • Archive Customer/Vendor data with deletion flag (optional) • Activate Business Functions • Check and integrate enhancements • Implement Check Reports • Check and adjust CVI/BP Customizing • Run Pre-Conversion Checks
ERP © 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
S/4 HANA 13
CVI Conversion – Preparation Business Function Activation Activate Business Functions – CA_SUPPLIER_SOA – CA_BP_SOA Switches VENDOR_SFWS_SC1 and VENDOR_SFWS_SC2 have to be active for the vendor contact person data to be synchronized with BP contact persons and make sure that the switches have “Global status” as On. See SAP Note 1454441 - Development of contact person for vendors. –
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
14
CVI Conversion – Preparation Check and Integrate Customer/Vendor Enhancement To include customer-specific Customer/Vendor fields in transaction BP, it is necessary to integrate these additional fields in the Business Partner and CVI. 2309153 - BP_CVI: Guideline Version 1.14 for customer enhancements in CVI (customer/vendor integration) in SAP S/4HANA releases 1623809 - Developer documentation for the XO framework 2295823 - BP_CVI: Transfer of customer / vendor fields to the business partner - template source code Implement check reports: ▫ 2216176 - Precheck report from business partner (PRECHECK_UPGRADATION_REPORT) ▫ 1623677 - BP_CVI: Check report for checking CVI Customizing (CVI_FS_CHECK_CUSTOMIZING) ▫ 974504 - Inconsistencies in link tables of master data sync.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
15
CVI Conversion – Preparation Customizing Tasks
1. Activate the PPO Request for the synchronization object Business Partner IMG Path
Cross-Application Components -> Master Data Synchronization -> Synchronization Control -> Synchronization Control-> Activate PPO Requests for Platform Objects in the Dialog
2. Activate Synchronization between Customer/Vendor and BP IMG Path
Cross-Application Components -> Master Data Synchronization -> Synchronization Control -> Synchronization Control-> Activate Synchronization Options
3. Activate Creation of Post processing Orders (PPO) for component AP-MD IMG Path
Cross-Application Components -> General Application Functions -> Postprocessing Office -> Business Processes->Activate Creation of Postprocessing Orders
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
16
CVI Conversion – Preparation Customizing Tasks Number Range
Recommendation
4. If Customer and Vendor number ranges are not overlapping
4. The business partner number ranges could be the same as the customer and vendor number ranges.
5. If Customer and Vendor number ranges are overlapping
5. Maintain the business partner number range in such a way that the most numbers from customer or vendor stay unchanged.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
17
CVI Conversion – Preparation Customizing Tasks 6. 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”.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
18
CVI Conversion – Preparation BAdI Implementation 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. During the CVI conversion process, it is possible to create a BP in different category e.g. person instead of 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. 2539457 - CVI and employee vendors in wrong BP category 2542175 - CVI and reuse of existing employee business partner
IMG Path
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings ->Business Add-Ins (BAdIs)
BAdI Definition
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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
19
CVI Conversion – Preparation One BP for both Customer and Vendor If the scenario where a single legal entity is represented in the ERP system as both customer and vendor, please refer to SAP Note 2363892. This note enables creation of a single BP with both customer and vendor roles. The MDS_LOAD_COCKPIT report converts such customers and the vendors to a single BP if Note 2363892 is applied and its restrictions are met. Otherwise, the customer or the vendor could be converted to a BP first. The remaining customer or vendor is linked to the BP via transaction FLBPD2 or FLBPC2, see Note 954816. The transaction can only create one BP role, e.g., FLVN00 or FLVN01. Often the customer and vendor used for intercompany sales or plant-to-plant stock transport order (STO) have the same number assigned.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
20
CVI Conversion – Preparation Mapping Tasks 1. BP roles are assigned to account groups 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)
2. For every customer/vendor account group a BP Grouping must be available
Customer Vendor
Customer Vendor
IMG Path
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration -> Define BP Role for Direction Customer to BP
IMG Path
IMG Path
…-> Settings for Vendor Integration -> Define BP Role for Direction Vendor to BP
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration -> Field Assignment for Customer Integration -> Assign Keys ->Define Number Assignment for Direction Customer to BP
IMG Path
…-> Settings for Vendor Integration -> Field Assignment for Vendor Integration -> Assign Keys ->Define Number Assignment for Direction Vendor to BP
NOTE: The screenshot field values in this document are for reference ONLY
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
21
CVI Conversion – Preparation Mapping Tasks 3. Attribute Assignment 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 4. Attribute Assignment for Customer a. Assign Marital Statuses b. Assign Legal Form to Legal Status c. Assign Payment Cards d. Assign Industries
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
22
CVI Conversion – Preparation Mapping Tasks 3. Attribute Assignment for Contact Person a. Activate Assignment of Contact Persons
IMG Path
IMG Path
b. Assign Department Numbers for Contact Person
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes->Contact Person-> Activate Assignment of Contact Persons
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes->Contact Person-> Assign Department Numbers for Contact Person
23
CVI Conversion – Preparation Mapping Tasks 3. Attribute Assignment for Contact Person c. Assign Functions of Contact Person
d. Assign Authority of Contact Person
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
IMG Path
IMG Path
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes->Contact Person-> Assign Functions of Contact Person
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes->Contact Person-> Assign Authority of Contact Person
24
CVI Conversion – Preparation Mapping Tasks 3. Attribute Assignment for Contact Person e. Assign VIP Indicator for Contact Person
4. Attribute Assignment for Customer a. Assign Marital Statuses
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
IMG Path
IMG Path
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes->Contact Person-> Assign VIP Indicator for Contact Person
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes-> Assign Marital Statuses
25
CVI Conversion – Preparation Mapping Tasks IMG Path
4. Attribute Assignment for Customer b. Assign Legal Form to Legal Status
c. Assign Payment Cards
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
IMG Path
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes-> Assign Legal Form to Legal Status
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes-> Assign Payment Cards
26
CVI Conversion – Preparation Mapping Tasks 4. Attribute Assignment for Customer d. Assign Industries Industry assignment for customer and vendor share the same configuration table.
IMG Path
IMG Path
Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration ->Field Assignment for Customer Integration>Assign Attributes-> Assign Industries Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Vendor Integration -> Field Assignment for Vendor Integration->Assign Attributes-> Assign Industries
Define outbound industry mapping means BP to Customer/Vendor mapping. Define inbound industry mapping means Customer/Vendor to BP mapping.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
27
CVI Conversion – Preparation Customizing Check Report Run CVI Customizing Check Report CVI_FS_CHECK_CUSTOMIZING This 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. This report checks the customizing required for CVI and displays any errors/missing configuration. Adjust the configuration if necessary
SAP Note: 1623677 - BP_CVI: Check report for checking CVI Customizing
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
28
CVI Conversion – Preparation Mapping Check Report Run pre-check report PRECHECK_UPGRADATION_REPORT to check and confirm if all the necessary CVI mappings are done. This report checks the following before converting the customer/vendor to BP: ▫ BP roles are assigned to account groups ▫ Every account group is mapped to a BP group ▫ Customer attribute value mapping ▫ Vendor attribute value mapping
▫ CVI Link, 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. If there are errors, double click the red lights to see the detailed messages and correct the errors
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
29
CVI Conversion - Synchronization Handover from Preparation Select - Activate BF - CVI Configuration
Synchronization
- Pre-check Reports
- Synchronization Cockpit - Completion check
Post Processing / Test
Conversion
- Pre-Check - SUM
- Activate BP->Cust/Vendor
Test
Task: • Run MDS_LOAD_COCKPIT • Run PRECHECK_UPGRADATION_REPORT
ERP © 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
S/4 HANA 30
CVI Conversion – Synchronization
1. Run report MDS_LOAD_COCKPIT 2. Double click the desired synchronization Process Customer à Business Partner or Vendor à Business Partner 3. Filter the customer/vendor by account group or by numbers. To facilitate error analysis, run a small batch initially by selecting 10 to 50 customers or vendors. 4. Execute the report 5. It creates a corresponding BP for the customer, vendor and contact person.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
31
CVI Conversion – Synchronization
5. If there are errors, 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 errors from the PPO screen or fix the errors outside PPO. See Synchronization Cockpit help document for more information. 8. Correct all master data errors and re-run the report to complete the conversion of customers/vendors/contact persons.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
32
CVI Conversion – Synchronization Mapping Check Report Run 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. Double click the red lights to see the detailed messages and resolve the errors Re-run MDS_LOAD_COCKPIT until all customers/vendors/contact person are converted to BP.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
33
CVI Conversion – ERP to S/4HANA Conversion Synchronization
Preparation
- Activate BF - CVI Configuration
- Pre-check Reports
- Synchronization Cockpit - Completion check
Conversion
- Pre-Check - SUM
Post Processing / Test
- Activate BP->Cust/Vendor
Test
Task: • System conversion from SAP ERP to SAP S/4HANA is completed • No additional CVI related activities are required during this process.
ERP © 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
S/4 HANA 34
CVI Conversion – Post Processing Preparation
- Activate BF - CVI Configuration
- Pre-check Reports
Synchronization
Conversion
- Synchronization Cockpit - Completion check
- Pre-Check - SUM
Post Processing / Test
- Activate BP->Cust/Vendor
Test
Task: • Activate synchronization direction BP ->Customer / Vendor • BP and Customer/Vendor Customizing must be consistent including field attributes • For Post Processing tasks, you may use Best Practice Building Block J61. If a project is not based on Best Practice, use those configuration parameters as reference only. • Complete testing
ERP © 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
S/4 HANA 35
Agenda
§ Business Partner & Customer Vendor Integration – BP & CVI in S/4HANA – Introduction – CVI Conversion Process – Impact on Custom Code and Interfaces – Lessons Learned – CVI Conversion Approach and Recommendation – Additional Information
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
36
Impact on Custom Code and Interfaces
– There is limited impact on custom code.
▫ Custom code calls to old transactions generally need not be adapted, they are automatically re-directed to the proper ▫
transaction. However, the Call Transaction statement or Batch Input will not work with old transactions
– The API CL_MD_BP_MAINTAIN is used to create business partners in the same system – To integrate BP/Customer/Supplier master data across different systems, IDOCs or SOA Service can be used. (SAP Note 2417298) – 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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
37
Agenda
§ Business Partner & Customer Vendor Integration – BP & CVI in S/4HANA – Introduction – CVI Conversion Process – Impact on Custom Code and Interfaces – Lessons Learned – CVI Conversion Approach and Recommendation – Additional Information
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
38
S/4HANA CVI Conversion How much time do you need? – The total CVI transformation time depends on different factors, such as - 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 - One customer or vendor could have multiple errors - Customer/Vendor Enhancements (Extensions) - Data volume - Master Data/CVI/Pre-Check Knowledge
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
39
S/4HANA CVI Conversion Lessons Learned – Customizing/Master Data issues Customizing issues (missing or incomplete customizing) •
Tax number categories
•
Industries
•
Address forms
•
Departments
•
Legal forms
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Master Data quality issues •
Wrong format for dates, tax codes, trading partners, bank keys, bank account numbers, postal code, bank control key
•
Missing / non existing links (e.g. customer vendor)
•
Non existing TAX and VAT values, bank numbers
•
Missing links to ADRC table
40
S/4HANA CVI Conversion Lessons Learned – Number range Scenario: Current sold-to, ship-to, bill-to and payer customers have different number ranges and reduced data input fields, and want to keep the same number ranges in BP Root cause: • Business requirement How to resolve: 1. Define the same number ranges in BP. 2. Create BP Grouping for each customer account group, and assign the corresponding number range. 3. Map the customer account groups to the BP groupings between customer and BP 4. Create new BP roles for each account group if reduced data fields are used for the account groups 5. Assign the customer account groups to their corresponding BP roles
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
41
S/4HANA CVI Conversion Lessons Learned – Configuration Issue Error: Tax number category doesn’t exist Root Cause: Missing tax number category entries in table TFKTAXNUMTYPE / view V_TFKTAXNUMTYPE How to resolve: Call the view V_TFKTAXNUMTYPE with transaction SM30, and add the missing Tax Number Category Then maintain customizing at SPRO -> CrossApplication Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Tax Numbers -> Maintain Tax Number Categories
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
42
S/4HANA CVI Conversion Lessons Learned – Master Data quality issue Error: Message No. BF00210 - Bank xxxxxx marked for deletion in country US Root cause: • System message is defaulted as error How to resolve: • Switch off the error message if acceptable to the business Tcode - OBA5, Application area = BF00 Change “E” to “–” for the Online and Batch input settings.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
43
S/4HANA CVI Conversion Lessons Learned – Master Data quality issues Miscellaneous Master Data Errors Root cause: •
Human error in data entry
How to resolve: •
Change master data manually or via tools
•
If the customer accepts the existing data quality due to time or resource constrain, and the check of the error is configuration, bypass check via configuration could be considered as a short term remedy so that S/4HANA conversion could start according to schedule. The data errors have to be fixed and the data error check is restored before go-live.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Customer Conversion Error Message No. AM129 AR102 AR103 AR104 AR129 AR191 AR196 BF00211 FSBP_FS_ATTRIBUTES015 GEOCODING002 R1286 R11124 T5002
Message The transport zone xxxxxx is not defined for country xx VAT Reg.No. xxxxxxxxxxx must have length 12 VAT Reg.No. xxxxxxxxxxxxx is longer than 12 characters Bank Key AAA must contain only numbers Tax code n is not valid ISO code XX is not correct in the VAT registration number VAT registration number contains invalid characters Bank NO does not exist Company xxx does not exist Geocoder SAP0: Country specification is incomplete (Customizing) Business partner x already exists Business partner with GUID xxxxxx does not exist Telephone/fax code for country code XX is not maintained
Vendor Conversion Error Message No. AR 102 AR 103
Message VAT Reg.No. BE448696957 must have length 12 Tax Code 1 is longer than 16 characters
44
Agenda
§ Business Partner & Customer Vendor Integration – BP & CVI in S/4HANA – Introduction – CVI Conversion Process – Impact on Custom Code and Interfaces – Lessons Learned – CVI Conversion Approach and Recommendation – Additional Information
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
45
S/4HANA CVI Conversion CVI Conversion Approach and Recommendation 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
CVI Conversion Approach – Recommendation • Perform CVI conversion in a sandbox with production data at early stage of the S/4HANA project • Identify/analyze all data errors and strategize/plan error resolution Certain high volume 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 by relaxing data validation. • Assess the CVI conversion processing time from the test results of sandbox • If the estimated conversion time is long and likely to impact the S/4HANA conversion project schedule, the CVI conversion could be done in advance according to the steps provided on the next slide
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
46
S/4HANA CVI Conversion CVI Conversion Approach and Recommendation Recommendation for completing CVI converion in advance of the S/4HANA Conversion Project § Configure CVI in ERP system for the synchronization of customer/vendor-to-BP in the production environment § Complete the CVI conversion process (preparation and synchronization phases as explained in the earlier slides) § The users will continue to use the ERP customer/vendor transactions as usual to create/maintain the customer/vendor master data and the CVI will create the business partners in the background automatically § Lock the BP transaction in the ERP system to prevent usage of BP transaction § (maybe a few months later) Strat S/4HANA Conversion project as scheduled § Convert the ERP system to S/4HANA § Activate the CVI in the BP-to-Customer/Vendor direction in the S/4HANA system § Make sure BP and Customer/Vendor Customizing is consistent including field attributes § Complete the S/4HANA conversion project © 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
47
Agenda
§ Business Partner & Customer Vendor Integration – BP & CVI in S/4HANA – Introduction – CVI Conversion Process – Impact on Custom Code and Interfaces – Lessons Learned – CVI Conversion Approach and Recommendation – Additional Information
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
48
S/4HANA CVI Conversion Additional Information § SAP S/4HANA Cookbook Customer Vendor Integration https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H.0781%20SAP%20S4HANA%20Cookbook%20 Customer%20Vendor%20Integration.pdf § IS Utilities: SAP Note 2344100 - S4TWL - CVI Integration for SAP ISU § Credit Management: SAP Note 2270544 - S4TWL - Credit Management § IS Retail: SAP Note 2310884 - SAP S/4HANA conversion for site master § HCM: SAP Note 2340095 - S4TWL - Conversion of Employees to Business Partners § CRM: SAP Note 2285062 - S4TWL: Business partner data exchange between SAPCRM and S/4 HANA, onpremise edition § Simplification List – TOP Items Business Partner Approach / Customer-Vendor Integration (CVI)
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
49
Thank you. Contact information: Chelliah Soundar SAP S/4HANA Product Expert [email protected]
© 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 platform 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 http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.