Hi,
I have more questions than answers re your post, but hopefully these will help understanding your configuration and requirements better:
Q1: What is the recommended approach to maintain separate rate lines for each resource?
Why would you want separate lines for each resource? Isn't there any way you could use the Group/Role/Skill to create and maintain the rate model? It's much easier, than having a rate line for every single resource especially if you know that in the future it will be a significant increase of resources. You can still create the odd one out for specific resources or if you're using Resource Assignments to make use of the "Rate override" function.
The recommended approach depends on how often you see the need of updating these rate lines. If the volume is low and changes are not often, probably you're best with manual changes, otherwise you can look into "Import Rate Line" functionality for bulk updates.
Q2: How can we automatically update the End Date of the previous rate line when a new rate line is created?
I had a look into the structure of Rate Line records and they seem a bit more complex than what they might look like at first glance.
In your case as you're using Resource only, given it resides at the Rate Line Attributes level, enabling automation could be a bit more challenging. On paper you could potentially try with an Insert Business Rule, but then you have to check against the sys_id of the resource (at the attribute level) getting a new rate line whether they already have an existent one and update the end date of that rate line (only if it's empty, so you don't mess with the other potential rate lines for the same resource). But then, what happens if there is more than one Rate Model in the system and the resource could have rate lines in multiple rate models?
OR if you explore and test the viability of importing the rate lines, that might be easier, than scripting something for the above. You prep a file with the new rate lines, including end dates for the existent ones (if applicable) and import them into the system.
Q3: Are there any additional configurations required in the Rate Model, Planning Attributes, or Resource Management setup to ensure the correct rate is applied?
I would have a few questions first to understand how you are using this
- what sort of tasks are you creating
- when you say assigning users to tasks, do you mean naming someone in the Assigned to field or creating Resource Assignment records linked to the task
- how are you linking the rate model to these tasks
Some screen shots would probably be useful to het a better understanding of the current built.
These are just some initial thoughts on your post, would be good to see what others think as well 🙂
Good luck 🙂
Regarding the questions 1 and 2 - I'm leaning to PaulaaO's answers.
Regarding the issue:
The rate model itself sounds fine in terms of configuration. Have you made the Rate Model the "Default" one (checkbox on the rate model form)? If so, keep in mind that demands/projects you've already created before the new model are not switching automatically to the new model. On the demand/project form, check under the Financials form section for the "Rate Model" field and update it accordingly:
If you're working with pre-existing resource assignments, check to see whether their "Rate Model" field is pointing to a previous rate model. If it does, update the model to point to your new one or make it blank (so it will follow the project's rate model then):
If this is an operational resource assignment, the rate model field will show up on the form and you should have it pointing to your new model if that hasn't been the default one:
