BTFR_MESS - Nachrichten BTFR-Texverwaltung
The following messages are stored in message class BTFR_MESS: Nachrichten BTFR-Texverwaltung.
It is part of development package SBTFR in software component BC-SRV-OTR. This development package consists of objects that can be grouped under "Text Storage in BTF".
It is part of development package SBTFR in software component BC-SRV-OTR. This development package consists of objects that can be grouped under "Text Storage in BTF".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | No text found |
| 002 | Invalid package |
| 003 | The concepts with errors have been deleted |
| 004 | Error with the list output |
| 005 | No usage found for the concept |
| 006 | Invalid concept ID |
| 007 | No inconsistent entry found |
| 008 | At least one of the newly created alias names exists in the new package |
| 009 | No entry found |
| 010 | Text saved |
| 011 | You are not authorized to display OTR |
| 012 | No concept has been selected |
| 013 | Text lengths have been changed |
| 014 | Invalid package &1 |
| 015 | Script statements in the text are escaping |
| 016 | Enter an object name |
| 017 | All concepts were reassigned |
| 020 | You are not authorized for OTR administration |
| 030 | The concept has been included in request &1 |
| 100 | Enter an object type |
| 101 | No BTFR texts are used in &1 |
| 102 | No text was found that meets the selection criteria |
| 103 | The fuzzy search did not find any suitable texts |
| 104 | Enter a package and/or object type and object name |
| 105 | No package exists that meets the selection criteria |
| 106 | No generic entry is possible for the object type |
| 107 | Enter a language |
| 108 | The target language must not be the same as the source language |
| 109 | Enter the exact text to be replaced |
| 110 | Enter the new text |
| 111 | Enter a target context |
| 112 | Pass both the source and target object name generically or exactly |
| 113 | Maximum text length is 255 |
| 114 | Text was deleted |
| 115 | Concept does not exist |
| 116 | Text does not exist |
| 117 | Object type &1 does not exist |
| 118 | Internal error: Inconsistent parameters |
| 119 | The text belongs to object type &1 |
| 120 | The text belongs to package &1 |
| 121 | The text has the type &1 |
| 122 | A TADIR entry is created for the texts in package &1 |
| 123 | There is no TADIR entry for texts in package &1 in original system &2 |
| 124 | Error when checking TADIR entry (&1, RC = &2) |
| 125 | The package in the alias name does not correspond to current package &1 |
| 126 | Alias name abbreviated |
| 127 | The alias name contains the character '&1', which is not permitted |
| 128 | The alias name can only contain the character '&1' |
| 129 | The alias name &1 already exists |
| 130 | Error creating the TADIR entry for package &1 |
| 132 | There are multiple concepts for the alias name &1 |
| 133 | Object type &1 is not valid in BTFR (for &2) |
| 134 | The text length will be set to &1 |
| 135 | Fuzzy search is not available (RC = &1) -> Continue with search in DB |
| 136 | The text belongs to the local packet &1 |
| 137 | The text &1 characters long, but only &2 is allowed |
| 138 | The texts from packet &1 cannot be changed |
| 140 | Not all texts exist in language &1 |
| 141 | Texts are also used in other objects |
| 142 | The concept is already used |
| 144 | Enter a package name |
| 148 | Enter a text |
| 150 | Choose a text |
| 160 | Number of '&1' uneven |
| 161 | Parameters must start with a letter |
| 162 | Parameters: Only letters, numbers, and underscores are permitted |
| 163 | The number of opening and closing tags is different |
| 164 | There is no closing tag for an opening tag |
| 165 | Parameter &1 is not allowed |
| 166 | There is no opening tag for a closing tag |
| 170 | Could not update at least one text |
| 171 | The concept &1 could not be updated |
| 172 | At least one text could not be deleted |
| 173 | Not all concepts could be deleted |
| 174 | Concept &1 could not be added because it already exists |
| 176 | Context has length &1; the original text however has length &2 |
| 177 | Text has length &1; though only &2 is allowed |
| 180 | The alias name has changed; change the calling positions too |
| 182 | The text will be displayed in secondary language &1 |
| 183 | The text will be displayed in the original language &1 |
| 185 | The namespace &1 is invalid |
| 186 | Country/region &1 does not exist |
| 190 | No concatenated concept exists |
| 200 | No concept was passed for the context resolution |
| 201 | No language was passed for the context resolution |
| 202 | Concept was assigned to package &1 |
| 203 | Enter a concept |
| 204 | Source package is the same as the target package |
| 300 | **** No. 300 - ??? Messages for registration |
| 301 | Attributes for &1, &2 already exist |
| 302 | Attributes for &1, &2 do not exist |
| 303 | Change program ID to &1 |
| 304 | Only program IDs LIMU, R3TR are possible |
| 305 | Attributes saved |
| 306 | Object vector & does not exist |
| 400 | An exception was raised in method/function module &1 (SY-SUBRC = &2) |
| 401 | &1 package(s) and &2 component(s) &3 created |
| 500 | Text created in language &1 |
| 501 | Text created in system &1 |
| 502 | The original system of package &1 is &2 |
| 600 | The fuzzy search is not active |
| 601 | Error while creating the index category |
| 602 | The index category is not active |
| 603 | No concepts were passed for indexing |
| 604 | No texts have been found for the indexing |
| 605 | This language is not available in the index category |
| 606 | The index could not be changed |
| 607 | Error occurred setting up the RFC connection to the retrieval system |
| 608 | Error occurred while optimizing the index for the fuzzy search |
| 609 | Only texts from one language can be passed |
| 610 | The fuzzy search is already active |
| 611 | Error while deleting the index category |
| 612 | Error while deleting the search server relation |
| 613 | Error while deleting the RFC destination |
| 614 | Error while creating the search server relation |
| 615 | Error while creating the RFC destination |