Shifting benefit plan with Demand start date : figures damagedIssue -> Shifting benefit plan with Demand start date looses all the data with respect to the entered benefit and functional benefit. It makes them 0 and also makes the total planned benefit and benefit in functional currency as 0. STEPS TAKEN:Steps to Reproduce:1. Create a demand from dmn_demand.LIST table and then click on New .2.Fill the start date and end date as Jan 1 2021 and dec 31 2021.3.Save the record and then create a benefit plan from the related list tab.4.Fill in the Offset type: start date and the offset value as 0 and the duration in periods as 12.5.Check and fill any other mandatory fields.6.Save the record and you will see that in the benefit plan breakdown there are 12 records with entered benefit as 0 and Functional benefit as 0 .7. Manually edit the entered benefit as 6000 for january and december.8 .You will see that the planned benefit and the benefit in functional currency becomes 12000.9.Go to the demand now and change the demand start date to june 1 instead of january 1 and save the record.10.Now you will see that in the benefit plan breakdown all the values will be zero that is the planned benefit will be 0 as well as the entered benefit for dec fy21 will also become zero.Investigation Summary: -> This issue is also reproducible OOB. In the instance vsquebec.-> Couldn't find any existing PRB with this issue.Update from dev team passed to customer:1.As per today's design, the estimated benefit in the benefit plan breakdowns are recalculated whenever fiscal period is changed so as to reflect the new benefit.For eg, if a benefit plan is created from FY21:M01 - FY21:M05 and there is a change in plan so updated it to start from FY21:M02, system ensures FY21:M01 benefit is cleared to reflect the same.2.Also, when recalculating, we divide the "Entered Benefit" into the breakdowns. If recurring is true, every breakdowns will get same entered benefit, if false the amount is split. However in the your case, i see that the entered benefit is 0 and that's why system is updating all the breakdown values to zero.3.There is no mechanism to identify if the breakdown benefit is manually entered. We have this implementation to support other use cases where customers always wanted benefits to be split if fiscal periods change.So, we wanted to understand the use case behind creating benefit plans with 0 entered benefit. And how often is this scenario happening for you? so that we can evaluate further on this use case.ReleaseQuebecCauseThis is a defect and a PRB has been raised for this PRB1508332.ResolutionPRB1508332.