GenFrontier homeScope a project
Menu
Filed under
Deliver toIT leads, EDI coordinators and project managers scoping integration work

Integration inventory worksheet for ERP, WMS and TMS

List every interface between your ERP, WMS, TMS, carriers and trading partners, with its direction, method, trigger, volume, owner and failure handling.

Plan integration work
resources / integration-inventory-worksheet
An old telephone operator's switchboard with rows of jacks and several patch cords plugged between them, one cord in red

Worksheet

The rows are a fictional example. Edit any cell, add or remove rows, then download a CSV to share with your team. Nothing leaves your browser.

InterfaceFromToDataMethodTrigger and frequencyVolume per dayBusiness ownerWhen it failsRemove

The interface that delays a go-live is often one nobody listed: the nightly file someone emails to a supplier, the carrier portal a coordinator checks by hand, the spreadsheet upload that keeps the item master current. This worksheet lists every place data moves between your ERP, WMS, TMS, carriers and trading partners, including the manual ones, with enough detail to estimate, build and test each.

The columns

Column What to write
Interface A short name for the data flow, such as “Advance ship notices”
From and To The sending and receiving system or party
Data The business records and key fields that move
Method EDI, API, flat file, database, manual, or “To decide”
Trigger and frequency The event or schedule that starts it
Volume per day An ordinary day, with the peak in a note
Business owner The person who decides what correct looks like
When it fails What happens to a rejected or missing message, and who is told

How to use it in a project

  1. Start from the documents, not the systems diagram: purchase orders, ship notices, receipts, invoices, labels and status updates. Each one moves from somewhere to somewhere.
  2. Walk each process step and ask where its data came from and where it goes next.
  3. Write one row per data flow per direction. Purchase orders out to suppliers and acknowledgments back are two rows.
  4. For EDI, record the transaction set and version, for example 856 Ship Notice/Manifest or 940 Warehouse Shipping Order, and whether the partner’s specification has been collected.
  5. Use “To decide” rather than guessing the method. An open decision is visible; a wrong guess is not.
  6. Download the CSV and keep it as a living document through build and testing.

Reading the example

The five fictional rows cover the item master, purchase orders, advance ship notices, receipts and carrier status. A few details are worth copying:

  • Advance ship notices come from suppliers by EDI with SSCCs and lot numbers. When one fails, it goes to an unmatched ASN queue: an ASN that does not match an open purchase order is parked for a person to resolve, not dropped.
  • Receipts to the ERP name the business consequence of a failure, “hold invoice match”, not just “error logged”. Finance knows what to expect.
  • Carrier status runs every 15 minutes at about 2,000 events a day, and the failure rule watches for silence: a stale feed alert after 2 hours. An interface that stops sending is a failure too.

What good looks like

  • Manual interfaces are listed: re-keying, emailed spreadsheets and portal checks. They are often the first candidates for automation.
  • Every row has a business owner, not only an IT contact.
  • Volumes include the peak, because interfaces that cope on an ordinary Tuesday can fall behind in the last week of the quarter.
  • Every “When it fails” names a queue, a retry rule, an alert and a person.
  • Rows connect to requirements and tests, so each interface is checked in user acceptance testing.

Who should fill it in

  • The IT lead or integration architect drafts the list from systems and jobs.
  • The EDI coordinator adds trading partner details, transaction sets and versions.
  • Business owners confirm the data, triggers and failure handling for their area.
  • The project manager tracks open rows and “To decide” methods until each is settled.

What happens next

In a project, this worksheet is part of the requirements. Each row becomes an interface design, an estimate and at least one test in the UAT test plan. Shipment events in the tracking milestone map usually add rows here. When you are ready to build, ERP, WMS and TMS integration describes how we build the interfaces, and requirements analysis covers the document this worksheet feeds.

Scope your project.

Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.