How to Use a Customer Specific UIBB in MDG Application 'Create Change Request' Author: Matthias Hubert Company: SAP Created on 5th July 2013
TABLE OF CONTENTS 1 INTRODUCTION... 3 2 PREREQUISITES... 3 2.1 Description of business scenario... 3 2.2 Create customer specific UIBB... 5 2.3 UI Configuration... 6 2.4 Personalization... 8 2.5 Maintain Personalization... 9 3 RELATED CONTENT... 11 2
1 INTRODUCTION This tutorial describes how to use a customer specific UIBB in Master Data Governance (MDG) application Create Change Request (WebDynproApplication usmd_crequest_create). 2 PREREQUISITES The tutorial was created using a SAP system which contains Software Component MDG_FND 732 Support Package 5. 2.1 Description of business scenario The business scenario comprises the creation of a change request for a single account using application Create Change Request (WebDynproApplication usmd_crequest_create). The application is based on a Guided Activity Floorplan (GAF). In step 3 of the GAF several tab strips shall be displayed. One of the tabs shall include a customer specific UIBB. Go to transaction pfcg (Role Maintenance). Select role SAP_MDGF_MENU_03 which is delivered by SAP. Then select tab Menu. Following that start application Create Change Request in order to create an entity of type account. 3
Choose a change request type which allows only the processing of a single entity (the definition of the change request type is described in the following chapters). Enter values in all mandatory fields. Then press Next button. Now enter an explanation. Then press Next button. In step 3 click on tab Translation. There a customer specific UIBB which allows the maintenance of descriptions is displayed. 4
The customer specific UIBB corresponds to WebDynproComponent ZMH_USMD_TEXT_TRANSL which is a modified copy of the SAP delivered UIBB (WebDynproComponent USMD_TEXT_TRANSL). This example is now used to explain how to configure the MDG application Create Change Request in order to display a customer specific UIBB in step 3. 2.2 Create customer specific UIBB Use transaction SE80 in order to copy the SAP delivered UIBB USMD_TEXT_TRANSL. The name of the copied UIBB has to begin with Z. In this example the copied UIBB is named ZMH_USMD_TEXT_TRANSL. 5
The caption of the table (CAPTION_1) which contains the descriptions is changed to My own Descriptions : Activate the copied WebDynproComponent ZMH_USMD_TEXT_TRANSL. 2.3 UI Configuration Call transaction mdgimg, Then click on Edit UI Configuration. Select the SAP delivered UI Configuration MDG_0G_FINANCIALS. 6
Then press button Create with Template. Then use the Deep-Copy Mode in order to copy all components of the UI Configuration. Specify the Target Configuration IDs. The IDs have to start with character Z : Now edit the copied application configuration (here ZMH_MDG_0G_FINANCIALS). Select Main Screens of Variant ACCOUNT because the copied UIBB shall be displayed when user processes an entity of type ACCOUNT. Then Go to tab Translation and replace the SAP delivered UIBB USMD_TEXT_TRANSL by the copied UIBB (in this example: ZMH_USMD_TEXT_TRANSL). Then press Save button in order to save the UI configuration (in this example ZMH_MDG_0G_FINANCIALS ). 7
2.4 Personalization The change request type 0G_ACC which is used in this example for MDG application Create Change Request does not refer to a UI Configuration. You can verify this by displaying the change request type in transaction mdgimg. Here you can see that the change request type allows only the processing of a single entity because flag Single Object is selected. When you click on entry Entity Types you can see that field Configuration Name is empty. Therefore the change request type does not refer to a UI Configuration. Furthermore you can see that the change request type allows the maintenance of an entity of type ACCOUNT. This is why the variant ACCOUNT was changed in the UI configuration (see chapter 2.3 UI Configuration ). It would be possible to enter the copied UI Configuration in the change request type. However in this example a different approach is used. When you select a change request type in MDG application Create Change Request which does not refer a UI Configuration the application checks whether a UI Configuration is maintained in the personalization settings. Then that UI Configuration is used by MDG application Create Change Request. As a result the copied UIBB which has been maintained in that UI Configuration is displayed in step 3 of MDG application Create Change Request. 8
2.5 Maintain Personalization Go to transaction pfcg (Role Maintenance). Then select role SAP_MDGF_MENU_03 : Now click on menu entry Create Change Request and then click on button application Create Change Request : in order to execute the 9
Now click on button Change Model in order to access the personalization settings. Select data model 0G because the change request type which is used in this example ( 0G_ACC ) refers to that data model. Assign the copied UI Configuration (in this example ZMH_MDG_0G_FINANCIALS) to that data model. Then click button Save and Apply in order to save the settings. Following that leave application Create Change Request (WebDynComponent: usmd_crequest_create) and start it again in order to make sure that the new personalization settings are used. Now you can execute all steps described in chapter 2.1 Description of business scenario. Then you will see that the customer specific UIBB is displayed in step3 of MDG application Create Change Request. 10
3 RELATED CONTENT SAP Master Data Governance 6.1 documentation: http://help.sap.com/mdg61 SAP Note 1866667, 1864191 11
www.sap.com 2013 SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.