I know the Microsoft documentation suggests only beginning with one plan when going live and this is typically a static plan but beware. Over time – depending on how intense you run Master Planning – this will more than likely become an issue. The InventSumLogTTS is a log file, used in Master Planning, that stores transaction records. This log file is cleared when a Dynamic plan is assigned on the Master Planning parameters and the plan run. If this file is left to its own, it will continue to grow and possibly become a space issue.
In the Master Planning parameters (Master Planning > Setup > Master planning parameters), the Current dynamic master plan must indicate a Dynamic master plan. The dynamic plan is setup in the Master planning > Setup > Plans > Master Plans form and can have the same setup as the static plan – but it must be a unique plan.
Once the dynamic master plan is identified, the Automatic copy checkbox must be ON. This will ‘copy complete updates of the static master plan (all items) automatically to the dynamics master plan’.
Now that the minimal setup is complete, process Master Scheduling using the Dynamic plan. This is completed through Periodic > Master scheduling. When running, the principle should be set to Regeneration where all existing requirements and planned orders (except where status = approved) are deleted. Typically this is run with no criteria selected, however if the file has grown to a size in which the scheduling using the Dynamic plan may take an extreme length of time, selection criteria can be used to ‘breakup’ the cleanup process.
Once the Dynamic plan has run, the standard planned order screen will include messages generated during the master scheduling run. As this may cause confusion by users, it is suggested that the Delete plan process be run to remove / delete the Dynamic planned messages. This can be performed by selecting Periodic > Plans > Delete plan and select the Dynamic plan for deletion.
Completing the Master scheduling process against the Dynamic plan should clear the InventSumLogTTS file. For normal maintenance on this file, a batch job may be set up to run periodically to assist in the housekeeping of this file. It is suggested this batch job (especially if not broken up into segments) be run during times when planners are not utilizing the system as this could cause a lock condition.