Time dependent employee hierarchy

HELLO GUYS
I Need HELP ON CREATING 0EMPLOYEE time dependent Hierarchy in bw using r/3 data. i am trying to bring r/3 hr organization chart which has employee hierarchy into bw. i am wondering if anyone did this using functional module or extractor
please LET ME KNOW the process .i am not able to get this using ABAP and i need help on this.

Following document might be helpful.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20a709c1-0a8e-2a10-21b4-f779728c63bf?quicklink=index&overridelayout=true

Similar Messages

Time dependent employee master data reading !in sap-bw

Hi,
Here iam using one routine to read employee master data.
as employee is a time dependent characteristic,we want employee monthly details from the period of joining to till now with all his status.(these status characteristics are attributes of 0employee master table).
how to code for this requirement.
regards,
swami.

Hi,
Why do you want to delete ?
No need to delete any Master Data
If you want to really delete ,you can do one thing
Right click on Master data Info Object 0EMPLOYEE
select Delete master data
And reload Master data for employee with full load
if delta Initilize delta with data transfer
Regards
Hari

Time dependent employee master data reading !

Hi,
Here iam using one routine to read employee master data.
as employee is a time dependent characteristic,we want employee monthly details from the period of joining to till now with all his status.(these status characteristics are attributes of 0employee master table).
how to code for this requirement.
regards,
swami.

Found it...
http://help.sap.com/SAPHELP_ERP2004/helpdata/EN/49/7e960481916448b20134d471d36a6b/content.htm
Regards
Juan

Hierarchy with time-dependent structure

Hello, collegues,
Im attempting to build a report on payrolll data using DS 0HR_PY_1_CE.
There is a time-dependent structure hierarchy which changes very often (new departments are created\dispatched) on 0ORGUNIT.
The data granularity in infoprovider is Calmonth.
To build a report we need to use a derivation either for the beginning or for the end of month.
In case of a new department creation with derivation set for the last day of month - new department will show up in the report asigned to the right place on organizational strucure tree.
If a department being disbanded during the month (since the derivation is set for the end) - the amount will go into not assigned hiearachy nodes which is unaccetable for the business.
The same thing happens vice versa.
Any ideas will be highly appreciated.

hi,
we have faced the same problem with closed-org units some orgunits get closed over a period of time and they will be in the un assigned nodes in bw.
its the structure thats maintained in the source and we only get them from the source as it is and we are only loading to bi based on the standrad extractor and its does not pick closed org units.
my idea would be we need to build a custom extractor based function module which would read the hirarchies based on version and and based on time and keep them in the relevant nodes according to the bussineeds and we can load it to org unit and build hirearchy node variables on them in the report.
hope this helps.
Thanks
krishna.y

Two versions of time-dependant hierarchy?

Hi,
Is it possible to have 2 versions of time-dependant( entire hierarchy) .. if yes how... Thanks

Hi,
transaction RSD1.
Change your InfoObject.
Select TabStrip Hierarchy
Switch on the flags:
-with hierarchies
-Hierarchy is version dependent
- entire hierarchy is time-dependent
So this means it is possible. But I have never heared about a need of both in the reporting.
Kind reg.
Michael

Time dependent Hirarchy Structure

Hi,
I need to create Hirarchy, i did not create before,
Please some one explaine me how to create     Time dependent Hirarchy Structure in CostCenter InfoObject.
Please, please help me.
Thanks

HI
Find the below link
http://help.sap.com/saphelp_nw2004s/helpdata/EN/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
Time-Dependent Hierarchies
Use
In a hierarchy that is not time dependent, the characteristic values are always the same.
If you want to create views of a hierarchy that are valid for a specific time period, you need to create the entire hierarchy as time dependent.
If you want to model relationships that change time-dependently, you need to create the hierarchy structure time-dependently.
Functions
In InfoObject maintenance, you can set whether and in which ways a hierarchy is time dependent. You can choose from the following:
·         whether the hierarchy is not time dependent (Hierarchy Not Time-Dependent). This is set by default.
·         whether the entire hierarchy is time dependent (Entire Hierarchy Time-Dependent).
·         whether individual node relationships are time dependent (Hierarchy Structure Time-Dependent)
·         whether a temporal hierarchy join is used with time-dependent hierarchy structures (Use Temporal Hierarchy Join)
Entire Hierarchy is Time-Dependent
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy). When you create a time-dependent hierarchy, you have to enter a validity interval (valid to and valid from fields).
If an entire hierarchy is time dependent, the system creates hierarchy versions that are valid for separate intervals. The system automatically uses the current valid version in this case. The hierarchy valid in each case can be uniquely identified by its technical name and the From-To Date.
In the InfoObject tree of the Data Warehousing Workbench, all time-dependent hierarchies under the associated InfoObject are displayed with the corresponding To Date, for example Time-Dependent Hierarchy 05/31/2000.
In reporting, the system returns the valid hierarchy when a query is executed using the query key date.
Within a restructuring company areas, you can create time-dependent versions of a hierarchy for the Main Area InfoObject. This enables you to compare the restructuring over different time periods in a query.
Time-dependent hierarchy 01/01/1999 - 05/31/1999
Time-Dependent Hierarchy 06/01/1999 - 12/31/1999
Main Area NORTH
Main Area NORTH
Area 1
Area 2
Area 2
Main Area SOUTH
Main Area SOUTH
Area 1
Area 3
Area 3
Area 4
Area 4
In reporting, you can work in the individual columns of the report structure with fixed date values. You may want to do this to compare Main Area North in the Time-Dependent Hierarchy 05/31/2000 with Main Area North in the Time-Dependent Hierarchy 06/01/2000 (simulation).
Time-Dependent Hierarchy Structures
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy).
In hierarchy maintenance, you can determine a valid time interval for each hierarchy node (Valid to and Valid from fields).
In reporting, a hierarchy with time-dependent hierarchy structures is created either for the current key date or for the key date defined for the query. In addition, you can evaluate a hierarchy historically using the temporal hierarchy join.
You can assign an employee to different cost centers at different times within the context of a restructuring.
In the context menu of a hierarchy, choose Display Hierarchy to access the hierarchy display: Each node and leaf has been given a date symbol. Hierarchy nodes that are assigned to different places in the hierarchy structure, depending on the time, are displayed more than once. By double clicking on a hierarchy node, you can display the associated validity period for the node relation.
In the following example, you can double click on the Jones leaf to see that the worker Jones was assigned to region USA between 01/01/1999 and 05/31/1999 and Puerto Rico from 06/01/1999 to 12/31/1999.
In order to use a hierarchy with a time-dependent hierarchy structure in reporting, you require the following settings in the BEx Query Designer:
                            a.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure for a fixed key date, enter the key date in query definition.
                            b.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure historically, for a key date that is to be derived from the data, choose the temporal hierarchy join option and specify the derivation type for the key date.
For a more detailed description of the functions and differences between the two evaluation views, see Time-Dependent Hierarchy Structures in the Query.
In maintenance of the key date derivation type (RSTHJTMAINT) determine the rule you want to use to determine the key date from the data. In this way you determine the time characteristic and way in which the key date is to be derived.
       1.      First determine the time characteristic.
If you choose a Basic Time Characteristic as a time characteristic (for example, 0CALDAY, 0CALMONTH, 0FISCPER), you can use a key date derivation type of this kind for all InfoProviders that contain exactly one time characteristic that references the selected basic time characteristic. If there are several time characteristics in an InfoProvider that reference the basic time characteristic, you have to either determine the time characteristic more specifically or select a particular time characteristic from a particular InfoSet (Time Characteristic from InfoSet).
       2.      Determine how you want the key date to be derived from the time characteristic.
The following derivation types are available:
¡        First day of the period
¡        Last day of the period
¡        Delay by number of days (you specify this in the Delay by Days field). In this case, the key date is calculated from the first day in the period plus the number of days specified minus 1. If the key date does not fall within the period, the last day of the period is used.
Key date derivation type with (basic characteristic = 0CALMONTH, derivation type = u201Cfirst day of periodu201C):
·         For January 2005 the key date is calculated as 1/1/2005.
·         For February 2005 the key date is calculated as 2/1/2005.
Key date derivation with (basic characteristic = 0FISCPER, derivation type = u201Cdelay by number of daysu201C and u201Ddelay u201C = 29):
·         For K4/01.2005 the key date is calculated as 1/29/2005.
·         For K4/02.2005 the key date is calculated as 2/28/2005.
·         For K4/03.2005 the key date is calculated as 3/29/2005.
Note that the way in which you determine the key date derivation type affects performance. The number of data records that the OLAP processor reads corresponds to the level of detail on which the time characteristic and the leaf level lie. For this reason, choose the time characteristic as approximately as possible in order to keep the hierarchy small.
A small hierarchy has 100 leaves. For a period of 12 months, the OLAP Processor reads 1200 data records at month level. At day level, it reads 36500 data records.
Regards,
kumar reddy.k
Edited by: kumar reddy on Nov 18, 2008 10:50 AM

Time-dependent BW hierarchies in Analysis for OLAP

Hi all,
We are using time-dependent hierarchies in combination with a key date variable.
Tools used: Query designer based on SAP BW 7.4 and BO 4.0.
The following steps are executed:
Report is executed and key date is prompted
According to the key date, the correct time-dependent organisation hierarchy will be used in drill-down
Bring up variable screen again and select different key date
The drill-down changes according to the now correct time-dependent organisation hierarchy
The above scenario works for BEx Analyzer, BEx Web, Analysis for Office - but not for Analysis for OLAP.
Whenever I run through this scenario and confirm the updated key date, the following error is displayed:
cube.get.dimension.info.runtime.error : java.lang.IllegalStateException: There is no default hierarchy for dimension [ORG].
In the user guide I don't find any specifics about the hierarchies and since it works in all the other applications, I wonder where the error is coming from. I also could not find it anywhere else in the forum.
Has anyone experienced the same error or any suggestions?

Hi Peter,
This issue is captured in SAP Note 1941865. Resolved in 4.0 (8.5, 9.2 or SP10) and 4.1 (1.6 or SP03).
Symptom
In BI 4.1, Analysis for OLAP returns errors similar to:"An error occurred in the MDAS service while processing a request from Analysis, edition for OLAP. Try the operation again. If the problem persists, please contact your administrator. (AOC00041)" and/or "cube.get.dimension.info.runtime.error: java.lang.IllegalStateException: There is no default hierarchy for dimension [DIMENSIONNAME]"
The BW Query the AOLAP workspace is created against has 2 different hierarchies that have the same text description
Environment
SAP BusinessObjects Business Intelligence platform 4.0
SAP BusinessObjects Business Intelligence platform 4.1
Analysis, edition for OLAP
Reproducing the Issue
In CMC, create an OLAP BICS connection to a multi provider
Connect to BI launchpad and launch Analysis, edition for OLAP.
Use the connection to create a new workspace.
The error is observed
Cause
This issue has been logged as a defect under ADAPT01720287 for BI4.0 and ADAPT01713663 for BI4.1
Resolution
A fix for this issue is included in the following maintenance releases:
BI4.0:
Patch 8.5
Patch 9.2
Support Pack 10
BI4.1:
Patch 1.6
Support Pack 03

Time Dependent

Hi
Can you please let me know how we can make the hierarchy in BW as time dependent.This hierarchy is created in r/3 using SETS.
Do we need to make the hierarchy as time dependent in R/3 itself to make it time dependent in BW or otherwise.
Thanks in advance.
Sarah.

yes your ABC object should be time dependent on BI.
does that mean I have to create sets as time dependent.
no need to create the set as time dependent(the system will figure it out for you), provided the master data of the object should be time dependent.
Meaning - if you have a cost center 1000(master data), it should be have a couple of more fields line date to and from, that would say that the object is time dependent

Creation of Time Dependent Hierarchy in R/3

Any ideas on how to create a time dependent Hierarchy in R/3?
Do we have any existing functionality we can leverage in R/3 for creating and maintaing time dependent hierarchy or through ABAP coding in R/3?
Any ideas or documentation will be helpful.

Hi Jasmine,
check this documents/links to get an idea how to set up hierarchy extractor in R/3
[How to Create a Hierarchy Extractor for Employees and their Department Managers|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20a709c1-0a8e-2a10-21b4-f779728c63bf]
Re: Build Hierarchy with ABAP
How to create datasource for hierarchy
Double post: Creation of Time Dependent Hierarchy in R/3
Regards
Andreas

0CS_Item with time-dependent hierarchy

Dear Experts,
we are discussing pros and cons for a time-dependent item catalog (characteristic 0CS_item with time dependent hierarchy in BW) within consolidation SEM BCS 4.0. Does anybody has experiences on this topic?
I am quite sure it will be a performance issue and it means additional reporting effort (e.g. using reference period/year in the report comparing different hierarchies).
I am not sure if there are any other risks so I it would be great if anybody has some hints.
Thanks in advance,
Birgit Laux
Message was edited by: Birgit Laux

Birgit,
Some other things to consider:
- frequency of changes to item hierarchy. Could lead to a lot of item hierarchies in BW over time.
- hierarchy validity date does not seem to be displayed when running web queries and thus makes it difficult for the user to select the correct hierarchy when executing the query. Still looking for a fix for this.
- greater complexity in overall design. Is it really necessary to achieve correct financial statement presentation?
Virtual cube performance is not great but you could implement the data mart which provides typical BW query performance.
I stayed away from setting the item as time dependent for these reasons.
Brian

Restricting time dependent records on employee master data in BW

Experts,
We have a Future hire report which gets data from 0Employee. Now whenever hire date of an employee is getting assigned in case of new hire record get's created in BW.
Now, due to some reason this new hire employee is not able to join on the hire date first assigned to him and new hire date is updated in PA30 for this employee in ECC.
This would create a new record in BW with new hire date for this employee which is valid in BW from the date it moved into BW till 9999 and the previous record 'Valid To' date is changed to previous date of the "Valid From" date of newly entered record.
Now all these records has moved into Multiple Cubes also therefore we cannot delete these records from Master data until transaction data is delete.
Client HR team is saying that previous records of all such employees are not valid , so they should not appear in BW reports even if they are running this report on historical dates.
0Employee is time dependent master data. So it makes sense to have one records for any actions done for an employee in HR system.
Cleaning up a master data for all such employee would be a tedious task and need lot of effort.
Is there any way , we can restrict previous records of all such employee , so that they do not appear in BW report in case users are going to run the report previous dates.

We were doing this activity as part of weekly house keeping job. Weekly we get list of invalid PERNR records from ECC team.
While deleting particular PERNR (say 10015824) from 0EMPLOYEE, and the log (SLG1)says, SID exists in DIM table (like /BIC/D0PA_C011).
First delete that PERNR (10015824) from cube (0PA_C01)
Use Tcode RSRV --> Tests in Transaction RSRV --> All Elementary Tests --> Transaction Data --> Entries Not Used in the dimension of an InfoCube (Dbl Click)
             From the right side window, expand “Entries Not Used in the Dimension of an InfoCube” Node &
             Enter InfoCube (like 0PA_C01), click “Transfer”
             Now, click “Execute” (Toolbar)… and the results displayed in the right side window..
             Now, click “Correct error” (Toolbar)
Now, try to delete same PERNR from 0EMPLOYEE, and if the log says SID used in some other DIM table, follow the above process.
If the log says, the SID used in DSO/Cube, then goto manage (of DSO/Cube) and do the selective deletion.

Why time-dependent not work for cost center and profit center hierarchy

Has anybody been able to successfully turn on time-dependent for cost center hierarchy? Looks like the R/3 datasource 0COSTCENTER_0101_HIER is defaulted to be NOT time-dependent, and I dont know how to change the R/3 configuration to enable time-dependent for this datasource.
Here is what I found. If you go to RSA2 in R/3 and enter datasource 0COSTCENTER_0101_HIER, and then select "Hierarchy Info", you will see that all the time-dependent properties are unchecked by default. By comparison, Cons Unit datasource 0CS_UNIT_CSCU_HIER has Version Dependent Hierarchy as selected, and we are able to load Cons Unit hierarchy as time-dependent, but have no luck so far with the Cost Center hierarchy.
Can any BI guru tell me how I can make time-dependent work for the cost center hierarchy?
Thanks a bunch!

Check SETLEAF and SETNODE.
Basically CO Master data groups dont have seperate tables. They will be available in above tables. Choose proper Set class to filter the results

0ORGUNIt time dependent hierarchy not showing all valid nodes in BO , but in BW its correctly shown

Hi All,
We have 0ORGUNIT hierarchy shown in one of the Webi reports. 0ORGUNIT is time dependent hierarchy.
In BW report we can see below nodes for hierarchy
Hierarchy                     Valid From         Valid To
Z05 Root Company        01.07.2013        31.12.9999 - Parent node
    Z05 Branch 2                 01.10.2013        31.12.9999 - Child Node
    Z05 Division                   09.12.2013        31.12.9999 - Child Node
In BO webi we can see only two nodes
Z05 Root Company        01.07.2013        31.12.9999 - Parent node
       Z05 Division                   09.12.2013        31.12.9999 - Child Node
Any idea why in BO webi the other node is not shown ? This is happening only for time dependent hierarchy and only in BO not in BW.
Thanks,
Shraddha

Hi Shraddha ,
Check at webi query panel level any restrictions applied to hierarchy levels.
Check at BEx query level,select 0ORGUNIT ,hierarchy -Expand to level .
Here specify Max level.
lastly, check any filters/restrictions applied on data.If yes,remove restrictions.

Time-dependent hierarchy in query selection screen

Hello all
I am running query where input selection has following fields -
Fiscal year variable ( e.g. i can enter 2008)
Period variable ( e.g. i can enter 12)
Hierarchy Node variable
The hierarchy is time-dependent. I want that if I enter year and period as 2008 , 12 then
my hierachy node selction pop-up should show me only that hierarchy structure which was valid in 12.2008.
But my hierarchy selection always shows me hierachy structure that is valid on current date.
Can anyone help me on how to achieve this?
I have already coded keydate variable based on fisc year and period. But then how to make use of this key date variable so as to get correct selection of hier?
Regards,
Sanjyot

Hi Marcio
RSRHIERARCHYVIRT is for maintaining time-characteristics hierarchy.
My hierarchy is based on Consolidation Groups and Units.
But the hier is time-dependent.
So I want that when selection pop-up opens for a hier node , it should show me correct hier depending on year and period i have enetered.
Regards,
Sanjyot

Selection of time-dependent hierarchy variables after selection of time

Hi guys,
I'm having the following question regarding the selections of variables in a BEx Query:
I need to select e.g. a position out of a hierarchy which is time-dependent. In the selection screen I'm only able to select a certain date but not the key date that I need for the hierarchy. Now I would like to replace the needed key date for the hierarchy out of the date value. Having the parameters for the hierarchy selected I would like to select a position of the right hierarchy.
My idea is to select the date first:
Date: 05.2009
In the next pop up window the hierarchy key date is replaced by the date:
Date: 05.2009 --> key date: 05.2009
Now I can select a position for the right hierarchy.
Is a two-stage selection possible? How can a variable be replaced and simultaneously serve in the selection of object with a hierarchy?
Thanks in advance!

Hi Partho,
Please check this link. Might be helpfull.
http://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/page551.html
Regards,
Rahul

Time dependent employee hierarchy

Similar Messages

Maybe you are looking for