Managing Query View Description :

          In some MDG system the Description of the Query View may not be present. (Highlighted in yellow in the Fig 1) .Instead name of the Query View will be displayed if description is not maintained.This document provides you the steps , how to maintain the Query View Description of the Graph in the initial screen of SAP-MDG .

          Fig 1  Screen-shot showing the Graph where Description is not maintained Initially.

Steps to maintain Query View Description :

1. Click the settings => Properties , of the Graph for which Description has to be maintained.

          Fig 2 Screen-shot showing the Step 1

2. Properties of the Graph is shown (Name & Provider ).

          Fig 3 Properties in Detail

We can see that provider is Business Context Viewer. So configuration for changing the description should be done in Business Context Viewer settings in SPRO.

Name of the Query View :  1MDG_EDTN_MY_CR_QV.

3. Go to the transaction SPRO. Click SAP Reference IMG.

          Fig 4 Initial SPRO screen

4. Configuration screen appears. Go to Cross-Application Components Step.

          Fig 5 SAP Customizing Implementation Guide => Cross-Application Component

5. Click Processes and Tools for Enterprise Applications.

          Fig 6 Cross-Application Component => Processes and tools for Enterprise Applications

6. Note that Graph is the Business Context Viewer. So configuration has to be done under Business Context Viewer => User Interface => Define Query Views. Click Business Context Viewer.

          Fig 7 Business Context Viewer

7. Click User Interface.

          Fig 8 User Interface Step

8. Click Define Query Views.

          Fig 9 Query View

9. Name of the Query View : 1MDG_EDTN_MY_CR_QV (Marked in yellow - First Column ) . We can view that Description field is empty (Marked in yellow - Second Column) . This is the reason why graph description is not shown in the SAP MDG initial screen.

          Fig 10 Description Change configuration page

10. Change the Description as required and save it in TR. (Here we have changed the description as My Change Requests).

          Fig 11 Description changed image

11. Now the Graph description is changed to My Change Requests.

          Fig 12 Result in MDG-M initial screen

Thus the steps for changing the Description of Query View.

Analysts and Partners on SAP MDG...

Find out about SAP's ranking in the latest Forrester Wave™: Master Data Management and the MDG solution extensions by Utopia. 19 April 2016

SAP MDG at a Glance

For quick insight into what SAP Master Data Governance is all about, watch theanimated 3-minute videos.18 January 2016

Innovations with SAP Master Data Governance 8.0

To find out about the innovations that have come with SAP MDG, release 8.0, read the SCN blog by Markus Kuppe and the complementary blog by Steffen Ulmer.25 November 2015

Extensibility and Configuration Options for SAP Master Data Governance

Find extensibility and configuration options for SAP Master Data Governanceat one spot. Includes recent updates. 11 May 2015

SAP Master Data Governance - Updated Product Roadmap

To find out about SAP MDG today, planned innovations and future vision, read Markus Ganser's blog. updated 28 July 2015

This page provides audio files about global trends in master data management as well as business benefits, basic functions, and integration aspects of SAP Master Data Governance.

Videos by master data domain:

Latest Presentations Featuring SAP Master Data Governance

Stay on top of what's going on with SAP Master Data Governance. Find key presentations at one spot. 28 June 2016

Analysts and Partners on SAP MDG...

Find out about SAP's ranking in the latest Forrester Wave™: Master Data Management and the MDG solution extensions by Utopia. 19 April 2016

SAP MDG at a Glance

For quick insight into what SAP Master Data Governance is all about, watch theanimated 3-minute videos.18 January 2016

Extensibility and Configuration Options for SAP Master Data Governance

Find extensibility and configuration options for SAP Master Data Governanceat one spot. Includes recent updates. 11 May 2015

SAP Master Data Governance - Updated Product Roadmap

To find out about SAP MDG today, planned innovations and future vision, read Markus Ganser's blog. updated 28 July 2015

This page provides domain-specific information on how to add fields or capabilities to your solution, reconfigure your solution, or integrate your solution within your software landscape. The documents are typically enriched with screenshots, instructions, and - where necessary - sample code.

The documents cover different releases from EhP5 to MDG 9.0; their exact validity is mentioned for the individual document.

Return to main page

Disclaimer

SAP code or application samples and tutorials are NOT FOR PRODUCTION USE . You may not demonstrate, test, examine, evaluate or otherwise use them in a live operating environment or with data that has not been sufficiently backed up. You may not rent, lease, lend, or resell SAP code or application samples and tutorials.

Document Description : The purpose of this document is to explain the steps for the configuration of Mass Data Upload in SAP MDG.

Table of Contents

1. 1.       Introduction
2. 1.1     Overview
3. 1.2     Scenario
4. 1.3     Purpose
5. 1.4     Prerquiesite
6. 2.       Process
7. 2.1     Steps

1. Introduction

1.1 Overview

SAP Master Data Governance provides business processes to find, create and change master data. It supports the governance of master data on a central hub and the distribution of 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.

Import Master Data service can be used to import files containing material and classification data to the Master Data Governance system. The data from these files can update existing master data records or create new ones using the options available in the Import Master Data service.

1.2 Scenario

This guide provides background information about the Data Import Framework (DIF) and describes how to use the DIF to upload material data from a CSV file using a BAdI for the file conversion.

1.3 Purpose

Data transfer represents a collection of functions and features you can use to move master data and mapping information between systems and clients. Examples of these systems include existing ERP systems and your Master Data Governance hub system. To transfer master data and mapping information, perform the following steps:

1. Export the master data and mapping information from the source system to an XML file. This file rests on your application server.
2. Copy the XML file from the application server of the source system to the application server of your target system.
3. Import the master data and mapping information to the target system using the Data Import Framework.

1.4     Prerequisites

Check if the required SAP Notes are implemented based on the module for which DI framework is to be used in the system.

Data in excel file should be given in pre-defied format.

2. Process

2.1     Steps

1. Enter data to be uploaded in pre-defined .XLSX template.
2. Convert Excel to UTF-8 .CSV format.
3. Mass Upload of Data in MDG
4. BADI responsible for technical control

Run Transaction NWBC, goto

Master Data Governance for supplier: Menu -> Data Exchange -> Data Transfer -> Import Master Data

and enter the required values check the checkbox Governance if the same is required -

5. Click on Add button in Data Sources,

      Select object type as Business Partner and enter the value of source directory –

  6. Click on Custom Converter Setting and select converter type –

  7. Click on the Import button on the top -

8. The bulk upload file will be placed in AL11 -

The bulk upload file can be uploaded in the directory using transaction CG3Z .

The above explained scenario is using Mass Upload for BP data. Other modules as Material, Customer etc. can also use DI framework for mass upload with limitation of respective modules.

BADI responsible for technical customisation

BADI : BADI_MDG_FILECONVERTER

Document Description : The purpose of this document is to explain the steps for customizing / modifying User Interface . Making fields/sections visible/hidden.

Table of Contents

1.       Introduction

1.1     Overview

1.2     Scenario

1.4     Pre-requisite

2.       Process

2.1     Steps

1. Introduction

1.1 Overview

SAP Master Data Governance provide standard 'Master' UI for each master data model . It is a very common need in SAP Master Data Governance to modify the UI with respect to customer/business need 

1.2 Scenario    

          This document will help you to  fulfill the business need it may require to hide or unhide the respective sections or           attributes  from UI

1.3     Prerequisites

           It is expected necessary BC set with respect to UI configuration are activated and  All necessary configuration is done  in       MDGIMG-->General Setting -->UI Modelling

2. Process

2.1     Steps

User interface attribute can be hide in two ways,

a) Complete Section

b) Single attribute in any section

A:- Complete Section : -  This requirement is suggested to achieve through change in properties of web-dynpro component.

B:- Single attribute  : - For this requirement BADI enhancement is preferred/suggested.

COMPLETE SECTION/BLOCK :

* Right click on UI & Select 'Technical Help'

* Select 'BS_MAT_OVP_05'...

Select 'BS_MAT_OVP_LAYOUT_05'

Select 'Add Adaptation'

On 'Add Adaptation' select desire parameter according to business need.

Post this process it will come like this

Scroll Down to 'Overview Page Schema'

Now Select Section which need to hidden

Change value as per below screen shot to change property from hidden/visible..

This way complete Section can be hide.

B: SINGLE ATTRIBUTE HIDDEN :

BADI Approach :

T-code : SE18

BADI Name :  USMD_ACC_FLD_PROP_CUST_DEP_SET

Method : IF_EX_USMD_ACC_FLD_PROP_CDS~MODIFY_FLD_PROP_ATTR

There is Table in Changing parameter : 'CT_FLD_PROP'  this contain property of every fields on UI.

Select field name & pass hidden value.

Sample Code.

Following above simple steps we can Modify UI on desired business requirement.

This page provides domain-specific information on how to add fields or capabilities to your solution, reconfigure your solution, or integrate your solution within your software landscape. The documents are typically enriched with screenshots, instructions, and - where necessary - sample code.

The documents cover different releases from EhP5 to MDG 8.0; their exact validity is mentioned for the individual document.

Return to main page

Disclaimer

SAP code or application samples and tutorials are NOT FOR PRODUCTION USE . You may not demonstrate, test, examine, evaluate or otherwise use them in a live operating environment or with data that has not been sufficiently backed up. You may not rent, lease, lend, or resell SAP code or application samples and tutorials.

This page provides domain-specific information on how to add fields or capabilities to your solution, reconfigure your solution, or integrate your solution within your software landscape. The documents are typically enriched with screenshots, instructions, and - where necessary - sample code.

The documents cover different releases from EhP5 to MDG 8.0; their exact validity is mentioned for the individual document.

Return to main page

Disclaimer

SAP code or application samples and tutorials are NOT FOR PRODUCTION USE . You may not demonstrate, test, examine, evaluate or otherwise use them in a live operating environment or with data that has not been sufficiently backed up. You may not rent, lease, lend, or resell SAP code or application samples and tutorials.

Problem Statement: In standard MDG implementation for customer/ vendor it’s a common requirement to get the details of customer / vendor through the Change Request number. SAP has not provided any standard table which stores this relation nor there any method of class to serve the purpose described above.

Solution: A small report program is developed. It takes the CR number as input as shows the customer details linked to this CR number as output. This solution could be molded as per the real time requirement to fetch the Customer / Supplier number from CR number.

Code:

REPORT z_r_get_cust_from_cr.

*****************************************************************************************
*                                                                    
* System   : MDG 7.0                    
* Author     : Sachin 
* Title        :  Customer Details through CR number                                     &*
*--------------------------------------------------------------------------------------------------------------&*
* Description : Report to get the customer details from CR number as input
*--------------------------------------------------------------------------------------------------------------*

* Type declaration
TYPES: BEGIN OF lty_bp,
bp_header TYPE  bu_businesspartner,
END OF lty_bp.

* Data declaration
DATA ls_usmd120c TYPE usmd120c.
DATA ls_kna1           TYPE kna1.

DATA lv_ktokd             TYPE ktokd.
DATA lv_bphdr             TYPE bu_businesspartner.
DATA lt_changelist_object TYPE if_usmd_cr_changelist=>gtt_changelist_object.
DATA lv_crequest          TYPE usmd_crequest.
DATA lv_kunnr             TYPE kunnr.
DATA lt_kna1              TYPE TABLE OF kna1.

DATA lo_data                 TYPE REF TO data.
DATA lo_cr_changelist        TYPE REF TO if_usmd_cr_changelist.
DATA lo_cr_changelist_object TYPE REF TO if_usmd_cr_changelist_object.
DATA lo_fsbp_object          TYPE REF TO fsbp_bo_cvi.
DATA lo_alv                  TYPE REF TO cl_salv_table.

FIELD-SYMBOLS <ls_key> TYPE any.

PARAMETERS p_cr_num          TYPE usmd_crequest OBLIGATORY.

* Start of selection
START-OF-SELECTION.

* Get all create and update change request with status Final Check Approved
SELECT SINGLE *
FROM usmd120c
INTO ls_usmd120c
WHERE usmd_crequest EQ p_cr_num.
IF sy-subrc IS NOT INITIAL.
* Display Error and Exit
WRITE:  'CR number is not correct' COLOR COL_NEGATIVE INTENSIFIED.
EXIT.
ENDIF.

* Get change list obj
lo_cr_changelist = cl_usmd_cr_changelist=>get_instance(
iv_crequest_id = ls_usmd120c-usmd_crequest
iv_model = 'BP' ).

CLEAR lt_changelist_object.
lo_cr_changelist->get_changelist_objects(
IMPORTING
et_changelist_object = lt_changelist_object ).

* Create data reference
CREATE DATA lo_data TYPE lty_bp.
ASSIGN lo_data->* TO <ls_key>.

* Get business partner
LOOP AT lt_changelist_object INTO lo_cr_changelist_object.
IF lo_cr_changelist_object->get_object_entity_type( ) EQ 'BP_HEADER'.
lo_cr_changelist_object->get_object_entity_key(
IMPORTING
es_entity_key      =   <ls_key>  " Business Partner ID
).
ENDIF.
ENDLOOP.

* Get the customer number
IF <ls_key> IS ASSIGNED.
lv_bphdr = <ls_key>.
ENDIF.

lo_fsbp_object ?= fsbp_business_factory=>get_instance( i_partner  = lv_bphdr ).
IF lo_fsbp_object IS BOUND.
CLEAR lv_kunnr.
lv_kunnr = lo_fsbp_object->customer->get_customer( ).
IF lv_kunnr IS NOT INITIAL.
SELECT SINGLE *
INTO ls_kna1
FROM kna1
WHERE kunnr EQ lv_kunnr.
IF sy-subrc IS NOT INITIAL.
* Display Error and Exit
WRITE:  'No Customer exists, CR might not be in final check approved state' COLOR COL_NEGATIVE INTENSIFIED.
EXIT.
ENDIF.
ELSE.
* Display Error and Exit
WRITE:  'No Customer exists, CR might not be in final check approved state' COLOR COL_NEGATIVE INTENSIFIED.
EXIT.
ENDIF.
ENDIF.

APPEND ls_kna1 TO lt_kna1.


* Display table
CALL METHOD cl_salv_table=>factory
IMPORTING
r_salv_table = lo_alv
CHANGING
t_table      = lt_kna1.

lo_alv->get_functions( )->set_all(
value = if_salv_c_bool_sap=>true
).

lo_alv->display( ).

Managing Query View Description :

          In some MDG system the Description of the Query View may not be present. (Highlighted in yellow in the Fig 1) .Instead name of the Query View will be displayed if description is not maintained.This document provides you the steps , how to maintain the Query View Description of the Graph in the initial screen of SAP-MDG .

          Fig 1  Screen-shot showing the Graph where Description is not maintained Initially.

Steps to maintain Query View Description :

1. Click the settings => Properties , of the Graph for which Description has to be maintained.

          Fig 2 Screen-shot showing the Step 1

2. Properties of the Graph is shown (Name & Provider ).

          Fig 3 Properties in Detail

We can see that provider is Business Context Viewer. So configuration for changing the description should be done in Business Context Viewer settings in SPRO.

Name of the Query View :  1MDG_EDTN_MY_CR_QV.

3. Go to the transaction SPRO. Click SAP Reference IMG.

          Fig 4 Initial SPRO screen

4. Configuration screen appears. Go to Cross-Application Components Step.

          Fig 5 SAP Customizing Implementation Guide => Cross-Application Component

5. Click Processes and Tools for Enterprise Applications.

          Fig 6 Cross-Application Component => Processes and tools for Enterprise Applications

6. Note that Graph is the Business Context Viewer. So configuration has to be done under Business Context Viewer => User Interface => Define Query Views. Click Business Context Viewer.

          Fig 7 Business Context Viewer

7. Click User Interface.

          Fig 8 User Interface Step

8. Click Define Query Views.

          Fig 9 Query View

9. Name of the Query View : 1MDG_EDTN_MY_CR_QV (Marked in yellow - First Column ) . We can view that Description field is empty (Marked in yellow - Second Column) . This is the reason why graph description is not shown in the SAP MDG initial screen.

          Fig 10 Description Change configuration page

10. Change the Description as required and save it in TR. (Here we have changed the description as My Change Requests).

          Fig 11 Description changed image

11. Now the Graph description is changed to My Change Requests.

          Fig 12 Result in MDG-M initial screen

Thus the steps for changing the Description of Query View.

Videos by master data domain:

Be up to date with what's going on in SAP Master Data Governance

Join the upcoming SAP MDG roadmap session, additionally find out specifically about the enhancements coming with SAP MDG 9.0, and also find the key presentations on SAP MDG at one spot. 31 August 2016

SAP Master Data Governance - Updated Product Roadmap

To find out about SAP MDG today, planned innovations and future vision, read Markus Ganser's blog. updated 31 August 2016

SAP Master Data Governance in the Cloud Appliance Library (CAL)

Read Kefeng Wang's blog to find out how to get hands-on experience with SAP Master Data Governance 8.0 using the Cloud Appliance Library. 11 August 2016

SAP MDG at a Glance

For quick insight into what SAP Master Data Governance is all about, watch theanimated 3-minute videos.18 January 2016

Extensibility and Configuration Options for SAP Master Data Governance

Find extensibility and configuration options for SAP Master Data Governanceat one spot. Includes recent updates. 11 May 2015

This page provides domain-specific information on how to add fields or capabilities to your solution, reconfigure your solution, or integrate your solution within your software landscape. The documents are typically enriched with screenshots, instructions, and - where necessary - sample code.

The documents cover different releases from EhP5 to MDG 8.0; their exact validity is mentioned for the individual document.

Choose the area you want to work with:

Application Framework including Custom Objects

Financial Data

Material Data

Customer/Supplier/Business Partner Data

Integration Scenarios

Miscellaneous

Disclaimer

SAP code or application samples and tutorials are NOT FOR PRODUCTION USE . You may not demonstrate, test, examine, evaluate or otherwise use them in a live operating environment or with data that has not been sufficiently backed up. You may not rent, lease, lend, or resell SAP code or application samples and tutorials.