Sorting a List on Parent Child Relationship

I have to sort a list on Parent Child relation
say
I have a following list
Object(Id,ParentId,.........)
obj1(1,1,........);
obj2(2,1,........);
obj3(3,3,........);
obj4(4,1,........);
obj5(5,3,........);
obj6(6,1,........);
obj7(7,3,........);
obj8(8,4,........);
Logic is such that
If Id and Parent Id is same then It is Parent Record
I want the Result like
obj1(1,1,........);
obj2(2,1,........);
obj4(4,1,........);
obj6(6,1,........);
obj3(3,3,........);
obj5(5,3,........);
obj7(7,3,........);
obj8(8,4,........);
Suggect Some Logic...............
Thanks in advance.............

sAsho wrote:
That's the question how to do that?????????????????????????One question mark is sufficient. If you're going to go out of your way to write like an idiot, people won't take you seriously.
"How do I do that?" is way to broad a question. You need to do some research, take your best shot, and post a specific question about the specific parts that are giving you trouble.
Suggest something. I did suggest something.
I suggested what you should google for to get you started. Just like writing clearly and intelligently, if you can't be bothered to read what people suggest and put in the effort to follow that suggestion and do your own research, you'll find people will quickly lose interest in trying to help you.
Now I am additionally suggesting that you 1) pay closer attention and 2) do your own research.
Recurcive sort kind of a think.................No idea what you're saying here. See my first point in this reply.

Similar Messages

Sorting a list with parent/child object relations

Hi,
I have an ArrayList of Genre objects that I want to sort:
class Genre{
int CategoryID;
int ParentCategoryID;
String name;
String level;
Example objects:
Pop (CategoryID=10, ParentCategoryID=root, "popular music", 1);
Jazz (CategoryID=11, ParentCategoryID=root, "jazz music", 1);
Indie pop (CategoryID=12, ParentCategoryID=10, "indie pop", 2);
American Indie pop (CategoryID=13, ParentCategoryID=12, "american indie pop", 3);
Soul (CategoryID=15, ParentCategoryID=root, "soul music", 1);
Commercial pop (CategoryID=14, ParentCategoryID=10, "commercial pop", 2);
I hope that you see the point:
I want that the order will be like this in my arraylist:
jazz music
popular music
commercial pop
indie pop music
american indie pop
soul music
I'll implement the comparator-class in Genre and then add the compareTo-method in my genre-class.
But my brain is too tired to figure out what to write in the compareTo-method?
Have somebody done a similar method??
Best regards,
Thomas

Unfortunately is this solution not plausible since I
don't can have the parent genre in the genre class.
... Hashmap?Hashmap works. Here you go, using your structure, minus the level, I'm sure you can work around that though. Don't use -1 as a category id, it's reserved for your root. This code is not thread safe, I leave that to you. Don't forget that as implemented, parent Genres must be constructed prior to any of their children. You could get around this with a two pass initialization process.
// Not thread safe.
import java.util.*;
public class Genre implements Comparable {
 private static Map<Integer, Genre> genreForId = new HashMap<Integer, Genre>();
 private int id;
 private int level;
 private int parentId;
 private String name;
 public Genre(int id, int parentId, String name) {
 this.id = id;
 this.parentId = parentId;
 this.name = name;
 this.level = level(this);
 Genre.genreForId.put(id, this);
 private static int level(Genre genre) {
 int i = 0;
 while (genre != null) {
 genre = genre.getParent();
 i++;
 return i;
 public static void main(String[] args) {
 Genre pop = new Genre(10, -1, "popular music");
 Genre jazz = new Genre(11, -1, "jazz music");
 Genre indiePop = new Genre(12, 10, "indie pop");
 Genre americanIndiePop = new Genre(13, 12, "american indie pop");
 Genre soul = new Genre(15, -1, "soul music");
 Genre commercialPop = new Genre(14, 10, "commercial pop");
 Genre[] genres = { pop, jazz, indiePop, americanIndiePop, soul,
 commercialPop };
 Arrays.sort(genres);
 System.out.println(Arrays.toString(genres));
 public int compareTo(Object o) {
 Genre lhs = this;
 Genre rhs = (Genre) o;
 switch (Integer.signum(lhs.getLevel() - rhs.getLevel())) {
 case -1:
 rhs = rhs.getParent();
 if (lhs == rhs)
 return -1;
 break;
 case 0:
 if (lhs == rhs)
 return 0;
 else {
 if (lhs.getParent() == rhs.getParent())
 return lhs.getName().compareTo(rhs.getName());
 else {
 lhs = lhs.getParent();
 rhs = rhs.getParent();
 break;
 case 1:
 lhs = lhs.getParent();
 if (lhs == rhs)
 return 1;
 return lhs.compareTo(rhs);
 public int getLevel() {
 return level;
 public String getName() {
 return name;
 public Genre getParent() {
 return Genre.genreForId.get(getParentId());
 public int getParentId() {
 return parentId;
 public String toString() {
 return name;
}-S

Does table STPOX contain parent-child relationship between components

Hello
I need to get a list of components of SO BOM.
FM CS_BOM_EXPL_KND_V1 exports an output table STPOX.
Does this table contain parent-child relationship between components? If yes , can somebody tell me which fields contain parent child id.
thanks

Hi,
STPOX is not a table, it is a structure & hence there is no storing of data in a structure. The table which stores this info is STPO.
To get the link you can refer to STPO-STLNR & pass this value to MAST-STLNR, this way you can link the child with its parent.
Regards,
Vivek

Parent Child Relationships between Drop Down Menus

I have a request for additional functionality. Parent child relationships between drop down lists.
for example,
the first dropdown, could contain North, South, East, West & assign values of 1, 2, 3, 4.
the second dropdown, could contain a filtered set of data depending on the option from the first dropdown,
so the data could look like this in the second drop down:
Manchester 1
Leeds 1
London 2
Southampton 2
Norfolk 3
Newquay 4
so if I select North in the first dropdown, the second drop down would contain all the items with a value of 1, so Manchester & Leeds.
I have managed to get round this using conditional show & hide, but it is much messier on the design screen & also the way in which the data
will be returned is very very messy - seems like a simple addition which would improve the functionality no end.

Hi,
We have an "ideas" page where you can see if others have added this already, I believe there are some similar, and you can add your vote. If you don't find something that fits you can add your idea here:
http://forums.adobe.com/community/formscentral?view=idea
Thanks,
Josh

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

Question about File Content Conversion and parent-child relationships...

Hello!
 I have read probably every blog, article and SAP Help document on the topic, but I am stuck on this one. I am trying to convert a General Ledger flat file to an IDoc using the classic file --> IDoc scenario. The setup is done and working, but the IDocs are formatted incorrectly and I believe at least part of the reason is how I am converting the file content.
The root of my problem is that the flat file has a parent-child relationship between the document header and the document item and I want to maintain that since the IDoc type (FIDCCP01) has the same structure in the BKPF and BSEG segments.
Here is the flat (non-XML) file layout that is coming into the file adapter:
FileHeader
DocumentHeader
DocumentItem
DocumentHeader
DocumentItem
and so on (until the number of documents is complete
I would really like the content to be converted so that the line items stay under their parent document headers like this:
<FileHeader></FileHeader>
<DocumentHeader>
 <ItemHeader>
 </ItemHeader>
</DocumentHeader>
<DocumentHeader>
 <ItemHeader>
</ItemHeader>
</DocumentHeader>
But I keep getting this, where it lists the document headers first (one after another), and then all of the line items after the document headers like this:
<FileHeader></FileHeader>
<DocumentHeader></DocumentHeader>
<DocumentHeader></DocumentHeader>
<DocumentHeader></DocumentHeader>
<ItemHeader></ItemHeader>
Is is possible to maintain that parent-child relationship from the flat file and pass it over to the XML?
Thanks,
John

Hi,
Check some links on FCC.
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani
Reward points if Helpful

EJB 3, OneToMany that Acts As Tree, or Parent Child relationship support?

(Sorry for the RoR reference)
I first searched the forum and found this post that came close, but not exactly what I'm needing since my table doesn't reference the PK:
http://forum.java.sun.com/thread.jspa?forumID=13&threadID=767913
I have a table called Folder that represents a folder hierarchy. It has a 'Path' field and a 'Parent' field, and of course 'ID'. Each Folder knows its parent by the 'Parent' field, which references 'Path', not* 'ID'. Both are Strings.
To find all the children of a Folder, the sql for a PreparedStatment might look something like this (shared for clarity of the situation):
SELECT * FROM Folder
WHERE Parent = ?Question:
What are the proper annotations in EJB 3 / JPA to allow this kind non-primary key parent/child relationship mapping?
Can I specify a named query that handles the logic and then reference it in the OneToMany annotation? Other cool tricks?
Here is what I am trying (no runtime errors, but no results either). (Example simplified)
@Entity
@Table(name = "Folder")
@NamedQueries(value = {@NamedQuery(.......)})
public class Folder implements Serializable {
 @Id
 @Column(name = "ID", nullable = false, updatable = false)
 private Integer folderID;
 @Column(name = "Path", nullable = false)
 private String path;
 @Column(name = "Parent")
 private String parent;
 // v Here's the kicker v
 @OneToMany(cascade={CascadeType.ALL}, fetch=FetchType.EAGER)
 @JoinTable(name="Folder",
 joinColumns={@JoinColumn(name="Parent")},
 inverseJoinColumns={@JoinColumn(name="Path")})
 private List<Folder> children;
 // getters and setters ....
}Thanks!

It looks like the relationship is bi-directional.
Will this work...
// Parent.java
@Entity
public class Parent implements java.io.Serializable {
@Id
public Long parentId;
@OneToMany(cascade=CascadeType.PERSIST,mappedBy="parent")
public Collection<Child> children;
// Child.java
@Entity
public class Child implements java.io.Serializable {
@Id
public Long childId;
@ManyToOne
public Parent parent; // target of mappedBy
}Then, in your code (a session facade?), you'll create the parent first, create the children, then add the children to the parent. Your code is also responsible for maintaining the reference back to the parent.
Parent p = new Parent();
for(int i=0; i<10; i++) {
Child c = new Child();
p.children.add(c);
c.parent = p;
em.persist(p);

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

Recursive Parent Child relationship in JPA

@Entity
@Table(name = "OBJECTCATEGORY")
public class ObjectCategory implements Serializable {
 @Id
 private String categoryId;
 private String categoryName;
 private String description;
 private static final long serialVersionUID = 1L;
 @ManyToMany(fetch = FetchType.EAGER)
 @JoinTable(name = "MAP_CATEGORY", joinColumns = @JoinColumn(name = "CATEGORYID"), inverseJoinColumns = @JoinColumn(name = "OBJECTID"))
 private List<MapC> mapList = new ArrayList<MapC>();
// Recursion
 @OneToMany(fetch = FetchType.LAZY, mappedBy = "fqQuesCatagory")
 List<ObjectCategory > categoryList = new ArrayList<ObjectCategory>();
 @ManyToOne
 @JoinColumn(name = "PARENTCATEGORY")
 private ObjectCategory fqQuesCatagory
// Recursion
 public FqQuesCatagory() {
 super();
 public String getCategoryname() {
 return this.categoryname;
 public void setCategoryname(String categoryname) {
 this.categoryname = categoryname;
 public String getDescription() {
 return this.description;
 public void setDescription(String description) {
 this.description = description;
 public List<MapC> getMapList() {
 return faqList;
 public void setFaqList(List<MapC> faqList) {
 this.mapList = mapList ;
 public String getCategoryid() {
 return categoryId;
 public void setCategoryid(String categoryid) {
 this.categoryid = categoryId;
 public List<ObjectCategory> getFqCategoryList() {
 return categoryList;
 public void setFqCategoryList(List<ObjectCategory> categoryList) {
 this.categoryList = categoryList;
 public ObjectCategory getFqQuesCatagory() {
 return fqQuesCatagory;
 public void setFqQuesCatagory(ObjectCategory fqQuesCatagory) {
 this.fqQuesCatagory = fqQuesCatagory;
Doesn't SAP JPA support recursive parent-child relationship (highlighted by "// Recursion"). The same model works in TopLink perfectly.

Sorry for the delayed update..
I see an issue in the WSNavigator. I have a method in my EJB exposed as a web service. This method has a single argument, which is a serializable class containing a few string variables and the above-mentioned Entity with suitable getters and setters for all the class variables.
When I try to select this operation under the WSDL in the Webservice Navigator, I get a stack overflow error. I think it is because WD4J run-time is not able to build the nested tree. Not sure though...I've attached the stack trace below:
Cannot send an HTTP error response [500 "Application error occurred during the request procession." (details: java.lang.StackOverflowError
at java.lang.String.lastIndexOf(String.java:1496)
at java.lang.String.lastIndexOf(String.java:1458)
at com.sap.dictionary.runtime.StringUtil.getPackageName(StringUtil.java:143)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:179)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler._getScalarType(DictionaryHandler.java:447)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:159)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:447)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:746)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:759)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder.createParameterNodeInfo(DWSContextBuilder.java:984)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder.access$400(DWSContextBuilder.java:88)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1591)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
Any thoughts on this will be highly appreciated.
BR.

Work Order and parent/child relationship

I have been looking into the vision instance. There is an Asset-Rebuildable relationship, that is Forklif and it's battery. If there is a work order on the forklik "replace battery" can this be done automatically, or is this all manual.
1. When I pick the new battery from stores the S/N of the battery is associated with the forklif (automatic I tested this)
2. When I say "remove the old battery" should't the old battery parent/child relationship between the parent be broken and a child work order "charge" for the battery be logged. I could not reproduce that, but queried that this is what happens in vision. Are all these supposed to be manual?
Regards

From this plan, we can't easily get the parent child relationship like autotrace. Is there a way to get like autotrace?
SELECT * FROM table(DBMS_XPLAN.DISPLAY);
Plan hash value: 3693697345
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | TQ |INOUT |PQ Distrib |
| 0 | SELECT STATEMENT | | 1 | 117 | 6 (50) | 00:00:01 | | | |
| 1 | PX COORDINATOR | | | | | | | | |
| 2 | PX SEND QC (ORDER) |:TQ10003 | 1 | 117 | 6 (50) | 00:00:01 | Q1,03 | P->S | QC (ORDER) |
| 3 | SORT ORDER BY | | 1 | 117 | 6 (50) | 00:00:01 | Q1,03 | PCWP | |
| 4 | PX RECEIVE | | 1 | 117 | 5 (40) | 00:00:01 | Q1,03 | PCWP | |
| 5 | PX SEND RANGE |:TQ10002 | 1 | 117 | 5 (40) | 00:00:01 | Q1,02 | P->P | RANGE |
|* 6 | HASH JOIN | | 1 | 117 | 5 (40) | 00:00:01 | Q1,02 | PCWP | |
| 7 | PX RECEIVE | | 1 | 87 | 2 (50) | 00:00:01 | Q1,02 | PCWP | |
| 8 | PX SEND HASH |:TQ10001 | 1 | 87 | 2 (50) | 00:00:01 | Q1,01 | P->P | HASH |
| 9 | PX BLOCK ITERATOR | | 1 | 87 | 2 (50) | 00:00:01 | Q1,01 | PCWC | |
|* 10| TABLE ACCESS FULL | EMP | 1 | 87 | 2 (50) | 00:00:01 | Q1,01 | PCWP | |
| 11 | BUFFER SORT | | | | | | Q1,02 | PCWC | |
| 12 | PX RECEIVE | | 4 | 120 | 3 (34) | 00:00:01 | Q1,02 | PCWP | |
| 13 | PX SEND HASH |:TQ10000 | 4 | 120 | 3 (34) | 00:00:01 | | S->P | HASH |
| 14 | TABLE ACCESS FULL | DEPT | 4 | 120 | 3 (34) | 00:00:01 | | | |
Predicate Information (identified by operation id):
6 - access("E"."DEPTNO"="D"."DEPTNO")
10 - filter("E"."ENAME"='hermann')
---------------------------------------------------

Help needed in retrieving parent child relationship values

Hi,
I have a requirement to get parent child relationship values as below.
Ex: Address table
cont cont_code state state_code
C1 10 S1 1
C1 10 S2 2
C1 10 S3 3
C2 20 S4 4
C2 20 S5 5
C3 30 S6 6
C3 30 S7 7
C3 30 S8 8
I want a result of country/state and corresponding code like below.
corresponding states should be displayed under each country with some space appended to it.
Geography code
C1 10
S1 1
S2 2
S3 3
C2 20
S4 4
S5 5
C3 30
S6 6
S7 7
S8 8
I am using oracle 10g version.
Thanks in advance.

Hi,
When you post formatted text (like your output) on this site, type these 6 characters:
\(small letters only, inside curly brackets) before and after each section of formatted text, to preserve spacing.
I think you're saying that you want this output:GEOGRAPHY CODE
C1 10
S1 1
S2 2
S3 3
C2 20
S4 4
S5 5
C3 30
S6 6
S7 7
S8 8
If so, UNION, as Hoek suggested, is a good way.
GROUP BY ROLLUP is more efficient, but harder to understand:SELECT     CASE
          WHEN GROUPING (state) = 1
          THEN cont
          ELSE ' ' || state
     END          AS geography
,      CASE
          WHEN GROUPING (state) = 1
          THEN MAX (cont_code)
          ELSE MAX (state_code)
     END          AS code
FROM     t
GROUP BY cont
,      ROLLUP (state)
ORDER BY cont
,      state          NULLS FIRST
By the way, this looks like a bad table design.
In a relational database, the fact that the name 'C1' belongs to cont_code 10 should only be stored in one place. You have the same information on 3 separate rows.
Also, if 'C1' and 'S1' are both names, they should probably be in the same column, so that (to give just one example) you can find the information about 'x1' without knowing if it is a cont or a state.
A better design would be.NAME     CODE     PARENT     DSCR
====     ====     ======     ====
C1     10          CONT
S1     1     10     STATE
S2     2     10     STATE
S3     3     10     STATE
C2     20          CONT
S4     4     20     STATE
S5     5     20     STATE
C3     30          CONT
S6     6     30     STATE
S7     7     30     STATE
S8     8     30     STATE
If the data is this simple, then the dscr column isn't needed. Whether parent is NULL or not tells whether the rows represents a cont or a state.
To get the results you want from a table like this, you could use CONNECT BY. Using either UNION or ROLLUP, you have to know, at the time you write the query, how many levels there will be in the parent-child tree, and the length of the code is proportional to that depth, and the table has to be changed if you ever need to add another level. CONNECT BY can handle any number of levels, and the length and complexity of the code is the same whether you have just 2 levels (countries and strates), or 7 levels (continents, regions, countiries, states, districts, cities and neighborhoods) or 72 levels. The table doesn't need any more columns, no matter how deep the tree gets.
Edited by: Frank Kulash on Sep 16, 2010 11:54 AM

Parent child relationship is not displaying for IDOC_OUTPUT_ORDERS (PO)

Hi,
Can somebody help me the reason why parent child relationship not displaying properly for ORDER05 basic type?
If we go in details about the problem, a purchase order is creating in R/3 through EBP. To modify my requirement I am using userexit EXIT_SAPLEINM_002. Here I am appending the records in the segment for E1EDKT1 and E1EDKT2. IDOC is creating with an error of status record 26.
When I check in the transaction WE19 for the respective IDOC the data is showing correctly for all the segments including e1edkt1 and e1edkt2 segments and also I check in the table EDID4 segment number is showing correctly and the for the segment E1EDKT2 PGNUM also showing correctly, but when I see the IDOC in the transactions WE02 unable to see parent child relationship between E1EDKT1 and E1EDKT2 segment. Simply the data is displaying one below other like other segment.
I don't know the reason why it is displaying like that?
If anybody is having the solution is highly appreciable.
Regards,
Noorul

hi hassan,
When you are appendng the REcods which belong to the purticular segment..
all the segment needs to be appended in in the proper order as in the WE30..
I think you are appending the segment E1EDKT2 at the end of the EDIDD.. or IDOC_DATA in the user exit.. .. eventho no eerror will be displayed but idoc will generted with sataus 26 .. if check the STATUIs Recored u ewill find the SYNTaX ERROR.
Sollution for ur probelm is... don append the E1EDKT2 at the lastr instead you ahve to insert the segment E1EDKT2. only afer E1EDKT1....
Tehn you r problem will be solved.. I had faced the Same proble when i worked on material maser idoc..
Close this thread if when u r problem ise solved
Reward if helpful
Regards
Naresh Reddy K

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

Sorting a List on Parent Child Relationship

Similar Messages

Maybe you are looking for