Incoming ICPO Suggestions Process All produces null reference error

Anyone ever encountered the rather ambiguous “Nullable object must have a value?” I’ve read other posts where this occurred in various other programs after an upgrade, and we did upgrade in April from 10 to 2022.1.

We get this in Incoming ICPO Suggestions and it prevents the creation of the SO. We have tried duplicating the PO in our test environment, running multico, and then trying to process the new suggestion with the same result.

Support suggested checking the IMOrder tables for null values on that ICPONum, but then said that none of the ones I reported should be causing the error. Still, I tried inserting values into all the UD columns, no change.

There are no customizations, and no BPMs hooked to SOPOLink which seems to be the method being called. But just to be sure, I also tried completely disabling BPMs on the Test environment appserver, still no change.

Support is now suggesting either creating a new PO, or sending them the db.

Application Error

Exception caught in: Epicor.ServiceModel

Error Detail

Message: Nullable object must have a value.
Program: Epicor.ServiceModel.dll
Method: CallWithCommunicationFailureRetry

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.SOPOLinkImpl.ProcessSuggestions(Boolean& needsConfig)
at Erp.Adapters.SOPOLinkAdapter.ProcessSuggestions(Boolean& needsConfig)

Do IC suggestions use PartDtl as the source to create suggestions? I have had null due dates in PartDtl cause issues, so have a bpm watch for them and set the dates as needed.

This ended up being nulls in NeedByDate and ReqDate on IM.OrderRel. I had to send the db to support for a datafix.