In many screens, such as PO, Issue, AP Bill, Receipt, even Project Transactions, the system allows a user to choose an existing Project Task and then apply any Cost Code existing on the project to that Task even if that combination of Project Task/Cost Code does not exist on the Project Cost Budget.
The system currently adds a new row in the Cost Budget, which to my client is a real issue.
Furthermore, it would be additionally helpful to NOT allow new Task/Cost Code/Account Group combinations beyond what exists on the Cost Budget.
Has anyone else ran across this issue and were you able to prevent it from happening?