web
You’re offline. This is a read only version of the page.
close
  • Service order line should allow negative quantity

    Currently, D365 does not allow negative quantity in Service order line.

    In some business operation, negative quantity in Service order is common practice: users use negative quantity as a return process, specifically when item is returned back to inventory.

    Hence, it is necessary to add negative quantity for a Service order, which can adapt several business requirements.

  • Service order line should allow negative quantity

    Currently, the Service order line does not allow negative quantity. In business operation, negative quantity in Service order line is a common scenario which represents as a return process.

    Having said that, it is necessary that the service order line can enable negative quantity, which should be applicable for several businesses.


  • Allowing users to attach documents in PR headers, block attaching documents in PR lines.

    Currently, users can attach documents in both Purchase requisition headers and Purchase requisition (PR) lines.

    But in some business's perspectives, it is easier for customers to monitor attachments in PR headers; hence users need to block attachments in PR lines.

    From there, D365 might need a function that can enable the action allowing documents in PR headers, but blocking documents in PR lines. This should be applied for other forms such as Purchase orders/Sales orders...


  • Posting inventory in both accounting and transaction currency.

    By default, in D365, when a Purchase order is booked in the foreign currency (EUR), the Purchase order is posted transaction currency, but inventory is posted in accounting currency (USD). 

    It brings a challenge to reconcile the inventory between USMF and different companies, because USMF manually booked the inventory in EUR in transaction currency.

    Hence, it should have a feature that can enable to post inventory in both transaction currency/ accounting currency.


  • Perform the Vendor credit balance check for Purchase order

    Currently users can submit the PO to the workflow even if the PO exceeds the credit limit, its only after the workflow is approved then system stops the purchase order when user post product receipt.

    From customer side, when submitting workflow to the Manager, the PO is being asked why the PO is exceeded credit limit but still user can submit it, which users want to prevent those kind of scenario. Secondly, when confirming the PO, the PO will be sent to Vendor and they will prepare goods to deliver. 


    Hence, it should have the Vendor credit balance check for Purchase order when users confirm the Purchase orders.

  • Change default account type in Sales quotation

    When creating a Sales quotation, the default pop up for account type is Prospect. In several business process, they use the Customer account type instead of Prospect and users accidentally miscreate Sales quotation with wrong account type.


    Hence, there should be a parameter where user can set the default account type is Customer.


  • System should allow Job type default forecast creation when the check "Enable validation to check if Activity is in closed state" is Yes

    Currently, when the check "Enable validation to check if Activity is in closed state" parameter is set to Yes, users are not able to create the Maintenace job type forecast with error message "Cannot set the activity number to XXX as it is already closed."

    In some business process, when the Activity is in closed state" parameter is set to Yes (they don't want to post transaction in the Closed activity), users need to create Maintenance Job Type Default forecast and the system should be able to create the forecast.


  • "Modified by" field in Costing version should present users who make changes for Item price.

    Currently, the “Modified by” field in Costing version is taking from Inventory dimensions, hence whoever make changes in Costing version form, it will present as "Admin".

    However, it should have a "Modified by" field that getting from Item price to present exact users who make changes to the Item price of the Costing version.

  • "Modified by" field in Costing version should present users who make changes for Item price.

    Currently, the “Modified by” field in Costing version is taking from Inventory dimensions, hence whoever make changes in Costing version form, it will present as "Admin".

    However, it should have a "Modified by" field that getting from Item price to present exact users who make changes to the Item price of the Costing version.

  • Purchase requisitions should be visible for specific legal entity

    Currently, purchase requisitions are shared across legal entities. But in some business process, all legal entities must show only their own PRs.

    Hence, it should be a function that can enable this process.