SCTC_SC - CTC System Copy
The following messages are stored in message class SCTC_SC: CTC System Copy.
It is part of development package S_LMCFG_SC in software component BC-INS-TC-CNT. This development package consists of objects that can be grouped under "System Copy Backend Functions".
It is part of development package S_LMCFG_SC in software component BC-INS-TC-CNT. This development package consists of objects that can be grouped under "System Copy Backend Functions".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Could not find directory &1 |
002 | Error in communication to application server (RC &1 &2) |
003 | Parameter Error (&1 &2 &3 &4) |
004 | &1 &2 &3 &4 |
005 | Missing authority &1 |
006 | The system could be a production system; productive client &1 found |
007 | The system could be a production system; wrong target SID |
008 | The system could be a production system; TMS SID: &2; target SID: &4 |
009 | The system could be a production system; TMS SID: &2; source SID: &4 |
010 | Enter valid SIDs |
011 | No such file or directory &1&2 &3 |
012 | Illegal character in &1 |
013 | The system could be a production system |
014 | Error while reading licences; return code &1&2 |
015 | Error while deleting licence ( Hardware &1 Product &2 ) |
016 | Error while deleting licence ( SID &1 Hardware &2 Product &3 ) |
017 | Error while inserting DBCON entry ( &1 &2 ) |
018 | Error while inserting DBCONUSER entry ( &1 &2 ) |
019 | Could not install license &1&2; check license file |
020 | CTC control file &1 not existing |
021 | Error in r3trans execution; return code &1 |
022 | Flush of RSPO caches not successful |
023 | Could not switch to new operation mode |
024 | CTC control file successfully processed |
025 | Error while saving TSLE4 (RC &1 ) on server &2 |
026 | The following messages contain list output |
027 | Invalid schedule mode &1 |
028 | Check failed: &1 &2 &3 &4 |
029 | SAPICC: Call Error |
030 | System &1 checked; no error reported by SICK |
031 | System &1 checked; error reported by SICK |
032 | Job open failed for &1; return code &2 |
033 | Job submit failed for &1; return code &2 |
034 | Job close failed for &1; return code &2 |
035 | CTC Control files will be deleted |
036 | CTC Control files will be not deleted |
037 | Could not delete CTC control file &1 &2 |
038 | CTC control file &1 deleted |
039 | Access to &1 failed; return code &2 |
040 | Data import of table names aborted; open file &1 error &2 |
041 | Invalid table name &1 |
042 | Open CTC control file &1 failed with error &2 |
043 | Refresh directory: &1 &2 &3 &4 |
044 | Directory is missing |
045 | File name is missing |
046 | Table &1 successfully checked |
047 | Table &1 does not exist in data dictionary |
048 | &1: &2 records removed |
049 | Table &1: Truncate failed; return code &2 |
050 | Job selection failed (RC &1 &2) |
051 | No Job matches the selection criteria |
052 | File &1 (directory &2) deleted |
053 | File &1 (directory &2) written |
054 | Character &1 not allowed in SID &2 |
055 | Call to &1 failed; return code &2 |
056 | Function not available; refer to note 1413577 |
057 | Could not find logical system name |
058 | Component name is empty |
059 | New Logical System Name &1 is equal to old Logical System Name &2 |
060 | Component &1 is not supported |
061 | Generation of program &1 failed |
062 | Avoid character '&1' in logical system name; refer to note 606757 |
063 | Error while getting information on work processes |
064 | Insufficient number of batch processes for concurrent jobs (at least 4) |
065 | Unknown variant &1 |
066 | &1 is not a valid action |
067 | No statistics from program RBDLSMAP; switch to program RBDLS2LS |
068 | Program not available; refer to note 1179714 |
069 | BAdI &1 not implemented |
070 | Customer sends table name &1 for action &2 |
071 | Unable to perform post configuration until profile parameter &1 is not &2 |
072 | Missing authority &1 fields &2 for component &3 |
073 | Missing authority &1 fields &2 for table &3 |
074 | DBMS &1 is not supported |
075 | &1 is not allowed for component &2 |
076 | Function &1 is not available; refer to note &2 |
077 | Insert table name &1 in table BDLSEXZ |
078 | Additional Information for Customer Exit (Parameter IV_CUST_INFO): &1 |
079 | Job &1 with number &2 released |
080 | Sign &1 not supported; supported signs: &2 |
081 | Options &1 not supported; supported options: &2 |
082 | Only values starting with '/' followed by [A-Z0-9] supported |
083 | Only values starting with [A-Z0-9] supported |
084 | Intervals not supported |
085 | No table for pattern &1 &2 (RBDLS_CHECK and excluding see note 932032) |
086 | Characters &1 only for option &2 supported |
087 | Invalid conversion pair &1 to &2 |
088 | New logical system name is empty |
089 | Field &1 is initial |
090 | Client &1 has more than 1 old logical system name (&2 and &3) |
091 | Client &1 has more than 1 new logical system name (&2 and &3) |
092 | Only 1 line per client supported |
093 | No table pattern without at least one partner conversion pair |
094 | No old logical system name provided |
095 | Only remote call to own system supported (RFC SID &1) |
096 | Remote call failed: RC&1 &2 &3 &4 |
097 | Parameter Max Size is initial |
098 | Selection of active batch jobs failed; return code &1 |
099 | Aborting of active batch job &1 failed; return code &2 |
100 | Existing domain configuration will be overwritten |
101 | Force mode not allowed for SAP systems; domain will not be deleted |
102 | Wrong transport domain: &1 found &2 searched |
103 | Update transport configuration failed |
104 | Unknown target group &1 |
105 | System &1: No locks set |
106 | System &1: No locks reset |
107 | System &1: No lock found |
108 | System &1: Still locked |
109 | Transport domain is missing |
110 | Local transport domain configured (single system) |
111 | System ID &1 is missing |
112 | System &1 included in transport domain |
113 | Transport requests originating from this system found |
114 | No systems before or after this system found; single system? |
115 | System &1 did not belong to transport domain &2 |
116 | System &1 is domain controller for domain &2 |
117 | Current system &1 is not the target system &2 |
118 | System &1 already configured in domain &2 |
119 | Error in TP execution; return code &1 |
120 | Buffer &1 moved to &2 |
121 | Move of buffer &1 failed |
122 | Duplicate systems in path from &1 to &2 |
123 | System &1 already configured |
124 | Unknown transport domain &1 |
125 | TADIR update, set WBO change to &1, user is &2 |
126 | No data for client &1 found |
127 | Configuration data is for client &1 not client &2 |
128 | Client &1 is not a valid client |
129 | No client entered |
130 | Excluding all available clients |
131 | No table names for component &1 found |
132 | Central User Administration is active; no user data export possible |
133 | No address data found |
134 | &1 is not a valid client information |
135 | Buffer &1 copied to &2 |
136 | Copy of buffer &1 failed |
137 | Central User Administration is inactive |
138 | Path to transport directory initial |
139 | Target system uses TMS QA procedure: Function unsupported |
140 | Parameter &1 changed: Old &2 New &3 |
141 | Function &1 not available |
142 | Destination could not be changed |
143 | Abnormal end of r3trans execution in function &1 for component &2 |
144 | Installation number &1 found |
145 | More than 1 installation number found |
146 | License &1 for installation number &2 deleted |
147 | RFC import failed due to installation number mismatch: &1 <> &2 |
148 | No errors found |
149 | Directory &1 found |
150 | &3 spool records removed from table &1 in client &2 |
151 | File &1 found |
152 | Selected batch jobs removed |
153 | Character &1 not allowed in Logical System Name &2 |
154 | Single Job Execution not possible for multiple conversion pairs |
155 | Invalid Logical System Name Mapping; check conversion pairs |
156 | Spool servers successfully assigned |
157 | Folder &1 moved to &2 |
158 | Could not move folder &1 to &2 |
159 | SAP standard jobs created (see /nsm37) |
160 | Job Execution Mode only possible with Single Job Execution |
161 | Table &1: All records successfully removed |
162 | No spool related folders found to be moved |
163 | Directory contains illegal characters |
164 | Job Execution Mode only possible with Concurrent Jobs based on Table Name |
165 | Select only LOCK TMS Queues or only UNLOCK TMS Queues |
166 | Disc Capacity data not available, SAPOSCOL not running |
167 | Profile parameter value for PCA_DIR &1 not found |
168 | Disc Capacity for Export Directory: &1 |
169 | Disc Capacity: &1 |
170 | Disc Space Capacity &1 MB on device &2 |
171 | Disc Space Capacity is sufficient for PCA Export |
172 | Disc Space Capacity is ready for PCA Export |
173 | Disc Space Capacity is not sufficient for PCA Export |
174 | Error in creation of directory for ALOG Copy &1 |
175 | Directory for ALOG Copy &1 created |
176 | TMS ALOG Files copied |
177 | TMS ALOG Files not copied |
178 | TMS ALOG Files deleted |
179 | TMS ALOG Files not deleted |
180 | Could not find logon group |
181 | No application servers found for logon group &1 |
182 | R3trans encountered scrap chars (note 718511) for component &1 |
183 | Directory is accessible |
184 | File system check not successful; return code &1 |
185 | R3trans - failed to execute external command |
186 | R3trans release: &1 Patch level: &2 |
187 | R3trans not supported with release < 7.20 |
188 | R3trans patch level too low (min. &1) |
189 | Lock problem in transaction RZ04 |
190 | Could not find profile parameter value for CTC_DIR &1 |
191 | <<<<< Import: CTC Control file >>>>> |
192 | Creation of CTC control check file &1 successful |
193 | Could not create CTC control check file &1 |
194 | &1 components with &2 MB exported to export directory |
195 | &1 shutdown of ICM server &2 started |
196 | Could not &1 shutdown ICM server &2; return code &3 |
197 | System distributes PSE |
198 | Table TADIR Entry HEAD SYST modified to system name &1 |
199 | STRUST: &1&2&3&4 |
200 | Opening Job for &1 failed, return code &2 |
201 | Closing Job for &1 failed, return code &2 |
202 | Export for component &1 not necessary, tables not existing |
203 | Instance name saved in TSLE4 (RC &1 ) on server &2 |
204 | Import customer component failed, empty BADI implementation for tables |
205 | PSE distribution status for server &1: |
206 | No PSE found for distribution, check transaction STRUST |
207 | No Logongroups available |
212 | &1 background jobs found to be deleted |
213 | Enter component name |
214 | Enter a valid component name |
215 | Customer table &1 as view identified; only tables will be exported |
220 | Task List Runtime Environment |
221 | Task Manager Version &1 |
222 | Task List Name &1 |
223 | Created on &1 by user &2 |
224 | Changed on &1 by user &2 |
225 | Copied from Task List &1 |
226 | Build Number &1 |
227 | Task List is obsolete |
228 | Task List Run &1 |
229 | Execution system &1 on host &2 in client &3 |
230 | R3Trans and Directory Capacity Check |
231 | R3trans encountered garbage character for component &1 |
274 | Error in creation of directory for SEC_INFO_FILES &1 |
275 | BACKUP SEC_INFO_FILES directory &1&2 created |
276 | Copy BACKUP SEC_INFO_FILES done &1 |
277 | SEC_INFO_FILES not existing &1 |
278 | Old BACKUP SEC_INFO_FILES deleted &1&2 |
279 | Old BACKUP SEC_INFO_FILES not deleted &1&2 |
280 | &1 Path Definition found in OP System Environment &2 |
281 | Error in creation of SECUDIR directory &1 |
282 | BACKUP SECUDIR directory &1&2 created |
283 | Restore SECUDIR &1 from Backup dir &2&3 done |
284 | Restore SECUDIR &1 from Backup dir &2&3 failed |
285 | &1&2&3&4 |
286 | Copy BACKUP Directory SECUDIR done &1 |
287 | SECUDIR not existing &1 |
700 | Execution of function &1 started |
701 | Access to internal passport failed (RC &1) |
702 | Access to own logical system failed (RC &1) |
703 | Access to stored session ID failed |