Import Server - Multiple Qualified Table - Map Crash

Hello,
Requirement: I need to update multiple qualified table using single source file.
Preparation: I have created a map where mapping to multiple qualified table fields maually.
Have created a Inbound Port using the above map.
Problem: Import server throws an exception; while opening the Import Manager using the Port Option and corresponding Exception; Lot of fields were un-mapped. Looks like Import map crashed.
Please feel free to throw some light reg the same!
Thanks
Alexander

Hi Alexander,
If you are performing multiple qualifier table mapping and importing then you will hav eto create differnt map for each table importing.In that case you will rrquire multiple inbound ports and in each ports deatils you will give the map name pertaining to which qualified lookup table you wish to import.
Actually using automatic importing for lookups is not desirable as the lookups always need to be prepopulated before your main table importing.
The exception taht you are receiving could be due to the reason that the map you are saving is using only one table mapping and so most of the fields are left unmapped.
try not to use automatic importing for Lookup qualifier tables and use manual importing and see if the the exception still comes.
Hope it helps
Kindly reaward points if found useful
Thanks
Simona

Similar Messages

Strange Errors from Import Server on Schema-based maps for repeating nodes

I have already posted one thread about this, but perhaps some more in-depth information is required:
We have uploaded our schema into the console, and have mapped the following multi-node file to it:
CUSTOMER <repeating node>
MDM_CUST (new Customer number returned)
CUSTOMER(mapped back from XI for RECORD MATCHING)
CREATE_DATE (text field)
CONTACT<repeating node>
    CONTACT_NO (RECORD MATCHING : NON-QUALIFIER)
    CONTACT_SAP_NO (QUALIFIER)
     [NOTE: There are other qualifers for CONTACT, but only this one
qualifier is being returned and is the only field that would and should be updated.
The other fields should be left alone. However, it appears to overwrite EVERYthing
with NULL other than these two fields. The CONTACT_NO is the sole qualifer on
the table. It is a calculated field that equals the Auto-ID that is also produced on
the table - but obviously not mapped.]
PARTNER<repeating node>
    CUSTOMER_NO (RECORD MATCHING : NON-QUALIFER)
    PARTNER_FUNC (NON-QUALIFIER - Code given to lookup from PARTNER_FUNCTION table which has Code and Desc)
    PARTNER_NO     (NON-QUALIFIER)
    DEFAULT_PARTNER_FLAG (QUALIFIER)
<CLOSE CUSTOMER NODE>
In the Customer main table, all records are matched on CUSTOMER. The CONTACT_NO non-qualifer is matched to the CONTACT qualified lookup table directly since it is the only available non-qualifier. For the PARTNER table, the three qualifiers are mapped and then a compound field is created to map to the PARTNER table entry.
We have the Configurations set at:
Default Multi-Valued Update: Replace
Default Qualified Update: Replace
Default Matching Qualifiers: None
Our record matching is: Create / Update(ALL MAPPED FIELDS) / Update(ALL MAPPED FIELDS)
When the map is reused, the repeating nodes are all recognized, be it one node or many. However, when the map is reused, it does not automatically map the values for many of the Partner fields (nor the compound field) though the fields are correctly mapped.
Also, when we attempt to use Import Server to automate the mapping, we use the mdis.ini set to
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
We get a very strange error saying that :
[code]Encountered a pre-SP4 map. The map needs to be upgraded to SP4.
Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map.[code]
Could it be that our MDM 5.5 SP4 is not compatible with schemas generated with XI v.7 SP9?
All of our MDM is 5.5 SP4. It makes no sense that we would get THIS kind of error. Also, I am questioning our combination of these and other configurations since it doesn't always seem to do what it should

Hi Donald,
this sounds good so far. Just a short hint: you've set "Default Qualified Update: Replace". This explains why Import server "appears to overwrite EVERYthing
with NULL other than these two fields.". The reason is the replace. A replace means that the old values are completely deleted and only the new incoming ones are stored. I'd suggest to use any of the Update possibilities.
Note: the definitions you set in in the record matching step are mainly for the new records in the main table! Records in qualified look ups are handled differently! If you open your map in Import Manager, switch to tab "Map Fields/Values". Select a field that is your non qualifier. Right-Click on it and choose "Set qualified update" from the context menu. Now you can define which qualifiers can be used for the qualified look up matching. And you can define as well what should happen with new and/or existing records.
Regarding the value mapping: do you use keymapping? Or do you use simple values only? Do you save the map everytime you add a new value mapping?
Regarding the issue "Encountered a pre-SP4 map. The map needs to be upgraded to SP4. Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map". This sounds very likely like a bug in MDIS and should be reported to SAP!
Hope that helps
Michael

Import Server issues with SP4 maps

While using the Import Server, I have a newly created map using Import Mgr 5.5 SP4. (I used a schema created by XI v.7 SP9). When it runs, it throw and exception with the following error message:
<b>"Encountered a pre-SP4 map. The map needs to be upgraded to SP4.
Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map"</b>
It appears to not like new entries on the Partners table and balks at auto-mapping values for the compound field for the qualified lookup table at the Customer main level. The input record is outlined below. I have set the CONFIGURATIONS to "Replace/Replace/None" and "Automap values in batch" and in the map they are set to "Create/Update (ALL MAPPED)/Update (ALL MAPPED)".
Thanks in advance. Don
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:CustomerCreateResponseTest xmlns:ns1="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100">
- <CUSTOMER>
- <item>
     <CUSTOMERNO>0099999989</CUSTOMERNO>
     <MDMCUSTOMER>4539</MDMCUSTOMER>
     <CREATE_DATE>16/01/2007,09:39:30</CREATE_DATE>
   - <RETURN>
      <TYPE>E</TYPE>
      <MESSAGE>F2381 MESSAGE</MESSAGE>
     </RETURN>
   - <PT_CONTPART_RETURN>                    qualified lookup table
    - <item>
        <MDM_CONTACT>0000000002</MDM_CONTACT>           non-qualifier
        <CONTACT>0002111119</CONTACT>                qualifier
      </item>
     </PT_CONTPART_RETURN>
   - <PARTNERS>                              qualified lookup table
    - <item>
       <CUSTOMERNO>0099999989</CUSTOMERNO>           non-qualifer
       <PARTNER_FUNCTION>RE</PARTNER_FUNCTION>          non-qualifer
       <PARTNER_NUMBER>0090098989</PARTNER_NUMBER>      non-qualifer
       <DEFAULT_PARTNER>X</DEFAULT_PARTNER>           qualifier
      </item>
     </PARTNERS>
    </item>
   </CUSTOMER>
</ns1:CustomerCreateResponseTest>

For all watching this thread:
We were running MDM 5.5 SP4. We applied Patch 2 (not patch 3) to our 32-bit system and we no longer get this error. We now get an error that the "Source File does not conform to the XML Schema", an entirely new issue. I will open a new question regarding that.
Thank you. Don

Import Bank Details qualifier table not getting mapped in vendor scenario

Hi All,
I am using MDM5.5 SP5.
Trying to import the IDoc CREMDM04 from ECC 5.0 to MDM.
Using the note 830864 i have copied all the reference data to MDM using the xml that was generated by the program referred in the note..
But Bank details is missing in this reference data. If i try to use the map 99 for bank details i get the error msg "The map cannot be loaded because the table "Bank details" is not a source".
How do I get the bank reference data into MDM .
If I skip this step and i try to import the xml file of CREMDM04 (generated through XI). And then if i use the map 99 i get the same error.
If i use the map CREMDM04 I get the error "The map cannot be loaded because the table "E1LFA1M" is not a source".
Please help!
Thanks a lot!
Jyotika

HI Jyotika,
This usually happens when you have a lookup table which has more than one display field. You get this error because you have to create an Compound field, which might not be set in the map. In order to create a Compound filed just check wether all the individual fields in the destinations field BankDetails<X,Y,Z>(X,Y,Z are individually mapped) then just right click in any portion on the source fields and select compound filed's, it creates a Bank details field and automatically maps it to the destination fields. Some times it also maps the values; if not you got to manually map it.
I you have any problem please let me know.
Regards,
CHARAN

Map including spliting operation dosen't work in MDM Import Server

Hi All,
I met a problem with MDM Import Server when using a map file with spliting operation in it, although I can use it in MDM import manager to load data successfully. The error in log file is like this:
Record Matching...
Importing Lookup...
One or more attribute values are invalid.
One or more attribute values are invalid.
One or more attribute values are invalid.
One or more attribute values are invalid.
Import Failed!
The spliting in my map is: I split field "Category" into category1 and category2 with space " ". e.g. value "Trousers M" is splitted into "Trousers" and "M" . Then I map category1 to category and category2 to size.
I tried to delete this spliting and just map "Category" to "Category" then it works well for Import Server.
Is it the bug of MDM import server? can anyone give me a explaination?
Thanks! Bin

Under Configuration Options of the Import Manager,
check the values for
<b>Default Batch Handling</b>
AutoMap Unmapped Values = Yes
Unmapped value Handling = Add/Ignore/Fail.
Set the values according to your needs.
Make sure that the data source is updatable as well.

Qualified table

Dear all,
I have a requirement, for a single vendor record need to maintain multiple License details.
ie., main table 'Vendor' will hold Vendor record and each vendor record may have multiple License's. Do i maintain the license table as 'multivalued' Qualified flat. If yes how do i link vendor and License tables and what field properties do i need to set.
ex: a field as qualified/non-qualifier ?
Sonali

Hi Sonali,
Vendor ID, Vendor Name, Description can be placed in the main table Vendor.
License Number, Date, Description can be placed in the Qualified table with the License number as NQ and the determining fields ie Date and Description as Qualifiers.
Now When you do mapping of the Qualified table you will be bale to see only the non qualifier fields there.Map those fields with the main table fields and import in the Qualified table.
Now when you perform the main table mapping you will be able to see the Qualifiers as well as the non qualifiers fields and the lookup qualified field as well.
Firstly map all the main table fields such as Vendor ID, Vendor Name and Description then map the qualified tabel fields this will establish the mapping between the main table nad the qualified tabel records.
Follow this below link which will explain you better on qualified atbel mapping:
Taming the animal - Qualified Tables
Hope It Helped
Thanks & Regards
Simona Pinto

Issue in Mapping Qualified Table in Import Manager

Hi Experts
I have extracted Customer data from R/3 ECC, I could successfully loaded reference data, but when trying to load Main table data (Using DEBMDM06 MAP) I am getting mapping issues with Qualified table (Sales Data and Bank Details).
Error Messages
Map 'Sales Data' field to import qualifier(s)
Map 'Bank Detals' field to import qualifier(s)
I have checked and found that all the field and value mapping is in place, If i remove mapping for the qualified table fields then the data is ready to import.
What is the issue, and how do I import Qualified Table data.
Appreciate your inputs
Gaurav.

Hi vickey ,
Kindly go through the below link it will help you understand better the mapping the workinga nd importing of Qualified tables:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e319a6e(Qualified importing with main table)
Hope It Helped
Thanks & Regards
Simona Pinto

SRM MDM - Multiple hyperlinks import into qualified table

Hi,
I need to create an import map where I can import two hyperlinks (URL2 and URL3) into the Hyperlink qualified table.
How can I achieve this?
I have an XML schema where the two hyperlinks are given in separate tags:
<URL2>http://www.test.net/xxxx</URL2>
<URL3>http://www.test.net/yyyy</URL3>
Can anyone provide me with a HOW-TO for how to map these two tags into the qualified table Hyperlink.
Maybe I should create two sections in the XML?
<URL2>
<MIME Type>URL</MIME Type>
<URL>http://www.test.net/xxxx</URL>
<URL Description>TEST URL</URL Description>
</URL2>
<URL3></URL3>
KR,
Thomas

Thank you very much. This worked fine.
Now I have another problem someone might be able to help me with.
The sending system does not wish to send a repeating XML tag with the two hyperlinks. It causes restrictions in the data amount that can be sent.
We see two possible solutions
1.
Building the hyperlinks in MDM, like a calculation.
<URL2>http://www.test.net/xxxx</URL2>
<URL3>http://www.test.net/yyyy</URL3>
xxxx and yyyy are values in fields we have in the MDM structure. Everything before this in the hyperlink is always the same.
Is it possible to create the hyperlinks based on the value of xxxx and yyyy? If yes, how could we manage this, also filling the fileds: URL Description, Hyperlink Type and MIME Type with correct information?
2.
PI can create the URLs during integration.
Which of these two should we use?
KR,
Thomas

Source file structure when importing a qualified table

Hello MDM:ers
I need to import a qualified table into the following repository
(it is simplified to illustrate the problem):
Main table: Products
Fields: ID (int), Name (Text), Part number (Qualified)
Qualified Table: Part Numbers
Fields: Manufacturer (Lookup), Part Number (Text)
Lookup table: Manufacturers
Fields: Name (Text)
The source file is a very large text file that has the following structure:
Part ID          Name     Part no. Manuf 1     Part no. Manuf2
123          Nut     ABC               XYZ
456          Bolt     DEF               QWV
The result Im looking for Is to map a file structured a above so that two main table records are created (Nut and Bolt) which both have two qualified table records for each manufacturer. I have not been able to create such a map. I have tried to partitioning and combining fields without success.
I have no problem creating the map if I manually restructure the file to look like:
Part ID          Name     Manufacturer           Part Number
123          Nut     Manufacturer 1          ABC
123          Nut     Manufacturer 2          XYZ
456          Bolt     Manufacturer 1          DEF
456          Bolt     Manufacturer 2          QWV
It where a way to import the file directly in MDM without restructuring it?

Hi Alexander,
MDIS will not work fine if you have multiple tables as the mapping is saved only for 1 table. If you have multiple tables then after performing the process of Pivoting/Reverse pivoting, you will have to use joins.
Join the other tables as Lookup in the Main Table
Save all your configuration in a map. And then configure the map in the port.
It should then work with the MDIS also.
hope it helps.
Thanks and Regards
Niitn Jain

Not able to Populate Qualified Table in Import Manager

Hi,
I am performing following steps for populating Bank Detail Qualified table in MDM from R3 but not able to populate the data.
1.Populating all lookup tables like Account_no,Bank-Key.......
2.Mapping all fields in Bank detail table except the 'Collect Auth'
field which is Qualifier
3.In Customer table(Main) mapping Collect auth to Bank Detail field and
customer_no to its corresponding ID.
It is not populating the Bank detail data which are available in lookup tables
Appreciate your suggestion
-regards,
reo

Reo
Matching will be based on the Display field (at least one) of the Main table. This is for example the Customer Number.
You also need to map all the display fields of the qualified lookup table. Then you can set the Qualified Update Action by right clicking on the field in the main that is linked to the qualified lookup.(the Collection_Authorization I think). Set the option that well update/append/replace the qualified data fields of the looked table.
There is two how_to_guides that will help. You can download from SAP Service Market Place. (Otherwise I can email to you)
How To Troubleshoot MDM Import Manager
HowTo_LoadQualifiedFields
Rgs
Con

Using Import Man to load Data into Multi Value Fileds in a Qualified Table

Hi there,
When using the Import Manager, i can not use the "append" option to load data into my multi value field which is contained within my qualified table.
Manually it works fine on Data manager, so the field has been set up correctly. Only problem is appending the data during Import Manager Load.
Any reason why I do not have this option available during Field mapping in Import Manager. The selection options are shown but in gray.
Would appreciate any sugestions.
Chris Huggett

Thanks Sowseel
Its a good document but doesn't address my problem, maybe My problem isn't clear.
The structure(part of) that I have currently is as follows.
Main Table - Material
                       QFTable- MNF PN
                           LUField - MNF Name(Qualifier Single Value)
                           LUField - BU ID (Non Qualifier Multi Value)
                           TField   - P/N- (Non Qualifier)
I know how to load data to the main and qualified tables, but what I can not do, using Import Manger, is updating the "LUField - BU ID (Non Qualifier Multi Value)" using the append functionality.
Thanks
Chris Huggett

Mapping issue with Qualifier table

Hi,
1. I have an issue after mapping all 3 non-qual flds of a qualifier table in main table getting the compound fld enabled but selecting it , not mapping automatically to the appropiate compound field in the destination side, but giving an error message
"unable to retrieve source record".
2. The second issue is that after mapping some of the fields and qualified table and loading the maintable data, saving the map but subsequently when trying to open the saved map , it is coming out with the usual main error window
SAP MDM Import Manager
SAP Import manager has encountered a problem and needs to close.
We are sorry for the inconvenience.
Debug Close
Appreciate your help/suggestion on this issues.
regards
-reo

Answer for Qn2:
First you have to map all the display fields to individual Source Fields..
Once you have mapped all the dispaly fields of the Qualified Table, you have to do value mapping for the Fields that require Value Mapping.
Ex: Source Field A -> Destination Display Field 1
Source Field B -> Destination Display Field 2
Source Field C -> Destination Display Field 3
Now Value Mapping where required should be done.
Once the value mapping is done, then you can create a Compound Field.
If you have done the previous steps correclty, then the compound field name is enabled for you to create Compound Field.
Now map the newly created Compound Field to the Qualified Lookup field of the main table.
Now you have to click on the Automap for value mapping.
Hope this helps.
Please reward if you find this helpful

Qualified Table (Bank Details) Import Question

I am using MDM 5.5 SP6
I am using the Standard SAP delivered Vendor Master Repository and trying to load the Qualified Bank Details table. Bank Details qualified table we have 9 non-qualified fields and 6 qualified fields.
Do we need to load the non-qualified fields in the bank detail table first?
Anyone help me with details about how to load this table including linking this to the main table?. If anyone has any document explain the steps in detail then could you send it?
Thanks in Advance
Steve

First thanks to all who contributed.
I am able to load the qualified table but these non- qualified fields (Street, City, Swift Code, Bank Group, Bank number and Bank branch), I am not able to map it so after loading it was blank.
Out of the 9 non-qualified fields in the Bank Details Qualified table, Country, Bank Key and Bank name are DISPLAY fields and I am able to map and load these fields.
Other non-qualified fields such as Street, City, Swift Code, Bank Group, Bank number and Bank branch are NOT DISPLAY fields. While using the import manager and doing field mapping, for these 6 fields there is NO destination fields displayed. So I couldnu2019t map it.
When I made the above 6 non-qualified fields as DISPLAY fields, then try to map it, I am able to see these fields in the destination side and did the mapping. After import still those 6 fields are blank.
What I am missing here?. Is there any limit that only 3 non-qualified fields we can map it?
Steve.

OCI mapping 2 Qualified tables

Is it possible that 2 qualified tables can be OCI mapped to the same set of fields on requistions page?
We are storing Material Master information in one Qualified table and Calalog information in another Qualified table. The end user can EITHER select Material Master information OR Catalog information, add it to the shopping cart. But, when the items from shopping cart are brought back to the Requistion page, it populates the same fields.
Can it be achieved. Any Ideas.
Thank you guys.
Shai

Hi Priti,
For multivalued field you need to check for Qualified Update option. For this you can refer page 257 of Import manager 7.1 reference guide. Try this option, it should solve your problem.
Thanks & Regards
Dilmit Kaur Chadha

Qualified table import

Hi folks,
could you please let know the procedure for importing the qualified table for a master?
Regards.
Jyoti

Hi Jyoti,
the procedure for importing the qualified table is as below:
1. First import the non qualifiers combinations and in this you may select the source table as main table and destination as the qualified table.
2. Now select main table as destination table and main table as source then first map the non qualifiers fields and all values.
3.MAke sure all the values are mapped for the non-qualifiers, now right click on any of the nonqualifier field and create a compund field.
4. the compund field will be created and automapped. BUt you have to map the values manually or "ADD" them.
REg,
Bis

Import Server - Multiple Qualified Table - Map Crash

Similar Messages

Maybe you are looking for