Dynamics 365 Project Operations

I n project management and accounting module

User is trying to reduce quantity or delete the line on item requirement. This is cause common scenario when the during project lifecycle the requirements are changing. Quantity on the item requirement list is used also for analysis of required and used items.

 Getting error message in Intercompany process The intercompany sales order is being updated, and therefore you cannot add/change/delete lines.

Once a partial quantity is picked we will not be able to change the line quantity

I would like to request a new feature in invoice sending that allows for specifying the last weekday within a given period, instead of just the end of the month.

Currently, there is no way to specify a weekday that falls on the last day of the month within the specified time period, nor can you specify the period as just a weekday.

Adding this feature would provide more flexibility for invoice scheduling.

Project Management - Workspace tile showing records of different legal entity.

Description - In project management workspace the tile count is not updating properly. The tile is showing the records of different legal entity.

Customer Expectation - In DEMF legal entity the tile is showing the USMF entity records., instead it should show DEMF entity records.

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.

Make it possible to correct or cancel packing slips for project item requirements sales orders. At least if the transaction is posted to non time and material project as there is no connection for the transaction to customer invoicing.

All Project entries are recorded on Historical Cost, as determined by the Project Date or the Open Ledger Accounting date (depending on the Parameters set).

When adjusting Project Entries or using the functionality Post Costs. Dual Currency scenario's are not accurately handled and posted.

An enhancement to the process, will be to ensure that Adjustments/Post Costs are performed from the original transaction and that the Accounting Currency and Reporting Currency values are determined off the original posted vouchers or Transaction ID's and not by applying the adjustment date Exchange Rates.

At the moment, date based inputs on Project Accounting creates permanent differences on Reporting Currency and requires consistent Reporting Currency Adjustment journals on Main Accounts prohibited for Manual Posting.

Example:

Source Transaction = ZAR 450.00; Posted: 3 Feb 2022.

Accounting Currency = ZAR, Reporting Currency = USD.

When performing a Post Costs entry and selecting 3 Feb on the transaction - Accounting Currency and Reporting Currency is correctly interpreted.

The Post Costs function is however generally used as an Adjustment event in future periods.

When performing the entry on 7 Feb, the Accounting Currency entry will be correct, but the Reporting Currency scenario will have interpreted the entry on the 7th of Feb and creates a permanent difference on a Balance Sheet account.

Therefore the request to ensure that Project Accounting transactions and adjustments are carried on Historical Cost.

Environment: Project Operations non-stock

Information: Microsoft time standard time zone is UTC - Universal coordinated time. When a transaction is made for actual transactions the transaction date uses the users specific time zones. The transaction date which is time zone independent shows the correct date.

Issue: When a user changes their local time zone from UTC, and their personalization to their local time zone, then the Document date/Accounting Date are one day off from the transaction date. This poses confusion and inconsistency.

Idea: Solution to make document date/accounting date consistent behavior with transaction date.

Business Value:

Improved decision-making, enhanced trust in the system, reduce risks

I have requirements to financially post discounts to a different GL on projects. The discounts would be coming from item requirement sales orders. I would like to see the Category Groups and Project Category Groups extended to be able to specify a GL account for discounts, similar to what is currently available for item group setup for sales orders.

When a Task on a Project is deleted, the operation initially seems successful as there is no user feedback and the Project is saved however after some time if we return to the Project, we get an error that says the task cannot be deleted. This should be improved with better user feedback so that the user is aware if a Project Task cannot be successfully deleted and for what reason this has failed immediately rather than after some time has passed.

In Project Operations for Manufacturing environments (Previously Project management and accounting module in D365 for Finance & Operations). there is a function for Vendor Retention. You can assign retention terms to a project. Then, when Project purchase orders are created for that project and an invoice is generated, the retention amount is automatically calculated. When this happens, the cost associated to the project is the full amount of the invoice MINUS the vendor retention amount. Then the rest of the invoice (The retained amount) is part of the project cost once the retention invoice is posted.

This seems incorrect. The project cost amount should be the full amount of the invoice. It would seem that just because an amount is being retained from the vendor doesn't mean that it is not due and still part of the project cost. The offset, after all, is a payable (just split up between retention and accounts payable). And when the retention invoice is posted, the posting just moves the amount from retention payable to accounts payable. This entry does not seem to correlate to adding the cost to the project at this point.

This is not to mention that this causes issues in being able to reconcile your project balance against the associated ledger balance for project costs until the final retention invoice is posted.

I would suggest that the project transaction amount on the initial invoice with retention should match the full invoice amount. Then when the retention invoice is posted it should have no effect on the project cost.