SAP How-To Guide. Master Data Governance for Material. How To... Extend MDG-M User Interface. Applicable Releases: EhP6, MDG 6.1, MDG 7. - PDF

Please download to get full document.

View again

of 60
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Information Report
Category:

Comics

Published:

Views: 368 | Pages: 60

Extension: PDF | Download: 7

Share
Related documents
Description
SAP How-To Guide Master Data Governance for Material How To... Master Data Governance for Material Extend MDG-M User Interface Applicable Releases: EhP6, MDG 6.1, MDG 7.0 Version Copyright 2015
Transcript
SAP How-To Guide Master Data Governance for Material How To... Master Data Governance for Material Extend MDG-M User Interface Applicable Releases: EhP6, MDG 6.1, MDG 7.0 Version Copyright 2015 SAP AG. 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, 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 in several other countries all over the world. 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. Document History Document Version Description 1.00 First official release of this guide 1.10 More UI Extensions 1.20 Hide Buttons, Configuration Search UI 1.30 Example coding 1.40 More UI Extensions 1.50 Small corrections 1.60 Chapter 4.3 Postprocessing after Model Change 1.70 Small corrections 1.80 Chapter 6.5 Launch Material UI with PFCG Menu Entry 1.90 Update chapter 5.5, Update , Small corrections 2.00 Chapter Hide Fields 2.10 Corrections in chapter 5.7, chapter , chapter and new chapter Make CR Type mandatory 2.20 Update of chapter 5.12 and new chapter Update chapter Update chapter 4.2 and chapter Update chapter 5.5, small updates Typographic Conventions Type Style Example Text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Icons Icon Description Caution Note or Important Example Recommendation or Tip Example text Example text Example text Example text EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER. Table of Contents 1. Business Scenario Background Information More Information Extension of the Governance Scope Additional Data: Stored in Data Model MM Fields from Backend (Mapped; Reuse) Additional Fields (Not Mapped) Temporary Fields (Transient) Permanent Fields (Flex Entity) Additional Data: Not Stored in Data Model MM Feeder Enhancement Enhance SPI Model MDG_MAT Steps for SPI Enhancement Example of a New Node Mandatory Postprocessing after Model Change UI Extension Delivered Application Configuration Context-Based Adaptation (CBA) Adaptation Schema Example of Context-Based Adaptation (CBA) Custom UI Configuration Customizing for Custom UI Configuration Assignment of UI to the Complete Process Assignment of UI to Different Steps Navigation Logic to Target UI Enhance Initial Screen Make Change Request Type Mandatory New Form UIBBs Field Properties Customizing: Configure Properties of CR Step Enhancement Spot USMD_ACC_FLD_PROP_CUST_DEP_SET Hide Fields Setup of T130F BAdI USMD_ACC_FLD_PROP_CUST_DEP_SET Enhancement Spot /PLMB/ES_SPI (SPI BAdI) Leading Zero s for NUMC Additional Buttons Buttons to Influence the Workflow Other Additional Buttons Implementation of the Logic... 26 5.8 Hide Buttons Change Request Buttons Material UIBB Buttons Page of Type DIALOG BOX New Feeder Example: Restrict Values Displayed in Dropdown List Example: Restrict Values Displayed in the Input Help Example Coding to build up Value List for Dropdown List and Value Help Example: Derive Material Number Example: OVS Adjustment of Header Line Search Help Sequence (in OVP and Search UI) Type Ahead and Field History Other UI hints Set OVP UI immediately in EDIT Search UI: Hide Classification Governance and Convenience API and Model EXT Launch Material UI with Custom Coding Launch Material UI with PFCG Menu Entry (without Initial Screen) Scrolling Behaviour of ATS-List (Component FPM_LIST_UIBB_ATS) Provide Description in Logon Language Enhance Copy functionality Copy all Plant Assignments Copying Template Filter Template Data During Copying Tabbed UI Change Label of Field New Layout for the Classification UIBB with Highlighting Changes... 54 1. Business Scenario SAP Master Data Governance for Material (MDG-M) provides business processes to find, create, change, and mark material master data for deletion. It supports the governance of material master data on a central hub and the distribution of material master data to connected operational and business intelligence systems. The processes are workflow-driven and can include several approval and revision phases, including collaboration between all users participating in master data maintenance. This guide describes how to extend the UI of Master Data Governance for Material to display additional data. Please be aware that Pre-, Post-, and Override-Exists must be verified after upgrading to another support package. 2. Background Information MDG 6.1 help: MDG 7.0 help: 3. More Information Check if the following SAP Notes are required and implemented in the system: Incorrect required field check for execution via BAdI USMD_ACC_FLD_PROP_CUST_DEP_SET Removes the following message in FPM OVP configuration: Connector class /PLMU/CL_FRW_W_CONN_TO_BOL does not match model namespace In this note, you will find some FAQs for Master Data Governance in EhP6 (Migration of EhP5 UI-BAdI) How to Create, Enhance and Adapt FPM Applications How to enable field input history for MDG applications Navigation Generic OVS Help for Flex Entities , , , and Hide fields Performance: Use parameter FPM_IGNORE_WIRE_SOURCE Performance: Use parameter FPM_IGNORE_WIRE_SOURCE Enhancement of Master Data Governance Content in EHP6: MDG Extensibility Guides on SDN: How to Create, Enhance, and Adapt Floorplan Manager Applications (FPM): 1 4. Extension of the Governance Scope Additional data can be displayed or maintained with an extended UI. The data can be stored in Data Model MM. See also Extensibility Options for SAP Master Data Governance for Material in topic Extensibility (http://scn.sap.com/docs/doc-7858#section2). 4.1 Additional Data: Stored in Data Model MM Fields from Backend (Mapped; Reuse) Examples: Additional Fields (including z-fields) from MARA, MARC etc. Necessary Steps: Extend Model (Reuse entity) including generated structures for Field Properties and Reuse Active Area. SMT Mapping (mandatory to PP, SA) UI Configuration Additional Fields (Not Mapped) Additional fields could be helper fields, info fields, and calculated fields Temporary Fields (Transient) Enhancement of single fields. Examples: Storage: Calculate volume of dimensions of alternative UoM and show result on UI. Calculation of volume is done in BRF+ or BAdI Derivation (BAdI USMD_RULE_SERVICE, Method DERIVE_ENTITY Derivation of Data for a Master Record) Net weight for alternative UoM. Calculation of net weight is done in BRF+ or BADI Derivation Only in Staging Value lost after activation of material Necessary Steps: Extend data model (Reuse Area blank) UI Configuration in an existing UIBB or a new UIBB Field property. The standard SAP behavior of field property is input-enabled. To change the field property, use enhancement spot usmd_acc_fld_prop_cust_dep_set (Method MODIFY_FLD_PROP_ATTR Change Field Attributes). The Prerequisite SAP Note is SAP does not recommend this type of data modeling because it contradicts the concept of governance (value loss, mapping problems). You should use the Flex Entity or chapter Feeder Enhancement Example: 2 You want to display field MCOD1 from table LFA1 in the UIBB of entity MARAPURCH without enhancing the data model MM. Necessary Steps: Create a new feeder. The feeder should inherit from the original feeder, which is used for entity type MARAPURCH.. From MDG 7.0 this is class CL_MDG_BS_MAT_FEEDER_FORM_MAT. For earlier MDG releases, the class depends on the notes you have implemented (relevant notes: , ). Without these notes, class CL_MDG_BS_MAT_FEEDER_FORM_MARA is used. Create a subclass in customer namespace. In this class, redefine the method /PLMU/IF_FRW_G_FIELD_DEF~CHANGE_FIELD_DEFINITION. Insert the additional fields in the catalog (internal table CT_DEFINITION). Redefine the method /PLMU/IF_FRW_G_AFTER_GET_DATA~AFTER_GET_DATA. Check your node name MARA and your entity type MARAPURCH for which the enhancement is valid. With MO_CONTEXT- GET_ATTRIBUTE you get any value from the UIBB, then you must read the field MCOD1 from the data base table LFA1 and with MO_CONTEXT- SET_CONTEXT you can write the value to the UIBB. Reset the shared memory Transaction : MDGIMG Path: Master Data Governance for Material Clear Shared Memory Buffer Change your UIBB Manufacture Parts with CBA. Replace the new feeder class in your configuration. Add the new field to the UIBB. The extension is only effective in the UIBBs in which the feeder is used. Enhance SPI Model MDG_MAT Permanent Fields (Flex Entity) Enhancement of a set of fields and/or a complete entity. Examples: Custom Organization Hierarchy Custom Material Hierarchy Fields for calculating material description Necessary Steps: Extend data model (new flex entity; Reuse Area = MDG) including generated structures for Field Properties and Reuse Active Area UI Configuration using a new UIBB Add wiring details (prerequisite SAP Note is ) For flex entities with a 1:1 relationship to a MARA entity ( For example, the entity MATERIAL), to use the mapping functions you have to add the mapping class to the wiring definition in your component configuration: o Open the OVP component configuration o Mark the wiring entry of the configuration that contains the flex entity o Enter CL_MDG_BS_MAT_MATNR2MATERIAL (new mapping class) in the field Mapping Class at the wiring attributes and choose 'Save' Field property. The standard SAP behavior of field property is input-enabled. To change field property, implement enhancement spot usmd_acc_fld_prop_cust_dep_set (Method 3 Storage: MODIFY_FLD_PROP_ATTR Change Field Attributes or MODIFY_ENTITY_PROPERTIES Change Entity Properties). Prerequisite SAP Note is In Staging Kept after activation 4.2 Additional Data: Not Stored in Data Model MM There are two ways of implementing additional data, which is not stored in the data model MM: Feeder Enhancement (UI-related) SPI Enhancement (Backend-related) Feeder Enhancement Example: You want to display field MCOD1 from table LFA1 in the UIBB of entity MARAPURCH without enhancing the data model MM. Necessary Steps: Create a new feeder. The feeder should inherit from the original feeder, which is used for entity type MARAPURCH.. From MDG 7.0 this is class CL_MDG_BS_MAT_FEEDER_FORM_MAT. For earlier MDG releases, the class depends on the notes you have implemented (relevant notes: , ). Without these notes, class CL_MDG_BS_MAT_FEEDER_FORM_MARA is used. Create a subclass in customer namespace. In this class, redefine the method /PLMU/IF_FRW_G_FIELD_DEF~CHANGE_FIELD_DEFINITION. Insert the additional fields in the catalog (internal table CT_DEFINITION). Redefine the method /PLMU/IF_FRW_G_AFTER_GET_DATA~AFTER_GET_DATA. Check your node name MARA and your entity type MARAPURCH for which the enhancement is valid. With MO_CONTEXT- GET_ATTRIBUTE you get any value from the UIBB, then you must read the field MCOD1 from the data base table LFA1 and with MO_CONTEXT- SET_CONTEXT you can write the value to the UIBB. Reset the shared memory Transaction : MDGIMG Path: Master Data Governance for Material Clear Shared Memory Buffer Change your UIBB Manufacture Parts with CBA. Replace the new feeder class in your configuration. Add the new field to the UIBB. The extension is only effective in the UIBBs in which the feeder is used Enhance SPI Model MDG_MAT Examples: Read data from MARA and show it on the UI Input-enabled new field for administrative purposes (completely independent from MDG) 4 Steps for SPI Enhancement Definition Enhance SPI Metadata with fields that are not stored in data model MM. Use SPI-BAdI (enhancement spot /PLMB/ES_SPI: BADI /PLMB/EX_SPI_METADATA method ENRICH_NODE_DEFINITION) to enhance the list of nodes for getting the additional fields. To check if the node is added to the meta data of the SPI as expected, use TX MDB (Metadata Browser) with the ABB-ID MDG_MAT To display the new fields, enhance the UI configuration with a new UIBB. Depending on the requested features, an existing PLM UI feeder (e.g. /PLMU/CL_FRW_G_FEEDER_FORM) or a MDG Material feeder (For example: CL_MDG_BS_MAT_FEEDER_FORM) can be reused. If their features are not sufficient, you must implement your own feeder (if possible it should inherit from one of the existing ones) Include the new UIBB in the used UI configuration(s) and adapt the wiring accordingly. In case the wiring doesn t exist or is incorrect, the new UIBB will remain empty and all its fields will be read-only Runtime Storage: Use SPI enhancement spot /PLMB/ES_SPI with BADI /PLMB/EX_SPI_APPL_ACCESS and implement method BEFORE_RETRIEVE Before Service Provider RETRIEVE call to skip the standard retrieval for the added node. Use SPI enhancement spot /PLMB/ES_SPI with BADI /PLMB/EX_SPI_APPL_ACCESS and implement method AFTER_RETRIEVE After Service Provider RETRIEVE call to determine the data to be displayed. If the method returns at least one empty entry then the field is inputenabled. If the method returns nothing then the fields are empty and read-only. Optional: Use SPI enhancement spot /PLMB/ES_SPI with BADI /PLMB/EX_SPI_PROPERTIES_ACCESS and implement method GET_PROPERTIES Get Properties call to change the field property, for example to read-only. Optional: Use SPI enhancement spot /PLMB/ES_SPI with BADI /PLMB/EX_SPI_APPL_ACCESS and implement method BEFORE_UPDATE Before Service Provider UPDATE call to disable standard coding and use SPI enhancement spot /PLMB/ES_SPI with BADI /PLMB/EX_SPI_PROPERTIES_ACCESS and implement method AFTER_UPDATE After Service Provider UPDATE call to save the field value UI Configuration Usage: custom UIBB which could be used together with MDG_M UIBBs on OVP, detail screen or pop-up Not in Staging Independent of activation Customer or backend tables Example of a New Node To extend the UI with fields that are not in the data model, you have to introduce new nodes in the context at design time and runtime. Usually, the nodes are derived from the entities of the data model; here, we define them in SPI. This is done in a BAdI extension of the PLM UI framework. Enhancement spot: /PLMB/ES_SPI BAdI definition: /PLMB/EX_SPI_METADATA 5 In the implementing class, add the following example coding: Method /PLMB/IF_EX_SPI_METADATA~ENRICH_NODE_DEFINITION DATA: ls_node LIKE LINE OF ct_metadata_node. READ TABLE ct_metadata_node INTO ls_node WITH KEY name = 'MARA'. IF sy-subrc IS INITIAL. ls_node-name = 'YYCUSTOM'. ls_node-name_parent = 'MARA'. ls_node-transient = abap_true. ls_node-data_struc = 'YCUSTOM_STR'. ls_node-update_relevant = abap_false. ls_node-supported_operation_group = 06. CLEAR: ls_node-data_description, ls_node-actions[], ls_node-update_sideeffect. ls_node-supported_properties-fields-insert = abap_false. ls_node-supported_properties-fields-transient_data_record = abap_true. INSERT ls_node INTO TABLE ct_metadata_node. ENDIF. In this example, YYCUSTOM is the new node (sub-node below MARA), and YCUSTOM_STR is the structure containing the fields to be displayed. To set the parameters in a simple way, we copied the entry from node MARA and modified it accordingly. SAP Notes and may be necessary
Recommended
View more...
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks