-
Ability to inherit Purchase Requisition Preparer to Purchase Order Orderer
PO Orderer is crucial to the Vendor Invoice (mis)matching assignment but as PR Preparer is not inherited we're unable to send the matching issues to the correct person and can only send to a User Group. Same as this community question: https://community.dynamics.com/365/financeandoperations/f/dynamics-365-for-finance-and-operations-forum/395981/purchase-requisition-preparer-to-purchase-order-orderer -
Data Entity for Accounts payable > Payment setup > Return format status mapping (VendPaymReconciliationReturnStatus_W)
Create a Data Entity for Accounts payable > Payment setup > Return format status mapping (VendPaymReconciliationReturnStatus_W) to allow
-
Ability to change Inventory Status in Transfer Journal
In Transfer Journal (Inventory Management > Journal entries > Items > Transfer) the Line details > Inventory Dimension > TO Inventory Dimension > Inventory Status is disabled/greyed out, which limits the ability to update the Inventory status in the transfer inventory process.
Enabling this would allow for greater flexibility and align with the overall solution where Inventory status updates are allowed in the Transfer Order receiving process.
-
Ability to set campaign/deal price rather than discount amount/percentage
We have a scenario where the retailer will have campaign prices; eg. Product X price during August is $150, regular price is $200. The campaign price cannot not used together with any other retail discount. If an affiliation discount (regular price - affiliation discount) is lower than the campaign price then it should be used, but the affiliation discount cannot be added on to of the campaign price.
We do not want to have a $50 discount.
(We tried using Trade Agreements (Price Group=Campaign) for the campaign prices but we are unable to exclude the retail discounts from said trade agreement.)
-
Make SalesFormLetter_Invoice PurchFormLetter_PurchOrder and similar classes respect Conditions so sequential execution can be setup in a batch job
SalesFormLetter_Invoice (Sales Order Invoicing) and PurchFormLetter_PurchOrder (Purchase Order Confirmation) classes does not pass of the conditions when creating run time tasks for multithreading. The main task also ends before the 'child tasks' are done prompting the next task in the batch to start running in parallel as the condition of the previous task being Ended or Error is met.
We ask the these classes get updated so that the main "parent" task either stays in executing until all "child" tasks are done and/or inherit the conditions setup in the batch job so that the next sequential task doesn't start executing in parallel.