Create a Single purchase order for multiple vendor

Hi,

Is it possible to create a single purchase order for multiple vendors in ax 2012

  • Not really. What is the business scenario ?
  • In reply to Kranthi:

    Scenario is that end user want to send same purchase order to multiple vendor.
  • In reply to SalmanHafeez:

    Not a valid scenario.
  • In reply to Kranthi:

    The RFQ allows you to send a request to various suppliers to get quotes and then accept and convert to a purchase order, but if you want to purchase the same item from a different supplier that is a different PO - you have contract terms etc. that could be different, but fundamentally it is designed as a 1:1 relationship PO to Supplier.
  • In reply to AdamRoue:

    Is there is a possibility in case of child & parent vendors.i.e belongs to one vendor only have multiple accounts
  • In reply to Krishna Rao Gummadi:

    You still order from one, the supplier can supply from multiple accounts but that is not your decision to make
  • In reply to AdamRoue:

    I am suppose to ask Is there any setup required to configure multiple vendors, to process one invoice against multiple POs from different vendors. Is there is a default functionality that AX providing.
  • In reply to Krishna Rao Gummadi:

    You cannot process one invoice against multiple PO's to different vendors - only one is legally liable to give you the invoice - if you are getting ONE invoice they are not multiple vendors, they are the same vendor supplying from different points.
  • hi SalmanHafeez,

    As far as I know every purchase transaction only have one vendor, the system should not accept one transaction with multiple vendors.
  • In reply to portia2017:

    Hi,
    Thanks for response, I have done R & D on this and i found that we can attach vendors in request for quotation then generate purchase order from request for quotation
  • In reply to SalmanHafeez:

    HI SalmanHafeez

    Great! So you answer your own question. I think AX is very extensive so we need to explore the module(s) and forms and what are the functionality of menus and buttons in there.
  • Salman,

    I had a similar requirement when I was on a project in Europe. What I ended up advising the client is to create a generic vendor, such as 'General Vendor' and create a PO with with that vendor. When a PO needed to be created for a specific vendor, I had the user navigate to the PO header and change the invoice account field to the vendor they wanted to send the PO to. Even though I understand that invoice account field is used to send PO's to vendors who have parent/child relationships, this was the best work around I found that satisfied my clients requirements. I tested the impact this procedure by running vendor aging reports and etc. and it seemed to work fine. I suggest you test on your end to ensure the downstream impact is not affected using the procedure listed above.
Related
Recommended