Hi Kyle Klinger,

Thanks for reaching out. Did you ever find a resolution to this issue? If you are still looking for guidance, please let us know and we can try to point you in the right direction or suggest some resources or next steps.

Warm Regards,
Erzsi

I did not receive a response, however I did create what is currently an acceptable workaround.  

I created a function that is ran by a batch task on a schedule.  

It would be nice have the order status be updated on creation rather than later by the batch task.  

Have you attempted to create a workflow that would trigger on creation to update the CDTSTA value?

Hi Kyle,

this entry point must work, take a look how is the MAJ variable value because if is not 2, never will rewirte F:SOH.

Also you must take care with mask variables because this entry point will be executed in. Automatic Allocations, automatic delivery notes creation, picking orders from delivery notes, expeditions preparations, etc. I recommend to you use a condition or GFONCTION="GESSOH" or dim([M:SOH0]SOHTYP)>-1

Kind Regards! 

This option must can have other considerations, like Approvals, don take this needs into MRP, etc. I think is not the best solution.

I am interested in your function that is run as a batch task on a schedule.  My issue is we have orders on hold.  Then payments are made but field CDTSTA is not updated.  So how can a person "report" orders on hold when the field is not automatically updated by the payment?  The only method I know currently is to "open" the order and then the field updates and is released.  Thanks

If you are waiting for payment, why not use a payment term that requires a "prepayment"?  then when it's paid, the order will be available to ship.

Here is our issue.  We create a sales order.  The payment term requires a prepayment.  We issue the prepayment.  The sales order is then on hold for payment (field CDTSTA).  Later - the prepayment is made and posted.  If the sales order is not "accessed" manually by a user - field CDTSTA continues to report the sales order is on hold (which is not true as the payment was made).  Sage confirmed field CDTSTA does not update whenever the payment is posted.  Only accessing (or opening) the sales order manually will the field get updated.  The issue with this is real time reporting of orders on hold for non-payment using field CDTSTA.

Oh wow, I did not know that!  Thank you so much for the explanation because I was just about to work on implementing prepayments for Sales Orders.

No worries - it is very confusing!  I assume the best method for reporting prepayments is starting with the GACCDUDATE table rather than the SORDER table