SRM-MDM Catalog: Problem with Automatic Import of Catalog Data

[former_member273752]

Dear All,

We are working on a SRM-MDM Catalog scenario involving SRM 7.0, MDM 7.0 and PI 7.0. Our scenario includes distributing Supplier and Catalog Items information from SRM to MDM (via PI) and to use this SRM-MDM Catalog in SRM Portal. We are using the standard repository and the standard import maps. Problem is, whenever we send some Catalog data from SRM (via transaction BBP_CCM_TRANSFER), we could see that the data is being put to MDM Port, but from therein it fails to update MDM. Everytime it gets into a structural or value exception, specifically with target field 'MSS Hierarchy Price'. We are not sure whether we need to actually edit the standard import map, and customize some mappings. Is this the way it is done? Also, how could we ensure that the source values coming in from SRM are mapped correctly to the target values (Like product groups)? We have already transferred the basic configurations like currencies, regions, product groups to MDM, by running transaction MDMGX in SRM; still we get value exceptions on currencies and product groups quite often. What is the strategy to mitigate these kind of error? Any help will be appreciated.

Thanks and Regards,

Sid

[former_member273752]

Problem Solved!

[Former Member]

Hi Siddhartha,

We are not sure whether we need to actually edit the standard import map, and customize some mappings. Is this the way it is done? There is sometime need to change Standard Import Map, there is no harm in it, on a safer side when you edit the standard map, save it with a new name and then assign this new name to Port. In this way you will have your standard map with you for reference also.

We have already transferred the basic configurations like currencies, regions, product groups to MDM, by running transaction MDMGX in SRM; still we get value exceptions on currencies and product groups quite often.

These exceptions occur when your main table source file comes with new values for currency, Product groups etc which does not exist in your MDM look-up tables Currencies and Product groups. So open the map for which you are getting these exceptions in Import Manager, Go to Configuration options--> For Default MDIS Handling, Automatic Unmapped values = Yes and

Unmapped Value Handling = Add. Set these properties in your Configuration options and make sure that you save it in your Import MAP. So now even if these values does not exist in MDM, files will easily imported through import server (MDIS)

Regards,

Mandeep Saini

[former_member205403]

Hi,

Solution was well explained by Mandeep. I would also like you to check the MDM logs to find more details about the exception. i.e. why exception is happening and provide correction according..

Please revert with the result.

Regards,

Shiv

[former_member273752]

Dear All,

Thank you all for the all the guidelines and points mentioned. We have resolved the problem by manually adjusting the Import map to include the product groups and currency codes from our SRM system. Later we realized that actually the configuration import using MDMGX had not happened properly the first time (Not sure why). The configuration values were showing in Data Manager, but the key field mappings for the SRM system was missing. Re-importing the configuration added the key field mappings, and from then on the automatic import is working. Thank you all once again; rewarded the contributions.

Thanks and Sincere Regards,

Sid

P.S: Above all, a Big Thanks to SDN!!

[Former Member]

Hello Sid

Data from SRM sent to MDM as file

That file you can found in MDM "....inbound eady" directory

You can get that file and check it ( if all sent data(in file) is OK going to next step)

Mdm used Import Server for load data from received source file automatically

if during the import it got exception - source file removed from "ready" to "exception" directory

You can fix error manually, for that do next:

load Import manager and select next parameters:

type: Port

Remote system: SRM(or something like that)

Port: (your inbound port- where your source file placed)

in Import manager you can test how work our map and fix some errors and load data from source manually

Aftet fixing you can save new map or save new map by another name and reconfigure inbound port

Some links:

and

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/601d4fee-719f-2910-4f86-fa030ab07358

Regards

Kanstantsin Chernichenka

Edited by: Kanstantsin Chernichenka on May 27, 2010 12:57 AM

[former_member273752]

Thanks Kanstantsin, for the explanation and the links above. We have already done the setup mentioned by you, now will try editing the map file and update this thread of conversation.

Thanks and Sincere Regards,

Sid