Vendor Approval Workflow

(0) Share

Report

Posted on by Community Member

A client requires a workflow that initiates after a vendor is created within the legal entity, and requires that a particular user approve the vendor before that vendor is made available for transactions. They do not wish to use the "Vendor Requests" functionality. I do not see any such workflow within Procurement & Sourcing or Accounts Payable modules. Does AX 2012 R2 provide any functionality that covers this, or would a modification be required?

Thanks.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Verified answer

Ajit 8,755 on at

Like (0)

Report

This is not available out of the box but it would be easy to create one.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,156 Super User 2025 Season 2 on at

Like (0)

Report

Hi Stennant,

Can you inform why the customer does not want to use the Vendor requests? Is it because of available fields or maybe the use of enterprise portal to create a new request? Or something else?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

They do not wish to use vendor requests because they only have one vendor for each product that they sell no matter what, and the vendor approval is just for proofing new vendors when they are created and viewing changes to key fields. All of their purchase orders are processed within a third party software that we are integrating, so the vendors are often created within AX after the purchase order has been created in the third party system.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,156 Super User 2025 Season 2 on at

Like (0)

Report

Hi Stennart,

Thanks for the explanaition. I have seen this feature being rejected only because there was no creation form in AX. So they decided to build complete new functionality in stead of just a new form in AX.

I can imagine with your explanation why they decided this.

Was this reply helpful? Yes No
Suggested answer

ZvikaR 168 on at

Like (0)

Report

Depending on the complexity of the approval process, you might be able to provide a solution without building a workflow.

In a previous project, we created a simple code on the vendor form, causing the status of the vendor to change into "On Hold" every time a new vendor is created or an existing vendor is modified.

Than we restricted, using security, who can remove the vendor from being "on hold'

For the customer's simple requirements, that was good enough.

Was this reply helpful? Yes No
Sajjad_00 477 on at

Like (0)

Report

Dears,

can you share your customization which you did. I need the same. in my case also the user are duplicating the Vendor and Customer also where I need to put on-hold before they can utilized for any transaction.

this will be for a new and also for existing one if modified.

additional if there is anyway to trace down what the change is happened to the record in case of existing record will be much better.

Was this reply helpful? Yes No