Import Server - Workflow related value exceptions

Hi,
Our Import Server is importing multiple records, one record per file. The inbound port is configured with a file threshold of 5, 50000 chunks and 5 parallel chunks.
We are using a workflow on import to assign values to 2 different fields. In the start step of the workflow the records do not get checked out.
When importing 1000+ records it works great, but a couple of times it runs into value exceptions.
In the log files I can find the following error:
Import failed. Cannot import record with workflow because the record is already checked out
Import action: Update (All Mapped Fields)
Source record no: 16
All MDM components have version 5.5.42.92.
I saw a similar issue in a different thread. Is this fixed in 5.5.42.98?
Thanks & Best Regards,
Ingo

Dear Saurabh,
The record is not checked out in Data Manager at the time the error occurs.
Nobody is checking out records prior and during the whole test run.
5.5.42.98 - I tried this out and get the same errors.
In our project we are still on 5.5.42.92 and won't upgrade until we know that another version is doing better.
There are some functionalities in MDM5.5 SP06 patch 1 that are not working well, for example try out the qualified update (update (new links create, existing links update (all mapped fields), that you can set on field level and you will get some unexpected results. We won't go for SP06 until we are really sure that all issues we experience are fixed.
What else could be the cause for this error?
Thanks & Best Regards,
Ingo

Similar Messages

Value Exception in Import server

Hi Experts,
My requirement is i have 100 files in the ready folder while processing first file through import server, it got value exception which i fixed manually through import manager port option and saved map as update. But even after the files which are having records with same values also moving to Value exception. Can you please me help me out to fix it.
Thanks
Narendra

Hi Mullapudi Narendra,
Value exception only come when any new value occurs in you lookup table so avoid this in importmanager configuration setting require to set MDIS parameter
in MDIS Add / Map / fail and ignore detail as follows
Add : value at destination side doesn't exist then this value get added to your lookup table as well as update this value at record. add new value at lookup subtable and update record at main table
Map : value will only map which are exist at destination side. update records at main table
Fail : if any new value occurs which is not exist at destination will not allowed to import this record as well as lookup field value.
entire record will get fail and doesnot import lookup subtable and maintable
Ignore : if any new value occurs which is not exist at destination will ignore this value and remaining data will get import except lookup field which contain new value .only value will ingore at lookup subtable and maintable for respective field, other field data of file will import
Thanks,
Jignesh Patel

Import Server Error - Value Transformation

Hi,
I have two questions on import server and import map.
1. My source xml does not have company code segment (customer repository), when I opened my xml thru import manager using my import map, I dont see any source fields belong to company code segment, which I think is right. But the same xml when it runs thru import server it throws "Value Transformation" error on fields that belong to company code segment which is not present in the source xml. Any help on this issue is appreciated.
2. In import maps, any new field mapping is saved using "Save update" option, but when I unmap any field, "save update" option does not save it, but "save as" option does save it, but the downside it just saves the current mapping. Any help on this is also appreciated.
Thanks
Job.
Edited by: Job Daniel on Jul 21, 2008 8:44 PM

Hi Sekhar,
Go to Services.msc in the system where your MDM servers are installed and restart the MDM Import server service.
Then try connecting again.
Your error message basiaclly points out that you are using Automatic import but as your MDIS server is not up and running the importing cannot be performed.
So make sure your MDIS is functioning properly and you have made the necessary settings in your MDIS.ini file and port property in console for correct importing.
You can check the mdis settings needed in the below path:
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)
The port in MDM Console must have processing type as Automatic and the correct map attached.
Hope It Helped
Thanks & Regards
Simona Pinto

Correct Import Server Registry Key

Zenworks 6.5, Zen 6.5 agent on the local workstation.
I have been troubleshooting some issues with workstation import at several
schools. I need to import the workstations to each schools container, so I
push the registry key to the workstation for the import server IP.
I am pushing this key HKLM/SOFTWARE/Novell/ZENworks/ZENWSREG with the
string value ImportServer = x.x.x.x
I have a local admin who has tried this (upgrade from Zen 4.x to Zen 6.5)
and hasn't been able to get it to work. He has configured another registry
key, and it does seem to work.
This is the other key - HKLM/SOFTWARE/Novell/Workstation Manager/Import
Server with the value as the IP address for the import server.
I thought the ZENWSREG key was the correct key, and everything I have read
on the forum indicates this.
Any ideas why the Workstation Manager key works and the ZENWSREG key
doesn't?
TIA
Dave

Thanks Jared. That's what I thought. This particular school has other
issues, including Clean Slate which blocks writing to both the HD and
Registry.
I'll post back if I find anything interesting.
Dave
"Jared Jennings" <[email protected]> wrote in message
news:Yk8Ag.3354$[email protected]..
> Dave,
>
>>I am pushing this key HKLM/SOFTWARE/Novell/ZENworks/ZENWSREG with the
>>string value ImportServer = x.x.x.x
>
> This one should be right. Have you seen the following TID?
> http://support.novell.com/docs/Tids/.../10068910.html
>
> Using the TID, you might enable logging and see why the import service
> doesn't like the key.
>
> --
> Jared Jennings
> Data Technique, Inc.
> Novell Support Forums Sysop
> http://wiki.novell.com

Workflow Manager with Project Server error Exception Starting Workflow: The value for column _WORKFLOW_INSTANCE_UID_ in table _WorkflowInstance_ is DBNull

Hello,
The project server workflows were running fine on my servers (2 App and 2 WFE). suddenly workflows are not working anymore.
and I am getting the below error:
DBNull.. Trace: at Microsoft.Office.Project.Server.Schema.WorkflowDataSet.WorkflowInstanceRow.get_WORKFLOW_INSTANCE_UID() at Microsoft.Office.Project.Server.BusinessLayer.Workflow.StartWorkflow(Guid projectGuid, Guid enterpriseProjectTypeUid, Boolean
isNewProject, Guid previousEntepriseProjectTypeUid, Boolean skipStage, Guid stageToSkipTo):
WorkflowExceptionStartingWorkflow (35115). Details: id='35115' name='WorkflowExceptionStartingWorkflow' uid='047a6f2d-8a44-e411-8bf4-0050568b37eb'.
I checked all DBs; all running fine. Also I tried to re-register the workflow with my site collection. but nothing worked.
Any suggestions?
Twitter : @MShoubaki | http://jo.linkedin.com/in/mshoubaki

Hi Mohammad,
I was able to resolve my issue by installing KB2880963. I did not have any of the other updates mentioned installed, but it did resolve the issue.
Note: I did need to restart my servers.
See Below from
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b189e4b8-bb9e-4ade-a3d5-cd2e0f90e93f/workflow-not-working-after-installing-service-pack-1-and-patches?forum=sharepointadmin
Here is
the security update which you will need to install.
Update 2880963 for SharePoint Server 2013
http://support.microsoft.com/kb/2880963
Chcek the link for details.
http://expertsharepoint.blogspot.de/2014/08/workflow-not-working-after-installing.html

Import server: Undefined elements exception

Hi,
I do have a problem with the import server. I get ,'save-update map' structural exceptions in the import server. It complains about undefined elements, and if saved the update it works for one single XML file but other still fail with similar (other element though) error. Mapping the files in the import manager just works. We are using version 5.5.41.70 here of all components. I noticed a thread which explains about sp5 patch 01, hotfix 1, which fixes this, but we're having that one already.
I did validate the xml already against the xsd used, the xml is valid.
Error from logfile is:
"Some portions of this import map are out of date.<LF/>Solution: Please, Launch the Import Manager GUI, preferably using the original source file that the map was generated for, otherwise the same source file and Save Update [File->Save Update] the map.<LF/> Parent hierarchy: <E1MARAM>.<LF/> Undefined element: <EKWSL>. ".
Thanks,
Wim

Hi Wim,
it looks like that your Import Map does not have all IDoc fields mapped to the corresponding repository fields. If you map the fields in Import Manager and choose the Save->Update option, IM adds the new mapping to the old existing one. But of course it is still possible that there are other unmapped IDoc elements which need to be mapped once manually before the Import Server can process the file automatically. The best way to solve this is creating a "Dummy" IDoc file that contains a value for each and every field. Then use this "Dummy" IDoc in Import Manager, load the Map and check the mappings. You can add/delete mappings according to your expected real data. Save->Update once again and you should not into the issue any longer.
Best regards
Michael

Import server - Structural exception

Hi All,
I configured all the necessary setting required for Import server.I manually placed the file in Ready folder.The file gets processed but goes and sit in exception folder under structural folder.
I tried the same file using Import manager and and dot loaded in DM without any error.I checked all the fields and structure but unable to find the solution.
I am getting the following error showing some timestamp.There are no fields in may main table using timestamp .our design has only literal date and time in tuple.Is this something to do with this?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <File>
<ExceptionSubFolder>E:\usr\sap\MD1\MDS00\exe\Distributions\HYDHTC100401D_MSQL\Sachin\Inbound\MDM\MRH2_MAP_AUTO\Exception\StructuralX\</ExceptionSubFolder>
<Name>20110721084955_S_MRH2_Customer_Master_Data.xls</Name>
<ExceptionType>StructuralX</ExceptionType>
<TimeStamp>20110721084955_S</TimeStamp>
</File>
Can any one help me in this ?
Thanks and Regards
Nitin

Hi,
Thanks for the help.
I clicked on the below link.But please clarify which one to download from below.Which one from below contains xsd.exe
What is xsd.exe used for.Is it some kind of tool to create xml files.Please need some information.Because if it is a tool i am using Altova XML spy for the same
Download .NET Framework 2.0 SDK x86 version (354 MB)
Download .NET Framework 2.0 SP2 (52 MB )
Thanks and Regards
Nitin
Edited by: nitin shanbhag on Jul 25, 2011 5:23 AM

Value Exceptions - Import Map Update

Hello MDM Gurus,
We have the requirement to update the existing import map by unmapping two of the fields that we no longer required.
When we try unmapping the required fields and save as another map name, export, reimporting it and overwriting the existing map with the same name. But the problem is we are loosing all value mappings. we are facing issue getting loads of value exceptions as all value mappings are gone.
Please we need experts advices to resolve this since we no longer need that two fields getting imported in to the repository.
We need a solution to unmap that two fields and keep all existing value mappings.
Save Update not works for filed mappings, it only works for value mappings.
Thank you very much in advance for the suggestions and inputs.
Example :
Field1 and Field2 Unmapped, We saved the Map by Save -> we are loosing all value exceptions ( As it stores only present config)
Field1 and Field2 Unmapped, We saved the Map by Save Update -> When reimport the map again, we are seeing this field1 and field2 still mapped.
Field1 and Field2 Unmapped, We saved the map by Save As -> Still it does like First Scenario.
Please Advice.

Hi Smartsoft,
Just try this below procedure and revert with result.
1. Open the existing map.
2. Remove all the fields from matching field under Match Records tab.
3. Now unmap these two not required fields under Map Field/Value tab.
4. Afterwards, set again all the matching fields like earlier under Match records tab. Now make sure that under your Import Status tab Action Item: Ready to Import. Once it is done.
5. Now try with Save As option as a new map in order you have had existing correct map as a reference for future.
If it work properly then you can overwrite this new map name with existing map. Kindly revert.
Regards,
Mandeep Saini

Updating record with check out in Workflow by Import Server

Hi,
I have a Workflow starting with "Checkout". During the Workflow, a syndicate is executed, a WebService is called and the response is processed by Import Server.
The record is not updated because it's u201Ccheckoutedu201D.
The user that executes the Import Server is the Admin, which have all roles and the u201CAuto-Join checked out recordsu201D parameter is u201Cyesu201D.
Can I update a record with check out by Import Server? The MDM version is 5.5.64.71
Thank you,
Evandro

Lets start with this....
1. Auto-Join checkout records -->Yes ; should join the record which is already checkedout as well as in workflow.
2. Check the [owner] assigned to workflow record that might stop you to AUTO-JOIN this record to exisiting.
please feel free to revert.
thanks
Alexander

Help on import server

Hi friends,
please provide full configuration file for mds.ini(server), mdis.ini(import server) and
mdss.ini (syndication server)
[email protected]
Thank you
S Naidu
shankar

Hi Shankar,
You can refer the following format for the configurations:
_mds.ini_
[MDM Server]
XCS Ini Version=1
MDS Ini Version=1
Accelerator Dir=C:\Program Files\SAP MDM 5.5\Server\Accelerators
Lexicon Dir=C:\Program Files\SAP MDM 5.5\Server\Lexicons
Extra DBConnection Validation=False
Log SQL Errors=True
RELEASE\UseAssert=False
String Resource Dir=C:\Program Files\SAP MDM 5.5\Server\LangStrings\
Stemmer Install Dir=C:\Program Files\SAP MDM 5.5\Server
Log Dir=C:\PROGRA2\SAPMDM1.5\Server\Logs\
MDS Scone=
Autostart=0
Log Protocol Transactions=False
Modifications Dir=C:\PROGRA2\SAPMDM1.5\Server\Modifications\
Report Dir=C:\PROGRA2\SAPMDM1.5\Server\Reports\
Archive Dir=C:\PROGRA2\SAPMDM1.5\Server\Archives\
Distribution Root Dir=C:\PROGRA2\SAPMDM1.5\Server\Distributions\
CPU Count=1
SLD Registration=False
Log SQL Modifications=False
Maximum DBMS Bind Count=256
Max Initial MB to Retain=4
Max Send Failure MB to Retain=4
Oracle\Dll=OCI.DLL
Default Interface Language Code=eng
Default Interface Country Code=US
Allow Console to Retrieve Files=True
Oracle Tablespace Files=1
Oracle DBA Username=sapmdm
Oracle Best Block Size=2048
Client Ping Timeout Minutes=0
Inactive Client Timeout Minutes=30
Value Retrieval Threshold=0
TrexDllPath=
LOG_REC_MATCH_PERF=0
LOG_IMPORT_RECS_PERF=0
Import Slice Size=2048
Allow Console to Delete Files=True
Protect Family Nodes With Locked Data=False
BULK_IMPORT_SILO_LEVEL=3
Disable Log Retrieval=False
Max Large Text Length=50000
Number of Rows Per Fetch=100
Logged-In Role Maintenance=True
DBMS Reconnection Attempts=10
Workflow Detailed Report=False
[MDM Server\Databases\CUSTOMERMDVORCL_15_3_4_3]
Port=3249
Login=sapmdm
Password+=19TL68AMP7LARMAHS9QLUB2QV3
Block Ports On Structural Exceptions=True
Valid Keyword Chars=abcdefghijklmnopqrstuvwxyz0123456789
Mail Server=
mdis.ini
[GLOBAL]
Version=5540
Interval=60
Server=Hostname
Verbose=0x0000
String Resource Dir=C:\PROGRA2\SAPMDM1.5\IMPORT~1\LangStrings\
Log Dir=C:\PROGRA2\SAPMDM1.5\IMPORT~1\Logs
SLD Registration=False
[CUSTOMERMDVORCL_15_3_4_3]
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
Login=mdis
Password=import
Log Protocol Transactions=False
Inter-Chunk Delay MS=10000
mdss.ini
[GLOBAL]
MDM Server Name=hostname
Auto Syndication Task Enabled=True
Auto Syndication Task Delay (seconds)=10
Default Interface Language Code=eng
Default Interface Country Code=US
String Resource Dir=C:\Program Files\SAP MDM 5.5\Syndication Server\LangStrings\
Log Dir=C:\Program Files\SAP MDM 5.5\Syndication Server\Logs
SLD Registration=False
[CUSTOMERMDVORCL_15_3_4_3]
User=Admin
Password=PWD
These all are there if you have only one repository "CUSTOMER" on your server. Make the entries for each repository following this customer and the [Global] wntries will appear only once.
Hope this is helpful to you.
Regards,
Dheeraj.

Differ between import manager and import server

Hi to all,
Can any one explain difference between import server and import manager and how the data will be imported to the same.
Regards
MM

Hi reddy,
Can any one explain difference between import server and import manager and how the data will be imported to the same
Please follow the text below, which has been taken from the help.sap.com
Both MDIS and the MDM Import Manager can import data from a source file into an MDM repository. However, each has unique capabilities that distinguish it from the other. When each is used to its advantage, the result is an import strategy which provides the most efficient importing of data possible.
The strength of the Import Manager is its connection to the source data, which enables its interactive map-making capabilities. When the Import Manager connects to a source it preloads the entire source file, giving it knowledge of every field and every value in the source data. This u201Ctotal awarenessu201D is crucial for preparing a complete import map. To help ensure a map is complete, the Import Manageru2019s Import Status tab alerts users to any discrepancies between source data values and the current map. The user can fix these problems interactively within the Import Manager and save the corrected map before any data is imported.
Preloading an entire source file comes at a price, however. It consumes memory on the computer running the Import Manager and very large source files may exhaust the computeru2019s available memory.
By contrast, MDISu2019s strengths are its scalability and automation.
For scalability, instead of preloading the entire source file into the host machineu2019s memory as the Import Manager does, MDIS processes records in a stream by loading a record at a time into memory.
This streaming technique enables MDIS to process much larger source files than the Import Manager, as the demand for memory on the host machine is not affected by the size of the import file.
In addition to file size, file quantity poses a second scalability challenge. For example, a real-time transactional environment may produce a staggering number of files, each containing only one or two records. To import these files individually through Import Manager would be extremely inefficient. MDIS tackles this problem with a file aggregation feature that processes files systematically in batches rather than as individual files, resulting in faster, more efficient import of data.
As it relates to automation, MDIS requires no user intervention to import files to an MDM repository. Instead, it relies on maps created previously within the Import Manager. Once an import file is placed in the appropriate folder, its data is imported automatically into the MDM repository using the rules of the pre-defined import map. Once a file is processed, MDIS scans the repository for the next file to import. This process continues 24 hours a day, seven days a week, until either MDIS or MDM Server are stopped.
The trade-off for this scalability and automation is that if discrepancies between the source data and the import map arise, MDIS cannot u201Cfixu201D these problems by itself. Instead, the u201Cproblem casesu201D can be fixed manually at a later time using the interactive capabilities of the Import Manager. Unlike the Import Manager, however, MDIS can set aside problem records or files and continue importing.
These conceptual and operational differences between the Import Manager and MDIS are summarized in the table below.
Item
Import Manager
MDIS
Source file location
Anywhere
Automatic inbound port
Import process
Interactive
Automatic
Import map state
Editable
Read-only
Object loaded in memory
Entire import file
Individual records
Streaming import support
No
Yes
File aggregation support
No
Yes
Maximum import file size
Limited (50,000 records)
Unlimited
Status location
Import Status Tab
MDM Console/Report file
Error correction prior to import
Yes
No
Exception handling during import
No
Yes
For additional info, kindly refer the link below:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
GO to-> MDM import Server
Hope it helps.
Thanks and Regards
Nitin Jain

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

Problem with import server automation(MDIS)...........

When i am importing the delimiter text data file manually with import manager(by both port method & delimiter file), 1116 records are getting imported, but when i do import server automation with same file & Map only 130 records are getting imported in to repository.
Details of server.
SAP MDM 7.1.04.122 (SP4)
Observations
1. In sap MDM console when i see port details, the status of port is : HAS exception.
2. In Exception folder log is created in ImportX subfolder.
3.in log folder, in files i could see most of lines as
<Failure ts="2010/04/01 12:43:26.084 GMT" tid="4184" entry-no="39" operation="Import" import-action="Create" row="1">One or more field values are invalid</Failure>
Did anyone faced the similar issue, or did i do any mistake or missed any step...

Hi Srinivas,
As you said that status of your import Exception is Empty once you delete all the records from Exception folders.
But when you again import records through MDIS all records are not getting imported. right?
I feel that it could be also possible that saved map which you are using into Port may have missed field/values.
So, I would suggest please go for this step by step and let me know if you face any issue.
1st step: Open this file using Import manager Type = Delimited text, select your Remote System and Delimiter as per your requirement. Map all your Fields and Values. Make sure that all your desired fields and their values are mapped correctly.
Now in the last come to import status and check that Action items: Ready to import . Don't import records here but save this map File-->Save As->Give Map name say MAP1 and then close your import manager.
2nd Step: Put this file into Ready folder and make sure that you MDIS services is stopped so that you can open this same file using MDM Import Manager Type = Port and select you required Remote system which you defined in MDM Console while defining Port and make sure that this port in console also contain the same map MAP1. Also make sure that you put same Delimiter Correctly in port as you put during mdm import manager.
check the status of Import into Import status Tab as Action items: Ready to import or not. It should have Action Items: Ready to import if not then map the missing values/fields and then Go to File-->Save.
Now Run your MDIS Services, and put this same file into your ready folder. This should import all of your records into MDM and i feel this will solve your Problem with MDIS.
Revert with result.
Regards,
Mandeep Saini

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 not picking up the file

Hello,
I have 2 repositories running on the same server. Import server picks up file for one repository, but not for the other. What could be the reason? Also, for the repository, import server not picking up the file, workflow also does not send an email notification.
Please help
Subhash

Hi Subhash,
Hope you are not using the same Import Server for both the MDM Servers. If yes then you need to mention the MDM Sevrer name in the MDM Server parameter of MDIS.ini. Check the parameter list of MDIS.ini file.
If your repository has password for Admin user then you need to specify the same in MDIS.ini file under your repository section for User = Admin and Passowrd = [Admin password]. Remove the E from the PAsswordE and give the password for Admin user. Once done restart the Import Server and check again, parameter Password would have converted to PasswordE.
For Email Notification two things you need to check:
1. You should have specified the mail server address in MDS.ini file under your repository section for parameter Mail Server.
2. Workflow owner should have entry in Email address field of the user. Check this in Console under Admin -> Users.
Regards,
Jitesh Talreja

Import Server - Workflow related value exceptions

Similar Messages

Maybe you are looking for