| RSAR167 |
The password for the OLTP user must be at least 5 characters long. |
| RSAR168 |
Password for the BI-ALE user is not correct |
| RSAR169 |
The passwords entered do not agree with one another. |
| RSAR170 |
Invalid data source: & (valid values: A, C) |
| RSAR171 |
Error when reading control file & (type &) |
| RSAR172 |
Error when reading data file & (type &) |
| RSAR173 |
User successfully created |
| RSAR174 |
It is not possible to create source system & manually - see long text |
| RSAR175 |
Source system does not exist |
| RSAR176 |
Source system has same name as BI |
| RSAR177 |
Error when creating the RFC destination & |
| RSAR179 |
Invalid source sytem type |
| RSAR180 |
Error when opening the data file & (origin &) |
| RSAR181 |
Error when reading data file & (origin &) |
| RSAR182 |
Requested file & (origin &) does not contain any data |
| RSAR183 |
Requested file & (origin &) contains obselete data |
| RSAR184 |
Record & of requested file & (origin &) is invalid |
| RSAR185 |
Invalid number of records in file & (origin &) |
| RSAR187 |
The entered saving location in row & of the control file is invalid |
| RSAR188 |
The file type entered in row & of the control file is invalid |
| RSAR189 |
The file name entered in row & of the control file is invalid |
| RSAR190 |
Invalid number entry in row & of the control file |
| RSAR191 |
InfoObject & contains invalid characters in record & in value & |
| RSAR192 |
InfoObject & does not fulfill ref. integrity in record & in value & |
| RSAR193 |
Errors occurred when reading ODS & (ref. integrity cannot be checked) |
| RSAR194 |
Formula in InfoObject &: & |
| RSAR196 |
InfoObject & contains non-alpha compliant value & |
| RSAR197 |
Record &:Contents & from field & cannot be converted in type & ->longtext |
| RSAR198 |
Record &:Contents & from field & cannot be converted in type & ->longtext |
| RSAR200 |
*** Meta data maintenance *** >> 399 *** |
| RSAR201 |
Source system & already exists. |
| RSAR202 |
Source system & can no longer be used. |
| RSAR203 |
Source system & does not exist |
| RSAR204 |
Error when calculating the node level in a hierarchy |
| RSAR205 |
No hierarchies available for InfoSource & (&), source system & |
| RSAR206 |
No meta data differences exist for source system & |
| RSAR207 |
InfoSource type & is not known |
| RSAR208 |
InfoSource & (&) is not known |
| RSAR209 |
No fields exist for InfoSource & (&) |
| RSAR210 |
InfoObject &1 is not available |
| RSAR211 |
Saving of communicatioin structure & in Dictionary failed |
| RSAR212 |
Activation of communication structure & in Dictionary failed |
| RSAR213 |
Function canceled due to user entry |
| RSAR214 |
& & activated |
| RSAR215 |
Source system & is not an external system |
| RSAR216 |
InfoSource type & (&) is not allowed here |
| RSAR217 |
Conversion exit & not available |
| RSAR218 |
No conversion exits found |
| RSAR219 |
& & & & does not contain fields |
| RSAR220 |
Communication structure & does not contain any fields |
| RSAR221 |
DataSource & (&) not available for source system & |
| RSAR222 |
Communication structure name & is not the same as & |
| RSAR223 |
Error & while generating transfer structure on source system & |
| RSAR224 |
Transfer structure & could not be deactivated |
| RSAR225 |
Master data InfoSoure & does not deliver any data |
| RSAR226 |
Master data InfoSource & refers to an invalid InfoObject |
| RSAR227 |
No transfer rules available for InfoObject & |
| RSAR228 |
You are not allowed to create hierarchies manually for ERP systems |
| RSAR229 |
Field name & used several times |
| RSAR230 |
No source system defined for client(s) & |
| RSAR231 |
Field definitions and change indicators are not synchronous |
| RSAR232 |
Error & when generating the upload program: Row &, message: & |
| RSAR233 |
Error & when compiling the upload program: row &, message: & |
| RSAR234 |
Error & when loading external data |
| RSAR235 |
Invalid statement(s) in the control file |
| RSAR236 |
InfoSource & already exists |
| RSAR237 |
Communication structure & for InfoSource & not found |
| RSAR238 |
IDoc type for source system & is not available |
| RSAR239 |
Name of source system BI is not defined (client &) |
| RSAR240 |
IDoc segment & could not be assigned to IDoc & |
| RSAR241 |
Rec. length of control file & does not correspond to that of IDOC seg & |
| RSAR242 |
The transfer structures and template do not have fields |
| RSAR243 |
InfoSource & (&) is already connected to source system & |
| RSAR244 |
No attributes exist for InfoObject & |
| RSAR245 |
Error generating program |
| RSAR246 |
Transfer structure for InfoSource & (&), source system & not available |
| RSAR247 |
Error & when activating report & |
| RSAR248 |
Error when determining the technical name of the InfoSource |
| RSAR249 |
InfoObject for the communication structure & cannot be determined |
| RSAR250 |
No fields selected, saving not possible. |
| RSAR251 |
Saving not possible, error in the transfer rules (change). |
| RSAR252 |
Communication structure for InfoSource & not maintained |
| RSAR253 |
Communication structure & could not be deactivated |
| RSAR254 |
Standard InfoSources cannot be changed |
| RSAR255 |
You are not allowed to maintain InfoSources of ERP systems manually |
| RSAR256 |
The communication structure does not contain InfoObjects |
| RSAR257 |
InfoSource & (&) not deleted |
| RSAR258 |
InfoSource & (type &) deleted |
| RSAR259 |
InfoObject for unit or currency key will be automatically transferred |
| RSAR260 |
Source system & is not active for this BI |
| RSAR261 |
Source system & not deleted |
| RSAR262 |
Source system & deleted |
| RSAR263 |
Error in global conversion rule for InfoObject & |
| RSAR264 |
Unit field & is not available in the InfoSource |
| RSAR265 |
Assignment of InfoSource & (&) to source system & not deleted |
| RSAR266 |
Assignment of InfoSource & (&) to source system & deleted |
| RSAR267 |
InfoSource & (&) cannot be deleted |
| RSAR268 |
Assignment of InfoSource & (&) cannot be deleted |
| RSAR269 |
The selection of the InfoObjects to be removed was adjusted |
| RSAR270 |
Only those InfoObjects not being used will be deleted |