Importing Key Combinations of a Lookup table.

Hi, I have created a lookup table which is equivalent to a check table in R3. For example table named, SPT (Special Procurement Type), Which has a key combination (Composite Keys) in R3 itself and the keys are Plant + Procurement Type and so in MDM Look table both keys are defined as display fields. The problem comes in automating the import. In IM source, both key fields are separate fields, I tried combining the field using Partion, but Automap is not working and so the import automation process. Any thoughts/advices on tackling this issue is appreciated.
Thanks
Job.

Hi Job,
IF u combine the fields in partition and then if try to do value mapping automatically,then it is not possible .There u have to map manualy .Automap in value mapping can be done only when values are not combination but single.
Like
Source----
Destination
abc----
<null>
def----
abc
xyz----
def
xyz
But if it is like:
Source----
Destination
abc,12----
<null>
def,23 -
abc,12
def,23
in above case it is a combination so not possible.
I hope u im able to make u understand.
If this has helped u then do Reward points.
Regards,
Neethu Joy
Edited by: Neethu joy on Dec 31, 2007 3:17 PM
Edited by: Neethu joy on Dec 31, 2007 3:19 PM
Edited by: Neethu joy on Dec 31, 2007 3:24 PM

Similar Messages

How to add a feild as key combination for existing condition table

Hi all,
please any body can inform me about how to add a feild as key combination for existing condition table ex 901 having the key combination of sales organisation and material
for this cond. table,how to add a new feild ex:price list
iam unable to add it in change mode of v/03.(even after removing this 901 table from Acc.seq.)
Edited by: rajendraprasad vasam on Apr 25, 2008 10:08 AM

mr.Rajendra
I you have the access key - you can copy the 901 table and create a new table along with your required field. v/03
Or
in the access sequence for the condition type - add 1 more step and add your field.
ie 10 - 901
and in 20 - your required field
regards,
Reshmi
Edited by: reshmi bhaskar on Apr 25, 2008 10:21 AM

Syndicating Key mapping value from lookup table

Hi Experts,
I want to Syndicating Remote Key value from lookup table as per the remote system.
In syndicator, if I map destination field to the remote key of the lookup table, I am getting blank value.

Hi Mrinmoy,
kindly check in the Data Manger whether have you maintained Remote keys for the lookup table. If yes then choose the specified remote system from Remote key override fields under Map properties in the syndicator.
Incase you cant find the remote system in the "remote key override" field for which remote key is assigned in Data manager, then you need to check the Type (outbound) of the remote system in Console admin node. Because only those Remote systems type set as Outbound can been found in Remote key Override in the syndicator.
After choosing the remote key you need to map the destination field with Remote key value as shown in the below image.
Regards
Rahul

Isn't there remote key concept for Hierarchy lookup Tables?

I don't see the [remote key] field in destination items.?
I really don't intend to use this remote Key concept in syndicating back to the source system, but specifically to satisfy this operation need:
I have a hierarchy table with two fields and both of them need to be display fields, Code & Name for Business reasons.
So when loading in the hierarchy field at main table level, I don't have to go through this compounding effort and just map the remote key which is just the code and not the name?
-Sudhir

Yes, remote key is available for Hierarchy Table as well. Set remote key ON on hierarchy table.
As per your Business requirement, you can create clone of code field and then map code to remote key and clone to Code field while initilizing hierarchy table in repository. Then while importing Main table data, if you are getting code in the source file, you need not to map code with the name of the hierarchy. if the code exists as remote key then Import Manager will automatically map code with the Hierarchy class name..
Try this and am sure it will work and solve your problem.
Regards,
Shiv

Key Mapping for Flat lookup tables

Hi,
How do we decide if we need to make Key Mapping "Yes" for flat look-up tables?
Can anyone plz explain with an eg on where to make key mapping yes or no for Flat Tables.
Thanks,
Ketan

Hi,
Can anyone plz explain with an eg on where to make key mapping yes or no for Flat Tables.
1. A remote systems objects are mapped to master data objects within MDM using key mapping. A key mapping maintains the relationship between the remote systems identifier (or key) for an object and the corresponding master data object in MDM.
2. in the data manger based upon some strategy, you found that 4 records are duplicate, and then you merged into single record.
the merged record is having 4 records inside it with respective remote keys.
if you want to edit those records, key mapping should be enabled for that particular table.
3. while harmonizing the records to the respective client systems, you can use edit key mapping functionality for merged records.
if you enabled key mapping functionality in the console for the particular table, then only you can aceess EDIT KEY MAPPINGS functionality in data manager & syndicator.
hope this may help you,
Regards,
Srinivas

Create key mapping using import manager for lookup table FROM EXCEL file

hello,
i would like create key mapping while importing the values via excel file.
the source file containing the key, but how do i map it to the lookup table?
the properties of the table has enable the creation of mapping key. but during the mapping in import manager, i cant find any way to map the key mapping..
eg
lookup table contains:
Material Group
Code
excel file contain
MatGroup1 Code System
Thanks!
Shanti

Hi Shanti,
Assuming you have already defined below listed points
1) Key Mapping "Yes" to your lookup table in MDM Console
2) Created a New Remote System in MDM console
3) proper rights for your account for updating the remote key values in to data manager through import manager.
Your sample file can have Material Group and Code alone which can be exported from Data Manager by File-> Export To -> Excel, if you have data already in Data Manager.
Open your sample file through Import Manager by selecting the remote system for which you want to import the Key mapping.
(Do Not select MDM as Remote System, which do not allows you to maintain key mapping values) and also the file type as Excel
Now select your Soruce and Destination tables, under the destination fields you will be seeing a new field called [Remote Key]
Map you source and destination fields correspondingly and Clone your source field code by right clicking on code in the source hierarchy and map it to Remote Key if you want the code to be in the remote key values.
And in the matching criteria select destination field code as a Matching field and change the default import action to Update NULL fields or UPDATED MAPPED FIELDS as required,
After sucessfull import you can check the Remote Key values in Data Manager.
Hope this helps
Thanks
Sowseel

Remote key for lookup tables

Hi,
I need some advice on remote keys for lookup tables.
We have loaded lookup data from several client system into the MDM repository. Each of the client system can have diffferences in the lookup values. What we need to do is to enable the keymappings so that the syndicator would know which value belongs to which system.
The tricky part is. We haven't managed to send out the values based on the remote keys. We do not want to send the lookup tables themselves but the actually main table records. All lookup data should be checked at the point of the syndication and only the used lookup values that orginally came from one system should be send to that particular system. Otherwise they should be tag should be blank.
Is this the right approach to handle this demand or is there a different way to take care of this? What would be the right settings in the syndicator?
Help will be rewarded.
Thank you very much
best regards
Nicolas

Hi Andreas,
that is correct. Let's take two examples:
1) regions
2) Sales Area data (qualified lookup data)
Both tables are filled and loaded directly from the R/3s. So you would already know which value belongs to which system.
The problem that I have is that we will not map the remote key from the main table because it will be blank for new created master data (Centralization scenario). Therefore we cannot map the remote key from the attached lookup tables, can we?
The remote key will only work for lookup tables if the remote key of the actual master data is mapped. Since we don't have the remote key (local customer ID form R/3) in MDM and since we do not create it at the point of the syndication... how would the SAP standard scenario would look like for that?
This is nothing extraordinary it's just a standard centralization scneario.
Please advice.
Thanks alot
best regards
Nicolas

Tab key and lookup table

Hi,
How to use the 'Tab' key to open a lookup table, E.g. BP Code, Name?
Alternatively, how to use the 'Tab' key to call a formatted search? I hope to follow the standard in SBO and do away the Shift-F2.
I am using VB and 2004B. Your input will be appreciated.

I think you can mimic every user action with UIAPI.
Therefore, e.g. in Sales Order Form you activate the BPCode item (.Click) and hit Tab (.SendKeys(vbTab)).
You could also try clicking the the iconitem ("67") next to BPCode.
If you want to assign a Choose From List (CFL) to an item of your choice using UIAPI then you should wait for 2005.
Shift-F2 is standard in SBO UI for launching FSs, why would you like to disable it?
If you want to enable tabbing to kick-off an existing FS, then you should capture the tabbing event (et_KEY_DOWN) in your item and then use SendKeys for sending Shift-F2 to keyboard.
HTH
Juha

How to import a lookup table

Hi all,
I am trying to import a simple XML file using import manager with the following information:
- NAME: STRING
- LAST NAME: STRING
- CITY: STRING
I have in my repository the next information:
- NAME: TEXT.
- LAST NAME: TEXT.
- CITY: LOOKUP TABLE (CITY TABLE)
CITY TABLE is a lookup table with just a fiel called 'NAME:TEXT'.
With import manager I select the XML field CITY:STRING and I clone it. After that, I select the lookup table called TABLE CITY and I make the following map:
- Remote key (Repository) maps with City clone (XML file)
- name (Repository) maps with city (XML file).
Finally, I select the Products table from the repository and I make a new map between CITY:LOOKUP TABLE (from the repository) and city (from the XML File).
The import status fails. What is wrong?
Thanks in advance,
Marta

Hi Marta,
you have to import the lookup table before importing the main table data using an extra import map.
But if I understand your description correctly, you only have one field in your city repository, which is the display field. This way, you can also load into the city lookup table using only the main table import.
When you select 'city' in the field mapping (destination table is the main table), you will see the distinct values in the value mapping area below.
In the destination pane of the value mapping, there shouldn't be any values for the initial import. So you have to select all your source values and 'ADD' them to your repository.
If this still doesn't work, try the two maps aproach and import the cities prior to the main table records, then you can automap them later with the main table import.
Please tell me if this still doesn't work.
Regards,
Christiane

Change the font color of a text field in a table by key-combination

I want to change the font color of a text field in a table (single cell only) on pressing a key combination. Does anybody know how to do this.
I have a lot of data in a table. During an evaluation of the data in a meeting I want to change the color of the text depending on the result of the meeting. (for example: High risk = CTRL+R makes the text red).
I know how to change the color using a button, but I do not want to add a button after each cell. For this reason I would like to do it on a key combination that alway refers to the active cell.
Many thanks for your help in advance.
Marcel

Hi,
I don't think you can use the ctrl key like that as those shortcuts will be intercepted by Reader (ctrl-R toggles the ruler display on / off). You also might have trouble updating the color while you still have focus on it. You can use the shift key in a similar way, so if you only have lower case characters in the text fields then you can do something like;
if (xfa.event.shift)
    switch (xfa.event.change)
        case "R":
            this.fontColor = "255,0,0";
            break;
        case "O":
            this.fontColor = "255,102,0";
            break;
        case "G":
            this.fontColor = "0,255,0";
            break;
    xfa.event.change = ""; // ignore character
If you need uppercase characters maybe you can have one button to set "review mode" and test that on the if (xfa.event.shift) line. But again it wont take effect until you have tabbed out of the field.
Regards
Bruce

Creation of Condition table & assigning in Key Combination(FV11)

Dear all,
I have created a new Condition table(M/03) for Plant/Vendor Code/Tax code/Material,and i am getting the condition table in the key combination in FV11,and maintained,getting the values in the condition table.But my problem is i am not getting the maintained values in my Purchase Order.Please give any suggestions to solve this problem
Regards,
PR

To get the values in PO, maintain the condition records in MEK1.
FV11 is for tax calculation conditions
Regards

Error in Import Manager if Constraints are assigned to lookup table

Hi Folks,
I am using the Repository SRM-MDM Catalog...and in the Console,
For a Role, if I assign a Constraint for the lookup-table Product Groups, System shoots the error message in Import Manager when I try to Map the file.
Scenario: Say I have Product Group from LOC1-LOC5, and for a Z-Catalog Manager Role(Manager1) if I assign the Constraint-LOC1.....and if I Import a file in the Import Manager, system shoots the error message "Unable to retrieve Unique values for Product Groups".

Hi Mohan,
Are you updating any Qualified table.Please explain what table and also some more details.
Thanks
Ganesh Kotti

Import of Main and Lookup table in a single Map

Hey Guys,
I am developing a Proof of Concept to Import Main and Lookup-Flat in a single Import Map (by using a single excel file).
Below is my Table structure:
Main Table: Customer
--->Customer_Number (Text,Unique Field, Display Field)
--->Sales_Area (Lookup Flat)
Lookup Table: Sales_Area
Sales_Area_ID (Text,Unique Field,Display Field)
Sales_Area_Desc (Text,Display Field).
The import File (excel) has below attributes:
Customer_Number,Sales_Area_ID,Sales_Area_Desc.
When i start both Main Table and Lookup tables are empty (there is no data in Data Manager for either of the tables)
Now in the Import Map, i selected source as the excel file and target as the Main table.
I did mapping of Customer_Number as usual after that I created a compound field for Sales_Area_ID+ Sales_Area_Desc and did the mapping of this compound field. then did the mapping for Sales_Area_ID and Sales_Area_Desc.
Now since there is no data in lookup table, i select the "Add" button in the "Value Mapping" section. when i execute this map, it works perfectly and data is loaded in both the Main table and lookup table but if a new value comes in the excel(a value which does not yet exist in lookup table), the map fails, when i open it , it says that i need to redo the Value Mapping, again i click on "Add" button and it starts working. So basically the Import Map fails whenever i get a value in excel which does not yet exist in Lookup table.
Now my question is, is there a way to automate my import map, i thought clicking on "Add" button will take care of all the lookup values which are not already present.
Can anyone please help me in this regard.
Thanks
Saif

Hi Saif,
You can try the following option.
Right click on the lookup filed/compound filed in destination fields, and select the option 'SET MDIS Unmapped Value Handling' as 'ADD'.
Cheers,
Cherry.

How to apply Foreign Keys on top of a Common Lookup table

I have an issue where i am mandated to enforce RI on an applications database (a good thing). but I have several common lookup tables where many of the "codes" reside for many different code types. I also have the mandate that i cannot change the
underlying DDL to make composite keys to match the codes table PK. I am currently looking at creating indexed views on top of the Codes table to seperate the logical tables it contains. This is several hundred views. Although doable is there another solution
I am not seeing? I have scoured the web in search of an answer knowing I cannot be the only SQL developer in this situation. I do know that I do not want to write several hundred triggers to enforce RI. Table schema below, the CdValue column is the column
that is used throughout the hundreds of tables that use this codes table, and their corresponding column is not named the same.
CREATE TABLE dbo.CodesTable (
PartyGrpId INT NOT NULL
, CdTyp VARCHAR ( 8 ) NOT NULL
, CompId INT NOT NULL
, CdValue VARCHAR ( 8 ) NOT NULL
, CdValueDesc VARCHAR ( 255 ) NULL
, AltValueDesc VARCHAR ( 100 ) NULL
, DefaultInd CHAR ( 1 ) NULL
, OrderNum SMALLINT NULL
, ActiveCd CHAR ( 1 ) NULL
, ExpireDtm SMALLDATETIME NULL
, EffectDtm SMALLDATETIME NULL
, ModById INT NULL
, ModDtm SMALLDATETIME NULL
, CreateById INT NULL
, CreateDtm SMALLDATETIME NULL
, CONSTRAINT PC_dbo_EcdDetail
 PRIMARY KEY CLUSTERED ( PartyGrpId ASC, CdTyp ASC, CompId ASC, CdValue ASC )
 ON FG_Data
) ON FG_Data;
I did though run into one forum where a person brought up a great idea. Filtered Foreign Keys, what a novel concept, if it could work it would make so much less code to fix an issue like this. :)
ALTER TABLE dbo.BusinessStatus WITH NOCHECK
ADD CONSTRAINT FK_dbo_BusinessStatus_CodesTable FOREIGN KEY (LoanStsDtCd) REFERENCES dbo.CodesTable (CdValue) WHERE CdTyp = 'Status'
U.S. Army Airborne! The only way to fly

>> I have several common lookup tables where many of the "codes" reside for many different code types. <<
No! This is called “Automobiles, S quids and Lady Gaga” SQL and laugh at you or fire you or both. A table is a set; a set has one and only one kind of element it it. This is the basis of RDBMS and First Normal Form.
This is so bad it has a name; OTLT for “One True Lookup Table” ;I give an example of how stupid this in one of my books where a Dewey Decimal Classification for Churches is the same as the ICD code for deformed testicles.
There is no such crap as a “generic_type_code” in RDBMS. It either a “<something in particular>_type” or a “<something in particular>_code” in data modeling and the ISO-11179 standards.
You have more NULL-able columns in one table than you should have in an entire schema!
You have audit data (creation and modification) in the row under audit. This is both stupid and illegal. You cannot expose the audit trail to the data user by law. When you delete a row, you also destroy the audit trail –Doh!
You have no CHECK() constraint on the (effective_date, expiry_date) pair.
Putting “_table” in a table name is a design error called a “tibble” to make fun of how silly it. You might want to download the PDF of bad SQL code smells from Red Gate so you can avoid things like this.
>> the CdValue column is the column that is used throughout the hundreds of tables that use this codes table, and their corresponding column is not named the same. <<
“_value” and “_code” are both what ISO-1179 calls an attribute property. It is a silly as a list of adjectives without a noun.
Each encoding is a separate table in a valid schema, each with its own validation and verification. You have to stop doing this. This is fundamental!!
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL

Not able to populate a lookup table in Import Mgr

Hi,
Any tips why a lookup table after mapping not able to do 'match record' process
since not able to add the fields for match operation even they are enabaled/highlighted.
While mapping all the source data got successfully mapped with green dots.
There is an Auto_id field in that table.
Thanks in advance.
-reo

There was an auto-id field whose parameter changed to no dispaly inorder to fix the issue.

Importing Key Combinations of a Lookup table.

Similar Messages

Maybe you are looking for