Title
Activating changes scheduled up to the current date

Purpose
With this program you can activate all changes to application objectsof the business data toolset that are scheduled up to the current date.
If you want to activate all changes relating to business partners, youhave to enter the application object 'BUPA'.
If the activation run encounters errors, you can display the changes inquestion by way of the normal business partner dialog and eliminatethem by calling change document display for the partner, and deletingthe scheduled changes that have been recognized as being incorrect. Ifnecessary, you can display the scheduling data that cannot be activated(by calling the business partner with the maintenance date of thefollowing day) and transfer them manually to the database (by callingmaintenance with the current date).
If the reason for the activation error lies in Customizing (fields arehidden, for example, you can start the program again once you have madecorrections.
If the 'No incorrect scheduled data' indicator is set, all data thathas already been recognized as being incorrect in a previous activationrun will not be considered in this new run.
If the indicator 'Delete incorrect scheduled data' is set, all datathat was recognized in this activation run as incorrect is cancelled;i.e. they appear in the error log, but are no longer taken into accountin all subsequent activation runs. This measure makes senseparticularly if much incorrect scheduled data exists, making a correctrun or subsequent manual processing impossible. As a rule, thissituation arises when there has not been an activation run for a longtime, and in the mean time most changes have been written manually tothe database. In this case, the planning basis has been changed to suchan extent that errors occur in most of the schedulings (which are inany case outdated.)
With the parameter 'Maximum Number of Activations', you can limit thenumber of records to be activated in a run. This can be necessary whena large number of schedulings are due to be activated. In this case atermination can occur due to runtime being exceeded. In this case, thenumber of records should be limited to 500 - 2000, according to theworkload and timeout parameter.
To guarantee on-going activation of all scheduled business partnerdata, you should include this program in a daily background processingrun.