·
2 min read

Step-by-step Walkthrough of the Vendor On-boarding Process

 

The Vendor on boarding process supported by workflows was introduced in AX2012.

This blog post guides you through the process from the point where an employee creates a vendor request to on-board a new vendor and to the point where the new vendor is introduced in AX together with a contact person who is a registered user in AX.

Preparation:

Setup 3 workflows – straight forward with one approval step.

System administration: User request workflow.

Procurement and sourcing:

Vendor add application WF  Vendor add justification WF

clip_image002[19]

clip_image004[19]

e.g.

clip_image006[15]

Start the workflow processor from AOT forms (for demo purposes).

clip_image008[12]

Set up External roles – (System administration/Setup/Security/External roles.

clip_image010[12]

Under System administration/Setup/Enterprise Portal/Enterprise Portal parameters.

Set up the default authentication method for authentication of the vendor user account.

clip_image012[8]

 

 

The process:

Initiate request from ESS

http://<machine>/sites/DynamicsAx/EmployeeServices. To initiate the request, you must have a role as no less than an Employee and be associated with a person/worker.

(You can also initiate the request from the Unsolicited vendor registration page).

clip_image014[8]

Create a new vendor request. Make sure you are in the company where the workflows are defined.

Add initial information about the new vendor. Name and contact person.

clip_image015

Create the request and make sure you enter an address for the vendor and an email for the contact person on the request.

clip_image017[8]

Submit the vendor request.

clip_image019[8]

The request now has the status Request submitted:

clip_image020

Open the AX32 client as the user you have assigned in the workflow to approve the request.

Navigate to the Vendor request pending approval list page.

clip_image022[6]

The request has the status Request pending approval.

Open the request, and approve it:

clip_image024[6]

If you go to the Vendor requests list page, the request now has the status Request pending complete.

clip_image026[6]

Now go to Prospective vendor user requests where the user request has the status Pending approval.

Open the record:

clip_image028[6]

Depending on how you have set up your user request workflow, you can take different actions. I have set it up to manually provision the user.

clip_image030[6]

Go to system administration, create a new user, and assign the role Vendor prospect (external).

clip_image032[4]

Furthermore create the relation to the actual person (Peter Nielsen) and to the Prospective vendor (New vendor XXX).

clip_image034[4]

When you have set up the user, approve the user request for the prospective vendor.

clip_image036[4]

The request now gets the status Completed.

clip_image037

Go to the Vendor request page. The vendor request now has the status Vendor invited. This is based on the approval of the user request.

clip_image039[8]

Now you can log in as the NEW user, and open the Vendor registration page for the prospective vendor:

Add the information. If a questionnaire was set up – you will be prompted to answer the questions of the questionnaire.

clip_image041[8]

When finished – submit the registration form (to the Vendor add application workflow).

clip_image043[6]

Go back to the AX32 client as the user that is set up to approve the request. Navigate to Vendor request pending approval and find the request. The request has the status Application pending approval.

clip_image045[6]

Approve the request. This will create the vendor.

clip_image047[6]

Now you can check the vendor list and see that the vendor has been added – and he also has a contact person, Peter Nielsen, which is the person that completed the registration form J

To view contact persons, go to the Vendor card.

A user will automatically be given new security roles:

– Vendor (external)

– Vendor portal administrator (external)

The roles are derived from the definitions that you set up for the external roles as a preparation.

clip_image049[6]

And now a relation is established to the new vendor record.

clip_image051[6]

Done J