RSOXML - BW Metadaten Repository: XML Import/Export
The following messages are stored in message class RSOXML: BW Metadaten Repository: XML Import/Export.
It is part of development package RSO in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "BW Repository: Infastructure and Core GUI Components".
It is part of development package RSO in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "BW Repository: Infastructure and Core GUI Components".
Message Nr ▲ | Message Text |
|---|---|
| 100 | ---------- Generic Messages XML Import / Export ------------------- |
| 101 | Specify an object type (with &1=...) in the URL |
| 102 | Specify an object name (with &1=...) in the URL |
| 103 | Specify an object version (with &1=...) in the URL |
| 200 | ---------- Importing CWM Metadata ------------------------------------ |
| 201 | &3 errors occurred when parsing document &1 (&2) |
| 202 | Rows &1, column &2: &3 |
| 203 | Type &1 for object &2 is not known |
| 204 | Object &1, type &2, could not be generated |
| 205 | Class &1 does not have any attributes or references with the name &2 |
| 206 | Imported object &1 (&2) is not newer. Not saved. |
| 207 | &3 errors occurred when parsing transport information for &1 (&2) |
| 208 | Import for object &1, type &2 |
| 209 | Parsing for object &1 (&2) |
| 210 | Saving object &1 (&2) |
| 211 | Object &1 (&2) has been saved successfully |
| 212 | Activation of object &1 (&2) |
| 213 | Activation of all objects with type &1 |
| 215 | Import objects |
| 216 | Saving the objects |
| 217 | Activation of the objects |
| 218 | SAP object &1 (&2) cannot be imported |
| 220 | The key for object &1 (&2) is missing from the XML Datei |
| 221 | Error saving the TLOGO data for object &1 (&2) in table &3 |
| 300 | ---------- Object-specific messages -------------------------------- |
| 301 | Error &1 in method DTA_GET_INFO for InfoProvider &2 |
| 400 | -------------------Messages for TLOGO XML ---------------------------- |
| 401 | &3 error(s) while parsing XML document for &1 (&2) |
| 402 | TLOGO type in the XML document (&1) is not equal to instance type (&2) |
| 403 | Analysis of the XML document for &1 (&2) resulted in &3 messages |
| 404 | Object name in XML document (&1) is not equal to the instance name (&2) |
| 405 | Tag <&1> (table &2) relates to an invalid field |
| 406 | Tag <&1> found. Tag <&2> expected |
| 407 | Error while creating the existentially dependent instance &1 &2 |
| 408 | XML error: Attribute &1 is not filled or does not exist |
| 409 | XML error: TLOGO key is empty. Current node name is &1 |
| 410 | XML error: Node <&1> not found |