Inventory Planning > Inventory Optimization > IO Purge and Update

IO Purge and Update

You use this program to remove history information that is no longer required, to purge invalid data (e.g. where the stock code or stock code/warehouse combination no longer exists) and to update forecast history for sales and sales returns for all items.

The program can also be used to extract information from the inventory movements file and create a daily summary table of stock movements.

IO Purge and Update

Field Description
Start Processing Select this to begin processing according to the options you selected.
Print Select this to print the information currently displayed in the Report output pane.
Save Form Values This option is only enabled in Design mode (see Automation Design). Your selections are saved and applied when the program is run in automated mode.

Details

Field Description
Processing options  
Number of months to retain information This indicates how long you have elected to retain information and is configured within the Inventory Optimization Setup program.

An entry of 999 indicates that you are retaining records indefinitely and that no records are to be purged.
Purge date This indicates the date when next records matching your selection criteria will be purged.
Purge historical/Invalid IO data Select this to delete historical information that is no longer required in the system, as well as invalid information.

Historical information is deleted according to the number of months you are retaining history (Inventory Optimization Setup).

See Purge.
Update movements table Select this to extract information from the inventory movements file and create a daily summary table of stock movements.

See Update Movements Table.
Rebuild movements table Select this to clear the inventory movement tables and regenerate records.

This function performs the same functions as Update movements table, but will recreate the movements table (i.e. It clears the existing table and then processes all records as if for the first time).

After processing completed These options are displayed within programs that can be automated. They enable you to indicate the action you want to perform once processing is complete (see Automation Design).

Purge

There are two sides to the purge:

  • Remove history that is no longer required

    This depends on the number of months for which you are retaining history (Inventory Optimization Setup). If this is set to 99, then no history is deleted.

    The tables affected by this purge are:

    • IOPSLS - Sales Transactions

    • IOPSLR - Sales Returns

    • IOPADJ - Sales Adjustments

    • IOPSNH - Forecast snapshot headers (alternate index)

    • IOPSNP - Forecast snapshots (based on the header being removed)

    • IOPJNA - Collection amendment journals (based on journal date)

    • IOPSEJ - Selection set amendment journals (based on journal dates)

    • IOPLVJ - Min/Max amendment journal (based on amendment date)

    • IOPSOP - Sales performance (based on sales order entry date)

  • Remove information that is invalid. This is where there is no longer a SKU-LOC entry in the Inventory Warehouse (INVWHS) which means that the stock code or stock code/warehouse no longer exists.

    The tables affected by this purge are:

    • IOPABC - IO Pareto results

    • IOPADJ - Sales Adjustments

    • IOPCSK - Collection SKU structures

    • IOPCWA - Consolidated adjustments (checks existence in INVMST)

    • IOPCWD - Consolidated draft (checks existence in INVMST)

    • IOPCWS - Consolidated sales (checks existence in a)

    • IOPNFR - New (draft) forecasts

    • IOPPRX - Proxy table (both source and proxy are checked)

    • IOPSLR - Sales Returns

    • IOPSLS - Sales

    • IOPWHS - SKU options (based on non-existent entry in INVWHS)

    • IOPSNH (based on a non-existent entry in IOPWHS)

    • IOPSNP (based on a non-existent entry in IOPWHS)

    • IOPMOV (based on a non-existent entry in IOPWHS)

    • IOPSOP (based on a non-existent entry in IOPWHS)

Update Movements Table

All movements in and out of stock from the Inventory Movements table (INVMOV) are summarised on a date basis and written to the IOPMOV table for each stock item that exists in the IOPWHS table. The IOPMOV table is effectively a summary Kardex table.

Each time it is run, unprocessed entries in INVMOV are added to the IOPMOV table.

The IOPWHS table contains the opening balance for the date, the quantity and value issued for the date, quantity and value received on the date and the number of stock outs on the date (i.e. the number of times the quantity on hand reaches zero or less on an issue for each day). The number of stock outs is calculated for each issue and receipt.

[Note]

For this to work correctly, receipts need to be made into stock timeously and the stock should not be allowed to go negative (Inventory Setup) otherwise it is assumed that there are no stock outs.

The quantity on hand and a count of stock outs are vital when calculating the min/max quantities in inventory optimization.

The quantities in and out are taken from:

  • Inventory transactions:

    • (A) Adjustment

    • (I) Issue

    • (P) Physical

    • (R) Receipt

    • (T) Transfer

  • Sales transactions:

    • (C) Credit note

    • (D) Debit note

    • (I) Invoice

    • (B) IBT

    • (N)(M) Dispatches

Report

The results of the processing function you selected are displayed in this pane once processing is complete (unless you enabled the option to close the application from the After processing completed section). You use this section to print or email this information.

Notes and warnings

eSignature considerations

Electronic Signatures provide security access, transaction logging and event triggering. This enables you to increase control over your system changes.

Access to the following eSignature transactions within this program can be restricted at Operator, Group, Role or Company level. You configure this using the Electronic Signatures program.

eSignature Transaction Description
IO Purge and update

Controls access to the Start Processing function in the IO Purge and Update program.

Application Help Pane

Application Help Panes provide step-by-step instructions for various functions within the program, including a brief overview of what the program does, what setup options are required and how to personalize the program. The intention is that the pane provides information that is uncluttered and easy to navigate.

You can embed an Application Help Pane:

  • in the main SYSPRO menu

  • in any program with panes, if not using roles

  • when adding a role layout in Design Mode.

Inserting Application Help

You would typically follow this procedure to display help for the current program in a customized pane that can be pinned to the program window.

Information includes step-by-step instructions for the various functions available within the program, including a brief overview of what the program does, what setup options are required and how to personalize the program.

  1. Open the program for which you want to insert application help into a customized pane.

    This functionality is only available for a program that has panes.

  2. Right-click any form field.

    You can also click the triangle menu icon that appears in the title area of a pane.

  3. Select Insert Application Help from the context-sensitive menu.

    The application help appears in a pane within your program. You can reposition the pane using the docking stickers or pin it to the program window.

Removing the Application Help pane

If you no longer want to display application help in a pane for your current program, you can simply remove it.

  1. Select the Close icon in the right-hand corner of the application help pane.

  2. Confirm that you want to delete the pane.