Hi,
Today we encountered an issue where stock-data where not transfered to F&R. As a result OrderProposals generated during FRP-run were based on incorrect stock stock-values. As a result also the OrderProposals resulting from the FRP-run were considered incorrect and have been deleted by the business.
After stocks were processed correctly to F&R, a new FRP-run was done for the first 4 sequences in /FRE/FRP_MID_BASIC. (Note that we have these first 4 steps executed in the time critical window, and the Analytics step as a separate job directly afterwards).
Result is ofcourse new, correct, OrderPropsals but also a second run of the Analytics step on the same planning-day. As a result, in table /FRE/ANA_WEEKLY the STOCK_COUNTER is increased 2 times during one planning-day, which will cause incorrect data at the end of the week regarding average weekly-stock level.
It appears, every time the Analytics-step in /FRE/FRP_MID_BASIC is executed on a day, the STOCK_COUNTER field is updated. (this can be reproduced). The result will be incorrect Analytics data if that happens, but on the other hand: not executing the Analytics step a second time during the planning-day will also result in incorrect Analytics data as in that case it would in my situation have contained the stock-data from yesterday(as the initial issue was that current actual stock-data was not sent to F&R)
Is this a bug in F&R, or am I missing something? If there is a guide on what steps to execute under what conditions if FRP-run has to be executed again, or how to correct any (incorrect)Analytics data built up during previous runs?