Kishore Melepati

The estimated column was not updated the some of Sales Orders.

1.create purchase order. 2.Create a new PO. 3.Choose the vendor account. 4.Then change the delivery address in the pop out window: 5.Then hit OK. 6.The created PO opens. 7.Add an item. 8.Open the line details -> Address. 10.A wrong delivery address was choosen: 11.I assume it is the default one, but not the one I have chosen at the creation of the PO.

Warehouse management parameters. 2. Created an warehouse item. 3. Directed by: user directed. 4. Purchase receive. 5. Click login. 6. Add the line with the item: test and quantity:10. 7. Click on inbound. 8. Click on purchase receive. 9. Click ok. 10. Click ok. 11. Work completed. 12. Registered quantity is 10. . Cancel the work. 14. Work has cancelled. 15. See the line quantity ordered:10 as expected. 16. Add the another line same Item : Test quantity:20. 17. Click ok. 18. Work has created. 19. Click on purchase put-away. 20. Enter the work id. 21. Work has completed. 22. Work has closed. 23. Cancel the work. 24. Work has cancelled. 25. Check the line quantity still has registered quantity. It is not correct.

Problem: Procurement hierarchy node cannot be deleted Error message: Category cannot be deleted while dependent Category access rule data exist. Delete dependent Category access rule data and try again. Documentation: Procurement and sourcing  Procurement categories A node has been created as shown below. The categories are handled by the ‘Category access policy rule’ in the purchasing policies. Procurement and sourcing  Setup  Policies  Purchasing policies  [Edit] The node has been included in the version identified by effective date/time: 22-02-2021 10:08:35. To prepare for the deletion, the node was removed from the selected categories in the version identified by effective date/time: 22-02-2021 10:09:27. To delete the node, select [Edit category hierarchy] and [Delete category node]. If pressing [Yes], the following warning and error message is thrown: Due to the category having been controlled by the policy rule, it is not possible to delete the category as it is not possible to remove from a policy rule history version.

We have an supplementary sales item setup: 1. Supplementary items needs to be added for all customer a. code = All 2. For a specific item a. Item code = Table b. Item = PW002 3. It is not optional a. Optional = No 4. It is free of charge a. Free of Charge = yes 5. It should be applied to all lines containing the item a. Once only = No   CALCULATE SUPPLEMENTARY ITEMS FROM SO When SO is created with one or more lines containing the items for which supplementary items are applicable and calculating supplementary items: 1. SO with 2 lines containing the item for which supplementary items are applicable. 2. Result after calculating supplementary items: a. 2 lines are inserted containing the expected qty of the supplementary items   3. Assume customer calls and wants to change the qty, or sales takes notices an order entry error and changes the qty of the original sales lines: a. Line 1 qty is changed from 5 to 4 b. Line 3 qty is changed from 2 to 1 4. Again calculate supplementary items and this is the result: a. again inserted 2 lines (red square) with correct qty b. But also the original lines with old quantity (arrow) 5. Now suppose the sales taker was distracted and forgot he already calculated the supplementary items and recalculates again: a. D365 CSM would keep adding the lines, instead of checking the existence and updating already created lines:   6. There seems to be a related between the calculated supplementary items, because when canceling the original manually created SO line all related supplementary SO lines are also cancelled: For this to happen you need to enable below setting on the customer masterdata: Sales order defaults: Automatic cancel = Yes

we have configured the keyboard shortcut on mobile device display settings, new warehouse application by using the keyboard short cut key Cancel(f3). It is not working on the new warehouse application.

When we do multiple registrations (because they are received on different LP’s) on the same purchase order line of the same batchnumber then multiple quality orders are generated. Registrations on purchase order line: - Registration qty 205, batchnumber B1 --> a quality order has been generated for batchnumber B1 - Registration qty 205, batchnumber B1 --> a extra quality order has been generated for batchnumber B1. o So this is duplicated in the system… - Registration qty 205, batchnumber B2 --> a quality order has been generated for batchnumber B2 - Registration qty 205, batchnumber B3 --> a quality order has been generated for batchnumber B3 Requested/expected behavior should be - Registration qty 205, batchnumber B1 --> a quality order has been generated for batchnumber B1 - Registration qty 205, batchnumber B1 --> no quality order should be generated for batchnumber B1 - Registration qty 205, batchnumber B2 --> a quality order has been generated for batchnumber B2 - Registration qty 205, batchnumber B3 --> a quality order has been generated for batchnumber B3

When we do multiple registrations (because they are received on different LP’s) on the same purchase order line of the same batchnumber then multiple quality orders are generated. Registrations on purchase order line: - Registration qty 205, batchnumber B1 --> a quality order has been generated for batchnumber B1 - Registration qty 205, batchnumber B1 --> a extra quality order has been generated for batchnumber B1. o So this is duplicated in the system… - Registration qty 205, batchnumber B2 --> a quality order has been generated for batchnumber B2 - Registration qty 205, batchnumber B3 --> a quality order has been generated for batchnumber B3 Requested/expected behavior should be - Registration qty 205, batchnumber B1 --> a quality order has been generated for batchnumber B1 - Registration qty 205, batchnumber B1 --> no quality order should be generated for batchnumber B1 - Registration qty 205, batchnumber B2 --> a quality order has been generated for batchnumber B2 - Registration qty 205, batchnumber B3 --> a quality order has been generated for batchnumber B3

The license plate has already been counted – error with counting through mobile device. I have this issue with the counting through mobile device. I count the following license plate: I have no problem, but physically I found on that license plate another item. So I try to add this item to the same license plate but I have the following error message: "The license plate has already been counted" Is it possible to add to a license plate already counted another item? I try also to add it at the end of the procedure (“Add new LP or item?”) but I have the same error:

1. Create an item:Test Storage dimension group: ware Tracking dimension group:Batch-phy Item model group:FIFO Reservation hierarchy:Batch-Above 2. Add the on-hand inventory. Batch number:2 and location”bulk0002 3. Create another item: Test1 Storage dimension group: ware Tracking dimension group:Batch-phy Item model group:FIFO Reservation hierarchy:Batch-Above 4. Add on hand inventory with the batch number:2 and location:bulk-002 5. Warehouse management << cycle counting << cycle count work by location. 6. Maximum number of cycle counts:3, location: bulk-002 and warehouse:62. Click ok. 7. Click ok. 8. Warehouse management << cycle counting << open cycle count work. 9. Work has been created : USMF-000043 10. Login to the emulator with the userid:62. 11. Click on Inventory. 12. Click on cycle count guided. 13. Batch:2 and quantity:250 and click ok. 14. Enter again the same values batch:2 quantity:250 and click ok. 15. Item: Test1 , batch:1 and the quantity:20 and click ok. 16. Again, the same batch number “1” quantity: 20 and click okay. 17. Click on finished. 18. Work completed. 19. Warehouse management << cycle counting << cycle count work pending review. 20. Click on cycle counting. 21. Select Accept count. 22. Two journals are created. Actual Results: When we select the same work id with different items and accept count, two journals have posted. Expected Results: When we accept the count with same work ids, there should be only one journal for both items.