Employee hierarchy in hr to bw

i am new to hr implementation . our company maintain hr employee hierarchies in hr system . i have told to brig that organization chart into bw. i need help on this.. what all i need to bring into bw..what info object and info area or module?
please help me to undestand if there is any sap standard for this

Hi can you please give me more detail ..if i need to do anything in BW sides or R/3 sides. user want to tie up sales info into this organizational chart so they can see who this sales guy is reporting to...
so i activated the ds and ods..then is there any configuration i need to do? any special extraction?
appreciated

Similar Messages

Urgent:::how to get the employee hierarchy

hi all.
let me know how to get the employee hierarchy in HR organizational management.
like when we give emp id it shows developer name---superior( team lead name)-superior(project lead name)---
points will be rewarded for valuable answer.

Hi,
1) You can use the relation '002' in the table HRP1001, between the position of developer (objid) and get the position of team lead (sobid field). With the position of the team lead got in SOBID field... with the relation '008' get the person name.
2) You can use the transaction PPOM_OLD to view the reporting structure...
Regards,
Meera

Nakisa Org Chart 3.0 SP1 - Employee Hierarchy - Detailed View

Hi All,
I am recieving a wierd error when accessing the detailed view of the employee hierarchy. The message on each employee box says "Non FlexML Content". I've checked on SDN and on the SMP and I do not see any reference to this error.
I was wondering if anybody has seen this before?
I've checked the log and there are no errors.
thanks.
JB

Hi Jamie,
Are you using the SMP version? If so, this is a bug in the OOTB version. You need to get the latest SP1 build.
Best regards,
Luke

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

BW Employee Hierarchy report to be specific for the users.

Hi *,
My BW system contains the data from HR. There is a report which displays the list of all employees in a strict hierarchial manner with the topmost position being assigned to the highest designation.
Now the change to this report should be done in such a way that the user who logs in should be able to see only his/her group. That is all the employees who report to him should be displayed with this user at the top.
Is it possible ? I can create a new report also if required.
Please suggest so that I can assign points.
Regards,
Srinivas

Hi Srinivas,
First u need to make that Info Object as Auth Relevant.
InfoObject > BusinessExplorer tab > Auth Relevant
In RSSM u need to generate the Auth Object for that.
Authorization Object
Regards,
Ram.

Stored Procedure- Multil level employee hierarchy in the same row

I have an employee table where I have employee details which includes the following properties:
EmployeeID, EmployeeName, ManagerID, DesignationCode.
ManagerID maps to EmployeeID in the Emp table. DesignationCode is to identify the employee designation.
The topmost person of the organization could be identified by : whose DesignationCode is 'XX' and ManagerID=EmplyeeID.
Here, 'XX' is fixed and will not change.
Also, we know there could be a maximum of 10 level for each hierarchy.
Example: Employee1 reports to Manager1 who reports to Manager2 who reports to Manager 3 ..... who reports to ManagerN.
I need to pull a hierarchy in the below format:
EmpName MgrName0 MagrName1 MgrName2 ..........MgrName7 MgrName8
MgrName9
SAMRAT
 XXX XXX
SUDHAKAR
XXX XXX XXX
SATESWAR
 XXX XXX
SRINI XXX XXX
XXX XXX XXX
IMPORTANT POINT: We need to identify the reporting hierarchy level for each employee's manager and then place the manager names accordingly based on the columns.
Example:
If an employee's manager has only 1 reporting manager(who is at top level), then he would be placed at the column "ManagerName8" and ManageName9 would be the topmost employee of the organization
In short, we need to identify the reporting level at which the employees manager belongs and then start filling the columns values for that row ( employee details)
I am stuck and unable to do the same. Please help.
Thank you.

Please post DDL, so that people do not have to guess what the keys, constraints, Declarative Referential Integrity, data types, etc. in your schema are. Learn how to follow ISO-11179 data element naming conventions and formatting rules. Temporal data should
use ISO-8601 formats. Code should be in Standard SQL as much as possible and not local dialect.
This is minimal polite behavior on SQL forums.
>> I have an employee table where I have employee details <<
An SQL programmer would have a Personnel table instead. What you have said is that you have only one employee!
>> which includes the following properties:
emp_id, emp_name, manager_emp_id, designation_code.<<
Why do you think that a manager is an attribute of an employee? This is absurd! They have a relationship; where is the table that models that relationship? It is missing from this non-normalized, improperly designed table.
There are many ways to represent a tree or hierarchy in SQL. YOU are trying to use an adjacency list model. This approach will wind up with really ugly code -- CTEs hiding recursive procedures, horrible cycle prevention code, etc.
Another way of representing trees is to show them as nested sets.
Since SQL is a set oriented language, this is a better model than the usual adjacency list approach you see in most text books. Let us define a simple OrgChart table like this.
CREATE TABLE OrgChart
(emp_name CHAR(10) NOT NULL PRIMARY KEY,
lft INTEGER NOT NULL UNIQUE CHECK (lft > 0),
rgt INTEGER NOT NULL UNIQUE CHECK (rgt > 1),
CONSTRAINT order_okay CHECK (lft < rgt));
OrgChart
emp_name lft rgt
======================
'Albert' 1 12
'Bert' 2 3
'Chuck' 4 11
'Donna' 5 6
'Eddie' 7 8
'Fred' 9 10
The (lft, rgt) pairs are like tags in a mark-up language, or parens in algebra, BEGIN-END blocks in Algol-family programming languages, etc. -- they bracket a sub-set. This is a set-oriented approach to trees in a set-oriented language.
The organizational chart would look like this as a directed graph:
Albert (1, 12)
Bert (2, 3) Chuck (4, 11)
/ | \
/ | \
/ | \
/ | \
Donna (5, 6) Eddie (7, 8) Fred (9, 10)
The adjacency list table is denormalized in several ways. We are modeling both the Personnel and the Organizational chart in one table. But for the sake of saving space, pretend that the names are job titles and that we have another table which describes the
Personnel that hold those positions.
Another problem with the adjacency list model is that the boss_emp_name and employee columns are the same kind of thing (i.e. identifiers of personnel), and therefore should be shown in only one column in a normalized table. To prove that this is not
normalized, assume that "Chuck" changes his name to "Charles"; you have to change his name in both columns and several places. The defining characteristic of a normalized table is that you have one fact, one place, one time.
The final problem is that the adjacency list model does not model subordination. Authority flows downhill in a hierarchy, but If I fire Chuck, I disconnect all of his subordinates from Albert. There are situations (i.e. water pipes) where this is true, but
that is not the expected situation in this case.
To show a tree as nested sets, replace the nodes with ovals, and then nest subordinate ovals inside each other. The root will be the largest oval and will contain every other node. The leaf nodes will be the innermost ovals with nothing else inside them
and the nesting will show the hierarchical relationship. The (lft, rgt) columns (I cannot use the reserved words LEFT and RIGHT in SQL) are what show the nesting. This is like XML, HTML or parentheses.
At this point, the boss_emp_name column is both redundant and denormalized, so it can be dropped. Also, note that the tree structure can be kept in one table and all the information about a node can be put in a second table and they can be joined on employee
number for queries.
To convert the graph into a nested sets model think of a little worm crawling along the tree. The worm starts at the top, the root, makes a complete trip around the tree. When he comes to a node, he puts a number in the cell on the side that he is visiting
and increments his counter. Each node will get two numbers, one of the right side and one for the left. Computer Science majors will recognize this as a modified preorder tree traversal algorithm. Finally, drop the unneeded OrgChart.boss_emp_name column
which used to represent the edges of a graph.
This has some predictable results that we can use for building queries. The root is always (left = 1, right = 2 * (SELECT COUNT(*) FROM TreeTable)); leaf nodes always have (left + 1 = right); subtrees are defined by the BETWEEN predicate; etc. Here are
two common queries which can be used to build others:
1. An employee and all their Supervisors, no matter how deep the tree.
SELECT O2.*
FROM OrgChart AS O1, OrgChart AS O2
WHERE O1.lft BETWEEN O2.lft AND O2.rgt
AND O1.emp_name = :in_emp_name;
2. The employee and all their subordinates. There is a nice symmetry here.
SELECT O1.*
FROM OrgChart AS O1, OrgChart AS O2
WHERE O1.lft BETWEEN O2.lft AND O2.rgt
AND O2.emp_name = :in_emp_name;
3. Add a GROUP BY and aggregate functions to these basic queries and you have hierarchical reports. For example, the total salaries which each employee controls:
SELECT O2.emp_name, SUM(S1.salary_amt)
FROM OrgChart AS O1, OrgChart AS O2,
Salaries AS S1
WHERE O1.lft BETWEEN O2.lft AND O2.rgt
AND S1.emp_name = O2.emp_name
GROUP BY O2.emp_name;
4. To find the level and the size of the subtree rooted at each emp_name, so you can print the tree as an indented listing.
SELECT O1.emp_name,
SUM(CASE WHEN O2.lft BETWEEN O1.lft AND O1.rgt
THEN O2.sale_amt ELSE 0.00 END) AS sale_amt_tot,
SUM(CASE WHEN O2.lft BETWEEN O1.lft AND O1.rgt
THEN 1 ELSE 0 END) AS subtree_size,
SUM(CASE WHEN O1.lft BETWEEN O2.lft AND O2.rgt
THEN 1 ELSE 0 END) AS lvl
FROM OrgChart AS O1, OrgChart AS O2
GROUP BY O1.emp_name;
5. The nested set model has an implied ordering of siblings which the adjacency list model does not. To insert a new node, G1, under part G. We can insert one node at a time like this:
BEGIN ATOMIC
DECLARE rightmost_spread INTEGER;
SET rightmost_spread
= (SELECT rgt
FROM Frammis
WHERE part = 'G');
UPDATE Frammis
SET lft = CASE WHEN lft > rightmost_spread
THEN lft + 2
ELSE lft END,
rgt = CASE WHEN rgt >= rightmost_spread
THEN rgt + 2
ELSE rgt END
WHERE rgt >= rightmost_spread;
INSERT INTO Frammis (part, lft, rgt)
VALUES ('G1', rightmost_spread, (rightmost_spread + 1));
COMMIT WORK;
END;
The idea is to spread the (lft, rgt) numbers after the youngest child of the parent, G in this case, over by two to make room for the new addition, G1. This procedure will add the new node to the rightmost child position, which helps to preserve the idea
of an age order among the siblings.
6. To convert a nested sets model into an adjacency list model:
SELECT B.emp_name AS boss_emp_name, E.emp_name
FROM OrgChart AS E
LEFT OUTER JOIN
OrgChart AS B
ON B.lft
= (SELECT MAX(lft)
FROM OrgChart AS S
WHERE E.lft > S.lft
AND E.lft < S.rgt);
7. To find the immediate parent of a node:
SELECT MAX(P2.lft), MIN(P2.rgt)
FROM Personnel AS P1, Personnel AS P2
WHERE P1.lft BETWEEN P2.lft AND P2.rgt
AND P1.emp_name = @my_emp_name;
I have a book on TREES & HIERARCHIES IN SQL which you can get at Amazon.com right now. It has a lot of other programming idioms for nested sets, like levels, structural comparisons, re-arrangement procedures, etc.
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL

Employee hierarchy

what's a better way to create employee dimension? say i have 10000 employee, it's not good there is only 2 generations,
how to categorize employee to create a hierarchy?

Hi,
You may have to think of some ways of grouping them mostly because aggregating a massive flat hierarchy is not walk in the park for Essbase.
Your options are not very diverse though. You can either use department codes to group them (possibly leading a duplication with entity dimension) or some virtual binders.
Department codes need no explanation I guess, it should reflect the organization hierarchy of the company with employees positioned under departments or sections. In the latter solution you can create binder members to group employees like below:
Employees (dynamic)
     Employee 0001-1000 (dynamic)
          Employee 0001-0100 (Store)
               Employee1 (with employee code)
               Employee2 (with employee code)
          Employee 0101-0200 (Store)
               Employee101 (with employee code)
               Employee102 (with employee code)
     Employee 1001-2000 (dynamic)
          Employee 1001-1100 (Store)
               Employee1001 (with employee code)
               Employee1002 (with employee code)
          Employee 1101-1200 (Store)
               Employee1101 (with employee code)
               Employee1102 (with employee code)
Consider making top two levels dynamic to save from aggregation time and disk space. As the members are not many in these levels, reporting will not be impacted much from dynamic members. You can bind employees groups of up to 300. Beyond this you may start seeing some slow down in aggregation but it depends on the design really, so it needs to be experimented.
You don't need to use binder members in forms or reports though. If you want other types of logical grouping of employees, you can assign attributes to them (i.e. salesman, officer, accountant etc.).
Cheers,
Alp

Position Hierarchy - Employee Supervisor Change

Hello,
We have few of our Operating Units setup with Position Hierarchy Approval method for Purchasing documents. We want to change this to Employee-Supervisor Relationship due to change in some of the global policies.
Would like to know what are the implications & what are the things to be taken care.
Thanks,
Shilpa

You will find that emp. Supervisor hierarchy (ESH) is simpler to setup and understand. But it has less functionality.
e.g. In PBH (position based hierarchy), you can submit PO's using different paths if necessary. But in ESH, the po always will go to the supervisor and his supervisor etc.
To implement your change
1) Go to the define employees screen (in the purchasing module if you use Shared HR or in the HRMS module if you use full HRMS). Enter the supervisor name for all employees that will submit /approve PO.
2) Purchasing > setup > organizations > financial options > Human resources tab > uncheck "Use approval hierarchies" checkbox
3) You can end-date existing hierarchies.
4) You don't have to run Fill employee hierarchy program anymore.
5) When a person leaves or there is a reorg, make sure you update the supervisor name for the employees.
6) You need to continue to maintain approval groups and assignments as before.
Hope this answers your question,
Sandeep Gandhi

Hierarchy not visible in Employee Lookup

Hi,
I have configured the Employee Lookup Fiori application. In the application, reporting employee hierarchy is not getting loaded as mentioned in the below screen shot
I have done the troubleshooting of the application as per the below link
SAP Fiori LL11 - Consultants should know about OData troubleshooting
I got the below 404 not found error
'/sap/opu/odata/sap/HCM_EMPLOYEE_LOOKUP_SRV/EmployeeInfoSet('40000026')/$value Failed to load resource: the server responded with a status of 404 (Not Found)\'
Also I looked the /IWFND/GW_CLIENT and found the exception as attached in the screenshot
Also in the Application log I found the exception as mentioned in the screenshot
Please anyone suggest
Regards
Pallavi

Hi Pallavi,
This is due to missing OADP configuration in the standard delivery. The oData service calls up the internal OADP configuration to read the data views HCM_EMP_DETAILS (for employee info on top) and HCM_EMPNAME_POS for the reporting employees to read the field configuration.
These data views have the column groups defined but contains no columns (fields) and that is why the app is not displaying any field as there are no columns defined.
Please create entries in table V_TWPC_ACOL_C (or in OADP SPRO node, navigate to Assign Columns to Column Groups).
Hope this helps.
Jigar

Employee/Supervisor and position based hierarchy combination

Hi All,
Can Employee/Supervisor and position based approval hierarchy used in the same Business Group? If I have OU1 and OU2 belonging to BG1. Can OU1 use employee supervisor and OU2 use position based?
Please throw some light on this setup and limitations.
Regards,
Praveen

Setup-->Financial Options-->Human Resources tab -->Use Approval Hierarchies check box. If you check uses approval hierarchies based on positions if not uses the employee hierarchy (supervisor in employee).
Thanks
Nagamohan

Navigation to find " Employee based hierarchy or Position Based Hierarchy "

Hi Experts,
Please let me know
Navigation to find Employee based hierarchy or Position Based Hierarchy.
regds
MRR

Setup-->Financial Options-->Human Resources tab -->Use Approval Hierarchies check box. If you check uses approval hierarchies based on positions if not uses the employee hierarchy (supervisor in employee).
Thanks
Nagamohan

In BEx, how to display hierarchy Upper Node with selected Lower Nodes only

Currently I am displaying the Cost Centre (GFL Responsibility Cost Centre) hierarchy in a workbook. I want to be able to filter on this hierarchy dynamically. E.g. the upper node must be displayed including the rolled up results for this node, together with a selection of the lower nodes e.g 2 nodes ( not all the lower nodes related to the upper node must be displayed in the query).
What's possible when filtering :
To filter on the 2 lower nodes only ( results are displayed as required)
Not possible:
When I include the higher node of the 2 lower nodes in the query, All the lower nodes of the higher node are displayed, and the filter selection of the lower nodes are over written.
This is logically what's expected when the higher node is included in the filter.
Creating a hierarchy variable gives the same problem, I am not able to filter on the hierarchy nodes as required.
 Upper Node
 Lower Node1 LowerNode2 LowerNode3
Filter the report for UpperNode and LowerNode 2 & 3 only
Thanking YOU in advance. Will reward points for the correct help

Hi
Do you want to show particular node or particular level ?
If you want particular node , then create hierarchy node variable and restrict to that node ( 3rd node)
If you want particular level, what does that mean say i am taking employee hierarchy and the hierarchy is as below.
Ihe setting that we have is to expand upto n levels but if yiou say i need level 2 what does that mean and how do you want to show in report ?
 A -
(level 1)
 B,C,D( --child of A ) --- level 2
 E(Child of B), F(Child of C) -
level 3.
Regards
vamsi

Parent Child Hierarchy Issue in OBIEE 11g

Hi All,
I am in OBIEE 11G v6. I have a sales fact table where the grain is one sale. So I have one row for every sale done.
Now I have a ragged employee hierarchy like this with David at the root node.
David >>Richard>>Sean
David >>James
Also, I have a role dimension which gives me what role each employee has performed on a sale. Only one employee can be associated with one sale. This is the way Roles have been asssigned
David = Manager
Richard = Off1
Sean = Off2
James = Off2
Both Sean and James can have same Roles. Now I have created a parent child hierarchy for my employee dimension and the closure table. Defined the member key, ancestor key relationship in the parent child setting etc.
Now in the report when I pull the parent child hierarchy and the sales_amount in the report, it comes out perfect with all the ragged hierarchy resolved. But the issue comes when I try to limit the report on Role = Off2. It gives me an error saying " The layout of this view combined with the data, selection , drills resulted in no data. Undo drill and view prompt values". Basically what i want is to be able to select any role type and then my hierarchy should be adjusted to show me that data. Like when I select Off2, I want to see David at the Top level and Sean and James under him because they are both Off 2 and David is their manager.
Is that possbile? Also, am I getting this error because when I select Off2 though it gets Sean and James but since David is not Off2, I don't get the data?
I hope I was able to explain the issue, any help on this would be greatly appreciated.
Thanks
Ronny

So basically this means that if I build a parent child hierarchy on table A having the stucture like
--David (Manager)
-----James (Off1)
--------Bill (Off2)
and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

Roll up of the formula results as per hierarchy in report

Hi,
I am using a employee hierarchy in report with key figure as ROWCOUNT and formlas as Total liability amount
Currently the report is showing the number of employee under its manager correct like if there are 5 employees under a employee E1.
Suppose there are 2 employees wose total liability amount is 0
The report is showing 5 as under E1.
But now user doesn't want to show the employees whose Total liability amount is 0.
So i make a condition to show only employees whose total liability amount is 0 but the report is still showing the number of employees as 5 (ROWCOUNT) instead of 3 although the employees with non zero total liability amount is displayed in the report.
SO,please suggest me how to achieve this.
Its would be a great help to me.

just need to properly maintain value categories..

I-Procurement problems with approval hierarchy - Urgent!! Please help!

Dear experts,
I am having a number of problems in i-procurement (12.1.3). When creating a Requisitions in i-procurement on the screen when it arrives with the approval list, it has retrieved a personel who is not in the hierarchy list at all. (not using AME just employee hierarchy)
I have checked the usual setting such as making sure the document type settings is correct and the position hierarchy for the position raising the requisition.
In addition to this once proceeding with submitting the requisition the created time is completly wrong. It is displaying a date occuring in the past. And in the Justification field it has already been populated it appears that it has captured information from a previous requisition. Furthermore in the created by field it also displaying a name of a different user to the one I am currently using.
I am out of ideas as to exactly what the problems is. Would appreciate if any I-procurement gurus can take a look at my issue.
Thanks and Regards
Ebsnoob

That sounds like a feedback loop.
Does the tone alter in pitch when you alter input and/or output levels or move your microphone?
And have you checked your coreaudio device in *Logic Pro>Preferences>Audio* ? And your recording settings in *File>Project Settings* ?
And how is your monitoring setup? Directly from the Presonus, or do you use *Software Monitoring* ?
Does the tone stop when you hit Pause ?
2nd possibility: a note event somewhere triggers a synth - but that would also happen in playback, so it is a long shot.... it does not happen in playback?
regards, Querik.
ps: the advantage of smashing up things is that then you are at least sure you can't fix it anymore. Better keep some broken stuff handy, because you'll regret smashing up working stuff.

Employee hierarchy in hr to bw

Similar Messages

Maybe you are looking for