Preparing inventory transfers between ERP systems.

Tyler Heshka · https://heshka.com/work/casebook/inventory-conversion

  • System Trace
  • Inventory operations · Business systems
  • 2 min read

A converter that selects finished materials, prepares import files and keeps records for checking and correcting transfers.

My part

Converter development, business-rule implementation, omission investigation and repair-file preparation.

Routine transfer

  1. Inventory export
  2. Finished-material list + transfer rules
  3. Group & format
  4. Prepared CSV
  5. Staff upload in receiving system
  6. Staff records outcome

Repair

Current-year records · prior matches and differences for review

  1. New finished-material list update
  2. Compare archived exports & import records
  3. Repair report + CSV when needed
  4. Human review

    CSV ready to upload

  5. Validate existing CSV
  6. Staff upload in receiving system

Saved exports · prepared files · conversion and upload decisions

The converter prepares the files. People review exceptions and upload them. Repair uses the saved records and returns to the same upload process.

Decide what should move.

During an ERP transition, I built a converter to prepare inventory transfers between the existing and replacement systems.

The export contained more than we wanted to transfer. It included finished material alongside work still moving through production. Preparing the import meant separating what belonged in the new system, reshaping the data and producing a file the receiving system could accept.

The converter selects the relevant transfer records using a maintained list of finished materials, groups the quantities and prepares a CSV in the format the receiving system expects.

Prepare the file. Keep the record.

Another staff member uses the converter for routine transfers. The application prepares the file and opens the receiving system’s upload page; the staff member uploads it and records the outcome back in the converter.

The converter keeps source exports, prepared files and a log of conversion and upload decisions. Its upload record reflects the outcome recorded by the operator, giving us information to refer back to when something needs investigating.

Checking and correcting transfers.

When new finished materials needed to be included, I used the saved records to check earlier transfers and prepare repair import files for omitted material.

I added a way to validate and use a prepared repair CSV without running the original export through the converter again. I also added a report that flags material which may belong on the finished-material list. It is still a review step: the report does not add anything automatically, and the operator can continue with the prepared file or defer it.

For current-year repairs, the tool can also work back through archived exports and prior import files after new finished materials are identified. It prepares a report and, where needed, a repair CSV for someone to review before uploading.