Succession Planning 3.0 -> Where to set Readiness high value

[jack_wong]

Hi,

I'm using custom scale ID for performance, potential, readiness, and ranking.

Well, for performance and potential, we could change the high value in extrainfo.xml

But what about readiness and ranking?

For readiness, I've change these 2 files:

/Titan_Templates_SRS/successionstatusxsl.xsl (from 0001 to 0003)

/Titan_Templates_SRS/successionstatusnofakenodexsl.xsl (from 0001 to 0003)

It kind of work in most scenarios.

But the Dashboard is wrong:

http://imageshack.us/photo/my-images/854/readiness.png/

Any idea?

Thanks

Jack

[lukemarson]

Hi Jack,

That looks like an issue with the caption rather than the values. If you have "swapped" your values around from the standard then that would make sense (e.g. the default Ready Now is 0001 but your Ready Now is 0003).

If you go to ..\SuccessionPlanning\Root\Language\Titan61.xml and search for keyPostionSuccessorsReadyNow you will find the caption there: Key Positions with Successors Ready Now. Just change the text to what you want ("Key Positions with Successors Ready Forward"?).

If this is not how you want to see it then you need to re-write this analytic or correct your scale in SAP.

Best regards,

Luke

[jack_wong]

Hi Luke,

I guess changing the text could solve the problem.

But the user would prefer to see the value of Ready Now instead of Ready Future.

Anyway that I could change it to count value of 0003(Ready Now) instead of value 0001(Ready Future)?

Thanks

Jack

[lukemarson]

Hi Jack,

I think the problem is that your order in SAP is the wrong way around. If you swap the values in SAP they will be reflected here correctly. It has no other impact on Talent Management.

Best regards,

Luke

[jack_wong]

Hi Luke,

The reason why we used 0003 as Ready Now is because we want the 9 Grid Box to show top performers on the top right corner.

If we used 0001 as Ready Now, the successor will be shown on lower left corner.

There is really no place to set the max value for readiness like potential and performance in extrainfo.xml?

Regards

Jack

[lukemarson]

HI Jack,

That is not correct - Readiness is not related to the Performance v Potential (9-box) grid. That only displays Potential, Performance and, if selected, Risk. Readiness shows in the Calibration grid, but this is just to calibrate successors for a position.

As I said previously, changing the order of your Readiness has no other impact on Talent Management. Readiness is only used during the assignment of Successors and talents to Successor Pools.

Best regards,

Luke

[jack_wong]

Hi Luke,

Yes, I agreed that Readiness has no impact on Talent Management.

But we would still wanted to show those who are in Ready Now (shortest period) with best ranking showing on the top right.

Even though it's calibration grid, we still want it to appear on top right for the successor who is in Ready Now and best ranking.

By using 0003 instead of 0001, we managed to do this.

But the Dashboard is counting the value of 0001.

How to change the dashboard to count value of 0003?

Thanks

Jack

[lukemarson]

Hi Jack,

The Dashboard counts the SAP default, so in that case this requires some customization.

In OTFSchema\functionConfiguration\DashBoard_SucPlanMerged.xml locate the processed table KeyPosWthSucReadinessCount. In the following line change ASC to DESC.

<processedSection processedName="OrderBy" function="" as="" delemiter="" type=""><![CDATA[SuccessorReadiness ASC]]>

Remember to make the change in your .delta folder.

Best regards,

Luke

[jack_wong]

Hi Luke,

Tried your suggestion, it's still not working.

The graph is still sorted by Ready Future, Ready Soon, and Ready Now.

The value is still picking the count of Ready Future.

Regards

Jack

[lukemarson]

Hi Jack,

Did you put the file into your .delta folder and did it publish to root\XML\OTFSchema\functionconfiguration?

Can you attach your file here?

Thanks,

Luke

[jack_wong]

Hi Luke,

Yes, it's in .delta folder.

There isn't a way to attach file into the forum.

The code looks like this:

<processedTable name="KeyPosWthSucReadinessCount" download="True">
  <source>KeyPosWthSucReadinessTemp</source> 
 <processedSections>
 <processedSection processedName="OrderBy" function="" as="" delemiter="" type="">
 <![CDATA[ SuccessorReadiness DESC   
  
]]>

Thanks

Jack

[lukemarson]

Hi Jack,

Sorry, I have an option to attach files. Maybe you can send it to me and I can attach it to a post?

Did your file publish to root\XML\OTFSchema\functionconfiguration folder?

Best regards,

Luke

[jack_wong]

Hi Luke,

Sent it to your email address.

I put the modified file in:

.delta\OTFSchema\functionConfiguration

When I check, the changes are being published to:

SuccessionPlanning\root\XML\OTFSchema\functionConfiguration

Thanks

Jack

Edited by: Luke Marson on Sep 15, 2011 12:40 PM - DashBoard_SucPlanMerged.xml added

[lukemarson]

Hi Jack,

Thanks for sending the file - I attached it to your post. Basically, I see nothing wrong with the configuration. I tested the function and it returned the data in a descending order (although I used a .NET utility).

The only thing I can suggest is to restart the SuccessionPlanning service in NetWeaver Administrator. If that doesn't work you could raise an OSS message with your function and specify that with ASC or DESC this returns the same data, when it should not.

Another solution might be to create a new processed table that just counts the 0003 value and then create a new data element and put that into the report configurations for this value (Dashboard_SPKeyPosSucReadinessCountRep.xml and Dashboard_SPKeyPosSucReadinessCountRepNumber.xml).

Best regards,

Luke