This happens in our Production environment. Our Demo environment, which is about a month or so old does not present with this issue.
We are having issues when creating a new Pack ID for a specific order. We open the Customer Shipment Entry screen, click on New Pack ID, and then type in the SO# and hit Tab, and then the background methods start to process before throwing this error:
Error Message Text
Application Error
Exception caught in: Epicor.ServiceModel
Error Detail
Message: Object reference not set to an instance of an object.
Program: Epicor.ServiceModel.dll
Method: ShouldRethrowNonRetryableExceptionClient Stack Trace
at Epicor.ServiceModel.Channels.ImplBase`1.ShouldRethrowNonRetryableException(Exception ex, DataSet dataSets)
at Erp.Proxy.BO.CustShipImpl.BuildShipToCustomerList(Int32 orderNum, String& shipToCustomerList)
at Erp.Adapters.CustShipAdapter.BuildShipToCustomerList(Int32 orderNum, String& shipToCustomerList)
When that error is thrown, the Shipment Entry form has populated the following fields:
- Ship Date
- Ship Via
- Customer
- Ship To
At this time, I click “OK” to dismiss the error and it pops up a 2nd time. Nothing on the Shipment Entry screen changes after the 1st error is dismissed and the 2nd appears.
My first thought was “Customization Issue”, so I ran it as the Base Form, which did not stop the error. My next thought was “BPM”, so I disabled all Methods that were tied to CustShip and hoped that maybe one of them was going to be the culprit. Unfortunately, that was not the case either.
I ran a Trace and performed the same steps, but nothing stood out in there either.
So now my mind goes to the data, thinking there must be an issue there. So I pulled all of the records for this order from the OrderRel table in both Databases (Production and Demo) and compared the 2 for differences.
I have taken the relevant parts of the results and have them posted here:
OrderNum | OrderLine | OrderRelNum | ShipToNum | ScheduleNumber | MarkForNum | DemandReference | ShipToCustNum | MFCustNum |
---|---|---|---|---|---|---|---|---|
150812 | 1 | 52 | 808844583 | 20230702-2417923 | 808844583 | 20230608 | 7073 | 7073 |
150812 | 1 | 53 | 808844583 | 20230723-2433531 | 808844583 | 20230628 | 7073 | 7073 |
150812 | 1 | 54 | 808844583 | 20230723-2433531 | 808844583 | 20230717 | 7073 | 7073 |
150812 | 1 | 55 | ------ | 20230813-2449161 | ------ | 20230724 | 7073 | 7073 |
150812 | 1 | 56 | ------ | 20230813-2449161 | ------ | 20230810 | 7073 | 7073 |
150812 | 1 | 57 | 808844583 | 20230815-2451822 | 808844583 | 20230925 | 7073 | 7073 |
150812 | 1 | 67 | 808844583 | 20230813-2449161 | 808844583 | 20230821 | 7073 | 7073 |
150812 | 2 | 1 | 808844583 | ------ | ------ | ------ | 0 | 0 |
150812 | 2 | 2 | 808844583 | 20230808-2447125 | 808844583 | 20230821 | 7073 | 7073 |
150812 | 2 | 3 | 808844583 | 20230808-2447125 | 808844583 | 20230807 | 7073 | 7073 |
150812 | 2 | 4 | 808844583 | 20230822-2457151 | 808844583 | 20231023 | 7073 | 7073 |
150812 | 2 | 5 | 808844583 | 20230822-2457151 | 808844583 | 20230911 | 7073 | 7073 |
150812 | 2 | 6 | 808844583 | 20230822-2457151 | 808844583 | 20230925 | 7073 | 7073 |
As you can see, there are 2 releases for line 1 that do not have a ShipToNum or a MarkFornum (which usually matches the ShipTo), and line 2 release 1 is missing a Schedule Number, MarkForNum, DemandReference, ShipToCustNum and MFCustNum.
With this being an EDI order, I would think that everything that is missing should be filled out, just like the rest of the lines are. Missing a Schedule Number, Demand Reference, etc., could easily cause problems, but I don’t know if they would cause the problem I am encountering.
Am I barking up the wrong tree? Or do y’all think I am heading in the right direction?