Naming Conventions for Background Jobs

Names for background jobs are composed of a prefix and suffix:

Job prefix	Job suffix
7 characters	25 characters
set by the system depending on the background job type	no restrictions
BI_BTCH	3P5WWALPUEITOUTYQ9T6MVO8F

Note: The prefix BI_<XXXX> is reserved for internal processes of the BW system, for example, InfoPackage-Jobs:

Job prefix	Process
BI_BTCH	Request data for the InfoPackage (request)
BI_DELR	Delete request from the data target
BI_REQD	Automatically delete requests from the InfoCube (when loading)
BI_BOOK	Further book data from the PSA into the data target (indicator in the Scheduler)
BI_STRU	Execute change run
BI_AGGR	Roll up data into an aggregate
BI_SAGR	Fill aggregates initially
BI_STOR	Cancel request
BI_COMP	Compress InfoCube
BI_NEW	Reconstruct data target
BI_STAT	Index- and statistics build / delete request from the PSA (PSA tree in the AWB  ® PSA  ® Request  ® Delete)
BI_HIER	Save hierarchy
BI_INDX	Wrapping of index and statistic build (prefix is used in the manage)
BI_EVEN	Event Collector
BI_ODSA	Activate data in ODS Objects
BI_PSAD	Delete PSA data (PSA tree in the AWB  ® PSA  ® Delete PSA data)

Using the prefix BI_<XXXX> with a self-defined job can lead to the system deleting this job. For this reason, for jobs you define, choose a name that starts with a different string.

Possible consequences of using a job prefix that is reserved for BW internal processes:

Jobs with the prefix BI_BTCH are used by the BW system for requests for the InfoPackage. The Scheduler checks jobs with this prefix to see whether they are valid or not. The jobs are deleted if they are not InfoPackage jobs.

Process Chain Jobs

Process chain jobs begin with BI_PROCESS. If you remove a process chain from the scheduling, the jobs scheduled in the process chain are deleted, as are all other jobs BI_PROCESS_* that are not scheduled in another chain. Note: Do not define jobs with the name  BI_PROCESS_* yourself.