Style Overview
Although M3 offers powerful product management capabilities, its standard interface can be complicated and scattered. This app consolidates essential information, such as style details, variant stock, pre-packs, planning, and product structure, into a single, simple interface. The result is a clearer, faster, and more flexible way to manage fashion products. This approach reduces complexity and improves overall efficiency.
User stories
Product managers in the fashion industry use a centralized application to search for and access detailed information about styles, SKUs, and pre-packs. This application enables them to manage product performance, availability, life cycle, and sourcing efficiently without the need to navigate multiple screens in M3.
M3 Business Engine configuration
These M3 Business Engine configurations are required to get the Style Overview application to work. It also lists fields or values that are hard-coded in the application, that may need to be manually changed to suit the set up for the tenant where the application is installed.
- 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 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).
- The sequence of colors and sizes are not sorted by the sequence number that the option is connected to the feature. For now, they are sorted alphabetically. In case color and sizes should be sorted differently, we recommend making a custom list.
- Only pre-packs created in 'Kit. Create' (PDS017) are shown in the prepack area. In other words, the search results for pre-packs are filtered by checking if the Kit indicator (KITI) = 1.
- The application is set up for two-dimensional styles using the X for sizes and the Y for colors. This feature sequence number for the color feature in 'Style. Connect Feature' (MMS017) is assumed to be 10 and for the size feature it is assumed to be 20.
- The structure type for a pre-pack product structure is assumed to be 'KIT'.
This table shows the fields that are following the naming convention as per PLM for Fashion Integration with M3:
| Application field name | M3 field | M3 table |
|---|---|---|
| Brand | Business area (BUAR) | MITMAS |
| Product category | Product group (ITCL) | MITMAS |
| Active season | User defined field 1 (CFI1) | MITMAS |
| Collection | User defined field 3 (CFI3) | MITMAS |
| Gender | User defined field 4 (CFI4) | MITMAS |
| Division (men's/women's apparel or footwear) | User defined field 5 (CFI5) | MITMAS |
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 Overview application.
| Function or API | Transaction | Information Category | View |
|---|---|---|---|
| CRS040MI | LstItmTypes | ||
| LISTMI | ListDataAsCSV | M3_LIST_MPDMAT | M3_01_01 |
| LISTMI | ListDataAsCSV | M3_LIST_MPDOMA | M3_01_01 |
| LISTMI | ListDataAsCSV | M3_LIST_MITMAH | M3_01_01 |
| LISTMI | ListDataAsCSV | M3_LIST_MITMAH | M3_02_01 |
| LISTMI | ListDataAsCSV | M3_LIST_MITMAH | M3_03_01 |
| MHS001MI | AddIntItmMst | ||
| MMS016MI | Update | ||
| MMS016MI | Get | ||
| MMS025MI | GetAlias | ||
| MMS162MI | LstStyleWhsBal | ||
| MMS162MI | LstStyleItem | ||
| MMS200MI | GetItmBasic | ||
| MMS200MI | SearchItem | ||
| MMS200MI | UpdateItmBasic | ||
| MMS200MI | GetItmWhsBasic | ||
| MMS200MI | UpdItmFac | ||
| MMS200MI | GetItmFac | ||
| MMS200MI | GetItmPrice | ||
| MMS200MI | LstItmWhsByItm | ||
| PDS001MI | ListByItem | ||
| PDS002MI | LstOperation |
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.
- You cannot use styles with more than two features. The setup supports two-dimensional styles using X for sizes and Y for colors.
- You cannot add or connect features to a new style. The style always inherits the features from the template item.
How to use the application
- Index List and Details Header
The Style Overview application starts with an index list. The list displays the styles and some data related to styles. The details header section also displays data about styles.
- 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 and SKU Creation application.
- Style
The Style tab consists of these tabs:
- Colors and Sizes: This tab contains two data grids that display existing colors and sizes connected to a style. They are populated with data when a style is selected in the index list. Each data grid contains a button that takes the user to 'Feature. Connect Options' (PDS056).
- Details and Hierarchy: This tab contains two forms. One form displays additional style information, and the other displays hierarchy and search group information. The forms are filled with data when a style is selected in the index list.
- Season Settings: This tab contains a form that displays season setting information. The form is filled with data when a style is selected in the index list.
- Pricing: This tab contains a form that displays pricing information. The form is filled with data when a style is selected in the index list.
- Weight and Volume: This tab contains two forms. One form displays weight information, and the other displays dimension information. The forms are filled with data when a style is selected in the index list.
- SKU
The SKU tab contains two data grids and three forms. When a style is selected in the index list, the first data grid is populated with the corresponding SKUs. This grid includes a button that opens the Style and SKU Creation application. Upon selecting a SKU, the second data grid is populated with information about the warehouses where the SKU is available. Additionally, these forms are updated with relevant data: SKU Details, EAN Information, and UPC Information.
- Pre-Packs
The Pre-Packs tab contains three data grids and one form. When a style is selected in the index list, the data grid displaying the pre-packs is populated. This grid also includes a button that opens 'Kit. Create' (PDS017). When a pre-pack is selected, the data grid showing its contents is populated. Additionally, the form displaying pre-pack details and the data grid listing the warehouses where the pre-pack is available are also updated.
- Planning Information
The Planning Information tab contains a data grid that shows the warehouses where the style exists. The grid is filled with data when a style is selected in the index list. The tab contains these additional tabs:
- Planning Information: This tab contains a form that displays planning data, and a button that opens 'Item. Connect Warehouse' (MMS002). The form is filled with data when a warehouse is selected.
- Warehouse Information: This tab contains a form that displays warehouse data, and a button that opens 'Item. Connect Warehouse' (MMS002). The form is filled with data when a warehouse is selected.
- Product Information: This tab contains a form that displays production data, and a button that opens 'Item. Connect Warehouse' (MMS002). The form is filled with data when a warehouse is selected.
- Weight and Volume: This tab contains a form that displays weight and dimension information. The form is filled with data when a style is selected in the index list.
- Product Structure
The Product Structure tab contains four data grids. When a style is selected in the index list, the data grid displaying facilities is populated. This grid also includes a button that opens 'Product Structure. Open' (PDS001). When a facility is selected, the data grids showing the Bill of Operations and Bill of Material are populated. Selecting a line in the Bill of Material further populates the data grid displaying the available options for that line.
- Style Creation and how to use the application
Provided that the setup in M3 is correct, you can create a style by selecting an item type in the index list, the item type serves as the base for this application, modifying values in the available fields as required, and then clicking the Create Style button. Additional details are provided:
- Index List
The Style Creation application begins with an index list that displays item types along with related data. It uses API transaction CRS040MI/LstItmTypes to retrieve and list the item types. When an item type is selected in the index list, the remaining fields in the application are automatically populated with data.
- General
The General form displays general information about the template item that is connected to the selected item type. The form is filled with data when you select an item type in the index list. The form uses API transaction MMS200MI/GetItmBasic to display the data, and using the template item as input to the transaction.
The fields in this form provide default values when you create 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.
- API transaction MHS001MI/AddIntItmMst is run with this input:
- Interface item (IFIN): randomly generated 16 character long string with FSH - as prefix - already specified on the data service.
- Message type (E065): FSH – already specified on the data service.
- Partner (E0PA): FSH – already specified on the data service.
- Process flag (PRMD): *IMP – already specified on the data service.
- Configuration code (CHCD): 6 – already specified on the data service.
- Additional input from the General, Hierarchy Level, Season Settings, Pricing, and Logistics fields.
- If transaction runs successfully, it generates an item number (ITNO).
- This item number is used as input to the other two transactions.
- MHS200MI/UpdItmFac is run with these input:
- Item number (ITNO): item number coming from API transaction MHS001MI/AddIntItmMst.
- Facility (FACI): facility set up on the user in 'User. Open' (MNS150)
- Additional input from fields in Logistics.
- If the transaction fails, the error message “Item number does not exist” is displayed.
- The transaction fails if no style (item number) was created through the API transaction MHS001MI/AddIntItmMst.
- Check that the setup in M3 is correct according to the list at the start of this document.
- Check what the API transaction MHS001MI/AddIntItmMst returns using Developer Tools in the web browser.
- The API transaction MMS016MI/Update is run with this input:
- Style number (STYN): item number coming from the API transaction MHS001MI/AddIntItmMst.
- Additional input from fields in Season Settings.
- If the transaction fails, the error message “Style number must be entered” is displayed.
- The transaction fails if no style (item number) was created through the API transaction MHS001MI/AddIntItmMst.
- Check that the setup in M3 is correct according to the list at the start of this document.
- Check what the API transaction MHS001MI/AddIntItmMst returns using Developer Tools in the web browser.
- 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).
- API transaction MHS001MI/AddIntItmMst is run with this input:
- Index List
Components
This table shows the components to use in the Style Overview 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 and SKU Creation Application. |
M3STYLEOVE |
| 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. You can search for style name, style number, and status. You must activate the MITMAS table for search in M3 Function Search Administration. |
M3STYLEOVE |
| 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 |
M3STYLEOVE |
| Colors data grid | Component ID: DataGrid_Colors
Purpose: Displays existing colors connected to the selected style in the index list. M3BE data used: 'Style. List Created Items by Matrix' (MMS277) Data services used: ListMI_SKUColors Comment: It uses KITI=0. Contains a button that takes the user to 'Feature. Connect Options' (PDS056). |
M3STYLEOVE |
| Sizes data grid | Component ID: DataGrid_Sizes
Purpose: Displays existing sizes connected to the selected style in the index list. M3BE data used: 'Style. List Created Items by Matrix' (MMS277) Data services used: ListMI_SKUSizes Comment: It uses KITI=0. Contains a button that takes the user to 'Feature. Connect Options' (PDS056). |
M3STYLEOVE |
| Style Information form | Component ID: Form_StyleDetails
Purpose: Displays further style information connected to the selected style in the index list. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_ItemBasic |
M3STYLEOVE |
| Hierarchy Level form | Component ID: Form_Hierarchy
Purpose: Displays hierarchy and search group information connected to the selected style in the index list. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_ItemBasic |
M3STYLEOVE |
| Season Settings form | Component ID: Form_SeasonSettings
Purpose: Displays seasonal information connected to the selected style. M3BE data used: 'Style. Open' (MMS016) Data services used: Get_SeasonInfo, Update_SeasonSettings Comment: The user can update this information. |
M3STYLEOVE |
| Purchase Price form | Component ID: Form_PurchasePrice
Purpose: Displays purchase price information connected to the selected style. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_StyleItemAndPriceInfo |
M3STYLEOVE |
| Sales Price form |
Component ID: Form_SalesPrice Purpose: Displays sales price information connected to the selected style. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_StyleItemAndPriceInfo |
M3STYLEOVE |
| Weight and Volume form |
Component ID: Form_WeightVolume Purpose: Displays weight information connected to the selected style. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_StyleItemAndPriceInfo |
M3STYLEOVE |
| Dimensions form |
Component ID: Form_Dimensions Purpose: Displays dimensions information connected to the selected style. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_StyleItemAndPriceInfo |
M3STYLEOVE |
| SKU data grid |
Component ID: DataGrid_SKU Purpose: Displays SKUs connected to the selected style. M3BE data used: 'Interface Item. Open Toolbox' (MHS200) Data services used: ListMI_SKU Comment: It uses KITI=0. This data service uses search. You must activate the MITMAH table for search in M3 Function Search Administration. Contains a button that opens the application Style and SKU Creation. |
M3STYLEOVE |
| Stock SKU data grid |
Component ID: DataGrid_StockSKU Purpose: Displays in which warehouses the SKUs exist. M3BE data used: 'On-hand. Display Style by Matrix' (MMS162) Data services used: List_SKUStockByWarehouse Comment: It uses CHCD=3. |
M3STYLEOVE |
| SKU Details form |
Component ID: Form_SKUDetails Purpose: Displays SKU details connected to the selected SKU. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_SKUDetails |
M3STYLEOVE |
| EAN form |
Component ID: Form_EAN Purpose: Displays EAN information connected to the selected SKU. M3BE data used: 'Item. Connect Alias Number' (MMS025) Data services used: Get_SKUEANAlias Comment: It uses ALWT=2 and ALWQ=EA13. |
M3STYLEOVE |
| UPC form |
Component ID: Form_UPC Purpose: Displays UPC information connected to the selected SKU. M3BE data used: 'Item. Connect Alias Number' (MMS025) Data services used: Get_SKUUPCAlias Comment: It uses ALWT=2 and ALWQ=UPC. |
M3STYLEOVE |
| Pre-Packs data grid |
Component ID: DataGrid_Prepacks Purpose: Displays pre-packs connected to the selected style. M3BE data used: 'On-hand. Display Style by Matrix' (MMS162) Data services used: List_Prepacks Comment: It uses CHCD=0. Contains a button that opens 'Kit. Create' (PDS017). |
M3STYLEOVE |
| Included in Pre-Pack data grid |
Component ID: DataGrid_PrepackContent Purpose: Displays what is included in the pre-packs connected to the selected style. M3BE data used: 'Product Structure. Open' (PDS001) Data services used: ListMI_PrePackMaterials Comment: It uses STRT=KIT. |
M3STYLEOVE |
| Pre-Pack Details form |
Component ID: Form_PrepackDetails Purpose: Displays pre-pack details. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_PrepackAndSeasonDetails |
M3STYLEOVE |
| Pre-Pack Stock Information data grid |
Component ID: DataGrid_PrepackStockInfo Purpose: Displays in which warehouses the selected pre-pack exists. M3BE data used: 'On-hand. Display Style by Matrix' (MMS162) Data services used: List_PrepackStockByWhs |
M3STYLEOVE |
| Stock Locations data grid |
Component ID: DataGrid_StockLocations Purpose: Displays in which warehouses the selected style exists. M3BE data used: 'Item. Connect Warehouse' (MMS002) Data services used: List_ItemWarehouse |
M3STYLEOVE |
| Planning Information form |
Component ID: Form_PlanningInfo Purpose: Displays planning data connected to the selected style and warehouse. M3BE data used: 'Item. Connect Warehouse' (MMS002) Data services used: Get_ItemWarehouseData Comment: Contains a button that opens 'Item. Connect Warehouse' (MMS002). |
M3STYLEOVE |
| Warehouse Information form |
Component ID: Form_WarehouseInfo Purpose: Displays warehouse data connected to the selected style and warehouse. M3BE data used: 'Item. Connect Warehouse' (MMS002) Data services used: Get_ItemWarehouseData Comment: Contains a button that opens 'Item. Connect Warehouse' (MMS002). |
M3STYLEOVE |
| Production Information form |
Component ID: Form_ProductionInfo Purpose: Displays production data connected to the selected style and warehouse. M3BE data used: 'Item. Connect Warehouse' (MMS002) Data services used: Get_ItemWarehouseData Comment: Contains a button that opens 'Item. Connect Warehouse' (MMS002). |
M3STYLEOVE |
| Weight and Volume form |
Component ID: Form_WeightVolumeDimensions Purpose: Displays weight and dimensions information connected to the selected style. M3BE data used: 'Item. Open' (MMS001) Data services used: Get_StyleItemAndPriceInfo |
M3STYLEOVE |
| Facility data grid |
Component ID: DataGrid_Facility Purpose: Displays facilities connected to the selected style. M3BE data used: 'Product Structure. Open' (PDS001) Data services used: List_ProductStructureHeader Comment: Contains a button that opens 'Product Structure. Open' (PDS001). |
M3STYLEOVE |
| Bill of Operations data grid |
Component ID: DataGrid_BillOfOperations Purpose: Displays bill of operations connected to the selected style and facility. M3BE data used: 'Product. Connect Materials/Operations' (PDS002) Data services used: List_Operations |
M3STYLEOVE |
| Bill of Material data grid |
Component ID: DataGrid_BillOfMaterials Purpose: Displays bill of materials connected to the selected style and facility. M3BE data used: 'Product. Connect Materials/Operations' (PDS002) Data services used: ListMI_BillOfMaterials |
M3STYLEOVE |
| Option per Line data grid |
Component ID: DataGrid_OptionLine Purpose: Displays options per line connected to the selected style, facility and bill of material. M3BE data used: 'Product. Connect Materials/Operations' (PDS002) Data services used: ListMI_OptionsLine |
M3STYLEOVE |
| 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. You can use this information 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. You can use this information 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. You can use this information 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. You can use this information 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. You can use this information 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 Overview application:
| Link ID | Type | Purpose | App shortname |
|---|---|---|---|
| Link_ColorOptions | M3 Bookmark | Opens the program 'Feature. Connect Options' (PDS056) when clicked. | M3STYLEOVE |
| Link_SizeOptions | M3 Bookmark | Opens the program 'Feature. Connect Options' (PDS056) when clicked. | M3STYLEOVE |
| Link_ProductStructure | M3 Bookmark | Opens the program 'Product Structure. Open' (PDS001) when clicked. | M3STYLEOVE |
| Link_ItemWarehouseFields1 | M3 Bookmark | Opens the program 'Item. Connect Warehouse' (MMS002) when clicked. | M3STYLEOVE |
| Link_ItemWarehouseFields2 | M3 Bookmark | Opens the program 'Item. Connect Warehouse' (MMS002) when clicked. | M3STYLEOVE |
| Link_ItemWarehouseFields3 | M3 Bookmark | Opens the program 'Item. Connect Warehouse' (MMS002)) when clicked. | M3STYLEOVE |
| Link_StyleandSKUCreation | M3 Bookmark | Opens the application Style and SKU Creation when clicked and brings the item number in the index list into Style and SKU Creation. | M3STYLEOVE |
| Link_PrepackCreatePrePack | M3 Bookmark | Opens the program 'Kit. Create' (PDS017) when clicked. | M3STYLEOVE |
| Link_StyleandSKUCreationDataGrid | M3 Bookmark | Opens the application Style and SKU Creation when clicked and brings the item number in the index list into Style and SKU Creation. | M3STYLEOVE |
Dialogs
This table shows the dialogs that you can use in the Style Overview application:
| Dialog ID | API program | Purpose | App shortname |
|---|---|---|---|
| Dialog_StyleCreation | Opens the Style Creation application in modal mode. | M3STYLEOVE | |
| Dialog_EditStyle | MMS200MI/UpdItmBasic | Enables the user to make changes to the selected style in the index list. | M3STYLEOVE |
Conditional styles
This table shows the conditional styles that you can use in the Style Overview application:
| Component | Condition name | Target field | Condition | Styling | App shortname |
|---|---|---|---|---|---|
| Index list | Condition_Status | STAT | STAT=20 |
Text color: green Text weight: bold |
M3STYLEOVE |
| Details header | Condition_StatusItem | STAT | STAT=20 |
Text color: green Text weight: bold |
M3STYLEOVE |
| 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 |