We have recently found an issue on storing a value on the server table and the issue happens exactly on a rest service using rest-erp and there isn’t an issue on payload. so the issue must be on the API function on the server. As our epicor environment hoisted by the epicor team, we have checked and found that we can update the rest services using “Epicor Service Connect”. while installing that, it requires a (.lic) file. So, If we can update the rest services using the Epicor Service Connect. Kindly share more info about how and where we can get the license file. If we can’t update the rest service using the “Service Connect”. Kindly suggest a way so that we can check and update the rest services on the server.
Backup and give us more information on what you are trying to do and why.
Explain the business problem and we’ll guide you to the technical solution.
And… welcome to the forum.
1 Like
Hi @klincecum
Thanks for your response
For your info, we are using Epicor Kinetic 2023.2.11
Here is the break down of the problem we are facing
The problem occurred on Job receipt to Inventory while submitting the job from ATC job approval page. The issue happens some times when submitting the job, it stores the overall production quantity on the partTran table’s tranQuantity instead of storing the completed quantity by the employee. we have listed an example below.
Suppose a job with production quantity of 80000 is created and the employee completed 20000 quantity. When the supervisor approves the job on the ATC job approval page, It stores the quantity as 80000 instead of 20000 on the partTran table. As the manufacturer receipts page
which used partTran table display the quantity as 80000 which is the issue
Regarding the issue, we have checked the functionality of the submit event on Application Studio. As there isn’t any issue on that. so, we hope that the issue might be on the rest service where it creates a record on the partTran table. we have shared the screen shot of the rest service for your reference. kindly review it. Also, this error only occur for some jobs and we couldn’t find the exact reason behind it. so that, we have planned to check the rest service.
This sounds more likely user error or a misunderstanding of the process.
It’s possible you’ve encountered a bug, but likely someone else would have encountered it on this bo.