Rebuilding F1602
Hi,
I have a customer who ran R1602 (Post to Cost Analyzer Balances) twice in quick succession on a muti-threaded queue, which has resulted in bad data for a period in the F1602.
They are currently on Period 5 of FY17 and need to recreate the F1602 for period 3 and some of Period 4, but face the following challenges:
1. R1602 is cumulative, so updates totals based on data it reads each time.
2. R1602P Purge cannot be data-selected (or doesn't seem to be) by period, so it will wipe all of FY17 for the given View Number.
Anyway... we have copied PD data to PY for testing and have run R1602P to clear the F1602.