How to create Parent Child relationship of Assets

Hi All
can any one provide the solution for the below mention requirment.
Problem Description: How to create Parent Child relationship of Assets in below case.
1. If asset Category of Child assets are different but both parent & child assets are already capitalized.
2. If asset Category of Child assets are same but both parent & child assets are already capitalized.
3. If asset Category of Child assets are same for new assets.

Similar Messages

How to model parent child relationship with DPL? @Transient?

Hello All,
I want to model a parent entity object with a collection of child entities:
@Entity
public class Parent{
@PrimaryKey
String uuid;
List<Child> children;
@Entity
public class Child{
@PrimaryKey
String id;
I know that the DPL won't support automatic persistence where it'll recursively go through my parent bean and persist my children with one call. Is there a way of applying the equivalent to JPA's @Transient annotation on "children" so I can persist the children manually and have the engine ignore the collection?
If not and I want to return to the user a Parent with a List named "children," do I have to create a new object which is identical to Parent, but doesn't have the BDB annotations and manually assemble everything? If possible, I'd like to avoid defining redundant objects.
Thanks in advance,
Steven
Harvard Children's Hospital Informatics Program
Edited by: JavaGeek_Boston on Oct 29, 2008 2:22 PM

Hi Steven,
The definition of persistence is here:
http://www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/persist/model/Entity.html
And includes this: "All non-transient instance fields of an entity class, as well as its superclasses and subclasses, are persistent. static and transient fields are not persistent."
So you can use the Java transient keyword. If that isn't practical because you're using transient in a different way for Java serialization, see the JE @NotPersistent annotation.
In general a parent-child relationship between entities is implemented almost as you've described, but with a parentId secondary key in the Child to index all children by their parent. This enables a fast lookup of children by their parent ID.
I suggest looking at this javadoc:
http://www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/persist/SecondaryIndex.html
as it describes all types of entity relationships and the trade-offs involved. The department-employee relationship in these examples is a parent-child relationship.
--mark

How to achieve parent-child relationship using self join?

my table structure is as follows
parent child name
-1     1     A1
1     2     A2
1     3     A3
how to achieve the hierarchy model using self join. this can be easily achieved using "connect by prior". but how to achieve the same using self join?

Hi,
Yes, that's definitely possible. If you only need to display two levels from the hierarchy, a self-join is a good option. Make it an outer join if you need to show everyone on one level, regardless of whether they have a match on the other level or not; for example, if you want the output:
child_name     child_id     parent_name     parent_id
A1          1
A2          2          A1          1
A3          3          A1          1It's good that you posted some sample data. Now post the results you want from that data, and your query (what you think is the best attempt you've made so far). If you haven't tried anything so far, then look at some other simple self-join to get ideas.

How do I create parent/child relationship between objects? so that if I change one, I change all

I have multiple instances of an object, and I would like to make any changes that I put on one of these objects to perpetuate and change on the other instances of the object

turn your object into a symbol, and place multiple instances of it on the artboard, when you edit the symbol all instances will update.

How to know 'parent-child relationship' of equipments

Hello experts,
I am currently having a problem here. How can I know if a certain equipment has a child/subordinate equipemt under it? for example, I typed in the value 000000345534 for the 'ILOAN' field in EQUZ table to get it's EQUNR and HEQUI. Now, where can I know if it has a child equipment under it? for example:
12610 (highest primary)
12611
12612 (subordinate and primary)
12613
Also, I have to display it in the report output like this:
ASSET    PARENT   DESCRIPTION LOCATION NETBOOK VALUE

Hi,
I had developed a code wherein I had a similar scenario.Please refer the same. Will give you an idea.
FORM link.
SKIP 2.
ULINE.
WRITE : / 'Link b/w Transform No and Conn. No' COLOR 6
INTENSIFIED ON.
ULINE.
TABLES:
        iflo.
INCLUDE <line>.
**Data type declaration
DATA: BEGIN OF h_iflo_sel OCCURS 0,
            tplnr LIKE iflo-tplnr.
DATA: END OF h_iflo_sel.
DATA : i_iloa1 LIKE TABLE OF iloa WITH HEADER LINE,
          i_iloa2 LIKE TABLE OF iloa WITH HEADER LINE.
DATA : BEGIN OF t_inet,
          kante LIKE inet-kante,
          eqnach LIKE inet-eqnach,
          END OF t_inet.
DATA: BEGIN OF h_iflo_tab OCCURS 0.
          INCLUDE STRUCTURE iflo.
DATA: END OF h_iflo_tab.
*For Final Display.
DATA : BEGIN OF i_final OCCURS 0,
            data(30) TYPE c,
            desc(40) TYPE c,
          END OF i_final.
DATA : BEGIN OF i_finalitab OCCURS 0,
            eqvon LIKE inet-eqvon,
            eqnach LIKE inet-eqnach,
            eqtyp LIKE equi-eqtyp,
            eqktx LIKE eqkt-eqktx,
            tplnr LIKE iflo-tplnr,
            pltxt LIKE iflo-pltxt,
            kunum LIKE zconnection-kunum,
            END OF i_finalitab.
DATA : BEGIN OF i_eqkt OCCURS 0.
          INCLUDE STRUCTURE eqkt.
DATA : END OF i_eqkt.
DATA : i_iflo LIKE TABLE OF iflo WITH HEADER LINE,
         i_zconn LIKE TABLE OF zconnection WITH HEADER LINE,
         i_kna1 LIKE TABLE OF kna1 WITH HEADER LINE,
         i_equi LIKE TABLE OF equi WITH HEADER LINE,
         i_inet LIKE TABLE OF inet WITH HEADER LINE.
DATA : var TYPE i VALUE 2,
         count TYPE i VALUE 0,
         tempcount TYPE i VALUE 0,
         lv_index LIKE sy-tabix,
         flag(5) TYPE c VALUE 'ODD' .
DATA : kante LIKE inet-kante,
            eqvon LIKE inet-eqvon,
            eqnach LIKE inet-eqnach.
DATA: equnr LIKE zconnection-equnr.
*Fetching the transformer no and the Connection no
SELECT a~kante a~eqvon a~eqnach
          INTO CORRESPONDING FIELDS OF TABLE i_inet
          FROM ( inet AS a
          INNER JOIN zconnection AS b ON a~eqnach = b~equnr )
          WHERE a~eqvon = dy_equnr.
LOOP AT i_inet.
    MOVE i_inet-eqvon TO i_finalitab-eqvon.
    MOVE i_inet-eqnach TO i_finalitab-eqnach.
    APPEND i_finalitab.
ENDLOOP.
LOOP AT i_finalitab.
*Fetching the Functional Location for Connection number
    CALL FUNCTION 'EQUIPMENT_READ'
         EXPORTING
              equi_no = i_finalitab-eqnach
         IMPORTING
              eqkt    = i_eqkt
              iloa    = i_iloa1.
    MOVE i_iloa1-tplnr TO i_finalitab-tplnr.
    MOVE i_eqkt-eqktx TO i_finalitab-eqktx.
    MODIFY i_finalitab.
ENDLOOP.
* Fetching desc of func location of conn no
SELECT * FROM iflo
                  INTO TABLE i_iflo
                  FOR ALL ENTRIES IN i_finalitab
                  WHERE tplnr = i_finalitab-tplnr.
LOOP AT i_finalitab.
    READ TABLE i_iflo WITH KEY tplnr = i_finalitab-tplnr.
    IF sy-subrc = 0 .
      MOVE i_iflo-pltxt TO i_finalitab-pltxt.
      MODIFY i_finalitab.
    ENDIF.
ENDLOOP.
* Fetching the customer no's for each connection no in Z table
SELECT   * FROM zconnection
                INTO TABLE i_zconn
                FOR ALL ENTRIES IN i_finalitab
                WHERE equnr = i_finalitab-eqnach.
LOOP AT i_finalitab.
    lv_index = lv_index + 1.
    READ TABLE i_zconn WITH KEY equnr = i_finalitab-eqnach.
    IF sy-subrc = 0.
      MOVE i_zconn-kunum TO i_finalitab-kunum.
      MODIFY i_finalitab.
    ENDIF.
ENDLOOP.
*Fetching the equipment category for each conn no
SELECT * FROM equi
           INTO TABLE i_equi
           FOR ALL ENTRIES IN i_finalitab
           WHERE equnr = i_finalitab-eqnach.
LOOP AT i_finalitab.
    READ TABLE i_equi WITH KEY equnr = i_finalitab-eqnach.
    IF sy-subrc = 0.
      MOVE i_equi-eqtyp TO i_finalitab-eqtyp.
      MODIFY i_finalitab.
    ENDIF.
ENDLOOP.
*Fetching the Functional Location for Transformer number
CALL FUNCTION 'EQUIPMENT_READ'
       EXPORTING
            equi_no = dy_equnr
       IMPORTING
            eqkt    = i_eqkt
            iloa    = i_iloa2.
*For Fetching the description of the func loc. of Transformer Number
REFRESH i_iflo.
SELECT SINGLE * FROM iflo
                  INTO i_iflo
                  WHERE tplnr = i_iloa2-tplnr.
*Moving into the final internal table .
MOVE dy_equnr TO i_final-data.
MOVE i_eqkt-eqktx TO i_final-desc.
APPEND i_final.
MOVE i_iloa2-tplnr TO i_final-data.
MOVE i_iflo-pltxt TO i_final-desc.
APPEND i_final.
*For finding the superior functional location.
REFRESH h_iflo_sel.
MOVE i_iloa2-tplnr TO h_iflo_sel-tplnr.
APPEND h_iflo_sel.
*Finding the Superior Func. Location until it reaches the top.
h_iflo_tab-tplma = '1'.
DO 100 TIMES.
    IF h_iflo_tab-tplma <> ' '.
      REFRESH h_iflo_tab.
      CALL FUNCTION 'FUNC_LOCATION_ARRAY'
           EXPORTING
                selfield     = 'TPLNR'
                spras        = sy-langu
                tabstructure = 'IFLO'
           TABLES
                iflo_sel     = h_iflo_sel
                iflo_tab     = h_iflo_tab.
      IF h_iflo_tab-tplma <> ' '.
*To find the above func .location
        REFRESH h_iflo_sel.
        MOVE h_iflo_tab-tplma TO h_iflo_sel-tplnr.
        APPEND h_iflo_sel.
*For Fetching the description of the func loc. of Transformer Number
        REFRESH i_iflo.
        SELECT SINGLE * FROM iflo
                        INTO i_iflo
                        WHERE tplnr = h_iflo_tab-tplma.
*Moving the values into the final internal table
        MOVE h_iflo_tab-tplma TO i_final-data.
        MOVE i_iflo-pltxt TO i_final-desc.
        APPEND i_final.
      ENDIF.
    ELSE.
      EXIT.
    ENDIF.
ENDDO.
*Displaying in a tree structure
IF NOT i_final[] IS INITIAL.
    DESCRIBE TABLE i_final LINES count.
    tempcount = count.
    DO tempcount TIMES.
      READ TABLE i_final INDEX count.
      count = count - 1.
      WRITE: i_final-data COLOR 4 INTENSIFIED ON.
      WRITE: i_final-desc.
      IF count <> 0.
        WRITE:/var sy-vline NO-GAP.
        ULINE :/var(8).
        var = var + 9.
      ENDIF.
    ENDDO.
ENDIF.
SKIP.
* Displaying the Customer no's.
WRITE : /'Transformer no'COLOR 7 INTENSIFIED ON,18(18)
        'Connection no'COLOR 7 INTENSIFIED ON,37(3)'Cat'COLOR 7
        INTENSIFIED ON,41(40)'Connection desc'COLOR 7 INTENSIFIED ON,
        81(42) 'Connection Object'COLOR 7 INTENSIFIED ON,123(40)
       'Conn Obj Desc'COLOR 7 INTENSIFIED ON,
        163(10)'Customer'COLOR 7 INTENSIFIED ON.
IF NOT i_finalitab[] IS INITIAL.
    DESCRIBE TABLE i_finalitab LINES count.
    tempcount = count.
    DO tempcount TIMES.
      READ TABLE i_finalitab INDEX count.
      count = count - 1.
      SKIP.
WRITE: / i_finalitab-eqvon COLOR 4 INTENSIFIED ON, i_finalitab-eqnach
           COLOR 5 INTENSIFIED ON,i_finalitab-eqtyp COLOR 4 INTENSIFIED
                     ON, i_finalitab-eqktx, i_finalitab-tplnr
    ,i_finalitab-pltxt
    ,i_finalitab-kunum.
    ENDDO.
ENDIF.
ENDFORM.
Regards,
Gayathri

How to use GL Parent Child relationships in Discoverer?

Subject: How to used GL Parent Child relationships in Discoverer?
How to use GL Parent Child relationships in Discoverer?
Please let me know how to incorporate the parent -child relation ships exsiting in GL Accouting flexfield Segments in Discoverer for drill downs? we have GL - BIS views installed.
How to create the specific Parent -child relationship hierarchies in Discoverer from the FND_* tables?
Please help.
Thanks.
KS.

Hi,
I'm also trying to implement this. If you have come any further in solving this any hints would be much appreciated...
regards,
AJ

How do I identify parent/child relationship

How do I identify parent/child relationship in Designer?

turn your object into a symbol, and place multiple instances of it on the artboard, when you edit the symbol all instances will update.

How to output the outline parent-child relationship using a report script?

I'd like to extract the outline's dimension members with it's parent-child relationship using a report script. Anybody can provide a sample script? Thanks.
Example:
DimensionX
-----MemberX
----------ChildX
Output:
Dimension X MemberX
MemberX ChildX
Edited by: obelisk on Jan 11, 2010 5:16 PM

Sorry a report script won't do it. You have two options
1. Use at Essbase Outline API to walk the outline and get it for you
2. Use the Outline extractor available from Applied Olap (it is a free download). It can be run interactively of as a bat file.
Frankly, I would rather use 2 since I don't have to code it myself

Parent-Child Relationships in Essbase Studio

In Essbase Studio, I am defining a hierarchy in which a parent member (Wholesaler) is from one dimension table and child member (Rep) is from another. When I preview this hierarchy or build an outline to include it, a few of the Reps that should rollup to a certain Wholesaler are missing. They are not dropped, but Essbase Studio just never recognizes these Reps as being children of that Wholesaler in the first place. However, if I run a sql query against the source data mart with the correct joins, these missing reps do show up in the records of that Wholesaler. Also, the missing Reps are showing up fine in the hierarchy preview as long as I don't make them children of anything in the Wholesaler dim. So Essbase Studio is able to see these Reps, but just can't figure out how they are related to the given Wholesaler. Again, this is only happening for about 10% of the Reps for the Wholesaler. Other Reps are showing up fine in the parent-child relationship.
In the source data mart, I don't see any NULLs or anything amiss in the records for the missing Reps. What other reasons would Essbase Studio not recognize a particular joined record?

it really does sound like a join issue. You say if you just load the children without the parent, they load, but if you associte them to the parent, they don't. You might try when creating the joins to do a full outter join to see if they load and to what.
One other thing you could try would be to create a user defined table that has the join in it. I've found data atype issues in joins from different tables before. Studio is very pickey about this
Edited by: GlennS_3 on Oct 20, 2010 9:12 AM

Function to get the path using a parent-child relationship

Hello,
I have a table which uses parent-child relationship to store the options available. I need a function to give me the full path given the id of a particular option.
I have two different functions. One of them uses the Oracle built in function and the other uses simple queries with a loop.The code of the functions are given below.
Now, the problem is with their "performance". The difference in their performance is significant. The function using the Oracle function takes more than 2 hours to run a query whereas the other function takes less than 2 minutes.
I am having trouble trusting the other function. No matter how many tests I perform on the output of both the functions, it always comes out to be the same.
Any thoughts to help me understand this ??
Function 1
=====================
FUNCTION Gettree (opt_id IN NUMBER,i_app_id IN NUMBER)
RETURN VARCHAR2
IS
path VARCHAR2(32767);
application_no NUMBER;
BEGIN
SELECT ABC.APP_OPT_ID INTO application_no FROM ABC
WHERE ABC.APP_ID = i_app_id AND ABC.PARENT_ID IS NULL;
SELECT LPAD(' ', 2*LEVEL-1)||SYS_CONNECT_BY_PATH(app_opt_name, '=>') "Path" INTO path
FROM ABC
WHERE app_opt_id = opt_id
START WITH parent_id =application_no
CONNECT BY PRIOR app_opt_id =parent_id;
path := SUBSTR(path,INSTR(path,'>')+1,LENGTH(path));
RETURN path;
END Gettree ;
Function 2
======================
FUNCTION GetOptPath(opt_id NUMBER,app_id NUMBER)
RETURN VARCHAR2
IS
string VARCHAR2(900);
opt VARCHAR2(100);
pid NUMBER(38);
BEGIN
SELECT ABC.parent_id,ABC.app_opt_name INTO pid,string FROM ABC WHERE ABC.app_opt_id = opt_id;
IF pid IS NULL
THEN
RETURN 'root';
ELSIF pid IS NOT NULL
THEN
LOOP
SELECT ABC.app_opt_name,ABC.parent_id INTO opt, pid FROM ABC WHERE ABC.app_opt_id = pid;
EXIT WHEN pid IS NULL;
string := opt || '=>'|| string;
END LOOP;
RETURN string;
END IF;
END;

Hi,
user8653480 wrote:
Hello Frank,
The parameters taken by gettree & getoptpath are app_opt_id and app_id and both the functions return only one string i.e. the path of that particular option (app_opt_id) starting from its root and not all the descendants of that option/root node of that option.
So, does that mean that gettree first fetches all the descendants of the root node of the given option and then returns the required one ??Yes. It's a little like the situation where you need to meet with your co-worker Amy, so you send an e-mail to everyone in the department telling them to come to your office, and then, when they arrive, tell everyone except Amy that they can leave.
>
And if that is the case, then won't it be better to use the bottom-up approach to fetch the required path just for that particular option ?? 'coz my requirement is that only.. given an option_id get the full path starting from the root.Exactly!
I have used explain plan also for both the functions.. but since I did not know how to anlayze the output from plan_table so I just compared the value in the fields and they were exactly the same for both the queries.If you'd like help analyzing the plans, post them, as Centinul said.
I am attaching a sample data with the outputs of both the functions for the reference.
(tried attaching the file but could not find the option, so pasting the data here)
App_opt_ID     App_ID     Parent_ID     App_opt_name     "gettree(app_opt_id,app_id)"     "getoptpath(app_opt_id,app_id)"
1          1     NULL          application          NULL                    root
2          1     1          module1               module1                    module1
3          1     1          module2               module2                    module2
4          1     2          submod1               module1=>submod1          module1=>submod1
5          1     3          submod1               module2=>submod1          module2=>submod1
6          1     5          opt1               module2=>submod1=>opt1          module2=>submod1=>opt1
7          2     NULL          app2               NULL                    root
8          2     7          scr1               scr1                    scr1
9          2     8          opt1               scr1=>opt1               scr1=>opt1
10          2     7          scr2               scr2                    scr2Please help.The best solution is to do a bottom-up query, and write a function like reverse_path (described in my first message) to manipulate the string returned by SYS_CONNECT_BY_PATH. You seem to have all the PL/SQL skills needed for this.
Another approach is a revised form of gettree, like I posted earlier. Does it do what you want or not?
If you'd help, then post a little sample data in a form people can actually use, such as CREATE TABLE and INSERT statements. Post a few sets of parameters, and the results you need from each set, given the sample data posted.

Master Detail - Detail parent child relationship

Hello All,
I have a setup where I have 3 tables. Call them A, B, and C. Table A is the parent table to the child table B. Also table B is the parent table to the Child table C. Is there a way to represent this in Apex? So far I have created two Master Detail forms: Master Detail form one has the relationship A+B and Master Detail form two has the relationship B+C. Can Apex support a Master Detail Detail form.
Also, is there a way to have my detail page editable without linking to another page to save and update?
Please let me know what everyone thinks.
Thanks
Ryan

Hi,
You can google it - so much information is available online. Any how
Parent Child relationship
PK FKBasic example - Parent and Child in real life -similarly the Table_A is having relation with some other Table_B.
Example
Table_A
columns :-
Student_No, Student Name, Student_address
Now the Table_B store the assignment details
Student_No, Subject_1,subject_2, subject_3
Now relation of join is Table_A.Student_No = Table_B.Student_No
With out the TAble_A details -can be identified the Sudent details etc., No - It's Master data - which is not dependent on any other table and Column Student_No- Acts Primary Key which is Unique -through which we can identify a specific details of particular student. Now comes to Table_B - with out the student_No - we can't say whose details of assignments belongs to whom - now the student_No in Table_B is dependent on some other table - now this table acts a child and Primary Key of Table_A acts Foreign Key - that column helps to identify the record.
Master Detail
Reference tablesconcept of understanding is same when - when comes c,c++, java and c sharp - acts the same but inheritance, interfaces, polymorphisms and overloading code of language differs. If you go further j2ee differs
HTH
- Pavan Kumar N
Oracle 9i/10g - OCP
http://oracleinternals.blogspot.com/

Find parent/child relationships At More Than 2 Levels

Hello,
Does anyone have a solution to find parent/child relationship for data more than 2 levels deep?
I have a solution when there's a simple parent-child relationship but not when there's a grandparent-parent-child relationship or deeper.
Ex. I have a table company_parent_child that stores the relationship betwen a company and it's direct parent.
create table TEMP_COMPANY_PARENT_CHILD
PARENT_ID NUMBER(10),
COMPANY_ID NUMBER(10)
insert into TEMP_COMPANY_PARENT_CHILD values (1, 10);
insert into TEMP_COMPANY_PARENT_CHILD values (1, 11);
insert into TEMP_COMPANY_PARENT_CHILD values (1, 12);
insert into TEMP_COMPANY_PARENT_CHILD values (2, 13);
insert into TEMP_COMPANY_PARENT_CHILD values (10, 100);
insert into TEMP_COMPANY_PARENT_CHILD values (10, 101);
insert into TEMP_COMPANY_PARENT_CHILD values (10, 102);
insert into TEMP_COMPANY_PARENT_CHILD values (11, 103);
1->
___10->
______100,101,102,
___11->103
Companies 100, 101 and 102 are under parent 10 and grandparent 1.
I need to create such a view or another temp table so that when I pass the parent ID, I will pull all the children on all levels. In addition, and this is the tricky part, when I join this new temp table or view to another data table without any parameters, the data should not be duplicate, ie. each company ID should appear only once.
create table TEMP_JOIN
company_id number(10),
order_id varchar2(10)
insert into TEMP_JOIN values (100, 'a');
insert into TEMP_JOIN values (101, 'b');
insert into TEMP_JOIN values (102, 'c');
insert into TEMP_JOIN values (103, 'd');
insert into TEMP_JOIN values (10, 'e');
insert into TEMP_JOIN values (11, 'f');
insert into TEMP_JOIN values (12, 'e');
insert into TEMP_JOIN values (13, 'f');
Thanks.

start by learning CONNECT BY/START WITH. once you've
written a query to read the grandparent-parent-child
relationship, then come back with more questionsYes. we did look heavily into connect by/start with, in fact along with "connect_by_iscycle","connect_by_isleaf","connect_by_root" as well.
Our dilemma is that when a joint is made between those two tables mentioned above TEMP_COMPANY_PARENT_CHILD and TEMP_JOIN, we are not able to create a view that would contain distinct company_ids, each mapped to a unique order id.
The problem is we cannot have this type of joint when there are "n" level relationship between companies (or company_id). Basically, I think we should have our unique order id mapped to a unique key. This unique key should be a specialized key that we can know at anytime the entire path of the ancestry which we can know by sys_connect_by_path(company_id,'/') path.
How do we know which path to take. The best bet is to "connect_by_isleaf" and just have the distinct "deep" path which form the specialized unique key. If you need help on this let me know. (A hint, sort by LEVEL and then do a rank after partitioning by company id and then filter the records by rank = 1, try this one!!!)
So, we will eventually have a joint (say Table X) like
PATH ORDER_ID
/1/10/100 a
/1/10/101 b
/1/10/102 c
/1/10 e
/1
/1/11/103 d
/1/11 f
I think this is the best view we can have to maintain a joint with no repetition along PATH as well as ORDER_ID. If you have any other thoughts, let me know.
Then you query by path using INSTR to pull records by company_id.
for example, if you want to get all the children for company_id "10" you would just say
select * from X where INSTR(PATH,10,1,1) <> 0
or if you want to get all the children for company_id "11" you would just say
select * from X where INSTR(PATH,11,1,1) <> 0
What do you think? Has anyone used the path information for traversing the tree? Or is there any article that tells us how to make effective use of sys_connect_by_path(company_id,'/') path.
Thank you. Hope it made sense!

Circular Parent-Child relationship among widgets.

I am trying to draw a Bar Graph on a panel which in turn sits on the main
window. The height policy of the panel widget is set to SP_TO_PARENT so that
when the window is resized the panel is also resized according to the parent
window. I have a situation that every time the panel is resized I need to
scale the Bar Graph in accordance with the new panel size and draw it. But
before drawing the newly scaled Bar Graph I am clearing out all the children
of the panel ( I am doing this just to refresh the panel) and then drawing
the newly scaled Bar Graph. But this does not work!!! I still find some
left over from the previous Bar Graph!!! Any help in this matter is greatly
appreciated.
Also I don't understand this circular parent-child relationship. If I assign
a NIL to Parent attribute of all the children of the panel, what will happen
to the Children attribute of the panel? Won't there be any memory leak by
adopting the above procedure of disconnecting a child from its parent? If
so, how do we take care of it?
Thanks in advance!
Alaiah Chandrashekar
The following is the segment of the code which could be useful for clarity:
// Draws the Bar Graph for the first time.
self.ShowChart(TestData);
self.Open();
event loop
when task.Shutdown do
exit;
// When the window is resized
// I am scaling the Bar Graph for the new
// panel size.
when self.window.AfterReSize do
self.ClearChartPanel();
// self.window.UpdateDisplay();
self.ShowChart(TestData);
end event;
self.Close();
Method ClearChartPanel is as follows:
for child in self.<ChartPanel>.Children do
child.Parent = NIL;
end for;

Hello Evandro,
I am listing the steps to create a relationship manually.
1. Create 2 records in the relationship table in console, one for "Married to" and the other one for "Owner". In order to do that the repository needs to be unloaded.
2. Once you create these 2 records in the table through console, load the repository.
3. Log on to the Data Manager.
4. Now as per your example, there are 3 records in the main table, namely
     JOHN
     MARY
     ACME
5. Select only one record in the record list area e.g. JOHN (where you see the list of records)
6. Then, in the record edit area, double click on the relationship tab,
7. New Window opens up.
8. HERE ALL THE OPTIONS ARE GRAYED OUT. But Select the relationship which you want to create, in our case married to.
9. Now select the record MARY in the record list area. (NOT in the pop window, but main window).
10. Then on the top bar menu, select Relationships --> Adds to Group.
11. Now close the Pop window and observe that the relationship has been created between JOHN and MARY.
Let me know if it worked for you. if not, post some more information about your problem such as where you tried to configure and what options were grayed out.
Please update.
Thanks
Shai
I need to do a relationship among the BP where each record in Main Table correspond a BP (Person or Organization).
The relationship should link the BPs as shown below:
Records
1; John
2; Mary
3; ACME
In record 1, I need to say that John is married with Mary, where Married is a type of the relationship and that Mary is Owner of the ACME, where u201COwneru201D is other relationship type.
I have tried to configure a Relationship (where the parent and child tables were the Main Table) in MDM, but I couldnu2019t to do it because the screen for this feature was locked. I need to be certified that the child link exist in the repository.
Thank you.
Evandro.

Material with Parent Child Relationship

Hi,
Need some advise.
We have this scenario, use purchased materials (.e.g Computer bundle with mouse, monitor and keyboard). We need to track these components separetely at different cost and update inventory with serial no.
Upon creating Sales Order for the above materials, how to we ensure that the full set of materials is picked and delivered. As each components has it own material code.
Is there possible to link up these materials with some sort of parent child relationship? And how to handle it in SAP MM and SD moduld.
Thank you.

Peck,
Unless I am missing something, this is not a Materials Management issue, it is a Sales/Distribution issue.
I think the easiest way is to check the 'complete dlv.' (Complete Delivery) checkbox on the Sales order (VA02>Sales Tab).
When this flag is set, none of the items in the sales order can be confirmed unless all of them are confirmed. All confirmations must be for the same day. No delivery can be created unless all items are deliverable.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/dd/560602545a11d1a7020000e829fd11/frameset.htm
Rgds,
DB49

Reverse Engineering fails to "identify" parent - child relationship

Using Reverse Engineering I obtained two classes - visual compapesence clearly shows that one is inherited from another.
I wish I could copy and paste individual "class Diagrams' for each of those two to demonstrate my point ...
How I could merge those two class diagrams together and "force"
to recognize "parent" <-> child relationship /

On possible solution is to create a diagram in each pacakge that was reverse engineered.
I agree with peter, that a single diagram would not be useful when revese engineering a large project. When diagram get that large, it is hard to see more than a couple of model elements at one time. While we do have the Navigate Link tool, it is still painful to navigate around the diagram. If you printed a diagram that big, it would take up an entire wall.
It is hard to determine what diagrams are needed to explain a software project. For this reason, we have tried to make it easy to build diagrams. Peter, mentioned the first mechanism. Create Diagram From Selected (CDFS) was designed to allow the user to select the model elements that need to populate a diagram. When performing CDFS the diagram will be populated, Relationship Discovery will be executed, and the diagram will be layed out.
Another approach is to create a dependency diagram. You can select a model element, and create a dependency diagram. The contents of a dependency diagram will be the model elements that the selected model element uses. For example, if the model element generalizes from another model element, the super class will be present on the diagram. If another model elements extends the selected model element, the subclass will not be represented on the dependency diagram.
Another diagram creation tool that might be needed is a inheritance diagram creator. An inheritance diagram creator, would make it very easy to see model element super classes, implemented interfaces, and the subclasses.
I hope this helps.

How to create Parent Child relationship of Assets

Similar Messages

Maybe you are looking for