Comments
Hello Kishor Mistry,thank you for the tip. In practice, this will probably happen very rarely, but it is clear that the example must also be possible on the system side.I see two possibilities for this case:Option 1:Both shipping numbers are printed in the comment line. I would probably completely balance the first shipment line booked and the remaining quantity in the second:Shipment No xxx Date xx.xx.xxxx and Shipment No xxx Date xx.xx.xxxx and Line 1 Item A, Ship Qty 8Shipment No xxx Date xx.xx.xxxx and Shipment No xxx Date xx.xx.xxxx and Line 2 Item B, Ship Qty 8Shipment No xxx Date xx.xx.xxxx and Shipment No xxx Date xx.xx.xxxx and Line 3, Item C, Ship Qty 8Option 2:A separate invoice line is created for each shipment line. I would probably completely balance the first shipment line booked and the remaining quantity in the second:Shipment No xxx Date xx.xx.xxxx Line 1, Item A, Ship Qty 5Shipment No xxx Date xx.xx.xxxxLine 1, Item A, Ship Qty 3Shipment No xxx Date xx.xx.xxxx Line 2, Item B, Ship Qty 5Shipment No xxx Date xx.xx.xxxxLine 2, Item B, Ship Qty 3Shipment No xxx Date xx.xx.xxxx Line 3, Item C, Ship Qty 5Shipment No xxx Date xx.xx.xxxxLine 3 Item C, Ship Qty 3
I see that the link to https://learn.microsoft.com/en-us/dynamics365/release-plan/2024wave1/commerce/dynamics365-commerce/planned-features no longer mentions batch tracking being available in 2024 Release Wave 1. Did this get dropped ot planned for the future release?Please respond as we are planning to utilize this new feature for one of our customers.
Actually, I think this is an application bug because if I have one or more dimensions as mandatory [Default Dim Account Type - Table 15 G/ Account - Posting Value = Required Code], when I execute the VAT calculation, I need to change this parameterization. So, this is a problem: the general ledger entries run out of dimensions, which causes problems in financial reporting due to the lack of dimensions that should be mandatory. And, customers will change an important setting which in itself is not a good solution either.
I am really curious what the design engineer at Microsoft was thinking when they decided on this whole logic that only uses item’s cost and not the SKUs??? Why would they assume that companies would create variants of the item and somehow magically their costs will all be the same as the item’s cost???