Since the upgrade to 2024.1, creating a quote for a customer that is not 'valid ship to' shows this error: The main Ship To is not valid for the customer

We were using the quote module to create a sort of budget for a project. When creating the customers, we didn’t check any of the valid payer, valid sold to or valid ship to checkboxes. That way, people weren’t able to create Sales Orders, shipments,etc.

However, since the 2024.1 update, it’s not possible because this error shows everytime:

image

Is there any way to bypass this or anyone know if it’s intentional?

1 Like

Is the Valid Ship To flag enabled in the customer record

I know that it’s the way to fix it but before 2024.1, this error message didn’t show up (I tested it yesterday in 2023.2 and 2024.1)

Our admin departement didn’t want to activate the Valid Ship To checkbox since we are doing a credit inquiry before. For the time being, I had no choice to activate that checkbox on every customer because it prevented the project creation in our process

1 Like

Trying in 2024.2 one moment

Tried doing it with Addison in Demo with it Valid Ship to off and no problems.

Created a new customer with the same and no problems…

Hold on… Is that a BPM message. I think it is.

Check any BPM possibly the quote change customer method…

Maybe this would solve your problem of managing shipments to customers.
When a customer is created, it is placed on credit hold by default.

If a customer is on credit hold - the default configuration is to stop the shipment.
When an order can be shipped (customer paid COD, other reason), the credit hold can be overridden on the sales order to allow shipment.
Typically, if you are checking/verifying credit with a customer for each order, you shouldn’t take a customer off of credit hold.

I looked at it yesterday and it happens on the Data Directive on QuoteDtl, which you cannot catch the error I think. If it was in a Method Directive, there’s some options to catch the error and not pay attention to it but not in that case

Yeah that’s already being checked on every new customer. To be fair, I don’t think that once the Valid Ship To customer is checked it creates much more problems. It can probably be configured as an alternate ship to or something like that but you can’t do a Sales Order unless the customer is checked Valid Sold To and you can’t do a Customer Shipment without a Sales Order

What’s in the detail of the error?

Business Layer Exception

The main Ship To is not valid for the customer.

Exception caught in: Epicor.ServiceModel

Error Detail

Correlation ID: 20510018-441f-42ab-9205-97bcdda90e3f
Description: The main Ship To is not valid for the customer.
Program: Erp.Services.BO.Quote.dll
Method: QuoteHedBeforeUpdate
Line Number: 22177
Column Number: 17
Table: QuoteHed
Field: ShipToNum

Client Stack Trace

at Epicor.ServiceModel.Channels.ImplBase.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer)
at Epicor.ServiceModel.Channels.ImplBase.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Epicor.ServiceModel.Channels.ImplBase.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Erp.Proxy.BO.QuoteImpl.Update(QuoteDataSet ds)
at Erp.Adapters.QuoteAdapter.OnUpdate()
at Ice.Lib.Framework.EpiBaseAdapter.Update()
at Erp.UI.App.QuoteEntry.Transaction.Update()