Download Changed or New Item Information from M3 to an External POS System

This document explains how to download changed items from the last transfer. A net transfer is performed. This is useful when there are large volumes of item data to different shops, where different shops can have different item assortments. The transfer can be performed several times a day.

Outcome

Basic item information is transferred to the files OPTMFI (transfer file) and OPTMML (transfer file mailing list) in M3. Information is prepared in these files that allows the user to retrieve the information from the POS system.

The POS system retrieves the downloaded item information, and any modification made to the data in M3 is passed on to the POS system.

If there are large volumes of basic data transactions, a net transfer is recommended. During a net transfer, only records changed from a specific selection date are transferred again.

For controlling changes the Change date field (LMDT) is used in the tables Item (MITMAS), Item/Warehouse (MITBAL, Alternate units (MITAUN and unit type 1), Price list record per shop (OPRICL), Alias (MITPOP), Style (MITMAH) and Item/Language (MITLAD).

When item data is exported from M3 to the external POS system, it is available in the OPTMFI file. For each record, an action code indicates the action to perform (delete, for example) and the record information is stored in a data field.

Each record in the OPTMFI file has an associated mailing list in the OPTMML file. This is a list of shops to which each record must be sent.

Before you start

OPS700 settings must be defined. The 'Mailing list base' field in (OPS700/E) defines the basis of the mailing list for the item transfer.

A shop must be created in 'Shop. Open' (OPS500).

The subscriber must be defined in (OPS500/E). Subscribers are used to group and connect shops. Replication is made on the subscriber level.

Follow These Steps

  1. Start 'Item. Net Transfer' (OPS620/E).

  2. Select the function to use:

    • Create records for new/changed items to replicate to the external Point Of Sales system.
    • Create records for items to be deleted in the external Point Of Sales system.
    • Total item replication. Create records for new items to replicate to the Point Of Sales system. This option is normally used when a new environment is started up. This option has limited selections and only selections for Planning method and Sales item are available.
  3. Make the appropriate selections. The 'Change date' is mandatory and represents the date as of when the changes are made. For example, if August 13, 2013 is entered it will check the change date (LMDT) from August 13 to today┬┤s date. Press Enter when you have made all your selections.

  4. The POS outboxes OPTMFI (transfer file) and OPTMML (transferfile mailing list) are now updated, and the information is ready to be retrieved by the POS system.

    The action codes are:

    Action code:

    Description:

    *DEL

    Delete:

    A delete record will be transferred to POS.

    This is set if the status is equal to 90 in MITMAS or in MITBAL or if function selection in OPS620 is set to 4.

    *UPD

    Update:

    An update record will be transferred to POS.

  5. In OPS600MI you can list and confirm the item data for a specific subscriber using transactions LstItm and CnfItm.

  6. In 'Item/Customer Net Transfer Delete' (OPS690), you can clean up completed (confirmed) transactions in POS outboxes OPTMFI and OPTMML.

Related topics