Unable to release a job. Receiving error "Record not available"

Kinetic ERP
1

Has anyone seen “Record not available” error when attempting to release a job? We are seeing this error on one job. The error is displayed when the user checks the “Released” checkbox and then selects “Save”. Detail for the error is below. I am thinking it is something the user(s) are doing but can’t figure out what.

System Information

==================

AppServer Connection:
Form Name: Job Entry
Customization Name: EspeyJobEntry_App.JobEntry
Menu ID: JCGO3001
Software Version: 11.2.300.10

============

Business Layer Exception

Record not available.

Exception caught in: Epicor.ServiceModel

Error Detail

============

##!Correlation ID:##! 9b0efe09-80ac-4469-8e89-6d04fa11b5d9
##!Description:##! Record not available.
##!Program:##! Erp.Services.BO.JobEntry.dll
##!Method:##! JobOperAfterGetRows
##!Line Number:##! 27538
##!Column Number:##! 17
##!Table:##! JobAsmbl

Client Stack Trace

==================
at Ice.Cloud.ProxyBase1.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer) at Ice.Cloud.ProxyBase1.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Ice.Cloud.ProxyBase`1.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Erp.Proxy.BO.JobEntryImpl.Update(JobEntryDataSet ds)
at Erp.Adapters.JobEntryAdapter.OnUpdate()
at Ice.Lib.Framework.EpiBaseAdapter.Update()
at Erp.UI.App.JobEntry.Transaction.Update()

2

Unfortunately Epicor’s error messages are not helpful. Somewhere in the job is a reference to a record (part, operation, supplier, etc) that isn’t there for some reason.

I’d copy the whole database to a test environment. Troubleshoot there, deleting subassemblies in the job until I located error. Could also copy just the job to a temporary job in your live environment, and troubleshoot there.

3

Thanks TerryR - the issue ended up being Orphaned JobOper records with no parent JobAsmbl record. Epicor support provided a data fix that deleted the orphaned JobOper records. Not sure how the user deleted the ASM that caused these orphans as we tried to recreate in our Pilot environment and could not.