LIMS to ERP: the number arrives, but the meaning changes

Situation and intended use

LIMS transfers approved test results to ERP. ERP uses the accepted disposition to control material issue. The transfer includes sample, material lot, analyte, result, unit, method/specification context, approval status, and message identity.

A message can arrive successfully while carrying incorrect meaning. Network success alone does not establish correct business behavior.

Varied challenges

1. A source result in mg/L reaches a destination expecting µg/L.
2. Two lots have similar identifiers and are mapped incorrectly.
3. A timeout causes the sender to retry an already accepted message.
4. Messages arrive out of order, with an earlier status following a later approved status.
5. The result arrives without the required approval state.
6. An unknown unit code is treated as a default unit.

Proposed controls and evidence

Use controlled mappings, explicit validation of required fields, transaction identity, defined duplicate and ordering behavior, and an owned exception queue. Challenge the receiving business action as well as the message content.

Completed test extract — fictional: “IF-T08 resends an accepted transaction with the same business identity. The receiver identifies it as a duplicate and does not create an additional disposition event. Source and destination logs retain the transaction association. A resend with altered content under the same identity is routed for investigation under the defined rule.”

That behavior is an example design choice. The approved interface specification must define the actual rule.

Worked outcome

Testing finds that an unknown unit becomes the destination’s default unit. The interface is not released for result-driven disposition until the behavior is corrected and the affected mapping and exception paths are reassessed. A passing connectivity test cannot compensate for this failure.

After correction, invalid units are held for review, alerts reach the designated owner, and approved recovery prevents duplicate disposition. The team demonstrates that material issue remains controlled while messages are unresolved.

Monitoring and reassessment

Monitor unresolved messages, repeated retries, unexpected unit codes, reconciliation differences, and changes to source or destination master data. Reassess on mapping, schema, status-rule, or receiving-process changes.

Challenge: Every transferred result matches numerically. What could still be wrong?

Worked answer: Sample identity, units, status, specification context, timestamp interpretation, or record association may be wrong. Compare meaning and downstream behavior, not only numbers.