System Administration
This chapter describes general steps for updating records and preserving database space.
Introduction to EOP System AdministrationDescribes some of the routine tasks that should be performed by the system administrator.
Maintaining Static DataLists some of the events for which records should be updated.
Deleting Old DataLists some of the records that can be deleted and explains how to do so.
Recalculating Summary RecordsExplains how to recalculate summary records.
Introduction to EOP System Administration
Periodically, you should perform certain tasks to update records and to preserve database space.
• When you change certain records in other modules, or whenever certain conditions change in your company, you must update operations planning master data.
• Typically at year-end, you should delete and optionally archive obsolete plan records.
• If inconsistencies develop between global and site-level quantities, you must run a utility program to correct the problem.
The following topics cover these tasks.
Maintaining Static Data
When your company changes item numbers, intersite sourcing relationships, and so on, you must update records in the Enterprise Ops Plan module.
Events Requiring Operations Plan Record Updates lists events that require such updates.
Events Requiring Operations Plan Record Updates
|
Event
|
Update Operations Plan Records in
|
|
Item numbers change
|
Family Hierarchy Change (33.3.6)
Family Item Cost Maintenance (33.3.13)
Weeks of Coverage Maintenance (33.5.1)
Coverage by Date Maintenance (33.5.5)
Source Matrix Maintenance (33.5.13)
Line Allocation Maintenance (33.5.17)
Item Pallet Maintenance (33.5.23)
|
|
Item records are added or deleted
|
Family Hierarchy Maintenance (33.3.1)
Family Item Cost Maintenance (33.3.13)
Weeks of Coverage Maintenance (33.5.1)
Coverage by Date Maintenance (33.5.5)
Source Matrix Maintenance (33.5.13)
Line Allocation Maintenance (33.5.17)
Item Pallet Maintenance (33.5.23)
|
|
Target inventory levels change
|
Weeks of Coverage Maintenance (33.5.1)
Coverage by Date Maintenance (33.5.5)
|
|
Intersite sourcing relationships change
|
Source Matrix Maintenance (33.5.13)
|
|
Intrasite production line relationships change
|
Line Allocation Maintenance (33.5.17)
|
At year-end, additional activities are required:
• Verify that records in Family Hierarchy Maintenance (33.3.1) and Source Matrix Maintenance (33.5.13) are still valid for the remainder of your planning horizon. Update the end dates as necessary.
• Rerun Calendar Cross-Reference Build (33.1.4) for the remainder of your planning horizon (up to three years).
Deleting Old Data
The system does not automatically delete old operations planning records. To preserve disk space, you should periodically remove outdated records.
Records To Be Periodically Deleted
|
Data
|
Program
|
|
Family hierarchies
|
Family Hierarchy Delete/Archive (33.3.23)
|
|
Family plans
|
Operations Plan Delete/Archive (33.15.23)
|
|
Data loaded into Item-Site Data Maintenance (33.13.3)
|
Item-Site Data Consolidation (33.13.6), Delete Item-Site Load Records option
|
|
Operations plans
|
Operations Plan Delete/Archive (33.15.23)
|
|
Work orders generated by Operations Plan Explosion (33.15.13)
|
Work Order Delete/Archive (16.23)
|
|
Simulation plans
|
Simulation Delete/Archive (33.17.23)
|
Do not remove records until all processing is complete for the planning period. When selecting data to delete/archive, consider how you want to manage restorations.
Example: If you delete/archive an entire year’s history, you must reload the entire file even if you only need data for a day or week.
Establish procedures to handle archive files. Keep a separate record of the file name and contents because there is no label within the file. The ASCII file name identifies only the module and the file creation date. Then, if you later reload the data, you will know which file to load from.
Note: Set up role permissions for delete/archive programs. The system does not maintain an audit trail of deleted records.
Delete
Enter Yes to delete the selected records. Enter No to print a report of records to delete. Before deleting records, run this program with Delete set to No. Review the report, then rerun the program with Delete set to Yes.
Archive
Enter Yes to copy deleted records to a disk file to be stored off-line. If you ever need to restore data, copy the file back to disk. Then, use Archive File Reload (36.16.5) to reload the file.
Archive File
The Archive option generates an ASCII file called xxYYMMDD.hst, where xx is the record type and YYMMDD is the delete/archive date. If you already ran the delete/archive for this date, the system appends to the existing file.
Recalculating Summary Records
After a database crash or other such event, the system can develop inconsistencies between an item’s site-level and global quantities. If this happens, use Recalculate Summary Records (33.25.1) to rebuild family plan and operations plan summary records.
Recalculate Summary Records (33.25.1)
