Record MFS telegrams. Reproduce bugs in minutes.
Record MFS telegrams from the production system and replay them exactly in test or development. Reproducing a bug takes minutes instead of weeks.
A tote stops at a communication point. The shift logs it, the ticket says “happens sometimes”, and by the time development looks at it the situation is long gone. Nobody can say which telegram arrived in which order, or whether an acknowledgement was missing at all.
So the search starts from scratch every time: read logs, guess, rebuild by hand, hope it happens again. Meanwhile the fault reappears on the next shift.
TeleTrace records the real telegram traffic and replays it against a test system. The fault happens again, on demand, in a system where you are allowed to debug.
Capture every MFS-relevant telegram from the production system, filtered by communication point, telegram type, handling unit or time window.
Asynchronous, with no interference in the live telegram flow. Storage of your choice: database table, file system or an external bucket.
Play recordings back against development, test or sandbox, one to one. Original timing, accelerated, or step by step.
A whole day of operation, a single handling unit run, or a targeted burst of telegrams. With or without response telegrams.
A Fiori cockpit with timing diagrams, telegram diffs between two runs, and automatic detection of gaps and out-of-order sequences.
Understand instead of guess. Is the jam caused by telegram timing, by a missing acknowledgement, or by customising?
Runs in namespace /FROEH/TT, no modifications to the SAP standard. Guided IMG path. Effort: 30 minutes including a smoke test.
From a Fiori tile or scheduled via ABAP. Runs as a background process alongside the MFS, with no performance impact on live control.
Pick a recording, pick a target system, play it. The bug is reproduced, the diff report is there, and handing it to development takes minutes.
Scales with the number of systems. All prices exclude VAT, no setup fee.
Joining early means permanently preferred pricing, direct influence on the analysis cockpit, and personal support during onboarding. In return I ask for an honest account of your experience after three months of use.