LTR2_ES -
The following messages are stored in message class LTR2_ES: .
It is part of development package LTR2_ES_BASIS in software component CA-LT. This development package consists of objects that can be grouped under "Basis components of LTR2_ES".
It is part of development package LTR2_ES_BASIS in software component CA-LT. This development package consists of objects that can be grouped under "Basis components of LTR2_ES".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Getting source embedded specification failed |
| 002 | Creating an embedded specification copy failed |
| 003 | Creating a new embedded specification failed |
| 004 | Setting the description failed |
| 005 | Setting the object context failed |
| 006 | New embedded specification &1 saved |
| 007 | New embedded specification discarded due to simulation |
| 008 | Business object &1 (&2) added |
| 009 | Embedded specification copied from &1 to &2 |
| 010 | New embedded specification with GUID &1 created |
| 011 | Method &1 not allowed for snapshot work set |
| 012 | Activating data set &1 failed: &2 |
| 013 | No authorization to create an embedded specification |
| 014 | Data set &1 activated |
| 015 | Accessing ES failed: &1 |
| 016 | Storing PE data failed: &1 |
| 017 | Embedded specification will be created in namespace "&1" |
| 018 | New embedded specification named as &1 |
| 019 | Source embedded specification &1 |
| 020 | Getting the object analysis header for sender failed |
| 021 | Getting the object analysis header for receiver failed |
| 022 | Getting the object analysis data for sender failed |
| 023 | Getting the object analysis data for receiver failed |
| 024 | Getting the delta analysis header for sender failed |
| 025 | Getting the delta analysis header for receiver failed |
| 026 | Delta analysis run does not fit to embedded specification |
| 027 | Object analysis run does not fit to embedded specification |
| 028 | Getting the delta analysis data for sender failed |
| 029 | Getting the delta analysis data for receiver failed |
| 030 | Getting the table analysis header for sender failed |
| 031 | Getting the table analysis header for receiver failed |
| 032 | Getting the table analysis data for sender failed |
| 033 | Getting the table analysis data for receiver failed |
| 034 | Getting the table analysis data for the execution system failed |
| 035 | Getting the table analysis header for sender/execution system failed |
| 040 | No source work set passed |
| 041 | Getting the source embedded specification &1 failed |
| 042 | Getting the embedded specification for analysis run GUID &1 failed |
| 043 | Continue to delete embedded specification &1? |
| 044 | Embedded specification &1 deleted |
| 045 | Loading embedded specification &1 failed |
| 050 | Table &1 removed from &2 |
| 051 | Table &1 with data, but remains inactive for data model &2, bus.obj. &3 |
| 052 | Activated tables |
| 053 | De-activated tables |
| 054 | Table contents |
| 055 | Table &1 active: &2 &3 |
| 056 | Table &1 has been deactivated for data model &2, business object &3 |
| 057 | Table &1 contains no data, but is active for data model &2, bus.obj. &3 |
| 058 | Table &1 is modeled in Business Object Editor. |
| 059 | Table &1 activated for data model &2, bus. obj. &3. The table is empty. |
| 060 | Table &1 has no relevant data, but active for data model &2, bus.obj. &3 |
| 070 | Object &1 does not exist but is contained in ES at position &2 |
| 075 | Getting data set for transformation rules failed |
| 076 | Getting transformation rules of posting engine failed: &1 |
| 077 | Getting transformation rule &1 failed |
| 078 | Getting transformation rules of repository &1 failed: &2 |
| 080 | Setting application component failed: &1 |
| 081 | Setting retention days failed: &1 |
| 082 | Setting OBT scenario GUID failed: &1 |
| 090 | System &1 set temporarily as remote connection for rule &2 |
| 091 | Setting system &1 as remote destination for rule &2 failed |
| 092 | Generation failed for transformation rule &1: &3 &4 |
| 093 | Transformation rule &1 |
| 094 | Runtime generated for transformation rule &1 |
| 095 | Generation: &1 |
| 096 | Generation on execution system failed for transformation rule &1 |
| 097 | Runtime generated on execution system for transformation rule &1 |
| 098 | No transformation rules used in embedded specification |
| 099 | Add tables to the Work Set failed with message &1 |
| 100 | Embedded specification &1 not found |
| 101 | Error while reading items of ES &1 &2 |
| 102 | Invalid data model &1 in ES &2 |
| 103 | Data model &1 not found |
| 104 | Error while reading tables of data model &1 |
| 105 | No interface object for table &1 found |
| 106 | Error while reading interface object parameters of table &1 |
| 107 | No tables assigned to data model &1 |
| 108 | &1 &2 &3 &4 |
| 109 | Data set for rule assignment created |
| 110 | No rule assignments available for ES &1 |
| 111 | Failed assigning rule &3 to table field &1-&2 (&4) |
| 112 | Embedded specification &1 not locked for editing |
| 113 | Transformation rule &1 (&2) does not exist |
| 114 | Rule assignment not simulated yet |
| 115 | Simulation of rule assignment set has errors. Assignment not started. |
| 116 | More than one rule defined for domain &1 (component &2) |
| 117 | More than one rule defined for data element &1 (component &2) |
| 118 | More than one rule defined for table &1 fieldname &2 (component &3) |
| 119 | No fields with domain &2 found for parameter mapping (&4) in table &1 |
| 120 | No fields with data element &2 found for param mapping (&4) in table &1 |
| 121 | &3 (&4) not unique: more fields with domain &2 found for param &1 |
| 122 | &3 (&4) not unique: more fields with data element &2 found for param &1 |
| 123 | Not supported value type &1 in domain rules |
| 124 | Not supported value type &1 in data element rules |
| 125 | Not supported value type &1 in table rules |
| 126 | More than one rule defined for domain &1 (&2) |
| 127 | More than one rule defined for data element &1 (&2) |
| 128 | More than one rule defined for &1-&2 (&3) |
| 129 | Rule &3 was manually added to table field &1-&2. Assignment of &4 skipped |
| 130 | Parameter &1 for domain &2 is not unique. |
| 131 | Parameter &1 for data element &2 is not unique. |
| 132 | Parameter &1 for table field &2-&3 is not unique. |
| 133 | Parameter &1 is not a valid parameter of transformation rule &2 (&3) |
| 134 | Transformation rule &1 is not released |
| 135 | For domain &1 (&2) no transformation rule specified |
| 136 | For data element &1 (&2) no transformation rule specified |
| 137 | For &1-&2 (&3) no transformation rule specified |
| 138 | Error while reading transformation rule &1 |
| 139 | No transformation rule assigned for domain &1 (&2) |
| 140 | No transformation rule assigned for data element &1 (&2) |
| 141 | No transformation rule assigned for &1-&2 (&3) |
| 142 | Rule &3 is assigned to table field &1-&2 (&4) |
| 143 | Parameter &1 assigned to source table field &2-&3 |
| 144 | Parameter &1 assigned to fixed value &2 |
| 145 | Source field &1-&2 for mapping &3 not found (position:&4) |
| 146 | &1 (&4) for &2-&3: no execution system defined |
| 147 | &1 (&4) for &2-&3: no receiver system defined |
| 148 | &1 (&4) for &2-&3: no sender system defined |
| 149 | &1 (&4) for &2-&3: no ES defined |
| 150 | &1 (&4) for &2-&3: no package defined |
| 151 | No analysis run found for ES &1 |
| 152 | No execution system defined |
| 153 | No receiver system defined |
| 154 | No sender system defined |
| 155 | Invalid Embedded Specification GUID |
| 156 | No package defined for ES &1 |
| 157 | &2 (&3) to rule &1: there are no parameters defined |
| 158 | &2 (&3) to rule &1: number of parameters do not match |
| 159 | Mapping type of transformation rule &3 not found for &1-&2 |
| 160 | Invalid rule assignment type &1 for field &2-&3 |
| 161 | Getting the BOD related data for the analysis tables failed |
| 162 | No supported value type &2 form parameter &1 |
| 163 | Source table (&2) for parameter &1 is missing (&3) |
| 164 | Table &1 is modeled in BOD and can not be moved to the proposed DMOD. |
| 165 | Table &1 not assigned to data model &2 |
| 166 | Field for parameter &1 is missing (&3) |
| 167 | More than one rule is active for domain &1 (component &2) |
| 168 | More than one rule is active for data element &1 (component &2) |
| 169 | More than one rule is active for table field &1-&2 (component &3) |
| 170 | Domain rule is available but will be overridden by &1 |
| 171 | Data element rule is available but will be overridden by &1 |
| 172 | Rule &1 assigned by &2 in data model/BO &3, WSPOS=&4 |
| 173 | Source field &2 (for mapping &3-&4) exists more than once in table &1 |
| 174 | For parameter &3 with value type &1 a value must be given (&2) |
| 175 | For &1 both, source table name and field name, must be given (&2) |
| 176 | For &1, parameters of type &2 may result in errors (&3) |
| 177 | &1 (&4) for &2-&3: no number conversion engine defined |
| 178 | No number conversion defined for ES (&1) |
| 179 | Invalid package &1 |
| 180 | The ES is currently locked by user &1. Try again |
| 181 | Rule for domain &1 will be skipped => rule for data element &3 (&2) |
| 182 | Rule for domain &1 will be skipped => rule for table field (&2) |
| 183 | Rule for data element &1 will be skipped => rule for table field (&2) |
| 184 | Failed removing rule &3 to table field &1-&2 (&4) |
| 185 | Invalid count (&2) of exporting parameters in rule &1. |
| 186 | For value type FIELDNAME the field name is missing (table &1) |
| 187 | For parameter &1 the table name is missing |
| 188 | For parameter &1 the field name is missing (table &2) |
| 189 | For parameter &1 the domain for field &3 is missing (table &2) |
| 190 | For parameter &1 the data element for field &3 is missing (table &2) |
| 191 | Assigned table field &1-&2 for parameter &3 does not exist in sender (&4) |
| 192 | No valid line selected. Data models cannot be selected for removal. |
| 193 | The transformation rule &1 is not part of the repositories of the ES. |
| 194 | Business Object &1 (GUID &2) not found. |
| 195 | Invalid assignment for exporting parameters in rule &1 |
| 196 | &1 |
| 197 | Transformation rule &1 has variant type "&2", which is not allowed |
| 198 | Fallback rule is not defined as parameter of the embedded specification |
| 199 | Failed to get fallback rule &1 |
| 200 | Loading data models |
| 201 | Data model &1 in main business object &2 |
| 202 | Table &1 |
| 203 | Check rule assignment sets |
| 204 | Rule assignment for domains |
| 205 | Rule assignment for data elements |
| 206 | Rule assignment for table fields |
| 207 | Domain &1 |
| 208 | Data element &1 |
| 209 | Table field &1-&2 |
| 210 | Parameters of transformation rule &1 (&2) |
| 211 | Starting simulation of assignment |
| 212 | Table &1 |
| 213 | Field &2 |
| 214 | Starting assignment |
| 215 | Rule assignment data has been changed, assignment run required |
| 216 | Rule assignment |
| 217 | Data model &1 does not exist |
| 218 | Table &2 not existing in data model &1 |
| 219 | Interface object for table &2 in data model &1 does not exisit |
| 220 | Field &3 does not exist in table &2 for data model &1 |
| 221 | Assignment of rule &1 to &2-&3 not longer valid. Assignment deleted. |
| 222 | Old assignments |
| 223 | Table &1 is a condition table. (De)Activated it in the conditions tab! |
| 224 | Error: &1 |
| 225 | Table &1 is a condition table. Change proposal in the conditions tab. |
| 226 | Fallback rule &1 is used instead |
| 229 | Table &1 is not relevant for this sub-business object |
| 230 | Enter an ES name |
| 231 | Enter a RFC destination pointing to sender/exec. system |
| 232 | Enter a RFC destination from sender/exec. system to control system |
| 233 | The entered ES name is not unique |
| 234 | Enter a description text |
| 235 | Object with identifier &1 is not a valid sub-business object |
| 236 | Data model &1 in sub-business object &2 |
| 237 | Check assignment of rule &1 to &2-&3 |
| 238 | Fallback rule &1 is used |
| 239 | Check active rule assignments |
| 240 | For domain &1 a rule assignment is defined |
| 241 | For data element &1 a rule assignment is defined |
| 242 | For table field &1-&2 a rule assignment is defined |
| 243 | Not used in embedded specification |
| 244 | Assignment of domain not unique. At least two rules are assigned. |
| 245 | Assignment of data element not unique. At least two rules are assigned. |
| 246 | Assignment of table field not unique. At least two rules are assigned. |
| 247 | Line ID &1 |
| 248 | Parameter &1 of rule &2 for domain &3 (&4) is not supplied |
| 249 | Parameter &1 of rule &2 for data element &3 (&4) is not supplied |
| 250 | Parameter &1 of rule &2 for table field &3 (&4) is not supplied |
| 251 | Error loading the data models. Simulation not possible. Check data models |
| 252 | Error in rule assignments. Simulation not possible. Check assignments |
| 253 | Transformation rule &1 is excluded (&2) |
| 254 | An error occured while registering repository &1 (type &2) |
| 255 | Register repositories |
| 256 | Failed to register repositories |
| 257 | An error occured while deleting repository &1 (type &2) |
| 261 | No client for sender system exists within table T000 |
| 262 | No client for receiver system exists within table T000 |
| 263 | No client for execution system exists within table T000 |
| 264 | No logical system for receiver system maintained |
| 265 | No logical system for sender system maintained |
| 266 | No logical system for execution system maintained |
| 267 | No RFC-destination for sender system exists within table T000 |
| 268 | No RFC-destination for execution system exists within table T000 |
| 269 | No RFC-destination for receiver system exists within table T000 |
| 270 | Assignment for &1-&2 already exists (&3) |
| 271 | Assignment for &1-&2 was added |
| 272 | Table &1 already deactivated for data model &2, business object &3 |
| 280 | General ES changes |
| 281 | No general ES changes |
| 288 | Enter a value between 1 and 99998 for the ES retention days |
| 289 | There are &1 retention days left for this embedded specification |
| 290 | Value '&1' is invalid for the retention popup reminder |
| 291 | Value '&1' is invalid for the retention warning reminder |
| 292 | Inconsistency of RFC-destinations between ES and the analysis detected |
| 293 | ES parameter MWB_WL_SCENARIO for white-listing in cloud not set |
| 294 | Business object '&1' exists already and will not be added to ES |
| 295 | Data model '&1' deactivated because of wrong product assignment |
| 296 | Data model '&1' added to Embedded specification |
| 297 | Data model '&1' (position: &2) deactivated |