Managing Item Hierarchy Structure

This document explains item hierarchy structure.

There are several requirements on user defined item hierarchy and product catalog functionality. The main requirements are from two areas:

  • E-business is focusing on product catalog.
  • Distribution is focusing on item hierarchy.

Product catalog is not the same as item hierarchy. One difference is that item hierarchy is focusing on companies' internal business structures, while product catalog is a way to present information between customers and suppliers.

The scope for this design is item hierarchy structure, a flexible way to search items and new term for statistics and control.

One reason why the product catalog is excluded from this design is that the product catalog logic most likely will be placed on the web server not within the ERP application it self.

Outcome

  • An Item Hierarchy Structure is created. Vertical and a horizontal search can be done.
  • Item hierarchy structure can be displayed in some programs.
  • Item hierarchy structure is valid for the whole company.

The main use is to give possibility to search items in a structured way and to have statistics on other terms than we have today. Item hierarchy fields be used as a path for user-defined tables, and also to create the contents of user-defined files:

The following tables are updated:

  • The Item master MITMAS table is changed.
  • The System parameters CSYPAR table is changed.
  • The Item hierarchy definitions MITHRY table is new.

Before you start

Items are registered as described in Create and Connect Item to a Warehouse Structure.

Description

The main use is to allow to search items in a structured way and to have statistics on other terms what we have today.

Structure

  • Item Group Structure

    This diagram shows an example of item group hierarchy. Note the difference between horizontal (search groups) and vertical (hierarchy ID) search.

    The vertical search is based on the fact that each hierarchy level (Hier lvl) is represented as an iterative identity field that is repeated for each level. The approach is a drill down approach.

    Each hierarchy level could also be unique. This makes it possible to do a horizontal search.

    Since the item hierarchies and search groups are stored on the item master can this information be used in views from different programs like item toolbox (MMS200), item statistics (MMS090) etc.

  • Some definitions

    Item Hierarchy = A hierarchical search patch that reflect a companies business in a structure way. A drill down approach, called hierarchy id in the data base.

    Search group = Could be used as a complement to do a horizontal search.

    Hierarchy level = Defines on which level a hierarchy entity is defined. Value 1 to 5 is permitted. One is the top level.

    Upper level = Defines the level above, used on keys for drill down purposes.

    Upper level identity = Defines the hierarchy identity for the level above.

Workflow in M3

  • Field length for item hierarchy fields is set in 'Settings - Item Hierarchy' (CRS704).
  • Allowed hierarchies and to build the vertical relations are defined in 'Item Hierarchy. Open' (MMS021).
  • How to build the horizontal relations and the allowed search groups are defined in 'Search Group. Open' (MMS022).
  • Item is connected to the item hierarchy structure in 'Item. Open' (MMS001), on the M panel.
  • Item hierarchy structure can be displayed in some programs if an appropriate view is defined, and be selected for search paths for user-defined tables, and also to create the contents of user-defined files.
  • In the warehouse area can item hierarchy structure be displayed in following programs, by creating a user defined view.

    Field group Program

    MM200 Item toolbox (MMS200)

    MMKV1 Item toolbox (MMS200)

    MMIT1 Views supply chain (MWS051)

    MMPV5 Stock transactions (MWS070)

    MWPV2 Balance id (MWS068)

    In following programs can item hierarchy fields be used as a path for user-defined tables, and also to create the contents of user-defined files:

    Field group Program

    • MMAD1 Allocation control table (MMS123)
    • MMAD2 Allocation control location (MMS124)
    • MMAD3 Joint delivery rules, groups (CRS016/MWS125/E)
    • MMAD4 Joint delivery rules (CRS016/MWS125)
    • MMAD5 Cross dock location matrix (CRS016/MWS130)

This diagram shows the files and programs involved in the described workflow.

Related topics