A002 Relationships in EHP 5

The company I work for is going through an upgrade soon to ECC 6 EHP 5.  We've recently been told that A002 relationships will no longer be available in EHP 5.  Is this correct? Please advise. Thanks!

Who told you this? A002 will still will be used/supported. Could you imagine all those SAP customers having to change existing configurations if it was no longer used.
Cheers,
Brad
Edited by: Brad Krahe on Jun 29, 2011 5:04 AM

Similar Messages

  • Populate Error Message while submitting Travel Request if Supervisor(A002) relationship is not maintained for employee

    Hi Team,
    We have a requirement to "Populate Error Message(Supervisor not Maintained) while submitting Travel Request if Supervisor(A002) relationship is not maintained for employee in ESS.
    We are using standard WDA application - FITV_REQUEST and standard travel request workfow - WS20000050.
    Please suggest how to do this.
    Thanks,
    Ravi

    Hi Rajesh,
    Thanks for the reply...
    We created enhancement for FM HRTRV_IF_GET_CUSTOMIZING and written code in that.
    So by this if Logged in Employee is not assgned with Line Manager , it will throw error while accessing "Create Travel Request application".
    Thanks,
    Ravi.

  • SAP TDMS - Could not copy A002 Relationships to the target system

    Hi,
      I had used HCM package for PD & PA from TDMS to transfer the Organizational Management data for couple of records. Everything went fine except that the A002 relationship records were not copied to the target system.
      I had verified the target ranges that were defined and it has the Object Type "S" included in it.
      But still the A002 relationship records were not copied.
      Can anyone help me out with a solution on how to transfer the A002 Relationship records to the target system?.
    I had defined the Object Types CP, P, A, AG, BP, C, EK, ET, G4, G7, GE, NA, O, Q, RY, S, T, UG and US. Is there anything wrong with my target areas definition?.
    Thanks and Regards,
    Anil.

    Hi,
    have your checked if there is a lock for that relationship in table T77Tr in target system?
    Regards,
    Ana

  • 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 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

  • Rule 168 to work with org structure and not relationships

    Hi,
    I would like to use rule 168 to work with the organizartional structure and not the relationships maintained in PO10 organizational unit.
    this is because i want the agent to be the person with the red hat and not the a002 relationship maintained in organizational unit. i tried using rule 157 but it does the same thing and determines agent based on relationships maintained in org unit.
    basically i dont want the agent to be any of the line mangers which may have been set up, i want it to be the red hat of the org structure
    does anyone know how i can do this, or will i need to delete the relationships between staffing?
    Thanks
    Forhad

    Here is a code example to read from the tables in base to the personnel number emulating the SWE_GET_MANAGER function, I hope this helps. Regards.
    Z GET MANAGER *******************
    ***Gets the position for the creator of the requisition
      clear V_OBJID.
      select single objid into V_OBJID from HRP1001
       where otype  = 'S'        and
              plvar  = '01'       and
              rsign  = 'A'        and
              relat  = '008'      and
              begda  <= sy-datum  and
              endda  >= sy-datum  and
              infty  = '1001'     and
              sclas  = 'US'       and
              sobid  = pt_cont-VALUE+2.
      if sy-subrc = 0.
       valid if the user has personnel number don't proceed to look for the chief
         clear V_OBJID2.
        select single objid into V_OBJID2 from HRP1001
         where otype  = 'S'        and
               objid  = V_OBJID    and
               plvar  = '01'       and
               rsign  = 'A'        and
               relat  = '008'      and
               begda  <= sy-datum  and
               endda  >= sy-datum  and
               infty  = '1001'     and
               sclas  = 'P'.
        if sy-subrc <> 0.
       if the user exist in the correspondant date gets the chief position
          clear V_POS_SOBID_CH.
          select single sobid into V_POS_SOBID_CH from HRP1001
           where otype  = 'S'        and
                 objid  = V_OBJID    and
                 plvar  = '01'       and
                 rsign  = 'A'        and
                 relat  = '002'      and
                 begda  <= sy-datum  and
                 endda  >= sy-datum  and
                 infty  = '1001'     and
                 sclas  = 'S'.
          if sy-subrc = 0.
          if the relationship with a chief position exist gets the chief user id
            clear V_US_SOBID_CH.
            select single sobid into V_US_SOBID_CH from HRP1001
             where otype  = 'S'            and
                   objid  = V_POS_SOBID_CH and
                   plvar  = '01'           and
                   rsign  = 'A'            and
                   relat  = '008'          and
                   begda  <= sy-datum      and
                   endda  >= sy-datum      and
                   infty  = '1001'         and
                   sclas  = 'US'.
            IF sy-subrc = 0.
              clear pt_actor.
              refresh pt_actor.
              pt_actor-otype = 'US'.
              pt_actor-objid = V_US_SOBID_CH.
              append pt_actor.
            endif.
          endif.
        endif.
      endif.
    ***************End of Z GET MANAGER.*****************************

  • Position to position relationship

    Hi,
    I have created customized relation between two position by copying A002 relationship.
    Thru Transaction code PP01, i maintained relationship between two positions.
    But if i maintains relations for other employee then it deletes the first relationship.
    For ex. consider two employees (position)  X and (position) Y reporting to employee  (position) Z.
    I maintained X-Z relationship.
    But when i creates Y-Z relationship after saving it deletes X-Z relationship.
    Please guide to resolve this issue.
    Thanks,
    Abay

    Solved.

  • Help Needed in reporting structure OM

    hi experts
    I am a certified Fresher in SAP i am doing practices with IDES
    I created an org unit and its sub units and created positions also ..i want to connect the positions  of the parent node and subnode in reporting structure
      O   head unit
              S CEO
              S  GM
          I
          I  O Unit 1
                 S Manager Unit 1
          I
          I  O Unit 2
                 S  Manager Unit 2
    I want to connect the GM with Manager Unit1 and Manager Unit 2  in reporting structure
    Please tell me steps to do this

    If you want Manager unit1 and Manager Unit 2 to report to GM then go to PO13 Select the Manager Unit1 and create relationship infotype with A002 relationship in the related Object type choose S (Position) and in the object id choose GM.
    Similarly do it for the Manager Unit2

  • How to send Notification email to Outlook mail?

    Hi all,
    am new to workflow,
    is there any possiblity with sending notification emails using rule?
    in my requirement i have to send email notifications to concerned manager using A002 relationship in HR?
    Can anybody help me?
    Thanks in advance,

    Hi,
    You will have to do the following:
    1. Create a new container element (for eg. APPROVER) with Data type WFSYST-AGENT.
    2. Create a new background method(if required create a new Business object also) to your BO object to populate this container element.
    3. Use the following code in your method:
         DATA: G_SNAME TYPE SMNAM,
            G_USER TYPE SYSID,
            NEXT_PROCESSOR_TAB     TYPE PTREQ_UIA_APPROVER_TAB.
         PERFORM FIND_NEXT_PROCESSOR(RPTREQAPPRCHK)
         USING
         PERNR
         REQTYPE
         CHANGING
         NEXT_PROCESSOR_TAB
         G_SNAME
         G_USER.
         CONCATENATE 'US' G_USER INTO APPROVER.
    3. Add a new activity step to your workflow calling this method.
    4. Use your(current) send mail step with agent field having value 'APPROVER'.
    Hope this will work.
    Regards
    Gautam

  • How to extract an employee reporting hierarchy per org unit in spreadsheet

    Hi Guys,
    Can any one advise if there's a standard report I can use to see employee's  reporting hierachy in spreadsheetformat ?
    Report must have per org unit positions with their  related positions :'reports to' A002  relationship between two positions in a specific org unit and person's name/employee number occuping the positions.
    I tried creating joint table but battling to undestand how I can have the two related positions info in the infoset.
    Current standard report give me only positions with reports to relationship but haven't found report showing me positions with reports to relationship and their related position.

    Have you tried using logical database PCH? That gives flexibility to create this kind of report. Create an infoset in SQ02 and an Adhoc Query in SQ01 based on PCH Logical Database. You will need the relationship subtype 'A002' and related object type 'P' on selection screen.
    Edited by: Shafiq Rehman on Feb 6, 2008 4:23 PM

  • Leave request mail trigers to whom in dual reporting

    Hi All
    When an employee reports 2 managers from 2 different departments, if he applies leave that mail will trigers to whom.
    eg: a position has A002 relationship with one manager
                                 A088 (dotted line)relationship with one manager
    if he applies leave that mail trigers to A002 relationship manager
    or A088  relationship manager

    hmm
    not sure
    it depends upon the Percentage of the Position say if he is working in X department 75% and 50 % than the mail trigger to the manager where the percetage of Occupacy is more

  • 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

  • MSS Team Overview - Direct Report

    Dear All,
    We are on EP7 and using the web dynpro Team Calendar. The client have requested that in one of the view, it only display the direct employee for the manager (A002 relationship). Anybody knows how to configure the "evaluation path" and the "rule for target object to cater this request".
    Thanks in advance
    Regards,
    Bryan

    Hi Brian,
    In R/3 navigate to t.code SPRO -> Integration with other mySAP.com Components. -> Business Packages/ Functional Packages -> Manager Self- Service -> Object and Data Provider -> Object Provider -> Define Rules for Object Selection
    For direct reports - you can use the existing evalpath MSSDIREC and a rule already exist with the eval path MSS_TMV_RULE5.
    if you want to use a different eval path create a new rule and include that rule into the object selection.
    And in the iView properties need to mention the ruke you created.
    Hope this helps.
    Cheers-
    Pramod

  • MSS Team Calendar - Direct Report

    Dear All,
    We are on EP7 and using the web dynpro Team Calendar. The client have requested that in one of the view, it only display the direct employee for the manager (A002 relationship). Anybody knows how to configure the "evaluation path" and the "rule for target object to cater this request".
    Thanks in advance
    Regards,
    Bryan

    Hi,
    Please find attached configuration.
    With thsese changes we are geting error under MSS --> Team Calendar
    "No Team setup for the user in the selection period. Contact Administrator"
    Please guide.
    Regards,
    Rashmi V.

Maybe you are looking for