Andy Pham

There should be a function that allows us to set up an automatic cost/sales price for item transaction on projects.

Currently, the standard D365 system allow us to set up a specific cost/sales price or markup for each project/project contract. However, this function is only available for hour, expense, fee transactions.

it appears that prices for item can only be configured via Inventory management. Unfortunately, there is no option to set an automatic price/markup for each project/project contract.

On an approved or confirmed purchase order, it is noticed that if we make a Request Change that edit the unit price, the PO will need to be re-approved through workflow and re-confirmed. Upon reconfirmation, a new record would be generated in "Purchase order confirmation" (001).

Now, if we make a Request Change but instead only make a change on header (method of payment for example), i's noticed that the PO will be automatically approved and confirmed. This request change, however, does not generate a new Purchase order confirmation record.

However, if we make a third Request change which requires re-approve and re-confirm again (similar to request change number 1), it will be noticed that the new record's number will skip number 002 and show up as 003 instead.

It appears that despite not generating a new record on Purchase Order Confirmation, request change number 2 would still be counted.

Cause:

When we confirm a PO, the PO confirmation journal number is created according to the count of purchase order version:

VendPurchOrderJour::setDocNum(): this.PurchOrderDocNum = strFmt('%1-%2', this.PurchId, VendPurchOrderJour::numberOfPurchaseOrderVersions(source));

When a PO was approved automatically by workflow, it will also be confirmed automatically, and no confirmation journal will be created. However, a purchase order version will still be created.

Thus, upon the next confirmation, the system will still take count the auto confirmation, leading to the Document Number on VendPurchOrderJour showing 3 instead of 2

Suggestion:

For better consistency, request changes which trigger auto approval/confirmation should either generate a confirmation journal or should not be counted upon the generation of new confirmation journal DocNumber