Is it possible to send UD fields across the ICPO process? I am wanting to send a single text field across for a BPM to work. There is no way to trace this, as the intercompany process handles all of the transactions.
I’m just curious if anybody has figured out a way to make it work. The big issue is it is across companies, so there is no way to use a standard lookup query because the users don’t have access to each other’s companies.
Yeah - I don’t think the IC process takes UD fields, but I haven’t tested it in v11 yet.
I would have hoped that if we extend a table with UD fields, that they would copy just the same, but in thinking about it, the IM tables that the transaction passes through do not get the same extended field treatment, so it probably won’t work.
Can you hide it inside one of the many unused Epicor fields and then take it back out using a BPM or code in the UI?
The issue is, it copies it from POHeader to IMOrderHed, so adding the field to the POHeader isn’t enough.
When you add in the UD field, it shows up in the IM.IMOrdeHed table, but there’s nothing I could find to trigger off of.
I ended up creating an external BAQ that gets the information based on Company/PONum. I just called that in the SOPOLink BPM and it worked like a charm.
So, the UD field gets to the IM table but the data does not?
Sounds like an Epicor Dev ticket! Do you have an open EpicCare case on it? Id’ press them on the ‘as designed’ or ‘submitted to dev’ resolution status before I’d let this go.
I was going to suggest the query, or even a SQL Trigger, but I thought maybe embedding and retrieving would be easier and more available to Cloud users.
I don’t think it’s a DEV issue. Saving the PO, I can write the data to the field. Transferring it to the IMOrderHed is not in the cards. I could propose an idea, but I don’t think there would be enough support to implement it.
I even thought about sending a text file to the EpicorData directory and consuming it when they process the SOPOLink. But the query was much easier…
True - probably not enough support, but internal to Epicor it might be different. MC/IC processing is where Epicor really could focus some work to make it better & more reliable. I would have thought that if they allow UD fields on a transaction table, then those fields should follow that transaction - in my opinion of course.
We’ve thought about switching to internal EDI just to make it so issues can be fixed. There are so many things that stop the IC process…
And it’s not transparent. The same is true for the Export to Mattec program. There’s an error log but not always complete. Like IC, it’s a black box.
Rant
Wouldn’t it be nice if there were only one import/export method for each object, including Sales Orders, Price Lists, Labor, material movement, customizations, BAQs, Configurators, etc.? The format would be JSON. DMT would just be a CSV/Excel mapper to JSON. Everything would be out in the open to inspect for issue. No DLLS involved. Fewer programs to manage. Web friendly.
End Rant