Demo: the nightly ERP file that can't go away yet
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
handle a legacy batch interface pragmatically.
Draft outline details
Step by step
- Document the file: schema, schedule, volume, consumers, downtime windows, owner.
- Learn why it exists: the ERP offers no usable API for the posting module and finance depends on the cutoff.
- Wrap it: the integration layer builds and delivers the file; upstream systems see events and APIs.
- Add safety: control totals, reconciliation report, late-file alert, replay.
- Planned mistake: plan to switch off the file in release one. Fix: keep it as a supported interface with an exit trigger (ERP upgrade or vendor API) and date review.
- Record the decision and update the interface catalog.
Check your understanding
Why wrap a legacy file instead of removing it?
Show answer
It protects dependent processes while isolating the rest of the design from it.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.