Scheduling InfoPackages 

Use

Determine 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 access an external system with the data request, you must make the data available in special formats. You can find additional information about this in the sections Maintaining InfoSources (Flat Files) and Maintaining InfoSources (External Systems)).

Procedure

...

       1.      Select whether you want to start the batch load 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 the 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 the process chain maintenance and you want to process the data request in the background, select the radio button 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 Conditions for the Start Date when Scheduling an InfoPackages 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 in the Schedule tab page.  The load process remains active until the data is updated.

For example, 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 was processed successfully or incorrectly, select: Postprocessing. For more information on controlling processes using the event collector, see Process Control.

For controlling and monitoring BW processing as of release 3.0A, SAP recommends that you use Process Chains.

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 successor processes are set in the process chain, and not using the post processing events.

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

Result

The load process is started either immediately or later in the background, depending on your settings. You can use the monitor to check whether the load process was successful or not. After the load process is completed, successor processes are triggered if necessary, for example, when the InfoPackage was scheduled in a process chain.

Scheduled InfoPackages (and also 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 already scheduled InfoPackages, your new selection is used in later background jobs, for example, periodic runs. You must create a new InfoPackage if you want to keep the existing InfoPackage, in order to continue using it in the background.

 

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

SAP recommends you serialize these processes using process chains.