Brent Wilson Sr Solution Architect

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.

The "Do not allow manual entry" should be added as an option to the Legal entity overrides.

We have many clients that have global operations where certain subsidiaries record their financial results as a ledger entry (monthly trial balance results) instead of having full operations transacted in each subledger.

They would often like to use a Shared Chart of accounts for all of these subsidiaries. However, the "Do not allow manual entry" flag on a Main account prevents that usage. If that is set on an account (such as Accounts receivable), that account is appropriately configured if all activity goes through the AR subledger. However, that account would then be prevented from being used in other Legal entities where they record ledger entries for their financial results.

Therefore, the Legal entity override should allow setting that differently than the global setting.

The Consumed posting method in the Project accounting > Production parameters doesn't allow having a Costing sheet to be configured.

Therefore, there is no way to include surcharges such as Overhead as part of the cost for the item that is produced.

The alternative would be to configure Indirect cost components within the Project accounting module to add indirect cost when a specific type of transaction is posted.

However, Indirect cost components are not supported when direct Production order transactions are posted.

Suggestion: Add functionality that will create the Indirect cost amount in a posted Project transaction when the Production posting method is set to Consumed and the appropriate Cost category is posted within the Production order. If an Indirect cost is configured for that Cost category, it should create the indirect cost even though the Transaction origin is Production-consumed.