Scheduling InfoPackages 

Use

Define the start conditions for the InfoPackage on the Schedule tab page.

Prerequisites

You have defined the conditions for data request on the scheduler tab page.

If you are accessing a flat file or a non-SAP system with the data request, you have to make the data available in particular formats. For more information, see Maintaining InfoSources (Flat Files) and Maintaining InfoSources (External Systems).

Procedure

...

       1.      Select whether you want to start the batch loading process immediately or later on.

Scheduling in the background is not possible for data requests from a client work station. In this case, you can only select Start Data Load Immediately. You can find additional information about loading flat files under Maintain InfoSource (Flat File) and under Tab Strip: External Data.

The initialization and execution of an InfoPackage is implemented as a process type in process chain maintenance. The Start Later in Batch setting is hidden if the InfoPackage is used in a process chain. This is because the start of the request is determined by the process chain itself.

If you do not use the InfoPackage in process chain maintenance, and you want to process the data request in the background, select Start Later in Batch and define the required start time. If start times already exist for this data request, this is indicated with a  next to the Scheduling Options pushbutton. You can change the start time using Settings Options. You can also enter an end date for the data request with a background job.

See also:

Selection Criteria for the Start Date when Scheduling an InfoPackage in the Background

If you schedule an InfoPackage in the batch later, the background request job runs until all data is updated in BW. This is displayed with a corresponding indicator on the Schedule tab page. The loading process remains active until the data is updated.

Among other things, this gives external scheduling tools the option of monitoring the request job. The job then also runs with a request from an SAP source system as long as the source system has sent the data to the BW system and posted it or until the monitor sets the request to red. In the job log, a success or error message is displayed according to whether the request was posted successfully or not.

       2.      If you want to trigger an event that is to be used in the event collector after it has (either successfully or incorrectly) processed, select:Postprocessing.

To control and monitor BW processes, we recommend using process chains however.

If you are using an InfoPackage in a process chain, it can no longer be started in the background using the scheduler.

The Postprocessing setting is hidden when the InfoPackage is used in a process chain. This is because subsequent processes are set in the process chain, and not by using the postprocessing events.

       3.      Press Start in order to start loading immediately or to schedule it.

Result

The loading process is started either immediately or later in the background, depending on your settings. You can use the monitor  to check whether the loading process was successful. Once the load process is completed, any subsequent processes are triggered, for example if the InfoPackage has been scheduled in a process chain.

Scheduled InfoPackages (and InfoPackage groups) are denoted by a  in the Administrator Workbench. You can delete or change the scheduled InfoPackages (and InfoPackage groups) at any time.

If you change InfoPackages that have already been scheduled, your new selection is used for all subsequent background jobs, such as periodic runs. If you want to keep the existing InfoPackage in order to continue using it in the background, you have to create a new InfoPackage.

 

Note that some processes lock. See Process Lock Logic for ODS objects and Process Lock Logic for InfoCubes.

We recommend serializing these processes using process chains.