Can anyone recommend best practices for splitting and rescheduling customer order lines in IFSCloud so that I can clearly see the tie between old and new lines?
As an example, I have a customer who sends in an order for 200 pieces of part ABC on 01Jan2026, with a wanted delivery date of 15Oct2026. My company acknowledges the order and begins working towards scheduling/fulfillment.
It becomes evident that my customer wants parts sooner and I determine that I can deliver 25 pieces on 01Jun2026, and 7 on 15Jun2026. Rather than doing a partial delivery, we create two new releases on the same line number, one for 25 pieces and one for 7, while reducing the qty on the original line by 32 pieces down from 200 to 168. In the meantime, the customer indicates that in addition to the 200 pieces, they would like 100 additional pieces, which we add in as the same line item but another release.
Sorting out what is a “rescheduled” qty directly from each line and what is new is difficult through the history log when you have many releases on the same line. I derived a method that uses the history_log in conjunction with the container_orderlog_tab, but this is not clean, nor is it evident to the end user without searching the data tables.
Any suggestions are appreciated for how to tie rescheduled/split lines together so I can clearly trace on a line where I have new qty, where I’ve simply rescheduled and from what lines the re-scheduled lines derived from.
Thank You