Forcing Cancellation Code when deleting Sales Orders into history through BOI

Question

Good morning all, So I figured this would have been a relatively easy script but I can't seem to find a way of accomplishing what I need. 
 I have a customer that would like to force a cancellation reason whenever you delete a Sales Order into history. They currently have the "Retain Deleted Sales Order" setting to Prompt in SO Options, which first prompts the user if they would like to delete the order (standard), but THEN it asks "Do you want to save the deleted order in history?" If you say yes, it's all good. However, you can say No and it will delete the order and not save it (a BIG no no for the customer). Furthermore, if you do click Yes to save to history, then it bring up this screen to enter the Cancellation Code: 
 While I have the Cancellation Code as a required field in Advanced Settings for UDF and Table Maintenance, it will not force an entry unless I validate the field with a list I create, which I would have to make it match the existing lookup on this field. If I don't have validation, the user can simply click OK without a code and it will delete it. So I was thinking my quick fix would be to set "Retain Deleted Sales Order" setting to Yes , then create a Table - Pre Delete script that would launch the Cancellation Code screen above BEFORE it asks to delete the order. I figured that by doing this, the Cancellation Code would be written into the table and then the order would be deleted into history. Unfortunately, I cannot seem to find the correct UI to bring that screen. This is the code I had tried but it brings up Cancel and Reason Code Maintenance On The Fly. 
 oSOCancel = 0 
 oSOCancel = oSession.GetObject("SO_CancelReasonCodeOTF_UI") Set oSOCancel = oSession.AsObject(oSOCancel) retVal = oSOCancel.Process() 
 
 I tried the SO_CancelReasonCode_UI object as well, but that brings up the standard Cancel and Reason Code Maintenance. Is there a way of bringing up that specific screen? I had also tried using the InvokeButton to bring up "fldr.DCANCEL" (Cancellation Code screen in SO_SalesOrder.M4L library) but I had no luck. Maybe I was using the wrong code? Any ideas or suggestions would be highly appreciated. 
 Thanks in advance! Javier

Javier Guzman · Accepted Answer

I think it might be problematic to write back into that CancelReasonCode field unless I write once it is in history. In the meantime, I will create a UDF called CANCELREASON and write the value into it. At some point, I may pursue writing that value into the CancelReasonCode from the UDF. Here is the final code. I am forcing the user to select a reason, otherwise they will get a popup and the order won't be deleted. Thank you David Speck and Kevin M for your knowledge and excellent assistance. It is very appreciated. sMsg = "Deleting Sales Order with Custom Delete button" oScript.DebugPrint sMsg sMsg = "StartProgram = " & oSession.StartProgram & " Updating = " & CStr(oSession.Updating) oScript.DebugPrint sMsg If oScript.UIObj > 0 And oSession.Updating = 0 Then If Not(IsObject(oUIObj)) Then Set oUIObj = oSession.AsObject(oScript.UIObj) sSalesOrderNo = "" : oBusObj.GetValue "SalesOrderNo$", sSalesOrderNo oScript.DebugPrint "sSalesOrderNo: " & sSalesOrderNo sMsg = "Do you want to delete Sales Order " & sSalesOrderNo oScript.DebugPrint sMsg sResponse = "" : sResponse = oSession.AsObject(oSession.UI).MessageBox("", sMsg, "style=YesNo,icon=?") If UCase(sResponse) = UCase("Yes") Then sMsg = "Deleting SO " & sSalesOrderNo oScript.DebugPrint sMsg sCancelReasonCode = "" : oUIObj.InvokeLookup "SO_CancelReason", sCancelReasonCode oBusObj.SetValue "UDF_CANCELREASON$", sCancelReasonCode oBusObj.Write() oScript.DebugPrint oBusObj.LastErrorMsg If oUIObj.BT_Accept() <> 0 and sCancelReasonCode <> "" Then oBusObj.Delete sSalesOrderNo oScript.DebugPrint oBusObj.LastErrorMsg oUIObj.BT_Cancel oUIObj.RefreshScrn Else sMsg = "You must select Cancel Reason Code to delete this order" oScript.DebugPrint sMsg sResponse = "" : sResponse = oSession.AsObject(oSession.UI).MessageBox("", sMsg, "style=OK,icon=?") End If Else sMsg = "Not deleting SO " & sSalesOrderNo oScript.DebugPrint sMsg End If End If

David Speck · Answer

As for the blank records in history, that may or may not have been caused by failed iterations of your script attempts. 
 For the Hold issue, just add another SetValue for the status field and pass the "H" as the value before you set the cancel reason code.

David Speck · Answer

I've seen "The is invalid" a lot as false positives, not saying that isn't the case here, but it could be. 
 Might need to try an alternate method to get the record back into an edit state, could try oUIObj.InvokeChange "SalesOrderNo", sSalesOrderNo before the oBusObj.Delete and not pass anything to oBusObj.Delete.

David Speck · Answer

Did you read this post. 
 https://www.sagecity.com/us/sage100_erp/f/sage-100-business-object-interface/160533/forcing-cancellation-code-when-deleting-sales-orders-into-history-through-boi/416666#416666

Sage 100

Forcing Cancellation Code when deleting Sales Orders into history through BOI

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING