Position Hierarchy Based on secondary assignments.

Hi,
We have created a position hierarchy. While defining the hierarchy, for a position, which is secondary assignment for a person, is visible.
However, when we create PO and forward to, the person whose secondary position is in hierarchy, is not coming in forward to list.
If we include primary assignment position in hierarchy, than the person is available in the forward to list.
Is there any sort of security of data working behind?
Abdul Wahid
http://iwidi.org

I understand, what you are looking forward is an Enhancement request
Have a look at the below ER
1351979: APPROVAL WORKFLOW TO ALLOW SECONDARY ASSIGNMENT IN POSITION HIERARCHY
Purchasing only uses the primary assignments for the purchasing functions.
To use the Position Hierarchy, it must be setup on the employee's primary
assignment.

Similar Messages

'Hierarchy Based Login' and 'Direct Reports' field in Dim - Position table

Hello -
I am trying to build a "My Team's" report, which basically shows the logged in Managers ( and his subordinates) revenues rolled up by default. Then the manager needs to drilldown on his name and see revenues grouped by his direct reports. I am using OBIEE 10G. In the out of the box RPD, there are two fields in the BMM layer called 'Hierarchy Based Login' and 'Direct Reports'.
1. The 'Hierarchy based Login' field uses the INDEXCOL method to get relevant column from the W_POSITION_DH table based on the the Logged in users hierarchy level (the hierarchy level is stored in a session variable (HIER_LEVEL). This session variable works fine and i have tested the SQL)
2. The 'Direct Reports' is using the same INDEXCOL method, just that it uses the formula HIER_LEVEL - 1. This works fine as well.
The issue i am facing is neither of these out-of-the-box fields are assigned to the Position dimension (the position dimension also exists OOTB).
So basically, i am able to create a manager and his direct subordinate report, but without any drill functionality.
I am trying to get the report to drill all the way down to the bottom most level of the heirarchy.
Any help to get this working is much appreciated

What i meant was neither of these out-of-the box fields are assigned to a Dimension Hierarchy ( there is a hierarchy called 'Position' that already exists out-of-the box). Other fields in the 'Dim-Position' table are assigned to a level in this position hierarchy, except these two. I guess what i am trying to achieve is to dynamically assign the hierarchy level based on the users Hierachy level in W_POSITION_DH table.
Thanks for spending time to look into my issue

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

Position Hierarchy in AME

Dear All,
I am new to AME. Can you please share the detail steps for using Position Hierarchy in AME. I understand approval limits are not honoured in AME.
We have a requirement that based on requistion type (regular, contract, Service) the approval should follow a different heirarchy and should have approval limits based on Positions . We enabled a DFF on requistion headers to determine the Req type.
Can we achieve this in AME.
KR,
Srikanth

Dear All,
I am new to AME. Can you please share the detail steps for using Position Hierarchy in AME. I understand approval limits are not honoured in AME.
We have a requirement that based on requistion type (regular, contract, Service) the approval should follow a different heirarchy and should have approval limits based on Positions . We enabled a DFF on requistion headers to determine the Req type.
Can we achieve this in AME.
KR,
Srikanth

Query regarding the Position Hierarchy.

Client Version:R12.1.3
We are setting up Position Hierarchy.
Have a query in the setup.
We have a position called Clerk--Number of Holders---2
Clerk --Holder 1 is reporting to Manager 1
Clerk Holder2 is reporting to Manager 2.
When we are trying to set the Hierarchy.
It is taking both the holders in consideration.
Request to assist.
Thanks in advance
Regards
Srini

914612 wrote:
Dear user13056460,
your query is very obvious you have a position type pooled and two employees are assigned to this position where in the hierarchy it shows two holder, if you want my opinion let each clerk have his own unique position as Clerk LA and CLerk DC by this you will not go through the headache of having two hierarchies and if youre having two hierarchies you need also to enable the document type (can change approval path option) the workflow engine by your scenario will get lost because two individuals have the same position so it will go to only one, options youre having
1- let the postion with a two holder but enable the users to select approval path and employee while submiting PO's
2- give each clerk a unique position name which is easier.
Let me know if you have any more inquiries
Regards
Ammar M. GhazalehAmmar,
That is what we have the requirment..
I tried changing the existing hierarchy..but it is not working..
For 2 clerks here..we created say 100.Purchase Clerk as Job and position as 200.Purchase clerk
for the second clerk it has same job as 100.Purchase Clerk as Job and position as 200.Purchase clerk1
(we changed a bit)
one clerk reports to one manager..and the manager reports to dept head.
one clerk reports to dept head..
so while in hierarchy dept has total 3 sub ordinates and when we drill down manager has 1 sub ordinates..
which makes sense...
i created approval groups also...and assignments too..
but when the newly created clerk logins and when he forwards documents..he is not seeing the default heiarchy..we have set this up in documents types..
and the second old clerk he is seeing this when he is forwading documents for approval..
where did i miss the setup?
Please Advise
Thanks
Mahendra
Edited by: 843237 on Feb 16, 2012 4:24 PM

Position Hierarchy Vs Organization Hierarchy

Hi
Our organization is position driven organization. I want to know what are the main advantages and disadvantages for Position Hierarchy and Organization Hierarchy.
Because on top the hierarchies we will create security profiles.
Can I have any document where I can find the comparison between both of these hierarchies.
Thanks
Gaurav

No, the supervisor hierarchy is constructed simply by specifying supervisors on assignments.
Added complexity can be added to the supervisor hierarchy in a multi assignment environment; you can then specify a 'supevisory assignment' as well but that is rare.
It sounds like you will be invariable be drawn into using Positions. Having a 1-1 relationship between positions and employees is not unusual but be warned it can be extremely time consuming to maintain. I have been to organizations where position maintenance is virtually a full time job for a member of staff.
If you are using Appraisals, definitely make use of the supervisor hierarchy, it is hard enough to implement correctly as it is without making it harder and trying to use the position hierarchy.
You should be able to use the supervisor hierarchy for the OTL and iRec approval processes too but I'm happy to defer to other experts on the forum for those.

Global Position Hierarchy....

Hi,
I have a question...this is a multiple Business Group situation. A Director Sales position lies in BG 2 and CEO's position lies in BG 1. Director Sales position reports to CEO's position and every request related to HR should/ must go to CEO's position for approval. How this scanario can be handeled. Is there any seeded functionality available to create a Global position hierarchy to create an approval group based on dynamic position.
Regards
Majid

I don't think there is any such feature available yet as Positions are partitioned by the Business Group. You will need to tweak your Approval Group queries...

Changing PO workflows to reference HR secondary assignments

Hi -
My client is currently implementing Oracle GL, FA, AP, AR, PO, iP, OPM, and OM. They are considering adding HR into the scope as soon as next week - however, only the portions of HR necessary for PO will be ready at our go-live. Based on this, I have one question. Has anyone had any experience with customizing Workflow to have the PO and Requisition approval workflows look at HR secondary assignments instead of primary? My client doesn't want to have to make their primary assignments to drive financial workflows. They would like to base the primary assignment on HR data and the secondary on the financial workflows.
Thanks!

Hi Michael,
Yes there is. In customizing under Personnel Management -> Organizational Management -> Transport. Check the documentation there for more information.
Regards,
Martin

Leave approval through Position Hierarchy

Hi All,
I have requirement regarding Leave approval which I want to perform through position hierarchy despite of immediate supervisor, can any body tell me the step where I can perform this through AME?
Regards,

You don't have to use the supervisor hierarchy. By using an AME rule, you can return the approver list using a wide range of logic. You can make use of the position hieracrhy, or you could choose to have an approver group based on some other logic. You will need to make sure that your transaction type (self service HR) has access to the appropriate action type (e.g. position hierarchy) to do this.
Regards
Tim

Differences between Position Hierarchy and Supervisory Hierarchy

Hi All,
Can somebody tell me the pros and cons of using Position Hierarchy and Supervisory Hierrarchy .
Regards,

If you use the Position hierarchy then you will have to go through the process of defining all of the positions / posts in your organisation and specifying all reporting lines in your organisation from top to bottom. You will then have the overhead of maintaining your positions and position hierarchy and keeping them in line with the business on a day to day basis.
If your organisation is fairly fluid, e.g. a project based organisation or an expanding organisation, these can be very significant overheads. Business re-organisation will create a large workload in creating new positions and migrating employees to them.
If you are in a fairly static organisation e.g. public sector then it may well be that the position structure is well documented and changes infrequently. In this case use of positions and position hierarchies is a simple data entry task and adds significant value.
The supervisor hierarchy is more flexible. It is simply a field held against the person record. However, there is very little validation on it so the you have to put manual processes in place to make sure the data is valid e.g. leavers are replaced and that no loops are created.
I would recommend NOT using positions unless yours is a public sector implementation.
Regards,
Andrew

SELECT QUERY BASED ON SECONDARY INDEX

Hi all,
CAN ANYONE TELL ME HOW TO WRITE SELECT QUERY BASED ON SECONDARY INDEX.
IN WHAT WAY DOES IT IMPROVE PERFORMANCE.
i KNOW WHEN CREATING SECONDARY INDEX I NEED TO GIVE AN INDEX NO -iT SHOULD BE ANY NUMBER RIGHT?
I HAVE TO LIST ALL PRIMARY KEYS FIRST AND THEN THE FIELD FOR WHICH I AM CREATING SECONDARY INDEX RIGHT?
LETS SAY I HAVE 2 PRIMARY KEYS AND I WANT TO CREATE SEONDARY INDEX FOR 2 FIELDS THEN
I NEED TO CREATE A SEPERTE SECONDARY INDEX FOR EACH ONE OF THOSE FIELDS OR ONE SHOULD BE ENOUGH
pLS LET ME KNOW IF IAM WRONG

HI,
If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVINGclauses, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
You create secondary indexes using the ABAP Dictionary. There you can create its columns and define it as UNIQUE. However, you should not create secondary indexes to cover all possible combinations of fields.
Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
What to Keep in Mind for Secondary Indexes:
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eb2d446011d189700000e8322d00/content.htm
http://www.sap-img.com/abap/quick-note-on-design-of-secondary-database-indexes-and-logical-databases.htm
Regards
Sudheer

Can we create a hierarchy based on two logical table in 10g RPD

Hi,
I have a question, please give me some clarity, about creating hierarchy,
I know we can create a hierarchy based on one logical table which is form by two physical table...
Can we create a hierarchy based on two logical table? If yes, and how?
Thanks in advance!
anne

Use preffered drill paths...
-suman

Problem creating hierarchy based on 2 physical dimension tables

I'm having a problem creating 1 logical dimension with a drill-down hierarchy, based on two separate physical dimension tables. The errors I receive when navigating the drill-down hierarchy is:
"Cannot find logical table source coverage for logical columns" &
"Missing join between logical tables".
I'm using OBIEE 10.1.3.4
Here are the details of what I have setup sofar:
Physical layer:
Dimension table DIM_ORG with columns:
-dimension_key
-org_total_code
-org_total_description
-org_detail_code
-org_detail_description
Dimension table DIM_DEPT with columns:
-dimension_key
-dept_total_code
-dept_total_description
-dept_detail_code
-dept_detail_description
Fact table FACT_SALES with columns:
-fk_org
-fk_dept
-sum_sales
Physical Joins:
FACT_SALES.fk_org = DIM_ORG_dimension_key
FACT_SALES.fl_dept = DIM_DEPT.dimension_key
Business Model & Mapping layer:
I created a logical dimension ORG_DEPT. It contains two logical table sources (DIM_ORG & DIM_DEPT) and the following logical columns:
- All Departments (mapped to dept_total_code)
- Organisation (mapped to org_detail_description)
- Organisation Number (mapped to org_detail_code)
- Department (mapped to dept_detail_description)
- Department Code (mapped to dept_detail_code)
The business logical key is based on the combination of Organisation Number & Department Code
The hierarchy I need is: All Departments -> Organisation -> Department so I created the following hierarchy for ORG_DEPT:
- Total Level containing: All Departments
- Organisation Level containing: Organisation Number (defined as the Logical level key) & Organisation (defined als the Drill level key)
- Detail Department Level containing: Department Code (defined as Logical level key) and Department (defined as Drill level key).
In the LTS of the dimension ORG_DEPT I've set the Content levels for the sources:
DIM_ORG : Organisation Level
DIM_DEPT: Detail Department Level
In the LTS no -inner- joins have been added against related physical tables.
I created a logical fact table SALES (based on the physical fact table) and joined it against the logical dimension table ORG_DEPT.
In the LTS the Content level for ORG_DEPT is set against the Detail Department Level. No - inner- joins have been aded against related physical tables.
When I create a report in Answers to test the hierachy and select only 'All Departments' I get the correct dimension value returned. When I try to drill to the next level I get the following ODBC error:
"Cannot find logical table source coverage for logical columns: [All Departments]. Please check more detailed level keys are mapped correctly".
When I create a report in Answers and select both 'All Departments' and 'Sales' I get the correct result. When I try to drill to the next level I get a different ODBC error:
"Missing join between logical tables DIM_DEPT and DIM_DEPT: There must be at least one physical join link between the underlying physical tables".
Any suggestions are welcome!
Thanks!

Hello Robert,
Your suggestions were known to me but I still wanted to combine the two physical dimension tables in one logical dimension. So I've played around a bit more and found the solution: In my original setup I had two seperate logical table sources (one for each physical dimension table). The solution was to combine the two logical table sources in one logical table source. I achieved that by logical joining the DIM_DEPT table to the FACT_SALES table and subsequently to the DIM_ORG within the 1 LTS and using inner joins.
Then I created the logical table key (a combination of org_detail_code & dept_detail_code). After that I could create the hierarchy with no problem.
Edited by: The_Dutchman on Nov 4, 2011 9:43 PM

Orgchart 3.0 doesn't show position hierarchy/detail due to (error) message?

Hi all,
at the moment we're implementing orgchart 3.0 (Product Version:7.0 Build Version:0700038500)
When using the wizard for setting the position view and details under organizational unit it provides the following
message/warning on the "profile"step as shown in the below link.
http://dc459.4shared.com/img/EW1Zf8-Y/s7/0.7417648190801285/screencap.PNG
This results in missing details for positions when publishing the build.
All the transports (ABAP and add on package have been imported and all included tables, views fm's are available.
Included an error log which is related to this issue?
697. 29 nov 2011 15:45:20 ERROR com.nakisa.Logger - com.nakisa.integration.sap.BuildingBlocks : while trying to invoke the method org.w3c.dom.Node.getNodeType() of an object loaded from local variable 'node'
698. 29 nov 2011 15:45:20 ERROR com.nakisa.Logger - java.lang.NullPointerException: while trying to invoke the method org.w3c.dom.Node.getNodeType() of an object loaded from local variable 'node'
699. 29 nov 2011 15:45:20 ERROR com.nakisa.Logger - Nakisa.SAP.SAPProcessor.BAPI_Hroci : while trying to invoke the method com.nakisa.framework.data.DataTable.select(java.lang.String) of an object loaded from local variable '<6>'
700. 29 nov 2011 15:45:20 ERROR com.nakisa.Logger - java.lang.NullPointerException: while trying to invoke the method com.nakisa.framework.data.DataTable.select(java.lang.String) of an object loaded from local variable '<6>'
The orgchart can be accessed and a structure is show on O level
but when trying to get in depth on position hierarchy we dont see any details or structure.
Any idea what might be the problem/issue and how to solve this?
Thanks in advance
Carlos

Luke,
thanks for your helpful and quick response.
Still have some additional questions/queries:-) as this is the first time we
try to implement orgchart.
So if I'm correct we need to undeploy the current SMP build of Nakisa 3.0
and deploy the latest build with SP2?
Or can we just deploy the latest build on our NWCE without any issues?
Regarding the 3.0 SP2 is this included in the latest build or do we need to download thisseperate from the SMP?
Can we resuse the current orgchart config builds in the latest build or is it advisable to configure
orgchart with a clean build?
Thanks in advance
Regards,
Carlos
Hi Carlos,
You are using the SMP build which contains quite a few bugs. I highly recommend that you contact SAP Support for the latest version and I strongly recommend that you implement 3.0 SP2 (the build you have deployed is 3.0 without any SPs). SAP Support will supply the latest version of the build upon request.
Best regards,
Luke

Creating a hierarchy based on a remote database link

I am trying to create a hierarchy based on a synonym for a remote database table. The hierarchy wizard works correctly, and the table columns do appear as choices in the drop boxes. However, when I try to run the application, I get the error "No data found. This data does not exist or you do not have privileges to view it". Does anyone know how to resolve this error? Or how to work around this?
I can successfully create and query a form based on the remote table. And, I am able to create a hierarchy from other tables (which do not use a database link) without a problem.
Thanks for your help!

This is the query which I am using to build a report
SELECT
rollup_timestamp "Date",
max(decode(target_guid,'199F0B201A3D71A63040BADFAA4F9E90',average,0)) host1,
max(decode(target_guid,'3FB1329F59339C07E11304B69DC4E594',average,0)) host2
FROM "sysman.MGMT$METRIC_DAILY"
WHERE
(target_guid='199F0B201A3D71A63040BADFAA4F9E90'
or
target_guid='3FB1329F59339C07E11304B69DC4E594')
AND
metric_name='Load'
AND
metric_column='memUsedPct'
AND
rollup_timestamp >= to_date('01-10-2009','dd-mm-yyyy') and rollup_timestamp <= sysdate
GROUP BY rollup_timestamp
ORDER BY "Date"
And for your previous question I couldn't even create a page.
Regards
Balaji
Edited by: user7290747 on 6/01/2010 16:17

Position Hierarchy Based on secondary assignments.

Similar Messages

Maybe you are looking for