Conversion Guide SAP S/4HANA Retail for merchandise management Document Version: 2.1 – 2017-09-25 Site Master Conversion Information SAP ERP to SAP S/4HANA CUSTOMER Typographic Conventions Type Style Description Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. 2 Example Emphasized words or expressions. EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R . CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Typographic Conventions Document History Version Date Change 1.0 2016-10-31 Initial version 1.1 2017-02-22 Updated descriptions and process enhancements introduced with SAP Notes and SAP S/4HANA 1610 Feature Package Stack 01. For more information, see 1.4 Important Updates. 1.2 2017-05-10 Updated descriptions and process enhancements introduced with SAP Notes and SAP S/4HANA 1610 Feature Package Stack 02. For more information, see 1.4 Important Updates 1.3 2017-06-28 Updated information about BP distribution. For more information, see 1.4 Important Updates 2.0 2017-09-15 Updated descriptions and process enhancements introduced with SAP S/4HANA 1709. For more information, see 1.4 Important Updates 2.1 2017-09-25 Site Master Conversion Information Document History Updated SAP Note 2502552 and the check report for the site migration CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 3 Contents 1 1.1 1.2 1.3 1.4 About This Document ............................................................................................................. 6 Target Users........................................................................................................................................... 6 Notes on Terminology Usage ............................................................................................................... 6 Related Information............................................................................................................................... 7 Important Updates ................................................................................................................................ 8 2 2.1 Business Partner Approach (Customer/Vendor Integration) in SAP S/4HANA ............... 10 Impact of the Business Partner Approach on Site Master .............................................................. 10 3 3.1 SAP S/4HANA Conversion .................................................................................................... 12 Preparing for Conversion .....................................................................................................................12 3.1.1 BP Conversion and Preparation for Conversion to SAP S/4HANA (Independent of Site) .......................................................................................................................................12 3.1.2 Preparing for Site Migration ................................................................................................12 Conversion ............................................................................................................................................ 17 3.2.1 Pre-Check ............................................................................................................................. 17 3.2.2 XPRAs....................................................................................................................................18 3.2.3 Site Migration Report...........................................................................................................19 Preparing Operations after Conversion..............................................................................................21 3.3.1 Resolving Site Conversion Issues .......................................................................................21 3.3.2 Additional Customizing for Sites ....................................................................................... 22 Conversion of Distributed System Landscapes ............................................................................... 22 3.4.1 BP Numbering ..................................................................................................................... 23 3.4.2 Phased Conversion to SAP S/4HANA .............................................................................. 23 3.2 3.3 3.4 4 4.1 4.2 4.3 4.4 4 Post-Conversion Operations ................................................................................................ 24 Customizing ......................................................................................................................................... 24 4.1.1 Site Profile............................................................................................................................ 24 4.1.2 Enable Standard Customer/Vendor As a Source for Site Update ................................. 25 4.1.3 Maintain Tables for Plant Transport.................................................................................. 25 4.1.4 Departments........................................................................................................................ 25 4.1.5 Customizing Activities for DRF .......................................................................................... 25 4.1.6 Delivery Customizing .......................................................................................................... 26 Site Maintenance ................................................................................................................................. 29 4.2.1 Integrated BP Maintenance ............................................................................................... 29 4.2.2 Address Display....................................................................................................................31 4.2.3 Maintenance of Departments and Receiving Points ........................................................ 32 4.2.4 Maintenance of Additional Addresses and Geolocation Data ......................................... 32 BP Maintenance ................................................................................................................................... 32 4.3.1 Time-Dependent Address Data ......................................................................................... 33 4.3.2 C/V Enhancements............................................................................................................. 33 Site Distribution ................................................................................................................................... 33 4.4.1 Distribution Modes.............................................................................................................. 34 4.4.2 Distribution Scenarios ........................................................................................................ 36 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Contents 4.5 4.4.3 Control of Site Distribution ................................................................................................. 41 4.4.4 BP Distribution.....................................................................................................................42 Site Archiving .......................................................................................................................................43 Site Master Conversion Information Contents CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 5 1 About This Document This guide describes the steps necessary for the migration of site master data from SAP ERP to SAP S/4HANA. It describes the process of conversion to an on-premise deployment of SAP S/4HANA and the impact of the business partner approach on operations that involve site master data. 1.1 Target Users Consultants, partners, and customers 1.2 Notes on Terminology Usage The following terms and abbreviations are used in this document: Term and/or Abbreviation Usage SAP ERP Enterprise resource planning (ERP) software developed by SAP SE. SAP ERP incorporates the key business functions of an organization. The latest version is SAP ERP 6.0. SAP S/4HANA SAP's next-generation real-time enterprise resource planning solution for digital business. Built on an advanced in-memory platform, SAP HANA and offers a personalized, consumergrade user experience with SAP Fiori. In this document, SAP S/4HANA refers to an onpremise deployment only. site An organizational unit used to document goods stored in distribution centers and stores for the purposes of inventory management and to model the associated business processes, such as goods receipt, physical inventory, and goods issue. In the context of SAP Retail as part of SAP ERP and SAP S/4HANA, site is a synonym for plant. 6 plant In the context of SAP Retail as part of SAP ERP and SAP S/4HANA, plant is a synonym for site. vendor (V) A business partner from whom materials or services can be procured. CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information About This Document Term and/or Abbreviation Usage In the context of SAP Retail as part of SAP ERP and SAP S/4HANA, vendor is a synonym for supplier. customer (C) A business partner with whom a business relationship exists, involving the issue of goods or services. supplier A business partner from whom materials or services can be procured. In the context of SAP Retail as part of SAP ERP and SAP S/4HANA, supplier is a synonym for vendor. business partner (BP) A person, organization, group of persons, or group of organizations in which a company has a business interest. This can also be a person, organization or group within this company. Customer/Vendor Integration (CVI) The assignment of a customer and/or vendor (supplier) to a business partner. C/V customer and vendor pre-check Checks used to identify the required steps for conversion and make sure that the system is compatible for the conversion process. XPRA Stands for eXecution of PRogram After import. An XPRA report is a report executed during an upgrade or during the conversion process in a customer system. 1.3 Related Information Document Checks Performed in the PreCheck Phase Available at Comment SAP Note 2310884 Detailed descriptions of all checks performed by the precheck https://help.sap.com/s4hana Conversion Guide for SAP S/4HANA Product assistance for SAP S/4HANA Retail for merchandise management Site Master Conversion Information About This Document Choose a version and go to Product Documentation Conversion Guide. https://help.sap.com/s4hana Choose a version and go to Generic information about the SAP S/4HANA conversion process Information about site master data is available under Location Management. CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 7 Document Available at Comment Product Assistance Industries Retail. 1.4 Important Updates Note Minor enhancements of the documentation are not included in the following table. Detailed Change History for Document Version 1.2 Type of Update Description Updated description Consolidation of common C/V data into central BP data. Enhanced process Updated description Chapter in This Document 3.1.2.2 Consolidation of Common C/V Data Available as of Feature Package Stack (FPS) SAP Note n/a 2422132 3.2.3.4 Address Data Address data handling during site migration. Post-processing of site migration. Enhanced process 3.3.1 Resolving Site Conversion Issues 2385606 2392727 1610 FPS 01 (shadow Notes for conversion) n/a n/a 4.1.3 Maintain Tables for Plant Transport Harmonization of departments and receiving points between site master and BP. 4.1.4 Departments 4.1.6.5 Tables for Plant Transport 1610 FPS 01 4.2.3 Maintenance of Departments and Receiving Points 2374568 2387393 4.5 Site Archiving 8 Enhanced process Harmonization of additional addresses and geolocation data between site master and BP. 4.2.4 Maintenance of Additional Addresses and Geolocation Data Updated description Referential integrity in site distribution. 4.4 Site Distribution CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 1610 FPS 01 2391784 n/a n/a Site Master Conversion Information About This Document Type of Update Enhanced process Description Distribution of contact persons with site distribution from SAP ERP to SAP S/4HANA. Chapter in This Document Available as of Feature Package Stack (FPS) 4.4 Site Distribution 1610 FPS 01 SAP Note 2371673 (SAP S/4HANA) 2366114 (SAP ERP) Enhanced process Option to use CVI Customizing check report for C/Vs assigned to sites. 3.1.2.4 CVI Customizing Check Report Enhanced process Mandatory field checks for C/V account groups. Enhanced process n/a 2451504 (SAP ERP) 3.1.2.1 Customizing and Configuration 1610 FPS 02 2437855 Option to create BP with reference. 4.2.1 Integrated BP Maintenance 1610 FPS 02 n/a Updated description Information about BP distribution added. 4.4.4 BP Distribution n/a n/a Enhanced process New Simplification Item Check (SIC) framework. 3.1.2.3 Preparation Report 1709 FPS00 n/a Site Master Conversion Information About This Document 3.2.1 Pre-Check CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 9 2 Business Partner Approach (Customer/Vendor Integration) in SAP S/4HANA In SAP S/4HANA, the business partner (BP) is capable of centrally managing master data for business partners, customers (C), and vendors (V). In SAP S/4HANA where the BP is the single point of entry used to create, edit, and display master data for business partners, customers, and vendors, unlike in SAP ERP, where C/V master data can be handled separately. As a result of the harmonization and unification of the data model, the transaction code for managing customer and vendor master data in SAP S/4HANA is transaction BP. The specific transaction codes used to maintain C/V master data separately in SAP Business Suite are not available on SAP S/4HANA. Note In SAP S/4HANA, vendor is referred to as supplier, and customer (C) and vendor (V) are roles of a business partner (BP). Only SAP Business Suite customers with Customer/Vendor Integration (CVI) in place can move to SAP S/4HANA. To ensure successful conversion, all customers and suppliers must be converted to business partners (BP) in the system. The integration of C/V master data with BP data is already possible on SAP ERP by means of Customer/Vendor Integration (CVI), which can be used on SAP ERP in two directions: • C/V can be maintained as the leading, independent entities and the corresponding BP data is updated in the background. • BP can be maintained as the leading entity with C/V roles and the corresponding C/V data is updated in the background. With the data model harmonization on SAP S/4HANA, only the second option (BP can be maintained as the leading entity) is supported for the maintenance of C/V data. For more information, see Simplification List – TOP Items, Business Partner Approach/Customer-Vendor Integration (CVI) (PDF). 2.1 Impact of the Business Partner Approach on Site Master The site master is affected by this data model harmonization because a site always has the role of a customer and can optionally also have the role of a vendor. In terms of the data model, a customer master record and optionally a vendor master record is assigned to a site. The integration of C/Vs with BP data (by means of CVI) is not supported on SAP ERP for C/Vs assigned to a site, but it is mandatory on SAP S/4HANA. Integration requires migration of C/Vs assigned to a site during the SAP S/4HANA conversion where BPs are created for these C/Vs. This step is illustrated in the following picture. 10 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Business Partner Approach (Customer/Vendor Integration) in SAP S/4HANA In addition to the impact of the one-time migration of C/Vs assigned to a site as part of the SAP S/4HANA conversion process and as a result of the business partner approach, some site-related processes differ on SAP S/4HANA compared to SAP ERP. The processes that are most significantly impacted are: • Maintenance of sites including Customizing for site maintenance • Distribution of sites • Archiving of sites For details about the migration process and changes in the existing processes, please read the following chapters. Site Master Conversion Information Business Partner Approach (Customer/Vendor Integration) in SAP S/4HANA CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 11 3 SAP S/4HANA Conversion This chapter describes the steps for conversion from SAP ERP to SAP S/4HANA that are necessary with regard to the site master adjustments to the BP approach: 1. Preparing for conversion 2. Conversion (with pre-check and site migration) 3. Preparing operations after conversion 3.1 Preparing for Conversion The preparation for conversion with regard to site master and the BP approach comprises: 1. BP conversion and preparation for conversion to SAP S/4HANA 2. Preparing for site migration 3.1.1 BP Conversion and Preparation for Conversion to SAP S/4HANA (Independent of Site) For regular C/Vs not assigned to a site, the BP conversion, that is, the creation of a leading BP for the C/V, must be performed before the actual SAP S/4HANA conversion. C/Vs assigned to sites are excluded from this step. That is, no BPs will be created for C/Vs assigned to sites. The BP pre-check ensures that a BP has been created for each C/V (not assigned to a site) before the SAP S/4HANA conversion can be performed. Furthermore, Customizing activities with regard to the BP settings must be performed. For more information about BP conversion and the BP pre-check, please see the central consulting SAP Note 2265093 and the additional documentation referred to from this SAP Note. 3.1.2 Preparing for Site Migration Before conversion to SAP S/4HANA takes place, we recommend a cleanup of site data and of Customizing related to sites and the C/Vs assigned to sites: • Remove obsolete data from the system and perform archiving of sites and their assigned C/Vs. • Remove known data inconsistencies and maintain missing mandatory data. 12 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information SAP S/4HANA Conversion 3.1.2.1 Customizing and Configuration The following (Customizing) activities are required in preparation for the migration of site data to the BP approach: • Activate CVI synchronization options. • Activate PPO requests and creation of post processing orders. • Define BP number ranges and groupings. • Define number assignment C/V to BP. • Define BP role for direction C/V to BP and BP role category for direction BP to C/V. • Maintain field assignment for C/V integration (if relevant data is used for C/V assigned to sites). • Implement BAdIs (if required or desired): o Adjust BP number of new BPs created for C/Vs assigned to sites (BADI_CHANGE_BP_NUMBER, method CHANGE_BP_NUMBER). o Adjust ID of new BP role for site (BADI_CHANGE_BP_NUMBER, method CHANGE_BP_ROLE_NAME_BPSITE). Some of these activities are also required for and might already have been done as part of the general BP conversion activities. For more information about these activities, see chapter 3.1.2.3 Preparation Report. To avoid issues with BP creation during the migration phase and later during SAP S/4HANA operations, we strongly recommend that you configure the field attributes of the BP consistently with the field selection/status of the C/Vs. There should be no mandatory fields for C/Vs and BP address data that are not mandatory for the site. As of SAP S/4HANA 1610 FPS 02 or if SAP Note 2437855 has been implemented, mandatory field checks based on the field status control for C/V account groups defined in Customizing for Logistics - General under Business Partner Customers / Vendors Control Define Account Groups and Field Selection for Customers / Define Account Groups and Field Selection (Vendor) are skipped for BP creation during site migration to prevent unwanted issues. Otherwise, issues could occur if fields are defined as mandatory after C/V data has been created, but the fields have not yet been maintained. Issues could also occur in the case of address data fields because the field checks for address data fields defined in the field status control for C/V account groups do not apply to the address data maintained for sites in SAP ERP. We also recommend that you prepare general BP Customizing, such as BP roles, BP field attributes, and authorization control, to be used for BPs representing C/Vs assigned to sites before the conversion process starts (Customizing path: Cross-Application Components SAP Business Partner Business Partner). Make sure that you pay special attention to existing custom enhancements of C/Vs that might need to be reimplemented by using the BP enhancement concept (see Customizing for Cross-Application Components under SAP Business Partner Business Partner Extensibility). 3.1.2.2 Consolidation of Common C/V Data If a site as a legal entity has both a customer and supplier role, one common BP is created for the C and V assigned to the site. A C and V share some common data that can be maintained independently on SAP ERP but on SAP S/4HANA are represented by central BP data. In order to create a BP with central data shared between the C and V role, there must be no conflicts in this data between an existing C and V that are assigned to the same site. If conflicts exist, the data must be consolidated prior to BP creation during conversion to SAP S/4HANA in order to avoid data loss or issues with BP creation. Site Master Conversion Information SAP S/4HANA Conversion CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 13 The following table lists common C/V data that is consolidated into central BP data and describes the potential conflicts that need to be resolved prior to SAP S/4HANA conversion. Data Table(s)/Field(s) Data Consolidation Requirements for central BP Data Address Data ADR* tables No data consolidation required because the address data of C/Vs assigned to a site is identical. Address fields in KNA1/LFA1/T001W Site migration: Separate address data records with same content are generated during BP creation (new BAS records are created for BP and V, whereas existing BAS record is used for C site). CVI on SAP S/4HANA: BP standard address is synchronized into C/V address without being specific for a C or a V. Contact Persons KNVK No data consolidation required since technical key ensures uniqueness of contact persons across C/Vs. Site migration: Contact persons of C/Vs are collected into BP contact persons (BPs of category person with contact person relation to the BP representing the C/V) during BP creation. CVI on SAP S/4HANA: BP contact persons are synchronized into C/V contact persons without being specific for a C or a V. Note After site migration, the union of contact person data assigned to C/Vs before migration is assigned to a BP, and the C/Vs also share this common set of contact persons with potential semantic doublets. Bank Details KNBK/LFBK Data consolidation might be required if bank details differ between a C and a V for the same logical key (country key/bank key/bank account number). Site migration: Bank details of C/Vs are consolidated into BP bank details during BP creation. Despite the technical key in the BP data model, only one record is allowed for each logical key. CVI on SAP S/4HANA: BP bank details are synchronized into C/V bank details without being specific for a C or a V. Note After site migration, the union of bank details assigned to C/Vs before migration is assigned to a BP, and the C/Vs also share this common set of bank details. Tax Numbers 14 Tax number fields in KNA1/LFA1 Data consolidation might be required if tax numbers differ between C and V. KNAS/LFAS for foreign country VAT numbers Site migration: Tax numbers of C/V are consolidated into BP tax numbers with BP tax number categories during BP creation. The tax number must be unique by tax number category. CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information SAP S/4HANA Conversion Data Table(s)/Field(s) Data Consolidation Requirements for central BP Data CVI on SAP S/4HANA: BP tax numbers are synchronized into C/V tax numbers without being specific for a C or a V. Note After site migration, the union of tax numbers assigned to C/Vs before migration is assigned to a BP, and the C/Vs also share this common set of tax numbers. Industries KNA1-/LFA1-BRSCH Data consolidation might be required if industries differ between C and V. Site migration: Industry key of C/V is consolidated into BP standard industry for standard industry system during BP creation. Although the BP allows multiple industry systems and industry assignments, the standard industry of the standard industry system, which is synchronized between the BP and C/V, must be unique. CVI on SAP S/4HANA: BP standard industry of standard industry system is synchronized into C/V industry without being specific for the C or V. Note After site migration, the C/Vs share the same industry key even if the industry key was only maintained for either the C or the V before migration. International Location Number KNA1-/LFA1-BBBNR, -BBSNR, -BUBKZ Data consolidation might be required if international location number differs between C and V. Site migration: International location number of C/V is consolidated into BP international location number. CVI on SAP S/4HANA: BP international location number is synchronized into C/V international location number without being specific for C or V. Note After site migration, the C/Vs share the same international location number even if the international location number was only maintained for the C before migration. Company ID of Trading Partner KNA1-/LFA1-VBUND Site Master Conversion Information SAP S/4HANA Conversion Data consolidation might be required if company ID of trading partner differs between the C and V. Site migration: Company ID of trading partner of C/V is consolidated into BP company ID of trading partner. CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 15 Data Table(s)/Field(s) Data Consolidation Requirements for central BP Data CVI on SAP S/4HANA: BP company ID of trading partner is synchronized into C/V company ID of trading partner without being specific for C or V. Note After site migration, the C/Vs share the same company ID of the trading partner even if the company ID of the trading partner was only maintained for the C before migration. Any conflicts must be resolved by maintaining the corresponding data for the C and the V assigned to the same site. The site pre-check checks for these conflicts. For information, see 3.2.1 and 3.1.2.3. 3.1.2.3 Preparation Report A mandatory pre-check is performed at the beginning of the SAP S/4HANA conversion process in order to check whether the prerequisites for the site migration to BP are fulfilled. Conversion is only possible if the checked prerequisites are fulfilled. This pre-check can and should already be executed during the preparation phase of conversion to facilitate the conversion preparation. The execution of the pre-check in the preparation phase is possible by using a preparation report. For information about the messages issued during the pre-check, see the Checks Performed in the Pre-Check Phase table, which is also attached to SAP Note 2310884. You can use the information in this table to prepare for conversion before running the pre-check or preparation report. Note There is a big overlap between the checks performed by the check report for checking CVI Customizing as preparation for the conversion of C/Vs not assigned to a site to the BP approach (see SAP Note 1623677) and the general BP pre-check for SAP S/4HANA conversion (see SAP Note 2211312). The Customizing activities required for the site migration might already have been performed during general BP conversion or BP preparation for conversion to SAP S/4HANA. The checks of the pre-check for site migration are only performed for C/Vs assigned to sites and only for other entities that are relevant for these C/Vs, such as C/V account groups. However, some checks are of a more general nature and are performed independently of the actual C/Vs. The relevant SAP Notes for executing the pre-check by using the preparation report are: • SAP Notes with pre-checks and preparation report that are only relevant for the conversion target release SAP S/4HANA 1610 using the previous pre-check framework: o SAP Note 2310871: Check methods for execution of checks (delivered through SAP Note and support package) o SAP Note 2336853: Preparation report (delivered through SAP Note and support package) • 16 SAP Note with pre-checks and preparation report that are relevant for the conversion target releases SAP S/4HANA 1709 and higher, using the new Simplification Item Check (SIC) framework: CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information SAP S/4HANA Conversion o SAP Note 2502552: Check the methods and preparation report for execution of checks in preparation mode (pre-check report: PERFORM_CHK_SMBP_FOR_S4_SIC) • The following SAP Notes are only required for the implementation of the BAdIs that are called during the precheck and during the migration to rename BPs and new BP roles: o SAP Note 2315639: BAdIs used in the pre-check and migration report (delivered through SAP Note and support package) o SAP Notes for the implementation of methods that call the BAdI methods: o SAP Note 2348529 for the use of the previous pre-check framework (delivered through SAP Note and support package) o SAP Note 2456668 for the use of the new SIC framework (delivered through SAP Note and support package) • SAP Note 2310884: Consulting SAP Note for the pre-check 3.1.2.4 CVI Customizing Check Report The CVI Customizing check report CVI_UPGRADE_CHECK_RESOLVE checks the necessary CVI and BP Customizing settings for each client and proposes a solution for missing or wrong Customizing entries. You can use this report to check the Customizing settings for C/Vs assigned to Retail sites when called using transaction code SM_CVI_FS_CHECK_CUS. We strongly recommend that you use transaction SM_CVI_FS_CHECK_CUS to check and potentially adjust CVI and BP Customizing for C/Vs assigned to sites before you start the SAP S/4HANA conversion process. Transaction SM_CVI_FS_CHECK_CUS is made available via SAP Note 2451504. The CVI Customizing check report CVI_UPGRADE_CHECK_RESOLVE can be implemented via SAP Note 2344034. See document BP Conversion Document attached to SAP Note 2265093 for a documentation of CVI_UPGRADE_CHECK_RESOLVE. 3.2 Conversion During conversion to SAP S/4HANA, the following steps are performed with regard to the conversion of site master data to the BP approach: • Pre-check • XPRAs • Site migration report 3.2.1 Pre-Check Before the technical conversion process starts, a mandatory pre-check is performed on the source release in order to check whether the prerequisites for the site migration to the BP approach are fulfilled. Conversion is only possible if the checked prerequisites are fulfilled. This pre-check should already have been executed during the conversion preparation phase to facilitate conversion preparation (see chapter 3.1.2.3 Preparation Report). Site Master Conversion Information SAP S/4HANA Conversion CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 17 For more information about the actual checks performed by the pre-check, see chapter 3.1.2.3 Preparation Report. If the pre-check returns issues, you can look for the corresponding check ID for further information in the Checks Performed in the Pre-Check Phase table, which is also attached to SAP Note 2310884. If Retail sites have been created in the system, conversion is only possible to SAP S/4HANA 1610 or higher. The relevant SAP Notes for the pre-check are: • SAP Notes that are only relevant for the conversion target release SAP S/4HANA 1610, using the previous pre-check framework: o SAP Note 2185960: SAP_APPL Master Check for SAP S/4HANA System Conversion Checks o SAP Note 2310871: Check methods for execution of checks (delivered through SAP Note and support package) • SAP Notes relevant for the conversion target releases SAP S/4HANA 1709 and higher, using the new Simplification Item Check (SIC) framework: o SAP Note 2502552: Check methods for execution of checks • The following SAP Notes are only required for the implementation of the BAdIs that are called during precheck and migration to rename BPs and new BP roles: o SAP Note 2315639: BAdIs used in the pre-check and migration report (delivered through SAP Note and support package) o SAP Notes for the implementation of methods that call the BAdI methods: o SAP Note 2348529 if the previous pre-check framework is used (delivered through SAP Note and support package) o SAP Note 2456668 if the new SIC framework is used (delivered through SAP Note and support package) • SAP Note 2310884: Consulting SAP Note for pre-check 3.2.2 XPRAs During the conversion phase, XPRAs are executed to convert data from the source release to a state required in the target release on all clients. The following XPRAs are relevant for the site. 3.2.2.1 XPRA: Site Profile XPRA: WFIL_XPRA_S4MIG_TWRF2 The XPRA converts existing site profiles (table TWRF2): • New indicator Plant with Supplier (SITE_WITH_BP_GRP_SUPPL) is set in case the field Vendor Account Group (KTOKK) is filled in the existing profile. 3.2.2.2 XPRA: Tables for Site Transport XPRA: WFIL_XPRA_S4_ADJUST_DISTR_TABS 18 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information SAP S/4HANA Conversion The XPRA converts the tables for site transport (table SITE_DISTR_TAB): • The tables belonging to the customer, the supplier, and to address data are removed from the list of tables relevant for site transport. The reason for this is that this data is distributed by means of BP distribution and therefore no longer needs to be handled by means of site distribution. • The following tables are required for the distribution of settings relevant for the material ledger on SAP S/4HANA and are added to the list of tables relevant for site transport: TCKM2, TMLCCSHD, TMLCCSCR, CKMLAB02. 3.2.3 Site Migration Report During the conversion phase, a migration report is executed to create BPs for C/Vs assigned to sites and for the contact persons of these C/Vs on all clients: • One BP organization is created per site. This BP has either a C role only or a C and V role. • One BP person is created per contact person and linked to the BP representing the C/V via a contact person relation. The report logs issues that might occur in this migration step and can be restarted after the conversion phase if required. 3.2.3.1 BP Naming The following logic is used to determine the number of the new BP created for each site: The BP grouping is determined for the customer account group of the customer assigned to the site (Customizing activity Define Number Assignment for Direction Customer to BP, table CVIC_CUST_TO_BP1). Note If a vendor is also assigned to the site and the account group of the vendor uses a different BP grouping (Customizing activity Define Number Assignment for Direction Vendor to BP, table CVIC_VEND_TO_BP1), this is ignored during migration. A corresponding check is performed in the pre-check and a warning is issued in the case of different BP groupings for the customer and vendor account group. The further processing depends on the number range settings of the BP grouping (Customizing activity Define Groupings and Assign Number Ranges, table TB001): • For internal numbering, a number from the internal number range is determined and used for the BP. In case the internal number determination failed, the BP for the site is not created and an error is logged (post processing required after conversion). • For external numbering, by default, the customer number is used as the BP number. Note The customer number is not used as the BP number in the following cases: o If a vendor is also assigned to the site and the vendor number is different from the customer number. o If the customer number does not fall within the defined BP number range. Site Master Conversion Information SAP S/4HANA Conversion CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 19 o If the customer number is already used as the BP number. o If the same BP number is used for more than one BP to be created during migration. In these cases, the BP number needs to be determined by using a BAdI implementation (BADI_CHANGE_BP_NUMBER, method CHANGE_BP_NUMBER). The same BAdI can also be used to change the external BP numbers that have been determined by default and would not need any adjustment. If a BP number has been defined or changed by means of this BAdI, the system checks that the BP number is not yet used and that it falls within the defined BP number range of the BP grouping. If no (valid) number is available for a BP after the BAdI implementation, the BP for the site is not created and an error is logged (post processing required after conversion). 3.2.3.2 BP Role for Site A new BP role with role category BPSITE is created by the migration report on each client. This role is assigned to the new BPs created for C/Vs assigned to a site. By default, the new BP role has the name BPSITE. A different name can be chosen by implementing BAdI BADI_CHANGE_BP_NUMBER, method CHANGE_BP_ROLE_NAME_BPSITE. If a role with name BPSITE but another role category than BPSITE already exists at the time of migration, the BAdI must be implemented in order to define a name for the new role that is not yet used. 3.2.3.3 Contact Persons In the BP data model, contact persons are modelled as BP persons and assigned to the BP representing the C/V by means of the Is Contact Person For-Has Contact Person relationship. During site migration, for each contact person of a C/V, such a BP contact person is created and assigned to the new BP representing the C/V by means of the Is Contact Person For-Has Contact Person relationship. The BP grouping marked as Standard Grouping for Internal Number Assignment is used for the contact person BPs and the BP numbers are determined from the corresponding internal number range. If a site has both a C and V assigned to it, the new BP representing this C and V will be assigned the sum of contact persons of the C and V and these contact persons are then valid for both the C and V. In other words, the C inherits the contact persons of the V and vice versa. If the C and V had assigned semantically the same contact persons on SAP ERP that were technically different entities, you might want to consolidate the contact persons assigned to the new BP on SAP S/4HANA. 3.2.3.4 Address Data A BP requires a separate address data record (BAS record) with different address numbers (ADRNR) for the C and V assigned to the same BP (the BP itself also has a separate address data record). However, the C and V assigned to one site in SAP ERP share the same address data record, that is, KNA1-ADRNR and LFA1-ADRNR are the same. Therefore, the migration report creates a separate address data record for the V assigned to a site (KNA1-ADRNR and LFA1-ADRNR are no longer the same, but the information in the address data records is identical). In this way, the prerequisites for the creation of the BP are fulfilled. 20 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information SAP S/4HANA Conversion Note The site itself still shares the address data record with the C assigned to it on SAP S/4HANA like in SAP ERP (that is, T001W-ADRNR and KNA1-ADRNR are the same). This applies both to migrated sites and to sites that are created on SAP S/4HANA. 3.3 Preparing Operations after Conversion 3.3.1 Resolving Site Conversion Issues If the migration report that was executed automatically during conversion could not successfully create the required BPs for all sites, the conversion of the remaining sites must be done before using the sites productively on SAP S/4HANA. Note It is not possible to maintain a site to which no BP is assigned on SAP S/4HANA. We recommend that you perform the following activities after conversion in order to check that BPs have been created successfully: 1. Check the migration log. The messages created during conversion process can be displayed by using report UPGBA_DISPLAY_REPORT_LOG with log ID MIGRATION_CV_BP (or via conversion file after conversion). Any error messages reported during BP creation can be found in this log with reference to the affected site. If an error message is reported during BP creation, the BP is usually not created. 2. Run the check report for site migration. Report PERFORM_CHK_SMBP_FOR_S4_SIC (for usage with SIC framework) or report PERFORM_CHK_SMBP_FOR_S4 (for usage with previous framework) issues information for sites with missing BPs if the option "Output of results as detailed list with selection of clients and sites" is enabled. Make sure that you run the report for all clients and all sites. Any site for which a message is issued does not yet have a BP, regardless of the message status. The report checks the required BP and CVI Customizing settings and the basic master data settings for sites to be converted, but does not simulate the complete BP creation process. Therefore, it is possible that the report issues the message "Site is ready for migration" even though the creation of a BP fails. For more details about the checks that are performed by this report, see chapter 3.2.1 Pre-Check. 3. Analyze the reason for reported issues and fixed them, then start the conversion of sites with missing BPs again. 4. Convert the sites with missing BPs by using migration report WFIL_CSR_S4MIG_CV_BP. You must execute this report on each client where issues occurred during conversion. 5. Check the migration log again and run the check report for site migration again. Each time you run report WFIL_CSR_S4MIG_CV_BP, the system clears the log messages of the previous run. Therefore, you can use report UPGBA_DISPLAY_REPORT_LOG after each run to see the issued messages. Site Master Conversion Information SAP S/4HANA Conversion CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 21 6. Check for BPs that have been created with issues (for example, incomplete data or missing mandatory fields) in PPO. You can use transaction MDS_PPO2 to find issues that need to be resolved for the BPs created using the migration report. 3.3.2 Additional Customizing for Sites This chapter describes the Customizing settings that might be required for the SAP S/4HANA operations of sites with regard to the BP approach, which can only be made after the SAP S/4HANA conversion. 3.3.2.1 Site Profiles Customizing path: Logistics - General Plant Master Control Data for Plant Maintenance Plant Profiles The following settings are required/recommended for site profiles that are used on SAP S/4HANA: • Assign BP Groupings (new mandatory field): New default BP groupings for site profiles are available with delivery Customizing on SAP S/4HANA. • Assign BP Role Groupings (new optional field): New default BP role groupings for site profiles are available with delivery Customizing on SAP S/4HANA. 3.3.2.2 BP Role Groupings Customizing path: Cross-Application Components SAP Business Partner Business Partner Basic Settings Business Partner Roles Define BP Role Groupings BP role groupings to be used for sites (assigned to site profiles or entered during site creation) can only be completely created after conversion because they must comprise a BP role with role category BPSITE which is only available on SAP S/4HANA. BP role groupings S_CUVN and S_CUST are part of the SAP S/4HANA delivery Customizing and already include the new BP role with role category BPSITE besides the standard C/V roles. You can define your own BP role groupings to be used for sites. 3.4 Conversion of Distributed System Landscapes This chapter provides information about SAP S/4HANA conversion of distributed system landscapes with regard to SM/BP harmonization. 22 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information SAP S/4HANA Conversion 3.4.1 BP Numbering If site data is distributed within a system landscape, that is, the same sites exist on several systems or clients and the site data is kept consistent between these systems or clients via data distribution, we recommend that you ensure that BPs with same numbers are created for the same sites on the individual systems or clients. This can be achieved by • Using synchronized number ranges for the BP creation in the different systems/clients • Using external numbering for the BP creation (potentially by switching internal number range intervals temporarily to external numbering) • Potentially through a BAdI implementation (if required) for BP naming during conversion that leads to same BP numbers for same sites 3.4.2 Phased Conversion to SAP S/4HANA In order to support phased conversion of an existing system landscape to SAP S/4HANA, the distribution of site data is also supported in a mixed landscape with both SAP ERP and SAP S/4HANA systems. Site Master Conversion Information SAP S/4HANA Conversion CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 23 4 Post-Conversion Operations This chapter describes the changes to the site master as a result of the harmonization of the data model that are relevant for operations on SAP S/4HANA. 4.1 Customizing The following chapters describe the changes with regard to site master Customizing (Customizing path: Logistics - General Plant Master) on SAP S/4HANA compared to SAP ERP due to BP approach. Changes in the Customizing structure: • Customizing for Control Data has been renamed to Control Data for Plant Maintenance. • New Customizing activities have been added under Settings for Plant Replication. 4.1.1 Site Profile Customizing path: Logistics - General Plant Master Control Data for Plant Maintenance Plant Profiles Changes in the site profile with SAP S/4HANA: • It is not possible to maintain the C and V account group in the site profile on SAP S/4HANA. Instead, the new BP Grouping field is a mandatory field with SAP S/4HANA. The C/V account group assigned to the BP grouping is displayed in the site profile (the V account group is displayed only if the V role is relevant for the site profile, that is, if the Plant with Supplier indicator is set). • The Plant with Supplier indicator has been introduced with SAP S/4HANA. It allows explicit control at the level of the site profile, if sites with this profile require a vendor (supplier) role or not. If this indicator is set, only BP groupings with assigned V account group are allowed for the site profile (a C account group is always required for the BP grouping, in the same way that a C account group is always required for a site profile on SAP ERP). • The Address origin field is obsolete with SAP S/4HANA. On SAP S/4HANA, the BP is leading for address data and the site does not have address data that might deviate from the BP address. • The BP Role Grouping field has been introduced with SAP S/4HANA as an optional field. It is used as the default value in the integrated site maintenance, where the BP role grouping is required for the creation of a new BP. If a BP role grouping is entered, it must include a particular site role (role with role category BPSITE) and at least one role for whose role category the creation of a C and V (if the indicator Plant with Supplier is set) is mandatory. • It is not possible to maintain reference data for a C/V in the site profile. 24 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Post-Conversion Operations 4.1.2 Enable Standard Customer/Vendor As a Source for Site Update Customizing path in SAP ERP: Logistics - General Plant Master Control Data Enable Standard Customer/Vendor as Source for Site Update This Customizing activity is obsolete on SAP S/4HANA. On SAP S/4HANA, the BP is the leading entity for address data and thus the address data imported in a distribution scenario along with BP or C/V data is always used as the address data of the site. 4.1.3 Maintain Tables for Plant Transport The Customizing activity Maintain Tables for Plant Transport has been moved. SAP ERP Customizing path: Logistics - General Plant Master Maintain Plants Maintain Tables for Plant Transport SAP S/4HANA Customizing path: Logistics - General Plant Master Settings for Plant Replication Maintain Tables for Plant Transport All tables belonging to the BP/C/V object model and to the address data (BAS) are removed from the tables for plant transport and should not be added again. On SAP S/4HANA, BP/C/V data is distributed using the BP distribution mechanism, which does not require this Customizing. Note Tables WRF4 for departments and table WRF12 for receiving points are not automatically removed during conversion, though not considered any longer by site distribution on SAP S/4HANA since now only handled as part of the C role of the BP (see chapter 1.4). If required, they can be removed manually in the Customizing activity. 4.1.4Departments The Customizing activity Departments has been removed. SAP ERP Customizing path: Logistics - General Plant Master Control Data Departments On SAP S/4HANA, departments are handled as part of the C role of the BP (see chapter 1.4). 4.1.5 Customizing Activities for DRF Customizing activities for the Data Replication Framework (DRF) required for the distribution of sites on SAP S/4HANA can be accessed by using transaction DRFIMG. More information and a corresponding link can be found in Customizing for Logistics - General under Plant Master Settings for Plant Replication General Information. Site Master Conversion Information Post-Conversion Operations CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 25 4.1.6Delivery Customizing New delivery Customizing has been introduced and the existing delivery Customizing has been adjusted with regard to the site master due to the introduction of the BP approach. 4.1.6.1 BP Role/Role Category Customizing path: Cross-Application Components SAP Business Partner Business Partner Basic Settings Business Partner Roles Define BP Roles Tables: TB003, TB003A A new BP role with new role category for sites is available. BP Role Description Role Category Standard Assignment BP Role Category BPSITE Site BPSITE X Note This new role/role category is required for the creation of new BPs for sites during the conversion process. Therefore, the role/role category is created during conversion on each client by using the site migration report. A BAdI (BADI_CHANGE_BP_NUMBER, method CHANGE_BP_ROLE_NAME_BPSITE) can be used to choose a different name for the BP role. The new BP role category is delivered via a system table (TB003A). If custom BP roles are used for a site instead of the new default site role, it is important that this BP role category is used. 4.1.6.2 BP Role Groupings Customizing path: Cross-Application Components SAP Business Partner Business Partner Basic Settings Business Partner Roles Define BP Role Groupings Tables: TB003G, TB003J, TB003I New BP role groupings/role grouping categories with the assigned BP roles are available for the maintenance of BPs assigned to sites. The role groupings include the required default roles for C/V and the new site role required for the creation of a BP assigned to a site. BP Role Grouping Description Role Grouping Category Assigned Roles S_CUVN BP role grouping for site with customer and supplier S_CUVN BPSITE FLCU00 FLCU01 26 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Post-Conversion Operations BP Role Grouping Description Role Grouping Category Assigned Roles FLVN00 FLVN01 BP role grouping for site with customer S_CUST S_CUST BPSITE FLCU00 FLCU01 4.1.6.3 BP Groupings and Number Assignment BP Groupings to C/V Account Groups Customizing path: Cross-Application Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Table: TB001 Additional Customizing paths: • 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 BP to Customer Table: TBD001 • Cross-Application Components Master Data Synchronization Customer/Vendor Integration Business Partner Settings Settings for Vendor Integration Field Assignment for Vendor Integration Assign Keys Define Number Assignment for Direction BP to Vendor Table: TBC001 New BP groupings are available to be used for sites. The BP groupings use external numbering with a number range corresponding to the number range used by the existing C/V account groups. The new BP groupings are linked to the existing C/V account groups that have been used in SAP ERP delivery Customizing in site profiles. BP Grouping Description BP Number Range S100 For distribution centers AB (external) S110 For stores w/o intercompany billing S120 For stores with intercomp. billing Site Master Conversion Information Post-Conversion Operations C Account Group Same Numbers for C Account Group V Account Group Same Numbers for V Account Group 0100 X 0100 X AB (external) 0110 X - - AB (external) 0120 X - - CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 27 BP Grouping Description BP Number Range S130 For stores with external billing AB (external) S150 For franchisees S160 For wholesale customers 4.1.6.4 C Account Group Same Numbers for C Account Group V Account Group Same Numbers for V Account Group 0130 X - - AB (external) 0150 X - - AB (external) 0160 X - - Site Profiles Customizing path: Logistics - General Plant Master Control Data for Plant Maintenance Plant Profiles Table: TWRF2 The site profiles already existing in SAP ERP delivery Customizing have been adjusted: • Assignment of C/V account groups replaced by corresponding new BP groupings. • New indicator Plant with Supplier set for site profiles requiring a supplier (vendor) role. • New field BP Role Grouping filled with new default values. • Obsolete SAP ERP field Address origin no longer available. • SAP ERP fields for C/V reference data no longer available. Plant Profile Description Plant Category Plant with Supplier BP Grouping BP Role Grouping 0100 Distribution center B X S100 S_CUVN 0110 Store w/o intercomp. billing A - S110 S_CUST 0120 Store with intercomp. billing A - S120 S_CUST 0130 Store with external billing A - S130 S_CUST 0150 Franchisee A - S150 S_CUST 0160 Wholesale customer A - S160 S_CUST 4.1.6.5 Tables for Plant Transport Customizing path: Logistics - General Plant Master Settings for Plant Replication Maintain Tables for Plant Transport Table: SITE_DISTR_TABS 28 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Post-Conversion Operations All tables belonging to the BP/C/V object model and to address data (BAS) are removed from delivery Customizing (due to the separate distribution mechanism). This includes tables WRF4 for departments and table WRF12 for receiving points, which are now handled as part of the C role of the BP (see chapter 1.4). The following tables required for the distribution of material ledger relevant settings are included in the delivery Customizing: TCKM2, TMLCCSHD, TMLCCSCR, CKMLAB02 4.2 Site Maintenance The maintenance of the C/V within the integrated site maintenance (WB01/WB02/WB03) has been replaced by the maintenance of the BP with C/V roles. Maintenance of address data is part of the BP maintenance. This centrally maintained address data is valid for the site including the BP with a C/V role. 4.2.1 Integrated BP Maintenance The maintenance of the BP with C/V roles for sites is integrated in the site maintenance in a very similar way to the maintenance of C/Vs for sites in SAP ERP: The C/V buttons are replaced by one BP button. The number of the BP assigned to the site is displayed on the site maintenance screen in the header area. The numbers of the C/V (roles of the BP) are also displayed in the header area. A BP with the required C/V roles according to the site profile must be assigned to a site before the site can be saved. The BP must also have a role with role category BPSITE assigned to it. If a role with role category BPSITE is not assigned to the BP, the BP role with standard assignment to this role category is automatically added to the BP when the site is saved. A new BP can be created from within the site maintenance or an existing BP can be assigned to the site. In the case of site creation (WB01), the BP number in the header area of the screen is defaulted with the site number if the BP numbering settings (assigned to the BP grouping) allow this. The BP number can be edited in the case of external and internal BP numbering; in the case of internal BP numbering, the BP number is open for entry in order to assign an existing BP, as it is also possible in the case of external BP numbering. As of SAP S/4HANA 1610 FPS 02, a BP can be createdandmaintained with reference to an existing BP, that is, to the C/V assigned to the BP (). Whether this feature is available in the BP maintenance depends on the role(s) or views to be maintained for the BP. Where applicable, the data of the reference BP is copied to the respective data of the new BP. The creation and maintenance of a BP within the site maintenance is a logical unit of work (LUW) on its own. The BP is created or updated independent of saving the site. If a new BP is created from within site creation, it is first saved without being linked to the site. Only when the site itself is saved, the links between site and BP or the C/V are established. Even if a new BP has been created and saved within the site maintenance, the BP number can still be changed in the header area of the site maintenance screen in order to create another BP or to assign another existing BP to the site. Note Some parameters of the BP maintenance that are called from site maintenance can be adjusted by BAdI (BAdI SITE_MASTER_BP_MAINT_ADAPT, method ADAPT_PARAMS_CREATE if called in WB01, method ADAPT_PARAMS_CHANGE_DISPLAY if called in WB02 or WB03). Site Master Conversion Information Post-Conversion Operations CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 29 4.2.1.1 Creation of a New Business Partner If a BP with this number does not exist yet, it can be created pushing the BP button. Pushing the button first opens a dialog box where the BP grouping (defaulted with the BP grouping from the site profile) can be changed. Furthermore, the BP number can also be changed here according to the selected BP grouping. A BP role grouping including the required C/V roles according to the site profile and a role with role category BPSITE must be entered in the dialog box. The BP role grouping is defaulted with the value from the site profile. After confirming the information on the dialog box, you enter the BP maintenance dialog where you can create a BP with the roles defined in the BP role grouping. The BP number can also be changed here before saving. When you create the BP with the role grouping, the BP is created with all roles of this grouping in one step (one LUW). You can also create the BP in the individual roles of the grouping subsequently (several LUWs) by selecting the individual roles in the BP maintenance. In this case, we recommend that you create the BP in the required role with role category BPSITE first, so that the BP can be recognized as BP belonging to a site and can be handled accordingly. Depending on the numbering settings for the C/V account groups assigned to the BP grouping, the C/V number must be entered in the BP maintenance. It is also possible to enforce same numbers for C/V and BP by setting the Same Numbers indicator in the CVI Customizing where C/V account groups are assigned to the BP grouping. You can leave the BP maintenance with or without saving the BP. 4.2.1.2 Assignment of an Existing Business Partner Instead of creating a new BP from within the site maintenance, an existing BP can be assigned to a site by entering an existing BP number in the header area of the maintenance screen. This BP can then be the maintained from within the site maintenance and completed by missing roles if required. 4.2.1.3 Change or Display of an Existing Business Partner If the BP with the number entered in the header area of the site maintenance screen already exists, only the BP role grouping can be changed in the dialog box after pushing the BP button during site creation (WB01). The BP can then be maintained in the roles of the selected grouping. If you push the BP button from site change (WB02 or WB03 in change mode), you can access the BP maintenance for the BP assigned to the site. In this case, you can also create additional BP roles, relations to other BPs or even switch to the display, change or creation of other BPs. The BP button allows the display of the BP assigned to the site with all its defined roles when pushed within site display (WB03). 4.2.1.4 Saving a Site Saving a site establishes the links between site and BP respectively the C/V assigned to the BP. Once a site has been saved, these links cannot be changed or removed again. 30 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Post-Conversion Operations When the BP has no role with role category BPSITE assigned to it at the time the site is saved, the BP role with standard assignment to this role category is added to the BP in background. 4.2.1.5 Customizing Transports Transports of Customizing table entries maintained in site maintenance are not created on SAP S/4HANA, irrespective of the system settings relevant to changes and transports of client-specific objects. The reason for this is because controlled, integrated site data distribution including Customizing tables is possible on SAP S/4HANA by using the Data Replication Framework (DRF); therefore, Customizing transports for the site are no longer required. Note Customizing transports according to the system settings with regard to changes and transports of client specific objects are still created if the settings are maintained in the Customizing views. This is also applies to Customizing views that are accessed from within site creation (transaction WB01) from the Copy Customizing for plant screen. 4.2.2 Address Display Since the address data (valid for the site with BP/C/V) is maintained with the BP as leading entity on SAP S/4HANA, the Address tab in the site maintenance as available in SAP ERP is no longer available with SAP S/4HANA. A new Display Address screen that can be accessed from the task bar allows the central address data to be displayed quickly and conveniently without needing to open the BP maintenance dialog. The following fields are included on the SAP ERP Address tab, but are not part of the address data: • County Code and City Code: o In SAP ERP, this data can be maintained via C and via site (Address tab) and have been synchronized between C and site. o On SAP S/4HANA, this data can only be maintained via BP/C and is synchronized with the site and displayed on the new site Display Address screen. • Tax Indicator: On SAP S/4HANA, this indicator is available on the Purchasing/Distribution tab of site maintenance. Note Address fields as well as county code and city code are still part of the field status control for site maintenance that can be defined for each site profile or in the Customizing activity for transactiondependent field selection. However, the settings for these fields only affect the visibility of the fields on the site master address display screen and have no effect on optional or required entries for the fields. Site Master Conversion Information Post-Conversion Operations CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 31 4.2.3 Maintenance of Departments and Receiving Points Departments (table WRF4) and receiving points (table WRF12) are only handled via the C role of the BP on SAP S/4HANA (see chapter 1.4). Therefore, it is not possible to maintain departments (table WRF4) and receiving points directly from the site maintenance and the corresponding buttons in the task bar have been removed. The maintenance of this data is done via the corresponding maintenance screen for the C data in BP maintenance, which can be accessed from the site maintenance. 4.2.4 Maintenance of Additional Addresses and Geolocation Data The maintenance of additional addresses and geolocation data (table WFIL_ADD_ADR) for a site is not supported on SAP S/4HANA (see chapter 1.4). The maintenance option via menu path Customizing -> Geolocation Data (and report RWBTRGEOLOC) has been removed. Multiple addresses can be maintained with the BP assigned to a site. Geolocation data (table GEOLOC) can be determined automatically for these addresses in Customizing or by using a geocoding program. Note Automated migration of existing additional addresses and geolocation data (table WFIL_ADD_ADR) to the address data handling of the BP is not supported. 4.3 BP Maintenance The display and maintenance of BPs assigned to sites is possible in the BP maintenance dialog integrated in the site maintenance and in the stand-alone BP maintenance dialog (transaction BP) on SAP S/4HANA. Data that is stored redundantly for BPs and sites, in particular, address data and city/county code, is synchronized between BPs and sites when a BP is saved. The following fields of a BP or the C/V roles of a BP cannot be maintained if a site role (role category BPSITE) is assigned to a BP or if the BP maintenance is called from within site maintenance: • Central archiving indicator (BUT000-XDELE) of BP. The BP archiving indicator (including the ones for C/V) is set via the site archiving marker (WB06). • Plant assigned to C and V (KNA1-WERKS, LFA1-WERKS): The plant links are set by the site maintenance and must not be changed manually. • V assigned to C (KNA1-LIFNR) and C assigned to V (LFA1-KUNNR): These links are set by the site maintenance and must not be changed manually. 32 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Post-Conversion Operations 4.3.1 Time-Dependent Address Data The BP allows the maintenance of multiple addresses, address usages and time-dependency for both addresses and address usages. The currently valid standard address of the BP is the relevant address for the site and the C/V. Report BUPTDTRANSMIT distributes time-dependent BP data to dependent objects. When the address that is stored with the C (address fields of KNA1) is updated by using this report, the address data stored with the site (address fields of T001W) is also updated. 4.3.2 C/V Enhancements The enhancement concept for C/V available in SAP ERP is not supported with the BP maintenance on SAP S/4HANA. C/V enhancements need to be implemented on SAP S/4HANA using the Business Data Toolset (see Customizing for Cross-Application Components under SAP Business Partner Business Partner Extensibility). 4.4 Site Distribution The site distribution in SAP ERP by means of transaction WBTIMEX, which provides site transfer in push or pull mode, is replaced by the distribution of sites using the Data Replication Framework (DRF) on SAP S/4HANA, which provides push transfer only. Transactions WBTIMEX and WBTIMEX_CUST are not available with SAP S/4HANA. In a distribution scenario from SAP S/4HANA to SAP S/4HANA, the DRF implementation for the site transfers all site data including the Customizing assigned to the site, excluding the BP with its C/V roles assigned to the site. The BP with its roles and relations is transferred through its own DRF implementation. The Customizing that defines the relevant tables for site distribution by means of WBTIMEX in SAP ERP is also used for the site distribution on SAP S/4HANA through the DRF; however, the tables that belong to the BP/C/V and address data object model are not included in this Customizing and must not be added (Customizing path: Logistics - General Plant Master Settings for Plant Replication Maintain Tables for Plant Transport; table SITE_DISTR_TABS). Customizing transports are not created from the site maintenance in order to have a controlled distribution by means of the DRF only. A particular sequence is required for the distribution of a site including the BP: 1. Creation of a BP with a C/V on the target system A special logic in the BP inbound processing allows the creation of the BP even if the site that the C/V refers to does not yet exist on the target system: If a site role (BP role with role category BPSITE) is assigned to the BP and the site does not exist on the target system, the site links of C/V (KNA1WERKS/LFA1-WERKS) are cleared so that the BP can be created. The BP inbound processing checks the referential integrity of the incoming data. This means that a BP can only be created if other object instances that are referenced by the BP are already available on the target system. For example, if site-specific purchasing data (table LFM2 with key WERKS) is maintained for the V role of the BP, the BP can only be created if the corresponding site already exists (was distributed before) on the target system. 2. Creation of a site on the target system Site Master Conversion Information Post-Conversion Operations CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 33 A site can only be created if the BP with the required C/V roles already exists on the target system. When the site is created on the target system, the site links of the BP and its C/V roles (KNA1WERKS/LFA1-WERKS) are also established on the target system. The relevant DRF parameters for site distribution are: • BO type: DRF_0021 using replication via RFC • Outbound implementation: SITE_OUT Outbound parameters: o PACK_SIZE_BULK: Number of sites transferred with one RFC (optional, one site per RFC if not set). o NUMBER_OF_RETRIES: Number of retries in inbound processing if BP does not exist yet for a site (optional, only one trial if not set). o WAIT_TIME_FOR_RETRY: Wait time between retries in inbound processing if BP does not exist yet (optional, retries without additional wait time in between if not set). Note Parameters NUMBER_OF_RETRIES and WAIT_TIME_FOR_RETRY are only relevant in the case of direct output. Initial and changes transfer by means of DRFOUT and manual transfer do not support the retry feature. The DRF outbound implementation for sites provides filtering by site number and site category. Sites that are marked for archiving are always excluded from distribution by means of the DRF. The setting of the archiving flag and the actual archiving must be performed for each system/client. The DRF instance filter for the BP provides a special filter to exclude BPs with the site role (BP role with role category BPSITE). This filter can be used in case BPs (meant to be) assigned to sites should not be transferred (automatically) to a target system, but are only transferred after manual selection. 4.4.1Distribution Modes DRF provides the following distribution modes. Automatic Distribution Automatic distribution with two output modes (DRF Customizing setting for business system and BO type): • Direct output Changes are directly transferred to a target system when an object instance is saved. • Pooled output Changes are collected and transferred in a mass process at a later point in time. You can trigger the mass process for pooled output by starting or scheduling the data replication (DRF outbound) for the relevant replication model with the replication mode Changes in transaction DRFOUT. DRF instance filters for the replication model (maintained using transaction DRFF) are considered for automatic distribution (you can use the filter in order to include or exclude particular object instances into/from the distribution). If the system filter is activated (DRF Customizing setting for the business system and BO type), all existing filters are overridden during data transfer for object instances that have already been transferred to a target system (with the system filter you can ensure that if an object instance was previously sent to a target system, it continues to be sent in the future, independent of filter settings. Please note, that in this case, newly 34 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Post-Conversion Operations created sites are not (initially) transferred with the Changes run of DRFOUT but have to be transferred by means of manual distribution, as described below. Note The automatic distribution is only triggered from site maintenance, not from Customizing maintenance of Customizing tables assigned to the site. Manual Distribution Manual distribution with different output options: • Data replication (transaction DRFOUT, report RDRF_MESSAGE_OUT) with the Manual replication mode: The manual replication filter is used instead of the DRF filter for automatic distribution, that is, direct selection of object instances. • Replication by object selection (WD application DRF_MANUAL_REPLICATION): Direct selection of object instances and target systems, optional use of the DRF filter. In addition to using these distribution modes for the regular distribution of new or changed object instances, manual data replication (transaction DRFOUT, report RDRF_MESSAGE_OUT) with the Initial replication mode can be used for the initial transfer of all object instances that match the DRF filter. The following table describes how the different distribution modes can be achieved by using the DRF features for the integrated distribution of sites with a BP. Distribution Modes for Site Distribution and Business Partner Distribution Distribution Mode Site Distribution BP Distribution Automatic distribution for initial and changes transfer Automatic distribution (direct or pooled) is used: Automatic distribution is used: Manual distribution for initial transfer, automatic distribution for changes transfer • Filter includes sites to be transferred automatically. • In case of direct output: DRF parameters for number of retries and wait time between retries can be used to ensure that a BP can be created on target system before a site. • Distribution with pooled output is performed using DRFOUT with the Changes replication mode. • Manual distribution is used for initial transfer. Filter includes BPs assigned to sites to be transferred automatically. • Same output mode used as for site. In the case of pooled output (for site and BP): BP output must be scheduled before site output so that a BP can be created first in the target system. • Manual distribution is used for initial transfer before manual distribution of site in cases where a BP is to be distributed only with the site. o The filter excludes sites from automatic (initial) transfer. o Manual distribution is performed using DRFOUT with the Manual replication mode or by using the WD application (DRF_MANUAL_REPLICATION). • Site Master Conversion Information Post-Conversion Operations • Automatic distribution (direct or pooled) is used for changes transfer: The filter excludes BPs with the site role from automatic (initial) transfer. • Automatic distribution (direct or pooled): CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 35 Distribution Mode Site Distribution BP Distribution o The system filter is used to transfer changes of sites that have already been transferred. o In the case of direct output: DRF parameters for number of retries and wait time between retries can be used to ensure that a BP can be created on the target system before a site. System filter is used to transfer changes of BPs that have already been transferred. OR • o Distribution with pooled output is performed using DRFOUT with the Changes replication mode. Manual distribution for initial and changes transfer • Manual distribution is used. Automatic distribution (direct or pooled) is used in cases where a BP is to be distributed independently of a site. The same output mode is used as for a site. In the case of pooled output (for site and BP): BP output must be scheduled before site output so that the BP can be created first in the target system. • o The filter excludes sites from automatic transfer. o The system filter is not used. Manual distribution is performed using DRFOUT with the Manual replication mode or by using the WD application (DRF_MANUAL_REPLICATION). Manual distribution is used before manual distribution of site in cases where a BP is to be distributed only with a site. o The filter excludes BPs with the site role from automatic transfer. o The system filter is not used. OR • 4.4.2 Automatic distribution (direct or pooled) is used in cases where a BP is to be distributed independently of a site. Distribution Scenarios Different distribution scenarios are supported with regard to objects to be distributed from a source system and to a target system: • 36 Integrated site distribution: Distribution of sites as a whole (site including BP/C/V) between SAP Retail systems. CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Post-Conversion Operations • Export [BP/]C/V out of site: Distribution of [BP/]C/V from SAP Retail system, where they are originally created and assigned to site, to a non-Retail system (for example, an FI system), where the site is not available. • Import [BP/]C/V into site: Distribution of [BP/]C/V from non-SAP Retail system (for example, an FI system), where they are originally created without site, to a SAP Retail system, where they are assigned to a site. The following tables describes how the individual distribution scenarios can be achieved in different system landscape constellations involving SAP S/4HANA (Retail means that the BP/C/V is part of a site in this system): Distribution Scenario: Integrated site distribution System Object Distribution Source Target Source Target Method Remarks SAP S/4HANA SAP S/4HANA Site-BP-C/V Retail Retail Site-BPC/V Site: Site distribution via DRF BP-C/V needs to be created on target system before site. BP-C/V: BP distribution via DRF Site links of BP-C/V are cleared during initial creation of BP-C/V in target system for BP with site role (BP role with role category BPSITE). Site links of BP-C/V are established in target system during initial site creation. Key mapping is supported for the BP, but not for the C/V and the site. SAP S/4HANA SAP ERP Retail Retail Site-BP-C/V Site-C/V Site distribution via DRF or Site distribution via WBTIMEX pull from SAP ERP Site Master Conversion Information Post-Conversion Operations BP is not transferred, only C/V and address data are extracted from source and sent to target system. BP assigned to site must not be transferred to SAP ERP, because a site cannot be created in SAP ERP if the C/V to which the site should be assigned is part of a BP. The distribution of BPs assigned to a site can be prevented using the BP filter on site role. It is important that BPs that are created independent of the site in the source system first get the site role (BP CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 37 System Object Distribution role with role category BPSITE) assigned from the very beginning. Key mapping is not supported for the C/V and the site. SAP ERP SAP S/4HANA Retail Retail Site-C/V Site-BPC/V Site distribution via WBTIMEX push from SAP ERP BP for C/V is created/updated in target system out of C/V data from source system. BP is created with C/V number (if identical) by default, BP number can be changed via BAdI (BADI_CHANGE_BP_NUMBE R, method CHANGE_BP_NUMBER). Reassignment of C/V to site is not supported in site inbound on SAP S/4HANA. Enhancement of WBTIMEX in SAP ERP required (available with SAP Note 2315007 If WBTIMEX is also used to distribute site data between two SAP ERP systems, this note must also be applied to the target SAP ERP system). Key mapping is not supported for the C/V and the site. SAP S/4HANA SAP S/4HANA Site-BP-C/V BP-C/V Retail BP distribution via DRF Site links of BP-C/V are cleared during initial creation of BP-C/V in target system for BP with site role (BP role with role category BPSITE). Key mapping is supported for the BP and for the C/V. SAP S/4HANA SAP ERP Site-BP-C/V Retail BP-C/V or C/V 38 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. not supported SAP ERP w/ CVI is not supported as target system since BP inbound on Site Master Conversion Information Post-Conversion Operations System Object Distribution SAP ERP requires site to be available in target system. SAP ERP w/o CVI is not supported as target system since ALE inbound for C/V requires site to be available in target system. SAP ERP SAP S/4HANA Site-C/V BP-C/V not supported Scenario is not supported since ALE inbound for C/V requires site to be available in target system. SAP S/4HANA BP-C/V Site-BPC/V BP distribution via DRF Address data of BP-C/V is leading, site address is update in target system (SAP ERP Customizing TWPA-ENA_STD_SRC_SIT not available in SAP S/4HANA). Retail SAP S/4HANA Retail Key mapping is supported for the BP and for the C/V. SAP S/4HANA SAP ERP BP-C/V Site-C/V Retail C/V distribution via ALE (DEBMAS/CR EMAS) Address data handling depending on Customizing TWPA-ENA_STD_SRC_SIT in target SAP ERP system: Address of site is leading, ignore address in target (default). Address of C/V is leading, update site in target. Key mapping is not supported for the C/V. SAP ERP SAP S/4HANA C/V Retail or BP-C/V Site-BPC/V C/V distribution via ALE (DEBMAS/CR EMAS) or BP distribution via DRF Site Master Conversion Information Post-Conversion Operations Address data of BP-C/V is leading, site address is update in target system (SAP ERP Customizing TWPA-ENA_STD_SRC_SIT not available in SAP S/4HANA). Key mapping is not supported for the C/V via ALE distribution, but it is supported for the BP and for the C/V via DRF distribution. CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 39 Distribution Scenario: Export [BP/]C/V out of site System Object Distribution Source Target Source Target Method Remarks SAP S/4HANA SAP S/4HANA Site-BP-C/V BP-C/V BP distribution via DRF Site links of BP-C/V are cleared during initial creation of BP-C/V in target system for BP with site role (BP role with role category BPSITE). Retail Key mapping is supported for the BP and for the C/V. SAP S/4HANA SAP ERP Site-BP-C/V Retail BP-C/V or not supported C/V SAP ERP w/ CVI is not supported as target system since BP inbound on SAP ERP requires site to be available in target system. SAP ERP w/o CVI is not supported as target system since ALE inbound for C/V requires site to be available in target system. SAP ERP Retail SAP S/4HANA Site-C/V BP-C/V not supported Scenario is not supported since ALE inbound for C/V requires site to be available in target system. Distribution Scenario: Import [BP/]C/V into site System Object Distribution Source Target Source Target Method Remarks SAP S/4HANA SAP S/4HANA Retail BP-C/V Site-BPC/V BP distribution via DRF Address data of BP-C/V is leading, site address is update in target system (SAP ERP Customizing TWPA-ENA_STD_SRC_SIT not available in SAP S/4HANA). Key mapping is supported for the BP and for the C/V. SAP S/4HANA 40 SAP ERP Retail BP-C/V CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site-C/V C/V distribution via ALE (DEBMAS/CR EMAS) Address data handling depending on Customizing TWPA-ENA_STD_SRC_SIT in target SAP ERP system: Site Master Conversion Information Post-Conversion Operations System Object Distribution Address of site is leading, ignore address in target (default). Address of C/V is leading, update site in target. Key mapping is not supported for the C/V. SAP ERP SAP S/4HANA Retail C/V or Site-BPC/V BP-C/V C/V distribution via ALE (DEBMAS/CR EMAS) or BP distribution via DRF 4.4.3 Control of Site Distribution 4.4.3.1 Customizing Settings for DRF Address data of BP-C/V is leading, site address is updated in target system (SAP ERP Customizing TWPA-ENA_STD_SRC_SIT is not available in SAP S/4HANA). Key mapping is not supported for the C/V via ALE distribution, but it is supported for the BP and for the C/V via DRF distribution. The following DRF (Customizing) settings are required for the site distribution via DRF: • Define Technical Settings for Business Systems o Define your business systems for distribution o Assign BO type for site (standard: DRF_0021) to business systems o Activate usage of system filter, if required (optional) o Choose output mode different than default, if required (optional, default is direct output) o Define replication via RFC as the communication channel for the BO type and the business system • Define Replication Models o Define your own replication model(s) o Assign a description o Define number of log days (optional) o Activate the replication model once it is finished • Assign outbound implementation for site (standard: SITE_OUT) to replication model(s) • Assign target business systems to replication model(s) Site Master Conversion Information Post-Conversion Operations CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 41 • Assign outbound parameters to replication model(s) o PACK_SIZE_BULK (optional): Number of sites transferred with one RFC (default: one site per RFC). o NUMBER_OF_RETRIES (optional): Number of retries in inbound processing if a BP does not exist yet for a site (default: one trial). o WAIT_TIME_FOR_RETRY (optional): Wait time between retries in inbound processing if a BP does not exist yet (default: retries without additional wait time in between). The relevant Customizing activities for DRF can be accessed by using transaction DRFIMG. More information can be found in Customizing for Logistics - General under Plant Master Settings for Plant Replication General Information. Optional filters for the automatic site distribution (direct output, pooled output via changes transfer and initial output) can be set by using transaction DRFF for each replication model. 4.4.3.2 Customizing Settings of Tables for Site Transport The site distribution via WBTIMEX (push/pull) and DRF (push) is based on the Customizing settings Maintain Tables for Plant Transport (table SITE_DISTR_TABS) of the source system of the data. Customizing path: Logistics - General Plant Master Settings for Plant Replication Maintain Tables for Plant Transport There are two distribution scenarios where a special logic applies with regard to these Customizing settings: • Distribution from SAP ERP to SAP S/4HANA (via WBTIMEX push) Since a BP is created for C/V in the target system which always requires a certain set of data, the tables relevant for C/V and address data maintained in Maintain Tables for Plant Transport in the SAP ERP source system are not relevant for inbound processing in the SAP S/4HANA target system. They are only considered for comparing the current state of C/V data in the source system with the current state of the same data in the target system. • Distribution from SAP S/4HANA to SAP ERP (via WBTIMEX pull or DRF push) Since BP data is not relevant for transfer to the SAP ERP target system but C/V data needs to be transferred to SAP ERP, the tables relevant for C/V and address data are implicitly considered in this case without being included in the Customizing of the SAP S/4HANA source system. 4.4.4 BP Distribution The following DRF settings are relevant for the BP distribution: • Standard BO type: 986 • Outbound implementation: 986_3 • Communication channel: Replication via Services For information about how to set up the SOA Manager for the BP distribution in SAP S/4HANA, see SAP Note 2472030. 42 CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. Site Master Conversion Information Post-Conversion Operations 4.5 Site Archiving There are only minor changes with regard to site archiving in SAP S/4HANA: • Transaction WB06 is still used to set the archiving indicator for a site. It also sets the archiving indicator of the BP on SAP S/4HANA, not only for the C/V. Setting the archiving indicator of a BP-C/V with a site role (role with role category BPSITE) independent of the site is not possible. • Actual archiving of the BP-C/V assigned to a site is only possible after archiving of the site. End of purpose handling of the BP can only start after the site to which the BP is assigned has been archived (as it was already for the C/V assigned to a site). • Sites that are marked for archiving are excluded from distribution. The setting of the archiving flag and the actual archiving must be performed for each system/client. • Departments (table WRF4) and receiving points (table WRF12) are not part of site archiving on SAP S/4HANA because they are only handled as part of the C role of the BP (see chapter 1.4). Site Master Conversion Information Post-Conversion Operations CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved. 43 www.sap.com/contactsap © 2017 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. 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. Please see https://sap.com/corporate/en/legal/trademark.html for additional trademark information and notices.