I'm wondering if BADI (WORKORDER_UPDATE-Method IN_UPDATE) may not be useful at the time, because, in my debugging, it seems that the it_header-AUFNR has not been set to the final order number yet in that menthod, but instead it is still set to the temporary number.
I'm having struggles of my own finding a place in the same group of exits BAdIs where the **reservation** for the components has been placed (and the ATP in Co09 has thus been affected). The BAdI methods that I've tried (and I think I've tried them all!) either don't seem to trigger in CO01, or the ones that do are too early in the process.
I need to send a file with ATP values for the component *after* the reservation has affected the component's ATP CO09 value.
I even tried calling my function in update task to put it last in the update stack (hopefully after the commit of the reservation, but it doesn't seem to work that way either).