Since updating to 10.2.600 we have found the inventory transfer screen frustrating as you have to clear the screen after each transfer to enter the next part number. On 10.2.200 we could just amend the part number as often we’d be changing just one digit, now we have to retype the whole part number each time. Does anyone know if there’s a way round this? It seems to be linked to the introduction of PCID to that screen, but it’s just a frustration to us!
This is a bug that has existed since 10.2.500.14. The issue is being addressed by PRB0227652, but I can’t find a targeted patch for when the fix will be implemented.
Thanks Travis, I’ve escalated this problem with Epicor now. Much appreciated
We just upgraded to 10.2.600 and are having the same issue. Our shipping team is not overly joyful about having to click the clear or new button between each transfer.
I submitted a support case referencing PRB0227652 also.
I was told by Epicor that they do not consider this a bug because there is a workaround and it was an intentional change. They do not plan to fix it.
Yes, they are not planning on fixing this.
From what I understand there was a different bug where the on hand quantity was not being calculated properly in the inventory transfer screen so when development fixed that, they made us start having to clear the screen. This then affected all of us who do multiple transfers of the same part…
Such a bummer.
I’ve tried escalating this with Epicor to no avail. To me it’s like having a problem with a car that means it stalls sometimes, so they make it so you have to turn the ignition off and back on again every time you stop at traffic lights. Fix the problem but make it a total pain to use. I wish there was a way of getting this feedback into the guys who actually made this stupid decision but there doesn’t seem to be unless anyone has any ideas!
Yeah this isn’t getting fixed.
The silver lining is that this is a UI design disagreement - and one in the soon to be legacy Smart Client. With the availability of REST, users are no longer limited to these UI design constraints. It is now possible to create your own web-based Transfer screen that is most efficient for your business needs and available on devices like tablets and phones.
Yes, I started fooling around in visual studio yesterday with this.
I got stuck on the GetNewTransferOrder Method which is the very first method I see in a trace.
The rest call is expecting a body of JSON filled out… I don’t understand where they are getting all of those values. I also don’t know if the method call is truly needed, but I know that the dataset it returns is used in many subsequent calls so maybe it is?
Very flexible though if you are adept at programming.
I recommend taking a page from the @Aaron_Moreng school of integration and make up your own API and just use the trace to create your Epicor Function library. One function might return the part information and another to do the transfer. Play around with it. Just keep the logic in the functions and simplify the API for the client. You’ll have to do the validations/error handling on your own but even those show up in the trace.
Is there documentation on functions in the ice tools tech ref guide?
You don’t need “workarounds” for properly functioning software. If the intent is that the user must clear it between entries, then that’s just how it works. And isn’t a “workaround”.
[ gets off soapbox ]
I agree I guess.
Just sucks they took away functionality. Didn’t really think it through in my opinion. And if this is the way they intended it to be used they did a horrible job with the UI.
It shouldn’t let you do anything with the previous transactions, there shouldn’t be a “new” button available if you have already made one transaction.
“This is how it works,” is not cool when it clearly isn’t working as it should. Fine if they take away the functionality, but change the UI and form to work the way you say it should.
Some forms (like the Inventory transfer) should be viewed as “one time use”. Because they create transactions, not records. Yes, the transactions are records. But you can’t pull up an in inventory transfer like you can a packer or order.
When you save an Order, it doesn’t clear the screen and expect you to make a new order from scratch.
Inventory Transfer used to create the partran records, clear some fields on the form(like: Transfer Qty, To and From Bins, Reference, Reason code, etc…), and update others (like the grid of Bins with QOH). But it would also leave some pre populated (like the PartNum). This was handy if you had to do multiple transfers for the same part. Not so much if a different part needed transfers.
If you needed to do a different part transfer you could click new and it added to the tree. You could process it and then click new again and transfer a different part number and it would save that one in the tree as well.
Then if you wanted to go back and transfer the same part you did three transactions ago, you could click that part in the tree, change the source (if needed), then click process. It would create another sub-entry in the tree under the original part.
This functionality no longer works.
You have to do a transaction, click process, then clear. Then type the part all over again if you want to make another transfer. It saves time to use the tree as a template, much like it does to use a job as a template or a quote as a template.
They took this away and now it is working as intended.
Ahhhhh … And the transaction log that can be printed is gone when you clear the form? So if you did 10 transfers, you’d have to print the log in between each of them, no?
Or am I confusing it with Qty Adj (which we definitely need the log to be printed, as we have a sign off procedure for Qty Adj’s)
Not sure, we aren’t really looking at the inventory transfer screen to see what happened. We are trying to use it to do transactions. And they used to make it easy to transfer parts over and over again by not having to click new, fill out the part number, the locations, etc… You could just select the part in the tree from a previous transaction and then use that again.