Invalid Mark For, Shipping Module

This is an Epicor 9 issue, one of the companies we just purchased is using it… For now. MWAHAHAHA!

Anywho! I do have an error I’ve never seen before even in my Epicor 9 days from the Shipping Module, Invalid Mark For when trying to ship. Now the order is coming off of Credit Hold and it was relieved from Credit Hold.

Here’s the entire Error:

Exception caught in: Epicor.Mfg.BO.CustShip

Error Detail

Message: Invalid Mark For.
Type: Error
Program: Server/bo/CustShip/CustShip.p
Method: shipDtlBeforeUpdate
Table:
Row:
Field:

Stack Trace

at Epicor.Mfg.Proxy.CustShipImpl.UpdateMaster(CustShipDataSet ds, Boolean doValidateCreditHold, Boolean doCheckShipDtl, Boolean doLotValidation, Boolean doCheckOrderComplete, Boolean doPostUpdate, Boolean doCheckCompliance, Boolean ipShippedFlagChanged, Int32 ipPackNum, Int32 ipBTCustNum, String& opReleaseMessage, String& opCompleteMessage, String& opShippingMessage, String& opLotMessage, String& opInventoryMessage, String& opLockQtyMessage, String& opAllocationMessage, String& opPartListNeedsAttr, String& opLotListNeedsAttr, String& shipCreditMsg, Boolean& cError, Boolean& compError, String& msg, String& opPostUpdMessage, Boolean& updateComplete, Boolean& checkComplianceError, Boolean& changeStatusError)
at Epicor.Mfg.UI.Adapters.CustShipAdapter.UpdateMaster(Boolean doValidateCreditHold, Boolean doCheckShipDtl, Boolean doLotValidation, Boolean doCheckOrderComplete, Boolean doPostUpdate, Boolean doCheckCompliance, Boolean ipShippedFlagChanged, Int32 ipPackNum, Int32 ipBTCustNum, String& opReleaseMessage, String& opCompleteMessage, String& opShippingMessage, String& opLotMessage, String& opInventoryMessage, String& opLockQtyMessage, String& opAllocationMessage, String& opPartListNeedsAttr, String& opLotListNeedsAttr, String& shipCreditMsg, Boolean& cError, Boolean& compError, String& msg, String& opPostUpdMessage, Boolean& updateComplete, Boolean& checkComplianceError, Boolean& changeStatusError)
at Epicor.Mfg.UI.App.CustShipEntry.Transaction.Update()

Inner Exception

ERROR condition: The Server application has returned an error. (7243) (7211)

Inner Stack Trace

at Progress.Open4GL.DynamicAPI.Session.runProcedure(String requestID, String procedureName, ParameterSet parms, Boolean persistent, Boolean internal_Renamed, Int64 procId, MetaSchema localSchema, Int32 stateModel)
at Progress.Open4GL.DynamicAPI.Session.runStatelessProcedure(String requestID, String fullProcedureName, ParameterSet inparams, Object procId, MetaSchema localSchema, Int32 stateModel)
at Progress.Open4GL.DynamicAPI.PersistentProc.runTheProcedure(String requestID, String procedureName, ParameterSet parms, MetaSchema schema)
at Progress.Open4GL.DynamicAPI.PersistentProc.runProcedure(String procedureName, ParameterSet parms, MetaSchema schema)
at Epicor.Mfg.Core.CallContext.CallContextPersistentProc.runProcedure(String procedureName, ParameterSet parameters, MetaSchema metaSchema)
at Epicor.Mfg.Core.CallContext.ProxyHelper.CallMethod(String methodName, ParameterSet parameters, MetaSchema metaSchema, BLConnectionPool connPool, Session connection, PersistentProc persistProc, CallContextDataSet callContextDataSet)
at Epicor.Mfg.Proxy.CustShipImpl.UpdateMaster(CustShipDataSet ds, Boolean doValidateCreditHold, Boolean doCheckShipDtl, Boolean doLotValidation, Boolean doCheckOrderComplete, Boolean doPostUpdate, Boolean doCheckCompliance, Boolean ipShippedFlagChanged, Int32 ipPackNum, Int32 ipBTCustNum, String& opReleaseMessage, String& opCompleteMessage, String& opShippingMessage, String& opLotMessage, String& opInventoryMessage, String& opLockQtyMessage, String& opAllocationMessage, String& opPartListNeedsAttr, String& opLotListNeedsAttr, String& shipCreditMsg, Boolean& cError, Boolean& compError, String& msg, String& opPostUpdMessage, Boolean& updateComplete, Boolean& checkComplianceError, Boolean& changeStatusError)

No one has seen this error?

I’ve never seen that error, but then again we don’t use “Mark For”

Have you checked the “Mark For” values in the Order? Maybe someone did a copy and paste, and a bad character worked its way in there. I’ve seen the Record Separator control character (ASCII 0x1E) give printing problems.

Nope, never seen it either. Checked old emails, searched here for you in case you “man looked” (:grinning:) … couldn’t help myself. But, Calvin, what is “mark for” on an order?

Nancy

I didn’t know either …

Wow ~ look at that. In my defense, I’ve only been using the program 10 years. I would’ve found it for sure in year 11. Thanks Calvin for helping me find it now. :+1: I think Jonathan must have something interesting on that tab.

I was really thrown by phrasing of the warning, “Do you want to refresh mark for with the changes?”

I took “mark for” to be an action, not a property of the order release.

Calvin, once again you save the day. LMAO. I was with you I thought it was an action. Geez.

1 Like