Managing data

These entities require various maintenance activities to reduce the usage of the storage space:

sFTP site

Users can remove files from the sFTP site that are not required. Responsibility for maintaining the sFTP site resides with the user as Infor cannot access the sFTP site.

Cycle Periods

Users can delete cycle periods that are not required. If a cycle period is removed, associated scenario values, versioned configuration (for example, code lists, and worksheets), audit logs, and related jobs are also removed.

Cycle periods can be removed manually (see Cycle Periods) or automatically after a new cycle period is created, ensuring that only a specific number of cycle periods are stored (see Defining cycles - Archive Settings tab).

Note: The volume of storage space is not reduced when archiving Cycle Periods.

Scenarios

Users can delete scenarios that are not required. The scenarios created for each cycle period can be reviewed to determine whether these are required for the business. The redundant scenarios can be disabled to ensure that these are not created as part of the cycle period. See Defining default planning scenarios for a cycle, and Cycle period scenarios overview for more information.

Scenario History

The scenario history storage maintains a record of all value changes for each item, location, and period. The history for scenario changes, and business metrics updates can be disabled unless there is a business requirement to maintain all changed values. See Defining cycles - Generate Scenario History tab for more information.

Audit Log Retention

Audit logs are stored by default unless specified in the System Settings Data Retention policy. Users can select the number of days based on the retention policy. See Data Retention Settings tab for more information.

Note: 

• The audit logs are removed in batches as part of a low-priority background process when a new policy is created.
• Audit logs related to cycle periods are not affected by the retention policy.

Planning Engines

Users can delete planning engines that are based on outdated scenarios or plans. In addition, this action removes the associated notes and audit logs related to the deleted Planning Engines. This action can be done manually from the Planning Engines screen of the Process menu. See Planning Engine process for more details.

Planning Data in SCV

SCV is an integration component of Infor SCP that focuses on planning data management.

SCV manages these types of planning data:

• Configuration data: SCV configuration data is loaded from SCP content templates or manually created in Infor SCP. The volume of configuration data is based on the content templates loaded to SCP. Therefore, load only the required content templates to reduce the volume of configuration data.
• Imported planning data: Planning data in SCV is the input data used by the Infor SCP application, imported from the ERP or manually specified in SCP. The volume of imported planning data can vary significantly. Older sales history records outside the start of the planning horizon can be removed. In addition, data types that are not required can be disabled. See Imported planning data for more details.
• Manually inputted planning data: Planning data can be manually inputted into SCV User Data tables using editable datasheets. The volume of planning data that is inputted manually is typically limited. Unused data can be manually removed or deleted using the PURGE_PLANNING_DATA program, if required.
• Generated planning data: SCV provides multiple data transformations that can be applied to the imported data or to the manually inputted planning data. Some of the transformations update the data (such as Data Enhancement), while some others create additional planning data (such as Generate Hierarchy or Prepare Profile). The volume of generated planning data is based on the related configuration, the volume imported, and manually inputted planning data. Therefore hierarchies and profiles that are not required can be disabled. See Generated planning data for more details.
• Generated plan results: SCP modules replace previously published plan results when publishing with some exceptions. For example, SCP Demand Planning maintains multiple versions of the published forecast in SCV. The PURGE_PLAN SCV program can be used to purge plan results that are not required from SCV Core Plan tables.
• Log data: SCV creates execution logs, snapshot logs, and validation logs. The PURGE_EXECUTION_LOG, PURGE_SNAPSHOT_LOG, and PURGE_VALIDATION_LOG SCV programs can be used to purge these logs. These purge programs are part of the SCV standard inbound macros.

Events

Events are stored for each user on the Event distribution list. Users can remove the events that are no longer relevant. See Displaying events for more details.

Production Scheduling

Users can review the storage of data on Production Scheduling to reduce storage:

• Backups: The Production Scheduling backups that are based on outdated plans can be removed. When creating and scheduling backups, ensure that each backup contains an expiry date. Backups without an expiry date can be reviewed and removed, if not required. The backup frequency and expiry date can be set with a suitable cadence when creating backups; for example, a one-day expiration date can be set for hourly backups.
• Model Management: The duplicated models can be reviewed frequently to determine whether to maintain or delete, if required.
• Data Management: Batches or orders that are older than the production cycle can be reviewed and removed, if not required. Regular reviews can be performed for master data. For example, process steps can be reviewed and removed if not required.
• Log Messages: Users can review the History section in the Production Scheduling application using Global Preferences from the File menu, and ensure the value set here, which is applicable for removing records from the macro execution log, is appropriate for the process and business.

There are additional data storage areas that although have minimal impact on storage, can be reviewed on a regular basis to ensure efficiency. These are the available data storages to be reviewed:

• Searches: Users can remove searches that are not used. Ensure that the searches are not used by Event Generators, or Event Notifications before removing searches.
• Event Generators:Users can remove Event Generators that are not used. Users must verify prior to deleting Event Generators, that the selected event generators are not used within Event Notifications.

  Any valid Event Generators can be reviewed to ensure they do not create an excessive number of events. See Creating event generators for more details.

• Event Notifications: Users can remove Event Notifications that are not used. Ensure that valid Event Notifications do not create excessive Notifications. See Creating event notifications for more details.
• My Selections: Users can remove my selections that are not used. My Selections are rebuilt when a cycle period using the same hierarchy is created or refreshed. Therefore, this can increase the processing time if many My Selections are used. See My Selections overview for more details.
• Calendars/Planning hierarchies: Users can disable the Calendars or Planning Hierarchies that are not used. This ensures a calendar or planning hierarchy that cannot be built is not reported as an error in the setup checker and audit log. See Calendars for more details.