P6.2.1 relationship lines

Is there a built-in feature of P6.2.1 to format relationship lines to display diagonally between tasks? I don't like how they "stack" on each other between common pred's and succ's.
Edited by: [email protected] on Apr 6, 2010 11:21 AM

Welcome to the forum :)
Are you talking about the form's object navigator? Or something else..and when you post any thread please mention the version.
-Ammad

Similar Messages

DM 3.0.0.665: Disappearing relationship lines

I am now realizing that also relationship lines are disappearing from my ER Diagrams for no apparent reason.
The relationships are not just not shown, they also affect the "Engineer to Relational Model" function, as the corresponding foreign keys of the relational model also disappear.
It has only happened a few times in my 150 entity model, but it is happening in the current production release.
/ Marc de Oliveira

Yes, I am seeing the relationships on the diagrams when I do "Engineer to relational". I found six relationships on three diagrams that did not engineer to foreign keys, even though all necessary primary keys were in place.
The only way I could make it work was to delete the relationships and recreate them, exactly the same way they were...
Also, these relationships have worked before, as corresponding foreign keys were in place in my relational model. Only when I deleted the foreign keys, I realized that "engineer to relational" did not recreate them...
One of the involved entities had undisplayed sub entities but these were not involved in the relationships.
- Marc de Oliveira

Self-referencing relationship line is non-movable

I am using Version 3.0.0.665 of data modeler. When I create a self-referencing relationship, the relationship line ends cannot be moved. They seem to be fixed. Is this the normal behavior. Any way to make them more flexible.

You can't adjust the size of self referencing lines at the stage. We do have this logged to fix in a future release.
Sue

Data Modeler - How to move relationship lines?

I can't figure out how to move the relationship lines on the data modeler.
Tried a bunch of things that have worked in all the other modelers I've used, but no luck. Couldn't find anything in the help text about it, either.
Edited by: David Wendelken on Nov 14, 2008 4:07 PM

Hi Jim, David,
AutoRoute (on/off) can be managed at diagram level - use right mouse click on empty space.
In current published release (AutoRoute off) - straight lines (only two connection points) cannot be moved. You need intermediate points (at least one) for better arranging. Points (Elbows ) are created using Ctrl+mouse click.
Connection points also can be moved in next EA release.
Philip

4.0EA3 Redrawing of Relationship and FK Lines

Is there a way to tell SDDM not to redraw automatically. I get my diagram the way I want it and then accidentally bump an entity or table and all the lines get redrawn center to center. An undo would be nice.
If there isn't a way I would like to add it as an enhancement request.
Marcus Bacon

Thanks. That is good for the accidental bump but what if I need to stretch an entity/table? Can I turn off auto redraw?
I know others have asked before but please allow us to turn off auto redraw and allow redraw of individual or group elements on demand. Anyone else see this as a desirable feature?
Here is my situation. I have a parent company entity and 12 child lookup entities which have relationships to a child entity, sort of like a fact table. The company entity goes across the top and has 12 relationships to the lookup tables which are placed below the parent and are staggered just enough for the relationship line connection to show. I have to move from 11 of the relationship lines from the center of the lookup entity to the left edge. The company entity also has a relationship to the "fact" entity and each lookup has a relationship to the fact entity which is below the company entity and to the right of the lookup entities.. Now I have a new lookup entity to add but the company entity needs to be stretched just a little to accommodate the new lookup. When I stretch the parent all 12 of the relationship lines to the lookup tables auto redraw to the center of those tables except for the one directly under the company table and I now have to move 12 relationship lines to be able to see the identity and nontransferable graphics. Then I have to repeat the process for the relational model. It should look something like this: If the diagram isn't clear make sure it is in a fixed pitch font.
+----------------------------------+
|                                  |
+----------------------------------+
|    |    |       |            |
|    |    |       N            N
|    |    | +--------+      +----+
|    |    | |        |-----<|    |
|    |    N +--------+      |    |
|    | +--------+           |    |
|    | |        |----------<|    |
|    N +--------+           |    |
| +--------+                |    |
| |        |---------------<|    |
N +--------+                |    |
+--------+                     |    |
|        |--------------------<|    |
+--------+                     +----+

Line item dimensions

hi..
wat is line item dimensions nd cardinal heights???
regards
deepa

Hi Deepa,
Line Item Dimension:
When your dimension table becomes large (>10% of the fact table) then you can make the dimension a "line-item" dimension. The constraint is that the dimension should have only 1 characteristic. By making the dimension as line item the SID values are directly used instead of the Dim ids and the query performance is better.
The disadvantage is that once you make the dimension line -item you cannot add another characteristic to that dimension and you cannot remove the line -item checkmark without deleting the cube data.
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Multi Dimensional modelling will include fact table in center with Dimension tables around it. Overall system performance is greatly affected and dependent on the size of these dimension tables in respect to the fact table. SAP recommends that size of dimension table should be 20% of the size of fact table. In case if this size is more than 40% dimension should be defined high cardinal ( should be supported by database) If dimension tables are more than 40% the dimension should be defined as line item. When dimension is defined as line item, Dim ID in the fact table is replaced with the SID ID, Only one characteristic will be defined in that dimension. This results in improved performace.
Here is how it will work
Fact table
Dim ID1 DIM ID2 DIM ID3 AMOUNT QTY
Dimension Table 1
Sid1 DimID1
Dimension Table 2
Sid 4 Dim ID 2
Dimension Table 3
Sid6 Dim ID 3
Cosidering that Dim1 is too big, We can define Sid 1 in Line Item Dimension and Dim ID 1 is replaced by Sid 1 so fact table will look like this
Sid 1 Dim2 Dim3 Amount Qty
Compounding Attribute is superior object to define characteristic, for example
Plant A manufactures TV
Plant B manufacture TV
The only way to differentiate product can be TV and Plant A
Also,
Cost center 100 can be in Controlling Area A and
Controlling Area B can also have cost center 200,
So Cost center is compounded with CO Area to uniquely identify that line.
Just check this thread line item dimension
Cardinality defines the numeric relationships between occurrences of the entities on either end of the relationship line.
Check this link:
http://www.datamodel.org/DataModelCardinality.html
For cubes -> High Cardinality means that this dimension contains a large number of characteristic values. This information is used in accordance with the individual database platform in order to optimize performance. For example, an index type other than the standard may be used. Generally a dimension is perceived to have high cardinality when the dimension is at least 20% the size of the fact tables in terms of the number of entries each contain. Avoid marking a dimension as having high cardinality if you are in any doubt.
Also refer the below link for Line Item Dim and High Cardinality.
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Check this explanation by pizzman:
Re: High cardinality (CARDHeight) vs Line item
Refer these links on line-item and cardinality:
Line Item Dimension
Re: Line Item Dimension
Cardinality
Re: High Cardinality Flag
****Assign Points If Helpful****
Regards,
Ravikanth

Data Modeler 3.0 / Logical Model / Move relationship names

Hi,
When showing relationship names in the logical model they often appear at a not so good place
(eg two labels at the same location, lable over a table name,lable showing nowhere near his relationship line, etc...)
In the former edition, when the model was still saved as a .xml file we had the possibility to 'move' the labels around
and put them at a more proper place and as such create a solid and clear schema.
In the new version (3.0.0....) it is no longer an xml file but a .dmd file that is created and it is no longer posiible to move the labels (relationship names).
They can only be resized...
The loss of this functionality is ..... making me print the schemas whithout displaying the relationship name (if not the outprint is rather messy)
Is there a way to move the labels?
and if not , will it be re-enabled in a next edition?
reards,
E.

Hello!
I have to follow this thread too.
I use SDDM 3.3 EA2
The autorouting of FKs is great and at the same time annoying. Sometimes the endpoints of FK-Lines stick to entities and you can't move them to a correct position.
Sometimes when you position the FK-lines in a desired postion and you resize the subview the autorouting changes them. Very annoying!
Formating notes is possible but when you open the subview again the format is lost.
Positioning self joins is another 'tearing the rest of my hairs'
And you cannot set the width of borders of entities
And I'd like to have the possibiltiy to change or configure at least 2 or all fields of the legend
To offer something positiv. Thank you very much Philip, for adding the possibilty to change the grid size!
Best wishes
Guenter

Data Model Layout (crossing lines)

Hi Everybody,
I downloaded the SQL Data Model and doing some modeling. It is doing a good job.
How can I adjust the crossing lines in the diagram. I am not able to bend the relationship lines.
Are there any hidden (undocumented) shortcut KEYS to do that?
Where can I find those defined shortcut KEYS?
Do we have an auto layout option to adjust the Entities and relationships in a page?
Thanks in sharing your experience.

Hi,
you need to switch "Auto route" off and you'll be able to position manually the lines.
Do we have an auto layout option to adjust the Entities and relationships in a page?There is limited "auto layout" functionality in relational model but it's not page oriented.
Philip

Multiple relationship modeling

Hello,
I am hitting a bug/issues/misunderstanding on my side with data modeller 4.0.0.833 (I had this issue in the previous versions too).
I was trying to model multiple relationships from a entity to a detail entity and am hitting some problems. I have the following situation (simplified) :
Party Entity : Party ID (PID), Party Name
Transaction Entity : Trans ID (PID), cost (number)
I then create 2 1-to-many relationship from party to transaction:
Party -> Transaction (1 to many)
Party -> Transaction (1 to many)
This creates 2 FKs on the transaction entity called (Party ID and Party ID1). I rename this attributes in the transaction entity as "From Party" and "To Party"
I then do a engineer to relational model.
This then ignores the attribute names in the transaction entity I had given ("From party" and "to party") and creates 2 new columns - "Party_Party_ID" and "Party_Party_ID1".
Is there a way I can preserve the names I had given in the logical model for the FKs when engineered to Physical? Or is this a bug?
Secondly, Is it possible in the Relation properties dialog box (by double clicking the relationship lines in the logical model) in the target cardinality section to select the FKs I had created ("From Party" and "to Party") so that I could document correctly which is the "from" and which is the "to".
Thanks in advance.
AK

Hi AK,
you have 2 options:
1) clear "Apply name translation" check box in engineering dialog
2) use proper setting for naming template and names in your model (as Dimitar suggested) - naming templates are available in design properties dialog>"Settings>Naming standards">templates"
2.1 change naming template for "Column Foreign key" to {relationship}
2.2 Rename your relationships as "From Party" and "To Party"
3.1 Check "Apply name translation" check box in engineering dialog
Philip

4EA3 Bug - Relationship Drawing Tool

On the logical model, when I select the "identifying relationship" drawing tool, i draw one relationship and the pointer remains as a relationship drawing tool but it will not draw another relationship line. In addition, I can select or double click an entity but not a relationship while the pointer icon is a relationship drawing tool. I have to click the identifying relationship drawing tool again to be able to draw another relationship or click the arrow pointer to be able to select or double click a relationship line.

Yep, Ann has the band-aid solution. Unfortunately, it won't cure the disease but it does work to quickly get rid of the symptom.
You might also see this annoying behavior with other tools like offset brush cursors and the path tool. Same (temporary) fix - hit F a couple of times.
-phil

"relationship types and lag" on activity network

Hi,
on activity network diagram , how can I indicate the relationship types and lag time on relationship lines ?
and instead of indicating each relationship line , how it could be drafted in groupped and branchs ?
thanks ,
h.e.

without being nostalgic, since I'm not a huge fan of PERT anyway, the P3 feel and look of the PERT view that you are looking for in P6... is just not there anymore.
no more direct/shared/branched display options for relationships. if it's a huge PERT printout you are interested in maybe (just maybe) it is worth manually positioning activity boxes to better display relationships. quite time consuming and even if you can save the positions in a file it still needs manual adjusting to accomodate changes. reorganising automatically doesn't always help (or rather creates the same mess in P6 as it did in P3 :)
no more labelling relationship lines. although you should get the type from the relationship line itself, they are not always easy to trace (which pretty much defeats the purpose of a PERT chart). also, no way to display relationship lag/lead time.
as I said, I do not use PERT much. I don't find it very practical in terms of overall look on fairly small screens/ print formats for most real-life projects.
sure, it looks great for really straightforward logic (?), low complexity projects (?) or very detailed WBS analysed one at a time. but then, whats's the point..
I suggest you try Table + Gantt + Trace logic instead. the combination of network logic and schedule info sharing the screen much more efficiently is a better compromise for a working layout, if you ask me.
best of luck,

Some contraints are not displayed in modeler

Hello,
I imported a set of tables into the modeler that is in Jdeveloper. There are some foreign key constraints that are not being displayed with a line although the constraint is there if I look at the table's properties.

Hello,
Answers to your questions:
-Oracle DB: 9.2.0.1.0
-Server OS: Win 2000/Server, updated all service packs
-Jdeveloper: 10g == 9.0.5.1 (build 1605)
-I use the import wizard to get all of the tables imported to a off-line set at the same time.
-Yes, the tables were all imported at the same time.
The schema is propietry, so I can't not release it. It would take me quite bit of effort to remove the propietry information, so I don't think I'll be able to provide the code. If I have free time in a week or so, I'll consider shrubbing it and sending it to you.
Anyways, here is a descrption ofthe behavior of Jdeveloper when the error ocurrs, a simple description of the DDL, and details on the constraints on the tables where the problem occurs:
1) I use the import wizard to get all of the tables imported to a off-line set at the same time. Sometimes a table will get imported without a tablename. Sometimes a blank line is in the list of table names, but all of the tables are there. When the blank line error occurs I get the problem with the missing relationship line in the diagram.
2) Create blank diagram.
3) Select all tables. Since there is a blank line in the list of table names, I have to use the control key to select all of the tables.
4) Drag all of the selected tables onto the diagram.
5) Only one relation is does not display in the diagram with a line although the details of the relation is there if I look in the properties for the table. The relationship that has the problem is a foreign key relationship from a table A to table B named PRE_SMD_FK that is listed below. Table A is different from other tables in the schema because it has a circle constraint which is also listed below.
DDL is about:
~40 tables
~20 in a star configuration
~19 tables linked in almost a chain
1 table has no relationships
ALTER TABLE B
ADD (CONSTRAINT SME_PK PRIMARY KEY
(ID))
ALTER TABLE B ADD (CONSTRAINT
SMD_STD_FK FOREIGN KEY
(SYSTEM_VERSION) REFERENCES C
(SYSTEM_VERSION) ON DELETE CASCADE)
ALTER TABLE A
ADD (CONSTRAINT P_PK PRIMARY KEY
(ID))
ALTER TABLE A ADD (CONSTRAINT
PRE_SMD_FK FOREIGN KEY
(ID) REFERENCES B
(ID) ON DELETE CASCADE)
ALTER TABLE A ADD (CONSTRAINT
P_P_FK FOREIGN KEY
(PARENT_ID) REFERENCES A
(ID) ON DELETE CASCADE)
ALTER TABLE A ADD (CONSTRAINT
P_P_FK FOREIGN KEY
(PARENT_ID) REFERENCES B
(ID) ON DELETE CASCADE)

Oracle SQL Data Modeler -COMPARE/MERGE

Hi all,
I am trying to compare/merge or just trying to merge a relation model with another in Oracle SQL Developer DATA MODELER.
Scenario:
I have tried to import from data dictionary the hr schema into 3 parts.
Table employee is alone imported in one design model's relational model(say DataModelerDesign1- DMD1).
Table Departments,Locations and Countries in another design model's relational model(say DMD2).
Table Job_history,Jobs and Regions in another design model's relational model(say DMD3).
Now, I tried to merge all this into one design model's relational model, here into DMD3.
Requirement:
I want all of this relational model's tables to get merged with exact mappings as if it is in HR schema all connected to each other. But they are all getting merged as separate entities not conencted to each other when taken from Compare/merge option. How should i do this task?
Issues:
1) I can never see anything in the compare model when i try to click on view compare mapping. Can anytime we see any data here?
2) In realtime scenario, when will we try to merge a table into another or split it. Because some foriegn key violations are happening here. Is it ever possible to succeed our requirement while merging itself instead of creating relationships between entities manually in main relationship model DMD3 in example here.

I have found on occasions the diagram pdf would be missing a few relationship lines. Usually it happens after I have been doing a lot of work in the tool or printing a bunch of diagrams. Seems to be a memory leak of some sort. If I close Data Modeler, re-open it, then print to PDF, the diagram is fine.

Cardinal - Dimensions

What does it mean by cardinality ? What is Cardinal dimensions
line item dimensions ?
How do these effect on the way we model the dimensions?
Thanks

Hi,
Cardinality defines the numeric relationships between occurrences of the entities on either end of the relationship line.
Check this link:
http://www.datamodel.org/DataModelCardinality.html
For cubes -> High Cardinality means that this dimension contains a large number of characteristic values. This information is used in accordance with the individual database platform in order to optimize performance. For example, an index type other than the standard may be used. Generally a dimension is perceived to have high cardinality when the dimension is at least 20% the size of the fact tables in terms of the number of entries each contain. Avoid marking a dimension as having high cardinality if you are in any doubt.
Also refer the below link for Line Item Dim and High Cardinality.
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Check this explanation by pizzman:
Re: High cardinality (CARDHeight) vs Line item
Refer these links on line-item and cardinality:
Line Item Dimension
Re: Line Item Dimension
Cardinality
Re: High Cardinality Flag
Bye
Dinesh

Retrieve HRTMC_PPOM succesor comment text.

Hi All,
In the transaction code HRTMC_PPOM, how can we retrieve the comment text in succesor tab in ABAP?
Please advise.
Thanks!
Regards,
Nickcy.

Hi Nick,
You could proceed as below:
1) Get Successor for position from HRP1001 (Relationsip B740)
2) From relationship line ADATANR, get the document class and id.
Refer Include LHRTMC_PPOMREL method get_current_comments Lines 1551 to 1556
loop at <lt_relationships> assigning <ls_relationship_wa>.
      assign component gc_additional_data_fieldname of structure <ls_relationship_wa> to
<ls_relationship_padnnn_wa> casting type (gv_relationship_padnnn_name).
      assert sy-subrc = 0.
      move-corresponding <ls_relationship_padnnn_wa> to <ls_padnnn_wa>. " to correctly initialize values (assign
does not take care of it)
      append <ls_padnnn_wa> to <lt_padnnn_table>.
    endloop.
3) Get Text based on Document class and id as below:
Refer Include LHRTMC_PPOMBUF method get_comment Lines 259- 272
ls_comment_key_wa-class = iv_document_class.
        ls_comment_key_wa-objid = iv_document_id.
        append ls_comment_key_wa to lt_comment_keys.
        lv_rfc_destination = get_rfc_destination(
          iv_plan_variant = iv_plan_variant
          iv_object_type = iv_object_type
          iv_object_id    = iv_object_id ).
        create object lo_message_handler.
        cl_hrtmc_document_utils=>get_content_of_texts(
          exporting it_texts           = lt_comment_keys
                    iv_rfc_destination = lv_rfc_destination
                    io_message_handler = lo_message_handler
          importing et_contents        = lt_comment_texts
                    ev_is_ok           = lv_is_ok ).
Regards, Zen

P6.2.1 relationship lines

Similar Messages

Maybe you are looking for