JOBREPO - Messages for Job Repository
The following messages are stored in message class JOBREPO: Messages for Job Repository.
It is part of development package STJR in software component BC-CCM-BTC-JR. This development package consists of objects that can be grouped under "Technical Job Repository".
It is part of development package STJR in software component BC-CCM-BTC-JR. This development package consists of objects that can be grouped under "Technical Job Repository".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Scope-dependent job definitions need further maintenance. See longtext. |
| 001 | Inactive version for JD &1 exists and please modify inactive version. |
| 002 | Please select a job definition. |
| 003 | Error in function "POPUP_TO_CONFIRM" |
| 004 | Job Definition &2 is already locked by &1. |
| 005 | Job Definition &1 cannot be locked. |
| 006 | Inactive version of Job Definition &1 cannot be deleted. |
| 007 | Job Definition &1 cannot be deleted. |
| 008 | Job Definition &1 cannot be retrieved. |
| 009 | Job Definition &1 cannot be saved. |
| 010 | No authorization to create a technical job definition |
| 011 | Inactive Object &1 cannot be transported. |
| 012 | Multi-Instance Job Definitions cannot be customized |
| 013 | Select a valid line |
| 014 | Technical Job Definition is currently locked by other user |
| 015 | Job Definition can't be customized/deactivated because it is not relevant |
| 016 | No authorization for changing Technical Job Definitions |
| 017 | Technical Job Definition is event-based. No customizing possible. |
| 018 | Job Definition cannot be saved because customizing is incomplete |
| 019 | Job Definition cannot be customized because it is deactivated |
| 020 | For job activation details please check the application log in SLG1 |
| 021 | with Object: &1 |
| 022 | and External ID: &1 |
| 023 | Size of worklist is &1 at &2 on &3. |
| 024 | Simulation mode is on for worklist. |
| 025 | Action mode is scheduling jobs. |
| 026 | Action mode is unscheduling jobs and force mode is &1. |
| 027 | Technical Job Definition has been deactivated. |
| 028 | Technical Job Definition has been reactivated. |
| 029 | Technical Job Definition has been customized. |
| 030 | Action cancelled |
| 031 | Job Definition &1 is customized. Time frequency is changed from &2 to &3. |
| 032 | Job Definition &1 is deactivated. |
| 033 | Job Definition &1 is reverted to standard. |
| 034 | Upgrade is running and no jobs are created or changed by Job Repository. |
| 035 | Generate job for JD &1 with variant &2. Time frequency is &3. |
| 036 | Delete job and settings for JD &1 with variant &2. |
| 037 | This is not a multi-instance job definition |
| 038 | Job for JD &1 with variant &2, time frequency &3 is not yet generated. |
| 039 | No Default Stepuser maintained in the current client |
| 040 | Job &1 is deleted due to obsolete job definition. |
| 041 | Job &1 is deleted due to obsolete client. |
| 042 | Customized entries are deleted due to obsolete job definition &1. |
| 043 | Scope entries are deleted due to obsolete job definition &1. |
| 044 | No report documentation exists for report &1. |
| 045 | In client &1, the default step user &2 already exists. |
| 046 | &1&2&3 |
| 047 | Step user creation is not allowed in this system configuration. |
| 048 | Error in function module 'USER_EXISTS' |
| 049 | User &1 has no SAP_ALL profile assigned. |
| 050 | Start to generate job &1 for job definition &2. |
| 051 | Job &1 for job definition &2 is generated. |
| 052 | Job &1 with count &2 from jd &3 is unscheduled. |
| 053 | Job &1 with count &2 from jd &3 cannot be unscheduled(&4). |
| 054 | Start to unschedule job &1 from jd &2. |
| 055 | Job &1 for job definition &2 with same settings was scheduled already. |
| 056 | &1&2&3&4 |
| 057 | JD &1 is not relevant for client &2. |
| 058 | Relevance check starts for JD &1. |
| 059 | Default step user is not given by CLMS_TENANT in S/4HANA Cloud system. |
| 060 | Background Job &1 exists already and the program compares settings. |
| 061 | Same name Background Job &1 exists but not with &2 as step 1. Check SM37! |
| 062 | Background Job &1 exists already but not scheduled by Job Repository. |
| 063 | Authorization check failed for JD &1. |
| 064 | Exception(&3) occurred in JOB_OPEN for job &1 with job count &2. |
| 065 | Exception(&3) occurred in JOB_SUBMIT for job &1 with job count &2. |
| 066 | Exception(&3) occurred in JOB_CLOSE for job &1 with job count &2. |
| 067 | JOB_OPEN for job &1 with job count &2 is ok. |
| 068 | JOB_SUBMIT for job &1 with job count &2 is ok. |
| 069 | JOB_CLOSE for job &1 with job count &2 is ok. |
| 070 | Set flag J in TBTCCNTXT meaning job &1(job count &2) from Job Repository. |
| 071 | Did not find scheduled background job for job definition &2. |
| 072 | Customizing attributes for JD &1 exist. |
| 073 | JD &1 is deactivated.Check table STJR_JOBD_CUST. |
| 074 | Job &1 with job count &2 is only scheduled and not released successfully. |
| 075 | Technical Job Definition has not been customized in current client |
| 076 | Report variant &1 is invalid. |
| 077 | Report and Job Definition are in different packages |
| 078 | Appending customizing data to transport request failed |
| 079 | No authorization for creating transport requests. Customizing not saved. |
| 080 | Attention: Job Terminations will always be ignored (see longtext) |
| 081 | Job &1 with count &2 and scheduled status is deleted. |
| 082 | Job &1 with count &2 and scheduled status cannot be deleted(&3). |
| 083 | Similar job &1 not from Job Repository with job count &2 is deleted. |
| 084 | Job &1 not from Job Repository with job count &2 cannot be deleted(&3). |
| 085 | Start to get report variant &2 for multi-instance JD &1. |
| 086 | JD &1 is not applicable for variant &2 since it is not multi-instance JD. |
| 087 | Cannot get variant &2 for multi-instance JD &1. Job is not generated. |
| 088 | Job generation is cancelled due to missing instance for JD &1. |
| 089 | JD &1 is multi-instance job definition without default instance. |
| 090 | JD &1 is multi-instance job definition with default instance. |
| 091 | JD &1 is set to "in scope" (&2~IS_JOBD_IN_SCOPE = TRUE). |
| 092 | JD &1 is set to "not in scope" (&2~IS_JOBD_IN_SCOPE = FALSE). |
| 093 | This multi-instance JD is scheduled with default settings (no variants) |
| 094 | This multi-instance JD has no job instances (see longtext) |
| 095 | Check current scope for scope dependent JD &1. |
| 096 | JD &1 is "in scope" according to table STJR_JOBD_SCOPE(Static Scoping). |
| 097 | JD &1 is "not in scope" according to table STJR_JOBD_SCOPE(Static Scope). |
| 098 | Apply variant &2 for multi-instance JD &1 to generate job instance. |
| 099 | Apply default instance for JD &1. |
| 100 | User cannot be created - no default usergroup defined in table USR_CUST |
| 101 | New default step user has been created in the current client |
| 102 | Default step user has been changed in the current client |
| 103 | The given report variant is not a system variant (see longtext) |
| 104 | Job Repository has been switched off in current client |
| 105 | Job Repository has been switched on in current client |
| 106 | No authorization for changing Job Repository status in this client |
| 107 | Set Job type to J for job &1(job count &2) failed in TBTCCNTXT. |
| 108 | Unschedule Job &1(jobcount &2) so that jobrepo flag is only in TBTCCNTXT. |
| 109 | Package should be &2. Click Change and activate to sync info. |
| 110 | No changes for client-specific objects allowed in this client |
| 111 | Changes saved locally without transport request |
| 112 | The job will be executed even when JobRepo is switched off (see longtext) |
| 113 | &1 as always run job or cloud technical client job is not unscheduled. |
| 114 | User &1 is not a system user. |
| 115 | No authorization to change default step user for SJOBREPO. |
| 116 | Client &1 specifies a nonexisting Job Repo step user &2 (note 2190119) |
| 117 | Client &1 specifies a locked Job Repo step user &2 (note 2190119) |
| 118 | Client &1 uses &2 as step user for Job Repo (note 2190119) |
| 119 | Client &1 does not specify a step user for Job Repo (note 2190119) |
| 120 | Solution: create/assign a Job Repo step user in client &1 (note 2664638) |
| 121 | User &1 is locked. |
| 122 | JobRepo is set to OFF in current client and only "always run" jobs run. |
| 123 | User &1 has no SAP_ALL profile assigned (see longtext). |
| 124 | Enter a username. |
| 125 | JD &1 is not applicable in technical client in cloud. |
| 126 | Variant does not exist in this client |
| 127 | JD &1 is deactivated.Check table STJR_JOBD_CONF. |
| 128 | JD &1 uses variant &2.Check table STJR_JOBD_CONF. |
| 129 | JD &1 uses variant &2.Check table STJR_JOBD_LOCL. |
| 130 | Variants cannot be changed in this system configuration |
| 131 | Variant has been changed in all clients |
| 132 | Variant has been changed in current client |
| 133 | Variant has been removed from Job Definition |
| 134 | The transaction is not relevant in Cloud Environment |
| 135 | Enter a user name |
| 136 | No authority to create/delete Default Stepuser |
| 137 | Stepuser is removed from Job Repository. Jobs will be unscheduled. |
| 138 | Target server or group &1 is wished in STJR_JOBD_LOCL. |
| 139 | Initial scope(changeable via IMG S_YI3_39000188) for JD &1 in on premise |
| 140 | Temporary tolerance of static scoping for JD &1 when config default ON |
| 141 | Start to check scope callback class state for JD &1 |
| 142 | Temporary tolerance of static scoping for JD &1 during migration phase |
| 143 | New change in scoping rule.Please read F1 help of Scope Class field. |
| 144 | Soft scope migration for JD &1 in on-premise systems |
| 145 | Generic (DEFAULT) user is used in this Z* or Y* job definition. |
| 146 | Target Servers cannot be added in this system configuration |
| 147 | Target group &1 is defined in STJR_JOBD_TARGET. |
| 200 | SAP_SDM_EXECUTOR_ONLINE_MIGR is deactivated and is not transportable |
| 201 | Targetserver(group) has been locally added to Job Definition |
| 202 | Targetservergroup has been added to Job Definition |
| 203 | Targetservergroup has been removed from the Job Definition |
| 204 | Targetserver(group) has been locally removed from Job Definition |
| 205 | Only targetservergroups can be transported |
| 207 | One of the JDs is not relevant in this client. No stepuser can be added. |
| 208 | SAP_SDM_EXECUTOR_* jobs must be executed by default stepuser |
| 209 | Local stepusers cannot be assigned in this system configuration |