Parent Child Hierarchies

Hi All,
I am setting up Parent Child Hierarchies in EBS. Currently, we have all of our base-level child accounts under one parent 'ALL'. I am trying to expand this having a level of parents underneath 'ALL' such as 'Cash', 'AR', 'Inventory', etc. My thought was to have 'ALL' set up as the parent of these new parents with 'Parent Values Only' selected rather than 'Child Values Only'. Then I would make all my new parents have the base level child accounts underneath them by selecting 'Child Values Only'. Is this the correct way to set up ALL as the top level parent, Cash / AR / Inventory as the next parent down and then finally all of my base level child accounts?
Specifically, when you have multiple levels of parents, do you have to select 'Parent Values Only' to show the proper hierarchy structure?
Can someone please confirm.
Thx,
Mike

Hi Leo,
Did you configure closure table? http://www.rittmanmead.com/2010/11/oracle-bi-ee-11g-parent-child-hierarchies-multiple-modeling-methods/
Also make sure to perform the hierarchy changes in offline mode.
Regards,
Dpka

Similar Messages

Error with Parent-Child Hierarchies in BIEE11.1.1.5

Hi ,
I am using BIEE11.1.1.5, I have created a Logical Dimensions with Parent-Child Hierarchies,
In answer,I draged the Hierarchies named 'H5 Sales Rep', then view the results,
It has error,error message as follows:
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 22056] To use hierarchical functions, you need to associate a Closure Table with Logical Table Source 'LTS1 Sales Rep'. (HY000)
SQL Issued: SELECT 0 s_0, "Sample Sales"."Sales Rep"."Sales Rep Name" s_1, CASE WHEN ISLEAF("Sample Sales"."Sales Rep"."H5 Sales Rep") THEN 1 ELSE 0 END s_2, IDOF("Sample Sales"."Sales Rep"."H5 Sales Rep") s_3, PARENT("Sample Sales"."Sales Rep"."H5 Sales Rep") s_4 FROM "Sample Sales" WHERE ISROOT("Sample Sales"."Sales Rep"."H5 Sales Rep")
anyone know why???
Thank you!

Hi Leo,
Did you configure closure table? http://www.rittmanmead.com/2010/11/oracle-bi-ee-11g-parent-child-hierarchies-multiple-modeling-methods/
Also make sure to perform the hierarchy changes in offline mode.
Regards,
Dpka

OBIEE 11g - Navigation in Parent Child Hiearchy not working

Hi All,
I have a employee parent child hierarchy and I want to show revenue for each employee in the report. I have modeled my revenue as a measure like case 4 shown in the following link
http://www.rittmanmead.com/2010/11/oracle-bi-ee-11g-parent-child-hierarchies-multiple-modeling-methods/
So for example this is my report ,
--David (30)
---Sandra (15)
-----Joe (10)
Joe'e revenue is 10, Sandra's is 5 (showing her 5 Joe's revenue) and David's is 5 (showing his 5 Sandra's revenue)
Issue :
Now what I want is to provide action link on the revenue column so that when user would click on revenue for any employee it would direct them to a detail report showing the bifurcation.
For ex, I want that when user click on 15 which is Sandra's revenue, he would be redirected to a detailed report for Sandra and similary for Joe and David
MY ISSUE IS that the navigation is NOT working for sandra and Joe. It is only working for David (who is the ancestor of sandra and Joe). When I click on 15 to see sandra's detail report, it doesn't do anything and in the bottom left corner of the browser status bar below I see an ERROR saying
(same for Joe but David work's fine)
Message: 'getLevelInfo(...)' is null or not an object
Line: 1
Char: 11142
Code: 0
URI: http://localhost:7001/analytics/res/b_mozilla/answers/selectionsmodel.js
Why is that happening? Is that because I have modeled the revenue as an measure and not attribute. Is navigation not possible in this case?
Anybody has any solution or workaround for this, it will be highly appreciated.
Thanks,
Ronny

Ok, so let me explain this in detail and give the structure of my tables and the data,
There are three tables.
1.Parent Child relationship table - pctable
2.Closure table which OBIEE creates through a script - reltable
3.Fact table which contains the revenue - facttable
This is the data
pctable
personid | managerid
David | NULL
Sandra| David
Joe|Sandra
reltable
memberkey | ancestorkey |distance |is_leaf
David|NULL|NULL|0
David|David|0|0
Sandra|Sandra|0|0
Joe|Joe|0|0
Sandra|David|1|0
Joe|Sandra|1|1
Joe|David|2|1
facttable
personid|revenue
David|5
Sandra|5
Joe|10
and my joins conditions are, I join pctable to reltable and then reltable is joined to facttable like this.
pctable.personid = reltable.ancestorkey
reltable.memberkey = facttable.personid
and then in the report, when I pull up the pchierarchy build from pctable and revenue , I get as below and like I said, when I click on Sandra to see the revenue she contributes, I am not able to navigate. Can you let me know what modifications needs to be done?
---David(20)
----Sandra(15)
------Joe(10)

Parent Child Hierarchy

I am new learner for using OBIEE 11g, when I try to create the Parent_Child_Hierarchy in the repository, BI answer in the web shows the errors:
"State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 38107] *Not all four columns are defined for closure table 'Parent_Chile_Table_Closure'*. (HY000)".
According to the help web "http://www.adivaconsulting.com/adiva-blog/item/22-obiee-11g-hierarchical-table.html", I have created the relational Parent-Child-Hierarchy table in the database that is imported into the physical layer, and finish every steps, but when I drag the hierarchy in the presentation layer into display scope, which shows the errors mentioned above.
If you known the method for solving it,please help me and share your idea, thanks!

Hey,
I am also facing the same issue when i try to replicate this practice. (Create Logical Dimensions with Parent Child Hierarchies -- http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/biadmin11g_02/biadmin11g.htm#t9s3)
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 22056] To use hierarchical functions, you need to associate a Closure Table with Logical Table Source 'LTS1 Sales Rep'. (HY000)
SQL Issued: SET VARIABLE PREFERRED_CURRENCY='USD';SELECT 0 s_0, "Y - Sample Sales"."Sales Reps"."Sales Rep Name" s_1, CASE WHEN ISLEAF("Y - Sample Sales"."Sales Reps"."H5 Sales Rep DimHier") THEN 1 ELSE 0 END s_2, IDOF("Y - Sample Sales"."Sales Reps"."H5 Sales Rep DimHier") s_3, PARENT("Y - Sample Sales"."Sales Reps"."H5 Sales Rep DimHier") s_4 FROM "Y - Sample Sales" WHERE ISROOT("Y - Sample Sales"."Sales Reps"."H5 Sales Rep DimHier")

Parent Child hierarchy Scenario

Hi friends,
Im just working on the parent child hierarchy using the following link with the sample data.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/biadmin11g_02/biadmin11g.htm_
I tried to implement the same hierarchy using my local data instead of referring to the sample data.
I have a below query which returns the employee with manager along with the employee position
select distinct papf.person_id, papf.full_name "Employee Name", supf.person_id "Manager Id", supf.full_name "Manager Name", pj.name "Position Name"
from per_all_people_f papf, per_all_assignments_f paaf, per_all_people_f supf, per_jobs pj
where papf.person_id = paaf.person_id and supf.person_id = paaf.supervisor_id and paaf.job_id = pj.job_id
and trunc(sysdate) between paaf.effective_start_date and paaf.effective_end_date and
trunc(sysdate) between papf.effective_start_date and papf.effective_end_date
Im looking forward to implement the same result in my BI with a parent-child hierarchy.
Since i have imported three tables to my physical layer
per_all_people_f------------Dimension
per_all_assignments_f-----Fact
per_jobs---------------------DimensionFor creating parent-child in BI, we need to have a separate Parent child table which consist of four columns like ancestorkey, memberkey, distance, leaf.
From the above column i can understand the meaning like
For Ancestorkey-->Managerid
Memberkey------->Employeeid
But i couldnt get with the meaning for distance column as the meaning suggest like a distance b/w the two and leaf column as the meaning suggest like a leaf member. which leaf member does it refer.
I also referred the below link then too couldnt get the meaning for it
http://www.rittmanmead.com/2010/08/oracle-bi-ee-11g-parent-child-hierarchies-differing-aggregations/+
How i can form the parent child table for the BI from my above three tables of HRMS.
Thanks
Regards,
Saro

Hi friends,
I think i found a link of doing it
http://prasadmadhasi.com/2011/11/15/hierarchies-parent-child-hierarchy-in-obiee-11g/
Let me try this and will update accordingly.
Thanks for your views.
Regards,
Saro

HELP: how to build a parent-child hierarchy

Hy everyone,
my question is very basic: i need to know what is the structure of the relational tables that OBIEE accepts upon which i can build a parent-child hierarchy. I have data that OBIEE does not accept, do you know where i can find a clear description of the structure of the tables that has to be builded for creating correctly a parent-child hierarchy?
Thanks anyone a lot,
Regards

I've found what i needed, for everyone else:
http://docs.oracle.com/cd/E21043_01/bi.1111/e10540/dimensions.htm#BGBGACFJ
The parent-child relationship table must include four columns, as follows:
•A column that identifies the member
•A column that identifies an ancestor of the member. Note: The ancestor may be the parent of the member, or a higher-level ancestor.
•A "distance" column that specifies the number of parent-child hierarchical levels from the member to the ancestor
•A "leaf" column that indicates if the member is a leaf member (1=Yes, 0=No)
The column names can be user defined. The data types of the columns must satisfy the following conditions:
•The member and ancestor identifier columns have the same data type as the associated columns in the logical table that contains the hierarchy members. Note that the example shown in Table 9-1 uses text strings for readability, but you normally use integer surrogate keys for member_key and ancestor_key, if they exist in the source dimension table.
•The "distance" and "leaf" columns are INTEGER columns.
Note the following about the rows in a parent-child relationship table:
•Each member must have a row pointing at itself, with distance zero.
•Each member must have a row pointing at each of its ancestors. For a root member, this is a termination row with null for the parent and distance values.

Representating Hierarchical (Parent-Child) relation graphically using Swing

Hi,
I have to represent a hierarchical data which is having Parent-Child relation using Swing. I am not able to upload the image overhere, so I am represnting the data in such a way so that one can understand this problem. If anyone knows how to upload image on Sun forum, please let me know it will be great help for me.
Parent Root - A
Child of A - B, C, D
Child of C - E, F, G
Child of F - H
Child of D - J, K
The data needs to be represented in two formats-
1. Tabular Format
I am able to represent data in this format using combination of JTree and JTable. The data is getting represented in tabular format and I am able to expand and collapse the parent nodes to see the childs. The tabular data will look like below structure,
A
I_B
I
I_C
I I_E
I I
I I_F
| I |_H
| I
I I_G
I
I_D
I
I_J
I
I_K
2. Graphical Format
This is the other way in which I need to represent the data. The above shown tabular data needs to represented in graphical form. The end result should look like,
I A I
____________________I__________________________
___I___ __I__ __I__
I B I I C   I I D   I
____________________I____________ ______I________
___I___ __I__ __I__ __I__ ___I__
I E I I F   I I G   I I J   I I   K    I
__I___
I   H   I
Each box representing alphabates will be a component (like JPanel) which will have details about the item to be displayed. The parent and child should be connected with each other using line. This representation should be created at runtime using the hierarchical data. Also the parent and child relations should be expandable/collapsible as they are in JTree.
I am not able to find any component or any solution in Swing which can provide me this graphical representation. It will be great help if anyone can help me out in this.
Thanks in advance.

Sorry for inconvinience for the data representaion in graphical form. I don't know how this get jumblled. Please try to figure out the tabular/graphical representation using pen and paper as forum is not providing any help to upload an image.
Sorry again for inconvinience.
Thanks
Manoj Rai

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

Dimension tables - parent child or hierarchical

The data I m dealing with is structured as follow.
A customer has many stores and each store has a POSSystem.
Customer
Stores
POSSystem
So now when I create Dimensions, will I create as:
TableName Cols
DimCustomer                  CustKey
DimStores                      StoreKey, CustKey
DimPOS                         POSKey, StoreKey, CustKey
Are these Hierarchical or Parent Child?
Now when I will create Fact table, will I have:
TableName Cols
Sample1: DimFactPOS CustKey,POSKey,StoreKey, #trans
OR
Sample2: DimFactPOS POSKey, #trans
If I do sample1, then why do I keep "StoreKey, CustKey" in DimPOS?

From your question, I can assume that you have beginners knowledge in Data modeling and Data Warehousing.
Let me elaborate it and dilute your confusion.
You have designed
Star Schema; basic intention for having star schema is to have normalized fact tables and de-normalized dimension tables.
Reason you are creating three dimension (i.e. DimCustomer, DimStores and DimPOS) here because you must have many-to-one referential integrity between each level. You can google about Hierarchies,
Levels and Level relationships to get insight information about it.
Keeping normalize data in dimensions and keeping keys in fact table is a business decision. To which level you want to show the aggregated data? You
need to define granuality level based on business needs.
As in star schema, there is 1 fact table related to different dimensions. If I sub divide your assumption, Sample 1 represents
Data Mart and Sample 2 represents Data Warehouse.
I hope it will help you in understanding basic concepts.

Parent - child tables foreign key relation ship

Hi All,
we have 600 hundred tables ..i would like to print a hierarchial tree based on the foreigh key relathionship
i tried my best but i couldnt.
parent table
child table 1
childtable3
child table 2
and so
Can somebody help me out with a query?
Thanks,
kt

CREATE OR REPLACE FUNCTION get_child_tables (
ptable VARCHAR2,
powner VARCHAR2 DEFAULT 'SCOTT',
plevel NUMBER DEFAULT 10
RETURN stringarray
-- -- create this ON SQL*PLUS "CREATE OR REPLACE TYPE STRINGARRAY AS TABLE OF VARCHAR2(50);"
-- AUTHID CURRENT_USER
PIPELINED
AUTHOR DATE VERSION COMMENTS
======================================================================================
[email protected] 26-OCT-2009 1.0 Developed to ease developers effort to find Nth level of Referential integrity
======================================================================================
-- PURPOSE -> To find PARENT=> CHILD relational TABLE(S) in Oracle upto a depth max N Level.
--SYNTAX TO USE
SELECT * FROM TABLE( get_child_tables('DEPT','SCOTT',3)); Store this query in a file for your use
SELECT * FROM TABLE( get_child_tables('EMPLOYEE')); Store this query in a file for your use
-- RESULTS looks as below
--1 => DEPT
--2 => EMP
--2 => EMP2
--3 => EMP_CHILD
--3 => EMP2_CHILD
-- and so on
--This can be leveraged to use in any oracle database REGION 10g having and above.
--This FUNCTION gives formatted result of the Oracle 10g Hierarchical query result coded in the cursor
--to find MASTER => CHILD relational TABLE(S) upto a depth max 10 Level.
--The result of the PIPELINED function can be retrieved using Oracle new operator
--TABLE(array name) in SQL query.
--Due to the AUTHID CURRENT_USER compiler directive any user can use based on his/her access privileges on the database.
--GRANT EXECUTE ON SCOTT.get_child_tables TO PUBLIC;
--CREATE OR REPLACE PUBLIC SYNONYM get_child_tables FOR SCOTT.get_child_tables;
IS
atname stringarray := stringarray ();
-- create this ON SQL*PLUS CREATE OR REPLACE TYPE STRINGARRAY AS TABLE OF VARCHAR2(50);
vlevel NUMBER;
vtname VARCHAR2 (50);
nindex NUMBER := 0;
bprocessed BOOLEAN := FALSE;
CURSOR c1 (powner_in IN VARCHAR2, ptable_in VARCHAR2, plevel_in NUMBER)
IS
SELECT LEVEL, LPAD (' ', (LEVEL - 1) * 2, ' ') || pt AS "TNAME"
FROM (SELECT a.owner w1, a.table_name pt, a.constraint_name c1,
a.r_constraint_name r1, b.owner w2, b.table_name ct,
b.constraint_name c2, b.r_constraint_name r2
FROM all_constraints a, all_constraints b
WHERE a.constraint_name = b.r_constraint_name(+)
AND a.owner = b.owner(+)
AND a.owner =
UPPER (powner)
-- Change Owner here while testing
--AND A.r_constraint_name IS NULL
AND a.constraint_type IN ('P', 'R')) v1
START WITH pt =
UPPER
(ptable)
-- Change your master table here while testing the QUERY
CONNECT BY PRIOR ct = pt AND LEVEL <= plevel;
-- Change lavel here while testing
BEGIN
atname.EXTEND;
atname (1) := 'NOTHING';
OPEN c1 (powner, ptable, plevel);
LOOP
bprocessed := FALSE;
FETCH c1
INTO vlevel, vtname;
IF nindex > 1 AND atname (atname.LAST - 1) = vtname
THEN
--DBMS_OUTPUT.PUT_LINE('2 ==== vtname ' ||vtname || ' '|| atname.count|| ' '||atname.last || ' '||atname( atname.last-1));
bprocessed := TRUE;
END IF;
IF NOT bprocessed
THEN
nindex := nindex + 1;
atname.EXTEND;
atname (nindex) := vtname;
PIPE ROW (vlevel || ' => ' || vtname);
DBMS_OUTPUT.put_line ( ' **** nindex - atname( nindex) '
|| nindex
|| ' - '
|| atname (nindex)
DLOG('ADDING ',vTname); A LOGGING ATONOMUS PROCEDURE FOR DEBUG PURPOSE
END IF;
EXIT WHEN c1%NOTFOUND;
END LOOP;
CLOSE c1;
FOR i IN 1 .. atname.COUNT
LOOP
DBMS_OUTPUT.PUT_LINE('atname (i) ' ||atname (i));
END LOOP;
RETURN;
EXCEPTION
WHEN no_data_needed
THEN -- THIS EXCEPTION HAS TO BE THERE TO GET THE FUCTION WORKABLE
DBMS_OUTPUT.put_line (SQLERRM);
RETURN;
END get_child_tables;
/

OBIEE 11g Parent Child hierarchy

Hi,
I'm trying to setup a parent-child hierarchy dimension. I have setup a new hierarchy dimension using numeric keys but want to display another field in the hierarchical column on a report e.g. employee fullname & not the member_key based on a numeric value. Can this be done & how do you do it? All the examples I have seen use varchar2 type columns as the keys to do this.
Thanks in advance, Phil
My Setup
=============
Dimension - logical level
===============
member key = employee_id
parent-child table source
===============
member key = employee_id
parent key = supervisor_id
relationship distance = levels_removed
leaf node identifier = isleaf
Employee logical folder
==============
employee_id ( number)- primary key
full_name (varchar2) - unique key
supervisor_id ( number)
Closure table
=========
employee_id ( number)
supervisor_id ( number)
level ( number)
isleaf ( number)

Thanks for the link Suresh but the aggregations are working correctly.
My problem is only at the display level. I need to create a dashboard that displays the complete hierarchy.
So for example if I have this hierarchy:
- Steven King
- Adam Frip
Alexis Bull
Anthony Cabrio
Alberto Erraruriz
Den Raphaely
I want the dashboard to display immediately that complete hierarchy. If someone adds a member to the hierarchy in the database, the dashboard should display this new member without having to manually modify the dashboard.
- Steven King
- Adam Frip
Alexis Bull
Anthony Cabrio
- Alberto Erraruriz
Mozhe Atkinson
Den Raphaely
Also, if I just manually open the hierarchy and save the dashboard, if "Steven King" is replaced by "Shanta Vollman", the dashboard doesn't like it and returns a result looking like:
- Adam Frip
Alexis Bull
Anthony Cabrio
- Alberto Erraruriz
Mozhe Atkinson
Den Raphaely
+ Shanta Vollman
So I'm looking for some option that will tell OBIEE to open the hierarchy without having to specify "Drill down on member "Steven King"", "Drill down on member "Adam Frip"...
I hope I'm explaining correctly...

No Results after build a Parent-Child Hierarchy in OBIEE11G

Hi All:
Here's an problem. I followed the "http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/" this article step by step to create a parent-child hierarchy in admin tool in OBIEE11G.
But after check in and try to retrieve the hierarchy data in Answer. There's always displays "No Results."
Is there any suggestions for this ? Really urgent and thanks for your help.
Best regards
Sunny

@Aketi
It is One way that We derive
"sys_connect_by_path(RowIDToChar(RowID),'.') as
RowIDList"
Then
We use Left Join Using
"instr(RowIDList,RowIDToChar(RowID))".sorry, didn't catch what you mean.
my site :-)
http://oraclesqlpuzzle.hp.infoseek.co.jp/4-13.html
pity, I don't know Japanese :(
@Rob
your query is good and simple :) probably it's the best alternative for the OP.
But it won't work with not a plain hierarchy, e.g.:
      1
    2   3
      4
    5   6
SQL> create table hierarchy (child,parent)
2     as
3     select 1, null from dual union all
4     select 2, 1 from dual union all
5     select 3, 1 from dual union all
6     select 4, 3 from dual union all
7     select 4, 2 from dual union all
8     select 5, 4 from dual union all
9     select 6, 4 from dual
10 /
Table created
SQL>
SQL> create table data (hierarchyid,value)
2    as
3    select 5, 10 from dual union all
4    select 6, 25 from dual
5 /
Table created
SQL>
SQL> select h.child
2           , sum(connect_by_root d.value)
3        from hierarchy h
4           , data d
5       where h.child = d.hierarchyid (+)
6     connect by prior h.parent = h.child
7       group by h.child
8       order by h.child
9 /
     CHILD SUM(CONNECT_BY_ROOTD.VALUE)
         1                          70
         2                          35
         3                          35
         4                          70
         5                          10
         6                          25
6 rows selected
SQL>

Very urgent- find parent-child relationship for wbs element

Hi,
There is a certain parent child heirachy in WBS elements.My requiremnet is to delete WBS element depending on certain field , say depending on some ""status"".If the status is active in some or any of the child then I am not suppose to delete its respective parent too. This parent-child relation can have say 5 levels.
For this I require a logic /program which shall maintain the parent reference for that particular child whih I want/ dont want to delete.
I am maintaining bottom- to -top approach.
That is I shall be checking for the status of the lowest level of WBS and then going to the highest.
Please Help!
Kshitija

hi you can use following code....
REPORT zpmgmt_rpt_projinfo NO STANDARD PAGE HEADING LINE-SIZE 160.
*& Includes
INCLUDE <icon>.
INCLUDE zdata_declare_n. " include for data declaration
INCLUDE zsubr_n.          " include for both subroutines
DATA: gv_index LIKE sy-tabix,
      lv_index LIKE sy-tabix,
      date_index TYPE sy-tabix.
*& Start of Selection ( Get Data )
START-OF-SELECTION.
For initial display cnt is set to X
IF cnt EQ 'X'.
    PERFORM getdata.
    CLEAR it_final.
    PERFORM hierarchy.
    cnt = ''.
ENDIF.
*&      Form GETDATA
Fetches the data and logic for T1 and T2
--> p1        text
<-- p2        text
FORM getdata.
Getting project header data
SELECT * FROM proj
    INTO CORRESPONDING FIELDS OF TABLE it_proj
    WHERE pspid IN so_posid
    AND werks IN so_plant
    AND stort IN so_loc
    AND erdat IN so_date.
IF sy-subrc <> 0.
    MESSAGE 'Enter the valid entry' TYPE 'I'.
    STOP.
ENDIF.
LOOP AT it_proj.
    PROJECT = it_proj-pspid.
Get project & WBS element details
BAPI used gives the output in some specific format
which is used for roll-up logic.
    CALL FUNCTION 'BAPI_PROJECT_GETINFO'
     EXPORTING
        project_definition           = project
        with_activities              = 'X'
     IMPORTING
        e_project_definition         = e_project_definition
     TABLES
        e_wbs_hierarchie_table       = e_wbs_hierarchie_table.
Appending all the projects in the e_wbs.
        LOOP AT e_wbs_hierarchie_table.
          MOVE-CORRESPONDING e_wbs_hierarchie_table TO e_wbs.
          APPEND e_wbs.
          CLEAR e_wbs.
        ENDLOOP.
    CLEAR PROJECT.
ENDLOOP.
SET COUNTRY 'US'.
i_repid = sy-repid.
Getting data into internal tables
Getting project WBS element
SELECT * FROM prps
    INTO CORRESPONDING FIELDS OF TABLE it_prps
    FOR ALL ENTRIES IN it_proj
    WHERE psphi = it_proj-pspnr.
Getting project activities
SELECT * FROM afvc
    INTO CORRESPONDING FIELDS OF TABLE it_afvc
    FOR ALL ENTRIES IN it_prps
    WHERE projn = it_prps-pspnr.
SORT it_afvc BY vornr.
Getting activities start & end dates from AFVV
SELECT * FROM afvv
   INTO CORRESPONDING FIELDS OF TABLE it_afvv
   FOR ALL ENTRIES IN it_afvc
   WHERE aufpl = it_afvc-aufpl
   AND aplzl = it_afvc-aplzl.
Getting plant name
SELECT * FROM t001w
    INTO CORRESPONDING FIELDS OF TABLE it_t001w
    FOR ALL ENTRIES IN it_proj
    WHERE werks = it_proj-werks.
Logic for passing data to final internal table
Passing Project master data
READ TABLE it_proj INDEX 1.
IF sy-subrc EQ 0.
    CALL FUNCTION 'CONVERSION_EXIT_ABPSN_OUTPUT'
      EXPORTING
        input = it_proj-pspid
      IMPORTING
        output = it_proj-pspid.
    it_final-posid = it_proj-pspid.
    it_final-post1 = it_proj-post1.
    APPEND it_final.
    CLEAR it_final.
ENDIF.
Passing WBS element to the final internal table IT_FINAL
LOOP AT it_prps.
    CALL FUNCTION 'CONVERSION_EXIT_ABPSN_OUTPUT'
      EXPORTING
        input = it_prps-posid
      IMPORTING
        output = it_prps-posid.
     CLEAR color.
Get WBS element status ans color(T2)from OBJNR
    CALL FUNCTION 'ZGET_STATUS_N'
      EXPORTING
        objnr    = it_prps-objnr
      IMPORTING
        color    = color
      TABLES
        t_status = it_tj30t.
    IF     color = 'RED'.
      it_final-t2 = '@0A@'.
    ELSEIF color = 'YELLOW'.
      it_final-t2 = '@09@'.
    ELSEIF color = 'GREEN'.
      it_final-t2 = '@08@'.
    ENDIF.
    SORT it_tj30t DESCENDING.
Getting User statuses of WBS element at component level.
    READ TABLE it_tj30t INDEX 1.
    IF sy-subrc EQ 0.
      CONCATENATE it_tj30t-txt04 '' INTO it_final-txt04 SEPARATED BY space.
    ENDIF.
    READ TABLE it_tj30t INDEX 2.
    IF sy-subrc EQ 0.
      CONCATENATE it_tj30t-txt04 it_final-txt04 INTO it_final-txt04 SEPARATED BY space.
    ENDIF.
    MOVE-CORRESPONDING it_prps TO it_final.
    READ TABLE it_proj WITH KEY pspid = it_prps-posid.
    IF sy-subrc EQ 0.
      it_final-werks = it_proj-werks.
    ENDIF.
    APPEND it_final.
    CLEAR it_final-txt04.
Passing activity to the final internal table IT_FINAL
    LOOP AT it_afvc WHERE projn EQ it_prps-pspnr.
      CLEAR color.
Getting user status and color(T2) for Activity from OBJNR
      CALL FUNCTION 'ZGET_STATUS_N'
        EXPORTING
          objnr    = it_afvc-objnr
        IMPORTING
          color    = color
        TABLES
          t_status = it_tj30t.
      IF     color = 'RED'.
        it_final-t2 = '@0A@'.
      ELSEIF color = 'YELLOW'.
        it_final-t2 = '@09@'.
      ELSEIF color = 'GREEN'.
        it_final-t2 = '@08@'.
      ENDIF.
      CLEAR: it_final-fsavd,
             it_final-fssad.
      MOVE-CORRESPONDING it_afvc TO it_final.
Getting User statuses of WBS element at activity level.
      SORT it_tj30t DESCENDING.
      READ TABLE it_tj30t INDEX 1.
      IF sy-subrc EQ 0.
        CONCATENATE it_tj30t-txt04 '' INTO it_final-txt04 SEPARATED BY space.
      ENDIF.
      READ TABLE it_tj30t INDEX 2.
      IF sy-subrc EQ 0.
        CONCATENATE it_tj30t-txt04 it_final-txt04 INTO it_final-txt04 SEPARATED BY space.
      ENDIF.
      APPEND it_final.
      lv_index = sy-tabix.
      CLEAR it_final-txt04.
      CLEAR it_final-ltxa1.
      CLEAR it_tj30t.
      REFRESH it_tj30t.
Start Date and End Date fetched from AFVV.
      LOOP AT it_afvv WHERE   aufpl EQ it_afvc-aufpl
                          AND   aplzl EQ it_afvc-aplzl.
        MOVE-CORRESPONDING it_afvv TO it_final.
        MODIFY it_final INDEX lv_index TRANSPORTING fsavd fssad.
      ENDLOOP.
      CLEAR it_afvc.
      CLEAR lv_index.
    ENDLOOP.
ENDLOOP.
Logic for T1.
T1 is based on T2 and start date and end date of activities.
LOOP AT it_final WHERE stufe = 3
                   AND ltxa1 IS NOT INITIAL.
    gv_index = sy-tabix.
    PERFORM date_difference.
    CASE it_final-t2.
      WHEN '@0A@'.     " If Red
        IF sy-datum GT it_final-fssad.
          it_final-t1 = '@0A@'.
        ELSEIF sy-datum LE it_final-fssad AND
               sy-datum GE it_final-fsavd.
          IF gv_diff > 1.
            PERFORM date_monitor.
          ENDIF.
          it_final-t1 = '@09@'.
        ELSEIF
          sy-datum LT it_final-fsavd.
          it_final-t1 = '@08@'.
        ENDIF.
      WHEN '@09@'.     " If Yellow
        IF sy-datum GT it_final-fssad.
          it_final-t1 = '@0A@'.
        ELSEIF sy-datum LE it_final-fssad AND
               sy-datum GE it_final-fsavd.
          IF gv_diff > 1.
            PERFORM date_monitor.
          ENDIF.
          it_final-t1 = '@09@'.
        ELSEIF
          sy-datum LT it_final-fsavd.
          it_final-t1 = '@08@'.
        ENDIF.
      WHEN '@08@'.     " If Green
        it_final-t1 = '@08@'.
    ENDCASE.
    MODIFY it_final INDEX gv_index TRANSPORTING t1.
    CLEAR gv_index.
ENDLOOP.
ENDFORM.                    " GETDATA
*&      Form hierarchy
Displays the data in ALV hierarchical manner.
In coding 3 tables are used for roll-up functionality.
FORM hierarchy .
DATA: it_final1 LIKE it_final OCCURS 0 WITH HEADER LINE.
DATA: it_final2 LIKE it_final OCCURS 0 WITH HEADER LINE.
DATA: it_final3 LIKE it_final OCCURS 0 WITH HEADER LINE.
DATA: count TYPE i VALUE 1.
DATA: posid LIKE prps-posid.
DATA: change,
        date_mask TYPE c LENGTH 10,
        lv_index2 LIKE sy-tabix.
DATA: index TYPE sy-tabix.
DATA: up LIKE prps-posid.
Deleting duplicate entries from the it_final.*****************
DELETE ADJACENT DUPLICATES FROM it_final.
LOOP AT it_final WHERE stufe EQ 2.
    IF posid NE it_final-posid.
      posid = it_final-posid.
    ELSE.
      DELETE it_final INDEX sy-tabix.
    ENDIF.
ENDLOOP.
CLEAR posid.
LOOP AT it_final WHERE stufe EQ 3
                    AND ltxa1 EQ space.
    IF posid NE it_final-posid.
      posid = it_final-posid.
    ELSE.
      DELETE it_final INDEX sy-tabix.
    ENDIF.
ENDLOOP.
Updating a new intrnal table for roll up functionality. ********
it_final1[] = it_final[].
CLEAR: lv_index2.
LOOP AT it_final1 WHERE stufe = 3
                    AND ltxa1 IS NOT INITIAL.
    READ TABLE it_final WITH KEY stufe = 3
                                  posid = it_final1-posid
                                  post1 = it_final1-post1.
   clear change.
    IF sy-subrc = 0.
      lv_index = sy-tabix.
      IF lv_index2 <> lv_index.
        CLEAR: change.
        lv_index2 = lv_index.
      ENDIF.
      IF it_final1-t1 = '@0A@'.
        it_final-t1 = '@0A@' .
        MODIFY it_final INDEX lv_index TRANSPORTING t1.
        DELETE it_final1 WHERE posid = it_final-posid.
        CONTINUE.
      ENDIF.
      IF it_final1-t1 = '@09@'.
        it_final-t1 = '@09@'.
        change = 'Y'.
        MODIFY it_final INDEX lv_index TRANSPORTING t1.
        CONTINUE.
      ENDIF.
      IF it_final1-t1 = '@08@'.
        it_final-t1 = '@08@' .
        IF change IS INITIAL.
          MODIFY it_final INDEX lv_index TRANSPORTING t1.
        ENDIF.
        CONTINUE.
      ENDIF.
    ENDIF.
ENDLOOP.
it_final2[] = it_final[].
CLEAR: lv_index2.
LOOP AT it_final2 WHERE stufe = 3
                    AND ltxa1 IS INITIAL.
    READ TABLE e_wbs WITH KEY wbs_element = it_final2-posid.
    IF sy-subrc = 0.
      READ TABLE it_final WITH KEY stufe = 2
                                   posid = e_wbs-up.
      IF sy-subrc = 0.
        CHECK it_final-t1 <> '@0A@'.
        lv_index = sy-tabix.
        IF lv_index2 <> lv_index.
          CLEAR: change.
          lv_index2 = lv_index.
        ENDIF.
        IF   it_final2-t1 = '@0A@'.
          it_final-t1 = '@0A@' .
          MODIFY it_final INDEX lv_index TRANSPORTING t1.
          CONTINUE.
        ENDIF.
        IF it_final2-t1 = '@09@'.
          it_final-t1 = '@09@'.
          MODIFY it_final INDEX lv_index TRANSPORTING t1.
          change = 'Y'.
          CONTINUE.
        ENDIF.
        IF it_final2-t1 = '@08@'.
          it_final-t1 = '@08@' .
          IF change IS INITIAL.
            MODIFY it_final INDEX lv_index TRANSPORTING t1.
          ENDIF.
          CONTINUE.
        ENDIF.
      ENDIF.
    ENDIF.
ENDLOOP.
it_final3[] = it_final[].
CLEAR: lv_index2.
CLEAR change.
LOOP AT it_final3 WHERE stufe = 2.
    READ TABLE e_wbs WITH KEY wbs_element = it_final3-posid.
    CHECK sy-subrc = 0.
    READ TABLE it_final WITH KEY stufe = 1
                                 posid = e_wbs-up.
    IF sy-subrc = 0.
      CHECK it_final-t1 <> '@0A@'.
      lv_index = sy-tabix.
      IF lv_index2 <> lv_index.
        CLEAR: change.
        lv_index2 = lv_index.
      ENDIF.
      IF   it_final3-t1 = '@0A@'.
        it_final-t1 = '@0A@' .
        MODIFY it_final INDEX lv_index TRANSPORTING t1.
        DELETE it_final3.   " WHERE stufe = 2.
        CONTINUE.
      ENDIF.
      IF it_final3-t1 = '@09@'.
        it_final-t1 = '@09@'.
        MODIFY it_final INDEX lv_index TRANSPORTING t1.
        change = 'Y'.
        CONTINUE.
      ENDIF.
      IF it_final3-t1 = '@08@'.
        it_final-t1 = '@08@' .
        IF change IS INITIAL.
          MODIFY it_final INDEX lv_index TRANSPORTING t1.
        ENDIF.
        CONTINUE.
      ENDIF.
    ENDIF.
ENDLOOP.
Building hierarchy table ***************
LOOP AT it_final.
    IF it_final-stufe = '0'.
      node_tab-type = 'T'.
      node_tab-name = 'Project'.
      node_tab-tlevel = '01'.
      node_tab-nlength = '8'.
      node_tab-color = '4'.
      node_tab-text = it_final-post1.
      node_tab-tlength ='20'.
      node_tab-tcolor = 5.
      APPEND node_tab.
      it_final_hsk-node = node_tab.
      APPEND it_final_hsk. CLEAR it_final_hsk.
      CLEAR node_tab.
    ELSEIF it_final-stufe = '1'.
      node_tab-type = 'P'.
      node_tab-name = 'Project'.
      node_tab-tlevel = '02'.
      node_tab-nlength = '10'.
      node_tab-color = '1'.
      node_tab-kind2 = 'I'.
      node_tab-text3+0(4) = it_final-t1.
      node_tab-tlength3 = '5'.
      node_tab-tcolor3 = 1.
      node_tab-kind3 = ' '.
      node_tab-text4 = it_final-posid.
      node_tab-tlength4 ='20'.
      node_tab-tcolor4 = 3.
Code added for plant name
      CALL FUNCTION 'CONVERSION_EXIT_ABPSN_INPUT'
        EXPORTING
          input = it_final-posid
        IMPORTING
          output = it_final-posid.
      READ TABLE it_proj WITH KEY pspid = it_final-posid.
      CHECK sy-subrc = 0.
      READ TABLE it_t001w WITH KEY werks = it_proj-werks.
      CHECK sy-subrc = 0.
Code End.
      node_tab-kind4 = ' '.
      node_tab-text5 = it_t001w-name1.   " Plant Name
      node_tab-tlength5 ='25'.
      node_tab-tcolor5 = 4.
      node_tab-kind5 = ' '.
      node_tab-text6 = it_proj-stort.
      node_tab-tlength6 ='15'.
      node_tab-tcolor6 = 4.
      node_tab-kind6 = ' '.
      node_tab-text7 = it_final-post1.
      node_tab-tlength7 ='25'.
      node_tab-tcolor7 = 4.
      APPEND node_tab.
      it_final_hsk-node = node_tab.
      APPEND it_final_hsk. CLEAR it_final.
      CLEAR node_tab.
    ELSEIF it_final-stufe = '2'.
      node_tab-type = 'P'.
      node_tab-name = 'Gate Id'.
      node_tab-tlevel = '03'.
      node_tab-nlength = '10'.
      node_tab-color = '1'.
      node_tab-kind2 = 'I'.
      node_tab-text3+0(4) = it_final-t1.
      node_tab-tlength3 = '5'.
      node_tab-tcolor3 = 1.
      node_tab-kind3 = ' '.
      node_tab-text4 = it_final-posid.
      node_tab-tlength4 ='20'.
      node_tab-tcolor4 = 3.
      node_tab-kind4 = ' '.
      node_tab-text5 = it_final-post1.
      node_tab-tlength5 ='25'.
      node_tab-tcolor5 = 4.
      APPEND node_tab.
      it_final_hsk-node = node_tab.
      APPEND it_final_hsk.
      CLEAR it_final.
      CLEAR node_tab.
    ELSEIF it_final-stufe = '3' AND it_final-ltxa1 EQ space.
      node_tab-type = 'P'.
      node_tab-name = 'Component'.
      node_tab-tlevel = '04'.
      node_tab-nlength = '11'.
      node_tab-color = '1'.
      node_tab-kind2 = 'I'.
      node_tab-text3+0(4) = it_final-t1.
      node_tab-tlength3 = '5'.
      node_tab-tcolor3 = 1.
      node_tab-kind3 = ' '.
      node_tab-text4 = it_final-posid.
      node_tab-tlength4 ='25'.
      node_tab-tcolor4 = 3.
      node_tab-kind4 = ' '.
      node_tab-text5 = it_final-post1.
      node_tab-tlength5 ='25'.
      node_tab-tcolor5 = 4.
Code added for start date and end date for component level.
      SELECT SINGLE pstrm petrf INTO (v_pstrm, v_petrf)
           FROM prte WHERE posnr = it_final-pspnr.
      it_final-fsavd = v_pstrm.
      it_final-fssad = v_petrf.
      MODIFY it_final INDEX sy-tabix.
      WRITE it_final-fsavd TO date_mask MM/DD/YYYY.
      node_tab-tpos1 = '0'.
      node_tab-kind5 = ' '.
      node_tab-text6 = date_mask.
      node_tab-tlength6 ='10'.
      node_tab-tcolor6 = 3.
      CLEAR date_mask.
      WRITE it_final-fssad TO date_mask MM/DD/YYYY.
      node_tab-tpos1 = '0'.
      node_tab-kind6 = ' '.
      node_tab-text7 = date_mask.
      node_tab-tlength7 ='10'.
      node_tab-tcolor7 = 3.
      CLEAR date_mask.
      APPEND node_tab.
      it_final_hsk-node = node_tab.
      APPEND it_final_hsk.
      CLEAR it_final_hsk.
      CLEAR node_tab.
    ELSEIF it_final-ltxa1 IS NOT INITIAL.
      node_tab-type = 'P'.
      node_tab-name = 'Element'.
      node_tab-tlevel = '05'.
      node_tab-nlength = '11'.
      node_tab-color = '1'.
      node_tab-kind = 'I'.
      node_tab-text1+0(4) = it_final-t1.
      node_tab-tlength1 = '5'.
      node_tab-tcolor1 = 1.
      node_tab-kind2 = 'I'.
      node_tab-text3+0(4) = it_final-t2.
      node_tab-tlength3 = '5'.
      node_tab-tcolor3 = 1.
      node_tab-kind3 = ' '.
      node_tab-text4 = it_final-ltxa1.
      node_tab-tlength4 ='45'.
      node_tab-tcolor4 = 3.
      node_tab-kind4 = ' '.
      node_tab-text5 = it_final-txt04.
      node_tab-tlength5 ='10'.
      node_tab-tcolor5 = 3.
      WRITE it_final-fsavd TO date_mask .
      node_tab-kind5 = ' '.
      node_tab-text6 = date_mask.
      node_tab-tlength6 ='10'.
      node_tab-tcolor6 = 3.
      CLEAR date_mask.
      WRITE it_final-fssad TO date_mask.
      node_tab-tpos1 = '0'.
      node_tab-kind6 = ' '.
      node_tab-text7 = date_mask.
      node_tab-tlength7 ='10'.
      node_tab-tcolor7 = 3.
      CLEAR date_mask.
      APPEND node_tab.
      it_final_hsk-node = node_tab.
      APPEND it_final_hsk.
      CLEAR it_final_hsk.
      CLEAR node_tab.
    ENDIF.
ENDLOOP.
CALL FUNCTION 'RS_TREE_CONSTRUCT'
    TABLES
      nodetab = it_final_hsk.
CALL FUNCTION 'RS_TREE_LIST_DISPLAY'
    EXPORTING
      callback_program      = i_repid
      callback_user_command = 'USER_COMMAND'
      callback_gui_status   = 'ZLD_TREE_N'
      screen_start_column   = 0
      use_control           = 'L'.
ENDFORM.                    " hierarchy
*&      Form MYGUI
      text
     -->EX_TAB     text
FORM zld_tree_n.
SET PF-STATUS 'ZLD_TREE_N'.
ENDFORM.                    "zld_tree.
**&      Form user_command
    Code for REFRESH button
FORM user_command TABLES   node STRUCTURE seucomm
                           USING ucomm CHANGING exit
                                    list_refresh.
CASE ucomm.
    WHEN 'REFR' .
      CLEAR it_final.
      REFRESH it_final_hsk.
      REFRESH it_final.
      PERFORM getdata.
      CLEAR it_final.
      PERFORM hierarchy.
    WHEN 'BACK1'.
      LEAVE TO TRANSACTION 'ZCN41_N'.
ENDCASE.
ENDFORM.                    "user_command
include.....
*& Include           ZDATA_DECLARE
*& Tables used for the report
TABLES: proj, prps, aufk, afvc, jest, tj30t, afvv, prte.
*& Type Pools used
TYPE-POOLS: slis, icon, fibs, stree.
*& Class & Data defination
CLASS DEFINATION
CLASS cl_gui_resources DEFINITION LOAD.
DATA DECLARATION
DATA: g_lights_name TYPE lvc_cifnm VALUE 'LIGHT',
      pspid LIKE proj-pspid,
      l_pos TYPE i VALUE 1,
      gs_layout TYPE slis_layout_alv,
      color TYPE zcn41_color_n-color.
DATA : cnt VALUE 'X'.
DATA : i_repid TYPE sy-repid.
DATA : t_node TYPE snodetext.
DATA : node_tab LIKE t_node OCCURS 0 WITH HEADER LINE.
DATA : gv_diff TYPE p, stort LIKE proj-stort.
CONSTANTS: st_formname_top_of_page TYPE slis_formname
                              VALUE 'TOP_OF_PAGE-ALV'.
*& Internal Table Declarations
DATA it_proj   TYPE STANDARD TABLE OF proj WITH HEADER LINE.
DATA it_prps   TYPE STANDARD TABLE OF prps WITH HEADER LINE.
DATA it_afvc   TYPE STANDARD TABLE OF afvc WITH HEADER LINE.
DATA it_tj30t TYPE STANDARD TABLE OF tj30t WITH HEADER LINE.
DATA it_afvv   TYPE STANDARD TABLE OF afvv WITH HEADER LINE.
DATA it_jcds   TYPE STANDARD TABLE OF jcds WITH HEADER LINE.
DATA it_t001w TYPE STANDARD TABLE OF t001w WITH HEADER LINE.
DATA: BEGIN OF it_final OCCURS 0,
          stufe LIKE prps-stufe,
          pspnr LIKE prps-pspnr,
          t1      TYPE icon-id,
          t2      TYPE icon-id,
          node    LIKE node_tab,
          posid LIKE prps-posid,
          post1 LIKE prps-post1,
          ltxa1 LIKE afvc-ltxa1,
          txt04(20),
          objnr LIKE afvc-objnr,
          vornr LIKE afvc-vornr,
          aufpl LIKE afvc-aufpl,
          aplzl LIKE afvc-aplzl,
          fsavd LIKE afvv-fsavd, "Ear. Start date
          fssad LIKE afvv-fssad, "Ear. finish date
          werks LIKE t001w-name1,     " added after update
          stort LIKE proj-stort,     " added after update
     END OF it_final.
DATA: BEGIN OF it_hsk OCCURS 0,
        t2      TYPE icon-id,
        t1      TYPE icon-id,
        posid LIKE prps-posid,
        post1 LIKE prps-post1,
        objnr LIKE afvc-objnr,
        stufe LIKE prps-stufe,
      END OF it_hsk.
DATA: BEGIN OF it_new OCCURS 0,
        objnr LIKE afvc-objnr,
        fsavd LIKE afvv-fsavd,
        fssad LIKE afvv-fssad,
        udate LIKE jcds-udate,
        t2(10),
      END OF it_new.
CLEAR : node_tab, node_tab[].
DATA : entval TYPE prps-posid.
DATA : ct_fieldcat TYPE slis_t_fieldcat_alv.
DATA : BEGIN OF it_final_hsk OCCURS 0,
          node LIKE node_tab,
        END OF it_final_hsk.
DATA : project LIKE bapipr-project_definition,
        e_project_definition LIKE bapi_project_definition_ex.
DATA : e_wbs_hierarchie_table TYPE STANDARD TABLE OF bapi_wbs_hierarchie
        WITH HEADER LINE.
DATA : e_wbs LIKE e_wbs_hierarchie_table OCCURS 0 WITH HEADER LINE.
DATA: v_pstrm LIKE prte-pstrm, v_petrf LIKE prte-petrf,
       v_posnr LIKE prps-pspnr.
*& Selection Screen of the report
SELECTION-SCREEN BEGIN OF BLOCK pms WITH FRAME TITLE text-001.
SELECT-OPTIONS so_posid FOR proj-pspid OBLIGATORY.
SELECT-OPTIONS so_plant FOR proj-werks.
SELECT-OPTIONS so_loc FOR proj-stort.
SELECT-OPTIONS so_date FOR sy-datum.
SELECTION-SCREEN END OF BLOCK pms.
*AT SELECTION-SCREEN .
READ TABLE it_proj WITH KEY pspid = so_posid.
IF sy-subrc <> 0.
   MESSAGE 'Project Name dose not exist' TYPE 'E.
ENDIF.
include..
*& Include           ZSUBR
*&      Form date_difference
      text
--> p1        text
<-- p2        text
FORM date_difference .
CALL FUNCTION 'ZDATETIME_DIFFERENCE_N'
    EXPORTING
      date1                  = it_final-fsavd
      time1                  = '000000'
      date2                  = it_final-fssad
      time2                  = '000000'
   IMPORTING
     datediff               = gv_diff
   EXCEPTIONS
     INVALID_DATETIME       = 1
     OTHERS                 = 2
IF sy-subrc <> 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " date_difference
*&      Form date_monitor
      text
--> p1        text
<-- p2        text
T1 for more than 1 days activities
Subroutines result out the T1 on basis of 80% of activity ( Green )
or if 20 % reamined. ( Yellow )
FORM date_monitor .
DATA: date TYPE string,
        temp_date TYPE string,
        lv_date LIKE afvv-fsavd,
        lv_date_final LIKE afvv-fsavd,
        lv_days LIKE bseg-dtws1 VALUE 0.
CONSTANTS: con TYPE f VALUE '0.8'.
*lv_date = it_new-fsavd.
IF gv_diff EQ 2.
    lv_days = 1.
    CALL FUNCTION 'ZCALC_DATE_N'
      EXPORTING
        date      = it_final-fsavd
        days      = lv_days
        months    = '00'
        sign      = '+'
        years     = '00'
      IMPORTING
        calc_date = lv_date_final.
    IF sy-datum LE lv_date_final.
      it_final-t1 = '@08@'.
    ELSEIF sy-datum GT lv_date_final AND
           sy-datum EQ it_final-fssad.
      it_final-t1 = '@09@'.
    ENDIF.
ELSEIF gv_diff > 2.
    lv_days = con * gv_diff.
    CALL FUNCTION 'ZCALC_DATE_N'
      EXPORTING
        date      = lv_date
        days      = lv_days
        months    = '00'
        sign      = '+'
        years     = '00'
      IMPORTING
        calc_date = lv_date_final.
    IF sy-datum LE lv_date_final.
      it_final-t1 = '@08@'.
    ELSEIF sy-datum GT lv_date_final AND
           sy-datum EQ it_final-fssad.
      it_final-t1 = '@09@'.
    ENDIF.
ENDIF.
ENDFORM.                    " date_monitor
this code will give you exact out put as you required from bootom to top functinality....with status....

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

Parent Child Hierarchy Issue

Guys,
I have a parent-child hierarchy and users would select a randomn level from the prompt (Hierarchical column used in the prompt). So for the level selected I need to capture all the leaves and put a top n function on them.. Any ideas??
Things that i have tried are using Selection steps with hierarchical columns.
Step 1: Start with all Memebers
New step: Step 2 is Selected Members based on hierarchy relation Ship (Keep only members of leaves of hierarchy)
But the problem is I am not able to override the Step -2 with dashboard prompt. I was able to do only fior STEP -1
So any ideas??
If i can atleast capture all the leaves of selecte level from the prompt that would solve my problem to a large extent?/ Thought abt Hierarchical Navigation Functions but didnt succeed?? Any suggestions really appreciated
Thanks..
Prash
Edited by: Prash11 on Aug 6, 2012 11:14 AM

I have got lot of hierarchies which are atleast 20 levels deep. So its not really feasible for me to create multiple views for multiple levels.
I tried to use hierarchical column functions and it works but not able to override the values from prompts in the selection steps. So still trying few things
Step 1: Start with All members (over ride with prompt checked)
Step 2: Select a level with in the hierarchy and Keep only leaves of the selected level
Step 3: Apply Condition do a TOP 10 and keep only that result set.
This works fine with out any issues from an ad-hoc stand point. Only problem there is no way for me to over ride the dashboard prompt value in Step - 2 as it expects me to select a value from the hierarchy. Any alternativeS?

Parent Child Hierarchies

Similar Messages

Maybe you are looking for