Skip to content
Service-King

Knowledge base · Service-King

WMS and MES integration: data, confirmations and errors

The hardest part of integration is often not sending the message, but figuring out which system is right and what to do after the error. Before you start, write down the data and responsibility for each operation.

Service-King team Published: Updated:

Transfer of components from warehouse to production.
Topic illustration · Service-King

Define who owns the data

Data exchange questions
AreaWhat to determine
RecordsWhich system assigns indexes, units and versions.
StatesWhere a binding record of movement and correction is created.
JobsWho creates, changes and cancels a requisition.
ConfirmationsWhen collection or return is deemed to have been made.
ErrorsWho explains rejections and resumes communication.

Define the event first, then the message

"Issuance" may mean document approval, physical collection or consumption settlement. If the systems understand the same status differently, a technically correct transmission will still produce an incorrect result. Integration requires matching operation meanings.

For each event, record the moment of occurrence, data and expected result. Determine whether the second system should only receive information or also confirm acceptance. Only then do you choose the format and method of communication. The description should also be understandable to the process owner, not only to the programmer.

Data ownership must be unambiguous

Records, states, locations and orders are not always created in the same place. It is worth specifying a parent system for each area. Two independent sources of binding status require reconciliation, not hope that they will always agree.

An update rule is needed when changing an index or unit. When making a correction, specify who does it and whether the information returns to the other system. Service-King can provide equipment flow data and agreed operations, and the scope of full cooperation should be confirmed for specific systems and interfaces.

One event should not create two stock movements

The message can be resent after a network outage. Integration must recognize repetitionsso that the same return does not increase your balance twice. Determine the operation ID, event sequence, and behavior after partial execution.

Also check the reverse situation: the physical check-out occurred, but the other system rejected the save. The operator should see that the matter requires reconciliation, instead of making further moves on a seemingly correct condition.

Where Service-King fits in the workflow

Records of tools, instruments, parts and machines can complement the production process. For example, the history indicates which piece of the device was issued for the position. This does not automatically mean ready integration with every MES or ERP.

Prepare the specifications: interfaces, fields, frequency and required level of confirmation. CSV file, periodic import and online communication are different technical and organizational scope.

Reconcile records after an interruption

Once communications are restored, simply sending outstanding messages may not be enough. In the meantime, operators could make adjustments, cancel the job, or change the assignment. You need a comparison rule and a list of things to clarify. Record which data takes priority and who can approve the discrepancy. The integration reception should include such a scenario, because only it shows whether the solution will cope beyond the ideal course of the demonstration.

Related topic: one recording source.

What to describe in the integration specification

Minimum data exchange contract
AreaDeterminationTest
IdentitySystem IDs and mapping.Unknown index or item.
OperationUnique number and meaning.Retrying the same operation.
TimeSource and order of events.Delayed message.
QuantityUnits and conversion rules.Partial return or cash on delivery.
StatusAcceptance, rejection and reason.Validation error.
CorrectionAccountability and change trace.Disaster reconciliation.

A retry must not create a duplicate stock movement

After a network interruption, the system may resend the message. What is needed is a way to recognize that an operation has already been handled. Transport confirmation and operation confirmation are different pieces of information.

Consider a situation where the writing on one side was created but the response was lost. The user should not perform another check-out just to see the green status. The integration problems view should indicate issues that need to be clarified and allow the exchange to safely resume according to the established rules.

Acceptance tests should cover failures and reconciliation

Test a correct stock movement, partial fulfilment, cancellation and a message containing an incorrect item record. Then test recovery after an interruption. Corrections or other operations may have occurred in the meantime, so transmitting the queued messages alone may not resolve discrepancies.

Record compliance criteria and responsible person. The acceptance result is intended to show that the warehouse and production can continue working with reliable data. System ranges are described WMS, process monitoring and device communication layer.

Scenario: an operation is recorded in only one system

The warehouse physically released items and recorded the movement, but the production system rejected the message. The status of both sides is no longer consistent. Integration error should be a visible issue to be resolved. Merely retrying without checking may create a duplicate or overwrite a later correction.

First determine whether the problem is transport, validation, or interpretation. Confirmation of receipt of the message does not necessarily mean acceptance of the operation. The user should know the status and the person responsible for the next step. It is useful to refer to a clear incident number so that both parties are talking about the same record.

If a return has occurred in the meantime, consider event order and dependencies. Manually reversing the state in one system can create further discrepancies. The procedure should define permitted corrections and when reconciliation takes place. Do not resolve the problem by deleting a message without establishing what happened to the physical stock movement.

In project receipt go such event controlling. Check if the history allows you to reproduce the result and if it is safe to resume. Measure the diagnosis time, not just the time of data exchange in the correct course. This will show the actual cost of maintaining the integration and the quality of cooperation between the teams responsible for the systems.

Arrangements to record after this scenario
AreaPractical arrangement
EventUnique operation number.
StatusTransport separated from acceptance.
ReasonValidation, data or communication.
OrderIncluding subsequent moves.
CorrectionCorrect permissions and change trace.
CollectionSafe restart and consistent result.

Integration acceptance test scenarios

  • Correct issue and return.
  • Repeat the same message.
  • No known index or item.
  • Cancellation or partial fulfillment.
  • Communication lost and reconciled upon return.

See production identification and machine and parts records.

Questions worth clarifying before implementation

Is online integration always better than file integration?

Depends on freshness and process required. Periodic import may be sufficient for some tasks. Ongoing replacement requires greater attention to errors, retries, and availability.

Who should approve the specification?

Process and data owners and representatives of integrated systems. The mere technical compatibility of the fields does not confirm the correct interpretation of the operation.

Does CSV export mean ready integration?

No. You also need agreed fields, identifiers, validation, accountability and a way to handle the result on the recipient's side.

Go to solutions related to this topic

Free consultation

Let's agree on the data flow between the warehouse and production.

Describe the systems, required operations, and current data exchange issues. We will prepare responsibilities and scenarios for testing.

Contact Service-King

Describe your case.

Fields marked * are required.

1. How can we help? *Your message will be sent to: Technical support.
2. How can we contact you?
I prefer contact:
3. Case details

Go to the contact form

Website language

Choose a language.