How To... Master Data Governance for Material: Create User Interface for Multiple-Record Processing. Applicable Releases: MDG7. - PDF

Please download to get full document.

View again

of 31
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:

Creative Writing

Published:

Views: 36 | Pages: 31

Extension: PDF | Download: 4

Share
Related documents
Description
How To... Master Data Governance for Material: Create User Interface for Multiple-Record Processing Applicable Releases: MDG7.0, MDG8, MDG9 Version 2.1 November 2016 Document History Document Version Description
Transcript
How To... Master Data Governance for Material: Create User Interface for Multiple-Record Processing Applicable Releases: MDG7.0, MDG8, MDG9 Version 2.1 November 2016 Document History Document Version Description 1.00 First official release of this guide 1.10 Update of chapter 3.8 with color table 1.20 New chapter and Exchange generic genil model MDGMC to MDGMCM 1.40 New screenshots in chapter MDG8 new features: Add, Copy, and Discard, CL_USMD_MC_FEEDER_FORM 2.1 Additional information, adding DELETE functionality and DISCARD for deleted entities 1. BUSINESS SCENARIO GENERAL INFORMATION BACKGROUND INFORMATION FUNCTIONAL RESTRICTIONS STEP BY STEP EXPLANATION CREATE AND CONFIGURE WD APPLICATION CONFIGURATION CREATE A MODEL-SPECIFIC ASSISTANCE CLASS CREATE A CONFIGURATION FOR THE APPLICATION CONTROLLER CREATE AND CONFIGURE WD COMPONENT CONFIGURATIONS Create and Configure OVP Component Configuration Type-1 Entities Type-4 Entities Create and Configure ATS List Configuration Define Feeder Class Parameters Define List UIBB Schema Define the Toolbar Schema Define General Settings Create and Configure Forms Define Feeder Class Parameters Define Form UIBB Schema Configure the Find and Replace Popup Configure the Add and Copy Popup Define the Wire Schema List Displaying Main Entity UIBBs Displaying Other Entities ASSIGN SEARCH HELP TO FIELDS INTEGRATE CHANGE REQUEST UIBB DEFINE BUTTON IN GLOBAL TOOLBAR TO NAVIGATE TO WD APPLICATION USMD_CREQUEST_PROCESS ADJUST CUSTOMIZING Define Change Request Types Z* Define Logical Actions Define Available UI Applications Define Business Activities Link Logical Actions with Business Activities Define Change Request Steps for Rule-Based Workflow Configure Properties of Change Request Step (UI and Highlight Changes) Adapt Limit of Multiple-Record Processing ACTIVATE SERVICE HIGHLIGHTING CHANGED TABLE CONTENT Color Schema Selecting the Color Schema Colors Setting Colors TRANSFER OBJECT KEYS FROM SOURCE APPLICATION TO MULTIPLE-RECORD PROCESSING WD APPLICATION Transfer by Change Request Transfer by Global Context Configure Source Application Write Object Keys to Global Context from Source Application Transfer by URL WORK WITH COPIES OF SUPPLIED DATA (FOR EXAMPLE FROM MATERIAL SEARCH UI MDG_BS_MAT_SEARCH_06) 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. With MDG 7 SAP also supports the processing of multiple materials in a tabular interface. Multiple-Record Processing offers a streamlined process, with a UI that enables you to create change requests for multiple records with greater efficiency. SAP delivers 8 UI configurations to support 4 scenarios (2 different UI configurations each) and additional 2 default configurations (where only one is used in the customizing: MDG_BS_MAT_MC_MATERIAL) for Material. The delivered UI configurations can be used as template to build new tabular interfaces for customer needs. With MDG8 the 8 delivered templates are updated with the new functions for Add, Copy, and Discard. The delivered UI s and change request types are only examples and can be used as template. You have to consider your business requirements while you build your own UI s and CR types. This guide shows how to create new UI configurations for material. 4 2. GENERAL INFORMATION MDG Extensibility Guides on SDN: How to Create, Enhance, and Adapt Floorplan Manager Applications (FPM): Building FPM Applications on BOL with NW 703 Search SAP notes for Multi Record Processing with search terms: MR-Processing or Multi Record Processing 3. BACKGROUND INFORMATION You can use the new FPM (Floor Plan Manager) list feeder class, CL_USMD_MC_FEEDER_LIST and CL_USMD_MC_FEEDER_FORM, to implement a list displaying data sets for a wide range of data models. In addition to the standard functionality of an ATS list (ABAP Table Services), the following functionality is offered by the list feeder class feeder CL_USMD_MC_FEEDER_LIST: You can mark all data sets having a predefined value for a given attribute (Select Rows with Identical Values) You can copy the value of a given attribute to all marked data sets (Copy Value to Selected Rows) You can replace any number of attribute values for all marked data sets (Find and Replace) You can remove Type-1 entities (with all dependent entities) even if the type-1 entity has already been assigned to the object list of a change request You can copy a selected data set to a new data set. Dependent on the list configuration, related entities are also copied. If a value will be copied depends also on customizing of the backend material master (transaction OMSR). You can add a new data set to the list. Dependent on the list configuration, related entities are also added All changes in respect to the active data can be discarded for all selected data sets. Changes of the dependent data sets are also discarded All data related to the supplied type-1 entity keys can be copied at startup (replication). In this case, the application works on the copied data. If a value will be copied depends also on customizing of the backend material master (transaction OMSR). For all new data sets, the type-1 entity key can be altered Active data for type-4 entities and text entities can be deleted The deletion of entities can be discarded The first and second function can only be reached using context menu, while the third function can either be triggered using the context menu or a related toolbar button. To remove, copy, add, or discard, or delete entities, the related toolbar button has to be pressed. In order to create new entities for all supplied type-1 entity keys, the application parameter USMD_NEW_MASS_COPY has to set to X. Replication takes place at startup of the application. The FPM form feeder class CL_USMD_MC_FEEDER_LIST does not provide special functionality to manipulate the data. Table cells can be highlighted using different colors for the following cases: The saved cell value is different from the active value The current cell value is different from the saved value Table cells and form fields can be highlighted using different colors. Highlighting indicates that the current value is different from the saved or active value, respectively. Table cells that are highlighted offer a tooltip describing the changes. In addition, a change indicator column can be configured for each list. Here an icon is indicating any change in respect to the active data. If required, you can switch on and off the table cell highlighting at runtime. Strike through text is used to indicate cell content for deleted entities. 5 Material list based on the generic mass change list feeder The functions to save, check, and activate the changed data are provided by the MDG change request UIBB (UI Building Block) that has to be embedded in the same page as the multiple-record processing list. 4. FUNCTIONAL RESTRICTIONS The following restrictions apply to a WD (Web Dynpro) application based on the new feeder class: To maintain type-4 entity data, you need to configure UIBBs for all entities being part of the relationship chain between the root type-1 entity and the type-4 entity. All UIBBs need to be embedded into the main page of the application and they need to be connected using wires. Example: you want to maintain plants. This requires that you also configure a UIBB displaying materials, since the type-4 entity related to plants depends on the root type-1 entity (MATERIAL). Data displayed by forms and lists can be constructed by joining entities. Joined entities are only displayed, if the root entity exists. Example: A material has assigned one plant. Only the MARCBASIC entity exists for this plant. A table displaying plant data, but having not MARCBASIC as its root entity will not display the material s plant. Objects for dependent entities are retrieved generically. The retrieval only depends on the objects displayed for the parent entity. Filter information supplied by the calling application is not considered. Example: The calling application sends a filter value for the plant specific material status. However, for the retrieval of the type-1 main entity which is MATERIAL this information is not relevant. On the other side, this information is also not considered when plants are retrieved, since this process only depends on the selected material. In order to connect two UIBBs using wires, the root entities displayed by the two UIBBs must have a 1:1 or 1:cn relationship. This means: the key of the parent UIBB must be part of the key of the child UIBB. Only one type-1 entity type can be handled by the multiple-record processing. For example Production Versions cannot be maintained together with materials. Classification data can t be displayed or maintained with Multi-Record Processing If you copy materials from search, classification data will not be copied. 6 5. STEP BY STEP EXPLANATION The following explanation shows you how to configure the UI for multiple-record processing. You need to define a new WD application configuration, which is assigned to the change request type and step representing the maintenance scenario. The WD application configuration can be assigned to the WD application MDG_BS_MAT_MC. The implementation of a multiple record processing application based on the list feeder class CL_USMD_MC_FEEDER_LIST and CL_USMD_MC_FEEDER_FORM consists of the following steps: Create and configure a WD application configuration for WD application MDG_BS_MAT_MC Create a model-specific assistance class inheriting from CL_USMD_MC_GEN_ASSIST Create a configuration for the application controller Create and configure the floorplan configuration Create and configure the related WD list and form component configurations Integrate the change request UIBB Implement the methods of your model specific assistance class Enhance the source application (For example, search) to transfer the entity keys to the WD multiple-record processing application Define customizing (CR types, navigation) Adjust the Global Context definition (optional) 5.1. Create and Configure WD Application Configuration Create a WD application configuration for WD application MDG_BS_MAT_MC. Configure the WD application configuration as follows: Assign the name of the OVP component configuration to the WD component FPM_OVP_COMPONENT Configure the application parameter USMD_OTC: Assign the business object type 194 of your data model MM to this parameter Do not configure the application parameter USMD_CREQ_TYPE: This parameter is used to transfer the type of an existing change request to the multiple-record processing application Do not configure the application parameter USMD_CREQUEST: This parameter can be used to transfer the number of an existing change request to the multiple-record processing application Do not configure the application parameter USMD_NEW_MASS_COPY: This parameter can be used to force the copying of the type-1 entities defined by the supplied object keys (replication). The application is then working with the copied entities. You can configure the parameters for highlighting changes here. If you have added the application parameters MDG_HC_COLOR_SAVED (to highlight saved inactive data different from active data), MDG_HC_COLOR_UNSAVED (to highlight current data different from saved data), or MDG_HC_DISABLE in the last step, you can configure the parameter values here. If you have added the application parameters USMD_MC_TCD_SAVED (to highlight saved inactive data different from active data), USMD_MC_TCD_UNSAVED (to highlight current data different from saved data), or USMD_MC_TCD_USE (highlighting changes initially switched on/off) in the last step, you can configure the parameter values here. See chapter Highlighting changed Table Content for more details. 7 Create / maintain WD application configuration (example for changing material data) Create a Model-Specific Assistance Class Create a new class inheriting from super class CL_USMD_MC_GEN_ASSIST. This class allows you to define modelspecific code for the following situation: add new entities copy existing entities discard entity changes delete existing entities copy existing entities before entering the multiple-record application retrieve descriptions for entity attributes implement OVS help for add/copy dialog box For data model MM, a template class already exists (CL_MDG_BS_MAT_MC_ASSIST) Create a Configuration for the Application Controller Create a component configuration for the WD component USMD_MC_GEN_APP_CTRL, which will serve as the application controller of your application. Set the component defined attributes as follows: Name = Name of your model-specific assistance class 5.4. Create and Configure WD Component Configurations Create and Configure OVP Component Configuration For each scenario you need to configure a new WD component configuration for the WD component FPM_OVP_COMPONENT. Make sure that the page ID is MAIN and use the WD component USMD_MC_GEN_APP_CTRL as Application Configuration Controller for your WD component. From the General Setting panel select Floorplan Settings Application Controller Settings. 8 Define the global toolbar schema. Define a button for each of the following FPM events: FPM_EDIT and FPM_CANCEL. You also have to maintain the properties: text, tooltip, and image. In General Settings section set Edit Mode to Read-Only and Maximum Message Size to 5. 9 Type-1 Entities Embed the ATS list UIBB (FPM_LIST_UIBB_ATS) and assign a component configuration (to be created) to this UIBB Type-4 Entities For each dependent entity type in the data model hierarchy, embed another ATS list UIBB (FPM_LIST_UIBB_ATS) or a form UIBB (FPM_FORM_UIBB_GL2) to the floorplan component. To each UIBB assign a component configuration. Create / maintain configuration for OVP component (example for changing material data) Create and Configure ATS List Configuration Define Feeder Class Parameters The following procedure has to be conducted one or more times: Once for the header UIBB, displaying the root type-1 entity data, and once for each UIBB displaying a type-4 entity Assign the feeder class CL_USMD_MC_FEEDER_LIST to the ATS list component configuration Set the feeder class parameters: Component = MDGMCM (Name of GenIL component) Object Name = Entity of Type-1 / Type-4 Editable = checked The genil model name depends on the application you use. For MDG model MM, the model MDGMCM is to be used. Optional: Add entities in the Join Structure table. This allows you to display not only the root entity, but additional entities having a 1:1 relation to the root entity When you close the dialog box choosing the ok button the system automatically configures ATS list 10 Set feeder class parameters for ATS list UIBB configuration (example for changing material data) Note: Each entity type you add will have a direct influence on the application performance. If the root entity exists, the joined entity and its properties also have to be retrieved. On the other side, if you want to offer the possibility to add new entities (Add/Copy), you may need to join entities you have not in mind. Customizing may set information as mandatory that is defined in entities other than the root entity. Example: You add a new plant to a material. The derived maintenance status requires that some fields in other entities get mandatory fields. These entities need to be configured, too Define List UIBB Schema Configure the columns you want to offer to the user of the application. Make sure that the entity key fields (common to root and joined entities) are only configured once. Delete the table column FRW_ROW_ACTIONS_COLUMN. For attributes containing translatable texts choose a non-editable field type (For example: Text View). For all other attributes, choose editable fields types. For each column you would like to offer for administration or personalization, but which should not be displayed at startup, set the visibility to not visible. If you want to indicate via an icon that data has changed (meaningful, if the changed attributes are not displayed), you can add a related column to your list configuration. Three attributes may be configured: o Attribute STAGING is displayed if the old color scheme is selected o Attribute CHANGES is displayed if the new color scheme is selected, but the business function MDG_APPLICATION_FRAMEWORK_5 is switched off o Attribute USMD_CHANGE_INDICATOR is displayed if the new color scheme is selected and if the business function MDG_APPLICATION_FRAMEWORK_5 is switched on o You may configure columns for all of these attributes. At runtime only one of these columns will be displayed Define the Toolbar Schema Remove all buttons that have been created automatically 11 Configure a button for each of the FPM events MDG_FIND_REPLACE, MDG_ADD, MDG_COPY, and MDG_DISCARD, or MDG_DELETE (if you want to offer the related functionality). For the ATS list displaying the type-1 main entity, you can also configure a button for the FPM event MDG_REMOVE (button is programmatically hidden for all other lists) Optionally: Configure a toggle button for the FPM event MDG_HIGHLIGHT_TC. This allows you to switch on/off table cell highlighting at runtime Define the attributes of the toolbar elements: o ADD button: Set the event parameters Entities to Add to define, which entities are created when a new row is added to the list. If you leave this field empty, only the root entity is created (default). If you want to create additional entity types, you can list these entity types separated by commas. However, only entities having the same key as the root entity will be created. For lists displaying a text entity, only the text entity will be created. This behavior may be adjusted by the model-specific application class you created before. Set the event parameter Structure to define the structure of the list displayed on the dialog box for adding new rows to the list. If you leave this field empty, the structure is defined by the key fields of the root entity (default). If you want to override the default, you can enter the name of a DDIC structure. This allows you to offer sophisticated DDIC search helps without having to code a line. o COPY button: Set the event parameters Entities to Copy to define, which entities are created when an existing row is copied. If you leave this field empty, all entities having the same key as the root entity of the selected row will be copied (default). If you want to copy only specified entity types, you can list these entity types separated by commas. However, only entities including the key of the selected root entity will be copied. For lists displaying a text entity, only the text entity of the selected row will be copied. This behavior may be adjusted by the model-specific application class you created before. The usage of the event parameter Structure is described above. If a value will be copied depends also on customizing of the backend material master (transaction OMSR). o DISCARD button: Set the event parameters Entities to Discard to define, which entity changes are discarded for the selected rows. If you leave this field empty, the changes of all entities having the same key as the root entity are discarded (default). If you want to override the default, you can list the entities to be discarded separated by commas. However, only entities including the keys of the selected root entities will be discarded. For lists displaying a text entity, only the text entities for the selected rows will
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