Mapping to two display fields for supplier table

[Former Member]

Dear Experts,

I have want to show supplier ID and supplier name on UI screen so I’m made both the fields in supplier table as display fields and it worked.

But when I did this, the data (info record) is not passing and it is falling due structural exception.

The reason is source supplier ID is not able to map with destination supplier ID as there are two display fields

So my requirement is how to map source supplier ID to destination supplier table (supplier ID and Supplier name).

Regards

Subhash

[Former Member]

Hi Subash,

When you multiple fields as DF then the same which was for single DF would not work.So the results are obvious.

This can have many solutions -

1.Refer to Import Manager reference guide on importing lookups with Multiple DF.Basically map the lookup fields Supplier Id and Supplier name with individual source fields.Post that create a compound field.This will automap to header.

2.Use Partitioning to prepare a field which has concatanated value of the 2 display fields and map to header field.

3.Do this transformation in PI so that it sends the value as expected by MDM.

4.Create a master source file with all values,map values and do a save update.

5.Use remote key to your advantage by making source value as per relevant remote key value.

Thanks,

Ravi

[Former Member]

Hi Ravi

Thank you for your response

Actually when I send info record data from ECC to MDM it contains only supplier # so in the source “supplier ID” and at destination due to display of two fields in supplier table it is combined in to one field “Supplier” and when I’m mapping to supplier ID it is not mapping.

See the screen shots

[Former Member]

Hi Subhash,

Although you have many options here trys this - Maintain Remote Keys of Lookup Supplier.

Once you have maintained remote key,map the header of lookup field with Supplier id.

Please see the example in which i have 2 display fields Country Code and Region Code.I have created a concatanated field with Countrycode and Region code.So if MDM has a source file with value NZWLG it will map to Region WLG in Country NZ based on the remote key I have maintained.

In your case remote key can be Supplier id itself and mapping should be done at header level.

Please come back with findings.

Thanks,

Ravi

[Former Member]

Hi Subhash,

Kindly close/update the thread.

Thanks,

Ravi

[Former Member]

Hi Ravi,

Sorry for the delay response actually I have changed company and due to this I’m unable to Login with existing user id.

The issue is I have remote key configured for supplier but the thing is supplier data is coming from SRM and remote key is updated with “SRM” and When supplier and other details (Info record update) coming from ECC all the values are not mapping for supplier due to different remote key and I could not load the data.

Regards

Subhash

[Former Member]

Hi Subash,

That is fine,I too faced that issue with user id

As I understand that you have different remote systems ECC and SRM,and the data coming from ECC is different to taht coming from SRM.Well in this case you will have to maintain 2 entries of remote keys,one for SRM and one for ECC.Maintain appropriate values in the keys,and test.

Thanks,

Ravi

[Former Member]

Hi Subhash,

• As communicated by Ravi, there are many options.
• But problem is that you have made Supplier Name as display field along with Supplier ID.
• So now system would need a data in the form of "Supplier ID, Supplier Name" in order to do auto-mapping od values, otherwise it will go into structural exception. This is the case happening with you.
• Now if you have supplier name in your source file(coming from ECC) then you can create a Partitioned field using that and then map that partitioned field to Supplier ID [DF] and it would solve the problem.
• Or you can map supplier ID and supplier name individually and then create compound field which will be automatically mapped to Supplier ID [DF].

Or the other option would be to simply set Diplay Field property to NO for supplier name and implement the display feature for this field separately on the Web UI(by doing additional coding).

Please check this and let us know if this is feasible for you.

Thanks and Regards,

Ankush

[Former Member]

Hi Ravi,

I am able to get the solution. The way I have achieved is, I have used MDMGX to send the supplier no and supplier name from ECC. So that in the MDM there will be two remote keys “ECC” and “SRM” for the same record.

I this way I’m able to load info record data from ECC and central contract data from SRM in to MDM automatically.

Regards

Subhash

[Former Member]

Hi Subhash,

Thanks for updating.Kindly close the thread.

Thanks,

Ravi

[former_member190061]

Hello Subhash,

As ar as I know mapping will not depends on How many Display fields you have, you can map it even for "N" number of DF's.

Now I hope you have automated the Import, and its failing because of structural exception means, kindly check the headers in your source against the predefined map you have saved in Console under Port.

Another possible scenario- Kindly remove Unique field selected under Match Records(If the Mapping option is disabled) and try to map the required field against the destination.

Kindly revert ...

Regards,

Girish