Vendor Master data management functionality forms part of the GRC module.
With Standard D365FO, the user can add a vendor to another legal entity form any legal entity.
With Vendor Master data management from the GRC module, the user can only release a vendor (“Add vendor to another legal entity”) from the one legal entity that is specified as the Master data company in the parameters. The functionality to release a vendor in all the other legal entities, is disabled.
With Standard D365FO, when the vendor is created it is created according to the destination legal entity numbering sequence. The result is that the same vendor will have different vendor numbers in the different legal entities.
With Vendor Master data management from the GRC module, when the vendor is created the user can choose to create this vendor with the exact same vendor account number in the destination legal entity. If this vendor account number already exists in the destination legal entity, the user will get an error message. With this functionality the user will have to rename the vendor with the same vendor account number in all the different legal entities where it is used.
With Standard D365FO, when the vendor is created in the new legal entity only the global address book (party) information is copied to the destination legal entity. Apart from this data, the only other information that can be specified is the Vendor group, currency, and vendor hold.
With Vendor Master data management from the GRC module, you can specify the additional fields that must be copied from the source to the destination legal entity on the parameters setup form.
Task management lets you create tasks that must be completed to hire (onboard), terminate (offboard), and transfer (transition) employees, vendors, or customers. Task management uses the concept of checklists. A checklist is of a list of onboarding, offboarding, or transition tasks. Task management uses checklists to group tasks together, and to assign them to individuals or groups. The checklist functionality for onboarding, offboarding, and transitions is similar.
Go to: Human resources > Task management > Onboarding checklists
On the Action pane, click on the New button
Enter a Name for the checklist
Enter a Description for the checklist
In the Process type field, select Onboarding from the dropdown list
Select the name of the Owner of the checklist from the dropdown list
Select the applicable Calendar for the checklist
Expand the Tasks Fast tab
Click on the New button
On the Create a new checklist task dialog:
Enter the Task
Enter a Description for the task
Move the Vendor slider to Yes to indicate that the task involves onboarding of a vendor
Click on the dropdown arrow in the Task link field and select one of the following options:
Menu item (then select the relevant menu item from the list)
URL (then type the URL in the field provided)
Worker details (then select the relevant actions from the list)
Click on the OK button
The Vendor and Customer sliders to be used for SCM trading partner related onboarding and offboarding tasks.
Do note the option to specify a Task link.
This could be to direct the users to a specific form (in D365) that needs to be completed as part of the on-boarding option or an external web site (maybe SharePoint to see if all required documents are uploaded to a specific documents library).
Go to: Human resources > Task management > Offboarding checklists
On the Action pane, click on the New button
Enter a Name for the checklist
Enter a Description for the checklist
In the Process type field, select Offboarding from the dropdown list
Select the name of the Owner of the checklist from the dropdown list
Select the applicable Calendar for the checklist
Follow the steps for adding tasks to the checklist as described above
User will then be asked if they want to create a formal "checklist". On Yes a To-do list for the worker in the setup (step 2 above) will be visible on the D365 F&O home screen.
For Overdue task items a vertical red line will be displayed.
Click on the relevant task on the to-do list
In the Task form Details Fast tab, users can see the status of the task.
On the button strip, click on the Change status button group and choose the new status. If "Completed" it will disappear from the to-do list
On the button strip, click on the Reassign button group and choose new "owner" for the task; it will disappear from the to-do list for the logged in user
The Task link field is usefull. If other forms (inside Dynamics) or external web sites are linked users can use the hyperlink of the value inside this field to first complete something before marking this task as complete.
On the Action pane, under the Vendor tab, click on the Add vendor to another legal entity button
On the dialog, complete the following fields:
Company – Select the company that this vendor must be created for
Vendor group – Select the relevant vendor group for the company
Currency – Select the default currency for this vendor
Vendor hold – Specify the vendor hold for this vendor
Include additional fields from parameters - Add additional vendor fields to populate on the copy action. These are the fields specified on the parameters (GRC added functionality)
Force consistent vendor number across legal entities - Force consistent vendor number from the Master data company across legal entities (GRC added functionality)
This button will only be available in the Master data company selected on the parameters. All other companies will not have this functionality
¶ Step 7: Runnung the Vendor certificate batch alert
Go to: Purchase ledger > Periodic tasks > Vendor certificate batch alert
On the Vendor certificate batch alert dialog, enter a number in the Days field
Alert to be sent as overdue (+ sign) and pre event notification (- sign). O will send a message only once for new records created. 1 or -1 for example, will send multiple times. O will ignore any dates
The global address book is a centralized repository for master data that must be stored for all internal and external persons and organizations that the company interacts with. The data that is associated with party records includes the party's name, address, and contact information. Other details vary depending on whether the party is a person or an organization. Each party record is assigned to a party, and each party can be associated with one or more party roles in a company. Party roles include customer, prospect, worker, user, vendor, competitor, applicant, and contact. For example, the organization party First Up Consultants, can be associated with customer, business relation, and vendor roles in the CEE company, and can also be associated with the vendor role in the CEU company.
Here are some of the benefits of this shared data:
The data shows the relationships that people and organizations have with other areas of the company. The relationship between two organizations changes when one organization has multiple roles, such as vendor and customer. Communication between the two organizations also changes. There might be special agreements that can be negotiated to encourage a closer partnership with the other organization.
Setup and maintenance are easier. For example, when an address changes, the update must be made in only one place. All the other associated records are updated automatically.
¶ Step 9: Release a product/item master to legal entities
This procedure walks through how to release a product or product master into one or more legal entities. The master Data Company used to create this task is MDC.
Go to: Product information management > Products > Products
Select the required products
On the Action pane, click on the Release products tab
The selected products will be listed on the next form