When the user changes an account from one account to another via account change, they would like their initial budget and GAAP original budget amounts to be carried over. The user would also like adjustments transactions to be carried over to the new account. Additionally, the user would like proposed amounts to be updated appropriately if they exist for budgets linked to an account change.
During the account change process, we need to re-assign any budget transactions from the budget associated with the old account to the budget associated with the new account.
In the case where transactions exist for the budget associated with the destination expenditure account, we want to sum the transactions of each type (temp intiial, initial, adjustment, GAAP initial, and GAAP adjustment) and assign that amount to the existing transaction in the destination budget. For example, if account A is changed to account B...and both budget A and budget B have initial transactions, then the resulting initial transaction in budget B should be the sum of the initial transactions from both budgets A and B.
Update proposed amounts for budgets associated with an account that was changed by changing the reference on the proposed amount to the correct budget.
NOTE: We are assuming that the relationship from Budget to Expenditure account is 1-to-1 in this case. We may need to revisit this in the future but for now we are going to move ahead with this assumption.
Update prior-year carryover amounts to be associated with the destination budget if carryover amounts exists for the source budget.
AccountChangeService needs security annotation. Update this and the menu option. -Comments on code review USASRCR-2142.
AccountChangeJob needs error logging if a request isn't retreived from the database. -Comment on code review USASRCR-2142.
When the user changes an account from one account to another via account change, they would like their initial budget and GAAP original budget amounts to be carried over. The user would also like adjustments transactions to be carried over to the new account. Additionally, the user would like proposed amounts to be updated appropriately if they exist for budgets linked to an account change.
During the account change process, we need to re-assign any budget transactions from the budget associated with the old account to the budget associated with the new account.
In the case where transactions exist for the budget associated with the destination expenditure account, we want to sum the transactions of each type (temp intiial, initial, adjustment, GAAP initial, and GAAP adjustment) and assign that amount to the existing transaction in the destination budget. For example, if account A is changed to account B...and both budget A and budget B have initial transactions, then the resulting initial transaction in budget B should be the sum of the initial transactions from both budgets A and B.
Update proposed amounts for budgets associated with an account that was changed by changing the reference on the proposed amount to the correct budget.
NOTE: We are assuming that the relationship from Budget to Expenditure account is 1-to-1 in this case. We may need to revisit this in the future but for now we are going to move ahead with this assumption.
Update prior-year carryover amounts to be associated with the destination budget if carryover amounts exists for the source budget.
AccountChangeService needs security annotation. Update this and the menu option. -Comments on code review USASRCR-2142.
AccountChangeJob needs error logging if a request isn't retreived from the database. -Comment on code review USASRCR-2142.