Cancel Order - Activities not marked as cancel

We are having the same issue with an activity tracking report. The intent of the report is to identify all Manually Allocated activities that have been placed on the console as a place holder. A report was built with a Demand status of ‘Manually Allocated’ and a Disposition of ‘Open’. We have since run into opening several of these Orders only to receive this error.

9 days later… still no respons from IFS? Who is going to contribute on this topic from IFS?

A portal like this will only work when all posts get a quality respons and dito action.

Hello Gijs,

I do understand your point the documentation does not align with the current behaviour of the application.  I have requested R&D to clarify this and confirm this is an issue either in the application or the documentation.

My expectation from reading the document is the DEMAND STATUS should be set to Canceled.  It is not the Disposition itself… I do know the demand status is set to canceled when you set the Disposition of the activity to Not Done.

When I hear from R&D, I will come back to this topic.

The response from R&D:

This is how the system was designed and worked from the beginning. There is a lot of code running on order cancellation - cancel materials, cancel labor PRs, cancel fixed appointments, etc. but activities are moved to history as-is without changing status. If, for example, some activity was already completed it will stay completed also on the canceled order.

This is a design decision and not a bug.

Having said this, for the issue in the Activity Tracking module, which I think was pointed out by Sean, is a problem and I will log a request to have this corrected as R&D agreed.

Custom reports or queries will have to also validate the c_order_line.order_stat_uniq_id to see the order itself has been canceled.  If these reports or queries are not supposed to display demands that have been moved to history, it is also possible to check c_order_line.order_stat_uniq_id >= 900 (invoiced) or c_order_line.is_history = Y.

There are currently no plans to adapt the design to populate the demand_status with canceled when the cancelling the order.

For clarity, I am still in discussion with R&D whether we will update the demand status to canceled when the order is canceled.  I don’t know yet what it would take, etc. but it is being investigated.

In the mean time, seems to me you can also create a process flow to update the demand status to canceled when the order has been canceled (demand status for canceled is 500).

You know what's annoying Phil, that the response from R&D is regularly so hugely detached from how the application works in a major operation. Works as designed is not always an answer for all issues. Somethimes things are badly designed and need fixing. Thank you for rasing this point again.

@Smstovall ,

For the Activity Tracking module which pulls up the list of activity demands and you are finding the demands in history giving you an error.

One thing that might help to alleviate this while we look into the problem is to filter the search to not show history.  There is a criteria to Display History.  If you say this to No, your history demands will not appear in the list.

In the meanwhile, I am working with our R&D team to address the error that appears when selecting an order that is now in history due to cancelation.

Thank you Phil. I have adjusted that organizational view and that solved this issue. Please keep me in the loop when the issue is resolved by R&D.

Thanks, Sean

R&D has created a fix to change the labor activity to canceled when the order is canceled and the activity is not yet completed.

Completed activities will not have their status changed.

The planned release versions for this fix is v15.3 HF6 and 15.4 SU4. 

The other issue where opening a link in the activity tracking module for an order now in history was also logged and I am waiting for feedback on this ticket. 

Hi Phil, great job, thanks!

@Smstovall 

Hi Sean, just to let you know, R&D has developed a fix for opening demands of orders in history from the Activity Tracking table.  For standard product, this is currently planned for release with 15.4 SU4 (the next standard release for our current version).

For your implementation, this will need to be discussed with the Alliance support team in the US how to proceed from here for your version or other upgrade possibilities.