Hana Trinh (Tek Experts) SCM

Currently system allows to ship transfer order from non-advanced warehouse to advanced warehouse by using work creation process "Transfer order item/line receiving”. However, if using this one, we can not ship this TO with license plate.

We hope PG can review and add feature that allows to Ship transfer order from non-advance warehouse to advanced warehouse and using same license plate.

Expect system should validate financial dimension right away PO submit, not show error in Purchase workflow history.

Currently when submitting PO without financial dimension, system will not validate it right away PO is submitted, it only shows error in purchase workflow history.

We expect that in the future, Product Group can review and add validation function that can provide warming to user checks if PO is submitted with blank financial dimension.

When version rule set to "List", the system is forcing us to select the next version list number during the upload of product records in D365 FinOps, rather than allowing us to upload products with a specific version number.

Example:

1. We need to upload the product records with the following version numbers:

  - ABC00001 version A

  - ABC00001 version C

  - ABC00001 version E

2. However, D365 FinOps currently forces us to upload in version sequence and not select the desired version number:

  - ABC00001 version A

  - ABC00001 version B

Expectation: System should allow importing multiple products with specify a custom version number in case version number rule is set to LIST.

We would like to request any function from standard environment that can restrict system generate production work order if cycle counting work exists.

Customer sometimes release work to the warehouse that does not need picking for several days. The warehouse workers manually block it at the moment so as not to show for picking on the scanners.

Request PG to consider adding a criteria that would help the system auto block work based on say 2 ship days ahead, or, prevent the sales staff from releasing these types of orders that do not need to be picked yet

We would like to request a function that allows system post product receipt in order registration lot.

If the LOT quantity that is registered first, system should consider to take first when posting product receipt?

Example:

We have PO with 1st registration “lota” 300qty

2nd registration “lotb” 100qty

3rd registration “lotc” 200qty

Step 2: Quality orders are passed.

Step 3: then when posting product receipt with 300 ea. We expected system will take the first lot in 1st registration in product receipt

We setup reason code policy Mandatory for counting reason code type, however, when process cycle counting work in mobile device, if we click "Finished" button, it bypass the reason code for counting even reason code is set mandatory.

The counting journal posted successfully without reason code. Please consider to improve process in the future or remove "finished" button in next releases.