Style and SKU Creation

Style and SKU Creation is an M3 Experience Designer application that helps product managers in the fashion industry to simplify and streamline the process of creating and managing styles and SKUs within Infor M3.

The application is designed to reduce complexity, improve efficiency, and minimize errors by consolidating multiple steps and programs into a single, intuitive interface. This feature enables users to create styles and their variant SKUs faster and with greater accuracy, which increases productivity and improves the overall user experience.

User stories

Product managers use a centralized application to create and manage styles and SKUs. This application streamlines the process by reducing the number of steps and systems involved, enabling faster task completion and minimizing errors in style and SKU creation.

M3 Business Engine configuration

These M3 Business Engine configurations are required to get the Style and SKU Creation application to work.

  • The facility used when creating a new style is the facility set up on the user in 'User. Open' (MNS150). For proper creation of styles, ensure to have a facility specified on the user.
  • The application works only for styles that have this setup on their item types: color is sequence number 10 and size is sequence number 20.
  • The item template related to the item type used when creating a style must have been added to the warehouses that must be created.
  • Auto flagging must be used on the item type for the related warehouses.
  • 'Stock Msg Partner. Open' (MMS865) must have been set up using FSH as the message type and partner.
  • 'Settings - Item Import' (MHS262) must have been set up using the value 0-'Create all' for the fields Lim itm/whs crt, Limit i/whs STY, and Lim itm/whs SKU.
  • The Style info parameter must be switched on in 'Item Type. Open' (CRS040).

See specific configuration per component in the Components section.

Application authorization

To access and run the Experience Designer application, you must be authorized to the M3 Business Engine functions and API transactions used by the application.

This table shows the functions and transactions that are used by the Style and SKU Creation application.

Function or API Transaction Information Category View
CRS040MI LstItmTypes
CRS912MI LstSeason
LISTMI ListDataAsCSV M3_LIST_MITMAH M3_01_01
MHS001MI AddIntItmMst
MMS016MI Update
MMS016MI Get
MMS017MI List
MMS200MI SearchItem
MMS200MI UpdItmBasic
MMS200MI UpdItmFac
MMS200MI GetItmPrice
MMS200MI GetItmFac
MMS200MI GetItmBasic
PDS056MI List
PDS061MI CreateSKU
PDS061MI AddSKUOption
CRS040MI LstItmTypes
CRS912MI LstSeason
PDS061MI LstSKUProposal

Limitations

  • The application does not contain images but it uses Infor Business Context information. Use the Smart Panel with widgets to display images and documents related to the styles as a complement to the application.
  • You cannot create a style using an item type that supports manual override. You must work with item types that do not support manual override.
  • The app only works for styles using only these types of features: color and size.

How to use the application

Given that the setup in M3 is correct, to create a style, click the Create new style button in the application header. See the section Style Creation – How To Use the Application for details on how to create styles.

To create a SKU:
  1. Select a style in the index list. The style is the base for this application.
  2. Create changes to season values in Season Settings and save the changes.
  3. Select all the colors, sizes, and season to include in the SKU. To select multiple colors and sizes, press Shift or Ctrl and click the lines with the mouse.
  4. Click the Create SKU proposals button.
  5. Click the Refresh button in the Preview Selected Options component to view all proposals.
  6. Click Confirm all and add to style to complete the SKU creation.
  7. Click the Refresh button in the SKU component to view all SKUs.

See more details on the next sections of how to use the application.

How to use the application - Index List and Details Header

The Style and SKU Creation application starts with an index list. The list displays the styles and some data connected to styles. It uses the API transaction MMS200MI/SearchItem with input CHCD=2 to list the styles.

When a style is selected in the index list, the other fields in the application are filled with data.

The details header section shows style-related data. It uses the API transaction MMS200MI/GetItmBasic and the selected style as input to the transaction.

How to use the application - Application Header

The application header contains three buttons: one button to edit the style selected in the index list, another to open the Style Creation application in a modal window, and the third button to open the Style Overview application.

The button that modifies the style opens a dialog that enables the user to change style values. It uses the API transaction MMS200MI/UpdItmBasic and data from the dialog as input to the transaction.

How to use the application - Create New SKU

The Create New SKU group pane contains a form that shows season settings, a data grid that lists colors to choose from, a data grid that lists sizes to choose from, a data grid that lists seasons to choose from, and a button that creates the SKU proposals. All components are populated with data when a style is selected in the index list.

The form that shows the season settings uses the API transaction MMS016MI/Get to display data and the selected style as input to the transaction. It also uses the API transaction MMS016MI/Update to update the data and the season fields in the form as input to the transaction.

The data grid listing colors uses two API transactions that run right after each other: MMS017MI/List and PDS056MI/List. When the data grid is loaded, the two transactions run automatically.

  1. API transaction MMS017MI/List is run with this input:
    1. Style number (STYN): style number retrieved from the index list.
    2. Sequence number sorting (SQNU): 10
  2. If transaction runs successfully, it generates a feature (FTID).
  3. This feature is used as input to the other transaction.
  4. PDS056MI/List is run with this input:

    Feature (FTID): feature coming from MMS017MI/List.

  5. If both transactions run successfully, colors are listed in the data grid.

The data grid listing sizes uses two API transactions that run right after each other: MMS017MI/List and PDS056MI/List. When the data grid is loaded, the two transactions run automatically.

  1. MMS017MI/List is run with these input:
    1. Style number (STYN): style number retrieved from the index list.
    2. Sequence number sorting (SQNU): 20
  2. If the transaction runs successfully, it generates a feature (FTID).
  3. This feature is used as input to the other transaction.
  4. PDS056MI/List is run with this input:

    Feature (FTID): feature coming from MMS017MI/List

  5. If both transactions run successfully, sizes are listed in the data grid.

The data grid listing seasons uses CRS912MI/LstSeason to display data.

The Create SKU proposals button creates SKU proposals. It uses one API transaction that runs with two different inputs: PDS061MI/AddSKUOption.

When the button is clicked, the transaction runs automatically with different inputs. The user does not need to change any input.

  1. PDS061MI/AddSKUOption is first run with these input:
    1. Option (OPTN): option retrieved from the data grid listing colors.
    2. Feature (FTID): feature retrieved from the data grid listing colors.
    3. Style number (STYN): style number retrieved from the index list.
  2. The transaction is run for all the selected colors.
  3. Then, PDS061MI/AddSKUOption is run with these input:
    1. Option (OPTN): option retrieved from the data grid listing sizes.
    2. Feature (FTID): feature retrieved from the data grid listing sizes.
    3. Style number (STYN): style number retrieved from the index list.
  4. The transaction is run for all the selected sizes.
  5. If both transactions run successfully, the SKU proposals are generated.

How to use the application - Preview Selected Options

The Preview Selected Options data grid lists the available SKU options. The list is filled with data when a style is selected in the index list, and when its own refresh button has been clicked. It uses PDS061MI/LstSKUProposal and the selected style as input to the transaction.

Refresh the list after creating the SKU proposals to be able to see the proposals in the list.

How to use the application - Confirm All and Add to Style

The Confirm all and add to style button properly creates the SKUs listed in the Preview Selected Options data grid. It uses PDS061MI/CreateSKU with these input:
  • Style number (STYN): style number retrieved from the index list.
  • Season (SEA1): season retrieved from the data grid listing seasons.

How to use the application - SKU

The SKU data grid lists the SKUs connected to the style in the index list. The list is filled with data when a style is selected in the index list, when its own search fields are used, and when its own refresh button has been clicked. It uses LISTMI with these configuration:

  1. Information Category: M3_LIST_MITMAH
  2. View: M3_01_01
  3. Search: yes
  4. Input to the search query:
    1. Company (CONO): company retrieved from the user.
    2. Style number (STYN): style number retrieved from the index list.
    3. Kit indicator (KITI): 0

Refresh the list after creating the SKU to be able to see the SKU in the list.

How to use the application - Style Creation

Given that the setup in M3 is correct, to create a style:
  1. Select an item type in the index list to create a style. The item type is the base for this application.
  2. Make changes to the values in the available fields, if required.
  3. Click the Create Style button.
See details for Style Creation application:
  • Index List

    The Style Creation application starts with an index list, which shows the item types, and some data connected to the item types. It uses the API transaction CRS040MI/LstItmTypes to list the item types.

    When an item type is selected in the index list, the other fields in the application are filled with data.

  • General

    The General form displays general information related to the item template that is connected to the selected item type. The form is filled with data when an item type is selected in the index list. It uses the API transaction MMS200MI/GetItmBasic to display the data and the template item as input to the transaction.

    The fields in this form serve as a base when creating a style. If you do not change the fields, the existing values will be used. If you change the fields, the new values will be used. These changes do not affect the template item connected to the selected item type.

  • Hierarchy Level

    The Hierarchy form displays hierarchy and search group information related to the item template connected to the selected item type. When you select an item type in the index list, the system fills the form with data. The form uses API transaction MMS200MI/GetItmBasic to retrieve the data and uses the template item as input to the transaction.

    The values in the fields define the style. The system uses the existing field values to create the style if you do not modify them. If you change the values, the system uses the new values to define the style. These changes do not affect the template item connected to the selected item type.

  • Season Settings

    The Season Settings form displays information about the season settings related to the item template connected to the selected item type. When you select an item type in the index list, the system fills the form with data. The form uses API transaction MMS016MI/Get to retrieve the data and uses the template item as input to the transaction.

    The values in the fields define the style. The system uses the existing field values to create the style if you do not modify them. If you change the values, the system uses the new values to define the style. These changes do not affect the template item connected to the selected item type.

  • Pricing

    The Pricing form displays pricing information related to the item template connected to the selected item type. When you select an item type in the index list, the system fills the form with data. The form uses API transaction MMS200MI/GetItmPrice to retrieve the data and uses the template item as input to the transaction.

    The values in the fields define the style. The system uses the existing field values to create the style if you do not modify them. If you change the values, the system uses the new values to define the style. These changes do not affect the template item connected to the selected item type.

  • Logistics

    The Logistics form displays logistical information related to the item template connected to the selected item type. When you select an item type in the index list, the system fills the form with data. The form uses API transactions such as MMS200MI/GetItmBasic, MMS200MI/GetItmPrice, and MMS200MI/GetItmFac to retrieve the data and uses the template item as input to the transactions.

    The values in the fields define the style. The system uses the existing field values to create the style if you do not modify them. If you change the values, the system uses the new values to define the style. These changes do not affect the template item connected to the selected item type.

  • Create Style

    The Create Style button creates a new style. It uses API transactions that run in sequence: MHS001MI/AddIntItmMst, MHS200MI/UpdItmFac, and MMS016MIUpdate.

    When you click the button, the system runs the three transactions automatically. You do not need to specify additional input. The transactions use the input already defined in the data service and the values from the General, Hierarchy level, Season settings, Pricing, and Logistics forms.

    1. API transaction MHS001MI/AddIntItmMst is run with this input:
      1. Interface item (IFIN): randomly generated 16 character long string with FSH - as prefix - already specified on the data service.
      2. Message type (E065): FSH – already specified on the data service.
      3. Partner (E0PA): FSH – already specified on the data service.
      4. Process flag (PRMD): *IMP – already specified on the data service.
      5. Configuration code (CHCD): 6 – already specified on the data service.
      6. Additional input from the General, Hierarchy Level, Season Settings, Pricing, and Logistics fields.
    2. If transaction runs successfully, it generates an item number (ITNO).
    3. This item number is used as input to the other two transactions.
    4. MHS200MI/UpdItmFac is run with these input:
      1. Item number (ITNO): item number coming from API transaction MHS001MI/AddIntItmMst.
      2. Facility (FACI): facility set up on the user in 'User. Open' (MNS150)
      3. Additional input from fields in Logistics.
    5. If the transaction fails, the error message “Item number does not exist” is displayed.
      1. The transaction fails if no style (item number) was created through the API transaction MHS001MI/AddIntItmMst.
      2. Check that the setup in M3 is correct according to the list at the start of this document.
      3. Check what the API transaction MHS001MI/AddIntItmMst returns using Developer Tools in the web browser.
    6. The API transaction MMS016MI/Update is run with this input:
      1. Style number (STYN): item number coming from the API transaction MHS001MI/AddIntItmMst.
      2. Additional input from fields in Season Settings.
    7. If the transaction fails, the error message “Style number must be entered” is displayed.
      1. The transaction fails if no style (item number) was created through the API transaction MHS001MI/AddIntItmMst.
      2. Check that the setup in M3 is correct according to the list at the start of this document.
      3. Check what the API transaction MHS001MI/AddIntItmMst returns using Developer Tools in the web browser.
    8. If all transactions run successfully, a new style and connected information is created or updated in 'Item. Open' (MMS001), 'Interface Item. Open Toolbox' (MHS200), 'Style. Open' (MMS016), and 'Item. Connect Facility' (MMS003).

Components

This table shows the components to use in the Style and SKU Creation application:

Component Component details App shortname
Application header Component ID: appHeader

Purpose: Contains three toolbar buttons used to update style information or take the user to the Style Creation application or the Style Overview Application.

 M3STSKUCR
Index list Component ID: IndexList_Styles

Purpose: Lists all the available styles in the company and division used by the user.

M3BE data used: 'Item. Open' (MMS001)

Data services used: Search_Styles

Comment: It uses CHCD=2 and is sorted to display the most newly created style on top of the list. The user can search for style name, style number, and status. You must activate the MITMAS table for search in M3 Function Search Administration.

 M3STSKUCR
Details header Component ID: DetailsHeader_StyleInfo

Purpose: Displays general style information connected to the selected style in the index list.

M3BE data used: 'Item. Open' (MMS001)

Data services used: Get_ItemBasicData

 M3STSKUCR
Season Settings form Component ID: Form_SeasonSettings

Purpose: Displays seasonal information connected to the selected style. The user can update this information.

M3BE data used: 'Style. Open' (MMS016)

Data services used: Get_SeasonInfo, Update_SeasonSettings

 M3STSKUCR
Colors data grid Component ID: DataGrid_StyleColors

Purpose: Lists the colors available for the selected style.

M3BE data used: 'Style. Connect Feature' (MMS017) and 'Feature. Connect Options' (PDS056)

Data services used: List_Colors

Comment: It uses SQNU=10 for color.

 M3STSKUCR
Sizes data grid Component ID: DataGrid_StyleSizes

Purpose: Lists the sizes available for the selected style.

M3BE data used: 'Style. Connect Feature' (MMS017) and 'Feature. Connect Options' (PDS056).

Data services used: List_Sizes

Comment: It uses SQNU=20 for size.

 M3STSKUCR
Seasons data grid Component ID: DataGrid_Seasons

Purpose: Lists the seasons available in the company and division the user uses.

M3BE data used: 'Season. Open' (CRS912)

Data services used: List_Seasons

 M3STSKUCR
Create SKU proposals button Component ID: ButtonGroup_CreateSKUProposals

Purpose: Creates the SKU proposals when clicked.

M3BE data used: 'Feature. Connect Options' (PDS056)

Data services used: Create_SKUProposals

 M3STSKUCR
Preview Selected Options data grid Component ID: DataGrid_SKUProposals

Purpose: Lists the SKU proposals connected to the selected style.

M3BE data used: 'Style. Create Item' (MMS276)

Data services used: List_SKUProposals

 M3STSKUCR
Confirm all and add to style button Component ID: ButtonGroup_CreateSKUs

Purpose: Creates the SKUs when clicked.

M3BE data used: 'Style. Create Item' (MMS276)

Data services used: Create_SKU

 M3STSKUCR
SKU data grid Component ID: DataGrid_SKU

Purpose: Lists the SKUs connected to the selected style.

M3BE data used: 'Interface Item. Open Toolbox' (MHS200)

Data services used: ListMI_SKU

Comment: This data service uses search. You must activate the MITMAH table for search in M3 Function Search Administration.

 M3STSKUCR
Index list Component ID: IndexList_ItemTypes

Purpose: Lists all the available item types in the company and division used by the user.

M3BE data used: 'Item Type. Open' (CRS040)

Data services used: List_ItemTypes

Comment: The user can filter on item type.

 M3STYLECR
General form Component ID: Form_GeneralItemInfo

Purpose: Displays general item information connected to the selected item type in the index list. This information is to be used when creating a new style. The user can change the item information before creating the new style.

M3BE data used: 'Item. Open' (MMS001)

Data services used: Get_ItemData

Comment: It is assumed that season, collection, gender, and department information are mapped to the fields User-defined field 1 (CFI1), User-defined field 3 (CFI3), User-defined field 4 (CFI4), and User-defined field 5 (CFI5) respectively in (MMS001).

 M3STYLECR
Hierarchy Level form Component ID: Form_Hierarchy

Purpose: Displays hierarchy level and search group information connected to the selected item type in the index list. This information is to be used when creating a new style. The user can change the item information before creating the new style.

M3BE data used: 'Item. Open' (MMS001)

Data services used: Get_ItemData

 M3STYLECR
Season Settings form Component ID: Form_SeasonSettings

Purpose: Displays seasonal information connected to the selected style. This information is to be used when creating a new style. The user can change the season information before creating the new style.

M3BE data used: 'Style. Open' (MMS016)

Data services used: Get_SeasonInfo

 M3STYLECR
Pricing form Component ID: Form_Pricing

Purpose: Displays pricing information connected to the selected item type in the index list. This information is to be used when creating a new style. The user can change the item information before creating the new style.

M3BE data used: 'Item. Open' (MMS001)

Data services used: Get_ItemData

 M3STYLECR
Logistics form Component ID: Form_Logistics

Purpose: Displays logistics information connected to the selected item type in the index list. This information is to be used when creating a new style. The user can change the item information before creating the new style.

M3BE data used: 'Item. Open' (MMS001) and 'Item. Connect Facility' (MMS003)

Data services used: Get_ItemData

 M3STYLECR
Create style button Component ID: ButtonGroup_CreateStyle

Purpose: Creates the new style and updates the facility data when clicked.

M3BE data used: 'Item. Open' (MMS001), 'Interface Item. Open Toolbox' (MHS200), 'Style. Open' (MMS016), and 'Item. Connect Facility' (MMS003)

Data services used: Create_Style

 M3STYLECR

Links and bookmarks

This table shows the links and bookmarks that you can use in the Style and SKU Creation application:

Link ID Type Purpose App shortname
Link_StyleOverview M3 Bookmark Opens the application Style Overview when clicked and brings the item number from the index list into Style Overview. M3STSKUCR
Link_ConnectFeatureSizes M3 Bookmark Opens the program 'Style.Connect Feature' (MMS017) when clicked. M3STSKUCR
Link_ConnectFeatureColors M3 Bookmark Opens the program 'Style. Connect Feature' (MMS017) when clicked. M3STSKUCR

Dialogs

This table shows the dialogs that you can use in the Style and SKU Creation application:

Dialog ID API program Purpose App shortname
Dialog_StyleCreation - Opens the Style Creation application in modal mode. M3STSKUCR
Dialog_EditStyle MMS200MI/UpdItmBasic Enables the user to make changes to the selected style in the index list. M3STSKUCR

Conditional styles

This table shows the conditional styles that you can use in the Style and SKU Creation application:

Component Condition name Target field Condition Styling App shortname
Index list Condition_Status STAT STAT=20 Text color: green

Text weight: bold

 M3STSKUCR
Index list Condition_Override OVIT OVIT=0 Text color: red

Text weight: bold

Text override: No

 M3STYLECR
Index list Condition_Override OVIT OVIT=1 Text color: green

Text weight: bold

Text override: Yes

 M3STYLECR
Index list Condition_Status STAT STAT=20 Text color: green

Text weight: bold

 M3STYLECR
Index list Condition_Status STAT STAT=50 Text color: red

Text weight: bold

 M3STYLECR
Related topics