Period Settings tab
Period settings allow the control of the recall windows, forward projection and data retention. Misconfiguring these settings can affect the performance of the system and the size of data. Do not change these settings unless you are trained and understand the impacts. If you are unsure, please seek assistance from Infor. The recommendations made for the recall window and data retention settings are based on a typical deployment of the Infor MES solution, and assuming normal volumes of data. The recommendations are not correct and require to be reviewed if data volumes are higher or lower than anticipated.
You can specify this information on the Period Settings tab:
Recall Windows (days)
- Default Concern Due Period
- The default number of days in which a concern must be resolved.
- Default SPC Trend Recall Window
- The default number of days used for SPC Chart Set Trend assessment. A recall window of 30 days is recommended to ensure correct SPC trends.
Forward Project (days)
- Shifts
- The number of days that the application uses to project future shifts. A forward projection of 5 days is recommended to ensure enough shifts are generated in the future.
- Maintenance
- The number of days to forward plan maintenance. A forward projection of 730 days is recommended to ensure a full 2-year plan is projected.
- Production Order Schedule
- The number of days that the application uses to project future work order schedules. A forward projection of 30 days is recommended.
Data Retention (days)
The following settings are available to control the number of days to retain data for. Any data older than the set number of days is deleted permanently. Configuring a zero value means that data is retained forever, however this can have performance and sizing impacts. Recommended to always configure values for each setting. Please contact Infor if assistance is required.
- Labels
- The number of days to retain label printing details. A data retention of 365 days is recommended to ensure a good history of records. However, this requires changing depending on the volume of usage.
- Process Parameters
- The number of days to retain process parameter records. Recommended practice is to maintain a complete history by setting data retention to 0 days. However, adjustments can be necessary based on the volume of usage.
- Transaction Log
- The number of days to retain entity transaction log information. A data retention of 365 days is recommended; however, this can require changes depending on the volume of usage.
- OPC Action Log
- The number of days to retain OPC action log records. A data retention of 30 days is recommended but requires changing depending on the data volume.
- Write Value
- The number of days to retain OPC write queue records. A data retention of 30 days is recommended but requires changing depending on the data volume.
- OPC Items
- The number of days to retain OPC item history. A data retention of 30 days is recommended but requires changing depending on the data volume.
- Initial Production Performance Population
- The duration that production performance data is recorded during system initialization. This process occurs on newly installed machines or on machines that are upgraded. A forward population of 30 days is recommended to ensure the required future records exist.
- Production Info
- The number of days to retain production performance records. Recommended to keep a full history by using a data retention of 0 days.
- API Client Log
- The number of days to retain API client log records. A data retention of 30 days is recommended but requires changing depending on the data volume.
ERP Holding Table Data Retention (days)
The following settings are available to control the number of days to retain ERP Holding Table records for. Any data older than the set number of days is deleted permanently. Configuring a zero value means that data is retained forever, however, this can have performance and sizing impacts. Recommended to always configure values for each setting. Please contact Infor if assistance is required.
For all the fields mentioned below, A data retention of 30 days is recommended, however, require to be changed depending on the volume of data.
- BOM
- The number of days to retain ERP BOM records.
- Inbound Delivery Item
- The number of days to retain ERP inbound delivery item records.
- Inbound Delivery
- The number of days to retain ERP inbound delivery records.
- Delivery Pack
- The number of days to retain ERP delivery inventory pack records.
- Inbound Item
- The number of days to retain ERP inbound item records.
- Inbound Order
- The number of days to retain ERP inbound order records.
- Pack
- The number of days to retain ERP inventory pack records.
- Fulfillment Item
- The number of days to retain ERP fulfilment item records.
- Outbound Shipment
- The number of days to retain ERP outbound shipment records.
- Outbound Pack
- The number of days to retain ERP outbound inventory pack records.
- Shipment Item
- The number of days to retain ERP shipment item records.
- Outbound Order
- The number of days to retain ERP outbound order records.
- Outbound Transaction
- The number of days to retain ERP outbound transaction records.
- Material
- The number of days to retain ERP material records.
- Routing
- The number of days to retain ERP routing records.
- Production Order
- The number of days to retain ERP production order records.
- Production Order Bill of Materials
- The number of days to retain ERP production BOM records.
- Login
- The number of days to retain ERP login records.
- SPC Analysis
- The number of days to retain processed SPC analysis queue records.
- Upload Data
- The number of days to retain ERP upload data. This applies to all data uploaded to the ERP system that is not included in the scope of the other holding tables.
- Download Data
- The number of days to retain ERP download data. This applies to all data uploaded to the ERP system that is not included in the scope of the other holding tables.