It starts out so simple, just a BAQ of transfer orders. Then I think, “Can a transfer be closed, voided, etc.?” And here is where I am at.
I closed a line in the classic UI and it closed the whole order (which had 5 other open lines)
I closed a line in the Kinetic UI, and it closed the line only.
a. (This is the one thing that worked as expected. But…)
There is no way in either UI to reopen a line.
Made a uBAQ;
a. It let me reopen the order
b. It did not reopen any line
Tried DMT for reopening lines
a. There is no detail DMT specifically; you use the generic Transfer Order DMT with fields like TFOrdDtl#TFOrdLine. OK fine.
b. Kept saying TFOrdDtl record not found
c. Then I thought to try the TFLineNum (a string) instead of TFOrdLine (an integer). And it processed, but it did this to lines 1 and 5…
We have a handful of old transfer lines visible in time phase due to the transfer order being forced closed when the order line was still open. We have no way of reopening and fixing it. I believe the only solution is a data fix from epicare and I have just not got around to logging a case. The entire transfer module is a shitshow imo
Thank you for the validation/sympathy. OK, so basically the best bet (at current state) sounds like I should make a BPM to just deny anyone the ability to manually close a line or order.
Requisitions are a mess, that’s my other peeve. But you can avoid those if you want.
But you can’t exactly avoid transfers - so it is strange to me the lack of complaints here on the forum. What are people doing instead???
We use transfer orders all of the time and I have also wondered why there was not much on this help site about them and why Epicor never addressed the most basic issues over the years. One version didn’t even provide the transfer order workbench in the standard menu! I suspect many here have one company or use different companies, inter company POs, or different warehouses and transfer parts with these setups.
I think of transfer orders as the red headed neglected stepchild of Epicor ERP. We lived for so long with the darn in-transit ones not being counted… nightmares. Might not seem like a big deal but getting an additional unfirm job for a parent with its associated 600 parts planning suggestions for additional jobs and purchasing and transfers, all so we could have a job in another state to do lab testing before shipping.
We still see some not needed suggestions to transfer despite firm transfer in there already; days of supply on the part being transferred helped. Our users would LOVE to have lock quantity and lock date on it similar to POs and Jobs.
I admit to backdoor method making a fix for these in the past when our hands were tied, but haven’t had to do that in a few years. UBAQ and DMT did not work there for us either.
I have also seen behavior of the transfer (whether get extraneous suggestion to transfer another) act differently if the transfer was made originally from firming a suggestion vs manual creation of one. Two other main culprits of problems we get are due to jobs getting setup with transfer part in BOM being pulled from other plant. This makes auto transfer and all hell breaks loose on those for us. So we don’t allow them (bpm) to setup pull from different site / warehouse on a job.
The other one is something going wrong on shipping or receiving, wrong one, etc, that is hard to fix.
HTH some or at least makes you know WE ARE HERE WE ARE HERE WE ARE HERE!
Nancy
Thank you. Yes I think I’ve seen you post the most over the years on inter-site stuff than anyone.
But I want to say that @aosemwengie1 has an Idea out there about mass-receipt of transfers.
Yeah I deliberately titled this “today’s complaints” because I knew I’d never finish typing if I listed everything I knew of. But it does make me want to do some sort of wiki post. Want to - I probably do not have the motivation to actually do it.
Anyway, I am trying to make a dashboard to help wrangle the madness. It’s long overdue.
Funny rereading this list after so long and seeing how almost none of these issues have been addressed. I would add to this list the ability to receive a different quantity than what was shipped on the transfer order.
But what should happen in that case if your idea was carried out? How would it reconcile the extra or missing pieces from the other site? Some sort of financial variance? And what about the quantity on hand at the sending site?
To that end, is this allowed with intercompany PO/SO? (We only have sites; no other companies.)
When I built a custom solution for this because I finally gave up on the ootb functionality, if you received less than the shipped quantity, the variance returned to the original site but in a special non-nettable variance bin. Then the inventory manager had to figure out what happened and deal with it accordingly. Either transfer back into stock, qty adj out, or put it on the next transfer order. But at least the receiving site’s stock was not forced into inaccuracy the way regular TOs work.
Oh I know the other absurdity I came across (again?) recently:
When you make a transfer order - which is a request for parts - you have to specify what bin the other site should pull the parts from.
WHY? How would a user know or care where stock is located in another building? Or ever? You don’t specify it on a sales order!
Then the other irony is that if you ship direct, then the system makes the TO for you, but it leaves the warehouse/bin blank, and that passes muster. Nice double standard, lol.
I did find how to make a default transfer shipping bin, so OK, there’s that.
Ha, well I doubt that - I am sure we are not the problem - but there is truth in the idea that we might learn something. I never run out of “I never knew that” days with Epicor. If nothing else, it will confirm what we all know already.
We are opening a second site at the end of Dec 2025. We have 3 of us signed up for the Dec 16th webinar and I decided to see what I would come across here as a little prep. You have all thoroughly shaken my confidence. So much appreciation to you for that. Any quick advice any of you would like to share? Something that you wish you had known at the outset as we begin?