MDM Data model design for Main table visa vis lookup table

Hi ,
I would like to know whether the legal entities or Address table which are common for all MDM main tables like Customer ,Vendor,Material,Business Partner etc can also become a main table when their attributes are around 30-40 range.
Is it a sound design approach to make Company table with about 50 attributes and say address table with 20 attributes as Main table and replicate a small company-id table with 2 or 3 attributes to link to the main table(company)? This will ensure replicating that small table(company-id) to all other Main tables(customer,vendor,......) instead of replicating that big company table as lookup for all main tables?
Thanks in advance for any idea or feasibility comments.
-reo

Hi, Deepak
>>> - How can I populate the data in the lookup table at the same time when I am populating the main table ? I have only the XML's that correspond to the main table . I don't have seperate data for the lookup tables .
I don't think you can populate both main table and all fields of lookup tables at the same time, i.e. using same map. You can consider 2 options to upload all information you have:
1) If your XML file contains data you would like to upload to lookup tables, you can upload it to MDM lookup tables with several maps using same XML and choosing different sections of that XML corresponding to different MDM lookup tables.
2) Also you can upload main table simultaneously with lookup table entries (using same map), but in this case new lookup table entries will only contain display field values that you mapped. To do this you should use 'Add' value mapping functionality for fields that you mapped to lookup tables.
>>>- Can I use the standard maps available for import in the business content of material repository in MDM ?
1) In case you have material master repository delivered by SAP and you use XML files which structure corresponds to SAP predelivered XSD schemas then you can use these maps undoubtedly.
2) If your repository is based on SAP predelivered, but you changed it ,you should adjust these maps due to differences in repository structure and XML files structure.
3) If you created your repository from scratch you should consider option of making your own import maps.
Regards,
Vadim Kalabin

Similar Messages

Trouble saving Data Modeler design 4.0EA3

Hello,
I'm having trouble saving a Data Modeler design. I can create and import tables into a physical model; however, when i save the model (File > Data Modeler > Save) it doesn't appear to be saved correctly since the resulting .dmd file is 0 bytes. If i close the design and reopen it, none of the tables that i created appear.
I'm using version SQL Developer Version 4.0.0.13.30 on Windows 7.
Thanks,
Pete

i don't see any recent errors in the datamodeler.log file. the only entries for the last 2 days are:
2013-11-12 11:04:52,116 [AWT-EventQueue-0] INFO DataModelerAddin - Oracle SQL Developer Data Modeler 4.0.0.825
2013-11-12 11:15:12,672 [AWT-EventQueue-0] INFO DataModelerAddin - Oracle SQL Developer Data Modeler 4.0.0.825
2013-11-12 11:26:59,517 [AWT-EventQueue-0] INFO DataModelerAddin - Oracle SQL Developer Data Modeler 4.0.0.825
2013-11-12 16:54:18,313 [AWT-EventQueue-0] INFO DataModelerAddin - Oracle SQL Developer Data Modeler 4.0.0.825
2013-11-13 10:44:03,694 [AWT-EventQueue-0] INFO DataModelerAddin - Oracle SQL Developer Data Modeler 4.0.0.825
2013-11-13 10:49:26,093 [AWT-EventQueue-0] INFO DataModelerAddin - Oracle SQL Developer Data Modeler 4.0.0.825
2013-11-13 11:08:11,679 [AWT-EventQueue-0] INFO DataModelerAddin - Oracle SQL Developer Data Modeler 4.0.0.825
if run sqldeveloper\sqldeveloper\bin\sqldeveloper.exe, the only message in the console is:
LOAD TIME : 205
no other messages.
I have 3 different builds of sql developer 4.x - they all have this problem. My 3.2 build does not have this problem. So, next, i installed the Data Modeler standalone version (4.0.0.825) and created a physical model with just one table - and i was able to save it! The .dmd had the following content (not 0 byte):
<?xml version = '1.0' encoding = 'UTF-8'?>
<OSDM_Design class="oracle.dbtools.crest.model.design.Design" name="test_dm_only" id="986F3685-3223-BAF6-8D69-6C2C4C52718E" version="3.5">
<createdBy>HillsP01</createdBy>
<createdTime>2013-11-13 16:36:18 UTC</createdTime>
<ownerDesignName>test_dm_only</ownerDesignName>
<capitalNames>false</capitalNames>
<designId>986F3685-3223-BAF6-8D69-6C2C4C52718E</designId>
</OSDM_Design>
So, looks like the Data Modeler works, but there's a problem with my installation with the full SQL Developer product. One thing that i noticed is that my full SQL Developer install does not have a full list of logical types. I had to manual create a the ones that i use. In the Data Modeler only install, all of the logical types were available out of the box.

Performance impacts of attributes versus entities in data model design

I'm trying to understand the performance implications of two possible data model designs.
Here's my entity structure:
global > the person > the account > the option
Typically at runtime I instantiate one person, one account, and five option 's.
There are various amounts determined by the person's age that need to be assigned to the correct option.
Here are my two designs:
Design one
attributes on the person entity:
the person's age
the person's option 1 amount
the person's option 2 amount
the person's option 3 amount
the person's option 4 amount
the person's option 5 amount
attributes on the option endity:
the option's amount
supporting rule table:
the option's amount =
the person's option 1 amount if the option is number 1
the person's option 2 amount if the option is number 2
the person's option 3 amount if the option is number 3
the person's option 4 amount if the option is number 4
the person's option 5 amount if the option is number 5
Design two
attributes on the person entity:
the person's age
attributes on the option entity:
the option's amount
the option's option 1 amount
the option's option 2 amount
the option's option 3 amount
the option's option 4 amount
the option's option 5 amount
supporting rule table:
the option's amount =
the option's option 1 amount if the option is number 1
the option's option 2 amount if the option is number 2
the option's option 3 amount if the option is number 3
the option's option 4 amount if the option is number 4
the option's option 5 amount if the option is number 5
Given the two designs, I can see what looks like an advantage for Design one in that at runtime you have less attributes (6 on the one pension member + 1 on each of 5 options =11) than Design two (1 on the one pension member + 6 on each of 5 options = 31), but I'm not sure. An advantage for Design two might be that the algorithm has to do less traversing of the entity structure: the supporting rule table finds everything for the option's amount on the option.
Either way there is a rule table to determine the amounts:
Design one
the person's option 1 amount =
2 if the person's age = 10
5 if the person's age = 11
7 if the person's age = 12, etc.
Design two
the option's option 1 amount =
2 if the person's age = 10
5 if the person's age = 11
7 if the person's age = 12, etc.
Here it looks like the rulebase would have to do more traversing of the entity structure for Design two.
Which design is going to have better performance with a large amount of rules, or would it make a difference at all?

Hi!
In our experience you only need to think about things like this if you were dealing with 100s or 1000s of instances (typically via ODS). As you have a very low number, the differences will be negligible, and you should (usually) go with the solution which is the most similar to the source material or the business user's understanding. I also assume this is an OWD project? Which can be even better, since the inferencing is done incrementally when new data is added to the rulebase, rather than in one "big bang" like ODS.
It looks like design 1 is the simplest to understand and explain. I'm just wondering why you need the option entity at all, since it seems like a to-one relationship? So the person can only have one option 1 amount, one option 2 amount etc, and there are only ever going to be (up to) 5 options...is that assumption correct? If so, you could just keep these as attributes on the person level without the need for instances. If there are other requirements for an option instance then of course, use them, but given the information here, the option entity doesnt seem to be needed. That would be the fastest of all :-)
Either way, as the number of instances is so low, you should have nothing to worry about in terms of performance.
Hope this helps! Write back if you have any more info / questions.
Cheers,
Ben

Architeture influence MDM Data Modeling??

Hi,
I understand If I have MDM SP05 then I can utilize some good functionalities of EP, Java Webdynpro or SAP NW CE, Webservices and BPM. and If same applications I integrate with MDM SP03 then I will loose this functionalities. Will this have any impact / influence on my Data Model designing decisions. What will be the change?
Cheers,
Rajesh

Hi Rajesh,
I don't think you have to think from that perspective. When you say Data Modelling - it is related to repository structure i.e. fields and tables.
Scenario 1 - You don't have any information about upcoming version
In this case since you have no idea what new version would consists of hence there is no point in thinking about data modelling. You can go ahead with the most optimized model based on your current requirements
Scenario 2 - You have some idea about the new features of the new version
Still I don't think you need to consider data modelling because new features might be in the form of new java classes or new iViews or may be introduction of new data type, etc. In all cases you cannot change your current data model.
It's always better to have POC and Live on same version so that things can be reused.
I have just shared my views and didn't provide any solution
Regards,
Jitesh

SAP BW SRM Workflow data model design

Hi All,
I have a requirement from my client to design SAP BW SRM Work flow report, in output user is interested for document flow/chain starting from Shopping cart (SC) - Bid invitation (RFx) - Bid (RFx responses) - Purchase order (PO) - Confirmation. There are standard datasources and DSO's for the same but I want to check experts ideas on data model design. I am thinking to build infosets on top of DSO's but it will impact Query performance as data volume for sure will be more and will increase down the line. In addition I need to consider below exceptions or restrictions as well:
1. Document may/may not start with SC for example one possibility is document start at SC and end at Confirmation or start at RFx and end at PO etc.
2. User is expected to see below various possibilities of document chain in report output:
SC - RFx - RFx responses - PO - Confirmation or
SC - RFx - RFx responses or
SC - PO - Confirmation or
SC - RFx - RFx responses - PO
SC - RFx or
RFx - RFx responses or
RFx or
RFx - RFx responses - PO or
RFx - RFx responses - PO - Confir or
PO - Confiramtion or
PO
your help and ideas on this is greatly appreciated
Thanks and Regards,
Reddy

Hi All,
Any inputs or ideas on the data model design? Thanks for your help in advance
Regards,
Reddy

How to save data model design in pdf or any format..?

how to save data model design in pdf or any format..?
i ve created design but not able to save it any mage or pdf format

File -> Print Diagram -> To PDF File

Data modeling dilemma for EAV oriented problems in Data Modeler

Hello,
Dealing with EAV( entity attribute value model ) oriented structure of data.
So this look like this:
Entity( Entity_Id number , Entity_Name varchar2, Entity_Desc varchar2 )
Entity that list attributes and some meta data on characteristics of attributes:
Type_Of_Attribute( Attr_Id varchar2, Type_Of_Value TOV_Domain, Unit_Of_Value varchar2 , Min_Value variant_type , Max_Value variant_Type )
Then we have actual data. Entity is described with set of attributes and their values. So aditionally to attributes on row form in Entity there are aditional attrbutes in columnar form.
Because of sparsity...
However there in columnar form the challenge or issue is type of values so domains of attributes.
For example:
weight_of_ person is number between min_number and max_number.
But another parameter for example mood_of_person is string from the domain which consists of set of strings/descpriptions.
Another possibility could be reference to some table of values ( key value ) that could be modelled as one:many relationship if put in entity Entity on row form of attributes.
But since this is attribute relate only to few intances or it is very dispersed....and for preserving table form..it was put in columnar form ..
Attribute_Of_Entity( Entity_Id, Attr_Id, value,
-- when not normalized, could be add also unit like kg or lbs or inch or piece ).
My question is on good/succesfull practice of modelling for VALUE in attribute_of_entity?
Somewhere read that some databases have feature of so-called variant type.
Guess the objective is to modell in such a way that implementation of this model is as easy as possbile in
issues like:
a) validating column oriented form during entering or updating values
b) consolidating queries when reporting
c) agregating data when grouping when grouping data and preventing non-comparable data.
So to implement value as structure/complex_type with methods or there is any other feature supporting variabilty of the data along same column in the table. So logical design that would not cause too much complexity in the relational design and table implementation and procedures are handled as much as possible on the database level?
Thank you in advance for comments, experiences, suggestions,

Hello,
EAV is rarely a good solution. Tell us about your business problem and we might be able to show you solutions that are performant/easier to maintain/...
https://www.simple-talk.com/opinion/opinion-pieces/bad-carma/
Regards
Marcus
BTW: this question should not be asked in the forum space for the tool SQL Data Modeler. Instead ask in SQL and PL/SQL or General Database Discussions

Data Modeler design rules warning

When I apply the design rules to the relationel model Data Modeler warns me about both Primary keys and Foreign keys "with wrong naming standards is not recommended".
However, I have designed the naming rules in the Tools => General Options => Naming Standard => Templates section for example like this: Primary Key: PK_{table abbr}_{column abbr} or like this {table abbr}_{column abbr}_PK and defined table and column abbreviations. Data modeler warns about either form, and since only recommended naming rules exists I do not understand the warning.

The warning is shown if you deviate/rename the constraints from what is set in the templates, so having selected abbr from the variable list you should not be seeing the warning. We extended the variables to include the abbreviation and it looks like these have not been included in the validation. I have logged a bug to track that.
Sue

SQL Developer - Data Modeler - Trigger for FK arc constraints

In the preferences there is an option "Data Modeler > DDL > Create Triggers for FK arc constraints". I think Oracle recomments to use constraints instead of triggers where it is possible. Can anyone from the Development team tell me why here is just the option to create triggers and not also the option to create table level constraints for FK arc constraints? If it is possible I'd like to have this option. My suggetion is to use the following check constraint construction for creation: nvl2(FK_IDx,1,0)+nvl2(FK_IDy,1,0)+...+nvl2(FK_IDz,1,0)=1 or with not only single FK columns: nvl2(FK_IDx1,1,0)+nvl2(FK_IDx2,1,0)+nvl2(FK_IDy,2,0)+...+nvl2(FK_IDz,2,0)=2. Please tell me if that would be possible (and maybe available in next Version) or why it is better to user triggers instead.
Thanks
/c

The Data Modeler forum is at:
SQL Developer Data Modeler

Data Model Design

Hi Experts,
In Current project I need to design data model and create data flow strategy for SD,MM,PP,FI modules from R/3.The client wants to use BOBJ on top of BI Info cubes/Reports.Based on KPI's given I need to do Data availability in R/3,Data extraction,Data model analysis and submit the documentation for that.Please guide me how to approach step by step so that I can go ahead with clear cut strategy.Any documentation if it is there please share with me.
Regards
Prasad

You can find ASAP methodology and accelleretors related to modelling data here
https://websmp203.sap-ag.de/roadmaps
see the "ASAP Implementation Roadmap for SAP Exchange Infrastructure" there are New roadmap content for SAP Business Intelligence.
Regards,
Sergio

Data model design in SAP BI

Hi All,
I have one requirement to design the data model for BI. How to design a dataflow in BI. I know dataflow is different from data model. Could you pls let me know hoe to design it.
Is there any model available ...so that i can refer. if not let me know clearly what is a datamodel and how to design it.
Thanks,
Jack

Example of data flow:
http://wiki.sdn.sap.com/wiki/download/attachments/44794331/a6.gif
Data model:
http://wiki.sdn.sap.com/wiki/download/attachments/36064/5.JPG

How to upgrade Data Modeler design to new version when using subversion?

Hi,
I just installed Data Modeler 3.1 product version and I'm using subversion. When I open a design which I have modified with earlier 3.1EA3 version, I get the message " This design is in old format You should use "Save as... from file menu ...
Is there other more smart way to upgrade to new version than "save as" ? I remember having problems in earlier versions with this also. Am I supposed to save the design with different name or...? Or what is the best way?

Hi ,
I have updated the model to 3.1 version with subversion and I have to say that is quite hard for me,
I have "save as" with other name in other folder and after I have dropped from SVN my current folder and copy the new files to new folder in SVN and add the files to SVN,
I hope that I should not do this workaround too many times in future,
maybe if we save the model below a folder with the version number of the tool will help us but I don't like this option,
I guess someone could help us with a simpler solution than mine,
Regards

HR BW Data Model - Design & Delta Possibility

Dear All,
In our SAP BW HR Implementation - we have to do a full load everyday for PA, OM, TA, PY streams. and it is very time consuming.
fyi - we are using generic extractors.
Questions -
1. We would like to know if it is possible to swtich to DELTA. If yes, how!
2. Also any idea on the data modelling part - Like best practice for HR Data Modelling- (we are following LSA).
Crux - is to get the data loaded in time frame from 6-8Hrs from 20+Hrs it is taking currently.
Regards,
Vinay

Hi Vinay,
Have u implemented Deltas to generic extractors ? if yes, can you please share your in puts.
As of now we would like to go for delta, but here are the challenges:
1) How to capture deletion records in ECC and update them to BI?
2) if you are extracting multiple times in day then how would you populate the TIMESTAMP in ECC as none of the info types have TIMESTAMP field

Data Model plugin for Flash Builder 4

Hello there!
I've just watched a video tut on Youtube (http://www.youtube.com/watch?v=U1aWeoTV63M) on how to work with Flash Bulder + LC Data Services and he mentions a plug-in to add this option (Data Model) to Flash Builder.
I looked around on Adobe's website and found two download links, both for Eclipse, with lots of jar files.
Sorry, I don't get it!
Please, where do I get the right plug-in file and how do I install it in Flash Builder?
Thank you!
Marcos

Same here. Modeler plugin for Helios, Eclipse 3.6, Flash Builder 4.5 would be great.

Project Server 2010 - create a custom enterprise project field for persons (no text, no lookup table...)

I want to create a custom enterprise project field and would like to use instead of for example a text attribute or a look-up table a field for employees (e.g. project manager) which are coming e.g. from the Active Directory. But when creating this custom
project field I cannot see such an option. What solution do you suggest as I want to avoid that everybody uses different names and spellings for e.g. the project manager and without having to fill the lookup table with all resources of the company.
Thank you so much for your help!

Hi,
Are you using Proejct Server 2007, 2010, 2013?
In case you're working with 2010 version, here is an excellent
blog about how to insert a resource picker in a PDP (project detail page).
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

MDM Data model design for Main table visa vis lookup table

Similar Messages

Maybe you are looking for