Reporting on records merged in SAP MDM

I would like to know if there is a way to report on records that have been merged through Portal? It would be nice to be able to report which records have been merged over a time period (like within the last month), but if that is not possible, I am just looking for a way to report on merged records through other criteria. I heard that an iView is being developed to do this, but I can't find one for this functionality right now. I can display the Key Mapping info without a problem. But there is no way to search against this information.
Thanks!

Hi Muni,
Please find the sample scenario that i will be using:-
Source records (CSV)-
2,DESC1,FG,SU,IC,BA,EX,CF
2,DESC2,FH,SU,IC,BA,EX,DF
3,DESC3,FI,SU,IC,BA,EX,EF
4,DESC4,FJ,SU,IC,BA,EX,FF
5,DESC5,FK,SU,IC,BA,EX,GF
Target XML(Each records in one line)
<?xml version="1.0" encoding="UTF-8"?> <TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="myTCRM.xsd"><Tag1>2</Tag1><Tag2>DESC1</Tag2><Tag3>FG</Tag3><Tag4>SU</Tag4><Tag5>IC</Tag5><Tag6>BA</Tag6><Tag7>EX</Tag7><Tag8>CF</Tag8>
<?xml version="1.0" encoding="UTF-8"?> <TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="myTCRM.xsd"><Tag1>2</Tag1><Tag2>DESC2</Tag2><Tag3>FG</Tag3><Tag4>SU</Tag4><Tag5>IC</Tag5><Tag6>BA</Tag6><Tag7>EX</Tag7><Tag8>CF</Tag8>
<?xml version="1.0" encoding="UTF-8"?> <TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="myTCRM.xsd"><Tag1>2</Tag1><Tag2>DESC3</Tag2><Tag3>FG</Tag3><Tag4>SU</Tag4><Tag5>IC</Tag5><Tag6>BA</Tag6><Tag7>EX</Tag7><Tag8>CF</Tag8>
<?xml version="1.0" encoding="UTF-8"?> <TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="myTCRM.xsd"><Tag1>2</Tag1><Tag2>DESC4</Tag2><Tag3>FG</Tag3><Tag4>SU</Tag4><Tag5>IC</Tag5><Tag6>BA</Tag6><Tag7>EX</Tag7><Tag8>CF</Tag8>
<?xml version="1.0" encoding="UTF-8"?> <TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="myTCRM.xsd"><Tag1>2</Tag1><Tag2>DESC5</Tag2><Tag3>FG</Tag3><Tag4>SU</Tag4><Tag5>IC</Tag5><Tag6>BA</Tag6><Tag7>EX</Tag7><Tag8>CF</Tag8>
Note- Please note that each records will come in one line as an xml and the target file is .out file having each records in one line.
Please let me know your thought on this.

Similar Messages

SAP MDM Data Manager Master Record

Hi All,
Currently we have two master records in the MDM repository however the original user who created these is no longer here; due to this these records are unable to be updated or deleted in SAP MDM Data Manager
I cant find away of deleting these or moving ownership, I am hoping someone can assist

If you have the Admin login cerdentails use those to delete the records.
It would be helpful if your could give the version
for 5.5 default Admin credentails are Admin and no password
for 7.1 default Admin and password is sapmdm
try these else ask for Basis/ MDM Administrator for Admin login credentails
regards,
Abhishek

Using the Open Catalog Interface (OCI) between SAP-ECC 6.0 and SAP-MDM

Hello ASUG Community.
I'm working on an SAP-MDM project where we will configure the OCI interface between SAP-ECC 6.0 and SAP-MDM. The business requirement will be to punch out to SAP-MDM's catalog from SAP-ECC for expensed items (e.g., no material master record exists in SAP-ECC).
The data that will be returned to SAP-ECC will be purchase price info, material group, short text, & our global SAP-MDM item number.
The question I've been trying to design around is "where to store the SAP-MDM item number"?
I've looked into creating a custom filed on EKPO but now feel that a configured text field will be the best solution from an SAP-ECC point of view (less effort on the SAP-ECC side from a development perspective, no need to regenerate the EKPO table, etc.).
The question I'd like to pose to ASUG is.... Does anyone have experience or an opinion to offer using this functionality? It seems that I will have to code in a user exit or BAdi to insure that the SAP-MDM item numbers are returned to the appropriate text field on my POu2019s. Or can this be done using the standard OCI functionality?
I found OSS note 1347656 which references BADI "ME_CATALOG_INTERFACE" but I'm not sure if this right path to go down or if this would be the correct place to code non-conforming OCI mapping requiremetns.
Any insight would be most appreciated.
Thanks. Sincerely,
Rich Wortmann

I would suggest you create a new field for this as you may require thois going forward for reporting as well. Text fields are difficult to report.
Sorry not sure about the BADI to use.

How to get the Reports of Change Tracking Table in MDM?

Hi!
Please tell me how to get the reports of Change Tracking Table in MDM which is a System table, directly from MDM without using any interface.
Thanks in advance for the reply.
With Best Regards
Devendra Pandey

Hi Devendra,
MDM can track changes on tables and fields. <u>The level of change tracking, and which tables/fields to track, are configurable in the MDM Console</u>. MDM opens a new database on the same database engine as the MDM repository and writes all change records to this database.
For information of various steps you can visit
<a href="http://help.sap.com/saphelp_mdm550/helpdata/en/45/c7b20339ee570ae10000000a114a6b/content.htm">this URL</a>
Regards,
Krutarth

SAP MDM features

Hi
Could someone tell me if SAP MDM has these features?
u2022     Security
u2022     Ability to maintain and assign security at Site level
u2022     Ability to maintain and assign security at Area ( Logical Grouping like SNOP) level
u2022     Ability to maintain and assign security at Role ( Logical grouping like SCDH, GMP) level
u2022     Ability to maintain and assign security at Object ( Can be a page or a subset on a page) level
u2022     Ability to maintain and assign actions-object combination to a role
u2022     Ability to maintain and assign security at Row Level
u2022     Ability to maintain and assign security at Column Level
u2022     Ability to inherit role characteristics to another role
u2022     Ability for one role characteristics to override the characteristics chosen for another role, while inherting ( Denial to update an Object for a role, should remain the same even if the role gets inherited
u2022     Ability to audit any changes to Security on any Role/Object/Action (Will be tracked against BR5.1)
u2022
u2022     Ability to handle Master Detail relationship
u2022     Ability to handle MultiLevel data Hierarchy
u2022     Ability to handle Dependency List
u2022     Ability to maintain detail data in tabs on the same page
u2022     Ability to mandate the need to enter Detail data for a new Master record, or tie a new Detail record to an existing Master record
u2022
u2022     Ability to handle import and export of predefined formats
u2022     Ability to import and parse CSV, XLS and TXT files
u2022     Ability to import and parse XML files
u2022     Ability to export data in PDF format
u2022
u2022     Ability to handle Approval Process for data entered
u2022     Ability to configure Approvers with Approval Levels at the time of object configuration
u2022     Ability to prevent an Approver with lower Approval Level to approve data, before the higher level Approvals are obtained
u2022     Ability to send an email to the required approvers, with the link to the page/object needing approval
u2022     Ability to authenticate the NT login of the approver, accessing a page/object via a link on an email
u2022     Ability to approve through email, by linking to a webservice
u2022     Ability for the user to nominate a proxy for a given time duration
u2022     Ability to control deletion of an approver through Admin access
u2022     Ability to identify data that has not been approved and prevent database access to it.
u2022     Ability to provide read-only access to data that has not been approved
u2022     Ability to message out changes/addition on Master data to all Subscribers.
u2022     Ability to message out potential changes on Master data to all Subscribers
u2022     Ability to add an approver/subscriber to any step of the entire approval process
u2022     Ability to prevent any further actions like export/import to data that has not been approved
u2022
u2022     Ability to provide Historical Reports to identify how tool is used and highlight areas with most frequent changes
u2022     Ability to capture and view all historical changes to user access
u2022     Ability to capture and view all historical changes to data
u2022     Ability to capture data range for all Master data, to indicate the validity of a data element.
u2022
u2022     Ability to provide a Dashboard to display data entered
u2022     Ability to provide read-only access to any data maintained throught the MDM
u2022     Ability to capture each page/object added to the MDM, and provide it as a drop-down list for the user to choose from
u2022     Ability to choose filter and view data for each page/object chosen
u2022
u2022     Ability to access Help Documentation / List of Contacts for each screen
u2022     Ability to maintain a Help document for each page/object
u2022     Ability to maintain Tool Tips for each column in a Page
u2022     Ability to provide a List of Contacts for each page/object
u2022
u2022     Ability to access data via a Web Service
u2022     Ability to access all data through Composite webservice
u2022
u2022     Ability to provide Maintenance features
u2022     Ability to provide Grid Feature which allows Search, Sort, Grouping and Pagenation capabilities for all maintenance screens
u2022     Ability to provide Lookups for Standard Input fields like Date time. Lookup would be dependant on the client location
u2022     Ability to provide timeout on inactivity, on the site
u2022
u2022     Ability to add Favorites
u2022     Ability to add Recently Accessed Pages as Favourites, at a Site Level
u2022     Ability to choose views of a page and make it a Favourite, so that every consequent login, gives the same look for the same Object
u2022
u2022     Ability to Support MultiLanguage
u2022     Ability to provide Labels/Legends in Multilanguage
u2022
u2022     Business Rules to Validate Data

Hello mkhairi
For more of your question answer -YES
SAP MDM support trusted connection technology and LDAP
SAP MDM has own user role functionality where you can set permissions for user security
SAP MDM has JAVA,ABAP, COM, .NET(ver.7.1) API and you can use it for custom development
SAP MDM has own web service for work with data in repository
SAP MDM has own packages for development SAP NetWeaver Portal content
SAP MDM has own workflow integrated with SAP NetWeaver Portal trough UWL
SAP MDM has application for web publishing
and many many other functionality from your list
more about SAP MDM you can read here:
http://help.sap.com/saphelp_nwmdm71/helpdata/en/index.htm
Regards
Kanstantsin Chernichenka

Approval Process within SAP MDM

Can SAP MDM workflow handle multiple approval process. Is MDM support looping mechanism?

Hi Rajesh,
If approver rejects the records then the workflow will go back to previous step also u can branch the workflow on the basis of approve/disprove i.e. if the records approve then to a step and if approved then to a default step by using Branch.The record will be in MDM .The workflow history can be seen in data manager.And to have a report u can make a application. The link shows hw to have the history.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/001d22fb-622d-2b10-22ac-998acecf68a8
The history will give complete report about approve/reject.
Rgds
Ankit

SAP MDM, ORACLE MDM, Microsoft MDM and IBM MDM

Could someone discuss the differences and similarities between these MDMs-
SAP MDM, ORACLE MDM, Microsoft MDM and IBM MDM. Who is/will dominate the Market?
Thank you.
Priya.

Hi priya k ,
These r the details regarding MDMs-SAP MDM, ORACLE MDM, Microsoft MDM and IBM MDM.
SAP Master Data Management
SAP Master Data Management (SAP MDM) enables master data on customers, partners and products to be consolidated and harmonized across the enterprise, making it available to all staff and business partners. A key component of SAP NetWeaver, SAP MDM ensures data integrity across all IT systems.
The SAP NetWeaver Master Data Management (SAP NetWeaver MDM) component of SAP NetWeaver creates the preconditions for enterprise services and business process management. The functionality represents customers, products, employees, vendors, and user-defined data objects in unified form. With SAP NetWeaver MDM, customers can manage master data and supplemental content, such as texts, PDF documents, high-resolution images, or diagrams in a central business information warehouse.
SAP Master Data Management (SAP MDM) is a component of SAP's NetWeaver product group and is used as a platform to consolidate, cleanse and synchronise a single version of the truth for master data within a heterogeneous application landscape. It has the ability to distribute internally and externally to SAP and non-SAP applications. SAP MDM is a key enabler of SAP Enterprise Service-Oriented Architecture. Standard system architecture would consist of a single central MDM server connected to client systems through SAP Exchange Infrastructure using XML documents, although connectivity without SAP XI can also be achieved. There are five standard implementation scenarios:
Content Consolidation - centralised cleansing, de-duplication and consolidation, enabling key mapping and consolidated group reporting in SAP BI. No re-distribution of cleansed data.
Master Data Harmonisation - as for Content Consolidation, plus re-distribution of cleansed, consolidated master data.
Central Master Data Management - as for Master Data Harmonisation, but all master data is maintained in the central MDM system. No maintenance of master data occurs in the connected client systems.
Rich Product Content Management - Catalogue management and publishing. Uses elements of Content Consolidation to centrally store rich content (images, PDF files, video, sound etc.) together with standard content in order to produce product catalogues (web or print). Has standard adapters to export content to DTP packages.
Global Data Synchronization - provides consistent trade item information exchange with retailers through data hubs (e.g. 1SYNC) Some features (for example, workflow) require custom development out of the box to provide screens for end users to use.
History
SAP is currently on its second iteration of MDM software. Facing limited adoption of its initial release, SAP changed direction and in 2004 purchased a small vendor in the PIM space called A2i. This code has become the basis for the currently shipping SAP MDM 5.5, and as such, most analysts consider SAP MDM to be more of a PIM than a general MDM product at this time.
Getting Started with Master Data Management
/docs/DOC-8746#section2 [original link is broken]
Master Data Management (SAP MDM)
http://help.sap.com/saphelp_mdm300/helpdata/EN/2d/ca9b835855804d9446044fd06f4484/frameset.htm
http://www.sap.com/netherlands/platform/netweaver/components/mdm/index.epx
http://www11.sap.com/platform/netweaver/components/mdm/index.epx
Master Data Integration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/f062dd92-302d-2a10-fe81-ca1be331303c [original link is broken]
Master Data Operations
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/a0057714-302e-2a10-02ad-b56c95ec9376 [original link is broken]
Master Data Quality
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/c0a78be0-142e-2a10-f6b9-f67069b835da [original link is broken]
Oracle MDM
Oracle MDM is a core Fusion technology that will enable them to integrate their diverse portfolio of acquired solutions (PeopleSoft, JD Edwards, Siebel, etc.) and allow them to work together much more effectively.MDM is also a key component of Oracles middleware strategy to aggressively target heterogeneous environments solutions running on different databases, operating systems, and using different data warehouse or analytical solutions. Oracle is a leading provider of ERP and CRM applications, but more broadly they are a provider of core platform solutions that help pull together and harmonise all a companys IT assets.
Master Data Management solutions provide the ability to consolidate and federate master information from disparate systems and lines of business into one central data repository or hub. As part of its Master Data Management strategy, Oracle offers solutions that enable customers to synchronise critical information in a single, central location to achieve an accurate, 360-degree view of data, whether from packaged, legacy or custom applications. Oracle offers the following solutions:
Oracle Product Information Management Data Hub Enables companies to centralise, manage and synchronise all product information with heterogeneous systems and trading partners.
Oracle Customer Hub Centralises, de-duplicates and enriches customer data, continuously synchronising with other data sources across the enterprise, to provide a single, accurate, authoritative source of customer information throughout the enterprise.
Oracle Financial Consolidation Hub Allows companies to control the financial consolidation process by integrating and automating data synchronisation, currency translation, inter-company eliminations, acquisitions and disposals.
Clean, consolidated and accurate master data distributed throughout the enterprise can save companies millions of dollars annually. With Oracle, organisations are equipped to leverage the best data management practices available today to help dramatically increase operating efficiencies, improve customer loyalty and ensure corporate governance.
MDM solutions provide the ability to consolidate and federate disparate systems and lines of business into one central data repository. Acxiom is the world's largest processor of consumer data and collects and manages more than a billion records a day for its customers, which include nine of the country's top ten credit-card issuers and most major retail banks, insurers and automakers. By integrating Acxiom's consumer data with Oracle's comprehensive MDM solutions, Oracle plans to provide customers with a pre-packaged, content-enriched customer information repository with unprecedented levels of data quality. This hybrid approach to customer data management will help clients conduct better, faster and easier MDM projects and perform more targeted marketing campaigns to cross-sell and up-sell into existing customer accounts.
Oracle's MDM solutions serve as a customer data hub to unify customer data across multiple business units and functionally disparate systems. Oracle's comprehensive functionality manages customer data over the entire lifecycle: from capturing customer data, to cleansing addresses and spelling, identifying potential duplicates, consolidating duplicates, enhancing customer profiles with external data and distributing the authoritative customer profile to the operational systems.
Microsoft MDM
http://www.microsoft.com/sharepoint/mdm/default.mspx
The Microsoft MDM Roadmap
http://www.stratature.com/portals/0/MSMDMRoadmap.pdf
http://msdn2.microsoft.com/en-us/library/bb410798.aspx#mdmhubarch_topic1
The IBM View of MDM
http://www.db2mag.com/story/showArticle.jhtml?articleID=167100925
cheers!
gyanaraj
*******Pls reward points if u find this informative

SRM Product / Material creation - Data flow to SAP MDM

Dear SAP friends,
I need your help with 2 issues. Thanks in advance for your collaboration.
Our client needs to create products and make them available to purchase almost immediately.
The scenario we had working for the last 2 years was: product creation in SRM (fields: short description / product category / measure unit), that would then be sent to SAP MDM for data enrichment, through BBP_CCM_TRANSFER_CATALOG (JOB running every 1 minute). This solution worked well for the last 2 years.
Recently, we are having some problems with this job. We noticed that, sometimes SRM doesn´t send the new products to MDM, and we think it´s a report performance problem. The report doesn´t maintain is normal behavior when executed every 1 minute.
SAP advice is to only run this report once a day. That would obviously require having a minimum time frame of 1 day between product creation and its availability (purchase), which isn´t acceptable in this client business model.
Question 1: Did anyone have a client with similar requirement? What was the implemented solution?
Because of report performance problems, we are running it (BBP_CCM_TRANSFER_CATALOG) every 5 minutes. It happens that sometimes, more than one catalog manager creates products in that time frame, and MDIS when importing the products to MDM, creates one unique workflow JOB making it impossible to assign it to both catalog managers for enrichment.
Question 2: How can we ensure that SRM sends only one product per xml files sent to XI / PI ? Or, perhaps, ensure that XI / PI splits the xml file sent from SRM into several files with one product each.
Thank you very much for your help in advance,
Best Regards,
João S. Carvalho

Hi meka
In product costing values flows as follows;
In product cost calculation raw material prices are costed which comes from material master in MM01
Product operations: i.e material BOM and master receipe or routings from PP module.From PP module operation costs comes in product costing.
In CO module: In Tcode KP26 we maintain activity\cost center planning for activities like machine hours, set up hours, labour hours etc.Here we define plan quantity and plan prices.
In Cost Sheet (KZS2) we maintain base cost elements & overheads and While order creation we calculate planned cost of that particular material.and then check the variances after getting actual cost of product.
Hope this will help you and if found useful assign points.
Let me know if you need more information.
Regards
Nilesh.

SAP MDM Joining tables in console? Help needed.

Hi,
I am placed in SAP MDM Project.
Currently, we have an unique requirement.
We, have to join two tables of SAP MDM Console in an unique field
named(House No and PO Code).
Actually, we have a main table named Business Partner and a Flat table
named Address.
Now, we have a field named House No and PO Code(Business Partner) which I have made as unique.
Also, the Field named House No and PO Code(Address) is unique.
Now, my colleague suggested if we can make remote key mapping at the time of import
it will automatically populate the address data for each individual.
But it is not true. Remote Key mapping is a different concept.
If Remote key is mapped with any field of the Main table.
It will show remote key mapping for that field with a remote system.
When data is syndicated back after modification same data is reflected in that remote system.
Only thing that we can do is that make House No and PO Code (Business Partner) as Lookup(Flat) field and it is mapped with the Flat table Address.
Now, the SAP MDM Data Operator needs to select the address manually from say 10,000 address records for a person George Smith in main table(Business Partner).
No other way round.
Please suggest if there is any other way.
Thanks and Regards
Kaushik Banerjee

I am closing it.

SAP MDM Vendor email addresses are not in order when sent to SAP R/3

Hi Experts,
We were trying to maintain vendor email addresses in this order in SAP MDM:
E-mail address: massupa@nexus
Sequence Number: 001
E-mail address: win@nexus
Sequence Number: 002
E-mail address: satita@nexus
Sequence Number: 003
But when saving the record, its order get mixed up like below: (I believe it was arranged alphabetically automatically---> is this the standard MDM functionality?!)
E-mail address: massupa@nexus
Sequence Number: 001
E-mail address: satita@nexus
Sequence Number: 003
E-mail address: win@nexus
Sequence Number: 002
When it gets syndicated to ECC, its order was maintained incorrectly with incorrect IDs:
E-mail address             ID
massupa@nexus        001
satita@nexus              002   -
> should be 003
win@nexus                 003 -
> should be 002
we checked both the XML Files and the IDOC and found that it has the same order maintained in SAP MDM
massupa@nexus        001
satita@nexus              003
win@nexus                 002
But how come the IDs were changed in R/3?
Many thanks in advance!

Hi Mike,
As per your requirement, i feel that for ID either you can create a new field say sequence ID in this e-mail addresses table of MDM and thus can syndicate it or can also use ID as key using remote key concept. I mean for this e-mail addresses table, you can set property Key mapping = yes in MDM Console and thus can use this IDs as key for this email address e.g. for massupa@nexus you can save ID as Key.
So during syndication, map this field with target IDOC structure field and I mean Remote Key under e-mail addresses table with IDOC ID target field. In this way you can have correct IDs with their corresponding email addresses.
Kindly let me know if you are looking for something else.
Regards,
Mandeep Saini

Brief discussion on SAP XI and its' Integration with SAP MDM.

Hi,
I have never worked on SAP XI.
I am discussing it on brief, please give your valuable replies.
SAP XI consists of System Landascape Directory(SLD).
SLD Consists of Business System and Techinical System.
Technical System contains all information about the software
component. The Business System consists of Inbound and Outbound Business
System which are used as logical names for data transfer.
There is communication Channel for Receiver and Sender Business System and n agreement
is signed between Sender and Receiver.
Outbound Interface defined for Business System Outbound and Techical System associated
with the Business System,
Inbound Interface defined for Business System Inbound and Techical System associated
with the Business System.
In SAP NetWeaver XI Integration Directory, we have defined the Integration Scenarios,
Actions, Interface Objects, Mapping Objects, Adapters Objects.
Mapping Object defines the Structure and Value Mapping.
Adapter Objects defines the Adapter program which implements RFC Adapter, FTP Adapter logic.
FTP Adapter is used for XI-MDM Communication.
RFC Adapter is used for XI-ECC Communication.
Integration Repository: Both Outbound and Inbound Interfaces are Mapped with Value mapping and
Structure Mapping inside Integration Repository.
The File Adapter takes the File from the Outbound port of MDM System
and sends it as IDOC to Receiver Business System.
Value Mapping must be done between Sender and Receiver interfaces.
Value Mapping is done by XSLT or Java based program.
SAP NetWeaver XI Integration Server at runtime:
Message Split, Interface Determination, Receiver Identifaction, Mapping, Techincal Routing
and Call Adapter Proccess are done.
In SAP XI 3.0 and MDM 5.5:
Step 1: Create busines system as service.
Step 2: Create communication channel for each business service. If the system can communicate
through different channels, then create all possible channel types if necessary.
Step 3: Create receiver agreement between the systems.
Step 4: Interface determination:
- Here you see for the first time the software component mentioned;
there are some special requirements regarding this software component in relation to the customizing ID mapping.
- To modify this software component, the customer needs to copy the SAP standard delivered software component
into its own namespace. The customer is able to modify to create archives
for the customized ID mapping.
Receiver determination.
Configure an FTP Server on the MDS.
Create a send folder for outbound messages using outbound port(s) for
remote systems(s).
Create receive folder inbound messages using inbound port(s) for remote systems.
This ia all about concept of SAP XI Infractsture and its' Integration with SAP MDM 5.5.
Regards
Kaushik Banerjee

Hi Kaushik,
You must be aware of File types that MDM Import Manager can Import i.e. we have XML, Excel etc. Now there are two transactions to extract data from R3
1. MDMGX -
         - For lookup table extraction
         - Output in XML format which MDM can import without using XI.
          - FTP can be configured to put the file in the desired folder which will be then picked by Import Server.
2. MDM_CLNT_EXTR -
          - For Main table records.
          - Output is in Idoc format which MDM doesn't understand hence we need XI in between which converts Idoc file received from R3 into XML which can then be imported using Import Manager or Import Server. For this we need to implement XI Scenario that consists of Source System, Receiver System, Type of Data etc.
Just a basic understanding...
Regards,
Jitesh Talreja

Vendor Master Fields to be considered for Centralization in SAP MDM

Hello Experts,
In my present assignment, we have 3 different ECC systems each for three different businesses. Now the objective is to consolidate, Harmonize and centralize the Vendor Master for all these standalone ECC systems in SAP MDM.
So multiple discussions are going on the which Vendor Master fields to be kept as Global fields and which ones as local in Central Vendor Repository in SAP MDM. The debate is whether should we keep "Vendor Account group" as Global field or as Local field in MDM.
The debate is each inidividual business unit has defined different account groups for the same vendor in their respective systems.
The question is : What is the best practice-- Should we keep Vendor account group as main table field and define Vendors with one unique account groups OR we maintain the account group in qualified table each pointing to different business unit.
Your inputs are highly appreciated
BR
PTM

Hi Manoj
The debate is each inidividual business unit has defined different account groups for the same vendor in their respective systems.
The question is : What is the best practice-- Should we keep Vendor account group as main table field and define Vendors with one unique account groups OR we maintain the account group in qualified table each pointing to different business unit.
In my opinion this is going to be very complex solution. Ideally we need to define all the Harmonization rules before syndicating data to different target systems.
Is this possibel that the same vendor record which is existing as vendor of different account groups in different systems have same set of attributes. If yes then enabling the remote key for Account group Lookup field is one option and defining a unique Account group 'AG" (which is mapped to say AG1 from remote system1, AG2 from remote system2 and so on..)..
Managing this via Qualified table will be very complex and not advisabel. As Rajesh also mentioned Account Group in MDM should be considered as Global attribute and all such harmonization rules should be defined in your project. AG1=AG2=AG in above exmaple.
Hope this clarifies.
Thanks-Ravi

Order to import data in to SAP MDM using import manager

HI All,
Is this the order to import data in to SAP MDM?
Import look up tables
Import Hierarchy Tables
Import Taxonomy Tables -
Non -Qualifiers
Then import main table----map Qualifers along with Mian table and import...
Can we import entire taxonomy tables (Qualifiers, Non-Qualifers) along with main table after importing look up tables?
Thanks
Rajeev

Hi Rajeev
The sequence mentioned by you is correct for importing data in MDM- flat lookup, hierarchy first followed by Main table.
Can we import entire taxonomy tables (Qualifiers, Non-Qualifers) along with main table after importing look up tables?
I am assuming that you are implying Qualified table here.
Import to qualified tables can be done in 2 ways-
1. Import separately using the unique field for the main table for linkages to the main table records.
2. Import can be clubbed with the main table import itself. In the import map we can use Join functionality to do a lookup based on the unique field for the main table.
For more details on the mechanism please go through the threads below-
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/6090d0bd-1da7-2a10-468f-bdd17badb396
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8090941f-a5a7-2a10-3ba6-b4af5ec6d97b
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/308c62a2-5faa-2a10-fda6-fa4aa7169734
thanks
Ravi

How to handle data quality by using rules defined outside SAP MDM

Hi All,
I have a requirement: There are number of cleansing rules defined in different quality product. I need to integrate that quality tool with SAP MDM. Is it possible to do this? I guess with the help of Java API's!!!!
Can I use MDM enrichment controller here? If yes, than how to use it.
thx,
R.n

Hi R.n
The MDM Enrichment Framework is certainly the best way to answer your requirements.
Please see the Enrichment Architecture guide at MDM Documentation Center http://service.sap.com/installMDM
A recorded demo session at SDS Community Page is available to present such system.
Regards
Orit

MDM Workflow Launch Problem version SAP MDM 7.1.2.59

Hi All,
I have installed SAP MDM 7.1.2.59 on SUSE Linux Server 64-bit m/c. And installed all Clients on Windows XP.
MS-Visio is also installed on my windows Box.
But when i open data manager i am seeing the workflow icon disabled. Also not able to add a workflow.
Any one knows what is the reason for this?
Please let me know if i need to add any specific patch at Server side.
Srinivas

Hey -
Checkout your visio setting
In MDM Data Manager, make sure the Workflows table is the current table. In the Records pane, select any workflow record.
In the Record Detail tab, then double-click on the Workflow property to open Microsoft Visio. Choose Tools > Options from the Visio main menu.Choose File Paths to open the File Paths dialog. In the File Paths dialog, set both Add-Ons and Start-Up to the folder where the Worklfow.vsl file is installed (the Data Manager installation folder, by default). Click OK to close the File Paths dialog.
also go through the links below for similar issue
for MS visio version
MS Visio version with MDM 7.1
MS Visio 2007 for MDM Workflow
MDM workflows and MS VISIO
Re: MDM workflow.
Hope that Help
thx
Deep

Reporting on records merged in SAP MDM

Similar Messages

Maybe you are looking for