| HANA | | | |
New November 2013 SAP
HANA-based Search - Implementation of the Access Class Interface for the Reuse
Model | You can use this document to implement the access class interface for your reuse model so that the HANA-based search of master data can retrieve both active data and inactive data. | MDG7.0 | MDG7.0 |
New November 2013 Joining Text Tables to Replace Technical Names with Descriptions in the HANA View for Drilldown Search | The SAP HANA-based search of master data is one of several ways of searching master data that reside in SAP HANA. You can create a HANA view and configure it to explore the master data or to perform a drilldown search. If the HANA view contains attributes with technical keys (such as Country Keys or Region Codes), the drilldown search results display technical keys instead of text descriptions. To ensure that text descriptions display in the browser panes and result sets of the drilldown search, you must manually modify your generated SAP HANA views in SAP HANA Studio by adding text joins to the corresponding text tables. | MDG7.0 | MDG7.0 |
| BI Content | | | |
New November 2013 Activating BI Content for Analysis of Change Requests | With MDG 6.0 EHP6, SAP supports BI Content; reports and functions that analyze how effectively change requests are processed in your organization. You must activate the content first, as described in this document. You can analyze change requests from the following perspectives: - Processing times (for example, view a graphic indicating what proportion of change requests violate Service Level Agreements)
- Statuses (for example, view a graphic indicating what proportion of change requests are in process)
- Change requests involving you
| EhP6 | MDG7.0 |
|
| User Interface | | | |
New November 2013 How to use a customer specific UIBB in MDG application 'Create Change Request' | This tutorial describes how to use a customer specific UIBB in the MDG application 'Create Change Request' (WebDynproApplication usmd_crequest_create). | MDG6.1 | MDG7.0 |
New November 2013 Customizing Navigation for Change Request Steps in the User Interface for Multi-Record Processing | In multi-record processing, you can define different user interfaces for the same change request step. For example, you can make the initial step appear different to the approval step or the processing step. | MDG6.1 | MDG7.0 |
| New November 2013 Creating a UI Configuration and Integrating it with the MDG Communicator | You can copy an existing UI Configuration and adapt it to your needs. As an example, we copy the Component Configuration of the Overview Floorplan (OVP) USMD_SF_CARR_OVP and delete the attachment User Interface Building Block (UIBB). | MDG6.1 | MDG7.0 |
| New November 2013Customizing Navigation for Change Request Steps in the User Interface for Single-Object Processing | During Single Object Processing, you want to define different User Interfaces for individual Change Request steps. For example, in a Supplier Scenario you might want one step to make the general data visible, and, in another step you might want only the purchasing organization data to be visible. | MDG6.1 | MDG7.0 |
| How to Add Fields to the Change Request UI (MDG EhP6) | This article describes how you can do this with the new UI technologies that are used by the domain specific Web Dynpro applications for material and supplier with enhancement package 6. | EhP5 | MDG7.0 |
| Hiding Fields in the Change Request User Interface | You want to hide fields of the change request UI. For example you do not want to allow users to enter a due date when submitting a change request. | EhP5 | MDG6.1 |
| Enhancement of the User Interface Building Block for Change Requests | In this example, you require an extra parameter to control the process and the workflow for change requests - Requesting Business Area. You do not model this parameter is as part of the MDG data model because it is not part of the business context. Instead, you store the parameter together with the change request number in a Z-table. In addition, you place the parameter on the change request UIBB on the tab for the general data. The user can select from business areas defined in Customizing. (The relevant data element is GSBER and the relevant table is TGSB). When a user opens the change request for display, the Requesting Business Area parameter is displayed and cannot be changed. | EhP6 | MDG7.0 |
| A demo of how to remove a field from the user interface and remove the corresponding validations. | EhP6 | MDG7.0 |
|
| API | | | |
| Updated November 2013 Application Programming Interface Customizing Guide | Depending on the software release, MDG offers different APIs for consumption with different functional scopes. This guide describes the Application Programming Interfaces for each release. | EhP5 | MDG7.0 |
Workflow | | | |
| How-to handle Entities with type 4 in BRF+ | This article explains how entity types 4 with 1:1 and 1:N cardinality are handled in BRF+ by an small example. | EhP5 | MDG7.0 |
| How to Check or Derive an Attribute Value in MDG Using BRFPlus | With SAP Master Data Governance you can use BRFplus to define rules for checking attribute values or to derive them. This step-by-step guide shows you how to create such a rule. This procedure can be applied to any MDG application
or data model. The MDG for Custom Objects Example Scenario is used as an easy
to understand basis for this how to document. | EhP5 | MDG7.0 |
| BADI USMD_SSW_RULE_CONTEXT_PREPARE | EhP5 | MDG7.0 |
| Rule Based Workflow: Enhancement for parallel workitems | BADI USMD_SSW_PARA_RESULT_HANDLER | EhP5 | MDG7.0 |
| Rule Based Workflow: Enhancement for Flexible User Determination | BADI USMD_SSW_DYNAMIC_AGENT_SELECT | EhP5 | MDG7.0 |
| BADI USMD_SSW_SYSTEM_METHOD_CALLER | EhP5 |
MDG7.0 |
| Sending an E-mail notification from the rules-based workflow | EhP5 |
MDG7.0 |
| Setting up extended workflow notifications in order to send out e-mails when new workflow items are generated (also allows you to include a link to the workflow inbox in the generated e-mail). | EhP5 | MDG7.0 |
| How to add an additional task to the inbox | You create own workflow definitions with new workflow tasks and want to see the corresponding workitems in the MDG inbox. | EhP5 | MDG7.0 |
| Description how to trigger an Email to all users involved once a change request is finally approved. The Email contains a protocol of the change request incl. changes and associated metadata. | EhP5 | MDG7.0 |
| Extensibility | | | |
| Description how to extend new attributes for entity type | EhP5 | MDG7.0 |
| SAP How-To Guide Develop a Custom Master Data Object in SAP Master Data Governance (ERP 6 EhP5 amd EhP6) | Many companies want to manage custom object in a central Master data system to be able to harmonize this information across the landscape. Custom objects can be individual defined object such as assets or locations. Custom objects are typically less complex master data object with a small and simple data model. | EhP5 | MDG7.0 |
| This tutorial describes how to create an enrichment spot implementation with user interaction in Master Data Governance. The implementation is called when executing Checking for non-existent objects in the object list of a change requesta consistency check in the Single Processing UI (WebDynpro Application usmd_entity_value2). | EhP6 | MDG7.0 |
| Checking for non-existent objects in the object list of a change request | SAP Master Data Governance offers the feature to include the keys of objects that do not yet exist in the object list of a change request. Rather than waiting until all data is ready before specifying changes, you can work simultaneously on object creation and the processing of the change request. This document shows how to implement BAdIs that provide warnings and errors about non-existent objects | EhP6 | MDG7.0 |
| Value Mapping | | | |
| You want to maintain mass value mapping (customizing mapping) via file export/import. | EhP5 | MDG7.0 |
| Data Replication | | | |
| You want to replicate data from your customer-specific data model to target systems (using flex option). | EhP5 | MDG7.0 |
