These functions should be run occasionally or periodically to keep the size of the database to a minimum and to have valid and correct data.
To run a batch job with no auto jobs, you must shut down the subsystem for auto start jobs and then start CMNGJOB. See instructions in M3 Business Engine Administrator’s Guide for Auto Start Jobs and Subsystems.
This function should be run periodically.
The function calculates the search sequence in the order attribute file in this sequence:
Counting the number of different attribute values per item and attribute identity in the stock.
Once completed, the values are turned into negative and are placed in the search sequence field.
Using this calculation, the search starts to validate the attribute where the most different values exist.
If you start to validate the attribute, the result will be the least possible number of balance identities.
This function should be run occasionally or periodically to keep the size of the database to a minimum.
The function performs a cleanup of the database with these activities:
Attribute searches in, for example, 'Balance Identity. Display' (MMS060) and 'Balance Identity. Open Toolbox' (MWS060), creates a record attribute with a negative number. These are normally not deleted when the user exits the function and therefore remain in the database. This is done for performance reasons.
If the check box 'Temp attrib no' is selected, the temporary attributes are deleted.
To do this, the function scans through the attribute files and confirms that each attribute number has a corresponding order. Normally, these records are deleted when an order is deleted, but if the user session is interrupted for any reason, these records remain in the database.
If the check box 'Orphn attrib no' is selected, the orphaned attributes are deleted.
This function starts 'Macro Orders. Delete Not Used' (PMS992).
This function should be run periodically when there are many changes in the product structure.