Field Type in Import Manager

Dear all,
I am importing Vendors in MDM SP4 that I extracted from BI. In Import manager my Vendor and GN_Vendor fields appears with numeric type but I created them in the Console with text type. I also cheched the xls input file but they are in text format. Can you please tell me where to change the field type from numeric to text.
Because I can only import Vendors who have numeric name.
In advance thank you for your kind help,
Aklilu

Hi Aklilu,
As Far as I understand,
the problem is with your source and not the destination.
The source field type from BI, is numerical and this has to be changed to text in the source
The destination field is a text field and hence no need to change the field type in MDM.
Hope this helps you solve the problem.
Let me know the result.
Thanks and Regards,
Rashmi Jadhav

Similar Messages

How to map Boolean Types in Import Manager

Hi,
I have a issue in Import Manager for mapping Boolean Types.
I have a field which has a single KEY and multilple values(for different languages).
I want to map it to a field in a Tuple.
I can map the Key to field name.
But the values, I am not able to map. Could you help me here please.
Thanks a lot in advance.
Regards,
Rashmi

Hi Anton
Format your GM Time source as YYYY:MM:DD:HH:NN:SS:TTT (e.g. 2010:02:19:14:34:28:000). Deviations from this format seem to confuse the IM.
HTH,
Mark

Date field conversion in Import Manager

Hi,
I am getting the source Date field as 'Text' type and want to convert it to Date type.
Is it possible in import Manager?
What are the best way to manage the issue.
Appreciate your reply
regards,
reo

Hi Reo,
The data types of source data values are automatically
converted within the Source Values grid based on the data type of the
destination field to which the source field is mapped, even when stored
in the source data as text values.
Original source values appear with their original data type in the Value
column, and the converted values appear in the Converted Value
column with the data type of the mapped destination field and the
proper grid cell type for editing (e.g. text, numeric, measurement,
currency, date, time, Boolean). If necessary, individual values can then
be manually edited to override errors or omissions in the source data.
Regards
Neethu Joy.

Designate form field type during import process Acrobat 10

Is there a way for me to assign a type of form field to content in Word when I import it into Acrobat to create a form? Acrobat knows to create entry fields when I input underscores after text, and it knows to create digital signature fields when it sees the word "signature" followed by underscores.
However, I'm having a problem with check boxes and radio buttons. I've been creating them manually, which means they're never exactly the same size or positioned exactly right. It's also very time-consuming. Is there something that indicates to Acrobat that it should create a radio button or check box, much like the underscores tell it to create an entry field?

No there's not. But there are a number of things you can do to create fields that are the same size and quickly align, as discussed here just the other day: http://forums.adobe.com/thread/1087979?tstart=0

Look up a field in MDM Import Manager

To look up a field from a lookup table into a primary table:1. In the Source Hierarchy tree, select the lookup table node in the primary table into which you want to look up a field. 2. Right-click on the node and choose Lookup from the context menu, or choose Source > Lookup from the main menu, and select the lookup field from the cascading menu of fields in the lookup table.
Let's say I have a lookup table "category", but when I right click on it, I can not choose Lookup, because it is gray. I am not sure if I am misunderstanding. Could anyone give me an example or explain somthing. Thank you.

Hi Alfred ,
May be I not understood correctly , Pls correct me if I understood wrongly .
It seems you want to create lookup field in 'Category' lookup table or 'Main' table .
I guess you created 'category' lookup table , and now add its field into main table as lookup table to get relationship between both .
If this is correct then you not have to make change in 'category' lookup table , but instead add a new field in 'Main' table as lookup[flat] and link it to 'Category' lookup table in 'lookup table' property of that field .
Hope you understood it , otherwise give you email . will send you a screenshot describing lookup relationship .
- An

Set Key Field in Import Manager

Hi All,
I have 2 fields in my source file(name,category) .category(look up Field) is the key field and name(display Field) is the matching field.
I got file like this......
Name                  category
1                           A
1                           B
1                           C
While importing i got an error stating that Import failed. The destination record was referred to by multiple source records. Duplicate source records should be merged before importing them.
Import action: Update (All Mapped Fields)Source record no: 1
But in this case my key field is Category based on category then these 3 records will be 3 different records.
Please let me know the use of Set Key field in the Import Manager and how it works?

Hi,
It's not about set of key field in MDM Import Manager but the reason is that you can not select more than 1 category(Lookup Taxonomy) in maintable for one record. thats why error is coming because for this Property Multi-valued always No.
Even, you can try this in Data Manager manually create three Category A, B and C in taxonomy mode on selecting Sub table Categories, then on selecting main table, when you select category field(which is lookup to categories table)for a particular record you could able to select only one category A, B or C.
i would suggest make a Attribute of type text having three values A, B and C and mark this as Multi-Valued in Attribute Detail and link this Attribute with your category. in this way you can attach three values A, B and C with your Record.
Other thing you can do,make this category field as (Lookup Hierarchy not lookup taxonomy) in main table to Subtable(Hierarchy) then for this field in main table you can set Property Multi-valued = Yes in MDM console and then after Import using MDM Import Manager finally only one record will get created in Data Manager as:
Name Category
1         A;B;C
Hope it will Help you,
Rewards if Useful.....
Mandeep Saini
Edited by: Mandeep Saini on Jun 20, 2008 8:46 AM

Combining two source fields in Import Manager

Hi,
I am trying to combine two source fields say fld1 with 5 digit and Fld2 with 3 digit so that combined fld3 of 8 digit can be mapped to a 8 digit field in destination MDM side.
Any suggestion how to do this is highly appreciated
Thanks,
-reo

Hi Reo,
I am just adding details to how to combine fields in the import manager.
To combine two or more existing partitions for a destination node steps are as follows:
1. In the appropriate source hierarchy tree, select the node whose partitions you want to combine.
2. click on the Partition Field/Value tab to make it the active tab.
3. In the appropriate Partition list, select the two or more partition items you want to combine into a single partition.
4. Click on the Combine button, or right-click on one of the items and choose Combine Partitions from the context menu.
5. MDM combines the selected partition items.
6. Now you can map this partition directly to the destination field.
But as ur requirement seems ,u do not need to set delimiter.
Hope it will help you and let me know the results. please remark .
Thanks,
Shiv Prashant Dixit

Updating Qualifiers using import manager

I am having difficulties with updating my data in qualified lookup tables. I have a qualified lookup table Produkt Market Data with market as a display field (hierarchical lookup).
All other fields in this table are qualifiers, most of them multi valued. I have loaded the non multi value fields in the table first, so there is an entry for eg product 4711, market Health Care.
When i try to update a field text (multi valued flat lookup) using the import manager, the record 4711-Health Care is not updated but a lot of entries 4711-Health Care are created extra, each of them containing one line of text. I used the option update all mapped fields (and have mapped only product, market and text). When I choose the option update Null fields only, nothing happens: only the lookup table for the text is updated.
can anyone tell me what i am doing wrong. It should be possible to update qualified fields using the import manager instead of creating new entries shouldn't it??
Regards,
Bert

Hi,
See the below example.
HeirarchyT [Hierrachy Table]
Name Text[5]
Data in Hierarchy Table
Hier1
-H1
--H3
-H2
--H4
MainT[Main Table]
Field1[Text5]
QField1[Lookup Qualified multivaled]
LT1 [ Flat Table 1]
NameLT1 Text[100]
CodeLT1 Text[2]
Data in this Table
LT1Val1 LT1Code1
LT1Val2 LT1Code2
LT1Val3 LT1Code3
LT1Val4 LT1Code4
LT2 [ Flat Table 2]
NameLT2 Text[100]
CodeLT2 Text[2]
Data in this Table
LT2Val1 LT2Code1
LT2Val2 LT2Code2
LT2Val3 LT2Code3
LT2Val4 LT2Code4
QualTable[Qualified Table]
QH1 Lookup[hierarchy]
No(Qualifier) Yes(DisplayField)
QMLV1 Lookup[Flat]
Yes(qualifier) LookupTable[LT1]
Yes(Multivalue)
QMLV2 Lookup[Flat]
Yes(qualifier) LookupTable[LT2]
Yes(Multivalue)
Intial data in the repository:
Record 1: N1
Qualified Data:
QH1 : H3
QMLV1: LT1Val1,LT1Val3
QMLV2: LT2Val2,LT2Val4
Record 2: N2
Qualified Data:
QH1 : H4
QMLV1: LT1Val2,LT1Val4
QMLV2: LT2Val1,LT2Val3
Lets say u have source data in Excel sheet like below.
N1 H4 LT1Val2,LT1Val4 LT2Val1,LT2Val3
N2 H3 LT1Val3,LT1Val1 LT2Val2,LT2Val4
Follow the instructions given by Rajani till step 5.
In the Step 6 selct The default import action as "Replace".
I hope this helps.
Thanks and Regards
Subbu

Difference bet. Import manager and Import Server

Hi
Can anybody tell me what is the difference between a Import Server and a Import Manager? And How data is imported using these two?
Thanks in advance

Heii,
In MDIS :
MDIS can be installed on any machine on a network. It works with the MDM Server to import data automatically into existing MDM repositories. If MDIS and its associated MDM Server are installed on the same machine, no further customization needs to be done. If the MDM Server is located on a separate machine from MDIS, you will need to edit the MDIS settings file, mdis.ini (for more information, see MDIS Configuration).
Before you begin using MDIS, you need to be sure that both MDIS and the MDM Server are running and that the target MDM repository is loaded and running. Directions for starting MDIS are located in this section. Directions for starting the MDM Server and loading a repository can be found in the MDM Console Reference Guide
In case of Import Manger :
The MDM Import Manager is a GUI cockpit that defines a very specific sequence of steps to prepare source data for import. But rather than perform the import a record at a time as with other import tools, the MDM Import Manager offers a comprehensive set of data transformation capabilities that allow you to pre-process the source data a field at a time prior to import.
Moreover, for each field, the MDM Import Manager collapses the set of all values across the entire set of source records down to the set of distinct values, whose number will usually be dramatically smaller than the total number of records, often by several orders of magnitude.
Field-at-a-time rather than record-at-a-time processing and the distinct value lists of the MDM Import Manager are together the lynchpin of its patent-pending Parametric Import technology, which supports the import of electronic source data from any tabular or XML format.
Hope this might help to remove your confusion between Import Manager and MDIS.
Plese reward If you find this useful.
Rgds
Deepak

How to import data usin Import manager if one of the field is of type LOOKUP[FLAT].

Consider a scenario:
Where I created a Main table named STUDENT and it has 4 fields,
a) Among which 2 fields are OF DATA TYPE TEXT[50] and
b) Remaining two are of DATA TYPE LOOKUP[FLAT] and corresponding look up table also created in the repository.
When I tried to create a file with certain input records and tried to import the values into the Main table using MDM IMPORT Manager, I am getting error at the IMPORT STATUS tab with the action item message: MAP 'FILED NAME OF LOOKUP[FLAT] TABLE' FIELD VALUE(S).
Do I need to do any special action to import record if the field is of data type LOOKUP[FLAT].
Please advice.

Hi,
Since you need to import value into a field which is referred by a flat look table, you need to map the values of that field to the values maintain in flat look up table.
You can do the mapping from "Map Fields/Values" Tab.
You have probably Mapped Source fields with destination fields, but in case of importing values in lookup fields you need to map Source Value with destination value.
Keep the cursor on the required lookup field in Source field section, below that section you will be able to see Source Value section perform the mapping in that section too and it will resolve your issue.
Regards,

SRM-MDM - loading hyperlink field in import manager

Hi forum members,
I am having trouble loading the hyperlinks in for SRM-MDM in import manager.
What fields / values do I need to map to load this please?
I have mapped the hyperlink source field to the hyperlink destination field, but get an error during import executing saying there is an creating lookup table entry.
Is anyone able to provide step-by-step details of which mappings are needed?
Thanks very much,
Nick

Hi Nicholas,
the non-qualifier for the hyperlinks table is the type. Therefore you need to also map this field. Please check note 1077701 (under 11.) on how to use the types.
Let us know whether that helped.
Best regards
Christian

Field type - Log - Syndicate and Import

Hello All,
How to syndicate and import the field type "log" .
I was not able to find any documentation for this.
Thanks in Advance.
Shai

Hi Shai,
The guide says the following about log field type "Text Large field with internal structure for managing multiple timestamped blocks of text within a single field."
I personally have not tried importing Log field.But what i would guess is,after you are done with field mapping just like it is for other fields in import manager,care has to be taken in mapping the values as there would be multiple blocks of text.
I guess value mapping should be the only tricky part in this,please let us know your findings.
thanks,
Ravi

Sharepoint 2013 Active Directory Import- Manager field not updating

Hi,
SharePoint 2013 Active directory import -Manager field not updating
Concern/Issue-
We are using SharePoint and configured the Active Directory Import .First import it seems everything is working fine and OOB Organization chart built using User profile data is coming out right.
Now the user is moved from one Organization Unit to Another.
Now our Manager field is not Updating .There is change in AD manager attribute but not reflecting in the SharePoint User profile.
Manger field is mapped to "manager" attribute in SharePoint.
We tried removing the user and Re-Import using Incremental import but no luck.
Thanks for help in advance
Sachin

Moving a user from one OU to another in AD won't normally change the Manager attribute in AD. You would need to edit the user's organization settings to change the manager value in AD. I've also seen these changes not be picked up unless something
other than just the manager field in AD changing. Try changing something like Office location and see if the manager change is picked up by AD Import.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Import Manager and Display Fields

I've been using SRM-MDM 3.0 for a couple of months and 1 fundamental MDM design has always bothered me and I was hoping to get some resolve on this.
The purpose of Display Field is 2 folds:
1. Display the field in the Catalog Search UI for a lookup table: i.e. if both Supplier Name and ID are Display Fields, then in the Search UI, both fields are displayed to the end-user. If only Supplier ID was the display field, then in the UI only the ID is displayed.
- From a usability pov, tables such as Supplier and Product Group should have the name or description fields displayed in the Search UI as the numeric values are meaningless to the end-users.
2. Display field ALSO affect what is the key used to import data into a table. So if Supplier ID is the display field for Supplier table, then in Import Manager, the Supplier ID values are displayed and must be mapped to the source values.
- From an importing pov, mapping values should always be an index-like field, such as Supplier ID or Product Group ID, or ISO, and usually never the actual name or description field.
But SAP has tied the two together. So in order to display the name/description to the end-user, we must enable the name/description field as a Display Field. But we also want to map based on the index/ID field, so we also enable the index/ID field as a Display Field. Now in Import Manager, we have two Display Fields for a table (i.e. Supplier ID and Supplier Name for Supplier table) and I've noticed some issues with this:
1. You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible. What is funny is that standard SAP extract program only extracts the ID fields, BUT the standard SAP repository has the name/description fields as the Display Field. Automap is a must for tables like Product Group where hundreds of lines can make manual mapping a pain.
2. I also noticed you cannot Add values to a table that has 2 Display Fields, you can only map to existing values. The Add button is grayed out.
With all that said, when you're replication ECC Contract Data using MECCM, for tables like Supplier and Product Group, what fields should be set as Display Fields, and if there are multiple Display Fields, what special setting needs to be done in Import Manager to enable automapping? Even standard SAP Import Map (_MDMContractDataTransmission_ProductID) throws errors when multiple fields are set as Display Fields.
I'm not familiar with the partitioning function, and I've seen PDF's about it, but don't really see how it could be helpful. I've also read someone suggesting changing the DF's before import, which I think is unacceptable, as this requires unloading/loading repositories everytime an import happens.
Thanks for reading my paragraph and any input is greatly appreciated.
Edited by: Derek Xu on Apr 30, 2009 6:50 PM

Hi Derek,
Thanks for writing your thoughts. I would like to provide some information on one of your points where in you have mentioned that :
You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible.
I completely agree that if you have 2 fields in MDM repository and you are only importing only one of them, then you cannot use the Automap feature of Import Manager. So in your case, the description is not getting importing, so you cannot use Automap in that case.
I had a very similar requirement in one of my project and we went with creation of a Import Value template. We created a template with all the possible values for all the look up tables in that and mapped it once in the Map. Hence, next time, the Map was used to automatically Map the source and Destination values for all the look up tables.
SAP-MDM Automatic Import Requirement u2013 Creation of a Value Mapping Template:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ad0cff-19ef-2b10-54b7-d4c7eb4390dd
Please read the above article and hope its useful. You can go for this approach in your case if suitable.
I have mentioned examples of descriptions and their respective fields in the article.
Hope it helps.
Thanks and Regards
Nitin jain

Import Manager - Problem with 0..n field in Import Manager

Iu2019m having problems with XMLs that contain multiple or single tags in MDIS process. For example: I did the map using a XML with multiple tags for Address:
<address>
<item>
u2026
</item>
<item>
u2026
</item>
</address>
When I send two address or more Address, the Import Server work fine, but when I send only one Address, the address is not imported.
<address>
<item>
</item>
<item>
</item>
</address>
Opening the xml file with only one Address in Import Manager, I saw that the fields isnu2019t mapped, but when I open a xml file with multiple Address itu2019s open correctly.
The XSD cardinality for the Address\Item is 0..n

Hi Evandro ,
If it is processing the input file correctly through the Manul Import manager process then update your latest Map by using SAVE As option or else save this correct map with a new name altogether and use this new map in the port for automatic importing.
If your file is able to process correctly through the Import manager without showing any errors till the Import step in the Import manager then this map must be correct and shoul automate the importing correctly.
Provided you are using the similar file for automatic importing as well.The file name and the fields as well as the value mapping as saved in this corrected map must not differ with the input file else this saved map will not be able to import correctly.
Check to see if you have made correct setting for automatic importing by refering the below link:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm (Automatic importing MDIS - Import manager ref guide>MDM import server(MDIS)>MDIS Consfiguration)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e(mdm import and syndication server)
Also check the exception folders if your import is not taking place automatically:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm (Exceptions- MDM Import Manager MDIS-Exception handling)
Hope It Helped
Thanks & Regards
Simona Pinto

Field Type in Import Manager

Similar Messages

Maybe you are looking for