SAP TALENT MANAGEMENT V/S NAKIS

Hello,
I am trying to prepare a document on SAP TLT MGT v/s Nakisa...
I am aware of entire talent mgt modules in sap but trying to figureout things in Nakika.
can anybody help with suitable links or docs available with you.
cheers
md
Moderator message: not directly related to ABAP development, please don't ask for documents, search for available information.
Edited by: Thomas Zloch on Apr 6, 2011 1:10 PM

Hi Mohammad,
I moved your thread to the correct forum. I am assuming that you are referring to STVN SuccessionPlanning.
Basically, Nakisa is not versus SAP Talent Management but is part of SAP Talent Management. STVN SuccessionPlanning is SAP's solution for succession planning and is part of their portal-based application strategy. Without this you will have to do succession planning activities in the backend and will also not have functionalities such as 9-box grid and profile match.
Best regards,
Luke

Similar Messages

New SDN blog post: Setting up TREX for SAP EhP4/5 Talent Management

Hi all,
I have written a new SDN Blog on Setting up NetWeaver Embedded Search (TREX) for SAP EhP4 Talent Management:
http://scn.sap.com/community/erp/hcm/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management
Enjoy!
Luke

Hi Luke
I'm looking for a copy of the SDN Blog, but having trouble trying to find it.
All pages lead to "Page not Found".
Is it possible for you to post this again or email me a copy of the Article ?
Thanks in Advance
Min

Issue in EHP5 Talent Management (Team Goals) Cascade goals functionality

Hi Friends,
Issue in EHP5 Talent Management (Team Goals) Cascade goals functionality.
Under Team Object While try to cascade goals, it pop-Up Warning Msg u201CChoose Save to save the goal in the employee document. The goal can no longer be deleted, only set to obsoleteu201D.
If we click Ok to proceed further, I am getting error stating u201CYou have made no selection" and " No appraisal template defined ".
Same functionality is working fine in u201CPerformance Management (Predefined)u201D
With Regards
Seranjeeve Kumar

Please set the parameter PROCESS "PMP" in the iview configuration.
ie
ROLE_ID=PA&PROCESS=PMP in application parameters
content provided by SAP ->
specialist ->
Talent management Specialist ->
iViews ->
COmpany goals etc
and you can confirm using this
CL_HAP_CASCADE_GOALS > meth0d GET_VALID_APPRAISAL_TEMPLATES
The parameter mentioned in the note 1457057, the one that you enter in
transaction SE80 is the default value. However, if you call application
with parameter PROCESS=PMP then the PMP process for cascading goals will
be used.
check note 1523527

Error while creating the Connector in PRD - Trex in Talent Management

Dear Luke,
Greetings.
We are in ECC 6, Eph4.
While setting up the TREX in Production we are encountring an error as below. But we dont have any issue in Development and Quality system. TREX related to Talent Management is working fine.
Would be great if you share your inputs.
Kind regards
Sathya

Dear Luke,
Thank you for response. We have posted an OSS message. SAP is suspecting this to a support pack level kind of issue. So we are waiting for a solution from SAP.
Appreciate your support.
Kind regards
Sathya

Is TREX mandatory for Talent Management?

Dear Experts,
Is TREX a mandatory component for Talent Management? It's because I am having issue when I click "Search" in Talent Management Specialist Launchpad, telling me "Error occurred during the search; contact your system administrator".
And it seems to me that TREX supports only LINUX and MaxDB, which is totally out of our company's landscape.
Thanks,
Steven

Hi Steven,
TREX is the search engine itself. That means Talent management is using enterprise search and enterprise search uses TREX to perform searches and store data.
Enterprise Search is part of SAP Netweaver ABAP ( also called embedded search ). Enterprise search is responsible to index data from HR to TREX and is responsible to redirect search requests from Talent management to TREX and put back the results back to the UI. It also provides tools to maintain and administer the data models.
So Enterprise Search is available on your Netweaver ABAP system. But ES uses TREX. That means if you want to get ES up and running you need TREX. (normaly installed on a different box and connexted by RFC to the Netweaver System)
hope that helps.
Martin Hastik

TREX - Search Talent Management

Hi All,
I know that there are many threads on the TREX and have looked at all of them and tried some of the things but i still get the error search not available.
We have created all search connector in the admin cockpit and have indexed all of them with no errors. All 32 of them are active. I then ran report ESH_TEST_SEARCH to test the searches. All of the objects templates return results except the following:
HRTMC_AES_DOCUMENTS
HRTMC_AES_ELEMENTS
HRTMC_AES_TEMPLATES
HRTMC_AUTHORITY_VIEW
HRTMC_CENTRALPERSON
HRTMC_FUNC_AREA
HRTMC_JOB
HRTMC_JOB_FAMILY
HRTMC_ORG_UNIT
HRTMC_POSITION
HRTMC_QUALIFICATION
HRTMC_REL_CP_JF_744
HRTMC_REL_CP_Q_032
HRTMC_TALENT_GROUP
For most of these templates I get the following error:
Search Engine Error 29 for DHR310HRTMC_FUNC_AREA : attribute not defined for physical index;index esh:dhr310dhr310hrtmc_func_area~functional_areayy has no attribute 'objid'.
For the HRTMC_AUTHORITY_VIEW i get no results, it comes back no values and has a yellow traffic light in the Log viewer. In the Job Log in the Admin Cockpit i see the following
31.05.2011 21:54:23 Object connector DHR310HRTMC_AUTHORITY_VIEW: New status: Indexing
31.05.2011 21:54:23 The implementing class does not support the iterator by time interface
31.05.2011 21:54:23 Implementation did not provide any data -> exit indexing
31.05.2011 21:54:23 Object connector DHR310HRTMC_AUTHORITY_VIEW: New status: Active
31.05.2011 21:54:23 Job finished
I also activated BADI HRTMC_AUTHORITY_VIEW_DELTA in the IMG and ran report RPTMC_CREATE_CHANGEPOINT_AUTH. I then scheduled ESH_IX_PROCESS_CHANGE_POINTERS for the HRTMC_AUTHORITY_VIEW, hoping the I would be returned with some results.howver
I do have a TMS linked to several org units via relation 741 and this is returned in the test search HRTMC_REL_S_O_RESP. In addition if I go to a Talent Review Meeting in the portal and click on 'ADD' to select an org unit, the managers of the Org Units that I am related to appear on the list. However as soon as I select any of them, they are added to the participant list but non of the nominated talents appear, i get the following message:
'No nominations are displayed since the search is not available'
for all other searches i get the error 'Search is not available' or 'No Relevant Records Were Found for This Search'
I Also checked SLG1 logs after attempting the searches and got the following errors:
2007 for DHR310HRTMC_CENTRALPERSON : NameServer error: no servers found; IndexId:esh:dhr310dhr310hrtmc_centralperson~~sap_talent
Exception occurred in program CL_ESH_IF_SEARCH_RESPONSE=====CP, include CL_ESH_IF_SEARCH_RESPONSE=====CM006, row 4
An exception has occurred
29 for DHR310HRTMC_CENTRALPERSON : attribute not defined for physical index;index esh:dhr310dhr310hrtmc_centralperson~personal_datayy has no attribute 'objid'
Exception occurred in program CL_ESH_IF_SEARCH_RESPONSE=====CP, include CL_ESH_IF_SEARCH_RESPONSE=====CM006, row 4
I also tried creating my own serch request using one of the search templates returning results. In this case i used the HRTMC_REL_CP_TB_743 templates with talent group ID as search field and assigned it to one of the search configurations. I then however got the following error.
The following error text was processed in the system DHR : The ASSERT condition was violated. The error occurred on the application server sivrs106_DHR_00 and in the work process 0 . The termination type was: RABAX_STATE The ABAP call stack was:
Method: GET_AUTHORIZATION_QUERY of program CL_ESH_IF_SEARCH_REQUEST======CP
Method: SEARCH_ONE_CONNECTOR of program CL_ESH_IF_SEARCH_REQUEST======CP
Method: SEARCH of program CL_ESH_IF_SEARCH_REQUEST======CP
Method: CONSTRUCTOR of program CL_HRTMC_SEARCH_REQUEST=======CP
Method: GET_INSTANCE of program CL_HRTMC_SEARCH_REQUEST=======CP
Method: TRIGGER_SIMPLE_SEARCH of program CL_HRTMC_AC_SEARCH============CP
Method: ONACTIONSTART_SEARCH of program /1BCWDY/JUNQ9FJYULV16JASJHWU==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/JUNQ9FJYULV16JASJHWU==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
Method: IF_WDR_ACTION~FIRE of program CL_WDR_ACTION=================
Anyone have any ideas on how i can resolve this.
Apologies for posting such a long thread, just trying to provide full picture.
Regards
Imraan

Hi Imraan,
You should be congratulated on a thorough post! What version and revision of TREX are you using? You should use TREX 7.1 revision 16 or higher. You should also review the PA-TM SAP notes for TREX. I would recommend reviewing some of the following (some you might need to come back to later):
u2022     1376055 - ESH_ADM_INDEX_ALL_SC: Exception in step 2: Create
u2022     1384953 - ESH: Error message 'A connection already exists' in cockpit
u2022     1437946 - TMC search: Frequently asked questions
u2022     1441190 - Error in model assignments to logical system
u2022     1457940 - Transporting software components: Error in after-import
u2022     1476894 - Transporting software components: Paths are lost
u2022     1483890 - Importing software components directly to target client
u2022     1492752 - Program to create a join index retroactively
u2022     1502296 - Too few ESH_OM_LOGSYSA entries after creating a connector
u2022     1538688 - Indexing Log: Warning "Object 'nw_esh_tst_auto' not ..."
u2022     1516237 - TMC search: Long runtime for indexing of HRTMC_REL_S_Q_031
u2022     1518396 - Indexes are not filled after TREX conversion
u2022     1520538 - TMC search: Performance for extraction of documents
u2022     1523648 - The search does not find any hits
u2022     1526710 - TMC search: Error during position switch by TMS
u2022     1529878 - Performance of authorization indexing
u2022     1534172 - TREX 7.10: Revision 42
u2022     1536663 - TMC search: Long runtime during indexing HRTMC_REL_SC_JF_FN
u2022     1536656 - Missing search attr for person search in Succession Planning
u2022     1540869 - TMC search authorization indexing with initial user ID
u2022     1541984 - Search connectors are not found
u2022     1542741 - Deleting connections
u2022     1550964 - TMC srch: Qualification srch criteria for CP-Q relationship
u2022     1551029 - TMC: Incorrect authorization check for PA infotypes
u2022     1554061 - TMC search: Error in search fields for job evaluation
u2022     1555950 - Indexing of HRTMC_AUTHORITY_VIEW: Data packages are too big
u2022     1558355 - TMC search: Empls. that have left company in search result
u2022     1560966 - TMC search: Error message when copying search configurations
u2022     1561070 - Termination when saving after deleting system assignments
u2022     1562742 - TMS / Search: Indexing fails with HRTMC_REL_S_MANAGER
u2022     1568563 - TMC search: Error when setting up authorization index
u2022     1567065 - TMC search: Simplifying the authorization indexing
u2022     1575454 - TMC search: Performance during CP indexing
u2022     1584309 - TMC search: Change pointer for newly created org. units
Also, did you follow these steps once TREX was connected?
[/people/luke.marson/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management]
Best regards,
Luke

Talent Management - TM - Trex 7.1 - Delta Indexing

luke.....are you out there??
congrats on your blog being featured right on the SDN homepage... very nice...
http://scn.sap.com/community/erp/hcm/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management
and congrats to Chris on his first two excellent blogs....
http://scn.sap.com/people/chris.mcnarney/blog/2010/08/26/whats-included-with-the-predefined-performance-management-process
http://scn.sap.com/people/chris.mcnarney/blog/2010/09/09/whats-included-with-the-predefined-performance-management-process--part-2
all 3 blogs are very helpful since there is little information available out there on these topics...
so we've been testing the delta indexing program very heavily - ESH_IX_PROCESS_CHANGE_POINTERS
we have found that it does not appear to be able to index new hires (new central_person index does not pick up the new CP). The only way this data can be indexed is by running a full re-index. That is problematic for us, b/c we were hoping to only do full re-indexing 1 a week or even 1 a month. our indexes take 2-3 hrs to complete and trex searching is pretty much inoperable during that time.
Have you tested new hires with delta indexing? it seems as a gap in the change_pointers program. We opened up OSS message to SAP.
some additional thoughts working with the program, relative to your blog. I would highly recommend that anyone testing this makes sure the following notes are implemented in your system. The first one is the most recent and we ourselves did not have that implemented.
1. 0.350 BC-EIM-ESH 1441190 Error in model assignments to logical system 24.02.2010
2. 0.230 BC-EIM-ESH 1408655 Alerts in syntax check due to unused indexes 18.11.2009
3. 0.260 PA-TM 1395703 Positions and termination are missing for indexing 30.10.2009
4. 0.330 BC-EIM-ESH 1249482 Functional corrections for Enterprise Search 7.01 SP03 26.01.2009
Another area which we found from testing: SAP by default does not delta index structural authority view. What this means is that if a new talent specialist is added with 741 relationship there access to see that structure will not be available in TREX search by default delta indexing. This would also impact existing organizations and positions shifted under existing 741 relationships.
The information in spro is actually quite helpful, you can find it in: talent management and talent development > basic settings > search > BAdI: Activate Delta Indexing for Authorization Data
Activtate the BADI, than the program to "create the change pointers" must run periodically in your system. This is done with RPTMC_CREATE_CHANGEPOINT_AUTH. Once that program creates the change pointers the next time your scheduled delta program runs (ESH_IX_PROCESS_CHANGE_POINTERS) all of the structural auths will be created and indexed correctly.
If we can just now get new hires to work with ESH_IX_PROCESS_CHANGE_POINTERS we will probably only run the full re-index once a week or once a month.
Let me know your thoughts,
Michael
Message was edited by: Luke Marson
Message was edited by: Luke Marson

so if anyone is interested, from my previous post I mentioned that new hires were not getting picked up by the change pointers program.
after further testing though, we found that when the authorization recon program identifies the new hires and appropriately creates a change pointer.
conclusion: to avoid full re-indexing of trex indexes, perform the following steps:
1. implement / activate the BADI - HRTMC_AUTHORITY_VIEW - talent management -> basic settings -> search
2. Schedule program RPTMC_CREATE_CHANGEPOINT_AUTH - every 30 mins, or 1 or 2 hr. This program will capture whenever anything changes from an authorization data perspective. This would include identifiying new central persons (new hires) or new TMC specialist being setup with 741 relationship. This program "creates change pointers" which than feeds the main delta program - ESH_IX_PROCESS_CHANGE_POINTERS.
3. Use Luke's blog on the instructions for the delta program - ESH_IX_PROCESS_CHANGE_POINTERS - this program you can have run every 5 mins, 10 mins, 15 mins, based on your needs. this processes all delta changes, the first time the program runs after the RPTMC_CREATE_CHANGEPOINT_AUTH program finishes it will also processes the data authorization changes, otherwise every other time the program is running it will catch non-data authorization for all the other indexes (employee name change, new performance rating, new potential, position name change, new profiiciency scale, new career profile data, etc).
hope this helps somebody!
michael
Edited by: Michael L Pappis on Oct 7, 2010 12:05 AM

Problem in Creating data for HCM Talent management System Risk of Loss data

Hello there,
I am trying to enter data for Risk of Loss in HR HCM TMS. Does anybody know in which SAP portal Release this functionality is delivered i have SAP portal 7.00 with JEECOR and JEE and with SP 16. i think all the new functionality delivered in SAP ECC6 EHP4 is supported in SAP portal 7.00 with NW EHP1. Can anybody help in configuring risk of loss in MSS package. I will really appreciate your help in the same. or any useful link for Portal configuration specific to HCM.
Thanks
Mandeep

Hi mani,
configuring Risks is part of the talent management suite, talent assessment.
check out this documentation on SAP help:
http://help.sap.com/erp2005_ehp_04/helpdata/en/b5/ae52db46094946933b2c4dd6cb5ae7/content.htm
Under SPRO you will want to use talent management -> talent assessment
there are however a number of basic things that should be looked at under talent management -> basic settings. Particularly for the "assessment landing" page to work it involves integration between the central person and the SAP business partner. This is the first step in spro, under tm -> basic settings.
Best Regards,
Michael
Edited by: Michael L Pappis on Aug 10, 2010 12:47 AM

E-recruiting - Talent Management Relationship

Hi,
we want to add search functionality to talent management relationship in our e-recruiting solution.
Search must sort on ***, female and male. Does anyone know how to customize this and what prerequisites is needed.
e-recruiting is running eh4.
kind regards,
hilde

Hello,
unfortunately there is no easy way to tidy up a complete e-recruiting.
While for pure HR components there is a way to clear all infotypes through a report SAP once delivered to get rid of database entries which were accidently transfered with a client copy including customizing tables (all infotypes are for any reason type C tables), the business partner integration of e-recruiting blocks that way.
Also doing it manually is not easy, e.g. deleting a requisition can only be done for requisitions marked "to be deleted" and this is only possible in the manager scenario.
We once developed a report to clear a complete e-recruiting system without touching process supporting data like process templates or questionaires for a customer who tested on production to ensure propper set up and a then wanted to clear everything. This took quite some days to get this right - unfortunately I cannot hand this out, I hope for ur understanding here.
Of course you can try to develop such report on your own. Other way would be a new system setup with importing all transports you did so far. Or third just clean up what really bothers ongoing project.
For a production system I would go for new setup. In best case there is a data recovery possible you only have to import the transports. Developing an own report might take you longer than this.
If it is only the dev system I would get rid of all things which could disturb my developments by throwing dumps or slg1 entries. If it is only dev full cleaning is not always necessary. But of course this need quite profund knowledge of the application and the project itself.
Sorry that I cannot offer an easy solution for this problem.
Kind Regards
Roman

Configuring TREX for HCM Talent management functionality using Nakisa

Hi,
We are configuring the Talent Management functionality in ECC-HR system.We have installed TREX 7.1 patch number 36 and Nakisa.
We are using the 'embedded search' functionality.
Now, also and are trying to create indexes using the Administration cockpit (tcode ESH_COCKPIT).
However we are getting the error 'System DHS, client 100: A connection already exists' while creating a 'search connector' in the cockpit.
Also, we are getting the below log error in the system in SM21:
''TREX_ICM - Send_Error; return code = 112, return text =HTTPIO_PLG_ICM_CONNECT_FAILED-Fehle''
Kindly let us know what should be done.
Thanks & Regards,
Kunal.

Hi,
Now the initial error we were getting is resolved by applying one note suggested by SAP OSS.
However, now we have another issue, while creating indexes using tcode ESH_COCKPIT in the backend system.
We get error when we try to go to tcode TREXADMIN --> TREX
ABAP Customizing --> 'Net Performance'.
It gives the error below:
ERROR
Remote communication failure with partner http://:33003/ICMConnectTest
HTTP Status 507: Kernel error:ICM_HTTP_CONNECTION_FAILED (400 )
Kindly let us know why we get the error because even while recreating
the indexes we get similar error i.e. Remote communication failure with
partner http://cca1cs0872:33003/asxml/multiIndexCellTable
The icm timeout parameter is sufficiently large i.e. around 30 minutes.
Also, the RFC (TREX_DHS) from ECC-HR system to the TREX is working fine.
Thanks & Regards,
Kunal.

Need help on HCM talent management

Hi,
Can anyone guide me on talent management calibrate, assesment and how to use employee development plans in new HCM
Thank You,
Jessi

read here
http://help.sap.com/erp2005_ehp_04/helpdata/EN/44/10215acc0d5cf8e10000000a155369/frameset.htm

Talent Management Enhancement pack 4 Business Function HCM_TCM_CI-1

This business function contains some new job architecture functionality that we would like to utilize. These new object types are functional name (FN) and job family (JF). We do not plan to configure any of the talent management functionality because we will not be using it at this time. Activating this business function also activates a functionality called Embedded Search which requires TREX 7.1. We do not plan to do any of the configuration for the embedded search functionality either at this time as we don't think we will need it.
My question is, is anyone aware of any issues that might arise or what other SAP functionality that might be impacted by moving this business function into our Production environment without doing any of the configuration. We have implemented SAP Payroll, Benefits, Org management, Personnel Administration, eRecruiting and Learning.
Thanks in advance for any advise you can provide.

Hi Kathy:
In a nutshell, you shouldn't run into any issue. You're just going to get a host of new web dynpro apps, OM data, and infotypes for the Central Person (the 74XX infotypes). If you don't use them, then that's fine, it won't hurt anything.
You should be just fine using the HRP1001 450 relationships from JF to FN and C to help drive your job architecture. You would potentially need to use transaction HRTMC_PPOM to manage your job family/functional area relationships, but you won't negatively impact anything you have already implemented.
If you're not going to use any of the Talent Mgmt functionality, you also don't need to worry about enterprise search or TREX. I'm assuming you aren't using Succession Planning in eRecruiting, right? If you do ever consider using the Talent Management functionality you've now implemented, you will have to migrate data over from the old eRecruiting version of Succession Planning. Other than that, you should be good to go.
Hope that helps!
Thanks,
Chris

Talent management: talent information

Hi gurus,
I've used a day or two trying to locate this issue, can't seem to find anything, so hopefully some of you have experienced this before.
Currently I'm working on what's supposed to display in talent information in portal, and the weird thing is that some employees gives results on all the fields, and some are almost blank. The fields are defined, and new fields are created through BAdI, these works fine. I tried to change the org unit of some persons (into test org unit), to get real PERNR (which is the statement for one of the fields), and not only fictional PERNR from the test persons, here is where the issues starts.
Ref IMG documentation:
"If you want to implement the Talent Management and Talent Development application, a Business Partner (object type BP) object must exist for each of the central persons (object type CP) in your system."
I access transaction SA38, and runs the program HR_SYNC_PERSON. What I've found out, is that persons with IT6 result in a Basic Data error, people without IT6 runs smoothly through, and displays all wanted information. Why is that, how can it be that persons with address data won't work? IT6 uses time constraint 1, and deletion is not a option. How can I solve this?
QUESTION: Have any of you defined XXDEFAULT as a address type (cross client)? IMG-path: SPRO u2013 SAP BP u2013 BP u2013 Basic settings u2013 Address determination u2013 Define address types
- This may solve the issue, but I'm not comfortable doing changes cross client. Hope there are other solutions.
I would really appreciate some help, and please ask if more information is needed.

Hi Smriti,
You cannot search for Talent Group = ''. Try Talent Group = '*' instead.
For the second issue, it looks an issue with the Talent Group names. First, check SAP Note 1555220 - Activation of advanced search for TMS to ensure that you have the prerequisite SAP Notes installed. I would also raise an OSS message as there doesn't appear to be any SAP Notes on the issue.
Best regards,
Luke

Talent Management - Talent Search and Enterprise Search

Hi All,
We are on ECC 6, Portal 7 SP3.
We are using Talent Management Business Package. Under Talent Management-> Talent Information, there is an iView called Talent Search(which is based on the Webdynpro ABAP "hrtmc_search").
For this Search functionality I have read that SAP Netweaver Enterprise Search is needed.
My question is:
1. Is TREX required for Talent Search. I've read that it can be integrated with Enterprise Search. Please note that we are not using KM and Collaboration.
2. Is it necessary to integrate AS Java with Enterprise Search since it will only be used for Talent Search iView which is in any case a webdynpro abap application.
So in this case Enterprise Search will only be integrated with AS ABAP / ERP system - Is this assumption correct.
Your input and help is much appreciated..
RD

Hi RD,
the TREX you will need for this will be specific to HCM and called via HCM's own strategy in ECC 6.0. This - for all I know - should be through AS ABAP for indexing and AS Java for searching.
This should have nothing to do with the Portal's access to TREX, as the functionality is HCM's, even if provided to Portal in an iView. For the specifics, please check your HCM Master Guide and other documentation and/or discuss with your technical consultant for ECC 6.0.
Best, Karsten

Talent Management - Change of Reporting Manager

Hi all,
I have changed the reporting manager relationship in SPRO: Talent Management and Development>Basic Settings>Specify Type of Reporting for Determining the Manager from INDIRECT to DIRECT (to A002 relationship).
However, after the changes I am unable to view the manager's name under the talent profile header and also those employees with A/B 002 relationship in MSS talent assessment.
Before the changes (with INDIRECT relationship), I was able to view the the manager in the talent profile header and employees under the manager.
Are there any other configurations needed besides the above is needed for me to view the A002 manager and the relevant employees under him.
Thanks in advance.

Hi Eric,
This is the only setting that you need to enable if you use S A 002 S relationships. I'm not sure why you don't see the correct reports and managers, so it could be down to an evaluation path (as suggested above) or it could be a bug. I would suggest raising and OSS message for some clarification.
If you do that please post the solution you get from SAP here, since it will be useful for other users of the forum.
Best regards,
Luke

SAP TALENT MANAGEMENT V/S NAKIS

Similar Messages

Maybe you are looking for