Settings for Integration to an External System

This document explains how you set up M3 Warehouse Integration (WHI). In this document a warehouse management system (WMS) is used as an example of an integrated system.

Outcome

Provided that the settings are defined for warehouse integration, all downloads and uploads are performed automatically from the host M3 to an external system. The settings also determine, to a certain extent, when downloads and uploads are executed.

For more information, refer to M3 Business Engine Administrator's Guide for Warehouse Management Interfaces.

Before you start

You have to perform a mapping job together with the person who is responsible for the external system.

Consider these issues:

  • Which system owns which function?
  • Where are the cuts in the business processes?
  • Do the two systems have the necessary data? (The unique keys must be provided).
  • Who is responsible for the actual interface?
  • Which technology should be used: file to file, middleware, APIs, EDI, XML or a combination of these techniques?

Follow these steps

General settings

  • Define External System

    1. Start 'Stock Msg Partner. Open' (MMS865). Here you define external system(s) to M3.

    2. On the B panel, the Message direction field indicates the direction of the message. If you want to both download and upload, you must create two records, one for output and one for input.

    3. Fill in the Partner field and the Message type field. For outgoing messages, the Message type field should be blank.

    4. Open the E panel. The only mandatory field is the 300 Partner manager field.

    5. For outgoing messages, there is an F panel with optional fields.

    6. On the B panel, option 12='Mail parameter' starts 'Stock Message Partner. Connect Msg Types' (MMS867). You activate the message types, which should be sent for the defined external system (partner). You can also create standard messages with F14=Create standard.

      Note: The partner controls how many download records to create per business event in M3. It is possible to integrate with several systems and each system must be defined as a partner.
  • Define What to Download and Upload

    1. Start 'Warehouse. Open' (MMS005). Open the H panel.

    2. Under Send you can, per warehouse, activate the Send planned receipts, Send picking lists and Send item master fields.

    3. Under Retrieve you can activate the Retrieve receipts/pick list and Retrieve stock transactions fields.

    4. The Alias qualifier field indicates which type of EAN code is to populate the alias number (POPN) field of the item master download file. This only applies if the Item master field in (MMS005/H) is set to 1.

  • Define Locations

    1. Start 'Stock Location. Open' (MMS010).

    2. At least two locations must be entered, one allocatable and one non-allocatable. On the E panel, the Allocatable field must be set to 1=Allocatable, and for the other location, to 0=Non-allocatable. If the two-step receiving flow for purchase orders must be used, then three locations must be defined, one per status (under inspection, approved and rejected).

Downloads - Item basic data, item alias data, expected receipts, picking list

The M3 job scheduler allows standard M3 reporting or batch functions to run automatically according to a schedule. This function can be used for automatic downloads.

For detailed step and action instructions, refer to Administrator's Guide for Job Scheduler.

Settings for using the MBM initiator for expected receipts

  1. An MBM initiator indicates whether downloads of expected receipts should be sent to M3 e-Collaborator. If you activate the MBM initiators, the download will be sent to M3 e-Collaborator.

  2. Check that the parameters on the F panel in 'Stock Msg Partner. Open' (MMS865) are set correctly. The planned receipts, picking list and item master parameters must be set to 1, depending on which functionality you want to activate. The planned receipts parameter in M3 e Collaborator must be set to 1 or 2 if you want to send planned receipts by the initiator.

  3. The send parameters on the H panel in 'Warehouse. Open' (MMS005) must be set to 1 to activate expected receipts, picking lists and the item master.

  4. Check that the document you want to connect to the initiator exists in 'Standard Document. Open' (CRS027). If not, create it. The document numbers are 120=Picking list, E01=Item data export, and E02=Planned receipts export.

  5. Check that the document also exists in 'M3 Document. Open' (CRS928) or create it.

  6. On the (CRS928/E) panel, set the Media control selection flag to 1. Field 1 and field 2 are the object values that are connected to a media, and at least Field 1 must be filled in.

    This could, for example, be partner, supplier, customer or anything else you want to use to trigger the initiator. The values you can choose from are retrieved from (CRS928) and must be hard coded for the document in question. Use F14='Generate Standard' afterwards in that case.

  7. In 'Std Document. Connect Media Ctrl Object' (CRS945) you see the field you indicated in (CRS928). Create a new record with a value for this field. Go through the panel sequence. Choose option 12=Media for your new record to start (CRS949).

  8. In 'Doc Media Control Object. Connect Media' (CRS949) you connect a media to the partner, supplier, customer or other object you specified in the previous step. Choose a service identity (the service provider for output from M3 that you want to use). Every record in (CRS949) gives rise to a record in 'Output. Manage per Job' (MNS206). The record with an exclamation mark in front of it in (MNS206) is connected to the initiator. Use option 13=Partner for that record to view the output per partner. The media is defined in (CRS116).

Uploads - Settings for internal stock messages

  1. Start 'Internal Stock Trans Qualif. Open' (MMS860).

  2. On the B panel, use option 14='Generate all qualifiers' to generate all the standard qualifiers that are used for the integration to PkMS.

Uploads - Settings for order-initiated stock messages

  1. Start 'Internal Stock Trans Qualif. Open' (MHS860).

  2. On the B panel, use option 14='Generate all qualifiers' to generate all the standard qualifiers that are used for the integration to PkMS.

  3. Start 'Number Series. Open' (CRS165).

  4. Create number series type 16 with series A for internal stock messages.

  5. Create number series type 17 with series 1 for order-initiated stock messages.

Check order configuration (optional)

  1. The different order types must have the correct auto level and next manual function. The picking list must be printed.

  2. Check the allocation method (6 is preferred) and issue method (1) for items.

Archive received messages (optional)

  1. Start 'Stock Msg Partner. Open' (MMS865).

  2. Select option 2 to start (MMS865/E). Activate the filing parameter and number of days before last activity.

Round decimal (optional)

  1. Start 'Stock Msg Partner. Open' (MMS865).

  2. Select option 1 in (MMS865/E) for parameter 325. This automatically rounds the value of the input that contained too many decimals for quantity and catch weights fields.

Parameters to set

Program ID/ Panel

Field

The field indicates …

(MMS865/B)

Message direction

… the direction of the message.

The valid alternatives are:

  • I = Input
  • O = Output

(MMS865/B)

Partner

… the identity an external partner, for example with the internal number of the customer.

(MMS865/B)

Message type

… the message type, which must contain the name of the standard message to be processed. Examples:

  • EDIFACT messages: ORDERS ORDRSP, etc.
  • ODETTE messages: DELINS AVIEXP, etc.

(MMS865/E)

300 Partner manager

… a unique user ID.

The ID can be used for selection and sorting.

(MMS865/E)

305 Override mail receiver

… whether overriding of an entered mail recipient is allowed.

The valid alternatives are:

0 = No, mail recipient will not be overridden.

1 = Yes, mail recipient will be overridden using a value in (RSS015/310).

(MMS865/E) 325 Rounding Decimal

The field indicates: The rounding decimal allows whether rounding may be applied to values with too many decimals in MHS850MI and MMS850MI transactions for the fields of Quantity and Catchweight.

The valid alternatives are:

  • 0 = No, the input value is not rounded, the API may return an error if the value has too many decimals
  • 1 = Yes, the input quantity and catch weight are rounded if they have too many decimals, the rounded value is saved in stock message details.

(MMS865/E)

Filing

… whether the message should be archived. The valid alternatives are:

  • 0 = No
  • 1 = Yes

This field is only valid for upload messages (MMS850, MHS850).

(MMS865/E)

Days before archive/deletion

… the number of days after a received and executed inventory transaction that a message is archived. When a message is archived, it is removed from production files and stored in an archiving file.

This field is only valid for upload messages (MHS850, MMS850).

F Panel for Download partners

Program ID/ Panel

Field

The field indicates …

(MMS865/F)

Download planned receipts (for a specific partner)

… whether planned receipts are downloaded to the MHEXRH and MHEXRD out files. These out files are used to standardize the format for interfacing external systems.

M3 updates the out files whenever the material plan in (MMS080) is updated.

This field also indicates to the system whether pre-allocations are to be downloaded to the MHPREA out file.

(MMS865/F)

Download picking lists (for a specific partner)

… whether the picking list is downloaded to the output files MHPICL and MHPICD. Output files are used to provide a standard output format for interfaces with external systems.

M3 updates the output files when a picking list is released (picking list status 40).

These alternatives are valid:

  • 0 = The picking list is not downloaded.
  • 1 = The picking list is downloaded.
  • 2 = The picking list is downloaded and printed.
  • 3 = The picking list is downloaded and printed but not validated against warehouse integration in (MWS420).

(MMS865/F)

Download item master (for a specific partner)

… whether the item output file (MHITMA) and alias number file (MHIPOP) are to be populated for this specific warehouse. Output files provide a standard output format for interfaces with other systems.

M3 updates the output file in these situations:

  • A download is initiated manually through the selection program (MHS630) or (MHS635).
  • Automatic download are defined through the M3 Job Scheduler. The item master is downloaded automatically according to a schedule.

(MMS865/F)

Create MBM initiators (Send pl receipts to e-Collaborator)

… whether MBM initiators are to be created for expected receipts so that they can be sent to M3 e Collaborator.

These are the valid alternatives:

  • 0 = No, do not create MBM initiators (do not send planned receipts to M3 e-Collaborator)
  • 1 = Yes, create MBM initiators. You can choose between Send manually (MHS815) or Send at regular intervals (MHS816)

(MMS867/E)

Activate application message type

… whether you activate the message types, which are to be downloaded for the defined external system (partner).

On the B panel, you can also create standard messages through F14=Create standard.

Note: The partner controls how many download records to create per business event in M3. You can integrate to several systems, and each system must be defined as a partner.

(MMS005/H)

Download planned receipt (for a specific warehouse)

… whether planned receipts are downloaded to the MHEXRH and MHEXRD out files. These out files are used to standardize the format for interfacing external systems.

M3 updates the out files whenever the material plan in (MMS080) is updated.

This field also indicates to the system whether pre-allocations are to be sent to the MHPREA out file.

(MMS005/H)

Download picking lists (for a specific warehouse)

… whether the picking list is downloaded to the MHPICL and MHPICD output files. Output files are used to provide a standard output format for interfaces with external systems.

M3 updates the output files when a picking list is released (picking list status 40).

These alternatives are valid:

  • 0 = The picking list is not downloaded.
  • 1 = The picking list is downloaded.
  • 2 = The picking list is downloaded and printed.
  • 3 = The picking list is downloaded and printed but not validated against warehouse integration in (MWS420).

(MMS005/H)

Download item master (for a specific warehouse)

… whether the item output file (MHITMA) and alias number file (MHIPOP) should be populated for this specific warehouse. Output files provide a standard output format for interfaces with other systems.

M3 updates the output file in these situations:

  • A download is initiated manually through the selection program (MHS630) or (MHS635).
  • Automatic downloads are defined through the M3 job scheduler. The item master is downloaded automatically according to a schedule.

(MMS005/H)

Retrieve receipts/pick list

… whether goods receipt or picking lists reported from external systems will be allowed to update M3 using batch entry in (MHS870).

Retrieved messages can be displayed and updated in (MHS850). Only messages with permitted order categories, as defined in (MHS860), are executed.

Note: There may be a conflict between opportunity cross-docking and integration to a warehouse management system.

(MMS005/H)

Retrieve stock transaction

… whether messages retrieved from external systems update M3 stock transactions when using batch entry in (MMS870).

The messages retrieved this way can be displayed and updated in (MMS850). Only messages with permitted qualifiers (as defined in (MMS860)) are executed.

(MMS005/H)

Alias qualifier

… which type of EAN code is to populate the alias number (POPN) field of the item master download file. This only applies if the 'Item master' parameter in (MMS005/H) is set to 1. These are the valid alternatives:

  • EA08 = EAN8, an EAN number containing eight digits
  • EA13 = EAN13, an EAN number containing 13 digits
  • DU14 = DUN14, a packaging variant of an EAN number
  • UPC = UPC number

(MMS010/E)

Allocatable

… allocation and must be set to 1=Yes, allocatable, and for the other location, to 0=Non-allocatable.

This field determines whether the balance identities created for the respective location should be allocatable.

It must be set to 1=Yes, allocatable.

When creating new balance identities in connection with receipts from stock, this code is obtained from the location for which the receipt is made. If there are exceptions, the allocation code may be changed in (MMS060).

(CRS165/B)

Number series

… the number series. The same ID may be used by other series if they belong to other types. For example, there may be a series A for order numbers as well as for invoice numbers, although they have separate number ranges and start values.

Number series type 16 with series A is used for internal stock messages.

Number series type 17 with series 1 is used for order-initiated stock messages.

(MWS010/E)

100 Auto print pick list

… whether picking lists are printed automatically when they are created.

Select 1=Yes.

(MNS310)

'Subsystem Job. Open'

… auto-start jobs used in this subsystem.

You have the predefined auto start jobs MHS855 –Order related messages and MMS855- Internal stock messages as predefined auto start jobs. These are for uploading. These start the MHS870 and MMS870 batch jobs.

(SHS050)

'Job Schedule Category. Open' All fields

You can schedule the download batch jobs in M3 Job Scheduler. See .

(SHS030)

'Job Schedule. Open' All fields

See .

(SHS031)

'Job Schedule Program. Open' All fields

See .

(SHS035)

'Job Schedule Field. Open' All fields

See .

(SHS231)

'Job Schedule Information. Open' All fields

See .
Related topics