IBM Support

Null Considerations for External source ID in Hybrid MDM

Question & Answer


Question

We are using hybrid MDM. The column on CONTEQUIV allows nulls, the same column on MPI_MEMHEAD does not. Please explain whether this will be a problem?

Cause

The memidnum column in mpi_memhead stores source system primary identifier for member data and this is a non Nullable field. This table is used by virtual MDM.
The ADMIN_CLIENT_ID column in CONTEQUIV is used by physical MDM and uniquely identifies the primary key for the administrative source system. This field can be Null.

Answer

In hybrid MDM, data entry is done in virtual MDM and then is persisted over to the physical MDM. Nulls would be rejected by virtual and not during virtual to physical as the PMR says. Any null would not be allowed to be stored in virtual MDM and even if it was, that wouldn't cause a problem in physical MDM. Therefore contequiv allowing Null is not a problem.

[{"Product":{"code":"SSPVUA","label":"IBM InfoSphere Master Data Management Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Product Synonym

MDM;MDM SE;MDM AE;MDS;PME;Master Data Management;Master Data Management Standard Edition;Master Data Management Advanced Edition;Master Data Service;Initiate;Probabilistic Matching Engine

Document Information

Modified date:
16 June 2018

UID

swg22000128

Page Feedback