Advanced Vendor Collaboration and Vendor Onboarding in Dynamics 365 For Finance and Operations, Enterprise edition
It has been quite sometime i have not written here. Last few months were very busy with several things and that did not allow any time to spend on blogging. I finally managed to get some time here!!
In one of my earlier posts, I elaborated some of the functionalities of the Vendor collaboration/Vendor self-service feature of Microsoft Dynamics 365 for Finance and Operations – Enterprise Edition and what was coming in future releases. With the Fall release (Version 7.3), Dynamics 365 for Finance and Operations has much more to offer to automate vendor self-service and collaboration, specifically around the vendor user and organization onboarding aspects.
In this post, lets take a look at some of those new features, specifically in the vendor onboarding area.
The diagram below shows an overall representation of how the data flows from a Prospective Vendor to an Approved vendor in D365FO.
Let’s now dig into some of the finer details of the processes and steps underneath each of these steps in the vendor onboarding process.
ProspectiveVendor shows interest to become a potential vendor: Before an organization or individual wants to become a vendor for your organization, they are referred as “Prospective Vendors”. They can apply to be a vendor for your organization either via a website you may have, with anonymous access, or they can apply via a contact at your organization. If they come in through your website, you can have an OData integration with D365FO, to send the prospective vendor’s data into D365FO. Alternately, you can also use Data Management Framework to import the prospective vendor data periodically into D365FO.
After the initial basic data for the perspective vendor comes into D365, it will appear in Prospective Vendors registration under Procurement & Sourcing > Vendor collaboration requests.
Procurement Personnel from your organization reviews the details and initiates the vendor invitation process:
Before a procurement personnel from your organization reviews these requests to initiate the vendor invitation process, lets take a look at the workflow that is set up behind the scenes to do all the heavy lifting.
Under System Administration > Workflow > User Workflows, you can set up workflows for adding, modifying or inactivation of a new prospective vendor/existing vendor user. For a new prospective vendor user, the workflow provides your various options to fully control the new user provisioning in Azure AD and new user creation in D365FO.
Take a look at the screenshot below which shows this workflow.
To initiate the invitation process for the new prospective vendor, the procurement personnel will select the required user and review the details. If they decide to proceed with initiating the invitation process, they click the Invite User button.
At this point, the Processing status of the vendor registration request changes to “User requested“. This means a request for setting up a new user account in Azure AD and in D365FO has been initiated in the workflow.
As soon as the user creation request is creation, the personnel setup in the workflow for this will get notified and will process the request further. If you notice the screenshot of the workflow above, the first step in our workflow is to review and approve the user request even before the Azure AD and D365FO user accounts are created.
The Personnel responsible goes into the user request and reviews the details to approve it.
The next step in the workflow is to set up the B2B user account in Azure AD. You can use the manual task within the workflow and assign it to the required person, who then can download the external user setup CSV file for import within Azure AD.
Alternately, you can use the automated task for provisioning the Azure AD B2B user account.If you chose to use the automated task, you need to make sure to complete the below setups.
- Register the D365FO app within Azure AD in Azure portal.
- Complete the required setup for the API permissions for Microsoft Graph for the D365FO app. The automated task of the user setup workflow will invoke this to provision the user account in Azure AD.
- Setup the Client ID, Application Keys within D365FO B2B invitation configuration page of D365FO.
With the above setup done, the automated task will provision the Azure AD user for the vendor user automatically. In the next step of the user setup workflow, you can set up automated tasks for provisioning the user account within D365FO and also send the email notification to the vendor with a URL link to D365 for signup and registration. You can set up an email template and use (%portalURL%) placeholder in the email message, which will automatically include the URL of D365FO, when it sends the email notification to the vendor.
In this demo, the prospective vendor i added was John Smith whose email id was firstname.lastname@example.org. Since i had done all the setups above, ( (John Smith, the vendor) got the email notification with a URL for sign up.
Prospective vendor signs up to D365 and completes registration Wizard:
Now, it is time for the prospective vendor to sign up and complete the registration wizard and provide additional information about their organization.
When the vendor logs in to D365 by clicking the URL in the email invite, they are directly taken to a registration wizard, which appears as shown in screenshot below.
The vendor selects the Country/region first in which they operate in. In this case , i selected USA.
On the next few screens, vendor enters their business information and all necessary details as shown in screenshots below.
You can also configure and assign predefined questionnaire and assign it to the vendor to answer and you also let them select procurement catalog.
New Vendor request created in D365 for review and approval:When done, the vendor submits all the information at the end of the wizard.
This create the new vendor request in D365FO, which will then be reviewed and approved by a procurement or AP person of your organization. Procurement personnel can navigate to Procurement and Sourcing > Vendor collaboration > Vendor requests to see these.
New vendor details reviewed and approved:
The Procurement personnel then completes the review process of the new vendor request and upon confirmation, the new vendor record is automatically setup in the Vendor master. After that, the vendor can have full access to the vendor collaboration portal and they can communicate with your organization in real time on purchase orders, invoices, consignment inventory, RFQs and responses, bidding and more.
That essentially completes the overall vendor onboarding process in D365FO. Stay tuned for more on this.
Published at Fri, 16 Mar 2018 02:11:21 +0000
Take advantage of configuration data templates for seamless data import and export management in your Dynamics 365 For finance and operations implementation
The Data Management Framework of Dynamics 365 For Finance and Operations – Enterprise Edition provides advanced data management capabilities, which makes the overall data export and import really seamless easy, for both standard Dynamics 365 data entities, as well as any custom entities that you might have developed for your business requirements. This framework provides an easy to use front end interface for data export and import management, so that regular pro-users of Dynamics 365 can interact with it, without requiring advanced knowledge of development and database.
In this post today, let us discuss about one of the features of this Data Management framework called the “Data Templates“, which will help you accelerate the data configuration and export/import management in your Dynamics 365 Implementation.
So, what are these data configuration templates ? One of the things you would have always done in every D365FO (Dynamics AX earlier) implementation, is probably use an excel spreadsheet to keep track of setup and master data configuration checklist and their sequence of import. While this works, it also requires extensive manual tracking, supervision and may lead to lot of human errors and mistakes.
Data configuration templates in D365FO are basically a predefined list of data entities for each module area, which are sequenced , so the data import will be processed in correct order automatically. This reduces human error in the data import sequence, save a huge amount of time in data import/export.
The templates are sequenced using Units, levels and sequence numbers and predefined dependencies between data entities. For example, before you import/upload your customer master data, you need to make sure all the number sequences formats, customer groups, payment terms etc. are imported prior to that. The data configuration templates addresses this and takes care of sequencing.
Let us now understand what is underneath these data templates and how these are managed in D365FO.
- Microsoft started releasing these predefined data templates with the July 2017 update and these are right now made available directly within D365FO. From home page of D365FO, Navigate to System Administration > Data Management Workspace > Click Templates tile and click the Load default templates button. This will load all the default templates which are made available by Microsoft.
Note: In future, these will be made available in the shared asset library of LCS(Lifecycle Services), just like other assets such as the Power BI report models, Software deployable packages etc.
- You can use these out of the box templates, modify them to meet your business requirement, or you can even create your own templates and define the entities under it. For example you might have customized D365FO to meet your business needs and you might have created various custom data entities for this. So you can create your own templates and include those entities.
- How are these entities sequences within a data template for processing? The “Execution unit”, “Level in execution unit” and “Sequence” fields under the Entities tab of the templates defines how the entities are sequences for processing.
- Execution Unit: Entities that have different units are processed in parallel.
- Level in execution unit: Entities that have the same level within an unit are processed in parallel.
- Sequence number: With the same level, entities are processed according to their sequence numbers.
Note: At some point in future, Microsoft will make it possible for the sequencing to happen automatically when you add entities to a template and will they will try to provide templates for every standard D365FO configuration and setup.
- The Module, category and Tags represent the entity category or classification for better understanding. Module represents the actual module name of D365 to which the entity belongs, Entity category shows if the entity is related to setup data, reference data or master data and the tags shows additional information tags.
- There are other miscellaneous features on this templates so that you can export and import templates, Open the list of entities within a data template in Excel to make changes to Units, levels, sequences, module, tag etc., or you can even create the templates from a data project.
Now, let us see how we can use these data templates (Predefined or custom created) in an actual Data project for export or import.
- Navigate to System Administration > Data Management > Click Import tile.
- Enter a name for the project and click Save. Now click “Apply Template” button. You will see all your data templates that you can select and add them to the data project. You can add more than one data template. Let us say I want to use the GL-Shared data template to load all the data for the GL shared area. I can select that and select preferred source type (EXCEL, CSV etc.) and click OK button.
- Notice here that all the data entities that were part of the General Ledger-Shared data template are automatically loaded and all the level and sequencing of these entities is also inherited from the template setup. Now, you can just upload the excel/source data files for all these entities and schedule the data project to run. It will run and automatically process the entities in the correct sequence as per the definition in the template.
This is certainly a huge time saver and you don’t have to select individual entities and import them one by one remembering their sequence.
- Similarly, you can use the templates for exporting too, so that system will automatically provide all the source files for each module, depending on the data template you selected in the project.
- As an example, I have exported the same GL Shared template in a data project and it exported all my relevant data entities with more than 500 records within few seconds.
- I can now download these packages and see the data on the files. See screenshot below.
I find this feature very useful and this will help save significant time in data export/import and will also enable users who are not experts of the system to seamlessly export and import data for all required modules by leveraging these templates. This is also a great step towards standardizing data configs as much as possible, so that customers don’t have to reinvent the wheel in every implementation.
That’s it for this post. Stay tuned !!
Published at Sun, 05 Nov 2017 02:19:57 +0000