Logical Vs Physical Data Model

Hi guys
What is the difference between logical data model and physical data model.

I assume you are talking about ERwin.
In short,
Logical data model is non-database specific model you can apply it to any database by convert it to target physical data model.
Physical data model is database specific, for example, column data type, physical storage parameter, SQL syntax etc.

Similar Messages

Logical Data Model Vs Physical Data Model

Hi guys, what is the difference between, logical data model and physical data model.

Duplicate Thread:
Logical Vs Physical Data Model
Daljit Singh

Physical data model

We are trying to report our physical data model from Designer2000 meta data.
Actually individual reports exists within Designer showing tables, attributes.
However, we would like to have a single report, combining all tables with their text description, along with their attributes and their characteristics (nullable, type, length, domain...)
Is anybody as always did that ???
Thanks,
Alain

Hi,
As you aware major part of GL is based on Chart of Account, Calander (GL Period) and Currency, you can check all tables related to these.
You can use below query to get those tables :
select from all_tables where table_name like 'GL%' and owner='GL'*
and table_name not like 'GL_ALLOC%' and table_name not like 'GL_CONS%'
Please do refer the doc suggested by the other expert in this thread..
Regards,
S.P DASH
N.B : We believe you put a GL question in a wrong folder/Thread (Procurement) :).. you could have received a better response had it been in Finance folder.. :)

I-proc physical data model

Hi Guys
Dose anyone out there know where I can lay my hands on a Physical data model of i-proc? One which shows the relationship of the tables.
Ruth

have a look on the e-trm on metalink for purchasing. i-proc uses the same datamodel as that of purchasing and I am sure that the e-trm has some pdfs of the data models on it.
on the e-trm - select the version that your are on , then go to the download files and documents, the find a pdf file of the PO items which will give you the erd

Domains and Logical Types in Data Modeler

Been out of serious design work for a long time. Can someone provide a good pointer to descriptions on Domains and Logical Types and presented in the Data Modeling tool?
For instance I am having trouble tracking the following distinctions:
Domain Logical Type
LongText Varchar
ShortText Char
Text Char
NText NTEXT
NVarchar NVARCHAR
CHAR and VARCHAR are listed as Logical Types but not Domains. There is a TEXT logical type, but ironically, it does not correspond to the Text Domain. Varchar2 appears in neither list. I believe I ready the N* domains/types are for international characters (multi-byte?), but basically see no pattern here so was hoping someone could straighten me out.
Thanks,
Robert Kuropkat

Hi Robert,
Logical types are abstraction for native data types in supported databases. You need logical types if you want to import from database or DDL script (mapping of native to logical is important here) or want to generate DDL script (mapping of logical to native). You can delete all logical types (only "unknown" has importance) and create your own logical types. In this case you have to map them to native database types. If you use only Oracle database then you can delete types related to other databases. Of course you can rename existing logical types if you don't like how they are named.
Domains are based on logical types - you need logical type in order to have valid domain definition. Provided domains are just sample. You can delete them - the only important here is "unknown". You can create two types of domains (it's usage point of view) - 1) per installation - common for all designs; 2) per design - they appear only for design they are defined. You also can import domains.
Also domains are automatically created during import of DDL script - it's kind of data type aggregation - domain is created for each used data type.
Best regards,
Philip

Physical Data Model For GL

Hi Experts,
I am new to Oracle Apps, I need Data Model for GL tables..from wherer we can get it.
Please suggest !
Regards
S

Hi,
As you aware major part of GL is based on Chart of Account, Calander (GL Period) and Currency, you can check all tables related to these.
You can use below query to get those tables :
select from all_tables where table_name like 'GL%' and owner='GL'*
and table_name not like 'GL_ALLOC%' and table_name not like 'GL_CONS%'
Please do refer the doc suggested by the other expert in this thread..
Regards,
S.P DASH
N.B : We believe you put a GL question in a wrong folder/Thread (Procurement) :).. you could have received a better response had it been in Finance folder.. :)

Physical Data Modeler - Model DB2 Prefereces

Hello,
I can't see how 'Create TableSpace for Each Table' preference works.
I can't find anything about this subject in the documentation.
Somebody can explain me how to use that preference ?
Regards
Nelson Rosa

Hi Nelson,
1) set default database where tablespaces will be created - default one is DSNDB04, let's change it DSNDB15
2) check "Create tablespace for each table"
3) define name template - two variables can be used - example: TBLS_{table}
4) press Ok button, create/open physical model for DB2/390
- database DSNDB15 appears in list of databases
5) create table - Table_1; tablespace TBLS_table_1 is created
6) rename table to Sales - tablespace is renamed to TBLS_Sales
Philip

BIP Trial 11.1.1..6: Error while generating XML data in Data Model

Hello,
I have created a Data Model with a single query. After saving the DM and clicking on the XML icon to generate sample data, I get the following error:
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
End tag 'span' does not match the start tag 'img'. Error processing resource 'http://localhost:7001/xmlpserver/servlet/xdo'...
*<table style='background=color: #d9e5ef; margin-top: 10px;' width='100%' cellspacing='0' cellpadding='0' border='0' summa...*
I have verified that the SQL runs without errors in SQL Developer using the same connection parameters as whats used in the DM.
There are no html tags/key-words etc being used in the sql our it's output.
Is there a a way to debug this? This is extremely frustrating. Especially since the same sql works without any issues in Oracle Reports.
Thanks,
Manish

ya i can understand we wont do the sql logic at the data model part as some time performance issue may come when comparaed to sql run in package and sql running in data model . so i have mostly done using package and i will just do select * from table in the data set of data model so i didn't face any issue's like this .
once check this tutorial may be you already
i use to create parameters like this i didn't face any issue
SELECT * from TEST where ID=:p_id
http://st-curriculum.oracle.com/obe/fmw/bi/bip/bip11g/gettingstarted/gettingstarted.htm

Data Model Exporting - MDM to Erwin or another data model tool

I would like to export the latest MDM physical data model in production to any erwin modelling tool or any othe data modelling tool

To export the schema of an MDM repository to an XML file:
1. In the Console Hierarchy tree, right-click on the MDM repository whose schema you want to export and choose Export Repository Schema from the context menu, or select the tree node and choose Repositories ® Export Schema from the main menu.
If the top-right pane is currently displaying the list of MDM repositories, you can also right-click on the repository in the grid and choose Export Schema from the context menu.
2. Click Save to close the dialog and export the schema.
Schema files are stored in XML format in a user-defined location using a user-defined filename. The file contains the schema definition only; no table or field content.
http://help.sap.com/saphelp_mdm550/helpdata/en/f2/2f21039e9146098e7b238f1a4c8e5e/content.htm
Thanks,
Shambhu.

Oracle Data Modeling tool interoperability with QDesigner models.

Hello,
Would it be possible to get some information on how Oracle SQL Developer Data Modeler works with models from other data modeling tools such as QDesigner.
How can Quest QDesigner read the .cdm (conceptual data models) and the .pdm (physical data models) from QDesigner.
Regards,
Mary

SQL Developer Data Modeler does not work with QDesigner models.
Sue

Importing logical and physical model from Sybase power designer/Erwin

Hello,
We have several models created in Sybase Power designer, logical and as a well as physical. Is there a way to directly import models into Oracle designer?
Thank you for your help.
Syed

Hi Syed,
ERwin has a facility to export to Designer 2000. Of course you're probably not using Designer 6.0 or earlier so it's of little use.
I have been looking at a couple of tools for importing from ERwin: Reischmann Informatiks TOOLBUS Interface for Oracle Designer and ALLFusion ERwin; and Meta Integration Technologys Meta Integration Model Bridge (MIMB). Neither product is free (nor inexpensive) but if you've got a number of models to convert then the tools seem cheap by comparison. Also, none of the products that I've looked at recreate the actual diagrams (not that I expected them to).
I am leaning towards TOOLBUS as it provides more complete migration of Logical and Physical models (especially the linkages between the models) using Oracle Designers API rather than a DAT file as provided by MIMB.
Hope this helps,
Wayne Lehman
Avanti Business Systems Inc.

Logical and Physical Models

Hi All,
I'm new to Designer. I need to produce a logical data model in Oracle Designer 10g. I have created a few tables in the RON and have used Design Editor to add these to a Server Model. I think this is giving me the physical model rather than the logical model.
Can you please tell me if I'm going about this the wrong way ? I need the logical model to confirm with the non-technical people before I produce the physical model for the techies.
Thanks

Billy wrote:
Hi,
John - yes I have already checked all this, all looks ok. Also, I'm only using the REPOS_MANAGER account for now so permissions should not be an issue.
Mark - when you say create an entity in the RON, I can create tables, how would I create an entity in the RON ? I can go to Diagrams in the RON and see my ERD.
When I installed the repository I do remember having to go to the SYS account to grant an execute on a package to the REPOS_MANAGER user because one of the REPOS_MANAGER packages required it.
Any direction would be appreciated ?
Thanks
BillyAh, but that IS the issue. You shouldn't use the repository owner account for your day to day work. Create another Oracle user and grant it privileges through the RAU. Then connect as that user to work in Designer. Oddly enough, the repository owner doesn't have the privileges that it needs - the privileges are stored in the repository, not database privileges.

Data Modeler Logical Data Type confusion!

I don't get it.
When defining a logical model, I want to assign data types to the attributes in my model.
I understand a logical datatype like money, and that a logical datatype might be implemented differently in different databases. The concept makes perfect sense to me.
I pick a datatype from the Logical Types.
It ignores the logical datatype that I picked and puts in another datatype instead. I'm guessing that it's a physical mapping. I would understand the logical-to-relational mapper doing that , but I don't understand it happening at this point in the model life cycle.
Let's say I pick Money. It puts Double into the logical datatype, not money.
If I pick Date or DateTime, it puts Date into the logical datatype, so what is the point of giving me two types to pick from?
Seems kind of wonky.

David,
We will publish soon a document on how the data types work.
If you go to tools, Types administration you will see that a logical type is mapped to a native type and a native type is mapped to a logical type.
The logical type MONEY is mapped to DOUBLE for Oracle.
Types and domain files can be customised.
One could argue that the logical name MONEY should show up and not the native name. Showing the native name has the benifit that you see what the logical type is mapped to. Both approaches could have their supporters, no?
Kind regards,
René De Vleeschauwer
SQL Developer Data Modeling.

SQL Dev Data Modeller: Auto-generate Surrogate PKs in the Physical Model ?

How can I have the logical modeller allow the user to design with logical PKs, but then have surrogate primary keys be auto-generated off sequences by the modeller when it comes to create the physical model - as in conventional application design?
Without this facility, this tool is useless, IMO.
I want:
i). sequences to become the physical PKs by default, and that what were the logical PKs in the logical model, to become a unique key in the physical model.
ii). I want this set by default when generating the physical model....
iii). ....with an option to turn this off on a entity-by-entity basis (as not all tables will necessarily require such a surrogate PK; so the logical PK may remain the physical PK).

It is common practice that physical PKs in Oracle tables are defined from sequences (surrogate PKs), and that the logical PK from the entity becomes a unique key in the table.
This may not always be the case in every application out there, and some people may disagree, but it is nonetheless a needed feature.
My new Feature Request is therefore:
I would like to see the following additions to the product.
1. In the Preferences -> Data Modeler -> Model -> Logical, a flag that by default indicates whether the designer wishes to opt to enable this feature (ie; have all logical PKs converted to unique keys, and replaced by sequence nos. in the physical model). This flags needs to be there since in real life, albeit erroneously IMO, some people will choose not to opt to use this functionality.
2. On every entity created in the model, there needs to be a flag that allows to override this default option, as not every table will require a surrogate PK to be generated. Being able to (re)set a flag located on the entity properties (perhaps under 'Engineer To'), will accomplish this.
3. When Forward Engineering to the physical model from the logical, the following should happen.
ENTITY 1 ---------->TABLE 1
---------------------> P * Surrogate PK
* Attribute 1 -----> U * Column 1
* Attribute 2 -----> U * Column 2
o Attribute 3 ----------> Column 3
Here you can see,
- Attributes 1 & 2 (the logical PK) of the entity become a unique key in the table (columns 1 & 2),
- optional Attribute 3 becomes NULLable column 3,
- and a physical surrogate PK column is added (type unbounded INTEGER, PRIMARY KEY constraint added).
From entity DEPT as: (Examples based on SCOTT schema)
DEPTNO NUMBER(2) NOT NULL <-- Logical primary key on entity
DNAME VARCHAR2(14)
LOC VARCHAR2(13)
CREATE TABLE DEPT
(PK_DEPT INTEGER, -- New column becomes surrogate physical PK, driven from sequence defined later
DEPTNO NUMBER(2) NOT NULL, -- Former logical PK becomes a UK
DNAME VARCHAR2(14),
LOC VARCHAR2(13))
ALTER TABLE DEPT
ADD CONSTRAINT PK_DEPT PRIMARY KEY (PK_DEPT) USING INDEX PCTFREE 0
ALTER TABLE DEPT
ADD CONSTRAINT UKLPK_DEPTNO UNIQUE (DEPTNO) USING INDEX PCTFREE 0 -- Former logical PK becomes a UK (constraint name reflects this)
CREATE SEQUENCE PK_DEPT_SEQ
CREATE TRIGGER PK_DEPT_SEQ_TRG
BEFORE INSERT ON DEPT
FOR EACH ROW
WHEN (new.PK_DEPT IS NULL)
BEGIN
SELECT PK_DEPT_SEQ.NEXTVAL
INTO :new.PK_DEPT
FROM DUAL;
-- Or from 11g onwards, simply,
:new.PK_DEPT := PK_DEPT_SEQ.NEXTVAL;
END;
From entity EMP as:
EMPNO NUMBER(4) NOT NULL -- Logical primary key on entity
ENAME VARCHAR2(10)
JOB VARCHAR2(9)
MGR NUMBER(4)
HIREDATE DATE
SAL NUMBER(7,2)
COMM NUMBER(7,2)
DEPTNO NUMBER(2)
CREATE TABLE EMP
(PK_EMP INTEGER, -- New column becomes surrogate physical PK, driven from sequence defined later
FK_DEPT INTEGER, -- New FK to surrogate PK in DEPT table (maybe NOT NULL depending on relationship with parent)
EMPNO NUMBER(4) NOT NULL, -- Former logical PK becomes a UK
ENAME VARCHAR2(10),
JOB VARCHAR2(9),
MGR NUMBER(4),
HIREDATE DATE,
SAL NUMBER(7,2),
COMM NUMBER(7,2),
DEPTNO NUMBER(2))
ALTER TABLE EMP
ADD CONSTRAINT PK_EMP PRIMARY KEY (PK_EMP) USING INDEX PCTFREE 0
ALTER TABLE EMP
ADD CONSTRAINT FK_DEPT FOREIGN KEY (FK_DEPT) REFERENCES DEPT (PK_DEPT)
ALTER TABLE EMP
ADD CONSTRAINT UKLPK_EMPNO UNIQUE (EMPNO) USING INDEX PCTFREE 0 -- Former logical PK becomes a UK (constraint name reflects this)
CREATE SEQUENCE PK_EMP_SEQ
CREATE TRIGGER PK_EMP_SEQ_TRG
BEFORE INSERT ON EMP
FOR EACH ROW
WHEN (new.PK_EMP IS NULL)
BEGIN
SELECT PK_EMP_SEQ.NEXTVAL
INTO :new.PK_EMP
FROM DUAL;
-- Or from 11g onwards, simply,
:new.PK_EMP := PK_EMP_SEQ.NEXTVAL;
END;
[NOTE: I use PCTFREE 0 to define the index attributes for the primary & unique keys since the assumption is that they will in general not get updated, thereby allowing for the denser packing of entries in the indexes and the (albeit minor) advantages that go with it.
This is certainly always true of a sequence-driven primary key (as it is by its very nature immutable), but if the unique key is likely to be frequently updated, then this PCTFREE option could be user-configurable on a per table basis (perhaps under Table Properties -> unique Constraints).
For non-sequence-driven primary keys, this storage option could also appear under Table Properties -> Primary Key.
I notice no storage options exist in general for objects, so you may like to consider adding this functionality overall].
Associated Issues :
- Preferences, 'Naming Standard: Templates' should be updated to allow for the unique key/constraint to be called something different, thus highlighting that it comes from the logical PK. I've used 'UKLPK' in this example.
- Mark the physical PK as being generated from a sequence; perhaps a flag under Table Properties -> Primary Key.
- When Forward Engineering, if an entity exists without a logical PK, the forward engineering process should halt with a fatal error.
!!! MODERATOR PLEASE DELETE ME !!!

Logical table with data restrictions from the physical table

Hello, I have a question about the relationships between the Logical Tables in Business Model and Mapping and The Physical table in the physical layer. The problem is the next one:
I have a Physical Table named T1 that contains the attributes: Id, DateChangeState, State,…
T1
DateChangeState| ID |State     | Other columns….
01/01/2011 | 1 | 03 |     …
02/01/2011 | 1 |     11 |     …
03/01/2011 | 1 |     02 |     …
02/02/2011 | 2 |     01 |     …
03/02/2011 | 2 |     02 |     …
I need filter this table and extract only one row per ID. The row that I need is the row who contains the Max(DateChangeState) per ID. I don’t know how extract only the rows selected from the physical table to the Logical Table.
I need that the logical table contains the next rows:
T1_Logical
DateChangeState |ID |     State     Other columns….
03/01/2011 | 1 | 02 |     …
03/02/2011 | 2 | 02 |     …
How can I extract only the rows with the Max(DateChangeState) grouped by ID in the BMM?
I thought put this condition in the column mapping (CASE WHEN DateChangeState=Max(DateChangeState)) but the Max(DateChangeState) was not grouped by ID.
Any idea about how solve this problem?
I can not use the group by in the answer and I can not change the physical layer.
Thank you,
Best Regards.

Hi Rajeevagrl your solution is very good but I dont´t know why obiee is applying twice the max condition, The select is the next one:
select distinct D1.c1 as c1,
D1.c2 as c2,
D1.c1 as c3
from
(select D1.c1 as c1,
D1.c2 as c2
from
(select D1.c1 as c1,
D1.c2 as c2,
max(D1.c3) over () as c3
from
(select T379.ID as c1,
T379.DATE as c2,
max(T379.DATE) as c3
from
T1 T379
group by T379.ID, T379.DATE
) D1
) D1
where ( D1.c2 = D1.c3 )
) D1
order by c2
Edited by: 848497 on 14-abr-2011 3:58

Logical Vs Physical Data Model

Similar Messages

Maybe you are looking for