I’m trying to set a default value for the ECO Group field when creating a new Revision (Rev) in Epicor Kinetic. The reason for this is that I want to import BOMs through the API, but to create child components, the ECO Group must be associated before I can use the API to POST child items. I found some information that suggested using BPM to achieve this, but my attempts haven’t been successful so far.
I would like to know if this functionality is achievable with BPM, and if so, how exactly I should configure the BPM to ensure the ECO Group is set correctly when a Revision is created. Alternatively, is there any API that allows me to directly POST BOMs without needing this manual setup?
I would think only time you would have one like this might be a case for DMT not a BPM unless you can give more information it would be difficult to suggest otherwise.
My goal is to use the PLM system to create a complete BOM through the API. Since I’m still new to this, I’m not sure what the best approach is and how to proceed. Currently, I’m able to create parts via the API, but when it comes to creating the BOM, as shown in the screenshot, the ECO Group value can’t be set via a POST request. It must be added manually through a button, which means without associating it with an ECO Group, I can’t create child parts through the API.
Are there any alternative methods I could use to solve this issue?
For complicated integrations, many find it useful to create an Epicor Function to do the heavy lifting at the server. The Engineering Workbench business object can do all this for you, including a method that will add child parts from a CSV. The advantages are it is less chatty over the wire and that you don’t have to put logic in your client and test for changes with each upgrade.
I provided one such method the DMT tool. AFAIR (about 2 yrs since I created a MOM), to create a MOM you need to:
Create the base part
Assign the Operations needed to create/mfg said part (unless this is a Phantom MOM/BOM)
Assign the Materials needed to above operations (or a parent assembly in Phantom MOM/BOM scenario) to create/mfg said part
I agree with @Mark_Wonsil an Epicor Function would provide the “heavy lifting” you need in this scenario via the Engineering Workbench BO allowing you to provide your “function” the data needed to utilize the EW BO to create the MoMs.
*Note: In Phantom MoM scenarios operations can cause issues (almost guaranteed) do not use unless you are single company & site.
The reason I’m looking to transfer data to Epicor via the PLM system is to streamline the process by selecting the data directly in PLM and then sending it to Epicor. After hearing your suggestions, I understand that the DMT tool would be required, but manual intervention in this process does not meet my goal of automating the transfer.
I’ve also tried using the Engineering Workbench API to create child parts, but I encountered the issue of “cannot be created.” I believe this is related to the ECO Group, as when I manually associate the Part with an ECO Group and then use the Engineering Workbench API, I’m able to create the child parts.
Therefore, I feel the only missing step is associating the Part with an ECO Group. Is there any way to resolve this issue, such as using a default ECO Group or setting it via API? Any guidance or alternative methods would be greatly appreciated.
Additionally, I followed the installation guide step by step and downloaded the XML from the Epicor web for language import. However, it seems that the installation was not successful. When I attempted to run the process, there were no errors displayed, but the installation didn’t complete correctly. If you have any suggestions or could assist with resolving this, that would be extremely helpful.
