![]() Product masters are used as generic products that hold the definition and rules that determine the behavior in business processes.For these products, one row is created in the Product table, and one row is created in the msdyn_sharedproductdetails table. Products with subtype product are products that are defined by themselves.To keep track of all products (released and not released), the Global products table is used.īecause the product is represented as a SKU, the concepts of distinct products, product masters, and product variants can be captured in Dataverse in the following way: Each released product will have its information in the mentioned tables (Product and Shared Product Details). The combination of these two tables is used to define the product according to the concept of the stockkeeping unit (SKU). Whereas the first table contains the definition of a product (the unique identifier for the product, the product name, and the description), the second table contains the columns stored at the product level. In this model, the product is represented by the combination of two tables in Dataverse: Product and msdyn_sharedproductdetails. The product tracking dimension group represents the method used to track the product in inventory. The product storage dimension group represents the method used to define the placement the product in the warehouse. The msdyn_sharedproductdetails table contains the columns from finance and operations apps that define the product, and that contain the product's financial and management information. Msdyn_productspecificunitofmeasureconversions Product bar codes are used to uniquely identify products. This concept is migrated to Dataverse to keep data consistent. The Shared product style table indicates the styles that a specific product master can have. The Shared product size table indicates the sizes that a specific product master can have. The Shared product configuration table indicates the configurations that a specific product master can have. The Shared product color table indicates the colors that a specific product master can have. The product dimension group defined which product dimensions define the product. Msdyn_productspecificdefaultordersettings They specify which category is used in each role the product category role table is used. ![]() Product hierarchies can be used for different roles in Dynamics 365 finance and operations. The category hierarchies are available in Dataverse using the Product category hierarchy table. You use product hierarchies to categorize or group products. To assign a product to a category the product category assignments table can be used. The following table shows the mappings.Įach of the product categories and information about its structure and characteristics are contained in the product category table. ![]() It includes individual products (products with subtype product) and the product variants. The Product table contains the columns that define the product. The all products table contains all the products available in finance and operations apps, both the released products and the non-released products. As the following table shows, a collection of table maps is created to sync products and related information. Product information contains all the information related to the product and its definition, such as the product dimensions or the tracking and storage dimensions. Although you can customize it, it's at your own risk, as Microsoft doesn't recommend this approach. However, the product infrastructure has been made open to make it bi-directional if required. The dual-write table maps for products have been designed to flow data one-way only, in near-real time from finance and operations apps to Dataverse. These two product data models have been integrated in Dataverse as shown below. Here is the product data model from finance and operations apps. Here is the product data model from Sales. The unified product experience brings the integrated product data model in to Dataverse, so that all application users, including Power Platform users, can take advantage of the rich product data coming from finance and operations apps. Businesses who use an external Product Lifecycle Management (PLM) system for sourcing the product data can channelize products from finance and operations apps to other Dynamics 365 apps. This is because these apps provide a robust product infrastructure complemented with sophisticated pricing concepts and accurate on-hand inventory data. When a business ecosystem is made up of Dynamics 365 applications, such as Finance, Supply Chain Management, and Sales, businesses often use these applications to source product data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |