882
Like
Share
ReportDear All,
In this blog post, I will discuss the approach and share the best practices to upload the master data in D365 Supply Chain Management.
Abstract: Managing master data from the legacy system to a new system is always a challenging task. This task can be manageable by using the Data Management Workspace available in D365 SCM. Before you export any data entity make sure to create your all setups and then enter few records manually for the customer, vendor, items, warehouses, and locations. These sample records will be exported and based on the sample data we can prepare the master data for all the entities.
What is Data Entity?
"A data entity is a conceptual abstraction and encapsulation of one or more underlying tables. A data entity represents a common data concept or functionality, for example, Customers or Vendors. Data entities are intended to be easily understood by users familiar with business concepts. After data entities are created, you can reuse them through the Excel Add-in, use them to define import/export packages, or use them for integrations."
Data Management - Import & Export
The data management workspace will be used to Import and Export the master data in D365. Below is the SS for the workspace, this workspace is available in the System administration module.
Export
Export is the process of retrieving data from a system using data entities. The export process is done through a project. While exporting the records from the system we can use the filter to Export a specific group of records, or we can export all the records already created in the system. The best practice is to create few records for the master data, setups, or journals in the system. Based on these exported records business users will prepare the master data in Excel.
First, we will create one Export Project for the entity "Released Products V2". As highlighted in the below SS, we can filter and export the records. If we do not select the filter for a particular set of items, the system will export all the line items.
Click Export now or schedule a batch job to export all the records.
Export Execution Summary
I have Filtered only one record for my testing. The system successfully completed the execution.
Now, download your file and prepare your master data for all the items. The sample record exported in the system will be helpful to prepare the item master data.
View the staging data
We can view the staging data. The item is exported with all the default fields created in the system.
Import
Import is the process of pulling data into a system using data entities. The import process is done through the Import tile in the Data Management workspace. Data can be imported either for individual entities or for a group of logically related entities that are sequenced in the correct order. The file formats vary depending on the type of import. For an entity, it can be an Excel file that is comma-separated, tab-separated, or text. For a data package, it is a .zip file. In both cases, the files are exported using the above-mentioned export process.
Create Import Project
The next step is to import the project. Select "Add File" and select the data entity "Released Products V2".
Make sure to Import your file template which you exported in the last step.
If you have few records you can select "Import now" or schedule a batch job to import the bulk of records.
Create Import Project
Import Execution Summary
Once the import is completed, you will get a message in the execution summary form "Succeeded".
Records updated.
Here, I am listing all the data entities which I have used during the implementation of my project.
|
D365 Supply Chain Management | Master Data Upload | Data Entities |
|||
|
SN |
Task |
Data Entity |
Details |
|
1 |
Product Category upload |
Product categories |
First, create the product categories. |
|
2 |
Product master creation upload |
Products V2 |
This will create a product master and also assign the categories with the items. |
|
3 |
Product translation upload |
Product translations |
Once all products are created, the next step is to upload the product translation. |
|
4 |
Released products |
Released products V2 |
This entity will be used to release all the items. |
|
5 |
Unit conversion |
Product-specific unit conversions |
Product number, from a unit (box) and to a unit(Pcs) and Factor(24). |
|
6 |
Barcode |
Item - barcodes V3 |
Upload the item barcodes. |
|
7 |
Physical dimensions |
Physical dimensions details by product |
This will be used to upload the item's physical dimensions. |
|
8 |
Trade agreements - Sales Price |
Open Sales Price Journal Lines |
First, create the sales trade price journal. Export the data entity. Enter the journal number in the Excel data entity along with item number, from and to date(YYYYY/MM/DD) format, currency, line number, and item-unit. |
|
9 |
Attribute assignment |
Product attribute values |
item number, attribute type name. Assign attribute type to item. |
|
10 |
BOM Header |
Bill of materials headers and versions V2 |
BOM ID, BOM Name, FG or SF Item, Site ID, Approve, Activate. |
|
11 |
BOM Lines |
Bill of materials lines V3 |
BOM lines will be imported and exported through this entity. |
|
12 |
Item physical dimensions |
Physical dimension details by product |
Item physical dimensions: Height, Width, Depth, and Weight. We can maintain the physical dimension for items in multiple UoMs Pcs, boxes, etc. |
|
13 |
Movement Journal |
Inventory movement journal headers and lines V3 |
We will use Inventory Movement Journal to upload the inventory data. First, create the same record for a movement journal. Export the sample record and enter your data in the Excel template. Finally, Import the template. |
|
14 |
Fixed locations |
Fixed product locations V2 |
Item fixed location for WAX. Enter Site, warehouse, and fixed location for an item in the data entity. Finally, upload the data entity. |
|
15 |
Sites |
Sites |
The site data entity will be used to upload all the sites, the default financial dimension for the site, and the address for the site. |
|
16 |
Create warehouse aisle |
Aisle |
This data entity will be used to upload the records for the warehouse aisles. |
|
17 |
Warehouse locations |
Warehouse locations |
Item locations for WAX, use location setup wizard it's smart option to create warehouse locations by zone and by location profile. |
|
18 |
warehouse zones |
Warehouse Zones |
Warehouse zones. |
|
19 |
Zone groups |
Warehouse zone groups |
Warehouse zone groups. |
|
20 |
Work pool |
Warehouse work pools |
Warehouse work pools. |
|
21 |
License plate |
License plates |
Warehouse license plates. |
|
22 |
Location profile |
Warehouse location profiles |
|
|
23 |
Warehouse worker |
Warehouse workers |
Mobile device workers. |
|
24 |
Warehouse Product filter code |
First product filter codes |
|
|
25 |
Customer master |
Customer V3 |
Customer master. |
|
26 |
Unit sequence group |
Unit sequence groups |
If you are using WAX, make sure to create the group for all default purchase units. Box, Carton, etc. |
|
27 |
Unit Sequence group lines |
Unit sequence group lines |
In the unit sequence lines sections, we will create the sequence from smallest to largest. (Pcs to Boxes) |
|
28 |
Number sequence |
Number sequence code V2 |
This will be used to export and import the record for the number of sequences. |
|
29 |
Create warehouse device users |
Warehouse device users |
This will be used to assign the menu items to the warehouse device users. |
|
30 |
Create warehouse work template |
Warehouse work template V2 |
Work template header will be created through this data entity. You need to manually add the query for the header. Also, the work template break will be added manually. |
|
31 |
Create work template lines |
Warehouse work template line |
Pick and put pair will be created through this data entity for the work headers. |
|
32 |
Vendors |
Vendors V2 |
Create few sample records for vendors and make sure to enter the data in all the relevant fields. Now export the records and prepare your master data for all the vendors. Finally, Import your file into the system. |
Conclusion and Recommendations
- Don't overthink, stick with basics, data entity is the solution and you can do it.
- Don't think you can create your own upload template for the item master data. If you start this task you will end up with "Released products V2. The custom solution requires a lot of effort for development and testing. Also, the solution fails while uploading the records for a hundred thousand items.
- For any data entity, the principle remains the same. First, create the sample records in the system and then export the data entity. Prepare your master data based on sample records.
- As a consultant, your job is to share the data entities with the customer. Also, explain all the relevant fields to the customer. Highlight the mandatory fields. Make sure to finalize your setups before you share the master data template.
- It's the customer's responsibility to share the master data in the correct template. Don't add any additional columns in the data entity. IT team must validate the data shared by the customer.
- The ownership of data validation lies with the customer, so don't manipulate the data shared by the customer. If there is any change required highlight the records and let the customer revalidate the data.
Good Luck!
If you need any help to manage the master data Export and Import related tasks in D365 feel free to contact, I am just a call away.
Regards,
Ali Danish
Microsoft D365 Business Consultant
M: +971554912688
*This post is locked for comments