Suggest a new Idea

    • 114

      Lead time by Vendor

      Suggested by Uwe SchlagmuellerPlanned 6
      Category: Procurement and sourcing

      In addition to the current lead time setup and calculation, a default lead time by vendor should be added to the vendor card. In several scenarios we had one vendor supplying 50K plus different products and maintaining the lead time per product is not really feasible. This is only the default vendor lead time, any other lead time calculations can stay as they are. 

    • 94

      Shipment date on Purchase order

      Suggested by Fredrik SætreNew 16
      Category: Procurement and sourcing

      Most vendors operate with a "delivery date" being the date where the items are shipped from their site or most often based on Delivery terms. So depending on the Delivery terms (Incoterms)  the concept of delivery date changes. EXW often means a long lead time from shipment to delivery as opposed to DDP where shipment = delivery. There is a lot of misunderstanding with these concepts and that often leads to late deliveries... 

      This means we need a similar feature on shipment and delivery as on the purchase order. Most vendors assume the delivery date is their shipment dates. It is a tough sell to change this, so a feature supporting this is sorely required and something we always do for our customers.

    • 55

      Emailing a Purchase order to a vendor

      Suggested by Microsoft – Under Review 1
      Category: Procurement and sourcing

      With the "EDIT" button in the printer set up screen I have three ways to let the system find an email to send a Purchase order to a vendor. But the most logical way, what the user expects, using the email on the contact that is linked to the Purchase order, is not available. Because the email address of the contact chosen on the PO header is copied to the PO header, the user is perplexed to find out that this email is not the one the Purchase order is sent to unless this same email is defined again in the contact info of the Vendor. I suggest a fourth way to email is added under the EDIT button of the print set up of a Purchase order, being 'Use the contact email address".
    • 37

      Add an approved purchase requisition line to an existing PO

      Suggested by Corey WarawaPlanned 3
      Category: Procurement and sourcing

      Adding an approved purchase requisition line to an existing unconfirmed PO would address the following scenarios:

      1. The Buyer overlooked the approved requisition line when the PO was created.

      2. A minimum PO amount is required to receive a discount with the vendor.

      The addition of this functionality would eliminate potential confusion with vendors as it would reduce the number of POs directed to them.  Furthermore, it would reduce internal effort required to receive the goods, process invoices and follow-up on any issues that arise.

      This function should be added to the Release approved purchase requisitions list page.  During the process, D365 would need to compare the accounting date on the requisition line to the PO.  If these differ, the user should be asked if they wish to proceed using the accounting date already on the PO header.

      Similarly, it would make sense to be able to “pull” an approved purchase requisition line into a PO.  The PO would have a function where the Buyer would see all the approved purchase requisition lines available to add to the PO.  The accounting date comparison and notification would be performed as identified above.

    • 35

      Add default underdelivery and overdelivery percentage fields to Procurement categories

      Suggested by Corey WarawaPlanned 1
      Category: Procurement and sourcing

      All PO lines created for procurement categories set the underdelivery and overdelivery percentages to zero since these cannot be defined on procurement categories.  Accordingly, the PO line for a procurement category must be edited each time it needs to be overdelivered or cancelled (underdelivered).

      Providing this configuration ability will allow organizations to improve PO receiving efficiency within their defined company tolerances.

    • 32

      Vendor onboarding approval workflow

      Suggested by Vinod KesavanPlanned 2
      Category: Procurement and sourcing

      Before the vendor can be transacted, it should be reviewed by finance related information like bank accounts, payment method in order to avoid fall over during generation of payment file

    • 31

      Ability to split a purchase requisition line to multiple purchase orders

      Suggested by Corey WarawaPlanned 0
      Category: Procurement and sourcing

      During the procurement process it is quite common to acquire the requested goods from different vendors - either external or intercompany.  In these situations, it would be very useful to be able to take a single approved purchase requisition line and create purchase orders for multiple vendors to fulfill the requirement.

      For example, a quantity of 100 items is requested in rush fashion using a purchase requisition.  During sourcing, the Buyer determines that a single vendor cannot supply all 100 items in a timely fashion.  Accordingly, they will source the goods from multiple vendors.

      Currently, the only options to handle this using standard D365 functionality are:

      1. Create a PO for one vendor from the approved requisition line; adjust the line amount; and manually create additional POs for the other vendors and quantities.

        • This makes it very difficult to trace the items from the purchase requisition to the PO for follow-up and audit purposes.

      2. Cancel the approved requisition line and ask the requester to create a new requisition with multiple lines representing the number of vendors that POs will be created for.

        • This is extremely inefficient and very frustrating for the requester as they have already followed the process to request the items and should not have to create another requisition simply to address the fact that the items need to be procured from multiple sources.

    • 29

      Vendor search functionality on RFQ

      Suggested by Sam AudooreNew 1
      Category: Procurement and sourcing

      When using the vendor search functionality on the RFQ form to search for vendors via criteria, this works fine the first time and I am able to transfer vendors from the list to my RFQ.
      However, when adjusting the search criteria and running the list again, I am not able to transfer vendors from the list to my RFQ.
    • 21

      Link a Purchase Order to a Purchase Agreement after the PO was created

      Suggested by Corey WarawaUnder Review 2
      Category: Procurement and sourcing

      A purchase order cannot be linked to a purchase agreement once the PO header has been created.

      This is problematic as a Buyer may not always know or remember that there is a purchase agreement in place with a vendor for certain items/procurement categories.  This is complicated even further when purchase agreements have been created for specific projects.  When this happens the Buyer needs to delete the existing PO and create a new one, ensuring that the purchase agreement is referenced.  This is very inefficient.

      It would be extremely beneficial to be able to link a PO to a purchase agreement after the PO has been created.  The function could filter the active purchase agreements based on the following criteria when attempting to create the link:

      1. Vendor account

      2. Project ID (if a Project PO)

      3. Item/Procurement Category

      Once the purchase agreement has been selected the user would then be able to update the PO lines to create the link as needed.

    • 21

      Enable intercompany with sales / purchase categories

      Suggested by Herman van NiekerkenPlanned 2
      Category: Procurement and sourcing

      In AX you can use the intercompany purchase / sales order for items only. Why not make it possible to also purchase / sell with a category in intercompany situations?

      The sales / purchase categories are already global, so it seems technically feasible.

      After the IC-connection between a customer and vendor is activated, currently you cannot use categories in the sales / purchase order anymore. You get an error that it is not allowed.