BW_ACTIVATE_INFOPACKAGE

Schedules one or more InfoPackages for immediate start

Transaction: RSA1

Syntax

BW_ACTIVATE_INFOPACKAGE

Syntax

Description/Format

NAME=

The technical name of an InfoPackage.

Format of value: script literal

ERROR= 

The required handling when an InfoPackage ends abnormally.

Format of the value: script literal

Allowed values: "ABEND" or "IGNORE" (default: "ABEND")
"ABEND" = The script aborts, the AE job ends abnormally.
"IGNORE" = The script continues, the AE job ends normally.

NOFOUND= 

The handling when the InfoPackage cannot be found.

Format of the value: script literal

Allowed values: "NORMAL" or "ABEND" (default: "NORMAL")
"NORMAL" = The script continues, the AE job ends normally.
"ABEND" = The script aborts, the AE job ends abnormally.

MAXRUNTIME= 

The maximum time in seconds in which the scheduled InfoPackages are monitored.
Format of the value: Number 
Default value: "86400"
LOG=

This value determines whether log messages of InfoPackages should be included in the job report.

Allowed values: "YES" or "NO" (default)
"YES" - Log messages will be included in the job report.
"NO" - The job report does not include log messages of InfoPackages.

Using this script element requires that the related InfoPackage is not scheduled. You can retrieve the technical name of the InfoPackage by using BW_GET_INFOPACKAGES. The script element stays active as long as the loading job in SAP BW has ended.The AE job will abort when the loading job does not end normally.

This script element can also be used without the parameter NAME=. In doing so, you can schedule several InfoPackages for immediate start in one step. The parameters NOFOUND= and ERROR= can be used to specify the reaction of AE when InfoPackages cannot be found or if one of the InfoPackages ends abnormally.

If InfoPackages are manually set to the quality status "Y" (yellow) in the administrator workbench, the AE job that has scheduled them will never end. With the parameter MAXRUNTIME=, you can specify how long the InfoPackage should be monitored. If this amount of time is exceeded, you can use the parameter ERROR= in order to decide whether the AE job should abort or continue.

Warning! A data-transfer process must be started after the loading process if you use BW 7.x DataSources and Transformation Services (as of SAP NetWeaver 04s).
Tip: Define suitable process chains in the BW that can be handled with BW_ACTIVATE_CHAIN.

Examples

The first example schedules an InfoPackage for immediate start. The waiting time for request ends after a maximum of one hour.

BW_ACTIVATE_INFOPACKAGE NAME="ZPAK_6LX4XTMC3RJ2DF4F09NFIJW98",MAXRUNTIME=3600

The second example selects all InfoPackages whose long text includes the sample "AE:*Text*". Afterward, the InfoPackages are scheduled for immediate start. Each error that occurs should cause the AE job to abort.

BW_SET_INFOPACKAGE_SELECTION SELNAME='TEXTLONG',SIGN='I',OPTION='CP',LOW='AE:*Text*'
BW_ACTIVATE_INFOPACKAGES NOFOUND='ABEND',ERROR='ABEND'