4 ms·
I worked one summer (2014) manufacturing emergency stop buttons for ABB. We used SAP for our incoming orders. Each order was printed on paper as some kind of r
by widforss 7y ago
I worked one summer (2014) manufacturing emergency stop buttons for ABB.
We used SAP for our incoming orders. Each order was printed on paper as some kind of report from SAP and put in our physical inbox. When we had manufactured buttons for an order, we would go to a desk with two computers, both logged in to SAP. With the first computer we would scan a barcode from the order to find it in the system, mark the order as done, and print a second paper containing the order.
Then we would proceed to the next computer, scanning a barcode from the second paper, and produce a freight order for the outgoing warehouse. This was printed to a third paper, and attached to the buttons, before they went to the outgoing warehouse.
Note that the freight order did not work as a waybill, so the process of shifting paper was probably conducted a couple of more times before the order reached the customer.
For someone really used to working with computers and not against them, it seemed rather innovative to print a paper to transfer an order to another computer two feet away. It was a learning experience and greatly motivated me to go get some higher education.
- jedberg 7y agoWhat did you do with the paper you used between the two computers? Did you toss it or was it filed somewhere? If it was filed, my guess was that it was an internal control measure. They wanted to make sure there was a paper copy of every transaction for audit purposes, and what better way to make sure of that then requiring the paper to move the order forward? If you tossed it, then it sounds like they were just too lazy to implement something other than the default config. :)