Skip to main content

Hello All,

Hoping someone can help me here.  We have a customer that apply material overhead to a work task.  I have set up the cost elements, buckets and templates and added the template to parts.  This process works and the OH is calculated on the work task as expected.  The issue we are faced with is the customer updates their OH rates on a quarterly bases.  When I run the update part specific overheads the system changes the rate even if the end date is specified.  I also noticed that I ran the update on Sept 12 but the date of the last activity did not change, although the field level details state it was the last time the record was updated.  

Here is the issue.  Even if I add a new line and end date the first line when I run the update job it changes the rate for both lines, therefore losing historical rates.  Should this job not allow to end date previous rates and insert a new rate based on the date the update is performed?

In the example below when the material is issued to the work task it is taking the proper rate with the most recent start date so financially it is ok but we lose the history.  

Is there a setting or step I am missing or is this IFS behaviour or bug?

I end dated the 1st line and added the second line.  Note the percentages of 40 and 35.

When I run the update job to adjust the percentage by 2

The system is updating both rates to 42 and 37 which does not appear to me to be correct.

Any thoughts or advice would be greatly appreciated.

Hi Michelle,

Well described case.

Last Activity Date should definitely be updated when you run this job, and system updates relevant records. So that is a bug.

And I really think it makes sense that the system should only update the records that are valid today and in the future. It should not update rates that are phased out! So that is another bug.

It would be too much right now to start creating new lines through this update job. You might want to raise an idea for this in IFS Community.

Regarding the bugs above, they should be easy to “hunt down”.

Thanks for highlight this issue, and please, please raise a support ticket for the two bugs above.

Cheers,

Mats at RnD 


Reply