BPM to prevent deleting an order if older than 1 day

Epicor ERP 10
1

Hi guys,

I’m working on a BPM to restrict deleting an order if it’s been more than one business day since the order was created. The condition is not picking up the
image
statement, and always goes False.

I tried simplifying it to ‘today’ for testing. What am I missing? How would I test this (so I can get better at troubleshooting)?

Thanks for the help!

image

image
image821×163 18.9 KB

image

image

image

2

First off, OrderHed.OrderDate is user changable. So if an Order was entered on Friday 3/13, (with an Order date of 3/13), you could just change it on Monday to 3/16, and then delete it.

Make a BPM to set OrderHed.UserDate4 to the current date when the order is saved created. Then compare that date to the current date when checking if it can be deleted.

3

The following worked for me:
image

with a lone condition of:

image

That still allows deleting lines and releases, but not the order head.

edit

one more thing. Not only can a user change the OrderHed.OrderDate, they can delete it. So how would you know how old the order is then? And comparing a date to a null, might throw an error.

2 Likes
4

Other ways to do the “freezing” of the order date:

  1. secure the OrderDate so that it cannot be changed from anything other than “Today”… This can be done with a BPM… OR a UI change (not preferred by me).
  2. Create a new UD Field called EnteredDate_c which is auto filled (with BPM) with the date that the order was entered. This way the Order date could be yesterday, but the Entered date could be today.
5

It’s now working (thanks for the example, Calvin) - I think the error was PICNIC, as I had my user in the security group that allows deletion. Oops!

Calvin & Tim - Thank you. I’ll be adding something to handle the potential for the OrderDate being able to be changed.

My next step for this BPM is to make sure the cancellation reason is set, but that’s not firing (BPM on Erp.SalesOrder/CloseOrder/Pre). I did a trace on Action > Orders > Close Order, and it doesn’t seem to be passing any data at all. I was hoping to check for CancelReason_c being “” or Null, and popping up an exception if it was not set.

image
image
I then tried checking if it’s closed using the VOID field, and that goes FALSE every time as well:
image

image
This is all I get with a trace, even with Write Full DataSet selected:

<tracePacket>
  <businessObject>Erp.Proxy.BO.SalesOrderImpl</businessObject>
  <methodName>CloseOrder</methodName>
  <appServerUri>snip</appServerUri>
  <returnType>Erp.Tablesets.SalesOrderTableset</returnType>
  <localTime>3/17/2020 16:05:44:3593925 PM</localTime>
  <threadID>1</threadID>
  <correlationId>c53d24c0-8899-4b52-8d8c-10f447638937</correlationId>
  <executionTime total="1953" roundTrip="88" channel="0" bpm="1856" other="9" />
  <retries>0</retries>
  <parameters>
    <parameter name="iOrderNum" type="System.Int32"><![CDATA[7593007]]></parameter>
    <parameter name="CallContext" type="Ice.Bpm.Context.ContextDataSet">
      <ContextDataSet xmlns="http://www.epicor.com/Ice/300/Bpm/Context">
        <BpmData>
          <Number01>0</Number01>
          <Number02>0</Number02>
          <Number03>0</Number03>
          <Number04>0</Number04>
          <Checkbox07>false</Checkbox07>
          <Checkbox09>false</Checkbox09>
          <Checkbox10>false</Checkbox10>
          <SysRowID>00000000-0000-0000-0000-000000000000</SysRowID>
        </BpmData>
      </ContextDataSet>
    </parameter>
  </parameters>
</tracePacket>
6

May need to use an in-trans data directive for this part. It looks like the CloseOrder call only gets access to the required info in its returnValues data set, so you won’t be able to access anything from the SalesOrderTableset unless you use a post-processing directive (which doesn’t do you much good since you are trying to check and possibly stop the transaction).

7

@Asz0ka - Thanks! That worked.

image

image
image724×100 10.8 KB

Since we like to make everything complicated, I’d like to do this for lines as well (sometimes we cancel some lines from an order, but need to keep the lines that may have already been manufactured).

When someone chooses a cancel reason on the header, I’d like to push that UD field from the OrderHed to all lines on the OrderDtl table. What’s the simplest way to do that? My search-fu didn’t find anything…

8

All of the ines for that order? Or just open lines? (I don’t think you’d want to set the CancelationReason_c field on a line that was already fulfilled.

And to update the OrderDtl records, an InTran could set ttOrderDtl.CancelationReason_c based on the value found in the OrderHed record. Conditional on the line status going from Open to Closed, and maybe some other checks to make sure its being closed from the OrderEntry UI, and not from a shipment.

1 Like
9

Thanks - Good point. The devil is in the details, eh? All open lines should have the OrderDtl.CancelReason_c field set to the OrderHed.CancelReason_c when you go to Actions > Order > Cancel Order.

I’ll try that, using the OrderDtl.VoidLine = TRUE for the condition. Thanks!

1 Like