Data of FI, SRM and R3 in MDM

Question

hi!
here's my question;
what information should i take for the three systems?
what happen if i create the mdm schema with all the fields, and tables that are used in FI, SRM and R3 and create a big repository with one main table of products, and a big subtable of suppliers?
the performance will be affected?
is there any documentation that explains how many subtables you can use?  or what to do in this cases?
thanx

Answer 1

In general this is not a good idea.  There are several reasons for this:
First is performance.  In order to mimic the complexity of the ERP data models, you would have to incorporate a large number of qualified lookup tables.  The more complex relationships you have in your MDM data model, the worse the performance will get.  MDM has to index all of the attributes you configure (for keyword or sorting) in the data model which has a hit on the memory of the server.  Additionally, your Import and Syndication Servers are going to choke if you have a large attribute set.
Next, in SAP there are some tables that have a matrix of lookup values.  For example, sales office field in the sales area is dependant upon a configuration which is a combination of sales area plus other things.  So you have the following affect:
x [ 1, 2, 3]
y [ 4, 5, 6]
z [ 7, 8, 9]
If I select X, I want 1,2, and 3 to be available to me.  If I select X and Y, then I want 1, 2, 3, 4, 5, and 6 to be available to me.  This sort of complexity is very difficult to rebuild into MDM. 
Third, there are some attribute sets in ECC which have proven to be incredibly difficult to build into MDM for technical reasons.  For example, Partner Functions. 
You want to design your data model to be restricted to enterprise level attributes (if possible).  This gives a more global view of the entire landscape.