1.   So, although it is good practice to do so, it is not normally essential to add new module versions to SPRs and SSRs.

2.   In the fullness of time when products are superseded, module versions may no longer be required and consequently may no longer need to be retained in magnetic form.

3.   HCMODULES identifies module versions that have yet to be hard copied for those charge codes and requests those versions to be restored from offline.

4.   Module versions which become redundant through time and supersession will be progressively cleansed from the magnetic database as they become hard copied.

5.   Module version information may be restricted to details on approved module versions only, with details on intermediate development versions omitted.

6.   In the latter case the module version is no longer available in magnetic form.

7.   FOREIGN type not permitted for this module header version.

8.   You may only use this option to extend the range of module versions to which this SPR relates.