Key benefits of using MDM

Hi,
I am trying to build a business case as to why a business should go for MDM implementation. Can anyone provide any insight into what are the key business benefits of implementing MDM ?
Thanks

Hi GS,
In addition to above posts
MDM Implementation basically deals to manage and maintain master data of the any firm/organization.
The Dis separate and bad data is lying through out your IT landscape. to get a "singel version of truth" or "360 degree view of your data" you need to implement MDM.
though many MDM technologies are in market in order to implement. but as far as SAP MDM is concern, it is the most versatile and beautiful platform over all others
as it gives you
Master Data Integration :
Use MDM remote system extractor to extract customizing data in the initial setup of your MDM system
Use MDM remote system extractor to automatically extract master data
Use MDM import mechanisms to load master data from various sources
Use MDM business content to integrate data
Use MDM Syndicator to distribute master data to various targets
Use MDM APIs and Web services to integrate data
Some of the Operations :
Data Modeling
Role-Based Data Access
Search
Workflow-enabled Data Creation/Maintenance
Data Publishing
Master Data Quality
Use validations and assignments to check the accuracy and consistency of your master data
Create more complete and meaningful master data using the MDM Enrichment Architecture
Create non-redundant and consistent master data using matching and merging capabilities
I think things are clear for you as far as MDM Implementation is concern.
Hope it helps.
Deep

Similar Messages

Why to Use MDM

Hi All,
Could you plz tell me,
In R/3 also Master data is available. Why we are using MDM( For Master Data ) seperately ?
In R/3 Master tables are there (MARA, KNA1, VBAK), Then Why we are Designing seperate Repositories in MDM for store the data ?
Regards...
Murali.
Edited by: Murali Dusi on Jul 3, 2008 12:24 PM

Hi Murali,
In R/3, Master data is available but we use MDM( For Master Data ) separately because of some special features of MDM which are given below:
CAPABILITIES OF MASTER DATA MANAGEMENT
1. Synchronization:
An MDM layer improves the ability to share, consolidate, and analyze business information quickly, both globally and regionally. And it makes it possible to rapidly assemble new, composite applications (software that combines the elements of a business activity in a coordinated application and user interface) out of accurate master information and reusable business processes. For e.g. helps to maintain Universal dimensional structures for multi-organizational regulatory compliance.
2. Reduced time to market.
MDM provides a single system for creating and maintaining product information, promotions, and rich, accurate consumer communications via online and traditional channels. One major retailer used MDM to reduce the time to introduce a new product from four weeks to one day.
3. Supply chain improvements.
A single, accurate and agreed upon definition of products and suppliers, made possible by MDM, eliminates duplication, increases buying power, and provides insight into supplier relationships. A major European retailer is combining MDM with Web Sphere Portal to allow more than 30,000 suppliers to manage their own master information
4. Revenue increases.
MDM contributes to better customer relationships. By creating a single 360 degree view of customers, MDM helps sales, marketing, and service teams better anticipate customer needs, provide targeted offers, and improve customer service. Revenue is increased by, for example, from providing more accurate and comprehensive information to the right customers at point of sale.
5. Realize Internal Efficiency
An MDM layer enables companies to realize internal efficiencies by reducing the cost and complexity of processes that use master data (through fewer code clashes, less data duplication, better control over business processes, and so on). It reduces manual translation and analysis to improve repeatability and speed to insight.
6. Finance and Operations:
MDM can lead to more accurate reporting and BI, more efficient planning and budgeting and enhanced ability for regulatory compliance.
7. Sales and Marketing:
MDM can provide a "single view of the customer," leading to greater customer satisfaction. For example Spend Analysis is one the trend that is used in Sales and Marketing with the help of MDM, say for example if we say HCL supplies computers to Wipro Technologies and also to Wipro InfoTech, now if HCL uses MDM than the data would be consolidated that is it would see that in total how many computers are being send to Wipro and accordingly HCL can plan out its business with Wipro like how much discount it has to give and all other business related issues.
8. Procurement and Supply Chain Management:
MDM could mean reduced delays in shipment and fewer errors in item coding. For Example Say we need to deliver a product to out Customer and if we have reliable and correct data, then we can send the Right Product to Right Place and at Right Time, because of which our delay in shipment would be less and it would also reduce the extra cost which the company has to pay for wrong shipment.
9. Product developers:
MDM means faster product launches and a better handle on customer feedback. For Example- We have heard about the companies like Maruti which deals in Cars, now say if Maruti comes out with a new Car Model, then it generally happens that many Customers do the Advance booking for that particular car, now if the data is not maintained properly then Company would not be able to release the product in Time and also this would affect its image in the Market, however if the Product launches on time we will always
get good Customer feedback which would in turn increase the reputation of our Company.
10. Customer Data Integration (CDI):
It is the process of consolidating and managing customer information from all available sources, including his contact details, customer valuation data, and information gathered through interactions such as direct marketing. CDI ensures that all the relevant departments of the company have access to the most current and complete view of customer information available.
11. Interpretability:
Interpretability, or the ability to recognize and understand data, is one of the biggest challenges to implementing successful data quality programs. In many cases, stored data exists in a wide variety of formats. Also, the individual elements within a given record have not been separated or may contain misleading data. Before any data quality processes can be implemented, the source data must be parsed into the appropriate components so that it can be understood by data quality systems. In addition, certain data elements may need to be moved, deleted or formatted.
12. MDM maximizes the return on SOA Investments:
Much of the hype and attention in service-oriented architecture (SOA) deployments has gone into web service creation and deployment and management standards and technologies. However, if data is inconsistent across applications, composite applications and business processes that cut across multiple systems and departments will not yield the desired results and benefits. For example, a composite application in a large multi-channel financial service institution that calculates a customers global credit risk will only work if that customer is described in a consistent manner across retail banking, brokerage, mortgage, and credit card systems. In a retail environment, a composite application that gets a customers order history from a data warehouse and recommends a related product requires consistent product and customer information across all the relevant systems. On a smaller scale, even business services to update an address or provision a service require semantic consistency of master data across customer relationship management (CRM), billing, and product systems.
Effective MDM helps organizations realize the full ROI potential from their SOA and business process management (BPM) investments.
13. High-end scalability:
Scalability is the growth capacity of a system. If a companys data volumes, transaction-processing rates and number of simultaneous users are modest and static, then most products should be able to meet those scalability requirements. But that is not the typical description of an MDM candidate.
Global enterprises with immense amounts of master data, millions of records, tens to hundreds of client business applications and thousands to tens of thousands of users are more the norm. Master data management is a large task. Smaller vendors with lesser-known products simply will not have the capability to support the capacities required.
14. Customer satisfaction due to effective and efficient supply chain management.
15. High productivity due to effective inters operability in company.
16. Effective formulation of policies in company in respect of vendors and customers.
17. In the absence of an MDM function, each system, application, and even department within the enterprise collects its own version of key business entities. Like the collection of customer data. Key attributes such as customer name and address information are collected repeatedly throughout the enterprise. Unfortunately, it is rare that this gathering process produces the same or consistent data about customers. This leads to the critical difficulty (aside from the storage costs of it) with such redundant data poor data quality. According to a report from The Data Warehousing Institute, Data Quality and the Bottom Line by Wayne Ackerson, corporations lose more than $600 billion a year due to poor data quality, and most of that cost can be attributed to redundant and low quality master data.
18. Organizations constant changes as new products and services are introduced and withdrawn, companies are acquired and sold, and new technologies appear and reach maturity. this changes can be managed effectively in MDM and can be reflected every where in the company data.
19. Organizations can build a complete view of their customers, products, and other critical business entities.
Regards
Richa

Unable to Edit/Remove Remote Systems using MDM 7.1

Unable to find an answer to this in either the forums or the Wiki...
Using MDM 7.1 through the SAP MDM Console 7.1.03.54
I can add a new Remote System, it comes up with the default values for the Remote System fields:
Name: New Remote System, Code: NewRemoteSystem, Type: Inbound, Key Generation: None
But I cannot modify the field values nor can I delete the Remote System.
The right-click context menu always has 'Delete Remote System' greyed out.
Nor do I see any mechanism to modify the fields' values. Moving to the Remote System Detail pane, none of the fields are edittable; I have tried left-clicking, right-clicking, double clicking, using the Edit tool bar menu - nothing lets me edit these fields.
My user account has the Admin role. Looking to the Admin role, it has Execute for all functions, and Read-Write to the Remote Systems in the Tables and Fields tab.
Any help would be appreciated.

Hi Andrew,
Your repository should be in unloaded state to make changes in any table whether main table, subtable, Ports, Special tables or Remote Systems table etc. As you want to make changes in your repository Remote Systems, please unload your repository->Go to Admin>Remote systems>Make necessary changes (Add/Delete/update)--> Then load repository.
Note: You can only add User and Roles during Repository loaded state.
Regards,
Mandeep Saini

How to map lookup main table field in another main table using MDM 7.1?

We created a new SAP MDM 7.1 repository with multiple main tables. The first main table is called ProductMaster table which contains Products information. The ProductCode is the primary key and the only display field for the table during data loading process. The second main table is ProductByRegion table which has a main table lookup field ProductCode and a RegionId field. These two fields (ProductCode and RegionId) combine as the PK for this main table. Both main tables have key mapping enabled.
I was able to load ProductMaster table using Import Manager. But Iu2019m having trouble to load data into ProductByRegion table using MDM Import Manager. Although I have met all the 5 requirements below (excerpted from MDM Import Manager Reference Guide P.222), the ProductCode wonu2019t show up on the destination value pane. If I mapped all productCode to NULL field, ProductCode wonu2019t load. If I u2018Addu2019 all ProductCode to Destination Value pane, the Import Manager added duplicated rows to Product Master table while only loading 1 record to ProductByRegion table. I canu2019t get ProductCode show up in Matching Destination Field list. When I checked ProductMaster records in MDM Data Manager, I right-clicked on one of records, chose Edit Key Mappings, it didnu2019t show anything. However, if I right-clicked on one of those duplicated rows, Edit Key Mapping shows remote system and key correctly.
Where did I do wrong? How can I fix the problem?
Thank you for help in advance.
From: SAP MDM Import Manager Reference Guide:
Mapping to Main Table Lookup Destination Fields
Import Manager handles main table lookup fields (Lookup [Main])
differently than other MDM lookup fields. Specifically, Import Manager
does not display the complete set of display field values of the records
of the underlying lookup table. Instead, the values it displays for a main
table lookup field are limited by both the key mappings for the lookup
table and the values in the source file.
Also, Import Manager does not automatically display the values of a
Lookup [Main] destination field in the Destination Values grid when you
select the field in the Destination Fields grid. Instead, for a main table
lookup field value to appear in the Destination Values grid, all of the
following conditions must be met:
u2022 The lookup table must have key mapping enabled
u2022 The lookup field must be mapped to a source field
u2022 The source field must contain key values for the lookup table
u2022 The destination value must have a key on the current remote system
u2022 The destination valueu2019s key must match a source field value
NOTE ►► The current remote system is the remote system that was
selected in Import Manageru2019s Connect to Source dialog (see
u201CConnecting to a Remote Systemu201D on page 416 for more information).
Vicky

Hi Michael,
Thank you very much for your response. I'm new to SAP MDM, I need some clarification and help regarding your solution.
I did use two maps to load ProductMaster and ProductByRegion separately. Here were my steps:
1. create main table ProductMaster with key mapping enabled at the table level and set ProductCode as unique and writable once (primary key).
2. create a map to load ProductMaster record from a staging table located an oracle database. But Key mapping didn't show anything when I looked at them using Data Manager.
3. create main table ProductByRegion with a lookup field looking at ProductMaster table. This field and RegionId combines as a unique field for ProductByRegion table.
4. create a map to load ProductByRegion table. But ProductCode records only shows on the source pane not destination pane and can't be mapped properly.
My questions:
1. How can I "Ensure that you add key mapping info for all ProductMaster records" besides enabling Key Mapping on the table level?
2. How can I define a concatenation of ProductCode and RegionId as a REMOTE KEY"?
Thanks a lot for your help!
Vicky

Remote Key Manupulation in Java MDM APIs

Hi ,
I need to do create/Modify/retrieve remote key using MDM Java APIs. I have found out two APIs for retrieve and modify of remote key (RetrieveRecordsKeyMappingsCommand and ModifyRecordsKeyMappingsCommand using RecordKeyMapping).
I am not getting any API to create remote key using Java APIs. Can anyone help me in this regard.If anyone has sample code also that would a great help.
Thanks and Regards,
Subhasis

Hi,
Please have a look on below code ...
          /TableID/
          TableId tableId = schema.getTable("table Code").getId();
RecordId recordId = new RecordId("R1"); // record id of record to which you are going to add key mapping
          /Remote System Properties/
          RemoteSystemProperties remoteSystem = schema.getRemoteSystem("RemoteSystemCode");
          /*Creating new instance of RecordKeyMapping */
          RecordKeyMapping recordKeyMapp = KeyMappingFactory.createRecordKeyMapping(tableId,recordId);
          /*Creating new instance of KeyMapping */
          KeyMapping keyMapping = KeyMappingFactory.createKeyMapping(remoteSystem.getId());
          /*Setting value to Key value */
          keyMapping.addKey("1234");
          /storing keymapping instance in RecordKeyMapping instance/
          recordKeyMapp.addKeyMapping(keyMapping);
          RecordKeyMapping [] recordKey = ;
          ModifyRecordsKeyMappingsCommand rkm = null;
          try {
           rkm = new ModifyRecordsKeyMappingsCommand(context);
          } catch (SessionException e) {
          } catch (ConnectionException e) {
          rkm.setKeyMappings(keyMappings);
          try {
               rkm.execute();
          } catch (CommandException e) {
Hope this helps you.
Cheers,
Veeru.

What are the key benefits and limitations of new pricing model of X5-2?

What are the key benefits and limitations of new pricing model that started with X5 version?

1. Elastic Configurations
Size/price hardware by the number of servers; Fixed configs no longer required
Start with 2 Database Servers and 3 Storage Servers. Incrementally add database or storage servers online.
2. Capacity-on-Demand (CoD)
Upon installation, activate 40-100% of the cores per server and reduce software licenses; Applies to Eighth Rack now too
Activate and license more cores when needed; Active cores may not be deactivated
3. OVM and Trusted Partitions
License software on Virtual CPUs within a VM; Ideal for special-purpose DB options
You can mix different combination of options for different DB on one Exadata.
OVM has no License cost; support is included with premier hardware support
Limitation:
At least 40% of usable cores on the machine must be licensed for Oracle software
Cannot use both OVM and CoD to license less than 40% of cores
A server must be virtualized or non-virtualized – not mixed
A RAC cluster can mix virtualized and non-virtualized servers
4. “Flash Drive” License Metric for EF Storage Server Software
$20K/drive; 8 flash drives/EF server vs 12 disk drives/HC server = 33% higher list
Can transfer licenses between Flash Drive (2 licenses/drive) and Disk Drive (1 license/drive) – part # is the same

Read data from MDM For Lookup and Flat table using MDM ABAP API

Hi,
I have requriment to read data from MDM from FLAT and Lookup table using MDM ABAP API. My design is like this ,
I have one ITEMS (Main table in MDM) and inside that i have one Lookup flat table ITEM_TYPE , my requriment is to read Item number and its related Item type.
From ABAP.
Please help if any body has any idea.
Regards,
Shyam

HI Guys,
I found my solution by myself. Below is the solution , hope this will help others:-
Retrieve data from MDM using MDM ABAP API.
Step- 1. Create structure in SAP with the same name as that of MDM field code for MDM Main table.
Step-2. Create another structure in SAP having all lookup fields of MDM , fieldname in ECC must be same as that of MDM field
code.
Step-3.Create structure in SAP for individual lookup field(Single Field only)   with the same name as MDM Field code.
Step-4.
DATA: IT_QUERY            TYPE STANDARD TABLE OF MDM_QUERY, "MDM_QUERY_TABLE,
      WA_QUERY            TYPE MDM_QUERY,
      WA_CDT_TEXT         TYPE MDM_CDT_TEXT,
      IT_RESULT_SET_KEY   TYPE MDM_SEARCH_RESULT_TABLE,
      WA_RESULT_SET_KEY   TYPE MDM_SEARCH_RESULT,
      WA_STRING           TYPE STRING.
DATA:<Internal table> TYPE STANDARD TABLE OF <SAP Str Having all LOOKup Fields>
DATA: :<Internal table>TYPE STANDARD TABLE OF <SAP Str one LOOKup field>,
     <Workarea> LIKE LINE OF :<Internal table>.
*PASS LOGICAL OBJECT NAME.
V_LOG_OBJECT_NAME = 'Logical object name defined in Customization'.
Define logon language, country & region for server
WA_LANGUAGE-LANGUAGE = 'eng'.
WA_LANGUAGE-COUNTRY = 'US'.
WA_LANGUAGE-REGION = 'USA'.
TRY.
    CREATE OBJECT LR_API
      EXPORTING
        IV_LOG_OBJECT_NAME = V_LOG_OBJECT_NAME.
ENDTRY.
CONNECT to repository. Apply particular logon language info
CALL METHOD LR_API->MO_ACCESSOR->CONNECT
EXPORTING
    IS_REPOSITORY_LANGUAGE = WA_LANGUAGE.
*NOW PASS ITEM NO AND GET KEY FROM MDM.
CLEAR WA_QUERY.
WA_QUERY-PARAMETER_CODE = <MDM FIELD CODE>. "Field code
WA_QUERY-OPERATOR        = 'EQ'. "Contains
WA_QUERY-DIMENSION_TYPE = 1. "Field search
WA_QUERY-CONSTRAINT_TYPE = 8. "Text search
WA_STRING                = <Field Value>.
GET REFERENCE OF WA_STRING INTO WA_QUERY-VALUE_LOW.
APPEND WA_QUERY TO IT_QUERY.
CLEAR WA_QUERY.
*PASS ITEM NUMBER AND GET RELATED KEY FROM MDM.
TRY.
    CALL METHOD LR_API->MO_CORE_SERVICE->QUERY
      EXPORTING
        IV_OBJECT_TYPE_CODE = <MDM Main Table>
        IT_QUERY            = IT_QUERY
      IMPORTING
        ET_RESULT_SET       = IT_RESULT_SET_KEY.
CATCH CX_MDM_COMMUNICATION_FAILURE .
CATCH CX_MDM_KERNEL .
CATCH CX_MDM_NOT_SUPPORTED .
CATCH CX_MDM_USAGE_ERROR .
CATCH CX_MDM_PROVIDER .
CATCH CX_MDM_SERVER_RC_CODE .
ENDTRY.
Pass record id into keys.
LOOP AT IT_RESULT_SET_KEY INTO WA_RESULT_SET_KEY.
WA_KEYS = WA_RESULT_SET_KEY-RECORD_IDS.
ENDLOOP.
WA_RESULT_SET_DEFINITION-FIELD_NAME = <Look field name>.
APPEND WA_RESULT_SET_DEFINITION TO IT_RESULT_SET_DEFINITION.
CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE
EXPORTING
    IV_OBJECT_TYPE_CODE      = <MDM Main Table>
    IT_RESULT_SET_DEFINITION = IT_RESULT_SET_DEFINITION
    IT_KEYS                  = WA_KEYS
IMPORTING
    ET_RESULT_SET            = IT_RESULT_SET.
LOOP AT IT_RESULT_SET INTO
        WA_RESULT_SET.
*PASS KEYS INTO MAIN TABLE TO GET Structure for FALT or Look up Table
TRY.
      CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
        EXPORTING
          IV_OBJECT_TYPE_CODE = <MDM Main Table>
          IT_KEYS             = WA_KEYS
        IMPORTING
          ET_DDIC_STRUCTURE =<SAP Strct having all Look up fileds of MDM>
ENDTRY.
LOOP AT <SAP Strct having all Look up fileds of MDM> INTO <Work area>.
    CLEAR WA_KEYS.
    APPEND <Work area>-field name TO WA_KEYS.
    CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
      EXPORTING
        IV_OBJECT_TYPE_CODE = <MDM Lookup table name>
        IT_KEYS             = WA_KEYS
      IMPORTING
        ET_DDIC_STRUCTURE   = <Single Structure in SAP For Lookup field>.
    READ TABLE <Single Structure in SAP For Lookup field>. INTO <Work Area> INDEX 1.
Here you can get the value of realted lookup fields associated with main table data.
ENDLOOP.
ENDLOOP.
LR_API->MO_ACCESSOR->DISCONNECT( ).
Edited by: Shyam Babu Sah on Nov 24, 2009 4:52 AM

KEY LOOKUP Operator using TCL

Hi,
I am trying to create a key lookup operator using tcl.
OMBALTER MAPPING 'TESTMAP' ADD KEY_LOOKUP OPERATOR 'INSTITUTION_CHARACTERISTIC_DIM'\
SET PROPERTIES (BOUND_NAME,CREATE_NO_MATCH_ROW, LOOKUP_CONDITION)VALUES
('INSTITUTION_CHARACTERISTIC_DIM','true','OUTGRP1.INSTITUTION_CHAR_SRCKEY
= INGRP1.INST_CHAR_SRCKEY')
and then adding an attribute to the INGRP
OMBALTER MAPPING 'TESTMAP'ADD ATTRIBUTE 'LAST_ACTIVITY_DATE' OF GROUP 'INGRP1' OF OPERATOR 'INSTITUTION_CHARACTERISTIC_DIM'
This is creating a key lookup operator by the name
INSTITUTION_CHARACTERISTIC_DIM, and i can see the Bound Name in the
properties window, but when i double click and open the key lookup, i
dont see the result table under the LOOK UP tab.Because of this, the
attributes dont get added in the OUTGRP of the key lookup.
Am i missing some important property of a key look up?
can some one please help me with this...
Thanks in advance...

Hi,
you have to bind the lookup operator to the table:
OMBALTER MAPPING 'MAP_LOOKUP' ADD KEY_LOOKUP OPERATOR 'MY_LOOKUP' BOUND TO TABLE '/MY_PROJECT/MY_DB/DIM_CUSTOMERS'
OMBALTER MAPPING 'MAP_LOOKUP' MODIFY OPERATOR 'MY_LOOKUP' SET PROPERTIES (CREATE_NO_MATCH_ROW, LOOKUP_CONDITION)VALUES ('true','OUTGRP1.ID_CUSTOMER=INGRP1.ID_CUSTOMER')
OMBALTER MAPPING 'MAP_LOOKUP' ADD ATTRIBUTE 'ID_CUSTOMER' OF GROUP 'INGRP1' OF OPERATOR 'MY_LOOKUP'Regards,
Carsten.

Benefits of using SAP CAR compared to SAP BW on HANA

Hi
I' like to understand the benefits of using SAP Customer Activity Repository. How is it better than SAP BW on HANA? What extra functions does the customer get?

Hi Waldemar (wow, I remember E.A.Poe...)
take a look to this document...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ad0a4b07-0301-0010-5095-ef7615676fc0
Hope it helps !
Bye,
Roberto

How to retrieve the data from MDM hierarchy table using MDM Java API

Hi,
I had a hierarchy table in MDM. This table had some column say x. I want to retrieve the values of this x column and need to show them in a drop down using MDM Java API.
Can anyone help me to solve this?
Regards
Vallabhaneni

Hi,
Here is your code...
TableId Hier_TId = repository_schema.getTableId(<hierarchy table id>);
java.util.List list = new ArrayList();
ResultDefinition Supporting_result_dfn = null;
FieldProperties[] Hier_Field_props =rep_schema.getTableSchema(Hier_TId).getFields();
LookupFieldProperties lookup_field = null;
TableSchema lookupTableSchema = null;
FieldId[] lookupFieldIDs = null;
for (int i = 0, j = Hier_Field_props.length; i < j; i++) {
if (Hier_Field_props<i>.isLookup()) {
                              lookup_field = (LookupFieldProperties) Hier_Field_props<i>;
     lookupTableSchema =repository_schema.getTableSchema(lookup_field.getLookupTableId());
                              lookupFieldIDs = lookupTableSchema.getFieldIds();
     Supporting_result_dfn = new ResultDefinition(lookup_field.getLookupTableId());
     Supporting_result_dfn.setSelectFields(lookupFieldIDs);
     list.add(Supporting_result_dfn);
com.sap.mdm.search.Search hier_search =new com.sap.mdm.search.Search(Hier_TId);
ResultDefinition Hier_Resultdfn =     new ResultDefinition(Hier_TId);
Hier_Resultdfn.setSelectFields(rep_schema.getTableSchema(Hier_TId).getDisplayFieldIds());
ResultDefinition[] supportingResultDefinitions =
(ResultDefinition[])list.toArray(new ResultDefinition [ list.size() ]);
RetrieveLimitedHierTreeCommand retrieve_Hier_tree_cmd =
new RetrieveLimitedHierTreeCommand(conn_acc);
retrieve_Hier_tree_cmd.setResultDefinition(Hier_Resultdfn);
retrieve_Hier_tree_cmd.setSession(Auth_User_session_cmd.getSession());
retrieve_Hier_tree_cmd.setSearch(hier_search);
retrieve_Hier_tree_cmd.setSupportingResultDefinitions(supportingResultDefinitions);
try {
     retrieve_Hier_tree_cmd.execute();
} catch (CommandException e5) {
          // TODO Auto-generated catch block
          e5.printStackTrace();
HierNode Hier_Node = retrieve_Hier_tree_cmd.getTree();
print(Hier_Node,1);
//method print()
static private void print(HierNode node, int level) {
if (!node.isRoot()) {
     for (int i = 0, j = level; i < j; i++) {
          System.out.print("\t");
     System.out.println(node.getDisplayValue());
HierNode[] children = node.getChildren();
if (children != null) {
          level++;
for (int i = 0, j = children.length; i < j; i++) {
print(children<i>, level);
//end method print()
Best regards,
Arun prabhu S
Edited by: Arun Prabhu Sivakumar on Jul 7, 2008 12:19 PM

Key code 24 using control down - no longer works in 10.6

I have a script that should open a dialog box to make a picture using Copernicus. the command I try to invoke is 'Control ='.
here is the script.
tell application "Copernicus"
activate
delay 2
tell application "System Events"
key code 24 using control down
end tell
end tell
or alternative I tried:
tell application "Copernicus"
activate
delay 2
tell application "System Events" to keystroke "=" using control down
delay 5
end tell
However both do not work, it does do nothing on - key code 24 using control down -.
If I do a manual 'Control =' it works regardless if the Application is active or in the background.
Has anything changed in 10.6 that this sort of code no longer works? How do I set it up for this to work?
Message was edited by: ChangeAgent

Pierre L. wrote:
I have downloaded Copernicus 1.5.2 (Build 15) just to better understand the issue.
is what I use.
However, I am unable to find any “Control =” keyboard shortcut in any menu of that application. Does that shortcut belong to Copernicus, or is it a shortcut that you have added yourself in the Keyboard pane of the System Preferences?
I added it replacing 'F7' for various reasons. however “Control =” works if I do it via the keyboard.
As for me, after assigning a “Control =” keyboard shortcut to a TextEdit menu command, I have no problem invoking it from the following script.
*tell application "TextEdit" to activate*
*tell application "System Events"*
*key code 24 using control down*
*end tell*
OK. as said it works using the keyboard, but not via the script. could it have something to do with Copernicus? I simply do not understand as to why it does not work using a script.

Retrieving hierarchy fields from MDM to SAP R/3 using MDM ABAP API's

Hi all,
I have developed a code to retrieve fields from MDM to SAP R/3 using MDM ABAP API's, i could retrieve all of the fields excluding the Lookup[Hierarchy] fields like- FACILITY CODE etc...
please update me if anyone has any experience on this.
Thanks and regards,
Aastha Mehrotra

Hi ,
Any one worked in the MDM API to retrieve Hierarchy fields ???
Regards,
Arun.

Attachments using MDM java API

Hi
How to store attachments in MDM repository using MDM java API.
Could you please suggest us.
Thanks
Sowmya

Hi Sowmya,
You can store attachments using MDM Java API. You can use the following piece of code.
BinaryBlobRecord record2 = RecordFactory.createEmptyBinaryObjectRecord(tableID);
//Attachment to be saved
String filePath = wdContext.currentContextElement().getVa_Resource().getUrl(0);
IWDResource resource = wdContext.currentContextElement().getVa_Resource();
FileInputStream stream = (FileInputStream)resource.read(true);
int length = 0;
while(stream.read() != -1)
     length++;
byte[] b = new byte[(int) length];
stream.read(b);
stream.close();
record.setName(new StringValue("filename"));
record.setOriginalName(new StringValue("filename"));
record.setHasOriginal(new BooleanValue(true);
RetrieveGroupTreeCommand groupTreeCommand = new    RetrieveGroupTreeCommand(wdContext.currentContextElement().getVa_ConnectionStr());
groupTreeCommand.setSession(wdContext.currentContextElement().getVa_SessionID());
groupTreeCommand.setGroupType(GroupTypes.DATA_GROUP_TYPE);
groupTreeCommand.execute();
//Set data location and data group ID
record.setDataLocationId(new GroupNodeId("GN2"));
record.setDataGroupId(new GroupNodeId("GN2"));
record.setBinary(new BinaryValue(b));
CreateRecordCommand createRecComm =
                         new CreateRecordCommand(wdContext.currentContextElement().getVa_ConnectionStr());
createRecComm.setSession(wdContext.currentContextElement().getVa_SessionID());
createRecComm.setRecord(record);
createRecComm.execute();
//Link this record to the main table record
Record QRec = RecordFactory.createEmptyRecord(mainTable);
//Setting the above created record in main table record object
QRec.setFieldValue(attachmentField, new LookupValue(record.getId()));
CreateRecordCommand createRecComm =
                    new CreateRecordCommand(wdContext.currentContextElement().getVa_ConnectionStr());
createRecComm.setSession(wdContext.currentContextElement().getVa_SessionID());
createRecComm.setRecord(QRec);
createRecComm.execute();
Now the main table record is created with an attachment.
Hope this helps you.
Regards,
Sruti

How to use MVC using MDM as backend... in Webdynpro for java

Hi,
How to use MVC using MDM as backend.. when we r using R/3 we used to create RFC model. I dont know how to use it here..
Regards,
laxmi.

Haii
Create a data a source using ur ODBC tool. This can be found in Administrative tools of windows.
In ur connectino class u can write the following code
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con=DriverManager.getConnection("jdbc.odbc.dsnname u have given when u created data source","user namet","pwd");( I think there is no need to give username when u connect to ur access)
The connection "con" is ready to use.. Put these statements inside a try catch...
I think i have explained enough..
regards
SHanu

I have an MacBook Air, which keys do i use to connect it to a projector

Which keys do I use to connect my MacBook to a projector

When you physically connect the mac to a projector (which is turned on), it should automatically detect the projector and configure itself. This can take a second or two.
System Preferences, Displays will provide you with a few options on how the external display will behave (e.g., mirrored).
In the Display preferences if you press the option key a button "Detect displays" will appear which will allow you to manually force the computer to connect to a display.

Key benefits of using MDM

Similar Messages

Maybe you are looking for