MDM 7.1 SP4 - do not show "inactive" records in look up tables

[Former Member]

Hi,

We've got requirement from customer to have for each record in Look up tables two additional fields "activation date" and "expiration date". As soon as business user in Data Manager set "expiration date" equal to value in the past we shoudn't show this record for business users anymore (only Admin user should be able to see all the records).

It is quite easy to implement this requirement for MAIN table using restriction by role + Named Search. At the moment we didn't find easy solution to do the same for "simple" look up table. Could you advice us something?

Thank you in advance,

Dzmitry

[Former Member · Accepted solution]

Hi,

The initial requirements not to show values in Look Up for business users where expiration date set in the past.

Could you explain your idea about several main tables and remote keys, because if we use several main tables we are not able to see values in import manager (we see only from one table),

Dzmitry

[Former Member · Accepted solution]

Hi,

General Restriction

MDM Import Manager is able to import data for a single main table only. It is not possible to create an Import Map that targets two different main tables in one import run. There is a stricit 1:1 relation between an Import Map and its destination table.

Import of Lookup Main Fields

Nevertheless it is possible to import data for fields that are actually lookup fields to either the same or a different main table of the repository.

Please go thru this link it will give you good idea about using Multiple Main tables. http://wiki.sdn.sap.com/wiki/display/SAPMDM/MultipleMainTablesandImport+Manager

Also read more about multiple main tables in the MDM Console Reference guide - pg 66 - http://help.sap.com/saphelp_mdm71/helpdata/en/4b/71608566ae3260e10000000a42189b/MDMConsole71.pdf

Thanks,

Shambhu.

[Former Member]

Hi,

Is the reuirement not to show the lookup values or is it that user should not be able to attach the inactive values to main table?

If its that user should not be able to attach the inactive values, you can think of configuring automatic validations in MDM.

Validation will fail if user has selected wrong / inactive value.

If you go by Main table solution, you will need to maintain remote keys for all the records to be able to perform the value mapping through import manager.

Hope this helps.

Best Regards,

Amol.

[Former Member]

Hi Konsta,

Yes, we thought about this (to make all the required tables as MAIn) but in this case import (data migration) procedure become inconvinient because you are not able to see in import manager entries of one main table from another.

Dzmitry

[Former Member]

Hello Dzmitry

For import/syndication you can use common tuple for both your main tables

Regards

Kanstantsin Chernichenka

[Former Member]

Hello Dzmitry

You can use another one main table instead your LUT

In that case you can use Named Searches

Regards

Kanstantsin Chernichenka