SAP MDM Repository Roles

Dear Friends,
We have a repository in MDM. As part of the MDM repository creation, the system delivered a user names 'Admin"n with super access.
Now, we wanted to create a user with the role "Who can just have access to Create Users".
Also, we wanted to create a user with the role "Who can do all the repository development work but shouldn't have access in Administration space (like create users, ports and so on)".
Kindly help me out and let me know on how to achieve this?
Thank you,
Sri

Early this month we upgraded the MDM server to:
MDM Server version: 5.5.63.57
And the portal components:
MDM 5.5 SP06 Technology Patch 3 (Build 5.5.63.57)
MDM 5.5 SP06 Application Patch 3 (Build 5.5.63.57)
MDM 5.5 SP06 Java API Patch 3 (Build 5.5.63.57)
However the issue just began 2 days ago?
We started intgrating MDM Workflow with UWL and assigned Roles and Iviews to the Universal Worklist Configuration
It seems the Iviews work for a while and then after some time everything gives up? Very confounding
And yes we are using standard Iviews (search, Result and detail)
Thanks
Edited by: Marty Monroe on Oct 31, 2008 3:07 PM

Similar Messages

Filter the results set for custom iviews in SAP MDM

We have a scenario where based on the user name/user role we want to filter the results retrieved by an search result iview developed for accessing data from SAP MDM Repository.
E.g.
We have a lookup table called Plants which contains master data pertaining to manufacturing plants.
The portal user P00100xxyy is responsible for maintaining master data for a plant 1101. However, the plant lookup contains data for other plants as well.
We would like to prevent the user P00100xxyy to see/modify data for other plants in the table.
We have explored the core MDM functionality of security/constraints. It does not provide row level granularity and we are hoping that the iview approach can help us achieve row level filters.

Hi Rajni thanx for ur prompt reply
The actual problem is that :
we have approx near about 100 Account Group, so it would become very complex to replicate same condition 100 times
AND
these account group may keep on increasing so even maintenance point of view it would be hard to maintain.
can u tell me some other way to do it, i mean is there any other feature by which we can perform validation in MDM.
Regards
Kuldeep

Create Roles with acess control in SAP MDM

Hi Experts,
I am new to SAP MDM.I want to know how to create roles with access control for various users in SAP MDM.
Thanks,
Manoj

hi,
in the console; you can create roles with access control and you can assign these roles to users.
follow this path:
Console --> repository --> Admin node --> roles,
here you can create new role. for role here you can maintain
1. role detail
2. Functions --here you can restrict the particular role , none / Execute the functions.
3. Tables/fields -- here you can give access to the role Read only / Read and write, and you can apply constraints also.
and follow the links:
http://help.sap.com/saphelp_mdm550/helpdata/en/8e/9f9c427055c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_mdm550/helpdata/en/8e/9f9c427055c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_mdm550/helpdata/en/8e/9f9c427055c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_mdm550/helpdata/en/8e/9f9c427055c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_mdm550/helpdata/en/8e/9f9c427055c66ae10000000a155106/frameset.htm
hope this may help you,
Regards,
Srinivas

SAP MDM-GDS repository structure

Hi,
Does anybody have any input or knowledge of SAP's direction regarding repository structures for MDM and GDS now that they've begun integrating the functions into the MDM solution the offer?
At present, whilst the GDS Console is basically just accessing data in an MDM repository, it can't be your core MDM product data repository, but rather it has to be a separate one, set up specifically for GDS and nothing else, and thus it needs to be populated separately. I am wondering if this is a long term vision, or just a result of the way the package has been developed and that further integration will be forthcoming.
Any ideas?
Steve

Hello lis716
I'm not recomend working with SAP MDM database directly moreover modify some data at Database level because database structure is close information. (i had expiriens to mass upload users and their roles directly in MDM database, after that operation repository hasn't been started - repair returned a lot of errors and i was very happy when repository has been started)
You can lost important data because database structure may be modify in any time.
SAP MDM provide API for different development platforms as is .NET, ABAP, JAVA, COM.
My suggestion you should use API in your application for connect to data.
Additional information about API you can find here:
https://websmp209.sap-ag.de/installmdm71
Regards
Kanstantsin Chernichenka

SAP MDM Console not allowing to add new fields or load repository

Hi all,
We are in SAP MDM 7.1 SP06. I do have access to create table, fields, ports etc., And I also have access to load and unload repository.
But when I login to SAP MDM Console and repository, options to load repository --> immediate and update indices are disabled. This is happening for Add/ Delete Table/Fields/Port etc.,
However, if I login to repository using MDM console in another laptop or system using the same userid, I am able to perform all the operations mentioned above.
Can you please help me with any suggestions to fix this. I do not want to reimage my laptop now inorder to fix this.
I tried to uninstall and install mdm console again but in vain.
Thanks,
Rajesh

Hi Rajesh,
In the Main Menu you have a lock sign,click on that and unlock the view.
This should solve the problem.
Thanks,
Ravi

Creating Repository in SAP MDM

Hi,
I am getting the below error when I am trying to create a respository in SAP MDM.
"Error Initializing database engine.".
Regards,
Venkatesh

hi,
follow the link:
Installing MDME 5.5
Database error - MDM server installation
hope this will help you.
Regards,
srinivas

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

SAP MDM Console

Hi,
I'm new to MDM Console. Can anyone please tell me how can I, from SAP MDM Console restrict a particular user from <u>viewing</u> specific records in MDM Data Manager.
Thanking you in advance.
Hemal

Hi,
You can achieve this using Masks.
Step 1:
In the Data Manager , you filter records based on what ever condition you are looking for. Add the filtered records to a Mask.
If you have no masks defined in the Data Manager.
Select Masks table from the top left corner list in the Data Manager and create a Mask.
Once you finished creating the Mask, go back to the Main table and add the Filtered records to the created mask.
(Select all the records right click and select Add to Mask and select the Mask).
Step 2:
a. For New Role:
1. In the MDM Console for that particular repository, create a new role and in the role details grid, select Table/Fields tab and look for Masks table. In the Constraints column, you select the Mask you created in the Data Manager.
2. Assign the created role to the user.
b. For Existing Role:
In MDM console select the role in the repository and
in the role details grid, select Table/Fields tab and look for Masks table. In the Constraints column, you select the Mask you created in the Data Manager.
Hope this helps.
Let me know if you need any additional information.
Thanks and Regards
Subbu

Step by step procedure of SAP MDM process

Hi PP Gurus,
Can anybody give me the step by step process of SAP MDM.
Regards,
Pramod

Hi,
1.First of all you need to know the list of the source systems whose master data you need to maintain in MDM.You can have the source data in the form of XML, excel or MS Access etc. The first thing you need to perform is designing of the repository in the MDM console wherein you have the structure for the incoming data . Here you also need to create the users , roles , mention the remote systems from where you are extracting the data .Then Extract or import source data (e.g. Customer master data, Product master data, etc) from connected remote sytems i.e client applications.
2. Consolidate this data centrally on MDM, cleanse it.
3. Then harmonize or export the data through MDM syndicator tool. Then if there is FTP then dump all your XML data in the FTP from where SAP XI would pick the data and send it back to the different client systems from where you have fetched the data.
4. In the client applications, the received data can be complemented with local attributes.
Reward points if it is helpful.
Regards,
Chinmoy
Message was edited by:
chinmoy mohanty

MDM Developer Roles ???

Hi Frnds,
I am XI Consultant , I am working for past 2 yrs on SAP XI, But recently i started learning MDM, I understood the concept of MDM and MDM Components, Pls help me who are working on SAP MDM Implementation
What exactly role of MDM Developer will do??
is there any methodologies to follow like SDLC, asap methodologies
explain Day to day activities, If any body implementing SAP MDM
And what is the difference between SAP MDM and ORacle
Regards,
Raj

Hi Raj,
This link will help you for most of the queries.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/newtoMDM
What exactly role of MDM Developer will do??
and
explain Day to day activities, If any body implementing SAP MDM
MDM(Master Data Management) is used to:
1. Consolidate master data from external system
2. Master data can also be created with in MDM.
3. Full harmonization scenario means importing data from external systems and after cleansing, sending it back to required sytems.
Console:-> used to create/maintain repositories, authorizations and Admin roles
Import Manger-> used to import the legacy data in to the repository ( like uploading data into the SAP tables using BDC)
Data Manager:->Managing the data in the repository( deleting duplicate data, merge the same data, consolidation, Normalization). Very important for Matching strategy.
Syndication:-> Sending data to the other or source system (legasy system).
is there any methodologies to follow like SDLC, asap methodologies
Yes, we implemented using ASAP methodology.
And what is the difference between SAP MDM and ORacle
SAP MDM, ORACLE MDM, Microsoft MDM and IBM MDM
Hope this helps,
+ An

Help Required -- Can we use SQL Query to READ data from SAP MDM Tables

Hi All,
Please help.........
Can we use SQL Query to READ(No Creation/Updation/Deletion just Read) Data from SAP MDM tables directly, without using MDM Syndicator.
Or direct SQL access to SAP MDM tables is not possible. Only through MDM Syndicator can we export data.
Thanks in Advance
Regards

All the tables you create in Repository comes under A2i_CM_Tables in Database named as your repository name. So the tables names are fields of table A2i_CM_Tables. Now i tried it but cant make it.
Now, I dont think its possible to extract all fields in tables and there values using select query. May be pure sql guy can do that or not.
But there is no relation of data extraction and syndicator. Data is viewed in Data Manager. and you can also store data in a file from DM also.
BR,
Alok

Need help on extraction of MDM repository data

I need to take an extract of records from the Customer repository. Total count of the records will be around 25,000 when the filter criteria is applied. As per the requirement I need to select some fields from main table, some from flat look up and few from the qualified look up tables.
What are the possible ways to take the extract?
I am using SAP MDM 5.5. I tried using the export option in Data Manager, but the qualified look up field values did not come properly in the file. The whole qualified look up table values came under a single column. So that exported file is not of much use for my requirement.
Please suggest me some ways.

Hi Priyanka,
Suggest you to use SAP MDM Syndicator for extracting data. Please refer the Syndicator document for all the details.
Thanks,
Shamir

Data Import from SAP R/3 to SAP MDM 7.1 without SAP PI

Hi All,
I have a requirement to import Vendor Master data from SAP R/3 to SAP MDM 7.1 on a regular basis. What are the Options available for data transfer between these two systems without any middleware(like SAP PI,etc). I checked the SAP Documentation and found the scenarios with SAP PI as middleware.
I have few very basic ideas:
1) Will there be any way for SAP MDM to pick a file from certain location and load the data..
2) Shall I use MDM ABAP API to write a program to connect to MDM Repository and schedule this at regular intervals to achieve the data transfer.
Pls suggest the best design approach..
Thanks in advance.

1) Will there be any way for SAP MDM to pick a file from certain location and load the data..
ANS : No, MDM will not pick up the file, file can be pick up from MDM Inbound folder and send from outbound folder for automize process and for MDM manual Process you can pick up and send file to local desktop, network shared path
2) Shall I use MDM ABAP API to write a program to connect to MDM Repository and schedule this at regular intervals to achieve the data transfer.
ANS : require to write code at ABAP side
so ABAP program will pick or send data file to MDM folder
Note following point
1. Require to write ABAP Program which will pick or send data file to MDM outbound / Inbound folder
2. Require to do some technical setting for ABAP program at SAP side, technical person will help regarding this matter
Note : There are many disadvantage and time consuming procss, monitoring file and it is not advisable to go without any intermidiate software for e.g PI, Tibco
Thanks,
Jignesh Patel

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

SAP MDM Repository Roles

Similar Messages

Maybe you are looking for