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 |
Any |
|
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 |
Book data from the PSA into the data target (indicator in the Scheduler) |
|
BI_STRU |
Execute change run |
|
BI_AGGR |
Roll up data in an aggregate |
|
BI_SAGR |
Fill aggregates initially |
|
BI_STOR |
Cancel request |
|
BI_COMP |
Compress InfoCube |
|
BI_NEW |
Reconstruct data target |
|
BI_STAT |
Build index and statistics |
|
BI_HIER |
Save hierarchy |
|
BI_INDX |
Wrapping of index and statistic build (prefix is used in the manage) |
|
BI_ODSA |
Activate date in DataStore object |
|
BI_PSAD |
Delete PSA data |
|
BI_PROCESS |
Process chain jobs 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. |
|
BIREQU |
Extraction in source system (file, BAPI and Data Mart jobs run in BW system) |
|
BIDTPR |
Data transfer process |
|
BI_ARCH |
Data archiving process |
|
BI_RDA_<daemon number> |
Real-Time Data Acquisition |
|
BI_COPY |
Copy data flow |
Using the prefix BI_<XXXX> for a job you defined yourself can lead to the system deleting this job. For this reason, for jobs you define yourself, choose a name that starts with a different string.