SAP MDM ONLINE TRAINING WITH REALTIME EXPERTS

HI,

We provide SAP MDM ONLINE training with realtime consultants at reasonable cost.

For further details reach us at

Sree
www.sapmdm.co.in
+91-9379914378

Google maps inside MDM Vito Palasciano

Introduction

Sometimes it can be useful to locate a vendor in order to understand in which part of the world it carries out his business activities. This blog describes how to encapsulate Google Maps directly into MDM so that it will show the vendor address each time a vendor is selected.
Getting to work…

Using the Google maps Web site (http://maps.google.com/) it is possible to search an address everywhere in the world. Once an address has been located, the “link“ functionality (the hypertext indicated by the red arrow) can be used in order to obtain the full link to the map, as highlighted in the red frame.

Google Maps

In the example above the link is http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Italy,+MILAN,+VIA+CALDERA+21
where the parameters are language (English, in this example) and address (Italy, MILAN, VIA CALDERA 21, in this example).

SAP MDM provides us with a tool named Web Tab which can be used to call an external application just by adding an URL in the Links table in Console and specifying same parameters.

It is necessary to paste a new link version into the Web Tab URL:
http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=
where parameter geo_map is a calculated field in MDM that contains Country name, City and Company Name separated by a comma.

A new link version into the Web Tab URL

Additionally, it is necessary to set the Web Pane URL in the configuration option in MDM Data Manager:

Web Pane URL configuration option

From now on, it will be possible to select a vendor and see the related map, as in the following examples:

Techedge Milan

Techedge Chicago

And, finally, hoping that Techedge will sooner or later open a branch at Beau Vallon Beach…

Techedge Seychelles

Enjoy your maps!

Vito Palasciano

Vito Palasciano is a Solution Architect at TechEdge currently focused on SAP Master Data Management.

MDM: Expectations v/s Realities

Master Data Management as a concept has existed as long as the ERP market or even before. The concept has been to help efficiently manage transactional and reporting functions within an application by having a separate repository for master data. The master data function gets called dynamically within the execution of a transaction.

This concept has evolved over the years, due to complexity of businesses and hence the IT Systems that are required to support it. In recent years the concept is gaining maturity by looking at Master data as a function to feed systems enterprise wide, not ERP alone. Hence MDM is now being viewed as a de-coupled application from the ERP applications.


Many vendors, some niche and other ERP vendors, have products to address this space. Though Gartner has reported the relative capability across various products in the ‘Magic Quadrant’, Consultants and Clients alike, are aware that none of the products have matured enough to warrant the name of ‘MDM Package Solution’. The products are still in the form of a tool/platform and a basic framework over which clients are expected to build a custom solution. Depending on what the client wants to achieve, the solution build up can be as expensive as a custom solution on any other platform.


SAP’s MDM product addresses master data across the enterprise like Material, Vendor and Customer. It also has certain content that is much suited for an SAP environment, hence there is good amount of data modeling effort that can be saved if the company has a SAP based landscape. These are some of the key differentiators for SAP MDM against other contemporaries.

The other features, like de-duplication, merging, harmonization etc are also part of the Product offerings.


However, the above alone does not make the offering a rich or a mature one. Today, the companies need to orchestrate and manage master data as a central application to the Enterprise. This needs a robust, user friendly and configurable package with a host of functionalities. The requirement from the Industry is the following:

* User friendly screens
* Complex validations that may need to be called from other applications
* Easy to configure and
* Manage workflows for data approval



What can SAP do to meet the above requirements with the current MDM package?

* SAP needs to bring the Key components of Enterprise Portal and MDM together. This would mean that the configuration of screens and fields should be in sync and should not appear as two disjoint applications.
* Since the companies preferring SAP MDM are predominantly SAP shops, SAP needs to have EP-MDM ready for an SAP landscape. The lead time to configure and set up a Central master data management should come down drastically. This will increase the adoption and usability of SAP MDM
* SAP has tried to merge BO with SAP MDM, but these again should not be viewed and communicated as two different components. This should be communicated and projected as one single component. Currently there is a lot of confusion on what is the ETL recommended, is it of BOBJ or SAP MDM? These confusions in messaging adds to the reluctance in adoption
* Workflow is a major component of central master data management. The workflow in some cases can be as complex as running across SAP MDM and SAP ECC or other SAP applications. This can be done using the new BPM, but this again needs to be offered as a part of the product.



SAP needs to work on maturing the product to make it a robust single unit, than expect customers to work on multiple components such as BPM, EP, Webdynpro and MDM to put up a MDM Solution. Essentially, the concept can be borrowed from ECC, where-in you have; Transactional processing UI; Configuration and Developer workbench. The skills required for the same are Functional and ABAP technical and it is easy to implement and use.

The skills required for setting up the current MDM solution –using number of SAP components- are too many and can act as a big entry barrier for larger customer adoption.


SAP needs to put in a lot of resources and get this going fast before customers start looking at other products to meet their MDM needs. Most of the vendors are just catching up and faster they move the larger the pie of the market they will acquire.
Historically SAP has developed a number of products and matured it quickly to gain market share. The more recent example being CRM. I would still place my bets on SAP maturing the MDM solution to the leadership space of the Magic Quadrant.

Ravishankar Hossur Prinicpal Consultant; SAP Technologies

SAP Business Objects and SAP NetWeaver MDM - Bringing Together The Best of Two Worlds--Markus Ganser

This is really good news for data stewards and other IT people dedicated to information management and data quality management: SAP Business Objects and SAP NetWeaver continue to team up in a common approach to establish sustained enterprise strategies.

Attentive community readers may already have noticed that the SAP NetWeaver Information Management space and the SAP Business Objects Information Management space are semantically closely related, both covering one and the same hot spot in current enterprise strategies applied to gain the competitive edge. This has already been addressed in the Extending the Value of SAP NetWeaver Business Intelligence with the Business Objects Business Intelligence Platform presentation. And - the common ground can also be observed in the master data management space.

As already depicted in the SAP NetWeaver Master Data Management roadmap graphic below, you can see one example of how these areas have started to interact, combining the best of two worlds featuring end-to-end data quality driven master data management.



Roadmap2008

[*) Please note that possible future developments are subject to change and may be changed by SAP at any time for any reason without notice]

With the Data Quality Management (DQM) for SAP NetWeaver MDM package at hand, you can leverage the powerful address cleansing capabilities of SAP Business Objects Data Services in SAP NetWeaver MDM*.

For an architectural overview of SAP NetWeaver MDM and SAP Business Objects interacting through the DQM-MDM Enrichment Adapter see the following graphic.

image"

From the package you will get the following benefits:

1. Ready-to-run sophisticated address cleansing capabilities on an international scale.
2. Master data excellence by combining master data quality and master data persistency
3. Streamlined service-based integration via the MDM Enrichment Architecture.
4. Workflow-embedded data enrichment process.

The related user guide provides a general overview of BusinessObjects™ Data Quality Management software, version for SAP NetWeaver MDM, as well as specific information for installing and integrating this product with SAP NetWeaver MDM.

SAP Business Objects Data Services customers can download the Data Quality Management (DQM) for SAP NetWeaver MDM package from the SAP Download Center (Path: Download > Installations and Upgrades > Entry by Application Group > SAP Business Objects packages and products > BOBJ DQM FOR SAP NW MDM).

*) refers to SAP NetWeaver MDM 5.5 SP6; version for SAP NetWeaver MDM 7.1 is coming soon (will be announced separately)

SAP MDM TRAINING

sap-netweaver-tep12-questions Part-2

sap-netweaver-tep12-questions Part-2

1) Accessing a Portal Component in the Default Mode

Ans : doContent();

2) Extending this class when Developing your Portal Components

Ans : AbstractPortalComponent.

3) Portal Runtime call the methods in the Life Cycle

Ans : init(),

service()

destroy()

4) What are the Parameters that we have to pass to doConent();

Ans : IPortalComponentRequest ,IPortalComponentResponse;

5) How do u access a Resource from a request object

Ans : request,getResource();

6) Personalization concept what are the data type ….the type attribute supports

Ans : String , Date , Select , Boolean

7) How do u get the property from the IPortalCompenentProfile

Ans : getProperty(String)

8) What is the method has to be overridden by the class that extends from PageProcessorComponent

Ans : getPage();

9) Give the sequence of methods execution of DynPage

Ans :

1) doInitialization()

2) doProcessAfterInput()

3) doProcessBeforeOutput()

10) sequence of method calls when an event occurs

Ans :

1) doProcessAfterInput()

2) on

3) doProcessBeforeOutput()

11) how do u get the getCurrentEvent();

Ans :

IPageContext myContext = PageConectFactory.createPageConext(request,responce);

Event = myContext.getCurrentevent();

12) onClientClick() and onClick() are specified then which method will be called first

Ans : onClientClick();

13) JSPDynPage uses _________ type of approach

Ans : Model View Controller

14) The two properties in the component profile indicate that a JSP need to be compiled into portal component :

Ans : Property name = “JSP”

Property name = “ComponentType”

15) Which one is true in the following statement

a)

<%@ taglib uri = “hbj” prefix = “htmlb”>

b)

<%@ taglib uri = “hbj” prefix = “hbj”>

c)

<%@ taglib uri = “hbj” prefix = “htmlb”>

d)

<%@ taglib uri = “htmlb” prefix = “hbj”>



Ans : a



16) How do u call a jsp file :

Ans : setJspName();



17) If java Script are used _______tag is necessary for the page

Ans : Page tag



18) Which tag is used for including bean in the jsp file

Ans :



19) What is the scope of the bean

Ans : Session



20) Give the objects that are extend form the IPrincipal

Ans :

IGroup,IRole , IUser,IUserAccount,IUserMaint,



21) ____is the Central object from which all UME object factories are obtained

Ans : UMFactory

22) IUser user = UMfactory.getUserfactory().getUserbyLogonID(uid)

String userName = user.getDisplayName();

String email = user.getEmail();

Response.write(“ userName”+ username+” Email :”+ email);



1) Displays the username and Email ID

2) Throws an exception

3) Doesn’t Compile



Ans : 1.

23) List the methods used to create successful user

Ans :

1) NewUser(uid);

2) setFirstName()

3) setLastName()

4) setEmail()

5) setPassword();





24) can we construct an unique id manually .

Ans : false can create a unique id .



25) Unique IDs are used to identify objects across data sources.

Ans : ..



26) How do u retrieve log on information

Ans : umdata.enrich(map);



27) What is the return type of map.get(“”);

Ans : String



28) How do u load the data in the Client Eventing across the iviews

Ans : EPCM.loadClientData();



29) What is the object available in the pages

Ans : EPCM

30) What problems does HTMLB the overcomes on servelts

Ans :

Visualization and business logic are not separate

Development has to take care of different web clients and versions

NamesSpace conflicts with form elements



31) Stored data is identified by the key …..

Ans : Namespace+name



32) Frame Work Levels

Ans :

Level = 0 ….. not supported by both javaScript, Java

Level = 1 ----only by browser (java Script )

Level = 2 ----both javaScript and Java



33) Features of portal Services in the portal

Ans :

1) portal services are way to provide functionality to portal component

2) portal services implement no user interface

3) portal service may be accessed from out side portal framework



34) Why do we need custom portal Services in the portal

Ans :

1) Can be used by other Portal Application

2) Provide commonly used Functionality

3) Can be exposed as webservice

35) To build a new portal service ……interface must be implemented

Ans :

IService



36) Life cycle of a portal service

Ans :

Init()

Afterinit()

Destroy()



37) Service name =

Ans :

.

.

.

.



38) Portal service name is myService …what would be the name of interface that extends IService

Ans : IMyService



39) JCA/J2EE connector Architecture is not API. True /False

Ans : true

40) ConnectorFrameWork is SAP Extended API from CCI . all methods in Connector FrameWork has methods with suffix as EX()….

Ans : False only some methods



41) What is the method used to get connection in the Java Connectors

Ans : Service.getConnection();



42) How do u get the locale from the request object.

Ans : Request.getLocale();



43) What is the return type for the table type structure .

Ans : IRecordSet.



44) Give the name of the method that returns resource bundle for the current locale.

Ans : getResourceBundle()



45) Localization.properties

Localization_de_DE.properties.

Localization_en_EN.properties.

What is the Resource bundle name : ?

Ans : Localization



46) What is the data type that returns by the method getString (key)



Ans : String



47) How do u access the a key in the properties file xyz = abc

Ans : getString (“xyz”)

48) What type of objects can be translated

Ans : Text

49) the portal translation process is supported by tools

Ans :

Translation worklist coordination

Worklist translation



50) to customize the Logoff screen to the portal ----file is used to change

Ans : masthead

51) SAP Recommends not to modify the SAP code , then what are the process to customize the code

Ans :

1) copy the existing file and rename it according to customer name space

2) create new custom component



52) how can we customize the company Branding



Ans :

1) masthead

2) through customize applicaton





53) Their one question on Desktop inner page




54) What are the components that are added to Portal Desktop

Ans :

Default Frame work

Themes



55) What is the jsp name that contains log on page

Ans : umLogonPage.jsp

56) Authschemes.xml is modified to get custom log on component



57) How do u access portal services from WebDynpro applications

Ans : WDPortalUtils



58) Cache Level :

Ans : none ,session ,user,shared




59) getCachingLevel() is used to get the Cachelevel



60) When will the doinitialization () method is called

Ans :

1 When the page is loaded for the first time

2 When the page is refreshed

3 When object is called from the another object



61) Cached objects are retrieved using the --- method

Ans : get(key)

62) How can the portal service access to external Web Service

Ans :

Generate java proxy out of WSDL file with PDK

You can execute the java proxy as portal service

MDM Import Manager capability Ravi Kumar

MDM Import Manager capability
Ravi Kumar


In my previous project we had a requirement of running matching strategy for finding duplicate Material master. The matching rule was pretty simple based on Material Description but the repository size was in tune of 500K with around 250 attributes.

to enable better matching results we had used lots of transformations on Material Description field for normalizing and standardizing of data. We were using combination of two rules in the Duplicate matching strategy:

1. Rule1: using functionality equal(on Material Description transformed field)

2. Rule 2: token equal( on Material Description field)

On an average the description was having 1.5 tokens per record. We found that performance was very poor as we had both token equals and a huge list of transformations( few of them were replacing string XXX to AAA, deleting blanks, other special characters etc etc). Even after restricting the total number of records considered for matching( we used Material group for Clustering) it was taking 20-40 mins for matching results.

Solution: We improved the data quality by re importing the same set of records which was used for initial load from ECC but this time MDM Import manager capabilities were harnessed to reduce number of transformations.

HOW: After mapping Material Description field apply value conversion filter on the mapped field and we have almost all excel based powerful functions available like replace, Append, Prepend. We can have even multiple such conversion rules applied on the same mapped field.

We also made Keyword normal for field Material Description, which optimized token based comparisons.

This effectively reduced our number of transformations from 22 to 5 and increased matching strategy performance.



Ravi Kumar is Consultant with Infosys.

MDM Import Manager capability
Ravi Kumar

SAP MDM integration with R/3 system Ravi Kumar

SAP MDM integration with R/3 system
Ravi Kumar


•We all know what are the different It scenarios supported by MDM, namely:
Master Data Consolidation

*
– Cleansing and de-duplication
*
–Data normalization including categorization and taxonomy management
*
–New interactive consolidation capabilities

•Master Data Harmonization

*
–Automated synchronization of globally relevant master data information
*
–New interactive distribution capabilities

•Central Master Data Management

*
–One-stop data maintenance
*
–Ongoing master data quality

In this Blog I will try to cover the different steps required for integrating MDM with R/3 system which is the source of Master data.After cleansing and de-duplication of Data in MDM all changes/ updates will be reflecting back in SAP R/3. this step by step procedure should help in understanding the procedure for implementing MDM IT scenarios. :)



Different settings required for doing this are:

* Settings in R3
* Settings in XI
* Settings in MDM
* MDM console
* Import Manager
* Syndication Manager

MDM Process flow









Process Flow: Trigger Idoc containing Masters from R/3.XI converts these Idocs to XML files and places in ready folder for Inbound port. Files received by Import Manager into MDM and after changes etal via Syndicator Manager xml file placed in Ready folder of outbound Port from where it will be picked by XI and sent to R/3 using the Idocs.





Setting in R/3:

Step 1



T.Code: SALE

Define Logical System





Sender Logical System:





Receiver Logical System:



















Step 2: T.code: SALE



Assign Client to Sender Logical System:







Step 3:

Create RFC destination of type ‘3' for SAP XI system using transaction - SM59





Step 4:



Create a Distribution model through T.Code: SALE/BD64



Here we need to mention Sender Client (DEVCLNT500) and Receiver Client (XICLNT100) and Message type (MATMAS)









Step 5:

Using T.Code: WE21



Maintain Ports for IDoc Processing



















Step: 6



Maintain Partner Profile using the T.code: WE20









Step 7:

Using BD12/BD10 T.code to Send Customer IDoc or material IDoc











Using T.code WE02 we can confirm or see the message transformations.







Now we are able to generate IDoc from R/3 containing the master data.

Settings in MDM:

Select the repository for which you want to do the settings.









Go to "Admin" and select "Client Systems" and right click on it and create your client system















Then go to "Ports" for creating a Port for Client System







Here you are defining the Outbound Port for the Client system (MDC R/3) defined in previous step.

You have an option of processing the data Automatically/manually.





After Saving the "Port" and "Client System" you need to ensure the folders in respective repository has been created in server.







Because "Ready" is the folder where all the files get exchange from.



Similar steps should be repeated for Inbound Port.





MDM Import Manager: Assuming that all the settings are done in XI also we move to Import manager where we will select the file to be imported and steps to be followed for import of Data into MDM



Step 1: Login to Import Manager and connect to Source file. Select type as PORT. System automatically connects to the Inbound Port of the repository logged into.







Step 2: Do all Field mapping and value mapping in Map Field/Value tab.we can use the standard maps provided in Business content or do all mappings manually and save the map.







Step 3: Go to match records Tab select the Field used for Matching records and select the import action. PS : For each record we can manually override create/skip as import action.











Step 4: After all mappings has been done and import action is Ready to Import in Import status tab execute the import









This will import the records contained in the xml file from the Ready folder into MDM.GO to Data manager and check all records created from R3.





Syndicator Manager MDM:



Any changes made in MDM data manager based upon the validations/Assignemnts and Business rules the changed record should be syndicated back to R3 which is Data source.



Step 1: Login to Syndicator Manager giving the repository name. select File> Destination Properties and select Port as shown:



Select the remote system R3 in this case

Select the Port which we have created for Outbound port where the Syndicated file can be placed in XML format.











Step 2: Do all the mappings again. Use the standard maps provided in Business content or do it manually like in Import manager. We have the options of selecting few records based on search parameters. We also have the option of Supressing all unchanged records in map Properties. This will select only those records which has been changed in Data manager instead of all existing records.









Step 3: In Destination Preview we can actually see all records with the values for fields before syndicating. This should be always done before executing to reduce the erroneous /incomplete data flow. Once you have all the details execute the syndication.











Step 4: Check the IDoc list in SAP. In case of status 51 do the further analysis why it has failed.











RESULT: data changed in MDM Data manager will be updated in SAP R3 system provided all the mappings are correct.

Ravi Kumar is Consultant with Infosys.

SAP MDM integration with R/3 system
Ravi Kumar