| SMOG161 |
No valid version : &1 |
| SMOG162 |
Cannot decrease version 00001 |
| SMOG163 |
Version 99999: unable to increase version |
| SMOG164 |
Lock object & created |
| SMOG165 |
Replication table & created |
| SMOG166 |
Message structure name for BDoc &1 missing |
| SMOG167 |
Unable to activate lock object &1. Check the activation log. |
| SMOG170 |
*************** Repository WB messages ****************** |
| SMOG171 |
No entry possible |
| SMOG172 |
Repository object(s) successfully transported |
| SMOG173 |
Repository object(s) successfully generated |
| SMOG174 |
Error reading repository log |
| SMOG175 |
No log entries exist |
| SMOG176 |
Object &1 version from repository &1 in cluster missing |
| SMOG190 |
*************** Transport messages ****************** |
| SMOG191 |
BDOC object(s) successfully added to transport request &1 |
| SMOG192 |
Table object(s) successfully added to transport request &1 |
| SMOG193 |
Replication object(s) successfully added to transport request &1 |
| SMOG194 |
Publication object(s) successfully added to transport request &1 |
| SMOG195 |
Flow object(s) successfully added to transport request &1 |
| SMOG196 |
R/3 Adapter object(s) successfully added to tp. req. &1 |
| SMOG197 |
TR object(s) successfully added to transport request &1 |
| SMOG198 |
Repository object &1 is inconsistent (no transport) |
| SMOG199 |
BDOC repository object &1 successfully imported and generated |
| SMOG200 |
BDOC repository after import processing is starting now. |
| SMOG201 |
BDOC repository after import is deactivated |
| SMOG202 |
Repository object type &1 doesn't exist |
| SMOG203 |
No active replication object for trans_id &1 |
| SMOG204 |
No version for object &1 for namespace &2 found |
| SMOG205 |
&1 : No customer namespace allowed on SAP system |
| SMOG206 |
Unable to split namespace from object name &1 |
| SMOG207 |
Namespace &1 not allowed in system |
| SMOG208 |
Object &1 no customer namespace |
| SMOG209 |
Unable to split namespace from version &1 |
| SMOG210 |
SMOG_TRANS: &1 TRANSTYPE is not CRT |
| SMOG211 |
Link table &1: Source field &2 does not exist |
| SMOG212 |
Link table &1: Dest field &2 does not exist |
| SMOG213 |
Cannot lock object &1 with key &2 |
| SMOG214 |
RSS_TEMPLATE_INSTANTIATE & Error |
| SMOG215 |
No entry for GENKEY &1 and Key &2 in TGN_OBJREG |
| SMOG216 |
GENKEY &1 not in table SMOG_GNREG |
| SMOG217 |
Object &1 is locked by order &2 and therefore not transportable |
| SMOG218 |
Number range &1 already exists |
| SMOG219 |
No number range with name &1 |
| SMOG220 |
Maximum of number range & exceeded |
| SMOG221 |
Transport for &1 &2 &3 &4 failed |
| SMOG222 |
Transport for &1 &2 &3 &4 succeeded |
| SMOG223 |
Statement 'inserted includes' in top include &1 missing |
| SMOG224 |
Statement 'table statements' in top include &1 missing |
| SMOG225 |
No object name for &1 &2 |
| SMOG226 |
Type &1 does not exist |
| SMOG227 |
TRANSPORT_ORDER_MODE in SMOFPARSFA missing |
| SMOG228 |
No transport order found to release |
| SMOG229 |
There is no memo field |
| SMOG230 |
&1&2&3&4 |
| SMOG232 |
Index &1 created |
| SMOG233 |
No Development class for object with namespace &1 |
| SMOG234 |
Object &1 &2 does not exist |
| SMOG235 |
No valid object selected. |
| SMOG250 |
**** messages for consistency check of repository data **** |
| SMOG251 |
The data set is too large (more than &1 bytes) to save to the table &2 |
| SMOG252 |
Table &1 in SFA DDIC inactive |
| SMOG253 |
Table &1 in R/3 DDIC inactive |
| SMOG254 |
Field &1 of Table &2 does not exist in SFA DDIC |
| SMOG255 |
Field &1 of Table &2 does not exist in R/3 DDIC |
| SMOG256 |
Data element & does not exist in SFA DDIC |
| SMOG257 |
Data element & does not exist in R/3 DDIC |
| SMOG258 |
Data element &1 used in SFA DDIC differs from &2 in R/3 DDIC |
| SMOG259 |
No reference table defined in SFA DDIC for field &1 of table &2 |
| SMOG260 |
No reference table defined in R/3 DDIC for field &1 of table &2 |
| SMOG261 |
Reference table in SFA DDIC ( &1&2) differs from in R/3 DDIC ( &3&4) |
| SMOG262 |
There is more than one version for Bdoc &1 with status &2 |
| SMOG263 |
Bdoc &1 has &2 root segments |
| SMOG264 |
Parameter &1 is not used |
| SMOG265 |
Invalid where-clauses &1 for segment &2 |
| SMOG266 |
Invalid join-condition &1 for segment &2 |
| SMOG267 |
Invalid mapping for field &1 of segment &2 to table &3 ( &4) |
| SMOG268 |
Parameter &1 has different domain from its where-clause &2 |
| SMOG269 |
R/3 structure name &1 is already in use. Choose another one. |
| SMOG270 |
Unicode setting in field &1 of segment &2 inconsistent |
| SMOG271 |
&1 update table(s) defined for segment &2 |
| SMOG272 |
No primary key defined for segment &1 |
| SMOG273 |
No Stored Procedure defined for segment &1 |
| SMOG274 |
Domain & does not exist in SFA DDIC |
| SMOG275 |
R/3-structure name for segment(s) is not allowed |
| SMOG276 |
A BDoc should at least have one segment, but &1 has no segment |
| SMOG277 |
Wrong or missing namespace for R/3-structure name |
| SMOG278 |
Repository object &1 with status &2 does not exist |
| SMOG279 |
No active nametab exists for &1, &2 ( &3) |
| SMOG280 |
No Stype defined for field &1 of segment &2 |
| SMOG281 |
Check failed for where-clause &1 |
| SMOG282 |
Table &1 in where-clause(Order = &2 ) differs from mapped table &3 |
| SMOG283 |
No R/3-structure name defined for segment &1 |
| SMOG284 |
No parent segment found for segment &1 |
| SMOG285 |
&1 | &2 | &3 | &4 |
| SMOG286 |
Child segment &1 must have a parent key, but &2 parent key was specified |
| SMOG287 |
Root segment &1 may not have parent key, but &2 parent key was specified |
| SMOG288 |
Segment order in BDoc &1 not unique |
| SMOG289 |
Field order in segment &1 not unique |
| SMOG290 |
Not all fields in segment &1 were mapped to table fields |