Suggested by Brent Wilson – New
Before deprecating the One voucher functionality, one additional scenario needs to be considered:
Account for different Projects on different Purchase order lines within the same PO.
Purchase orders are often split to multiple Projects, where separate Project Ids are selected in different PO lines (within the same PO). These PO lines will add cost to each Project, and need to be included in the same PO.
The One Voucher functionality (when the LedgerParameters.AllowMultipleTransactionsWithinOneVoucher is disabled) will prevent posting the Product receipt and Invoice for the Purchase order.
This is also a valid scenario for Fixed assets to create different Fixed assets per PO line.
We need to support these scenarios as well, and I would prefer to do it efficiently - without adding multiple transactions using a clearing account, creating a difficult-to-follow audit trail, and adding another Balance Sheet reconciliation for the clearing account.