Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Depth of Evaluation for Standard Evaluation Paths (Bottom Up Approach)

Former Member
0 Kudos

Hi All,

We are facing a unique issue when using OOSP and defining evaluation path. for e.g. we used the standard SBESX (Staff assignments along Organizational structure). We also defined the following fields to test the Org structure results for a user's structural authorization on what he/she can see (e.g. Org unit(O), Positions(S), Users(P))

1. Object Type = O

2. Evalutaion Path = SBESX

3. Status vector = 12345

4. Depth (D) = 5 (which defaults to 1 automatically if we set the sign field to -(negative) for Bottom-up approach (displaying org structure bottom to up)

5. Function Module = RH_GET_ORG_ASSIGNMENT

6. Key Date = D

The issue we have is for the above settings on OOSP Depth field defaults to 1 everytime we use the Bottom up approach (i.e setting the Sign field to - (negative)). Has anyone encountered the above problem with the depth field? Let us know if you had any fix or you had to escalate this to SAP?

Best regards,

-Murali

3 REPLIES 3

former_member74904
Contributor
0 Kudos

hi murali,

I cannot give you an answer on why exactly the depth filed is defaulting to 1 when using the negative in the sign fields (T77PR-SSIGN). but can you perhaps explain what you're trying to accomplish with your structural profile. in that case, maybe I/we can figure out a way to circumvent the use of the sign field...

Edited by: Dimitri van Heumen on Mar 19, 2008 2:24 PM

(typing errors)

0 Kudos

>

> hi murali,

>

> I cannot give you an answer on why exactly the depth filed is defaulting to 1 when using the negative in the sign fields (T77PR-SSIGN). but can you perhaps explain what you're trying to accomplish with your structural profile. in that case, maybe I/we can figure out a way to circumvent the use of the sign field...

>

> Edited by: Dimitri van Heumen on Mar 19, 2008 2:24 PM

> (typing errors)

Thanks for your reply Dimitri.

Here is what we are trying to acheive with the Org structure below:

O - 00001004

S - 00000253

O - 00001005 O - 00001006

S – 00000251 hradmin1 S – 00000256 essuser2 (120)

S - 00000252

O - 00001007 O - 00001008 O - 00001009 O - 00001010

S - 00000257 S - 00000259 S - 00000260(121) S - 00000254 (122)

S – 00000258 essuser1 S – 0000255 hradmin2(114)

Position # 00000255 (far right down below in the above Org structure) is the HR Specialist for (Org #00001006 and Org #00001009). Employee # 114 (far right bottom) has been hired into this position 255. They should be able to see Employees 120, 121, 122 and themselves(114).

We have created a structural profile for the user hradmin2(114) and attached him to a role which has ess/mss functionality. We are trying to use the evaluation path SBESX to test what org units, postions and users this user hradmin2(114) can see which should meet the requirement stated above that he should see 120,121,122 and 114 themselves.

So from the Org structure above it is a bottom up scenerio where hradmin2 must see org units 00001010, 00001009 and 00001006 and whenever we set the sign field to -ve (bottom up approach of displaying org structure) and depth of lets say 4 it automatically defaluts to 1 and when we check hradmin2 authorization profile in oosb we only see org unit 00001010 being displayed and not the org units above it for this bottom up approach.

Are you aware of any methods to acheive this for the org structure above?

Thanks

-Murali

Edited by: Murali Sripadam on Mar 19, 2008 1:47 PM

0 Kudos

Hi,

Something that could help is the creation of a custom relationship - similar to an 012 relationship, you could remove the entries that are not required. If you are not sure how to do this then you could chat to the HR consultants about this.

Then use this relationship to allocate the relevant org units to the HR Specialist position. Then you could use a pretty simple structural auth for O-S-P.

Regards