Compensation-Combined Statement tokens for position effective date

[Olskar]

Hello everyone,

My client requested the following requirement for the statement:
In the case of a promotion, a condition text appears. In that section, they want the effective date of the new position and the new position title to be displayed.
To retrieve the position title, we used the token [[$TITLE]], which works fine.
However, we can't find a similar way to retrieve the effective date.
Does anyone know anything about this and could guide me?
From the investigation we've done, we haven't found anything that brings in the position effective date.

Thank you in advance,

Olga

[xavierlegarrec]

Hi @Olskar 

There is a set list of standard tokens that can be used in statements and in email notifications and I am pretty sure that one isn't in it. If you want to double check I am pretty sure the link to that list of token is somewhere in this community chat.

To add complexity to your requirement this date you set in Plan Setup > EC settings cannot even be reported on from Adhoc reports or People Analytics, it's a hard-coded "setting" of the template.

I think your only option here would be to add a custom column on the worksheet that gets that date from a lookup table customer updates every year (I do that almost in every varpay customization with fiscal year dates to be able to make comparisions between records dates and fiscal year dates).

Once you have the date showing in a custom column for everyone then you can use this trick in case you want to show it on the Main Body area of the statement: 

https://blogs.sap.com/2020/09/12/making-your-standard-compensation-statement-always-fit-on-one-page/

All the best,

Xavier

[Olskar]

Hi Xavier,

Thank you so much for your detailed response — really appreciate it!

I actually already had the article you referenced and had thought along the same lines. I’ve thought the workaround with a custom column pulling the date from a lookup table, just like you suggested, as a temporary solution until I find something more robust (or something I might have missed). Thanks again for confirming the approach and for sharing the link!

Τhank you,

Olga