SAP Master Data Governance on SAP S4HANA V18_Part6.pdf

UNIT 3 MDG for Business Partner, Supplier, Customer Lesson 1 Explaining SAP MDG Capabilities for Business Partner 154 Exercise 6: Update ERP Supplier Master Data...

UNIT 3 MDG for Business Partner, Supplier, Customer Lesson 1 Explaining SAP MDG Capabilities for Business Partner 154 Exercise 6: Update ERP Supplier Master Data 165 Lesson 2 Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail 178 Exercise 7: Request and Approve a New Customer via SAP Fiori 245 Exercise 8: Copy Organization and Contact Person in a Change Request and Maintain 257 Bank Details Through IBAN Lesson 3 Explaining Integration Scenarios 269 UNIT OBJECTIVES Explain the SAP MDG capabilities for business partner Explain the functions of MDG for business partner, supplier and customer in detail Explain features and integration scenarios of MDG for business partner, customer, and supplier © Copyright. All rights reserved. 153  Unit 3 Lesson 1 Explaining SAP MDG Capabilities for Business Partner LESSON OBJECTIVES After completing this lesson, you will be able to: Explain the SAP MDG capabilities for business partner SAP MDG Capabilities for Business Partner Figure 117: Establish Best-Quality Master Data to Optimize Business Processes Master Data Governance for Business Partner data offers a central hub-based maintenance of BP master data. To address the key business issues related to such a governance solution for master data, MDG for business partner follows some basic principles that are shared across the domains of MDG: Maintain once, use many. One standardized process to be used by everybody. One standardized user interface for everybody. One standardized set of business logic. In order to fulfill these principles, SAP has built a Master Data Governance solution that offers: 154 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner Central maintenance of master data. Workflow-driven processes that are flexible while ensuring governance and standardization. Harmonized user interface, based upon Enterprise Portal, Business Client, or SAP Fiori launchpad. Data model and business logic follow the best practices of SAP and reuse existing data structures, business validations and various services. I would now like to take you through some of the product's capabilities, that we believe make MDG a very attractive offering - especially for our Business Suite customers. In the course of the next couple of slides we will discuss questions like: What does "out-of-the-box" mean in this context? What are domain-specific applications that come with an "Integrated Object Model"? How do we enable Governance in a way that allows for collaboration and better data quality? How do we support data replication? And how do we allow customers to re-use our (and their own) past investments and do we allow them to extend the standard? Master Data Governance Capabilities: Deliver Out-of-the-Box Figure 118: Deliver Out-of-the-Box What does "out-of-the-box" mean in the context of MDG? Our customers regularly complain about the high cost for implementing and running software solutions. This is also an issue when they are investigating MDM Solutions of our competitors. With SAP MDG we have a clear advantage here, as we offer MDG in way that you can for example co-deploy it with existing SAP ERP system. MDG is easy to consume and ready to run. It comes with standard roles, workflows, pre- defined workflow inboxes for processing change requests, with user interfaces for data maintenance or approval, interfaces for integration to BusinessObjects Data Services and so on. This allows customers to immediately start with a proof-of-concept. And it avoids one of © Copyright. All rights reserved. 155 Unit 3: MDG for Business Partner, Supplier, Customer the probably most costly parts of any other MDM implementation - the reuse of existing processing logic in the back-end. But regardless of its out-of-the-box nature, at the same time MDG is very flexible and this flexibility comes at a low price tag. There is many things you can change by configuration: for example by adapting workflows, or validation rules in BRF+. For many of this adaptations you do not need to change or create any coding. MDG's pre-delivered "best practice" data models are based on the models in the SAP Business Suite and hence are already proven in the SAP business context across multiple applications and industries. To a large extent, MDG behaves like master data applications in the Business Suite already do, especially in the sense that MDG uses the exact same validations that existing master data transactions use. In order to replicate the data from MDG into other systems, it uses established replication mechanisms (like existing IDoc templates) and thus provides out-of-the-box integration mechanism into the Suite, but of course also the means to replicate to non SAP systems (for example using Enterprise Services). Integrated Object Model: Business Partner Figure 119: Integrated Object Model: Business Partner MDG provides a directory of Business Partners (organizations, persons, groups of persons). This directory contains data primarily used for identification (for example: name, address, ID numbers, etc.). The MDG objects like Customer and Supplier will be based on this directory and offer seamless integration with customer-specific data and supplier-specific data. Animation: Integrated Object Model: Business Partner For more information on Integrated Object Model: Business Partner, please view the animation in the lesson Explaining SAP MDG Capabilities for Business Partner, online in the SAP Learning Hub. 156 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner Integrated Object Model: SAP Business Partner Figure 121: Integrated Object Model: SAP Business Partner The Entity type Business Partner is a generic application for business partner management (maintaining organizations, persons and groups of persons). Integrated Object Model: Solutions for Customers, Suppliers, and Business Partner Fundamentals Figure 122: Solutions for Customers, Suppliers, and Business Partner Fundamentals All solutions use the SAP-BP as central anchor for identifying data: Business Partners that are both a customer and supplier are represented by one BP only. MDG-BP as basis for: Customers limiting their governance scope to BP data only. Solutions only being based on SAP-BP (for example: Service Industries). Transition from MDG-BP to MDG-S / MDG-C without disruption. © Copyright. All rights reserved. 157 Unit 3: MDG for Business Partner, Supplier, Customer Animation: Solutions for Customers, Suppliers, and Business Partner Fundamentals For more information on Solutions for Customers, Suppliers, and Business Partner Fundamentals, please view the animation in the lesson Explaining SAP MDG Capabilities for Business Partner, online in the SAP Learning Hub. The MDG-BP Data Model Figure 124: The MDG-BP Data Model The figure illustrates the data model of the MDG-BP. 158 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner The MDG-C Data Model Figure 125: The MDG-C Data Model The figure illustrates the MDG-C Data model. The MDG-S Data Model Figure 126: The MDG-S Data Model The figure illustrates the MDG-S Data model. © Copyright. All rights reserved. 159 Unit 3: MDG for Business Partner, Supplier, Customer Customer/Vendor Integration Figure 127: Customer/Vendor Integration: Example Vendor Integration A Business Partner is always created when a customer or supplier is created. The complex interface of the CVI (Customer/Vendor Integration) contains Business Partner specific data as well as Customer and Vendor specific data. Partially, the data of the Business Partner and Customer/Vendor are redundant (BUT000 against KNA1 & LFA1 data). For instance Name and Address specific attributes are available in both persistencies. Customer or Vendor specific data is routed through the Customer/Vendor specific interface and combined with the Business Partner central data. On commit, the Business Partner and corresponding Customer and/or Vendor is maintained or created. Governance and Collaboration Figure 128: Master Data Governance Capabilities Governance, Collaboration… Part of the solution strategy are principles that represent the people-centric and flexibility goals of the solution. This is not specific to material data, but holds true for the overall SAP MDG solution. In general the processes of the solution can be adapted and tailored to the customer needs. 160 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner This includes: Workflows that are even linear, can be distributed or even started immediately. Clear roles and responsibilities following a task-oriented approach. Process steps can be added, either by reusing existing logic or using a flexible rules- engine. The data in the governance process is separated but transfer to operational database is done in very controlled mode. In summary this fosters flexibility and user acceptance while ensuring governance. Data Quality Figure 129: Data Quality Prevent creation of duplicates for increased effectiveness and efficiency: Checked early and embedded in the process. High detection quality of matching using SAP HANA or Enterprise Search. Validations are: Reuse of existing validation logic. Custom validations can be modeled and programmed (For example, code lists, simple checks, or rules using BRFplus). Integration of rules from MDG Data Quality Management. Address Enrichment: Simple check and selection lists. Integration with content provided by SAP Data Services. Automatically adding Tax Jurisdiction Code reusing existing interfaces/ providers. © Copyright. All rights reserved. 161 Unit 3: MDG for Business Partner, Supplier, Customer Robust Data Replication Figure 130: Robust Data Replication Once you have maintained and approved the master data on the central MDG system, you might want to replicate the data to all SAP and non SAP systems that will need the master data. MDG comes with a framework that supports the organization and execution of this data replication - it is called Data Replication Framework (DRF). With MDG, we of course did not want to invent yet another way to do this replication, but we intended to better support customers in managing the distribution they already do today. Accordingly the DRF framework sits on top of the established replication mechanisms that SAP customers have already been using for a long time (like ALE IDoc) and newer ones like Enterprise Services. The purpose of MDG's DRF is to help our customer keep track of what needs to be distributed where, and what has been distributed successfully or not - regardless of the various replication mechanisms used underneath. In DRF, systems can subscribe to the distribution of master data based on certain filter criteria. In addition MDG can handle things like key mapping (in order to keep different historical keys for existing master data in de-central systems and at the same time only maintain the data once centrally). It also manages value mapping (in order to allow distribution into systems that might have a different understanding of the values of an attribute). DRF also helps in monitoring the distribution, and in resolving errors. Deployment Options Figure 131: Consciously Decide for a Central Hub or Co-Deployment 162 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner The figure illustrates possible deployment options. Customers typically choose to… … create a dedicated master data hub and distribute to all operative systems from there, or … co-deploy with their single instance SAP S/4HANA / ECC (or pick one of their SAP S/ 4HANAs / ECCs as the master for a particular domain) and create and distribute master data from there. Reusability and Extensibility Figure 132: Reusability and Extensibility A major focus of MDG has been put on re-use and extensibility. But re-use does not only mean re-use for us in SAP development. Yes, we are re-using the existing ERP coding to validate entered data and we are often re-using the existing tables to store the active data after approval. But more importantly it is also about re-use for our customers: They can re-use extensions that they have already made to SAP master data in the Business Suite and they can include these extensions directly in the MDG data models. They can re-use the own business logic that they have created in SAP Business Suite for example to validate newly created master data. We know that each and every SAP customer has made extensions to SAP's standard master data model. And that many companies have very specific master data creation and change processes. Accordingly, MDG offers the flexibility and extensibility features to adapt the standard to their needs. The big value proposition here is that we allow our customers to do these extensions and still benefit from MDG out-of-the-box capabilities. © Copyright. All rights reserved. 163 Unit 3: MDG for Business Partner, Supplier, Customer 164 © Copyright. All rights reserved.  Unit 3 Exercise 6 Update ERP Supplier Master Data Simulation: Update ERP Supplier Master Data For more information on Update ERP Supplier Master Data, please view the simulation in the lesson Explaining SAP MDG Capabilities for Business Partner online in the SAP Learning Hub. Business Scenario You are acting as a business user of the purchasing department. You are supposed to maintain supplier master data to change some relevant data of an existing supplier master record with standard ERP mechanism. We are not focusing on Master Data Governance within this exercise. At the end of this exercise you can do the following: Use the search capabilities of SAP ERP Transaction for Supplier master View and Update an existing supplier master data record with standard ERP transaction View the Change history of the supplier master data records Note: In this exercise, when the values include ##, replace the characters with the number that your instructor assigned you. In MDG you can work with the NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. We will use the term Supplier, Vendor and Creditor as synonym in this exercise for the time being. Task 1: Search for Suppliers and Change Them 1. Search for a certain business partner. 2. Update the Address and Bank Data for your BP. Note: Ignore the warning about valid time zones for the current country settings. 3. Maintain the Account Management Information data related to company code 1010. 4. Update the vendor payment transactions. © Copyright. All rights reserved. 165 Unit 3: MDG for Business Partner, Supplier, Customer Use the following information: Note: For the payment methods use F4 value help or the appropriate button. 5. Change the BP role from FI Vendor to Supplier. 6. By switching organization, maintain the partner functions assigned to the purchasing organization 101C. Note: A value is missing to assign the ordering address (OA) as mandatory partner field. Select a valid one, for example: S-MDG400, from value help. Task 2: Check the Updated Supplier To determine what happened, when, and by whom with this master data record, you want to view the details of the performed changes of your supplier. To do this, a function in the extras / environment menu item is available. 1. View the supplier and perform the activities to check all the changes. 2. Display the Vendor master record purchasing organization data details. Task 3: Verify Supplier Data Tables We also want to see the pure database tables in the system used to partially represent the material supplier data records. We use browser transaction SE16. 1. Enter vendor number S-MDGA## into the field of supplier number represented by the field identifier LIFNR. Execute the Search and see the details of the master data record here. 166 © Copyright. All rights reserved.  Unit 3 Solution 6 Update ERP Supplier Master Data Simulation: Update ERP Supplier Master Data For more information on Update ERP Supplier Master Data, please view the simulation in the lesson Explaining SAP MDG Capabilities for Business Partner online in the SAP Learning Hub. Business Scenario You are acting as a business user of the purchasing department. You are supposed to maintain supplier master data to change some relevant data of an existing supplier master record with standard ERP mechanism. We are not focusing on Master Data Governance within this exercise. At the end of this exercise you can do the following: Use the search capabilities of SAP ERP Transaction for Supplier master View and Update an existing supplier master data record with standard ERP transaction View the Change history of the supplier master data records Note: In this exercise, when the values include ##, replace the characters with the number that your instructor assigned you. In MDG you can work with the NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. We will use the term Supplier, Vendor and Creditor as synonym in this exercise for the time being. Task 1: Search for Suppliers and Change Them 1. Search for a certain business partner. a) Call transaction BP to start the update procedure for Supplier / Vendor / Creditor master record. b) On the Maintain Business Partner window, on tab Find enter the following values: Field name Value Find Business Partner By Number © Copyright. All rights reserved. 167 Unit 3: MDG for Business Partner, Supplier, Customer Field name Value Business Partner S-MDGA* If the embedded search is active you can start writing the id of the supplier in the field Business Partner; start with S-MDGA. From the value list, choose your group's supplier id. c) Choose Search. d) In the hit list, double-click your group's supplier id S-MDGA##. 2. Update the Address and Bank Data for your BP. Note: Ignore the warning about valid time zones for the current country settings. a) To enter the maintenance choose the pencil icon in the menu bar. b) To change the role of your BP, use the selection list for the field Change in BP role and choose FI Vendor (Maintained). 168 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner c) Enter the data from the table: Table 9: Transportation Zone Field Value House Number Attach an "A" Transportation Zone 0000000001 Region Berlin d) In the Control tab, enter the data from table. Table 10: Control Tab Field Value Data Origin 0001 e) Press Enter to confirm your change. f) In the Payment Transactions tab, enter the data from the table: Table 11: Bank Record Field Value Country DE © Copyright. All rights reserved. 169 Unit 3: MDG for Business Partner, Supplier, Customer Field Value Bank Key 10040000 (or any other valid one) Search for -for example- “Commerz*” Bank Account 23456## Account Holder Group## g) Press Enter to confirm your changes. 3. Maintain the Account Management Information data related to company code 1010. a) On the Change Organization screen, choose Company Code. b) In the Vendor: Account Management tab, enter the information provided in the table: Table 12: Account Management Information Field Value Sort Key 000 Authorization Group SAP 170 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner 4. Update the vendor payment transactions. Use the following information: Note: For the payment methods use F4 value help or the appropriate button. a) Change to the Vendor: Payment Transactions tab. b) Set the flag for Check Double Invoice. c) For the Payment Methods field, choose the F4 input help and select the options Credit Transfer and SEPA Credit Transfer. Press Enter. © Copyright. All rights reserved. 171 Unit 3: MDG for Business Partner, Supplier, Customer d) Confirm the mask and return to the main window. e) Choose Save. 5. Change the BP role from FI Vendor to Supplier. a) In the Change in BP role, select Supplier. b) Choose Purchasing and switch to the edit mode. Note: c) Enter value 1010 as Purchase Organization and press Enter. d) Specify the ABC indicator and the purchasing group. Field Value ACB indicator B (flag is set) 172 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner Field Value Purchasing Group Z## e) Save your changes. 6. By switching organization, maintain the partner functions assigned to the purchasing organization 101C. Note: A value is missing to assign the ordering address (OA) as mandatory partner field. Select a valid one, for example: S-MDG400, from value help. a) Choose Switch Organization and enter the new purchasing organization 101C. Press Enter. b) Switch to the Partner Functions tab. c) Enter the values and confirm your settings with Enter: Field Name Value PF OA Number S-MDGA## d) Save your changes (or press CTRL+S). © Copyright. All rights reserved. 173 Unit 3: MDG for Business Partner, Supplier, Customer Task 2: Check the Updated Supplier To determine what happened, when, and by whom with this master data record, you want to view the details of the performed changes of your supplier. To do this, a function in the extras / environment menu item is available. 1. View the supplier and perform the activities to check all the changes. a) In transaction BP open Extras → Change History → For This Partner menu. 2. Display the Vendor master record purchasing organization data details. a) In the Select Changed Fields window, select Vendor master record purchasing organization data and choose Continue (Enter). 174 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner b) The Change Documents screen appears, where you can find all related changes. c) Leave the transaction. Task 3: Verify Supplier Data Tables We also want to see the pure database tables in the system used to partially represent the material supplier data records. We use browser transaction SE16. 1. Enter vendor number S-MDGA## into the field of supplier number represented by the field identifier LIFNR. Execute the Search and see the details of the master data record here. a) Start SE16. b) Enter LFA1in the Table Name field. c) Choose the table LIFNR that represents the main table for vendor master. © Copyright. All rights reserved. 175 Unit 3: MDG for Business Partner, Supplier, Customer d) Enter your Business Partner S-MDGA## into the LIFNR field and choose Execute. e) Select the line from the hit list and choose Display. Note: The figure, Vendor and Address, shows some related tables of the vendor master record explaining what their purposes are as a simplified data model. Figure 134: Vendor and Address f) Leave the transaction. 176 © Copyright. All rights reserved.  Lesson: Explaining SAP MDG Capabilities for Business Partner LESSON SUMMARY You should now be able to: Explain the SAP MDG capabilities for business partner © Copyright. All rights reserved. 177  Unit 3 Lesson 2 Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail LESSON OBJECTIVES After completing this lesson, you will be able to: Explain the functions of MDG for business partner, supplier and customer in detail Functions of MDG for Business Partner, Supplier and Customer in Detail In this lesson, we will discuss the following topics: Process Flow User Interface Business Partner Data Data Quality Data Enrichment Data Replication Client Maintenance Processing of Multiple Objects Hierarchies MDG Framework Capabilities Data Protection MDG for FI Contract Account 178 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Process Flow Figure 135: Process Flow Let’s have a look at the typical maintenance process in MDG: The process typically starts when a user requests new master data or changes to existing master data. Or when changes to master data are requested through data flowing into the system through an API. At this moment a so called “MDG Change Request” is created. This change request is the container that keeps all intended changes in a “staging area”, separate from the productive master data. This ensures, that all changes are only used in production after the final approval. Via workflow the change request is then handed over from one person to the next, in order for everyone to contribute their knowledge to complete the master data. The good thing about change requests is also that data can be stored “incomplete” in between. This means, that the company can decide how many people shall contribute and who contributes what – regardless if the SAP ERP could save the master data in the current status. During the maintenance the data is always validated by the system. This validation re-uses existing business logic and the customizing settings in the Business Suite system, but can also integrate various services for data enrichment and cleansing. For example, addresses could be checked for correctness against reference data from an SAP BusinessObjects Data Services system. Companies can also add their own validation rules, like all material numbers need to follow a certain pattern etc. At some point in time the workflow will meet a person for approval of the changes. Only after the approval the data is moved from the staging area into the productive master data and can then be used in business processes and replicated to other systems. Often we see that organizations only put a subset of all master data attributes under central governance. The other attributes can then be enriched in the receiving systems according to the local needs. © Copyright. All rights reserved. 179 Unit 3: MDG for Business Partner, Supplier, Customer When to Use Which Process? Figure 136: When to Use Which Process? The figure illustrates the main usages: These are: Create: Business Partner, Customer, or Supplier does not exist for processing. Change: A search is successful, but the data is incorrect. Block and Unblock: Business Partner, Customer, or Supplier is no longer relevant for processes. Set Flag for Deletion: Business Partner, Customer, or Supplier needs to be deleted in the next archiving run. Animation: When to Use Which Process? For more information on When to Use Which Process?, please view the animation in the lesson Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail, online in the SAP Learning Hub. 180 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Navigation to Create/Change Process Figure 138: Navigation to Create/Change Process The figure illustrates the navigation of the create/change process. Figure 139: Workflow Template: Create Supplier (Distributed) The figure illustrates the workflow of the workflow template for Create Supplier (Distributed). © Copyright. All rights reserved. 181 Unit 3: MDG for Business Partner, Supplier, Customer Figure 140: Workflow Template: Change Supplier (Distributed) The figure illustrates the workflow of the workflow template for Change Supplier (Distributed). Figure 141: Workflow Template: Block/Unblock Supplier (Distributed) The figure illustrates the workflow of the workflow template for Block/Unblock Supplier (Distributed). 182 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Figure 142: Workflow Template: Set Flag for Deletion Supplier (Distributed) The figure illustrates the workflow of the workflow template for Set Flag for Deletion Supplier (Distributed). Figure 143: Workflow Template: Create Customer (Distributed) The figure illustrates the workflow of the workflow template for Create Customer (Distributed). Figure 144: Workflow Template: Create/Change/Block/Set Flag for Deletion Supplier (Simple) The figure illustrates the workflow of the workflow template for Create/Change/Block/Set Flag for Deletion Supplier (Simple). © Copyright. All rights reserved. 183 Unit 3: MDG for Business Partner, Supplier, Customer Figure 145: Workflow Template: Create/Change/Block/Set Flag for Deletion Customer (Simple) The figure illustrates the workflow of the workflow template for Create/Change/Block/Set Flag for Deletion Customer (Simple). Out-of-the-box Workflow templates are: Table 13: Workflow Templates: Out-of-the-Box Title Process Workflow Type Simple Workflow Two-step workflow: SAP Business workflow (Supplier & Customer) Starting with a requestor Rule-based workflow (Busi- Completed by an approver who is ness Partner) also allowed to change / enrich the data. Distributed Workflow Separate process steps for Central da- SAP Business Workflow ta, Financials data, and Sales / Pur- chasing data providing 4-eyes princi- ple for each segment. Process for Fi- nancials data and Sales / Purchasing data run in parallel. Sap Fiori Workflow Three-step workflow with: Rule-based workflow A requester maintaining a limited number of fields. A data steward changing / com- pleting the data Another data steward to finally ap- prove the data. 184 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Figure 146: Workflow Templates Out-of-the-Box The generic workflow template (WS60800086) is the foundation of the RBWF. The different processes are reflected by BRFplus decision tables, which are maintained in the Customizing for each change request type. The combination of this workflow template with the BRFplus decision tables allows you to easily set up many different processes that can be flexibly changed through Customizing. Function in Detail: Processes Figure 147: Function in Detail: Processes The figure illustrates different components of the rule-based workflow. The combination of this customizing and workflow template with the BRFplus decision tables allows you to easily set up many different processes that can be flexibly changed through Customizing. © Copyright. All rights reserved. 185 Unit 3: MDG for Business Partner, Supplier, Customer Workflow-Step Dependent Configuration Figure 148: Enables Flexible UI / Process Design The figure illustrates the steps of the flexible UI/process design. Example: Lean Request UI. UI Configuration Provide different User Interface for each workflow step, based on user task/know-how. Validations Enable or disable checks/enrichments. Example: Switch off required field check and address validation in Lean Request UI. Field Properties Set some data to read-only. Example: Processor for company code 0001 can only maintain these fields. Functions of MDG for Business Partner, Supplier and Customer in Detail: User Interface Figure 149: Homepage for NW Business Client Facts about the homepage for NW Business Client: 186 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail All relevant tasks reachable with one click. Additional analysis / graphics like Change Requests with my participation can be integrated. Easy to configure and personalize. SAP Fiori Launchpad for MDG on SAP S/4HANA Figure 150: SAP Fiori Launchpad for MDG on SAP S/4HANA To access the MDG Governance Tiles for Business Partner, Customer or Supplier you need the SAP template Business Role: SAP_BR_BUPA_MASTER_SPECIALIST All relevant tasks reachable with one click and it is easy to configure and personalize. Workflow Inbox Figure 151: Workflow Inbox Workflow inbox shows Change Requests for which you are the processor. You can personalize this list to your needs. Multiple options are available, for example your can open the Change Request or you can forward it. A preview of the Change Request is available. UI Configurations: Overview of out-of-the-box configurations are © Copyright. All rights reserved. 187 Unit 3: MDG for Business Partner, Supplier, Customer Table 14: Out-of-the-box UI configurations Title Process Configuration BP-UI UI consisting of all data (central data as WD-App: well as organizational data) of a BP, cus- BS_OVP_BPBS_OVP_BPB tomer and / or supplier. Separate pages S_OVP_CU for BP data, central customer / supplier BS_OVP_SPBS_OVP_BP_A data as well as organizational data. LL ERP Customer / UI consisting of all data (central data as WD-App: ERP Vendor well as organizational data) of a customer BS_OVP_BPBS_OVP_CU_C like UI or a supplier. Look & feel very similar to LBS_OVP_SP_VL ERP Customer / ERP Vendor UI in ERP standard. Specialized UIs UI for Sales, Purchasing, Financial special- WD-App: for org. data ists consisting of organizational data for BS_OVP_BPBS_OVP_CU_ one organizational unit. ORGBS_OVP_SP_ORG SAP Fiori UIs Lean UIs to request new customer, suppli- er or Business Partner; intended for busi- ness users with no / limited MDG knowl- edge UIs to approve new or changed cus- tomer / supplier; intended for experts ap- proving MD changes Implemented as SAP Fiori applications running on all devices. UI Configurations: BP Maintenance UI Figure 152: UI Configurations: BP Maintenance UI The figure illustrates the BP single maintenance UI. 188 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Figure 153: UI Configurations: Specialized UI, Maintain / Approve Company Code Data 1/3 This UI contains data of the relevant company code only. There is also a direct navigation from inbox to the UI. You are able to finalize processing of the task on the same page. Figure 154: UI Configurations: Specialized UI, Maintain / Approve Sales Area Data 2/3 This UI contains data of the relevant sales area only. There is also a direct navigation from inbox to the UI. You are able to finalize processing of the task on the same page. © Copyright. All rights reserved. 189 Unit 3: MDG for Business Partner, Supplier, Customer Figure 155: UI Configurations: Specialized UI, Maintain / Approve Purchasing Organization Data 3/3 This UI contains data of the relevant purchasing organization only. There is also a direct navigation from inbox to the UI. Your are able to finalize processing of the task on the same page. UI Configurations: SAP Fiori UI, Lean Request for New Customer Figure 156: SAP Fiori UI, Lean Request for New Customer Business/Process Context: MDG Fiori lean request for customer is meant for a business user who does not have much expertise in MDG master data handling but would still like to request a new MDG Customer. 190 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Such a business user may require a new customer for his product, even while on the move. Rather than sending an email to or calling a master data expert, he/she can raise a request to create new customer by using Lean MDG Fiori application for customer. The figure shows a business partner in the role: general BP. Typical Business Challenges: Manual efforts (emails, phone calls) to create MDG customer when request comes from users either having no access to MDG or have no MDG / SAP knowledge. Dependency on few employees having MDG knowledge to trigger MDG master data creation. High Total Cost of Ownership (TCO) and Total Cost of Development (TCD) for improving the user experience for commonly used business functions of SAP MDG software. Features and Capabilities: An easy, simple and user-friendly UI for users with no master data expertise. Provides a simple, easy-to-use and coherent experience across devices - desktop, tablet, or smartphone. Leverages responsive design, the concept of making apps sensitive to the form factor of devices with a single user interface. Automatic duplicate check when creating a new customer. Attachment functionality to attach a document with request. Supports creation of Organization or Person for a customer. Supports US and European address form layouts for customer. UI Configurations: SAP Fiori UI, Lean Request for New Supplier Figure 157: UI Configurations: SAP Fiori UI, Lean Request for New Supplier 1/2 Typical Business Challenges: Manual efforts (emails, phone calls) to create MDG supplier when request comes from users either having no access to MDG or have no MDG / SAP knowledge. © Copyright. All rights reserved. 191 Unit 3: MDG for Business Partner, Supplier, Customer Dependency on few employees having MDG knowledge to trigger MDG master data creation. High TCO and TCD for improving the user experience for commonly used business functions of SAP MDG software. Features and Capabilities: An easy, simple and user-friendly UI for users with no master data expertise. Provides a simple, easy-to-use and coherent experience across devices - desktop, tablet, or smartphone. Leverages responsive design, the concept of making apps sensitive to the form factor of devices with a single user interface. Automatic duplicate check when creating a new supplier. Attachment functionality to attach a document with request. Supports creation of Organization or Person for a supplier. Supports US and European address form layouts for supplier. Figure 158: UI Configurations: SAP Fiori UI, Lean Request for New Supplier 2/2 Typical Business Challenges: Manual efforts (emails, phone calls) to create MDG business partner when request comes from users either having no access to MDG or have no MDG / SAP knowledge. Dependency on few employees having MDG knowledge to trigger MDG master data creation. High TCO (Total Cost of Ownership) and TCD (Total Cost of Development) for improving the user experience for commonly used business functions of SAP MDG software. Features and Capabilities: An easy, simple and user-friendly UI for users with no master data expertise. Provides a simple, easy-to-use and coherent experience across devices - desktop, tablet, or smartphone. 192 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Leverages responsive design, the concept of making apps sensitive to the form factor of devices with a single user interface. Automatic duplicate check when creating a new business partner. Attachment functionality to attach a document with request. Supports Organization or Person for a business partner creation. Supports US and European address layouts for business partner. UI Configurations: SAP Fiori UI, Lean Request for change of Customer (Flexible Search) Figure 159: UI Configurations: SAP Fiori UI, Lean Request for Change of Customer (Flexible Search) Facts: Uses standard search defined in MDG configuration. Configure search fields visible on main screen. More search options via Filters link. Save predefined filters to reload next time. Navigate to SAP Fiori app to request a new customer. SAP template Business Roles: SAP_MDG_BCR_MYREQUESTS and SAP_MDG_BCR_REQUESTOR_T. © Copyright. All rights reserved. 193 Unit 3: MDG for Business Partner, Supplier, Customer Figure 160: UI Configurations: SAP Fiori UI, Lean Request for Change of Customer (Change Data) Same data available as in SAP Fiori Lean Request for new Customer. Guided step-by-step UI to support unexperienced users: Select data to be changed (for example: Name & Organization Data, Address, Bank Account, etc.). Select action to be executed on selected data (for example: Change selected address). Change data: Possibility to finalize change or add more changes. UI Configurations: SAP Fiori UI, Track My Request Figure 161: UI Configurations: SAP Fiori UI, Track My Request Typical Business Challenges: Manual efforts (emails, phone calls) to contact and check the status of raised request with MDG expert. Dependency on few employees having MDG knowledge to convey the status of MDG master data requests. 194 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail High TCO and TCD for improving the user experience for commonly used business functions of SAP MDG software. Features and Capabilities: An easy, simple and user-friendly UI for users with no master data expertise. Provides a simple, easy-to-use and coherent experience across devices - desktop, tablet, or smartphone. Leverages responsive design, the concept of making apps sensitive to the form factor of devices with a single user interface. Filter and sort functionality for selected requests. Configurable duration for which user wants to see the raised requests. Figure 162: UI Configurations: SAP Fiori UI, Approve Customer The figure illustrates the differences in the Approve UI between a New or Changed Customer. Figure 163: Function in Detail: User Interface UI Configurations: SAP Fiori UI, Approve Supplier The figure illustrates the differences in the Approve UI between a New or Changed Supplier. © Copyright. All rights reserved. 195 Unit 3: MDG for Business Partner, Supplier, Customer Highlight Changes: Field changes Figure 164: Highlight Changes: Field Changes Highlighting of Saved and Unsaved Changes: The system shows saved changes and unsaved changes in two different colors on the UI. If you create an object, the system highlights unsaved changes but no saved changes. If you change an object, the system highlights unsaved changes and those saved changes that have a value that is different from the active value. If you change an edition-based object, the system uses the active value either from the validity period to which the change refers to or from the previous validity period. If the object did not exist before the validity period to which the change refers to or if the object was deleted in the previous validity period, the system highlights unsaved changes but no saved changes. Highlighting of Table Rows: The system also highlights table rows referring to changes that you can only see navigating from a table row to the details of a dependent entity. You can distinguish new rows from changed rows in a table. Tooltip Information: The tooltip of the field shows the previous value. If you change a value several times before saving it, the tooltip displays the active value and the last saved value. Highlight Changes: Table changes, Create / Update Figure 165: Highlight Changes: Table Changes, Create / Update 196 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail The figure illustrates the highlighting capabilities in a list UIBB. Highlight Changes: Table Changes, Delete Figure 166: Highlight Changes: Table Changes, Delete The figure illustrates the highlighting capabilities for deletion in a list UIBB. Highlight Changes: Changes on Detail Pages Figure 167: Highlight Changes: Changes on Detail Pages The figure illustrates the propagation of changes to the first page with the Change Icon. © Copyright. All rights reserved. 197 Unit 3: MDG for Business Partner, Supplier, Customer Undo Changes Figure 168: Undo Changes The MDG system collects all your actions between two client/server roundtrips in MDG Web Dynpro applications in one step that can be undone. You can undo all actions of this step using Undo. You can undo all steps carried out since the last save. After you have used Undo, you can use Redo to recover your actions. After you have saved or deleted an object, you cannot use Undo anymore. After you have canceled your changes, you cannot use Undo anymore. To deactivate this function, set the application parameter DO_START_VETO to X. Animation: Undo Changes For more information on Undo Changes, please view the animation in the lesson Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail, online in the SAP Learning Hub. 198 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Create with Reference Figure 170: Create with Reference Copy Pattern. Two patterns delivered by SAP: Standard: Copy non-individual data only. Complete: Copy all except fields causing business error, for example: do not copy Date of last dunning notice. For more information, see SAP Note 2020896. Copy Segments Figure 171: Copy Segments The figure illustrates how to copy customer/vendor or organization data. © Copyright. All rights reserved. 199 Unit 3: MDG for Business Partner, Supplier, Customer Flexible UI via Configuration / Personalization: Call personalization Figure 172: Flexible UI via Configuration / Personalization: Call Personalization The UI is easy to configure and personalize: Choose Change Page Layout button. The Change Page Layout pop-up appears. Possibilities: - Multi-column (up to 3) design. - Change sequence. - Stacked UIBBs (Tabs). - Expand / compress / suppress blocks. Flexible UI via Context-Based Adaptations (CBA) Figure 173: Flexible UI via Context-Based Adaptations (CBA) 200 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail The CBA schema can be reused and enhanced with custom-defined dimensions. The delivered CBA schema can be substituted by custom-defined schema. Use Customizing: Configure Properties of Change Request Step, if the CBA is not used in the UI Configuration. Integrating Additional Information via BCV Side Panel: Open Side Panel Figure 174: Integrating Additional Information via BCV Side Panel: Open Side Panel The figure illustrates the Side Panel in the Supplier Overview Page (OVP). Integrate Additional Information via BCV Side Panel: Content for MDG Customer Figure 175: Integrate Additional Information via BCV Side Panel: Content for MDG Customer This reuses the generic component Business Context Viewer (BCV). You can easily add content to the Side Panel. © Copyright. All rights reserved. 201 Unit 3: MDG for Business Partner, Supplier, Customer Integrate Additional Information via BCV Side Panel: Content for MDG Supplier Figure 176: Integrate Additional Information via BCV Side Panel: Content for MDG Supplier This reuses the generic component Business Context Viewer (BCV). You can easily add content to the Side Panel. Functions of MDG for Business Partner, Supplier and Customer in Detail: Business Partner Data Figure 177: Data Model Business Partner The figure illustrates general data of the Business Partner Data Model. 202 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Central Data Figure 178: Central Data The figure illustrates the UIBBs for Organization, Persons and Groups. Figure 179: Addresses The figure illustrates the UIBBs for Addresses. Figure 180: Address Usage © Copyright. All rights reserved. 203 Unit 3: MDG for Business Partner, Supplier, Customer The figure illustrates the address usage. Configuration in Implementation Guide → Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Address Determination. Figure 181: Address Versions The figure illustrates different address versions. Configuration in Implementation Guide → SAP NetWeaver → Application Server → Basis Services → Address Management → International Settings → Activate International Address Versions. BP Roles Figure 182: BP Roles The figure explains the different business partner roles. Configuration for CVI in IMG:Cross-Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings. Settings for Customer Integration: Set BP Role Category for Direction BP to Customer Settings for Vendor Integration: Set BP Role Category for Direction BP to Vendor 204 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Bank Accounts Figure 183: Bank Accounts The figure explains the handling of bank accounts. Configuration in IMG: SAP NetWeaver → General settings → Set Countries → Set Country- Specific Checks. Figure 184: Payment Cards The figure illustrates the handling of payment cards. More Information: Data is stored during activation No security measure or masked display SAP-BP: Table BUT0CC, CCARD ERP Customer: tables VCKUN/VCNUM. Masked display and encrypted when saved SAP-BP: Tables BUT0CC, PCA_* ERP Customer: Tables VCKUN/VCNUM. Replication Using ALE (IDoc DEBMAS) or SOA Service BusinessPartnerSUITEBulkReplicateRequest © Copyright. All rights reserved. 205 Unit 3: MDG for Business Partner, Supplier, Customer Identification Numbers Figure 185: Identification Numbers The figure illustrates the UIBB for Identification Numbers. The Single Euro Payments Area (SEPA) is a system of transactions created by the European Union (EU). SEPA harmonizes the way of cashless payments transactions between Euro countries. The International Bank Account Number (IBAN) is an international agreed number of identifying bank accounts across national borders. The IBAN identifies the account of a customer at a financial institution. The SEPA mandate is required to collect a SEPA direct debit. On this mandate, the debtor confirms by signature that you may debit his account. The SEPA mandate is not supported in MDG. It's only available in the back end. Figure 186: Tax Numbers The figure illustrates the UIBB for Tax Numbers. 206 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Figure 187: Tax Numbers: Support of Numbers with More Than 20 Characters The figure illustrates the support of numbers with more than 20 characters Multiple Industries per BP Figure 188: Maintain Multiple Industries per BP Precondition: Define industry mapping for CVI in IMG: 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. Settings for Vendor Integration Field Assignment for Vendor Integration → Assign Attributes → Assign Industries. © Copyright. All rights reserved. 207 Unit 3: MDG for Business Partner, Supplier, Customer BP Relationships Figure 189: BP Relationships The figure illustrates the UIBB of Relationships. Figure 190: BP Relationships, Add Relationship in UI The figure illustrates how to add relationships to existing or new business partners. Figure 191: BP Relationships, Time Dependency The figure illustrates the time dependency of the relationships. 208 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Time dependency to be activated by customer, this requires manual action, for more information see SAP Note 2249877. Figure 192: BP Relationships, Specialized UI for Contact Person Relationships The figure illustrates the UIBB for Contact Person Relationship. Business Background Relevant contact person information distributed across several pages (person data, relationship data, workplace address). The requirement was to merge most relevant data on one page, decrease the navigation, and so optimize usability. Figure 193: BP Relationships, Specialized UI for Contact Person Relationships The figure illustrates the UIBB for Contact Person Relationship. © Copyright. All rights reserved. 209 Unit 3: MDG for Business Partner, Supplier, Customer Data Model ERP Customer / ERP Vendor Figure 194: Data Model ERP Customer / ERP Vendor The figure illustrates the ERP Customer/ERP Vendor specific data of the Business Partner Data Model. Figure 195: Assign ERP Customers / ERP Vendors, Use Cases and Concept The figure illustrates the use cases and concept to assign multiple ERP customers/vendors to one business partner. 210 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Assign ERP Customers / ERP Vendors, Implementation Figure 196: Assign ERP Customers / ERP Vendors, Implementation The figure illustrates the UI to maintain multiple ERP customers/vendors to one business partner. Address Usage Figure 197: Assign ERP Customers / ERP Vendors, Use of Multiple BP Addresses (Use Case) The figure illustrates an example for one business partner having 3 addresses. © Copyright. All rights reserved. 211 Unit 3: MDG for Business Partner, Supplier, Customer Figure 198: Assign ERP Customers / ERP Vendors, One BP Per Address The figure illustrates that Sold-to-party, Bill-to-party and Payer are using the same address in Berlin, while Ship-to-party uses the other two addresses in Hamburg and Frankfurt. Figure 199: Assign ERP Customers / ERP Vendors, One BP Per Legal Entity For the above example, the figure shows the implementation with 3 business partners, one business partner per address. 212 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Assign ERP Customers / ERP Vendors Figure 200: One BP Per Legal Entity, Use Interface Concept of one Business Partner with multiple addresses in the MDG UI. Note: In MDG on SAP S/4HANA 1709 / MDG 9.1 activated ERP Customers can only be referred within Partner Functions. Eventually, the process will need to be split into two consecutive Change Requests. Figure 201: Create BP with Assignments and Partner Functions in One Change Request Within one change request, you are now able to create a Business Partner with multiple ERP Customers / ERP Vendors and maintain partner functions between these ERP Customers / ERP Vendors. © Copyright. All rights reserved. 213 Unit 3: MDG for Business Partner, Supplier, Customer General Data (Customer and Vendor) Figure 202: General Data (Customer and Vendor) Data will be stored in tables KNA1 / LFA1 during activation and Replication via ALE and SOA Service is possible. Figure 203: General Data (Customer and Vendor), Select Account Group During Creation Business Background When first assigning an ERP Customer / ERP Vendor to a Business Partner, the account group was automatically derived according to CVI Configuration. The requirement is to enable users to select another account group manually. 214 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Figure 204: Documents (Customer and Vendor) Replication: Document as well as link to ERP Customer / ERP Vendor via ALE (IDoc DOCMAS) or Link to ERP Customer / ERP Vendor via SOA Service BusinessPartnerSUITEBulkReplicateRequest Lean Classification (Customer and Vendor), Motivation The Motivation for Lean Classification (Customer and Vendor) is based on: Feedback for MDG-M Classification (up to MDG 9.0 and SAP S/4HANA 1610): - UI-related feedback: Classes and characteristics are not on same page. User should not see a difference between normal attributes and classification. More usable UI, possibility to adapt the UI. - Function-related feedback: Integration of derivations missing. Simultaneous display and change of classification is not supported (authorizations for display not possible). Simultaneous processing of different class types or classes using a parallel change request is not possible. Missing support in other MDG applications (up to MDG 9.0 and SAP S/4HANA 1610): - No support for classification in MDG Consolidation. - No support for classification for Supplier and Customer in MDG Central Governance. Lean Classification (Customer and Vendor), Concept: For Customer, Supplier and Material: © Copyright. All rights reserved. 215 Unit 3: MDG for Business Partner, Supplier, Customer - MDG Single-Object Maintenance UI. - MDG Consolidation. Simplified UIs Mass-enabled API Simplified back-end features to reduce complexity. Class assignment and characteristics valuation work like normal entities in data model. Lean Classification (Customer and Vendor), Features and Restrictions are: Supported Features: - Derivations using BAdI CROSS_ENTITY_BADI (incl. defaulting for class types and classes). - Checks using BRFplus. - Authorizations (incl. display authorization). - Change Documents. - Multiple class types and class assignments. - Characteristic values: Single or multiple values, additional values, intervals, mandatory checks (required entry). Restrictions (not supported): - Object dependencies (preconditions, actions, selection condition, procedures). - Overwriting of characteristic values and overwriting of inherited values. - Engineering Change Number. You can find detailed information about included/excluded features in SAP Note: 2479869. Figure 205: Lean Classification (Customer and Vendor), User Interface Lean Classification (Customer and Vendor), Further Details are: Configuration / Master Data: 216 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail - Based on Customizing configuration of classification system to, for example, maintain object types and class types (see Customizing under Cross-Application Components → Classification System). - Based on master data of classification system to for example: maintain characteristics and classes (see SAP Menu under Cross-Application Components → Master Data). Consolidation: - Can be consolidated like other entities. - See separate presentation about consolidation. Data Activation / Replication: - Classification data will be stored in classification system during activation: Object Type LFA1 for ERP Vendor. Object Type KNA1 for ERP Customer. - ALE replication via standard IDoc CLFMAS. - SOA Service replication via BP service BusinessPartnerSUITEBulkReplicateRequest. Texts (Customer and Vendor) Figure 206: Texts (Customer and Vendor) You can now enter explanatory texts for ERP Customers and ERP Vendors for different text types and for different languages. © Copyright. All rights reserved. 217 Unit 3: MDG for Business Partner, Supplier, Customer Unloading Points (Customer) Figure 207: Unloading Points (Customer) Multiple unloading points can be maintained per ERP Customer. Company Code Data (Customer and Vendor) Figure 208: Company Code Data (Customer and Vendor) Screen Layout per Company Code supported in IMG: Financial Accounting (New) → Accounts Receivable and Accounts Payable → Customer Accounts → Master Data → Preparations for Creating Customer Master Data → Define Screen Layout per Company Code (Customers). Similar path for ERP Vendor. 218 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Dunning Areas (Customer and Vendor) Figure 209: Dunning Areas (Customer and Vendor) Data will be stored in tables KNB5 / LFB5 during activation and replication via ALE and SOA Service is possible. Withholding Tax Types (Customer and Vendor) Figure 210: Withholding Tax Types (Customer and Vendor) Activate Extended Withholding Tax per Company Code in IMG: Financial Accounting (New) → Financial Accounting Global Settings (New) → Withholding Tax → Extended Withholding Tax → Company Code → Activate Extended Withholding Tax. Data will be stored in tables KNBW / LFBW during activation and replication via ALE and SOA Service is possible. © Copyright. All rights reserved. 219 Unit 3: MDG for Business Partner, Supplier, Customer Figure 211: Sales Area Data (Customer) Data will be stored in tables KNVV during activation and replication via ALE and SOA Service is possible. Partner Functions (Customer) Figure 212: Partner Functions (Customer) Data will be stored in tables KNVP during activation and replication via ALE and SOA Service is possible. Tax Indicators (Customer) Figure 213: Tax Indicators (Customer) Data will be stored in table KNVI during activation and Tax Indicators can be replicated via ALE and SOA Service. 220 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Purchasing Organization Data (Vendor) Figure 214: Purchasing Organization Data (Vendor) Data will be stored in tables LFM1 during activation and replication via ALE and SOA Service is possible. Different Purchasing Organization Data (Vendor) Figure 215: Different Purchasing Organization Data (Vendor) Data will be stored in table LFM2 during activation and replication via ALE and SOA Service is possible. © Copyright. All rights reserved. 221 Unit 3: MDG for Business Partner, Supplier, Customer Partner Functions (Vendor) Figure 216: Partner Functions (Vendor) Data will be stored in table WYT3 during activation and replication via ALE and SOA Service is possible. Functions of MDG for Business Partner, Supplier and Customer in Detail: Data Quality Figure 217: Functions in Detail: Data Quality: Search Overview Search - a first step to data quality. 222 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Figure 218: Functions in Detail: Data Quality: Search Capabilities Consistent search UI containing all search capabilities: Search methods are easy to configure, more search methods can be added. Drop-down lists of available fields and operators. Add and remove search criteria (AND combination of multiple parameters). Search criteria can be saved using a descriptive name for quick and easy reuse (as a global or private variant). Search for hits within active and inactive data. One or more business partners can be selected to find related change requests. Search Options Figure 219: Functions in Detail: Data Quality: Search Options The figure illustrates the different search options. © Copyright. All rights reserved. 223 Unit 3: MDG for Business Partner, Supplier, Customer Enterprise Search Figure 220: Functions in Detail: Data Quality: Enterprise Search Using Enterprise Search with MDG provides: Free-text search across many attributes. Attribute-based search in specific fields only. Search active data only to limit search to active area. Fuzzy search checkbox to enable error-tolerant search mode. SAP HANA-based Search Capabilities Figure 221: SAP HANA-based Search Capabilities The figure explains possible entries of the search. 224 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Duplicate Check, Validations, Address Enrichment Figure 222: Duplicate Check, Validations, Address Enrichment Prevent creation of duplicates for increased effectiveness and efficiency: Checked early and embedded in the process. High detection quality of matching using Enterprise Search or HANA-based search. Validations: Reuse of existing validation logic in SAP S/4HANA. Custom validations can be modeled and programmed (for example: code lists, simple checks, or modeled rules via BRF+). Address Enrichment: Simple check and selection lists. Integration with content provided by SAP Data Services. Automatically adding Tax Jurisdiction Code reusing existing interfaces / providers. Duplicate Detection via SAP HANA-based Search Figure 223: Duplicate Detection via SAP HANA-Based Search © Copyright. All rights reserved. 225 Unit 3: MDG for Business Partner, Supplier, Customer The figure illustrates the UIBB for duplicate check using SAP HANA-based search. Checks and Derivations using BRFplus Figure 224: Checks and Derivations Using BRFplus For general information on how to work with BRFplus, see: SAP Help Portal and SAP Documentation. Process Flow in Data Quality Management Figure 225: Process Flow in Data Quality Management The figure illustrates the typical process flow in data quality management. 226 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Data QualityMDQ Rule Adapter in Central Governance Figure 226: Data QualityMDQ Rule Adapter in Central Governance As a master data steward, I want to use existing data quality rules for quality evaluation in change request processing as well. Solution: Integration of Master Data Quality rules in Central Governance Change Request Processing: Enable additional usage of rule for check in change request. Reuse of the same rule implementation. Flexibility to independently enable rules for evaluation and check. Open for custom implementation in the access class of MDG, central governance for custom objects. Functions of MDG for Business Partner, Supplier and Customer in Detail: Data Enrichment Data Enrichment: Overview: Data Enrichment is a business service based on SAP Cloud Platform that onboards partner data for easy consumption to SAP systems. SAP will provide a seamless consumption of external data as well as enrichment of existing data sets in customers’ enterprise management systems. Commercial Model: - Pay-per-use model for Content, sold via SAP App center, customer will have direct contract with content providers. - Flat price model for Connector to SAP system sold on SAP Digital store. Data Enrichment: Business Need External data that enriches "latent data" in customer systems is a key element of driving business; having such data available seamlessly is a key concern for driving digital transformation. © Copyright. All rights reserved. 227 Unit 3: MDG for Business Partner, Supplier, Customer Customers are asking SAP to provide a streamlined approach to on-board third-party data into SAP S/4HANA (and potentially other non SAP systems). This would be an attractive alternative to the traditional professional services approach. Content partners (providing third-party data) are asking SAP to help them to connect to existing and new SAP S/4HANA customers. For more information on 'SAP S/4HANA Cloud for Data Enrichment' see here: https://blogs.sap.com/2018/12/17/sap-s4hana-cloud-for-data-enrichment/ https://help.sap.com/viewer/product/Cloud_Platform_Data_Enrichment/1.4/en-US? task=discover_task https://www.sapstore.com/solutions/40106/SAP-Cloud-Platform-Data-Enrichment Figure 227: Enrichment in MDG, Central Governance via SAP Cloud Platform Data Enrichment The figure illustrates the UIBB for the data enrichment using SAP S/4HANA Cloud for Data Enrichment. 228 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Functions of MDG for Business Partner, Supplier and Customer in Detail: Data Replication Figure 228: Data Replication, Overview Animation: Data Replication, Overview For more information on Data Replication, Overview, please view the animation in the lesson Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail, online in the SAP Learning Hub. Once you have maintained and approved the master data on the central MDG system, you might want to replicate the data to all SAP and non SAP systems that will need the master data. MDG comes with a framework that supports the organization and execution of this data replication - it is called Data Replication Framework (DRF). With MDG, we of course did not want to invent yet another way to do this replication, but we intended to better support customers in managing the distribution they already do today. Accordingly the DRF framework sits on top of the established replication mechanisms that SAP customers have already been using for a long time (like ALE IDoc) and newer ones like Enterprise Services. The purpose of MDG's DRF is to help our customer keeping track of what needs to be distributed where, and what has been distributed successfully or not - regardless of the various replication mechanisms used underneath. In DRF, systems can subscribe to the distribution of master data based on certain filter criteria. In addition MDG can handle things like key mapping (in order to keep different historical keys for existing master data in de- central systems and at the same time only maintain the data once centrally). It also manages value mapping (in order to allow distribution into systems that might have a different understanding of the values of an attribute. DRF also helps in monitoring the distribution, and in resolving errors. © Copyright. All rights reserved. 229 Unit 3: MDG for Business Partner, Supplier, Customer Replication Status Information Figure 230: Replication Status Information Replication Status Information: Overview of replication status per customer / supplier to all relevant target systems. Status per target system: - Green: OK. - Yellow: OK, but answer from target system still pending. - Red: Error occurred. Detailed log per target system available. Explicit Selection of Target Systems Figure 231: Explicit Selection of Target Systems Activate option per Change Request type in IMG under Master Data Governance → Central Governance → General Settings → Process Modeling → Change Requests → Create Change Request Type. 230 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Pooled or Direct Replication Figure 232: Pooled or Direct Replication You can decide if you want to enable direct replication or pooled replication for each combination of business object and target system. With direct replication, the messages are sent with the activation of the change request. With pooled replication, the messages are sent periodically using the DRF change pointer: Direct Output Changes are directly transferred to a target system. 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 report Execute Data Replication (RDRF_MESSAGE_OUT) for the relevant replication models. Functions of MDG for Business Partner, Supplier and Customer in Detail: Client Maintenance Figure 233: Client Maintenance: Process Steps The figure illustrates the required steps in client maintenance. Search on the Hub A new synchronous SOA service will be offered to provide hub search functionality on the client. In the client system, an additional search help for business partner search on the hub has to be integrated in the existing search helps of the corresponding application. © Copyright. All rights reserved. 231 Unit 3: MDG for Business Partner, Supplier, Customer The search requester search needs to have a user on the hub system as well to perform the relevant authority checks by propagating the user data from the client system to the hub using the service. The search result list containing the objects (passed by the authorization check) is sent to the client system and the search result list is shown in the client UI. The result list on the client contains both local hits and global hits not locally available. In an additional column, the records are marked accordingly. If the record is not locally available, the selection of the record is not possible. Only the function “create local copy” will be possible. In the CRM web UI, a link can be configured to navigate from the result list to the display customer UI on the hub. In the case where fuzzy search capabilities are available on the hub also, the score is displayed in the search result list (which will always be 100% for local hits not available globally). To enable the customer to include the global search also in clients of earlier releases, a RFC- enabled function module will be offered on the hub. ERP Customer: Search on Hub and Copy From Hub Figure 234: ERP Customer: Search on Hub and Copy From Hub The figure illustrates the UI of the F/4 Help in the client systems to find also the customers in the MDG Hub system. 232 © Copyright. All rights reserved.  Lesson: Explaining the Functions of MDG for Business Partner, Supplier and Customer in Detail Maintenance on Hub and on Client in Unison Figure 235: Maintenance on Hub and on Client in Unison Maintenance on MDG Hub 1. Maintain data on MDG Hub: The user maintains a Business Partner (BP, means customer or supplier) on the MDG Hub. Automatically, a Change Request (CR) is created. After finalizing all steps to maintain / approve data, the BP is activated on the MDG Hub. 2. Replicate data to client systems: As the last workflow step, the replication of the activated data is triggered. Replication can be executed to SAP systems and non SAP systems using the SOA Service or ALE. Client systems give feedback to MDG on whether the import of the data was successful. Maintenance on Client 1. Maintain data on Client 1: