Stephanie Woods

When updating the account structure segments and allowed values, system updates sibling records (same values to the left) without informing user that this has happened.

This leads to additional records being changed which the user has no knowledge of.

Suggest that either a warning message is implemented to inform the user that additional records will be updated, or that only the selected record is updated.

In the business process where the user updates attributes relating to project transactions, often in bulk, the simple yes/no option under Sales price update is insufficient.

Some transactions it would be appropriate to recalculate the sales price. For PO item transactions, this is problematic because the price for recalc coming from the released product rather than the PO means that the sales price is missing in the case of service items, where one service item is used for multiple purposes and will never contain a sales price against the released product.

In the case where you select Yes for an item transaction, the Sales price is recalculated from the details against the released product record, and does not respect the calculation for sales price already carried out for the purchase transaction on the purchase order. In the case of service items where we do not hold any prices against the items, this will always calculate as zero when referring back to the released product record.

The impact is zeroing out a sales price which should be non-zero, this has significant impact on both sales invoicing and accounting as the billed amount will be lower than expected, meaning that the only feasible alternative is to select No therefore making it impossible to make sales price adjustments to service item transactions on projects.

If this function was adjusted to be parameterised to respect source transaction (e.g. Purchase Order) price rather than released product price, this would be a significant improvement.