Parent-child repeating frame display parent-attributes

I have the following object-structure
M-D-DD-DDD
so, the tree would look something like
M1
--D1
----DD1
------DDD1
------DDD2
----DD2
------DDD3
----DD3
------DDD4
--D2
----DD4
------DDD4
I need to display parent's attribute on each page ie
M1-D1-DD1-DDD1
M1-D1-DD1-DDD2
(there would be total five combinations)
Now, I changed the settings of DD, 'Print Object On'->All pages and 'Base Printing on'->enclosing object,
but this caused only two records to be displayed in the entire report
M1-D1-DD1-DDD1 and M1-D2-DD4-DDD4
so, i changed the settings of all the parent frames and ended up with only one record
M1-D1-DD1-DDD1
I cant figure out whats happening.
Response appreciated.

Hi Chirag,
I would say that you try to build a test report with 2 or 3 levels of grouping. For example, an employee report with first level group on Department, and second level group on Manager. Use the Report Wizard to create this report, and choose "Group Above" style.
Now take a look at the resulting paper layout. The top level group (department) as well as second level group (manager) will appear at the top of every page. Try to use the same settings for "Print object on" and "Base Printing on" as used in this test report.
Navneet.

Similar Messages

Parent Child Dimension Not displaying Name value.

I have a parent Child attribute in my dimension. It show the correct ID value in the reports but when I change the value from the NameColumn to be something else it still only shows the ID value.
I have an identical case in another dimension and it is working correctly. However this dimension for some reason does not seem to work and I believe they are built the same way I must be missing something. I have tried to show the OrgNodeID
and tried to display the OrgNodename but neither displays all it displays is the intdimParentOrgNodeID.
My dimension table looks something like this
intdimOrgNodeID int Key (surreget key)
intOrgNodeID int (Actual ID)
intDimParentOrgNodeID
intOrgNodeName
In the Propertys I have set
KeyColumns = tbldimOrgNode.intDimParentOrgNodeID
NameColumn = tbldimOrgNode.intOrgNodeID
Parent-child values
=NonLeafDataVisible
=*(Direct)
=
=ParentIsBlankSelfOrMissing
=(none)
Ken Craig

I have been pulling my hair out for days to find this and what I finally found that resolved this shocked me and I am still not sure why it would matter. You can see below my table and then dimension info. Although I agree my OrgNode ID attribute
is really not needed in AS and could be removed.   In places where that is used we could instead rename the key column Dim OrgNode ID to OrgNode ID.    However why the key attribute must have the name column set to intOrgNodeID
instead of just using the Key value of intdimOrgNodeID is what I am lost at.
Outside of this parent dimension I have never seen issues with this. I want to say sometimes in the past I have seen duplicates if I use the surreget key to display the actual ID so I have normally left that as a key and just added another attribute
to house the actual ID, like I did below.
Can someone explain to me this and what is the best suggested practice here.
My table is like this
intdimOrgNodeID int Key (surreget key)
intOrgNodeID int (Actual ID from source and used by customers)
intDimParentOrgNodeID (ID used for parent child (it is the Parent intOrgNodeID surreget
key intdimOrgNodeID))
intOrgNodeName (Source Name)
My AS dimension is like below
Dim OrgNode ID
AttributeHierarchyVisible=False
KeyColumns = tbldimOrgNode.intDimOrgNodeID (Integer)
NameColumns= tbldimOrgNode.intDimOrgNodeID (Integer)
OrgNode ID
AttributeHierarchyVisible=True
KeyColumns = tbldimOrgNode.intOrgNodeID (Integer)
NameColumns= tbldimOrgNode.intOrgNodeID (Integer)
OrgNode Hierarchy ID
Usage=Parent
AttributeHierarchyVisible=True
KeyColumns = tbldimOrgNode.intDimParentOrgNodeID
NameColumns= tbldimOrgNode.intOrgNodeID (WChar)
Change I had to make was this
Dim OrgNode ID
From     NameColumns= tbldimOrgNode.intDimOrgNodeID (Integer)
to
NameColumns= tbldimOrgNode.intOrgNodeID (Integer)
Ken Craig

Empty parent-child hierarchy if a date attribute is "1800-01-01 00:00:00.000"!

I have an Employees dimension that contains a parent-child hierarchy as the supervisor->employees (Org. chart. starts from the CEO to the lowest level of employees). The hierarchy is built on a relation between the employee_id (as the primary and
surrogate key) and supervisor_id (as a foreign key). There are many other attributes in this dimension one of them is the Termination_Date. The value for Termination_Date for the current employees in the source
system is "1800-01-01 00:00:00.000" (which is also the default value). The weird thing is that keeping this value in the employee dimension will cause the previously mentioned parent-child hierarchy to show nothing! if I change it to any other
value or NULL, the hierarchy works fine and shows the expected tree of employees!
I can change "1800-01-01 00:00:00.000" to Null in the ETL stage and solve the problem, but I want really to know what causes this ? why ?!

I have an Employees dimension that contains a parent-child hierarchy as the supervisor->employees (Org. chart. starts from the CEO to the lowest level of employees). The hierarchy is built on a relation between the employee_id (as the primary and
surrogate key) and supervisor_id (as a foreign key). There are many other attributes in this dimension one of them is the Termination_Date. The value for Termination_Date for the current employees in the source
system is "1800-01-01 00:00:00.000" (which is also the default value). The weird thing is that keeping this value in the employee dimension will cause the previously mentioned parent-child hierarchy to show nothing! if I change it to any other
value or NULL, the hierarchy works fine and shows the expected tree of employees!
I can change "1800-01-01 00:00:00.000" to Null in the ETL stage and solve the problem, but I want really to know what causes this ? why ?!

Repeating frame does not shift upwards !

Hi , i have a simple report which is built in a parent-childern pattern .
the layout consists of parent repeating frame and inside it a child repeating frame.
the parent and the child frames has a print on the first of the enclosing object property set.
in the first page the parent and the child frame are printed together well.
the outcome in the second page should be 2 child frame printed one after the other since
the parent frame is not printed and therfore should shift the first child frame upwards taking it's place
and by that leaving space to print the one after it .
instead only one child frame is printed in the same location as the previous one.
i have tried every possible combination of values in all of the properties of each repeating frame ,
including adding and removing regular frame that encloses the repeating frames .
nothing help.
it is a very important report and need help urgently.
Please help.
Thanks you.

probably a bug in repors .
i just resized the whole report and it worked .
thank you for your replay.

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

OBIEE Parent-Child Dimension with multiple hierarchies

Is it possible to have in a parent-child dimension multiple hierarchies? I want to have the same botom childs to aggregate to different parrents. example.
Account Dimension
HR1-total
HR1-parrent1
CHILD1
HR1-parrent2
CHILD2
HR2-total
HR2-parrent1
CHILD1
CHILD2
Thanks in advance.

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

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')
---------------------------------------------------

How to delete parent child relation in Toplink

Hi All,
I have 3 tables A,B,C.
In Table A ,I am saving record.
Table B & C has parent child relation.
B-->Parent
C-->Child
So I want to save records in Table A.
And delete from child(C) 1st then from parent(B).
I m writing my code as,
em.getTransaction().begin();
em.persist(Table A);//save in Table A
em.remove(em.merge(Table B));//Remove from Parent
But how to delete records from child table then from parent table.
Thanks
Sandip

If you have a @OneToOne relationship between two entities, the join column information is used to order the SQL when you remove two entities. For example, if I have:
@Entity
public class Employee implements Serializable {
     @OneToOne
     @JoinColumn(name="ADDR_ID")
     private Address address;
...Then the following code runs regardless of the order of the remove calls.
          em.getTransaction().begin();
          Employee parent = new Employee();
          Address child = new Address();
          parent.setAddress(child);
          em.persist(parent);
          em.persist(child);
          em.getTransaction().commit();
          em.getTransaction().begin();
          parent = em.merge(parent);
          child = em.merge(child);
          // order of next two statements unimportant
          em.remove(parent);
          em.remove(child);
          em.getTransaction().commit();If I don't remove the parent and just the child I get the same error you do because of the FK from Employee to Address.
--Shaun

Parent Child list form using infopath 2013

Hi All
I have two SharePoint list heaving parent child relation ship ( one parent have multiple child) now i want to create a single form in info path 2013 using code less solution . I am using SharePoint Online don't want to use c# code.
Journey Man

Hi,
Please check this
https://www.sharepointdrive.com/blog/how-to-establish-a-parent-child-relationship-in-sharepoint/
http://sharepoint.stackexchange.com/questions/6493/how-to-automatically-link-parent-in-child-list-new-form
Please remember to click 'Mark as Answer' on the answer if it helps you

Service Manager Incidents - Automatically Linked Parent Child

Hi Team
i'm looking for a solution using Orchestrator or using Powershell to be able to validate Incident Title, Search for any existing duplicates and then link them together in a Parent, Child relationship.
once it's Parent/Child engineers can solve parent issue which will auto-close all child incidents.

Hi WS12R2,
Are you looking for such workflow to detect the same incident Title?
Ex:
IR1: can't open Internet
IR2: can't open internet
Regards
Antoine AL Ibry

Restrict the data in main repeating frame

my report consists of 4 repeating frames.
main repeating frame consists of 3 child repeating frames
im not getting the data from 3&4 repeating frames. but the data is comming from 1&2. it contains two parameters in main group....
in such cases tht record should not been shown in the report...
so wat to do any alternative solution for this....
Please help me out with this.
Thanks.

Don't mind i am not yet clear.
My exact requirement is :
I have 3 measures and 2 dimensions.
A,B,C are measurures and D,E are dimensions
I want the report like this
D(Column1) E(Col2 ) A(April 2009 to Jan 2010)+B (Jan 2010) (Col3) C (Col4)
Please clarify me how to do this
Thanks in Advance
Edited by: user8949151 on Mar 10, 2010 4:06 AM

Best way to add additional parent child attribute values.

I have a parent Child attribute in my dimension. I am currently displaying the correct ID value as the business wants. So now they can see the rollup of the ID(intOrgNodeID
values.They would also like to see the same rollup of the Name (vcharOrgNodeName) for this ID.However they do
not want it concatenated. They want to be able to see them separate.
You cannot create two parent child attibutes in one dimension so not sure if there is some simple trick to make this work?
It seems like there should be some simple trick for this.
My dimension table looks something like this
intdimOrgNodeID int Key (surreget key)
intOrgNodeID int (Actual ID)
intDimParentOrgNodeID
vcharOrgNodeName
In the Propertys I have set this below.
KeyColumns = tbldimOrgNode.intDimParentOrgNodeID
NameColumn = tbldimOrgNode.intOrgNodeID
Ken Craig

Hi Ken,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Charlie Liao
TechNet Community Support

Parent - child - hierarchy - display in report output?

CHILD PARENT LEVEL HIERARCHY
140339991000 901589991000 1 /901589991000
140349990000 901589991000 1 /901589991000
140359999000 901589991000 1 /901589991000
991539998000 906349995000 3 /901589991000/140359999000/906349995000
991539998000 906339996000 3 /901589991000/140359999000/906339996000
991539998000 951309993000 2 /901589991000/140359999000/
In my report I need to display these as levels. Example level1 displays only those numbers with level1. Level 2 on following frame displays level 2 children with the parent numbers. Similarly, level 3 in next frame displays children and parent one below the other. How can I achieve this?
Something like this:
level 3
level2
level1

If you have a limited number of levels, then you may have a frme for each possible value for a level. And you would print frame_level1 only when :field_level=1 (you use the format trigger for frame_level1), print frame_level2 only when :field_level=2 and so on ...
In case you have a large number of levels, then I simply can't imagine how you wish to have the data printed.
HTH

Issue to check in parent-child closure table attributes to OBIEE repository

I use OBIEE 11.1.1.5 Administration Tool to open repository in online mode and set up parent-child hierarchy. There are no issues but after I check in changes to server, close repository and open it back from server, closure table attributes are missing.
On the other hand when I save repository file locally, close it and then open offline, all mentioned attributes are there. Also all other modifications (except hierarchy) are properly checked in to remote repository.
When I compare UDML from remote and local copy of repository here is part missing in remote:
CLOSURE TABLE ATTRIBUTES( "xxx".."yy"."ORG_STRUCTURE_CLOSURE"."MEMBER_KEY",
          "xxx".."yy"."ORG_STRUCTURE_CLOSURE"."ANCESTOR_KEY",
          "xxx".."yy"."ORG_STRUCTURE_CLOSURE"."DISTANCE",
          "xxx".."yy"."ORG_STRUCTURE_CLOSURE"."IS_LEAF")
When trying to build web report I get "[nQSError: 38107] Not all four columns are defined for closure table" (which is actually not surprising).
Unfortunately I need to do this change in online mode without restarting obiee services.
Any ideas how to force admin tool to check in all changes to remote repository?

Finally I applied workaround:
- modified hierarchy in offline mode
- deployed repository
Now when importing repo in online mode closure table parameters are in place.

Load Parent-Child dimension with attributes by rule file

Well, I've cracked my head open while banging against this wall.
Task is plain & simple:
How can I load build dimension from such table, using rule file?
Data
ProductParent ProductChild ProductAttribute
Balls Ball_8 Round
I want to load both product dimension and attribute by single rule file (neither of these dimensions exists in database before load), so I do the following:
1) Set dimension build settings, creating dimension Products (marking it P\C generated, sparse), having an attribute dimension AttributeDim
2) Mark the fields as Parent, Child and AttributeDim of dimension Products
After loading rule file a get three types of errors:
a) "Base member (Balls) association level does not match base dimension association level" -- does this mean that I cannot assign attributes in P\C way?
b) "Record #327 - Can not uniquely identify member by Balls (3335)
Balls Ball_8 Round" -- That's strange, I thought member should be identified by Ball_8 (and this column is unique)
c) "\\Record #418 - Error in association transaction [Ball_8] to [Round] (3362)"
I've read all I could find on topic from this forum, network45 board and going to start my way through metalink3, but maybe some kind soul will rescue me from drowning in information ocean?

Hi,
Outline is blank at the start of load and I expect dimensions Product and ProdAttribute to be added.
Generations are unapplicable, since I can't turn this parent-child dimension (it's ragged) into generation one.
And, by the way Integration Services manages to do this somehow, why rule files wouldn't?

Parent-child repeating frame display parent-attributes

Similar Messages

Maybe you are looking for