Defining additional information in Datasets

In DMP, you can extend the processes to incorporate various types of additional information into DMP and link this information to datasets.

This table shows the process for this type of additional information, which is similar in DMP:

Action Description
Using the dataset properties to define the appropriate Extra Key, Text Keys, or Numeric Key to store the information. Solution configuration done once in dataset properties, defining the Attribute, Extra Key, or Text/Numeric Key
Defining the Attribute, Extra Key, or Numeric Key, along with the link relationship and target dataset. For Attributes, go to dataset properties and ensure the attribute is enabled.
Defining how to retrieve the data, such as using the Import M3 Data to call APIs. Repeating operations best placed in a workflow to run every cycle
Updating dataset with data retrieved.

Examples

  • M3 Assortments
    • CRS105MI.LstAssmItem: Lists assortments related to Items, which you can link if the Dataset contains the Item Key.
    • CRS105MI.LstAssmCust: API list all customer records that have the specified assortment. You can link this additional information if Customer is a key of the dataset.
  • Item
    • MMS200MI.GetItmBasic, MMS200MI.GetItmPrice, MMS200MI.LstItmPrice, and so on.
    • Extra Key such as Grouping/level fields or Attribute columns. For example, Hierachy, User-defined field, or Responsible.
    • Numeric Key such as Volume, Weight, Danger indicator, Sales price, or Purchase price.
  • Warehouse and Item
    • MMS200MI.GetItmWhsBasic, MMS200MI.GetItmWhsBal, MMS200MI.LstItmWhsByWhs, or MMS200MI.LstSumWhsBal
    • ABC methods and Class, Safety stock, Maximum stock, Order quantity, Minimum order quantity, Maximum order quantity, Supplying warehouse, Shelf life, Catch weight approved on hand balance, or Reserved quantity