Manage Items in the Item Data Interface

This document explains how you manage items in the item data interface. The item data interface enables you to do the following:

Outcome

You can receive, process, and import items in M3 through the item data interface.

You can also perform changes and log changes for already imported items in the item import function.

The item data interface provides a solution in which item data can be exchanged and enriched between M3 BE and other applications or third-party products.

For further details, refer to the API Repository in M3 API Tools.

Solution

Receive large amounts of structured or unstructured item-related data to interface

An interface item master record is created by the MI transaction MHS001MI –AddIntItmMst ('Add Interface Item Master'). The transaction contains all existing fields in MHIMAS. Other 'Add' transactions are

The function program MHIMPITM imports the interface items and creates BE items.

The item type is either entered manually or retrieved as the standard item type defined for the partner used. Mandatory fields are:

All other attributes can be added through manual enrichment or through additions through 'Add' or 'Chg' MI transactions.

Level of Processing

By using a process flag in the MI transactions, you can control whether interface item data is added only, whether it is added and validated, or whether it is added, validated and imported into M3. The valid process flags are as follows:

blank - Data is only added. Validation and import to M3 is done manually.

*VAL - Data is added and validated. Import to M3 is done manually.

*IMP - Data is validated and, if there are no validation errors, imported to M3.

*AUT – Same as *IMP, but the processing is done through an auto start job, MHS250, instead of interactively.

For more information about the MI programs and their transactions, see the Redbook Item Import Interface.

Work with item data manually in the item interface

MHS200 is the toolbox from which all functions in the interface can be accessed.

Interface items and all related data can be searched and displayed.

The following options are available on the (MHS200/B) panel.

All the interface item programs have normal detail panels where the data can be changed or enriched after being received from the external system. The following fields are added for the item import interface function:

All MHS programs have the following:

In the case of MHS001/E, 'External message number' indicates the sender's message number. This number can be used for traceability. 'Item number' indicates the number the item has in M3 BE if it is imported. Before the import, you can also manually enter the M3 BE item number here. 'Message ID' indicates an error message received when validating or importing items.

For more information on 'Lowest status', see Statuses in the Item Interface.

Import interface item data to M3 BE

Item data can be imported to M3 BE in three different ways:

Perform changes through the interface

An interface item can be changed manually through the MHS programs or through the MI transactions. When an interface item record is changed, the status of that record is lowered to 20. To make the changes take effect in M3 BE, the interface item needs to be validated and imported again.

A change log function is available. You can select the fields to be logged for changes. Any change to these fields made through the MI program will be stored in the change log instead of taking effect immediately.

Using the change log

Note: You must first make the settings for the change log.
  1. Start 'Interface Item Change Log. Open' (MHS210). On the B panel you display the interface item and the table s that are affected by the change.

    Keys 1, 2 and 3 display the value for the table. For example if the table is MHIBAL key 1 is a warehouse.

    'Field' is the field you have set for logging (MHS264).

  2. Display the E panel to check the changed values. The From value field indicates the value before the change. The To value field displays the new value.

  3. Display the B panel again. To approve the change, select option 12=Approve. To reject the value, select option 11=Reject.

    You can also approve or reject all records for one interface item by function F15=Reject all, and F16=Approve all.

  4. The Change log status can be one of the following:

    • 10 = A change log exists. The change log contains a record.
    • 15 = Rejected. The record will remain in (MHS210) for the number of days defined in (MHS262) before it is deleted.
    • 20 =Approved. The change takes effect. The record is updated in the interface program (in this example the purchase price is updated in MHS001) and can be imported to M3. The record will remain in (MHS210) for the number of days defined in (MHS262) before it is deleted.
    Note: You can manage receiving fashion item data through the item import interface.
    • Receive styles into the interface
    • Import style to M3 BE
    • Ensure the features/options are in place and connected to the style in M3 BE (done automatically if created from style template)
    • Create interface SKUs
    • Send SKU/style relations to the interface (which style and which features/options combination is one SKU)
    • Import SKUs and all SKU-related data in M3 is created (no difference to BE-created SKUs)
    • Season functionality is supported from the interface

    For details on creating settings for templates, refer to these documents in the see also section:

    • Create Style and Stock Keeping Units
    • Settings for Style and Stock Keeping Unit
  5. The style is added in (MHS001) or (MHS001MI) as a regular interface item but always with configuration code 6 on the (MHS001/F) panel.

  6. The style is imported to M3 in the same way as a regular interface item. The style is created in (MMS001) or (MHS001MI) and (MMS016).

    Features are automatically copied to (MMS017) if template data exists. If there is a need to add features and options from the external system, MMS017MI, PDS056MI and PDS050MI should be used.

The SKUs

The SKUs are added in (MHS001) or (MHS001MI) as a regular interface item but always with configuration code 7 on the (MHS001/F) panel.

The style and SKU connection

A style/SKU relation must be created in order to specify the options of the features that apply for this SKU.

  1. Start 'Interface SKU. Connect Style' (MHS220). Select the partner and enter an interface item (the SKU). Open the E panel.

  2. The interface style number indicates the interface style that should be connected.

  3. If working in MHS220, you can press F14 to retrieve the features of the imported interface style.

  4. Specify the options for the feature.

  5. The Style field on the bottom of the E panel indicates whether the style has been imported to M3 before. The first time the style is received; this field is open and empty. When the interface style has been successfully imported this field is entered with the M3 style number and is not editable.

  6. Display the (MHS220/B) panel again.

The season definition per style or SKU

  1. Select option 11=Style/season on the (MHS220/B) panel. 'Interface Style. Connect Season' (MHS221) starts.

  2. Specify an interface style number or an interface SKU. (Season can be specified at either level. Note that season control must be checked in (MHS001/F).)

  3. Specify a season. Seasons are defined in (CRS912).

  4. Select Create and press Next until the B panel is displayed again. Alias records with alias category 88 will now only be created for the connected season in (MMS025).

Related topics