Maintenance plans can be used to perform routine database operations. After you create a plan, you can save it and reuse it.
INVOICES has two types of maintenance plans, described below:
To keep INVOICES running smoothly, it is important to detect and repair discrepancies in the database. INVOICES makes this task easy with database maintenance plans. You can save and organize maintenance plans, giving you easy access to INVOICES' built-in maintenance features.
Apart from handling corrupt data, INVOICES' database maintenance feature can also clear the database from objects that are no longer needed, making INVOICES more efficient.
Note: If the maintenance plan deletes invoice definitions due to data corruption, any invoices connected to them that have not yet been transferred will have their status set to Scanned. You must process these invoices again in Interpret and Verify. (You must have at least one Interpret job with the Source setting set to Internal, to detect and process these invoices.)
Note: By default, maintenance plans do not remove objects that have read errors (which appear as "ReadBO" in the log file), as the problem may not be due to a corrupt object, but due to network connectivity or database issues. To remove these objects as well, use MaintenanceRepairReadBO in Eilocal.ini.
Master data can change frequently, so it is important to update it routinely and automatically. Use maintenance plans to import master data from your financial system on a regular basis.