MDM qualified range - concern

Hello Experts,
I am using qualified range to generate customer number based on the account group.
But its not allowing me to syndicate the alphanumeric values since it expects
numbers only. If I enter the remote system & key mapping details in the record while
creation the alphanumeric record then syndication goes fine. But it doesn't allows
to key the remote system details all alone for the internal number range as its
using a qualified range.
Any way to resolve this issue?
Thanks in advance,
Elizabeth.

Hi Elizabeth,
This is true that it uses only Numeric values while defining Qualified Range using Remote System of MDM Console.
But it doesn't allows to key the remote system details all alone for the internal number range as its using a qualified range.
I didn't get you exactly here, if you mean that you want to syndicate records on the basis of account number and want to generate customer number which is numeric then its possible. For this the Qualified field which is look-up to some sub-table, for this sub-table Key mapping Property should also be Yes.
Please refer step by step guide to make use of qualified range:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807ce1ba-94c0-2a10-a398-afdfd8135ebd?quicklink=index&overridelayout=true
Kindly let me know if you are looking for something else
Regards,
Mandeep Saini

Similar Messages

QUALIFIED RANGE MAPPING/PI-MDM CONFIGURATION FOR AUTOMATIC SYNDICATION

Hi Experts,
I am setting up automatic import and syndication using an xml schema to a qualified lookup, will this be able to work? I made tuple to work but not with a qualified lookup even the mappings are all corrent, the import doesnt work.
We are using the MDM-PI Adapter instead of the File Adapter to automatically syndicate, Is it possible to create multiple channel? As when we configure the message starts to branch to the other channel since they have existing mapping but different remote port. Other port was configured as Manual while the new one was automatically to syndicate? Is there a workaround to this?
Many thanks!

Hi Elizabeth,
This is true that it uses only Numeric values while defining Qualified Range using Remote System of MDM Console.
But it doesn't allows to key the remote system details all alone for the internal number range as its using a qualified range.
I didn't get you exactly here, if you mean that you want to syndicate records on the basis of account number and want to generate customer number which is numeric then its possible. For this the Qualified field which is look-up to some sub-table, for this sub-table Key mapping Property should also be Yes.
Please refer step by step guide to make use of qualified range:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807ce1ba-94c0-2a10-a398-afdfd8135ebd?quicklink=index&overridelayout=true
Kindly let me know if you are looking for something else
Regards,
Mandeep Saini

Qualified Range is not Working

Hi,
I am having issue with Number Range getting crated for my Customer Number.Steps what I took to Acheive .
In Console :
For Remote System R/3
Key Genration : Qualified Range
Lookup Fields : Account Group.
Even For Account Group table has Key Mapping set to "Yes"
Then in the syndication Remote Key Value is mapped to Customer Number .When I syndicate the Records customer number not getting created and also when I check the Edit Kay Mapping,doesn't show anything for the Record.
Please help us onthis ,do I miss something here.
Thanks,
Manju

Hi,
after completing MDM Console setting for qualified number range
kindly Note following points:
1. make sure main table(for e.g. Product) and account group table key mapping should enable
2. import main records with specific remote system
3. open syndication map, and map value field under remote to destination side
4. in syndication map properties tab select remote system under Remote Key Override
5. Dstination preview tab will display customer number based upon qualified number range
Thanks,
Jignesh Patel

Read "Qualified Range Key Generation" with Java API.

Hi guru,
I use MDM 5.5 SP6.
In MDM Console I read Qualified Range Key Generation it in "ADMIN -> Remote Systems -> Qualified Range".
I have to get "Qualified Range Key Generation" with Java API.
It's possible?

Hi Rocco,
I am also thinking of same scenario.I thought it is possible in Java Apis by calling the webservices for MDM.there is a service of "get key mapping" where we can pass this "Qualified key range" as parameter.In MDM we have to define a look up table for that key ranges .We will access that table through JAVA API and then link it with the key mapping service .
If u find any solution to apply this ,please share.
thanks and regards
Ank

Assign records to different remote systems in MDM

Hello Experts,
I am using qualified range to generate internal number range for vendor. The remote key & remote system details for the records are generated during syndication. My scenario is that I have couple of records in MDM for different remote systems. I want to syndicate it to the respective systems. Is there a way to identify the respective records per system with out inserting the details in "edit key mapping".
If we try specifying Remote system details in edit key mappings with a blank or specific Key value , then the qulaified number generated for vendors is overwritten with this key value mentioned in key mapping.
I need to retain both the qualified range functionality as well as tag the records to different remote systems.
Kindly advice.
Thanks and Regards,
Elizabeth.

Hi Shiv
So, i am not sure, but this all makes me feel that syndication tasks can not be executed parallel.
Your understanding here is correct since we are using here the same table for syndication process so it will be executed in steps. I mean syndication 2 has to wait until the syndication 1 ends. But the thing is that even after syndication 1 completes syndication 2 is not going to place that's the issue here.
Please find solution which tells same thing in MDM import manager context.
Can I run two Import Managers at the same time?
Yes, several instances of the Import Manager can be open concurrently. The only existing limitation though is when actual importing process starts the tables involved in the importing process are locked for write access. So if two instances of the Import Manager import to different tables then no synchronization issue occurs. If they use the same table, then the instance getting access second has to wait until the first ends.
For more details, Please refer this below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7dc6ba86-0501-0010-0b82-849437929f0d?quicklink=index&overridelayout=true
@ Elizabeth: After Syndication 1, Have you checked after sometime whether syndication2 & so-on takes place or not. I feel that Syndication for syndication 2 , syndication 3 & syndication 4 should also occur after some time as they executed one by one not parallel so will take some time. Just check and revert with result whether your workflow gets completed after some time or not.
Note: Make sure that for all these Syndications outbound ports Processing Type = Manual in Console else syndication will not occur.
Regards,
Mandeep Saini

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

Unique key for Qualified tables

Hello Experts,
We are currently facing an issue with qualified tables. We need to retain existing system keys as below:
Item (Main table)
Item_Id, Item_Number
Item_Price (Qualified Table)
Item_Price_Id, Item_Id, Price_Type_Id, Price
E.g.
1, Pencil
2, Pen
3, Notepad
1, 1, Retail_Price, $10
2, 1, Wholesale_Price, $5
3, 2, Retail_Price, $15
4, 2, Wholesale_Price, $10
We need to migrate the existing ids (Item_Price_Id) in MDM qualified table and need to maintain the same as max(Item_Price_Id) + 1 for all future records.
Is there a way we can achieve this?
Your help is greatly appreciated.
Thanks in advance,
Vinay

Hi Karol,
The Interface Iprinciple has this function as it:
Gets the unique identifier which unambiguously identifies the object's principal type and principal's data record(s) in the data store (e.g. a relational database).
Note: the unique ID is a case sensitive string
Use this identifier to keep and persist references to principals. As this identifier contains internal information and is usually not readable, it should not be displayed in user interfaces.
UME implementation guarantees to return Strings which are not longer than 255 characters.
Returns:
a non-null String identifying this principal
I hope this helps you.
Regards
Pravesh

When will MDM be put on WebAS?

We are considering implementing MDM, but are concerned that MDM -- being the backbone to the NetWeaver stack -- is not "Powered by NetWeaver" (meaning that it doesn't run on WebAS and integrates with other NW components).
Are there any plans to port MDM over to WebAS? If so, when?
Thanks!

Hi Kevin,
I did not find any reference to this(WebAS) in the recent MDM Roadmap (2005-2008) webinar.
But, SP2 already have iViews and SP3 will have maintenence iViews. You always have Java & COM APIs to integrate with other applications.
MDM will be much more aligned with BI with Global Spend enablement in MDM - release due in Q3'06.
BPM will be enabled from MDM - release due in Q3'06.
Full ESA support is available from MDM 2008 release.
For additional information, please check the webinar that was held on Oct 7th.
Regards,
Rajani Kumar

Number Generation & Remote Key Updation

Hi Experts,
We have a scenario of integrating MDM with SAP and 3 Non SAP systems
All the systems have the same number range for the account types
Whenever there is a request , a copy should always go to SAP plus the requested system
Doubt:
The request comes to the import server and the requirement is to automate it
Now the question is how to generate the number in main table and it should update the key mapping of 2 remote systems automatically
Kindly help
Regards,
Antony

Hi Antony,
As you have 4 remote systems, one SAP and 3 non-sap systems, you need to create 4 remote systems in MDM Console ( as shown in page 3/10, 1.2 Create/modify the remote system u201CSAP R/3u201D and specify type as u201Cinbound/Outboundu201D and key generation as u201CQualified Rangeu201D in below article).
While syndicating you have to select remote system one by one as it is shown here for SAP R/3 (on page 5/10, 2.5 Specify the type as u201CFlatu201D and remote system same as created in step 1.2 : u201CSAP R/3u201D ), you need to do it for all the 4 remote systems one by one. you need to be carefully map remote key for all of these remote systems as shown in section, 4.2 The u201CSAP Material Numberu201D field, which is to be generated during syndication, is to be mapped to the remote key field u201CValueu201D.
For complete understanding, Please refer the below Article.
[Using qualified ranges to generate SAP numbers|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807ce1ba-94c0-2a10-a398-afdfd8135ebd?quicklink=index&overridelayout=true]
Regards,
Mandeep Saini

Key Generation in console

Hi Folks,
I have defined key generation in console .I need some information in key generation such as ,if i define None ,range and Qualifed Range.
Where it effect and what are significance of it.
Secondaly., We create clone in Import manager and then we do mapping to remote key to the clone of the main table. I am looking for the business significance and techanical signifiance of it.
Thanks in advance,
Rohit

Hi Rohit,
If you choose
NONE: - Then remote key will not be generated automatically and has to be applied explicitly either using import manager or in data manager.
RANGE: - Here we can specify a range using TO and FROM. This generates the key automatically for that client between that range.
Qualified range: - Here we specify a range for a qualified table for key generation.
Keys are generated on a per value basis i.e. MDM automatically generates keys for the specified single-valued lookup field based on values you specify
using the Range property. You can specify Qualified Range values by selecting the
single-valued lookup field from the drop-down list and specifying From
and To values for each lookup table value.
Let me know if this helped your cause.
BR,
Siddharth

Key Generation, doesnt work

Hi, every body
I want to generate new Material Number automatically for new Materials
I have done the following steps
- I have set Key Mapping to YES in Products main table
- In the remote systems I added a new remote system called SAP_ECC
- In this remote system I set the Key Generation to Qualified Range and set the Look Field to Material Type, also fill the Qualified Range to something like this
[NULL] 9990000001 to 9999999999
ZHOR   9010000001 to 9019999999
ZVER   9020000001 to 9029999999
ZHIB    9030000001 to 9039999999
- In the syndicator I configured a port called TO_ECC to work with SAP_ECC remote system
- Mapped the [Remote Key]/[Value] to MATNR field in iDOC MATMAS05
In the Preview pane I only see Material Numbers (MATNR) which I have manually edited    its mapping value. Material Numbers are empty for new Materials.
Please tell me. What I'm missing?

Hi Rafael
In my experience with Key Generation, the keys are only created for the remote system once a Syndication job has actually processed the record. I'd guess that this is so in order to minimise the amount of work done by the MDM Server and to avoid "wasting" keys.
To see that it does work : execute the Syndication job then refresh the Record view (press F5) in the Syndicator. The Destination Preview tab should now contain the newly generated key.
HTH,
Mark

Steps in Key mapping

Hi all,
i have gone through many forum's regarding key mapping.
i can see that the following are used..
--> remote systems
--> key mapping option in table-field properties
--> key mapping option in table properties.
-->key generation(none, range, qualified range) field in remote system properties.
But never understood like in which order we need to define all the above, what is the relation b/w them.
i have gone through some theory in sdn regarding key mapping but unable to get the logic..
can any one one show me with 2 records in 2 tables so, that i can clear my confusion.
Thanks in advance.
Regards
phani

Hi Phani,
first you should understand the basic idea of key mapping. MDM usually wants to consolidate master (objects like vendors, customers, and so on) and/or reference (lookup tables like countries, regions, and so on) data. The idea is to load this data from various remote systems into MDM, compare and match the data, and in some cases merge multiple records into a single one. Let's take an example.
Image you have attache two remote systems to MDM. The first is an ERP system, the second a CRM system. Both system contains countries as reference data. In ERP, your country India looks like
Name = India
Code = INDIA
whereas in CRM it looks like
Name = India
Code = IND
It is obvious that the country is the same, but the systems use a different internal code. Now you load this data into MDM. What do you do? Do you want to create two records having different codes? Or do you want to "merge" the indentical records into a single one. The common decision in MDM is the second one.
But what happens now if you send customers from ERP and CRM to MDM? Usually the Customer message contains the Country CODE but not the Country NAME. From ERP the message could look like:
Customer = Mr. X
Country = INDIA
whereas from CRM the message could look like
Customer = Mr. X
Country = IND
Surely you want to map the different code in both case to the same country "India". That's why you use key mapping in MDM. Key Mapping allows MDM to store different codes for the same data. So in MDM you store just one record, but if you receive and/or send data from and/or to remote systems, you can always ensure that you store and/or send the correct codes.
Hope that clarifies your doubts about key mapping in general?
OK, now regarding your question about "Update NULL fields only":
In Import Manager you have several options for data import. If you import for the very first time (for RS1), your table in MDM is usually empty. That why you need to "Create" the records. If you import the second time (for RS2), your table in MDM already contains data. Depending on the matching field for import, several options are now possible. If Import Manager is not able to match the record you want to import against any other existing in the repository, you have to "Create" the new record. If Import Manager is able to match the record that you want to import with a record of your repository table, you can choose what happens next. "Update NULL fields only" compares the record you want to import with the existing values in MDM. In your case, following info is already part in MDM:
Country = India
Code = INDIA
Remote Key RS1 = INDIA
Remote Key RS2 = NULL
Now the file you want to import contains the following values:
Remote System = RS2
Country = India
Code = IND
Import Manager identifies that only "Remote Key RS2" is NULL. All other fields already have values. As you choose to "Update NULL Fields only", only Remote Key RS2 gets a new value. If you choose a different option, e.g. "Update All Mapped Fields" Import Manager would update the Country and Code fields, too.
Best regards
Michael

Import Manager 'Error 5611520 - Error Saving Key Mapping'

I am using CREDITOR_EXTRACT in R/3 to send Vendor IDoc to XI and use CREMDM04 type. XI generates an XML file that I load into MDM using a client that is set up for Inbound/Outbound. The key mappings have been turned on for the Vendor repository.
In IM, I use the standard map CREMDM04 and the system maps the incoming XML file to the vendor main table. There are few values that I have to map manually - fine. Next, when I click Import, I get a error pop-up message 'Error Saving Key Mapping - Errno 5611520'.
Has anybody experienced this when using all standard content (schemas and maps) for Vendor?
Thanks in advance.

Subbu,
Found another system that has the same versions as you do. This particular error did not appear, but we got some internal IM error. Also, the SAP training demos are on the same versions as mine.
I am using MDC R/3 as the client and the CREMDM04 schema map. Not using MDM inbound ports for now. Just loading XML file generated by XI based on CREMDM04. Do you think that I need to define a Qualified Range for this client in the Console or can it be left blank?
Thanks.

Unable to use *Keygeneration* property

Hi All,
I am trying to use Keygeneration property under remote system.
Selected Keygeneration as QualifiedRange. and selected lookup field (Say
Department Number) but i am not able to see any lookup values in the qualified
range property.
Finally i am not able to give keygeneration values for lookup values.
Can anyone tell me the solution for above problem?
Cheers
Narendra

Hi,
I am trying to use Keygeneration property under remote system.
Apart for this you have to set KeyMapping = Yes for that Qualified table for which you set Property Keygeneration under Remote System by going into MDM Console.
Suppose you have two records into Data Manager which also lookup( associated to) this qualified table.
Syndicate these records after syndicating your Qualified range for these two records Visible when you right click on these two records in Edit Key Mapping
Hope it will Help you,
Rewards if found Useful....
Mandeep Saini

Syndicator Issue

Hi
I am following the this pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90e42521-0645-2b10-d1b2-e9f6fab39856
MDM console , data manager, import manager were successful.
But syndicating I was trying to select Destination Items by File-->Destination Properties->
2 ways I have tried:
1. I tried with Type: XML Schema File
   Remote System: MDM
   XML file name: *.xsd ( I have exported repository schema and Using xomLite i have converted it as .xsd )
   Root: By defaultI got the root (Product Msg)
when I click on ok my Destination Items were shown like this
http://www.flickr.com/photos/28108043@N08/2756752244/
but as per the PDF, Pls refer page 17
2. I tried with Type: Port
Remote system: MDM
Port: Nothing appears in the Drop Down List
How should I do to get the proper Destination Items as shown in the PDF page 17 ?
correct me if my steps are worng
In console , Admin Node
In Remote Systems:
I have to create one Remote system,
Type: Inbound/Outbound
Key generation: None or Range or qualified Range (which one I have to select)
Incase Key generation is Qualified Range , which lookup field I have to gve ?
From: 0
To:100
Port:
One Port
Type: Outbound or Inbound
Remote System: i have to give the one which i have created above
Map: I tried but no value is appearing here
Processing Type: Automatic
Processing Interval: Continous
How should I do to get the proper Destination Items as shown in the PDF page 17 ?
Thanks
Manian

Hi Manian,
How should I do to get the proper Destination Items as shown in the PDF page 17 ?
Either you can export the file in .CSV format or in XML file.
The page you are refering in the pdf is exporting .CSV file.
For that, you go to the Destination items.
Create fields which you want to export by right clicking in Destination Items manually.
You will get the fields after creating it maunally.
Then in Item mapping map the field to the source side.
Then in Item Mapping, in the source side, as mentioned in the PDF, select the respective multilingual field and right click on it. Select SPlit Multilingual Field.
You will be able to proceed.
For your other queries:
correct me if my steps are worng
In console , Admin Node
In Remote Systems:
I have to create one Remote system,
Type: Inbound/Outbound
Key generation: None or Range or qualified Range (which one I have to select)
Incase Key generation is Qualified Range , which lookup field I have to gve ?
From: 0
To:100
Port:
One Port
Type: Outbound or Inbound
Remote System: i have to give the one which i have created above
Map: I tried but no value is appearing here
Processing Type: Automatic
Processing Interval: Continous
1 Yes, you will have to create 1 remote system if you have to syndicate the records back to the system.
2) You will hvae to create a port of type - OUTBOUND. Since you are exporting the file from MDM.
3) All the other settings like Map, Processing type, Processing Interval are required only if you want to ecport the records automatically, which I feel you dont require now.
For further steps, please follow the Pdf.
Hope it helps.
Thanks and Regards
Nitin Jain

MDM qualified range - concern

Similar Messages

Maybe you are looking for