on 2023 Jun 22 6:41 PM
HI
We would like to use lumpsum standard functionality available in the compensation . For this I have enabled lumpsum guidelines and std field lumpsum.
Calculation which it should be based upon is different and should not be using Currentsal( as defined in std code) . Im trying to edit below XML code so that it should take Curr sal+merit (Which I have stored in Custom Column named as Cust_finsal)
While saving this code it is throwing an error which says I cant use custom field
Error:- Line 1115, column 49: Attribute "basedOn" with value "custom_finsal" must have a value from the list "CurrentSalary LumpSumTarget
Custom Field Created with below calculation . So that lump should be on the basis of this field
xavierlegarrec :- Any solution for this issue? Pl guide.
Thanks much for your help
Thanks
Ritanshi
Request clarification before answering.
Try changing the basedOn to "LumpSumTarget" and change the id of the custom column to "lumpsumTarget".
I am pretty sure you can't do this though, as like with meritTarget, lumpsumTarget needs to be an imported field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ritanshi_07
It's difficult to get you unstuck at every single step of the process... please try to explore more by yourself.
What is the ID of the Adjustment column in your template ? maybe it isn't Extra, maybe it's another field.
Make sure that in the xml for your template has the following tag set to true
then try adjusting comp-compounding as per my explanations.
All the best
Xavier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Phil and Xavier for sending responses.
I did tried both the option provided
1) Changing the name of custom column to lumpsumTarget is not allowed . Since it throws the error The comp standard field lumpSumTarget is defined with the custom field flag.. I would like to keep this field as Non-editable only.
2) Tried using Extra field (adjustment) which already in use in compensation template. While changing below code in XML for extra. it throws an error message as Element type extra-calc must be declared.
Since Im already using this as a part compensation template. Why it needs to be declared then. Can you pl guide.
xavierlegarrec
Thanks So much for all help. Im not able to tag phil. So just tagged you
Thanks
Ritanshi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI xavierlegarrec :- your expert opnion is also required here,Pl reply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ritanshi_07
Phil is our HXM lead for Pay for Performance and as expert as me if not more !
I also think Phil that you can use lumpsumTarget but unfortunately when these target fields are based on a custom formula it makes the Pct of the lumpsum column greyed out on the worksheet. And I am assuming you would like to keep it editable.
So I'm thinking of the following : you could use the extra (Adjustment) standard field for your lumpsum field and use comp-compounding feature :
https://userapps.support.sap.com/sap/support/knowledge/en/2085254
The only impact of doing so is that you would need to recalculate the final compa ratio in a custom field because the standard one would include the lumpsum which it shouldn't. You will lose colors on final compa ratio as a consequence.
You can also test whether comp-compounding is available for lumpsum (I'm not sure) because if that's the case then you got a perfect solution.
All the best
Xavier
Thanks Philip for prompt reply
How does system defines lumpsumTarget calculation. Do we have that in XML too?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.