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.. :)

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

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.

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

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

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

OBIEE EXECUTE PHYSICAL sql as Data Model Query

The following SQL was generated using OBIEE. I'd like to use it as the SQL query for my data model. It works fine it I hard code all of the values into the where clase. However when I attempt to pass parameter values (:ACCOUNTING_PERIOD & :FISCAL_YEAR) into the below SQL statement, I get an error and the report will not generate. The error is the typical "The report can't be rendered. Check with your administrator". Any ideas on how I can pass parameter values into this SQL?
EXECUTE PHYSICAL CONNECTION POOL SDEVDW SELECT A.BUSINESS_UNIT,A.PROJECT_ID,A.PROJECT_STATUS,A.EFFDT FROM SPSDW.PS_PROJECT_STATUS A WHERE A.EFFDT = (SELECT MAX(B.EFFDT) FROM SPSDW.PS_PROJECT_STATUS B WHERE B.BUSINESS_UNIT = A.BUSINESS_UNIT AND B.PROJECT_ID = A.PROJECT_ID AND B.PROJECT_STATUS<>'C' AND B.EFFDT <= (SELECT PPERIOD_END_DT FROM SPSDW.PS_D_DET_PERIOD WHERE PPERIOD_CD = 6 AND PYEAR_NUM = 2008 AND DT_PATTERN_CD = '01' AND SRC_SYS_ID = 'FSCM')
) ORDER BY 1,2,3

I turned on debug and bounded OC4J. After I ran the report, I did not see any link.
The error that returns is:
"The report cannot be rendered because of an error, please contact the administrator."
Where will the link be located. Is there are log file that I can review. We are using BI Publisher enterprise (10.1.3.3.0).

Data Modeler bug? - it keeps reporting missing physical model files

Hi,
I'm having a rather serious problem with the latest data modeler, Oracle SQL Developer Data Modeler 3.1.4.710. It keeps losing physical model files for some reason.
I started to notice that it was not generating all the tables in my small design. After hours of struggle I found multiple error messages in the log file:
2012-12-18 10:51:20,126 [Thread-71] ERROR XMLTransformationManager - Unable to load object from XML: C:\cygwin\home\Brian\codebase\models\data\Design\rel\395D160B-C7224B8EAD05\phys\D9582E4E-2ED963CB9D32\View\seg_0\A555DB9B-8864-9C0B-DCA8-BAC5231F55C6.xml
java.io.FileNotFoundException: C:\cygwin\home\Brian\codebase\models\data\Design\rel\395D160B-C7224B8EAD05\phys\D9582E4E-2ED963CB9D32\View\seg_0\A555DB9B-8864-9C0B-DCA8-BAC5231F55C6.xml (The system cannot find the path specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:138)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.openPhysicalModel(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.openPhysicalModel(Unknown Source)
     at oracle.dbtools.crest.swingui.browser.BrowserPanel$88.run(Unknown Source)
These messages appeared every time I opened my physical model (Oracle 10g).
After deleting and recreating the physical model the problem went away for a while. But after closing and reopening the design I started to see the errors again.
Has anyone seen something similar?
Regards,
Brian

Thanks Philip!
The workaround does the trick for the tables, primary keys and unique keys.
I have just observed that table level constraints show a slightly different behaviour.
Names show up like TCC5, TCC6, etc.
Seems the same problem as previously in SQL*Modeler forgets check constraint names
Is there a workaround for that problem too ?
I already noticed that there is no parameter NameChanged for a table constraint.
Enrico

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 !!!

Data modeling tool: physical model migration

Hi,
I have imported my relational model with a generated physical model for oracle 9i.
I'd like to migrate my DB to oracle 10g, but I don't feel like creating a new physical model for Oracle 10g from the scratch and configuring it all.
Is there any way to copy that oracle 9i physical model into an oracle 10g model? I know there could be any implementation change from 9i to 10g, but at least copy the main 99% (and warn about the 1% impossible to replicate in 10g).
Could this feature be taken into the production version?
By the way, is this a BUG? when I start the tool, my oracle 9i physical model is not shown in the tree, and I've to right-click over physical model, press open, and then select oracle 9i, to be shown in the tree. But I close the data modeling tool, and when I start again, there is no physical model shown in the tree :(
thanks a lot in advance, I'm evaluating the tool.

Thank you very much for your reply, and hearing those news makes me very happy, because I'm evaluating the product and I miss some functionality like that.
By the way, where can I find the new functionality or the fixed one that is going to be on the production release? Or could yo send it to me by email or any other way? I'm very interested in it.

Data modeler, physical model related view

Hi community,
is there a way to create a physical model related view in the data modeler or a better idea?
The reason is simple, let me say, I have a view with string concatenation and want use this view in oracle and sql server, the syntax is different.
In Oracle it is " column1 || ' ' || column2". The same thing in sql is "column1 + ' ' + column2"
Regards, Henrik

Hi Kent,
thank you for the answer, but it is not really a solution for me to copy the complete relational model to a second one! It is unfavorable for later changes on the model. You must do them all changes on both models.
Currently I have one relational model together with four physical models, Oracle 10, Oracle 11, Oracle 12 and MS Sql. If I work with stored functions, procedures, packages, triggers and so one, it is possible to change the content of these objects in the physical model, depending of the sql language and the database version features.
Only tables and views are not changeable and I’m not able to add a table or view to the physical model.
Other suggestions?
Regards, Henrik

Oracle Data Modeler commit change seg physical table

Hello,
Sometimes when I record a data model, Oracle Data Modeler (SVN) given as outgoing a chage of segment of physical table , if you committees are to change, duplication of files in the physical model is produced. Later when you open the physical model gives errors that have duplicate files
How you can correct this error? Why the segment change occurs?
Thanks

Hello,
Versión 4.0.0.833.
No pattern is occasionally when shooting in the data model. How you can correct this error? Why the segment change occurs?
Thanks

Data Modeler: is it possible to compare physical models?

Hello,
We're looking for a new Data Modeling tool, as we will abandon Designer (for many different reasons...). The SQL Developer Data Modeling-tool looks very promising. Especially the "compare models" -tool looks interesting to create change-scripts for new implementations. What I don't find, however, is the possibility to generate typical physical attritutes, like permissions (resulting in grant-statements), tablespaces. Is this available? Is it possible at all? For your information: I've just downloaded the EAR 2 (version 1.5.1 build 525)
Thanks in advance for your reply,
Peter

Peter,
I would like to echo your feature request. I too spent many years with Designer and until SDDM came along, I was still using it for server model diagrams mostly. We always wanted to make sure that we have a record (model) of what was in a schema. We deploy to MANY environments - several for development, various phases of testing etc. and of course production and clones of production. It's really nice to run a utility of some sort that compares my model to an implementation. I might compare the same model to half a dozen environments. It helps me quickly pinpoint differences that aren't expected.
I also like to ability to compare models with each other. We're all looking forward to the future of data modeling with SDDM!
In some ways, SDDM is already ahead in the features department. I can version models in Subversion with the XML files. That’s HUGE!
Maggie Tompkins, USMC

Physical data model

Similar Messages

Maybe you are looking for