MSS - A012 Relationship or A002??

Hi
I think MSS can be only accessible to A012 (Person who manages an Org. Unit). If we want MSS to be accessibel to A002 (Reports to ) wat do i need to do??
if we want some MSS services to be shown to ESS users, how can we do it??
Please help

This fairly simple, You can create your evaluation paths and assign it to the profile being used.
check table t778a
3/ Report RHSTRU00
You can use report report RHSTRU00, to check your own path
4/ Table V_T77AW
You can mantain the evaluation paths.
You can use the FM HRWPC_GET_PATHROOTS
go to Simg_sport > OADP (Object and Data Provider () for the customisation of the evaluation paths
refer more on http://help.sap.com/erp2005_ehp_03/helpdata/EN/2e/5a5d45d9f24fbdb06be2ff53651c3e/frameset.htm

Similar Messages

Org Unit and Cost Center not displaying in 0001 with A012 relationship

Hi Guru's,
Kindly help me in this regard ,
Whenever i hire a person to a position which has an A012 relationship (Chief Position) then Org Units and Cost centres are not getting displayed in IT0001 .
But when i hire a person in the same org unit with A003 relationship ; both Org units and Costcentres are getting displayed
I have used an LSMW for uploading relationships and objects and i have also run integration reports for the same but still i am not able to display org unit and cost centre in it0001 when i hire a person with A012 relationship .
Kindly Help

both great advice, also, check this link:
http://help.sap.com/saphelp_45b/helpdata/en/14/d22fe48435d111950d0060b03c6b76/content.htm
within this information there are various reports to run, which help recon OM and PA integration. it will help you find your data problem and then fix the data for you if you follow step by step.
best regards,
michael

Time Constraint for Position A012 Relationship

Our organization's structure is such that one position may manage more than one organizational unit. The time contstraint for A012 relationship for positions is currently set to 2, which appears to be restricting me from establishing a position as chief for more than one subordinate org units. In our test environment I changed the constraint to 3 and now am able to have a position as chief of multiple org units. Have I created any potential problems (i.e. with workflow) by changing the A012 time contraint?
Thanks for any advice,
- Lora

Not that I am aware of. In the situation of having the time constraint is the when certain program uses evaluation path, it doesn't know which one of the path to pick since there are more than one path presented.
In the case of workflow, usually it will go to all of them. The first one that open the task owns the task.
But in the case of A012, it should be okay. There are situation where the chief relationship will be towards more than one organizational unit. Where his position belongs to is a different story. As where his position belongs to for the org unit defines who is his/her reviewer for performance and compensation. But he could have as many A012/B012 to manages all those org units as he wishes.

MSS Reporting relationship

Hi Experts
I would like to know about MSS functionality.
I am currently configuring MSS at one of the client site and wherein i could see the standard functionality of Manager who has reporting relationship A012 (Manages) has the authorization for viewing and approving his sub-ordinates requests. If he has only reporting relationship A002 relationship he will not be able to view and approve any of the sub-ordinate request.
e.g. If there are 3 employees are working the same dept. as A, B, C.
C is reporting to B and B is reporting to A.
And A is having relationship A012 (manages), will be able to see and approve the sub-ordinate request but B will not be able to view or approve the sub-ordinate request.
Could you please give your comments on the same.
Regards,
Anand

Hi Suresh
Problem is narrted below with detail example
In one of the department i.e. HR, there are 3 (A,B,C)employees are working.
Where C is reporting to B (A002 reporting relationship)
Where B is reporting to A (A002 reporting relationship)
A is a head of the department and he forms the relationship with organizational unit A012 (Manages)
Suppose C raises the leave request for approval from ESS which should go to B since C is reporting to B.
If B logs into the system, he should be able to approve leave request of C in MSS.
Similarly in case of B and A. In my current system A is able to view the B request and approve the same. Actual problem lies between B and C
I would like to know that whether B will be able to view C as a staff and approve all his related request since he is not the head of the department as C and B only forms the reporting relationship A002.
As per the MSS document, i have read the pre-requisite for viewing the sub-ordinate and approve their request, immediate superior should be head of the department i.e. relationship A012.
Could you please give your expert comments on the same.
Regards,
Anand

A012 relationship

REquire our help gurus on scenario:
There are three Org Units- A the Main Department and B, C Child Department. We have maintained Chief position A012 to all Units 'A', 'B' and 'C'. Org Units B and C as said earlier reports to (002) to A. Is it possible for Chief of A to have full visibility to the Child units B and C with respect to
1) MSS: Team View . The Chief of A should be able to view persons from B and C also as his team and able to do all other MSS operations
2) B and C chief should also be able to do the same for people under their control.
Thanks in Advance gurus.

Hi
I am not sure what more input you are looking for. There Object and Data provider in MSS delivers scenarios for this by standard. Manager for A can in MSS choose:
1. Directly reporting employees -> Would give employees in A
2. All employees -> Would give employees in A, B, C.
3. Choose from org.unit -> Would give only employees in A, B or C depending on org.unit chosen
I would suggest you deploy standard MSS and have a look at it. Also open the standard OADP and look at it. It is a little intimidating at first. Start from the bottom and work your way upwards - that makes the most sence to me at least.
You can also set up your own object rules. They are determined by evaluation paths.
Hope this helps you.
Kirsten

MSS General Information Employee Search A002 relationship

Hi All,
We are having A002 based reporting structure ( no A012 relationship maintained).
In General information there is a Iview for employee search.
When we execute this search ( say using pernr), search does not return any values.
Now if I maintain A012 relationship between Organization unit and the managerial position then this search works fine.
My question is:
1. Is issue related to structural authorization?
2. Do i need to maintain some entry in T77S0 table?
3. Or do I need to implement Z search class in Object and Data provider similar to CL_HRWPC_SEARCH_VIA_SELID?
Any help would be highly appreciated.
Thanks and warm regards,
Aditya

No the issue here is evaluaiton path what shall be used cause as you see
This iView displays the employees in the manageru2019s area of responsibility, that is, employees who report either directly or indirectly to the manager. The display is based on the SAP application component Organizational Management.
so check the properties of the iview ie
Group of organizational structure views
sap.xss.tmv.orgviewgroup
Administrator
Optional
Organizational structure view group, for example MSS_TMV_EE, stored in Customizing.
Individual organizational structure view
sap.xss.tmv.orgview
Administrator
Optional
Organizational structure view, for example MSS_TMV_EE_DIR, stored in Customizing
ie check Function module HRWPC_GET_DIREPS_OF_LEVEL_1
(Rule MSS_TMV_RULE1 uses evaluation path SAP_MANG and rule MSS_TMV_RULE5
uses evaluation path MSSDIREC.)
http://help.sap.com/erp2005_ehp_04/helpdata/EN/2e/5a5d45d9f24fbdb06be2ff53651c3e/frameset.htm
You can use your own evaluation path to accomodate your a012 relationship ie using OADP
modify sap_mang to return your relationship
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=190743879
HRWPC_OADP_GET_SEARCH_ROOTS calls HRWPC_GET_PATHROOTS

A002 Vs. B002 relationship

Background:
When creating a new position and attempting to create an A002 relationship with certain supervisor positions, an error is generated 5A 028 or "Relationship structure A002 S ########## not allowed."
Additionally, if a priority is provided it will create the relationship.
Alternatively, if we go to the supervisor position and create a B002 relationship to the position being created it works fine as well and no priority is needed.
I'm looking for understanding as to why the priority is needed when creating the supervisory relationship using A002 on the created position as well as understanding as to why the same relationship, albeit B002 coming from the other direction is created without the need for a stated priority.

Paul,
Thanks for your reply.
The relationship seems to be maintained correctly in T778V:
002   Reports (line) to         Is line supervisor of
Also looking at it from the Allowed Relationships:
S     Position     A     002     Reports (line) to     S
S     Position     B     002     Is line supervisor of     S
The time constraints look correct:
S     1001     Relationships     A002     Reports (line) to     2
S     1001     Relationships     B002     Is line supervisor of     3
For 95% of these relationships we don't get the error. For a select few of our supervisor positions this error is generated.
Any other thoughts?

MSS Team Calendar and ESS in MSS

Hi OADP and MSS experts,
My client organization is implementing ESS (Basic personal information and leave request services) and MSS (leave approvals and team calendar). Partly the organization has a line manager (A012) relationship who would approve the leave request in MSS (which is fine using SAP standard). Other than line manager relationship, they also have Absence Coordinators who approve the leave request where there are no line manager relationship.
I would like to get your views on the following-
1. Is it possible to use standard OM relationship 'S' A/B 290 is administrator of 'O' for Absence Coordinators and configure OADP to get the views in the MSS team calendar.
2. also the absence coordinators - can they submit leave request (ESS in MSS - related activity for Leave request) on behalf of employees based on the above relationship (A/B 290) .Please note that they will not have chief position assignment
If this can be achieved by OADP configuration I would appreciate any help with configuration documentation.
Looking forward to get your opinions and suggestions please.
Many thanks,
Terence
Edited by: TBOSCO on Aug 11, 2009 8:47 PM

Here is the paths
V_TWPC_ORGVWGRP > MSS_TMV_EE
Check the IMG step
Integration with Other mySAP.com Components -> Business Packages/Functional Packages -> Object and Data Provider -> Organizational Structure Views -> Group Organizational Structure views
MSS_TMV_EE is assigned to MSS_TMV_EE_ORG2 etc etc
And then
These organizational views are defined in IMG step u2026u201Ddefine Organizational Structure viewsu201D:
They have the following Object selections:
MSS_TMV_EE_ORG2
Organizational View             MSS_TMV_EE_ORG2 Employees from Organizational Structure
Object Selection               MSS_TMV_EE_ORG2 Employees in Org.Structure Up to Level 2
Group of Data Views            MSS_TMV_EE      Display
Then you have to check the IMG step u2026 Object and Data Provider -> Object Provider -> Define Object selections:
Object Selection     MSS_TMV_EE_ORG2 Employees in Org.Structure Up to Level 2
   Rule for Root Objects          MSS_TMV_RULE1   Managed Organizational Units
   Rules for Navigation Objects   MSS_TMV_RULE3   Organizational Structure Up to Level
   Rule for Target Objects        MSS_TMV_RULE4   Employees of an Organizational Unit
Then you can check the rules for object selection: IMG u2026Object provider -> define Rules for Object selection
Object Selection Rule          MSS_TMV_RULE1   Managed Organizational Units
Evaluation Path               SAP_MANG Org. units managed by persons or users >>> got from t77aw
Depth of Structure
Function Module
Other examples
MSS_LTV_RULE1: evaluation path SAP_MANG >>> This has to be customised accordingly using T77aw
MSS_LTV_RULE2: SBESX
MSS_LTV_RULE5: MSSDIREC
MSS_LEA_RULE1: SAP_MANG
MSS_LEA_RULE2: SBESX
You can use FM or above table T77aw.
Let me know if you have further queries.

Providing HR Admin/TIme Admin view like MSS

Hi,
I am trying to develop Time Admin/HR Admin/Delegated MSS view just Like MSS . So, these administrator can see the employees and approve time and request leave request and perform clock-in/out entries.
As you know MSS goes A012 relationship. I tried to use B290 relationshipvfor this one. but MSS Team calendar views are not showing the employees.
How cana achive through OADP. What kind Group Views I can use.
What exactly the steps I need to perform.
Is there any other group org structure views I need to use.
Thanks in advance.
Regards,
Mark
Edited by: Mark Komaragiri on Feb 10, 2012 6:02 PM

Now regarding Custom relationship, Yes adding in evaluation path should work in T77AW and then adding to the correct organization view in OADP customization as explained in WIKI or you can use FM.
check the wiki for the exact tables etc,
Let me know if you run into any issues.
Also regarding the EHp5 roles,
You can create a area group of EHp4 and then add that into EHp5 using LPD_cust
or use two different roles

Problem in Assigning Relationships (Org Mgmt)

Hi,
The system does not show (neither through PPIS or through PPOME) organizational structure when I create A003 (Belongs to) relationship between organizational units (Object Key 'O'). The same is shown when I change relationship to A002 (Reports to).
Moreover, system does not show (in PPOME & PPIS) positions that are assigned A003 relationship with object key 'O', but the same is shown when this relationship is changed to A002.
Now, a position is supposed to report to a super position & for which relationship has to be A002 (Reports to). But when this is assigned, the system does not show it throguh PPOME / PPIS.
What shall I do to fix the problem? Moreover, can anyone tell me which tables store the OM Objects (i.e. OUs, Positions, Work Centers, Jobs, Persons & Relationships)
Rgds,
Tapan Shah

Hi,
The display characteristics of PPOME is determined by evaluation path SBESX.
Please check table T778A.
You may change the relationships displayed using this table.
However, this display behavior is determined due to some logic and think twice before changing the standard system.
As of your requirement, 002 relationship can be used btw O objects instead of 003, why do you want the second?
And the tables for OM objects are basically HRP1000 (object names, etc), HRP1001 (relationships)
Regards,
Dilek

Relationship 012

Hello Experts,
The organization I am with records a priority level on the position and org for the 012 relationship.
Question: When the priority level (Field Name PRIOX) is changed for the A012 relationship on the position is the B012 relationship on the Org automatically changed and vis versa.
Thanks for your help.
Regards,
Jeanette

Hi,
Yes, like other attributes of any relationship record, priority will be updated for the B012 record as well and vice versa. Further, priority fieldu2019s main purpose is to control how objects show up in a hierarchy so it will make no sense if only one way relationship was updated and not the other.
Hope this helps.
Donnie

Approve Working Time Error

Hi
We are on EP7 with ECC6.0 as backend.
We are trying to use the Approve Working Time iview in MSS but it gives the following error:
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE
We have maintained the following customizing in backend(
1.Define Approval view: SAP_LINE ( SAP Approval by Line Manager)
2.Define Field Selection for Individual Approval view: SLIN1 and with it Field customizing Field label
Personnel Number , Attendance or Absence Type,Text for Attendance or Absence Type, WorkBreakdown Structure Element, Receiver Order etc.
3. Define Field Selection for Detail View: Attendance, Counter etc
4.Define Profiles and Assign to Views: SAP_Line: Initial View=SAP_Line.
5. Create Rule Groups: SAP Standard( 01)
6 Adjust Webmo feature: Time Sheet Application..assigned rule group: SAP Standard(01)
The Approver is a Manager with A012 relationship with a particular org unit.
Kindly suggest where may lie the problem.....we have a requirement of Collective Approval of Working Times of his subordinates by the Manager.
I would like to add here that we are able to approve Working time requests individually through UWL...but we need to use the Approve Working Time Iview.

Hi
We are using the standard taskTS20000460. But we want to use the Approve Working Time service iview.
When we were using the evaluation path for approving the working time data through A012( Chief) in MSS, we were able to see all the working times recorded by the subordinates of the said Chief( Manager) in the service Approve Working Time itself, we did not necessarily have go to UWL and approve from there....Now after we have made the required changes in the evaluation path and made A002 as the approver, the same iview Approve Working Time has a message that "No date exists that needs to be approved'.
At the same time we are able to view and approve the working time data from UWL of A002.
Is there a change that needs to be done in the service to get it working ? or it this because of some other reason.
Please advise.

Using Rule 168, SWX_GET_MANAGER and Chief Position

We have enabled standard SAP Travel Workflow WS20000040 - Approve Trip. We are not currently using OM relationships A002 (Reports Line to) or B002 (Is Line Supervisor of). We currently identify the Line Manager of the employee using the Chief Position designation A 012 and would like to use this for Trip approvals in lieu of building all of these additional relationships.
Rule 168 is bound to the workflow. According to the documentation associated with the rule, it seems that the rule should work with either the A002 or A012 relationship. However, we only seem to be getting a superior identified when relationship A002/B002 exists.
Are there additional configuration or parameter settings that we might need to consider to make the manager (agent) determined properly exclusively with the Chief Position assignment?
Thanks for any guidance you can provide.
Regards,
Edited by: Bruce Hull on Jul 24, 2008 5:37 PM
Edited by: Bruce Hull on Jul 24, 2008 5:37 PM
Edited by: Bruce Hull on Jul 24, 2008 7:29 PM

What I found through trial and error is that rule 168 does indeed evaluate the A012 relationship by default with no change in the standard evaluation path. In our testing system, the "Chief" postion was not properly assigned. Once this was resolved, the workflow works properly.
As a side note, I also learned that you must have the parameter WFLOW VAPOS set for the rule to properly look up the organizational structure when a position (and chief) are vacant.

Organisational structure Maintaince

Hi Gurus,
Our Oraganisational structure is a quite messup. The Chief positions and reporting structure is in a mess up state because of which workflow doesnot work well. Suggest me relevant steps which i have to follow to bring it in the right shape.
Does it require some data upload?
Regards,
Shr

Hi
You can do following to correct your Org. Structure
1. First, run a standard OM Report to get A002 Relationships (Reports to) b/w positions and A012 Relationship (Chief) b/w Position and Person OR get this information from HRP1001.
2. Delimit the incorrect relationship entries by using RHGRENZ* Report.
3. Create an LSMW for Infotype 1001 updations. Prepare a file with correct A002 and A012 Relationships and upload the same by using LSMW.
Hope this helps
Best Regards
Reddy

Permitting a Manager of one org unit access to another org unit

Hi,
I have a problem with the use of relationships between the position and org units.
If a manager has an A012 relationship to org unit 123, but should be able to view & approve leave for employees from another org unit 456.
Is it possible to have a different relationship to org unit 456? To provide access to employees who are not part of the managers direct reporting structure.
Thanks in advance
Sujeet

1. Create a separate relationship for the special access.
2. You might need to add the new relationship to evaluation path
3. If you are using MSS and need to display this, that evaluation path needs to be updated
4. Structural authorization profile needs to be updated
5. Role needs to be updated. Context senstive authorization needs to be activated and PA authorization + structure abc, PA authorization + structure xyz needs to be added to the role
Hope it help.

MSS - A012 Relationship or A002??

Similar Messages

Maybe you are looking for