Data Modeler: Replicating common attributes across many entities

Hi,
I am designing a system with many entities (in hundreds) for an SaaS application. These entities all have some common attributes that should appear in all of them. At present my design has about 14 such common attributes which may be increased (or reduced) in future.
Is it possible to group these common attributes under a single umbrella identifier (Data Type?) and then using this identifier in all the entities such that whenever the structure of the identifier is altered all the entities are automatically updated?
The Structured Data Type might have worked if there was a capability to separate its constituent attributes into individual table columns (while generating relational/physical models) rather than being retained as an Object type.
For now I created a 'dummy' entity with all the common attributes which I then copy and rename to actual entities. The problem of course is that I will have to manually update all the entities if any of the common attributes is altered.
If this were possible, it will really make life very easy.
Thanks
PS: Maybe I should submit this as an enhancement request

Hi Chiedo,
no, it's not implemented. You can do that using transformation scripts - here is demo http://download.oracle.com/otn_hosted_doc/sqldev/EA1_UserDefinedDesignRules/EA1_UserDefinedDesignRules.html
There is script for tables, we can provide similar script for entities.
Philip

Similar Messages

New SQL Developer Data Modeler : name of attributes of foreign key

Hi,
with designer the name of column of foreign key was the " short name of entity/table master" + "_" + "the name of column attribute of the master table" .
Instead in the sql developer D.M. the system uses directly the name of the column/attribute of the master table and if the name exists in the slave table it uses a number to distinguish them .
So, if i have a table with short name gp and a primmary key id and a slave table with even a column id ,
with the D.M i'll have in the slave table a column named id2; in the designer instead the new column is gp_id .
Is possible to have the same behavior of designer even in the SQL Developer Data Modeler ?
Regards
Gianpaolo Giliberto

Hi Gianpaolo,
the columns of foreign keys are generated without the short name of master tablehow do you define that short name? Table and column have property "Abbreviation" - short name should be set there. You need also to set naming templates in "General Options>Naming Standard>Templates". Templates will be used when foreign key is created or you can apply them in Table dialog or for whole relational model using pop-up menu in the browser.
no foreign key index is generated on foreign key columns I assume, you want it for DDL generation only - this is controlled in "General Options>DDL"
Regards,
Philip

ADF custom binding for given service data model

hi
I have this business service that has a given data model. I would like to bind ADF Faces components to this data model.
two examples:
(1) The data model has a date attribute somewhere that holds the date of when something has been "checked"/"approved". The user interface should present this information as a regular checkbox.
(2) The data model has some attribute as "multilingual text". It is like a regular text attribute, but the text (data) has been translated. The user interface should present this information as a regular text input field, but depending on some "selected"/"current" language.
I looked at this example from Steve Muench about custom binding:
http://otn.oracle.com/products/jdev/tips/muench/custombinding/CustomAttrBindingClass.zip
I have found some "solution" to implement the kinds of custom binding I need:
http://verveja.footsteps.be/~verveja/files/oracle/CustomBindingStuff-v0.08.zip
(Check the README.txt file.)
I extend JUCtrlAttrsDef and JUCtrlAttrsBinding, introduce a ConversionProxyRule interface and added meta-data to the <x>PageDef.xml files.
JDeveloper shows warnings like these in the "Compiler - Log", but it all seems to work fine:
Warning(55,62): <Line 55, Column 62>: XML-24534: (Error) Element 'NamedData' not expected.- questions:
(1) Do I really need all this, have I missed some typical approach for this?
(2) How do I now that "extending" the binding this way, doesn't break in the next JDeveloper release?
(3) What alternatives are there to approach this kind of "binding requirements"?
many thanks
Jan Vervecken

(1) Is the simplest overall and the solution I myself would do, but given your comments....
(2) This would be the second easiest, but would involve some delegation, sure.
(3) Involves creating custom binding objects, which while possible, we don't have much documentation on that
JDeveloper shows warnings like these in the "Compiler - Log", but it all seems to work fine: Warning(55,62): <Line 55, Column 62>: XML-24534: (Error) Element 'NamedData' not expected.
This is an XMLSchema validation failure since the schema for the <attributeValues> element in that namespace does not allow <NamedData> children, only the <action> element does. You can extract all the schemas from the adfdt_common.jar file in the ./adfdt/lib directory to have a closer look at that.
- questions:
(1) Do I really need all this, have I missed some typical approach for this?
I mentioned a straightforward approach that in my opinion doesn't qualify as radically altering your data model, but I respect your opinion to see that differently of course. :-)
The approach I mentioned would be the typical approach for this case.
(2) How do I now that "extending" the binding this way, doesn't break in the next JDeveloper release?
There is no 100% guarantee other than the fact that we try our best not to perform breaking changes since keeping upward compatibility is something we've tried to do since the beginning.
(3) What alternatives are there to approach this kind of "binding requirements"?
We've discussed the three alternatives above that I can think of. This doesn't preclude others, but those are the first three we both thought of... I hope others chime in with some insights based on there experiences, too.

NWDS does not open Webdynpro Component's Data Modeler

Hi,
All of a sudden my kindly Tool does not open any of the Component's Data Modeler for Mapping attributes. It happened all of a sudden. I cleaned everything and reinstalled from a proper software.
If any one has a solution kindly let me know or if you can direct me to appropriate forum or Weblog to recover it will be a great help.
-Shekhar

HI Shekher...
May be following link will helpful to u...U see some basic tutorial in this link that will help u abt webDynPro.....
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d
Also I m Giving U some Basic IDEA abt Data-Modular.
Data Modeler
Features
The Data Modeler is a graphical tool and part of the range of Web Dynpro tools. Using the Data Modeler provides you with efficient support for a number of central development tasks.
·        Creating a View
·        Controller definition
·        Declaring a Model to the Component
·        Nesting Components
·        Creating a Data Link
·        Working with View Templates
·        Working with the Service Controller
The perspective area that displays the Data Modeler is the Diagram View. The entities of a Web Dynpro application are created using graphical means. A selection list of Data Modeler actions is available from which you select the relevant entity and insert it in the design area of the Data Modeler.
Starting the Tool
Prerequisites
You have created a Project and a corresponding root Web Dynpro Component.
Procedure
To open the Data Modeler, choose Open Data Modeler from the context menu for the component name in the Web Dynpro Explorer. To create an application entity, choose the corresponding Data Modeler action in the tool selection area. Then click on the relevant area in the Data Modeler editor. The corresponding wizard is then started and you can make the required entries.
For example, to define a custom controller, choose Create Custom Controller and then click on the area Custom Controllers. The definition wizard is started automatically.
If This is not the case then plz check ur WebDynPro Installation Manual....
Hope So ur problem will Solve.....:-)
Regard's
Dheerendra Shukla

Sharepoint 2013 Reporting Services & OLAP Cubes for Data Modeling.

I've been using PowerPivot & PowerView in Excel 2013 Pro for some time now so am now eager to get set up with Sharepoint 2013 Reporting Services.
Before set up Reporting Services I have just one question to resolve.
What are the benefits/differences of using a normal flat table set up, compared to an OLAP cube?
Should I base my Data Model on an OLAP Cube or just Connect to tables in my SQL 2012 database?
I realize that OLAP Cubes aggregate data making it faster to return results, but am unclear if this is needed with Data Modeling for Sharepoint 2013.
Many thanks,
Mike

So yes, PV is an in-memory cube. When data is loaded from the data source, it's cached in memory, and stored (compressed) in the Excel file. (also, same concept for SSAS Tabular mode... loads from source, cached in mem, but also stored (compressed) in data
files, in the event that the server reboots, or something similar).
As far as performance, tabular uses memory, but has a shorter load process (no ETL, no cube processing)... OLAP/MDX uses less memory, by requiring ETL and cube processing... technically tabular uses column compression, so the memory consumption will be based
on the type of data (numeric data is GREAT, text not as much)... but the decision to use OLAP (MDX)/TAB (DAX) is just dependent on the type of load and your needs... both platforms CAN do realtime queries (ROLAP in multidimensional, or DirectQuery for tabular),
or can use their processed/in-memory cache (MOLAP in multidimensional, xVelocity for tabular) to process queries.
if you have a cube, there's no need to reinvent the wheel (especially since there's no way to convert/import the BIDS/SSDT project from MDX to DAX). If you have SSAS 2012 SP1 CU4 or later, you can connect PV (from Excel OR from within SP) directly to the
MDX cube.
Generally, the benefit of PP is for the power users who can build models quickly and easily (without needing to talk to the BI dept)... SharePoint lets those people share the reports with a team... if it's worthy of including in an enterprise warehouse,
it gets handed off to the BI folks who vet the process and calculations... but by that time, the business has received value from the self-service (Excel) and team (SharePoint) analytics... and the BI team has less effort since the PP model includes data sources
and calculations - aside from verifying the sources and calculations, BI can just port the effort into the existing enterprise ETL / warehouse / cubes / reports... shorter dev cycle.
I'll be speaking on this very topic (done so several times already) this weekend in Chicago at SharePoint Saturday!
http://www.spschicagosuburbs.com/Pages/Sessions.aspx
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

How to create an exclusive relationship in IE Data Model

Hello Experts,
How can I specify exclusive relationships in the IE Data Model? I have a PERSON and a ORGANIZATION entity. Both have a relationship to an ADDRESS entity. The ADDRESS entity can only have a relationship to either PERSON or ORGANIZATION. How is this situation modeled in the IE Data Model?
Thank you,
Carsten

Relationships in the IE Data Model method are between only 2 entities. There is no way to directly model a three-way relationship that you are trying to use. The alternatives for modeling it in the IE method would be to use a generalization structure on one end or the other. You could generalize Person and Org into a higher level concept (typically called Legal Party or just Party) and draw the relationship from the new Party entity to Address. Or, you could subtype Address as either a Person Address or and Organization Address and draw relationships from the new subtypes to Person and Organization respectivley.
You could also choose to just annotate it on the diagram using either text or a graphic object.

Role of text & hirarhies of info object property in cube data model & Bex

Hi,
Info object have properties : first > attribute can be either display or navigational which are as charatristics(dimension's) display property and as in navigational folder res. in cube > display data model, in display attribute can we see same as like data modle while navigational attribute will serve as charateristics of res dimension. ( in BI 7.0 )
where is the text and hirirchey property of info object in cube data model and bex analyzer?
Best regards,
Dushaynt.

hi,
follow this link. it will help.
http://help.sap.com/saphelp_bw33/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm

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

Data Modeling for a Small Database Tutorial - understanding "Creating Relations Between Entities" part

I am trying to understand and make use of Tutorial: Data Modeling for a Small Database
During this tutorial I'm supposed to make Transactions Entity containing two attributes that will refer to Patrons (patron_id) and Books Entities (book_id) (2.1.4)
Later, I'm adding two one-to-many relations that duplicate mentioned attributes in Transactions Entity (patron_id1 and book_id1). (2.1.5)
So here comes my questions: what's the purpose of creating those attributes in point 2.1.4 if they're then duplicated in paragraph 2.1.5?
If it might be crucial, i'm using Oracle SQL Developer Data Modeler Version 4.0.0.825 Build 825 on jdk1.7.0_25.
Bonus question: How to turn on attributes types on Logical Diagram? I can't find corresponding option anywhere...
I would be really grateful for every answer and for every trick!

You are looking at release 2 documentation. I checked 3.3 and 4.0 EA3 and the tutorial has been corrected You may want to download the latest version and use that documentation.

How to handle One to Many relation In BI Data Model

Hi,
I posted this same question earlier but bit in a different way ..
I have may be infact many come across this requirement ..
As you know R3 Multiple Partner functions would be assigned to a single Sales document but when we want to show the same sales report along with Sales document and respective partner functions in BI it is bit difficult because we can not really allow to split the keyfigure values based on Partner functions when they drilled down by Pfunctions ...
Only alternative is to have multiple partner function attributes (columns) like one for each pfunction in one of the Sales Doc Masterdata and define them as navigational attributes..so that all partner functions would be saved
SALES DOC -
PartnerFunction-----AMOUNT
100000----
   ZZ -
5000
100000--   AB--
100000--    BC--
to meet above requirement as per my above proposed alternative looks like as below
SALES DOC -
Partner Function 1--PArtner Function2-- PF3------ AMOUNT
100000--ZZABBC--
5000
So other than this do you see any other better Data Model ??
Could you please share your thoughts on it??
Thanks & Regards,
BRK

Create a view based on VBPA ( Sales partner functions) and VBAK,VBAPor VBEP ( anyone relevant to your case) and create a generic datasource based on that

Many pages and complex data model in JHS app

I am using JHS to create an application containing data that is structured something like:
- Country
- Company
- Department
- Employee
- Payments Details
I have created entity and view objects corresponding to each of these and the appropriate accessors/view links. We need the user to be able to search, work on data and 'drill down' from any level (not always starting with company). In order to make this possible my JHS application has 5 'top level' tabs corresponding to each of the above entities. From each of these top level pages users can drill down to the children.
This works but we end up with many pages and a large data model with lots of replication and nesting.
Country - 5 pages
Company - 4 pages
Department - 3 pages
Employee - 2 pages
Payments - 1 page
total 15
You can picture how the data model is structured. Obviously this is a very simple example but I hope it illustrates my concerns. We have so many pages that post-generation changes are going to be difficult to manage. I'm also worried about the size and complexity of the data model. In this case views are almost all entity based so I guess the data is only cached once but supposing they were not?
Are we using JHS in the best way ? perhaps I'm overcompilcating it ?
I have started to rewrite the JHS generated application so that it (almost) always reuses the same top level generated pages (with some modifications). When the user wants to navigate to a child I modify the whereClause of the target ViewOjbect appropriately, reexecute it and forward to the corresponding 'top level' page. This approach seems to work well, cuts down the number of pages enormously and simplifies the data model (and has enabled me to put breadCrumbs in).
In doing this though, am I creating work for myself that JSH could have done if we had used it differently in the fist place?

This sounds like a valid approach in your situation. We have been playing with the idea of having something like 'Group Links' where you can generate navigation items from one group to the other. Then, you would need to have one, 5 level deep nested group, and 4 other top level groups to provide the search&select on each of the nested groups, but they themselves would not need to have nested groups, but a navigation link to the nested groups in the 5-level deep group.
Although nice and simple in theory, the details are a bit tricky to work out with all the possible layout- and samePage settings, so we have not implemented this yet. So your approach seems a valid one. If you have any suggestions on a way to generate what you are now doing manually, we'll be interested.
Kind regards,
Peter Ebell
JHeadstart Team

Needed SAP CRM Data model with Object, Entity and Attribute level details

Hello all,
We are working on a huge IS-U / CRM implementation and we are still in the data gathering phase. The client has a whole load of legacy systems that will be replaced with IS-U and CRM. Right now we are in the process of developing data models using Excel first and then presenting them to the client to go forward from there. For this we need to have all the business objects, entities and their attributes.
I know about the SD11 transaction, but we don't have a CRM system yet. My colleagues have access to a German ERP system and they were able to get models for HR, FI and Asset management. I tried for the Business partner / customer in there, but the models were not proper.
So, once again, I need the specific data models out of SD 11 for CRM business partner. If anybody has the information, please do pass it on to me as I need them urgently. It would be a great help if somebody can do so.
Regards
Rajesh

I suggest the following:
Please, check whether the system works if you activate the implementation BUPA_F4_AUGRP.
In addition check the notes 559662, 674869 and 782927. Maybe the notes are already implemented but you can try then the implementation of the BADI (SE19). It should resolve your issue.
I have implemented this Badi solution before, and after activation; the search help ; nor search result list did NOT show any Business partners anymore that had an authorization group I was not allowed to see.
kind regards
Davy Pelssers
SAP CRM/Security consultant

Reuse Dimdate across different database for different data models

Hi,
I am designing a new data model for a data mart. I need to add dimdate dimension in this data model. I noticed that dimdate already exists in another database and being used by another
data model. Is it possible to re-use the existing dimdate table for my new data model? If so, what about the foreign key constraints? Normally we link the date columns from fact table to the dimdate keys. How would we achieve that in case we are using the
same table across different databases?
Any opinion on this will be highly appreciated.
Thanks in Advance.
Cheers!!

You can create a copy of dimdate table to your new data warehouse.
If both data marts were in a single data warehouse, then you don't required to copy. but as these are in two different databases then you just copy that.
regarding FK relationship. you can connect any fact table to you date dimension. even if you want to use more than one instance of your date dimension, it would be simply adding multiple FK columns in your fact table (role playing dimension).
For date dimension be sure that your date dimension covers most of the attributes required. here is an example of date dimension:
http://www.rad.pasfu.com/index.php?/archives/156-Script-to-Generate-and-Populate-Date-Dimension-Version-2-Adding-Multiple-Financial-Years.html
Regards,
Reza
SQL Server MVP
Blog:
http://rad.pasfu.com Twitter:
LinkedIn:
SQL Server Integration Services 2012 Tutorial Videos:
http://www.radacad.com/CoursePlan.aspx?course=1

PowerPivot removed table replicated into the data model on refresh

Hey
I am facing the following problem which is absolutely persistent and annoying in nature. I am using a data model created with PowerPivot with connections to three different SQL servers and 25 tables. The bug is that every time I refresh my data, a table
that was initially added to the data model (and later removed) is replicated in equivalent number of tables that use this connection, which is currently around 12 tables, so I get 12 duplicates of the same unnecessary table on every refresh, named with the
name of the schema on the SQL server that is followed by a running number. Removing these from the data model on every refresh simply takes too much time on a daily basis. The additional undesired table which is created is what is defined in the SQL query
of the connection string of this connection.
I tried to solve this problem by zipping the Excel file and modifying this SQL statement present in the connection string in the connections.xml file in a way that it would not return anything, but this always leads into a corrupted workbook.
After encountering this I have managed to avoid this problem by making sure that the initial table I'm adding to the data model will remain in the model, but I really don't want to rebuild this current model. Is there any fix for this issue without
rebuilding the data model?
Thanks for all the help in advance!

I am using 64-bit Office 2013 with the recent SP1 upgrade and the included PowerPivot plug-in on a Windows 8.1 machine.
I always create the connection by using "From SQL server" then fill in the server and log in details and use a ready SQL statement that I have written by using SQL Server Management Studio to import the initial table. For all the preceding tables
using the same server and schema, I always select it from existing connections and just paste the SQL queries required for any additional tables to the "Write a query that will specify the data to import", rather than using the table import tool.
I am not sure if it could have any effect that I've been using the type connection "From SQL server" although the database is really running on Azure (there is a possibility to select From Other sources > Microsoft SQL Azure, but the functionality
seems the same).
I don't really understand what I should edit from the existing connections section. Just to clarify, apparently the Connection String parameters can be edited from PowerPivot, but not the Command Text which can be viewed from Excel Data > Connections
> Properties, but is shown in gray with a message "Some properties cannot be changed because this connection was modified using the PowerPivot add-in."
In the data model I am using two sets of identical tables, but connected to two different servers that are running a database 1:1 in structure. Initially the problem considered only the other of these, but I accidentally reproduced it by, again, editing
the SQL query in the table that was initially imported when that connection was created (PowerPivot > Design > Table Properties). Now when refreshing I get tables that are structured as in what the "Connection Text" part of the connection would
produce, which replicated for the equivalent amount of additional tables using the same connection, so now I'm getting 12 tables (the number of tables using the same connection) each named "*schemaname1* Query", "*schemaname1* Query2",
"*schemaname1* Query3" "*schemaname2* Query" and so on.
Personally I can definitely see a pattern here. If there isn't a table matching what has been specified in the "Command Text" that was described when the connection was created, then it for some reason runs this query anyway on every table that
is using the connection.

Identify Entities for Logical Data Model

Hi,
I donno exactly this is the correct forum for this question. I believe there are database experts here to help me on this.
I am in confusion that, phsically the data can be saved in a set of tables (4-5 tables). But different views (User Interfaces) and reports can be created from these tables.
Assume that,
View1 - Uses all tables
View2 - uses only 3 tables
View3 - uses only 1 table
Report 1 - uses only 2 tables
Report 2 - uses only 4 tables
Should my Logical Data Model reflect all these view1, view2, view3, Reprt1 and Report2?
How exactly do we need to identify the entities for Logical Data Model?
Could you please any one help me on this?
Thanks & Regards
M Thiyagu

sorry, i couldnt understand your query..
thanks,
baskar.l

Data Modeler: Replicating common attributes across many entities

Similar Messages

Maybe you are looking for