R1 - Business Partner Meldungen aus S_BUPA_GENERAL
The following messages are stored in message class R1: Business Partner Meldungen aus S_BUPA_GENERAL.
It is part of development package S_BUPA_GENERAL in software component BC-SRV-BP. This development package consists of objects that can be grouped under "SAP Business Partner: Basic Components".
It is part of development package S_BUPA_GENERAL in software component BC-SRV-BP. This development package consists of objects that can be grouped under "SAP Business Partner: Basic Components".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | * Organization: From 001: Reserved |
| 002 | * 020: General |
| 003 | * 080: Number assignment and lock management |
| 004 | * 100: BDT |
| 005 | * 200: CBP data |
| 006 | * 300: BDT (Part 2) |
| 007 | * 400: Validity/Time Dependency |
| 008 | * 440: Address Data (Part 2) |
| 009 | * 450: CBP Data (Part 3) |
| 010 | * 500: Table Maintenance (Customizing and Control) |
| 011 | * 550: CBP Data (Part 2) |
| 012 | * 600: Address data (BUA0, BUA1) |
| 013 | * 700: CBP Relationships (Control) |
| 014 | * 800: CBP Relationships (Data) |
| 015 | * 850: Central messages |
| 016 | * 380: BDT in subscreen |
| 020 | * 020: General |
| 021 | Incorrect parameters |
| 022 | No entries found |
| 023 | Table/structure &1 does not exist |
| 024 | First data screen reached |
| 025 | Value for the 'save with update' indicator is not valid |
| 026 | Activity & does not exist |
| 027 | List is incomplete because of missing authorization |
| 028 | Choose a valid line |
| 029 | Missing authorization for & of entry |
| 030 | Value &1 is invalid for the indicator 'save mode' |
| 031 | Application object &1 does not exist |
| 032 | Value &1 is Invalid for indicator 'Display initial screen' |
| 033 | Select an entry before executing the function |
| 034 | Data has already been saved |
| 035 | No errors found |
| 036 | Entry is Invalid |
| 037 | Field &2 does not exist in table &1 |
| 038 | Action was canceled |
| 039 | Text for application object &2 in language &1 not maintained |
| 040 | Obsolete entries were deleted |
| 041 | New entries created |
| 042 | Obsolete entries have been deleted and new entries created. |
| 043 | & were created |
| 044 | & were changed |
| 045 | & were deleted |
| 046 | & were saved |
| 047 | & applied |
| 048 | & was applied |
| 049 | The stated object type &1 does not correspond to valid object type &2 |
| 050 | Authorization object &1 does not exist |
| 051 | Field &2 in authorization object &1 does not exist |
| 052 | Key fields for table &1 of business partner &2 are incomplete |
| 053 | Address &1 not valid for selection date &2 |
| 054 | There is no valid usage for address type &2 address number &3 for &1 |
| 055 | There is no valid usage for partner &2 address type &3 for &1 |
| 056 | There is no valid usage for partner &2 for &1 |
| 057 | For partner &2 there is no valid usage for &1 |
| 058 | Business partner &1: category &2 ID number &3 does not exist |
| 059 | Category &1 ID number &2 not valid for selection date &3 |
| 060 | No ID number is valid for partner &2 for &1 |
| 061 | No roles exist for business partner &1 |
| 062 | Role &1 differentiation value &2 not valid for selection date &3 |
| 063 | No partners found for role &1 |
| 064 | No partner is valid in role &2 for &1 |
| 065 | No bank details are valid for &2 for partner &1 |
| 066 | No usage is valid for partner &2 transaction &3 for &1 |
| 067 | A change is not possible for bank details &1 for partner &2 |
| 068 | Update of Variable Node was Not Carried Out |
| 069 | Form of address &1 is not intended for groups |
| 070 | TEST: Contract & with partner 1 & and partner 2 & was saved |
| 071 | Authorization group already exists in standard BP authorization group |
| 072 | Authorization group is already being used by business partners |
| 073 | Authorization group exists in authorization group for SAP HANA VDMs |
| 074 | Authorization group was updated successfully (see long text) |
| 076 | Role category group &1 is not assigned to a role category. |
| 077 | Relationship cat. &1 must not have a role category and role cat. group. |
| 078 | Business partner &1 has not been maintained in role category group &2 . |
| 080 | * 090: ...Number assignment |
| 081 | The number specified is in the critical area of number range &1 |
| 082 | The specified number is the last in number range &1 |
| 083 | No more numbers are free in number range &1 |
| 084 | Business partner &1 is currently being processed by &2 |
| 085 | & & is currently being processed by & |
| 086 | Business partner &1 is currently locked by you |
| 090 | Card cannot be created. Digital payment is activated for card type &1. |
| 091 | Grouping & has external number assignment, enter a number |
| 092 | Grouping & has internal number assignment; do not enter a number |
| 093 | Error in number assignment for planned change documents |
| 094 | Error when inserting table TB200 (internal address number management) |
| 095 | Error during insert/delete in table TB201 (planned role changes) |
| 096 | Error during update of table TB200 (internal address number management) |
| 097 | Archiving object &1 is not assigned to any application object |
| 098 | Numerical entry not allowed |
| 099 | Number not in interval &1 - &2 |
| 100 | * 100: BDT |
| 101 | Data on current screen is correct |
| 102 | Standard screen sequence variant &1 may not be deleted |
| 103 | Application object &1: Table with DI structure &2 does not exist |
| 104 | Application object &1: Screen sequence variant &2 does not exist |
| 105 | Activity category &1 does not exist |
| 106 | Application object &1: Screen &2 does not exist |
| 107 | Application object &1: BP role grouping &2 does not exist |
| 108 | Application object &2: No text for BP role grouping &3 in language &1 |
| 109 | Application object &1: No assignment exists for BP role grouping &2 |
| 110 | Application object &1 was not initialized |
| 111 | Application object &1: Section &2 does not exist |
| 112 | Application object &1: View &2 does not exist |
| 113 | Application object &1: Application &2 does not exist |
| 114 | ApplObject &1: Field grouping for external application &2 does not exist |
| 115 | Application & for function module & does not exist |
| 116 | Application object &2: No text for screen &3 in language &1 |
| 117 | Application object &1: External application &2 does not exist |
| 118 | Application object &1: No text in language &3 for external application &2 |
| 119 | OK code & is not defined |
| 120 | Transaction code &1 assigned to multiple application transactions |
| 121 | GUI function & does not exist |
| 122 | Application object &1: No views exist |
| 123 | No field group exists for the selection |
| 124 | Transaction & is not defined as a control transaction |
| 125 | Transaction & is not defined as an application transaction |
| 126 | Transaction code &1 assigned more than once as a configuration activity |
| 127 | Application object &1: No BP role grouping exists |
| 128 | Application object &1: BP roles cannot be passed |
| 129 | Application object &1: BP role groupings cannot be passed |
| 130 | Application object &1: Views cannot be passed |
| 131 | Application object &1: Applications cannot be passed |
| 132 | BP role groupings cannot be used without BP roles |
| 133 | Application object &1: No standard screen sequence variant exists |
| 134 | Application object &1: No further view checks found |
| 135 | Application object &2: No text for BP role &3 in language &1 |
| 136 | Object &1: Text in language &2 is missing |
| 137 | 'Valid-From' date may not be greater than 'Valid-To' date |
| 138 | Date interval is entirely in the past |
| 139 | Date interval is entirely in the future |
| 140 | Specify at least one valid BP role |
| 141 | Select at least one BP role |
| 142 | Select at least one BP role or BP role grouping |
| 143 | Select one BP role |
| 144 | Select one BP role or BP role grouping |
| 145 | BP role groupings must not be active for single selection |
| 146 | The passed GUI function &1 does not exist |
| 147 | Application object &1 has already been called in this LUW |
| 148 | Application object &1: No BP role exists |
| 149 | Application object &1: Table &2 does not exist |
| 150 | Application object &1: Read function module missing for table &2 |
| 151 | Changing screen is not possible |
| 152 | No authorization to create partner with authorization type &1 |
| 153 | No authorization to change partner with authorization type &1 |
| 154 | No authorization to display partner with authorization type &1 |
| 155 | Application object &1: No assignment exists for DB field &2-&3 |
| 156 | Input or non-input fields must be selected |
| 157 | Differentiation type & does not exist |
| 158 | Texts for differentiation type &1 do not exist in language &2 |
| 159 | Text for activity type &1 does not exist in language &2 |
| 160 | You must select the Involved in maintenance or Call only indicator |
| 161 | &1 &2 assignment to generic DiffType element &3 does not exist |
| 162 | Differentiation type element & does not exist |
| 163 | Texts for differentiation type element &1 do not exist in language &2 |
| 164 | Relationship category & does not exist |
| 165 | Texts for relationship category &1 do not exist in language &2 |
| 166 | Role definition category & does not exist |
| 167 | Texts for role definition category &1 do not exist in language &2 |
| 168 | Not all planned changes for the day activated in table &1 |
| 169 | Application object &1: Data sets cannot be passed |
| 170 | General maintenance may not be assigned |
| 171 | You cannot assign general maintenance to a BP role grouping |
| 172 | Applic. object &1: No assignment BP role->applic. exists for BP role &2 |
| 173 | Application object &1: No application exists |
| 174 | Application object &2: No text for application &3 in language &1 |
| 175 | Application object &1: No BP role with screen sequence variant &2 exists |
| 176 | Application object &1: No assignment for dynpro field &2-&3 |
| 177 | Application object &1: No dynpro field > DB field assignment exists |
| 178 | Control object &1: No assignment exists for application object &2 |
| 179 | Application object &1: No screen sequence variants exist |
| 180 | Application object &2: Text for screen sequence &3 not in language &1 |
| 181 | Application object &1: No screens exist |
| 182 | Application object &1: No screens with screen container &2 exist |
| 183 | Application object &1: No sections exist |
| 184 | Application object &2: Text for section &3 does not exist in language &1 |
| 185 | Application object &2: Text for view &3 does not exist in language &1 |
| 186 | Application object &1: No section -> view assignments exist |
| 187 | Application object &1: No views exist for section &2 |
| 188 | Application object &1: No sections with view &2 exist |
| 189 | Application object &1: No screen -> section assignments exist |
| 190 | Application object &1: No screens exist for section &2 |
| 191 | Application object &1: No sections exist for screen &2 |
| 192 | Application object &1: No role cat->view assignment for role cat &2 |
| 193 | Application object &1: No role cat->view assignment exists for view &2 |
| 194 | Application object &1: No role category &2 -> application &3 assignment |
| 195 | Application object &1: No screen sequence exists with screen &2 |
| 196 | Application object &1: No screens exist for screen sequence variant &2 |
| 197 | Application object &1: No field grouping criterion exists |
| 198 | Application object &1: No field groups exist |
| 199 | Application object &1: Field group &2 does not exist |
| 200 | * 200: CBP data |
| 201 | Business partner &1 does not exist |
| 202 | No changes were made |
| 203 | Select at least one screen |
| 204 | Business partner &1 already exists in role &2 |
| 205 | Business partner &1 does not exist in role &2 |
| 206 | BP role &1 does not exist |
| 207 | Academic title & does not exist |
| 208 | Date of death may not be earlier than date of birth |
| 209 | No business partner found |
| 210 | Form of address & does not exist |
| 211 | Make at least one register entry |
| 212 | Grouping & does not exist |
| 213 | Enter a business partner number |
| 214 | Business partner &1 created in role &2 |
| 215 | Business partner & changed |
| 216 | Business partner not yet created: enter grouping |
| 217 | The partner data was applied |
| 218 | Bank &2 for country/region &1 does not exist. |
| 219 | Enter at least one set of bank details |
| 220 | Select bank details |
| 221 | Bank details do not exist |
| 222 | First enter bank country/region and bank key (or bank account) |
| 223 | First enter an Internet address. |
| 224 | Enter the bank details ID |
| 225 | Bank details with ID &1 already exists |
| 226 | Country/region &1 does not exist |
| 227 | Bank account number &2 is invalid |
| 228 | Bank details &1 &2 &3 in the validity period are not unique |
| 229 | Business partner &1 does not exist in role &2 (differentiation &3) |
| 230 | Form of address &1 not designated for persons |
| 231 | Form of address &1 not designated for organizations |
| 232 | Enter an account holder |
| 233 | First execute program &1 |
| 234 | All changes as from &1 will be displayed |
| 235 | Select at least one data area |
| 236 | Specify a valid sorting method |
| 237 | Specify an entry in commercial register |
| 238 | There are no bank details for business partner &1 |
| 239 | Select payment card details |
| 240 | Specify interval size or number of intervals |
| 241 | Business partner category cannot be changed! |
| 242 | Bank details ID &2 does not exist for business partner &1 |
| 243 | Sex not specified |
| 244 | Business partner &1 created in &2 roles |
| 245 | Business partner & is not a person |
| 246 | Business partner & is not an organization |
| 247 | Business partner & is not a group |
| 248 | The local memory does not contain any data for business partner & |
| 249 | Business partner number &1 is not permitted |
| 250 | Name prefix & does not exist |
| 251 | Name affix & does not exist |
| 252 | Legal form &1 does not exist |
| 253 | Industry &1 does not exist |
| 254 | Sex unclear ("male", "female" or "unknown") |
| 255 | Partner groups type &1 does not exist |
| 256 | Please enter a bank country/region. |
| 257 | Legitimation type &1 does not exist |
| 258 | Country/region &1 entered in the nationality field does not exist |
| 259 | Marital status &1 does not exist |
| 260 | Occupation/group &1 does not exist |
| 261 | The text in language &2 does not exist for form of address &1 |
| 262 | No valid academic titles exist |
| 263 | No valid name suffixes exist |
| 264 | Bank details with ID &1 do not exist |
| 265 | Bank details with reference number &1 already exists |
| 266 | Bank details ID or reference number must be specified |
| 267 | Bank details with reference number &1 does not exist |
| 268 | Business partner &1 not created for &2 |
| 269 | Business partner category &1 does not exist; use 1, 2 or 3 |
| 270 | There are no unsaved business partners |
| 271 | There is no unsaved business partner selected |
| 272 | No authorization to create partner with authorization group &1 |
| 273 | No authorization to change partner with authorization group &1 |
| 274 | No authorization to display partner with authorization group &1 |
| 275 | No authorization to create partner in role &1 |
| 276 | No authorization to change partner in role &1 |
| 277 | No authorization to display partner in role &1 |
| 278 | No relevant business partner category for all selected BP roles |
| 279 | Business partner cat. &1 not permitted for BP role &2 |
| 280 | Date cannot be in the future |
| 281 | Date cannot be in the past |
| 282 | Bank details with external number &2 for partner &1 do not exist |
| 283 | Business partner with external number &1 does not exist |
| 284 | Business partner type &1 does not exist |
| 285 | Business partner type was changed, field selection will be adjusted |
| 286 | Business partner &1 already exists |
| 287 | Business partner with external number &1 already exists |
| 288 | Field grouping for business partner category &1 does not exist |
| 289 | Business partner &1 already exists for &2 |
| 290 | Application object &1: Field grouping for BP role &2 does not exist |
| 291 | Changes for business partner &1 have been flagged |
| 292 | Application object &1: Field grouping for activity &2 does not exist |
| 293 | Application object &1: There is no screen configuration for BP role &2 |
| 294 | No text for business partner type &1 in language &2 |
| 295 | No text for legal form &1 in language &2 |
| 296 | No text for industry &1 in language &2 |
| 297 | No text for group type &1 in language &2 |
| 298 | No text for marital status &1 in language &2 |
| 299 | No text for occupation/group &1 in language &2 |
| 300 | * 300: BDT (Part 2) |
| 301 | Error linking field attributes. |
| 302 | Application object &1: Field &2 is assigned to multiple field groups |
| 303 | ApplObj.&1: Trans. for RolCat.&2, RolCatGp &3, activ.&4 does not exist |
| 304 | Required field &1 has no entry |
| 305 | This field already assigned to field group &1 |
| 306 | Parameter mode &1 is not provided for |
| 307 | Parameter I_DIFF_TYPE missing for parameter mode &1 |
| 308 | System unable to determine any relevant views |
| 309 | Application object &2: No text exists for field group &3 in language &1 |
| 310 | Application object &1: No field group with field &2-&3 exists |
| 311 | Application object &1: No GUI functions exist |
| 312 | Application object &1: No assignment to differentiation types exists |
| 313 | Application object &1: No tables exist |
| 314 | Application object &1: No text for GUI function &2 in language &3 exists |
| 315 | Application object &1: No matchcode for field &2-&3 exists |
| 316 | Application object &1: No fields assigned to field group &2 |
| 317 | Application object &1: No field group->field assignments exist |
| 318 | Application object &1: Field group &2 is not assigned to a view |
| 319 | Application object &1: No view->field group assignments exist |
| 320 | Application object &1: No field groups assigned to view &2 |
| 321 | Application object &1: No BP role grouping->BP role assignments exist |
| 322 | No screens exist |
| 323 | Creation of business partner &1 in role &2 for &3 flagged |
| 324 | Creation of business partner &1 in &2 roles for &3 flagged |
| 325 | You cannot plan changes to bank master data |
| 326 | Business partner &1 already exists in role &2 |
| 327 | State the ID of the payment card details |
| 328 | Payment card details with ID &1 does not exist |
| 329 | Application object &1: No screen sequences for screen seq. category &2 |
| 330 | Application object &1: No screen sequence categories exist |
| 331 | Card company and card number must be defined |
| 332 | Credit card &1 &2 does not exist |
| 333 | Changes to credit card details cannot be planned in advance |
| 334 | Select payment card details |
| 335 | No authorization to display card master data |
| 336 | No authorization to change card master data |
| 337 | Card &1 &2 does not exist; you have no authorization to create |
| 338 | Payment card &1 &2 does not exist |
| 339 | Card &1 &2 is blocked by another user |
| 340 | Select only one set of payment card details |
| 341 | ApplObject &1: No standard screen sequence exists for screen seq.cat.&2 |
| 342 | Appl.object &1: Screen sequence cat. &2 not assigned to screen seq. &3 |
| 343 | State at least one set of payment card details |
| 344 | You cannot delete all payment card details |
| 345 | Payment card ID &2 does not exist for business partner &1 |
| 346 | No payment card details for business partner &1 |
| 347 | No payment card details exist |
| 348 | Application object &1: Activity &2 does not exist |
| 349 | Application object &1: Text for activity &2 does not exist in language &3 |
| 350 | Application obj. &1: In screen sequence &2 a screen is missing in pos. &3 |
| 351 | Message handler not activated (initialized) |
| 352 | Invalid Message-Collect-Status (Field: COLL_STAT) |
| 353 | Invalid message type |
| 354 | State either an activity or an activity category |
| 355 | Application object &1: There are no texts for screens in language &2 |
| 356 | Application object &1: No texts for screens exist |
| 357 | Application object &1: There are no texts for sections in language &2 |
| 358 | Application object &1: There are no texts for sections |
| 359 | Application object &1: There are no texts for screen sequences in lang.&2 |
| 360 | Application object &1: There are no texts for screen sequences |
| 361 | View &2 appears more than once on screen &1 |
| 362 | Overflow during generation of screen sequence variants |
| 363 | Main screen sequence &3 does not exist |
| 364 | Item number &1 is in customer name range |
| 365 | Item number &1 is in SAP name range |
| 366 | Screen sequence variant & cannot be changed |
| 367 | Consistency error: & |
| 368 | Deletion of generated screen sequence was canceled with errors |
| 369 | Application object &1: No DI field -> DB field assignment exists |
| 370 | Application object &1: No assignment exists for DI field &2-&3 |
| 371 | Tree control Cannot be Initialized |
| 372 | No view variant has been created |
| 373 | Application object &1: No data sets exist |
| 374 | Application object &2: Text missing for data set &3 in language &1 |
| 375 | Application object &1: No views exist with data set &2 |
| 376 | Application object &1: No assignment RlCat->Set for RlCat &2 exists |
| 377 | Application object &1: Data set &2 does not exist |
| 378 | Application object &1: No assignment RlCat->Set for Set &2 exists |
| 379 | Application object &1: BOR object cannot be determined |
| 380 | BDT: Change OBJID from &1 to &2 not permitted for secondary instances |
| 381 | BDT: OBJID &1 is already being used in another primary instance |
| 382 | BDT: Entry of ID for external interface (FRGID) is missing |
| 383 | BDT: FRGID set to &1 even though external interface is not active |
| 384 | BDT: Screen stack is empty |
| 385 | Application object &1: No screens exist to be regenerated |
| 386 | There are no screens to be regenerated |
| 387 | Dynpro container number &1 for full screen is not permitted |
| 388 | BDT: General error in function module &1 |
| 389 | BDT: General error in subroutine &1 |
| 390 | BDT: Only views or only applications or only data sets can be passed |
| 391 | BDT: Tabstrips are not possible in display mode & |
| 392 | No relevant data screen exists; all fields are hidden |
| 393 | Field &1-&2 Not Ready for Input Due to Customizing Settings |
| 394 | Field &1-&2 Cannot be Scheduled |
| 395 | During Activation, You Must Enter the Field Group For Each Field Group |
| 396 | Function &1 is controlled by the field group; navigation not possible |
| 397 | Delete dynpro containers only if all screens are regenerated |
| 398 | Function Module &2 Already Assigned to Event &1 |
| 399 | Function Module &2 is Already Assigned to Event &1 |
| 400 | * Validity/Time-Dependency |
| 401 | Time constraint cat. & invalid |
| 402 | Activity & invalid |
| 403 | Incorrect validity interval |
| 404 | Index & does not refer to an existing validity interval |
| 405 | Deletion only possible within validity interval &1 - &2 |
| 406 | Error in minimum/maximum limits & & & & |
| 407 | Existing validity intervals are incorrect |
| 408 | Valid from &1 not correct (gap in predecessor/minimum) &2 &3 &4 |
| 409 | Valid from &1 is prior to minimum date &2 &3 &4 |
| 410 | Valid from &1 is after the minimum date &2 &3 &4 |
| 411 | Valid to &1 not correct (gap in successor/maximum) &2 &3 &4 |
| 412 | Valid to &1 is prior to the maximum date &2 &3 &4 |
| 413 | Valid to &1 is after the maximum date &2 &3 &4 |
| 414 | Deletion ineffective due to re-renewal & & & & |
| 415 | Deletion not allowed (only interval for time constraint type 1) & & & & |
| 416 | No change document objects are assigned to application object &1 |
| 417 | No tables have been assigned to application object &1 |
| 418 | No changes to date are planned for application object &1 |
| 419 | No role data exists for change document &1 (table TB201) |
| 420 | No change document objects have been assigned to the application tables |
| 421 | Change document objects have not been assigned to all application tables |
| 422 | It is not possible to create organizational units |
| 423 | Personnel number &1 has already been assigned |
| 424 | Business partner &1 does not exist in role &2 |
| 425 | Business partner &1 created |
| 426 | Creation of business partner &1 has been scheduled for &2 |
| 427 | Enter a specific selection set under the general selections |
| 428 | Enter at least one user role |
| 429 | You May Not Delete All User Roles |
| 430 | * BP: Evaluation generator |
| 431 | Table &1 does not contain entries |
| 432 | Table &1 does not exist as a runtime object; you must activate it |
| 433 | Field &1 does not exist in table &2 and was therefore not saved |
| 434 | &1: Unknown error |
| 435 | &1 &2 could not be activated |
| 436 | &1: &2 &3 could not be created |
| 437 | Function &1: &2 |
| 438 | Validity date does not match date of time stamp |
| 439 | BUSPCDACT no longer possible for object BUPA from Release 6.40 |
| 440 | * Address data (part 2) |
| 441 | Change type &1 for teletex number is not defined |
| 442 | Change type &1 for telex number is not defined |
| 443 | Change type &1 for RML mail address is not defined |
| 444 | Change type &1 for X.400 address is not defined |
| 445 | Change type &1 for RFC destination is not defined |
| 446 | Change type &1 for printer is not defined |
| 447 | Change type &1 for SSF address is not defined |
| 448 | Change type &1 for URI address is not defined |
| 449 | Change type &1 for pager number is not defined |
| 450 | * CBP data |
| 451 | External BP number &1 has already been assigned for business partner &2 |
| 452 | Partner &1 has not been created in all the relevant roles |
| 453 | Partner &1 has not been created in any of the relevant roles |
| 454 | Entry &1 of &2 |
| 455 | Address is still being used and may not be deleted |
| 456 | Address is still being used, but can be deleted / restricted |
| 457 | No ID Numbers Found for Partner &1 |
| 458 | No ID numbers found for partner &1, ID category &2, ID type &3 |
| 459 | ID Category &1 and/or ID Type &2 Do Not Exist |
| 460 | ID type &1 does not exist |
| 461 | ID number &2 does not exist for business partner &1 |
| 462 | ID type &2 and ID number &3 do not exist for business partner &1 |
| 463 | No industries found for business partner &1 |
| 464 | Industry &2 does not exist for business partner &1 |
| 465 | Industry &2 for industry key system &3 does not exist for BP &1 |
| 466 | No industries exist for industry key system &2 for business partner &1 |
| 467 | First edit the standard address with the error |
| 468 | Maintain changes to the address in the organizational unit |
| 469 | Select a Standard Industry System |
| 470 | An active Internet user &2 does not exist for business partner &1 |
| 471 | An IBAN is defined for the bank details and this IBAN cannot be deleted |
| 472 | No IBAN defined for these bank details |
| 473 | Invalid value &2 for field &3 for business partner &1 |
| 474 | Gender 'male' does not match form of address '&1' |
| 475 | Gender 'female' does not match form of address '&1' |
| 476 | The move or change date &1 occurs before the validity start &2 |
| 477 | Number &2&4 is already assigned to partner &3 for ID type &1 |
| 478 | Validity period not allowed: Address is move target address for &1 |
| 479 | Address still in use; change to validity not allowed |
| 480 | Address is standard address; restriction to validity not allowed |
| 481 | Enter an address for the validity date |
| 482 | Error in address &1 |
| 483 | Validity period incompatible with validity of address |
| 484 | Restricting the validity of a standard address is not allowed |
| 485 | The validity of the standard usage may not be restricted |
| 486 | Choose a target object for the move date |
| 487 | Enter a target object that differs from the source object |
| 488 | Move target address does not exist or does not belong to partner &1 |
| 489 | The move date &1 does not occur in the validity area of the target object |
| 490 | Address is address for move target and may therefore not be deleted |
| 491 | Assignment for field &1 in structure &2 is not possible. No data transfer |
| 492 | Field &1-&2 is Not Assigned to Role &3 |
| 493 | 'Standard usage' not planned for standard addresses |
| 494 | Indicator 'standard address' no longer allowed |
| 495 | Addresses and/or address usages are inconsistent |
| 496 | Address already created in selected period in usage &1 |
| 497 | Year '000' not plausible |
| 498 | Selected period already taken by other usages |
| 499 | No move or change dates exist |
| 500 | Enter move or change date |
| 501 | Do not specify any coordinates for the dynpro type "Normal" |
| 502 | Do no enter any coordinates for the dynpro type "Modal dialog box" |
| 503 | Status &1 is Not Permitted for Field Group &2 |
| 504 | Field group must not be greater than &! |
| 505 | Field group cannot be less than & |
| 506 | Invalid object ID |
| 507 | Parameter & is blank. |
| 508 | Select one entry only for simulation |
| 509 | Field does not exist on the assigned subscreen |
| 510 | Do Not Enter a Function Module for a Screen From BDT |
| 511 | Table &1 is not assigned to change document object &2 |
| 512 | Enter function module for imported screen |
| 513 | Upper line must not be longer than lower line |
| 514 | Left column cannot be greater than right column |
| 515 | Reference table field for differentiation type element & incorrect |
| 516 | Text for identification type &1 does not exist in language &2 |
| 517 | Section &1: Maximum number of views exceeded (upper limit is &2) |
| 518 | Screen &1 &2 &3: Maximum Number of Sections Exceeded (Upper Limit is &4) |
| 519 | Could not create dynpro container |
| 520 | Maximum number of dynpro containers reached |
| 521 | Mark at least one business partner category |
| 522 | Screen &1 &2 &3: Maximum Number of Lines Exceeded (Upper Limit is &4) |
| 523 | Input field &1 does not exist |
| 524 | Import error: Dynpro & does not exist |
| 525 | Generation error: Dynpro &, text: &, line &, word: & |
| 526 | Undirected rel. category: BP roles of both partners must be the same |
| 527 | BP role for business partner 2 must match the role definition category |
| 528 | DiffType for BP role BP1 must be the same as DiffType for RelCat |
| 529 | DiffType for BP role BP1 must be the same as DiffType for RoleDefCat |
| 530 | DiffType for BP role BP2 must be the same as DiffType for RelCat |
| 531 | DiffType for BP role BP2 must be the same as DiffType for RoleDefCat |
| 532 | BP role &1 cannot be used ('General Maintenance' indicator set) |
| 533 | Mark at least one business partner category for partner 1 |
| 534 | Mark at least one business partner category for partner 2 |
| 535 | BP cat. of both partners must be the same for undirected relship category |
| 536 | Hiding all business partner numbers is not possible |
| 537 | No grouping with internal number assignment is defined |
| 538 | Enter field for authorization object &1 |
| 539 | Higher-level BP role cannot be the same as the BP role itself |
| 540 | BP role &1 already has a higher-level BP role |
| 541 | BP role &1 is a higher-level BP role of &2 |
| 542 | Standard Industry Number System &1 Must Not be Deleted |
| 543 | No industry system exists |
| 544 | Industry system &1 does not exist |
| 545 | No identification categories exist |
| 546 | Identification category &1 is assigned to multiple identification types |
| 547 | Text for industry system &1 does not exist in language &2 |
| 548 | Identification Category &1 Does Not Exist |
| 549 | Identification Category &1 is Not Assigned to Any Identification Type |
| 550 | * 500: CBP Data (Part 2) |
| 551 | Text for legitimation type &1 in language &2 does not exist |
| 552 | Business partner type &2 not applied; change this on the data screen |
| 553 | &1 &2 is assigned to business partner &3 |
| 554 | Object ID & is not defined (TB210) |
| 555 | &1 &2 is not assigned to a business partner |
| 556 | Data origin type &1 does not exist |
| 557 | Text for data origin type &1 does not exist in language &2 |
| 558 | Legal entity &1 does not exist |
| 559 | Text for legal entity &1 does not exist in language &2 |
| 560 | Liquidation date must not be earlier than creation date |
| 561 | Enter a card type |
| 562 | Card type &1 does not exist |
| 563 | Card type &1 does not exist |
| 564 | Block &1 does not exist |
| 565 | Enter a card number |
| 566 | Card number &1 is not allowed for card type &2 |
| 567 | Checking rule &1 does not exist |
| 568 | Enter a card category |
| 569 | Credit card ID &1 already exists |
| 570 | Credit card &1 &2 already exists |
| 571 | Standard credit card details must be unambiguous |
| 572 | Valid-from date is after valid-to date |
| 573 | Valid-to date is in the past |
| 574 | Valid-to date is earlier than date of issue |
| 575 | Text for card company &1 does not exist in language &2 |
| 576 | Text for card category &1 does not exist in language &2 |
| 577 | Text for blocking category &1 does not exist in language &2 |
| 578 | User &1 does not exist |
| 579 | Date &1 invalid: Partner &2 is already maintained with date &3 |
| 580 | Enter an ID for this set of payment card details |
| 581 | Enter the business partner number or business partner GUID |
| 582 | Employees cannot be created in this system |
| 583 | User &1 already assigned to business partner &2 |
| 584 | Authorization Group Object &1 Does Not Exist |
| 585 | Text for Authorization Group Object &1 Does Not Exist in Language &2 |
| 586 | Object &1: Authorization group &2 does not exist |
| 587 | Auth. group obj.&1: Text for auth.group &2 does not exist in language &3 |
| 588 | Error when inserting business partner &1 |
| 589 | Error when updating business partner &1 |
| 590 | Entry &1 Not Permitted for Contacts |
| 591 | Bank Details &1 are Still being Used and Must Not be Deleted |
| 592 | Bank Details &1 are Still being Used, But Can be Deleted |
| 593 | Payment Card &1 is Still being Used and Must Not be Deleted |
| 594 | Payment Card &1 is Still being Used, But Can be Deleted |
| 595 | Enter at least one ID number |
| 596 | You Cannot Delete All ID Numbers |
| 597 | Enter at least one industry |
| 598 | You May Not Delete All Industries |
| 599 | Partner &1 not in memory for date &2, but there for alternative date &3 |
| 600 | * 600: Address data (BUA0, BUA1) |
| 601 | Telephone number for business partner &1 does not exist |
| 602 | Fax number with sequential number &1 does not exist |
| 603 | Internet address with sequential number &1 does not exist |
| 604 | Teletex number with sequential number &1 does not exist |
| 605 | Telex number with sequential number &1 does not exist |
| 606 | R/Mail address with sequential number &1 does not exist |
| 607 | X.400 address with sequential number &1 does not exist |
| 608 | RFC destination with sequential number &1 does not exist |
| 609 | Printer with sequential number &1 does not exist |
| 610 | Address with address number &2 does not exist for business partner &1 |
| 611 | Address with address ID &2 does not exist for business partner &1 |
| 612 | There is no address for business partner & |
| 613 | No other address exists for business partner &1 |
| 614 | The 'standard address' indicator may not be deleted |
| 615 | Address &1 does not exist; cannot assign telephone number &2 &3 |
| 616 | Address &1 does not exist; cannot assign fax number &2 &3 |
| 617 | Invalid change type &1 for telephone number |
| 618 | Cannot change or delete telephone number because &1 &2 does not exist |
| 619 | Cannot create telephone number because &1 &2 already exists |
| 620 | Invalid change type &1 for fax number |
| 621 | Cannot create or delete fax numbers because &1 &2 do not exist |
| 622 | Cannot create fax number because &1 &2 already exists |
| 623 | Change type &1 of the address is not defined |
| 624 | Change type &1 of the Internet address is not defined |
| 625 | Standard address cannot be deleted |
| 626 | Address with number &1 already exists |
| 627 | Cannot change or delete address because &1 does not exist |
| 628 | Cannot create Internet address because &1 already exists |
| 629 | Cannot change or delete Internet address because &1 does not exist |
| 630 | Cannot create because address usages &1 &2 already exist |
| 631 | Address &1 does not exist; address usage &1 &2 cannot be created |
| 632 | Address usage &1 &2 &3 do not exist; action not possible |
| 633 | Address &1 does not exist; address usage &1 &2 cannot be changed |
| 634 | Address &1 does not exist; address usage &1 &2 cannot be deleted |
| 635 | Position cursor on the address type of the usage to be created |
| 636 | Position cursor on an address usage |
| 637 | Standard address usage cannot be deleted |
| 638 | Address usage &1 &2 cannot be modified (address &1 does not exist) |
| 639 | Address cannot be deleted due to address usages. |
| 640 | Position cursor on the new standard usage |
| 641 | An address with ext.address no. = INITIAL already exists for partner &1 |
| 642 | Address type &1 does not exist: Address usage &1 &2 cannot be created |
| 643 | Address number &1 is not unique; do not change or delete |
| 644 | No Address Type is Assigned to Transaction for Address Determination &1 |
| 645 | You cannot create more than one usage for address type &1. |
| 646 | No other address exists for usage for address type &1 |
| 647 | Change type for address or communication data has not been defined |
| 648 | Cannot change because multiple addresses with external number SPACE exist |
| 649 | Address usages for deleted address also deleted |
| 650 | Standard telephone numbers cannot be deleted |
| 651 | Standard fax numbers cannot be deleted |
| 652 | Address usage &1 &2 cannot be changed (standard indicator blank) |
| 653 | Fixed address for partner &1 does not exist; standard address is used |
| 654 | Address with external number &2 for business partner &1 does not exist |
| 655 | No address type has been assigned to BP role &1 |
| 656 | Address type &1 does not exist |
| 657 | Text for address type &1 does not exist in language &2 |
| 658 | Address with external number &2 for partner &1 already exists |
| 659 | Address incomplete; enter the city or the P.O. box |
| 660 | The standard Internet address must not be deleted |
| 661 | The standard teletex number must not be deleted |
| 662 | The standard telex number must not be deleted |
| 663 | Standard RML address must not be deleted |
| 664 | The standard X.400 address must not be deleted |
| 665 | The standard RFC destination must not be deleted |
| 666 | The standard printer must not be deleted |
| 667 | The standard SSF address must not be deleted |
| 668 | The standard URI address must not be deleted |
| 669 | The standard pager number must not be deleted |
| 670 | Transfer of CBP to address category 2 completed successfully |
| 671 | Transfer of CBP to address category 2 started on &1 at &2 |
| 672 | &1 partners in total were edited |
| 673 | &2 address/es were transferred with &1 partner/s of the category "person" |
| 674 | &1 addresses for the partner in the organization/group cat. were edited |
| 675 | Transfer of CBP to address category 2 completed on &1 at &2 |
| 676 | Select an Address |
| 677 | Transaction for address determination &1 does not exist |
| 678 | SSF address with sequential number &1 does not exist |
| 679 | URI address with sequential number &1 does not exist |
| 680 | Pager number with sequential number &1 does not exist |
| 681 | Cannot change or delete teletex number because &1 does not exist |
| 682 | Cannot create teletex number because &1 already exists |
| 683 | Cannot change or delete telex number because &1 does not exist |
| 684 | Cannot create telex number because &1 already exists |
| 685 | Cannot change or delete RML address because &1 &2 does not exist |
| 686 | Cannot create RML address because &1 &2 already exists |
| 687 | Cannot change or delete X.400 address because &1 &2 &3 does not exist |
| 688 | Cannot create X.400 address because &1 &2 &3 already exists |
| 689 | Cannot change or delete RFC destination because &1 does not exist |
| 690 | Cannot create RFC destination because &1 already exists |
| 691 | Cannot change or delete printer because &1 does not exist |
| 692 | Cannot create printer because &1 already exists |
| 693 | Cannot change or delete SSF address because &1 &2 does not exist |
| 694 | Cannot create SSF address because &1 &2 already exists |
| 695 | Cannot change or delete URI address because &1 &2 does not exist |
| 696 | Cannot create URI address because &1 &2 already exists |
| 697 | Cannot change or delete pager number because &1 &2 does not exist |
| 698 | Cannot create pager number because &1 &2 already exists |
| 699 | Partner &1 is invalid |
| 700 | * 700: BP-Relationships: Control |
| 701 | Modus & for relationships/role definition maintenance not permitted |
| 702 | No authorization for one of the active & |
| 703 | Bank details &1 not valid for selection date &2 |
| 704 | No gap allowed between move/change date and validity end |
| 705 | &(s) do not exist or are not active or you do not have authorization |
| 706 | Partner selections are combined (correspond. search strategy) |
| 707 | Function module does not exist for differentiation element &1 |
| 708 | BP role &1 not permitted ('General Maintenance' indicator set) |
| 709 | No data for relationship/role definition found in local memory |
| 710 | Only & entries were read |
| 711 | Enter differentiation criteria |
| 712 | Program or dynpro does not exist for differentiation element &1 |
| 713 | No maintenance of & & without complete differentiation |
| 714 | Choose & |
| 715 | Enter & |
| 716 | Enter the first business partner |
| 717 | Enter the second business partner |
| 718 | No differentiation specifications are required for & & |
| 719 | &1 &2 &3 &4 updated; no display because no longer in work area |
| 720 | &1 &2 &3 have default values; there are no other input options |
| 721 | No details need to be edited |
| 722 | BP role &1 not permitted for role definition category &2 |
| 723 | &1 already exists in listing |
| 724 | Overlapping of validity areas; &1 already exists |
| 725 | Business partner &1 does not exist in a role with diff. type &2 |
| 726 | No data exists to be saved |
| 727 | This &1 already exists |
| 728 | For business partner &1, no further &2 of this category can be created |
| 729 | Business partner &1 is being processed in this mode |
| 730 | User &1 is processing the business partners &2 &3 &4 |
| 731 | SYST: Error during blocking of BP &1 |
| 732 | 'Valid From' greater than 'Valid To' (&1 &2 &3 &4) |
| 733 | &1 &2 &3 &4 do not exist |
| 734 | Cannot create &1 &2 &3 &4 because internal number is missing |
| 735 | Number range interval &1 for number range object &2 incorrectly maintain. |
| 736 | Validity key date &1 not adhered to |
| 737 | BP role &1 does not have required differentiation type &2 |
| 738 | & was not saved; make entry in all required fields |
| 739 | &1 &2 is not within work area |
| 740 | Detail data must still be maintained |
| 741 | Enter a 'Valid From' date |
| 742 | Enter a 'Valid To' date |
| 743 | BP role selections are mutually exclusive |
| 744 | Partner is ignored unless indicator is set |
| 745 | Relationship maintenance possible only for selected partner(s) |
| 746 | You can only maintain relationships or role definitions |
| 747 | Select nodes or place cursor on end node |
| 748 | Change was made |
| 749 | There is no detail data |
| 750 | &: Generic value not permitted for & & |
| 751 | Place cursor on an end node (representing &) |
| 752 | Delete selection, then position cursor |
| 753 | Date updated (& & & &) |
| 754 | Place cursor on the line with the partner data |
| 755 | Place cursor on the field with the partner number |
| 756 | Define &1 (&2) uniquely |
| 757 | Effect on another validity interval; use change mode |
| 758 | Maximum no. of relationships (&) in this relationship set exceeded |
| 759 | Maximum no. of role definitions (&) in this set exceeded |
| 760 | No time constraint; date specifications will be ignored & & & & |
| 761 | Time constraint 1; Deletion of a single interval not permitted & & & & |
| 762 | There is a gap in lower date limit &1 &2 &3 &4 |
| 763 | Predecessor &1 renewed until &2 &3 &4 |
| 764 | Validity intervals changed & & & & |
| 765 | Multiple intervals changed at same time & & & & |
| 766 | Interval &1 deleted &2 &3 &4 |
| 767 | Interval &1 extended to &2 &3 &4 |
| 768 | Interval &1 delimited at the beginning &2 &3 &4 |
| 769 | Interval &1 delimited at the end &2 &3 &4 |
| 770 | Interval &1 divided &2 &3 &4 |
| 771 | Interval &1 moved to &2 &3 &4 |
| 772 | Interval &1 is limited at beginning and end &2 &3 &4 |
| 773 | No time constraint; &1 already exists &2 &3 &4 |
| 774 | Existing interval does not match time constraint & & & & |
| 775 | Time constraint 1; single interval to &1 is enough &2 &3 &4 |
| 776 | & cannot be created between identical business partners |
| 777 | & cannot be planned |
| 778 | Notes cannot be planned |
| 779 | &2 already exists; further interval not possible &3 &4 |
| 780 | &1 has more validity intervals than were designated &2 &3 &4 |
| 781 | BP &1 already has max. no. of relships possible for this relship category |
| 782 | Partner &1 already has the maximum number of role definitions possible |
| 783 | Differentiation according to the BP role is not defined |
| 784 | Do not enter a role with relationships |
| 785 | Validity Intervals No Longer Correspond to the Time Constraint |
| 786 | Relationship category & does not have any fields requiring configuration |
| 787 | Role definition cat. & does not have any fields requiring configuration |
| 788 | Enter the Relationship Number or Relationship Category |
| 789 | Enter the Relationship Number or Role Determination Category |
| 790 | Differentiation Criterion &1 &2 is Not in Work Area |
| 791 | You May Only Change Validity Dates |
| 792 | Cannot fill all required entry fields |
| 793 | No valid relationship exists |
| 794 | No valid role determination exists |
| 795 | Enter at Least One Change Document Type |
| 796 | Transfer module for reading distribution-relevant data is missing |
| 797 | Validity period not allowed; bank details are target for move using &1 |
| 798 | Bank details are target of move and may therefore not be deleted |
| 799 | Bank details still being used; change of date not allowed |
| 800 | * 800: BP Relationships: Data |
| 801 | Department & does not exist |
| 802 | Function & does not exist |
| 803 | Power of attorney & does not exist |
| 804 | VIP ID & does not exist |
| 805 | No text exists for department &1 in language &2 |
| 806 | No text exists for function &1 in language &2 |
| 807 | No text exists for power of attorney &1 in language &2 |
| 808 | No text exists for VIP indicator &1 in language &2 |
| 809 | Specifiy either all or no bank details to enter the IBAN |
| 810 | Spouses are the same sex |
| 811 | Spouse &1 is already married |
| 812 | Marital property regime & does not exist |
| 813 | Text for marital property regime &1 does not exist in language &2 |
| 814 | Role &1 cannot be created/edited with BP transaction |
| 815 | HCM integration active: Relationship can only be displayed in this system |
| 816 | Shareholding total in partner &1: &2 % (&3) |
| 817 | Percentage is too high (maximum 100%) |
| 818 | Currency & does not exist |
| 819 | Enter a currency |
| 820 | Personal addresses in a company cannot be copied |
| 821 | No central evaluation of communication data without company address |
| 822 | No time dependence in address data |
| 823 | Cannot maintain address data; display only |
| 824 | Cannot maintain relationship data in full |
| 825 | No address exists for relationship &1 |
| 826 | Business partner &2 is already contact person for business partner &1 |
| 827 | Business partner &2 is already employee of business partner &1 |
| 828 | Business partner &1 is not an (internal) organizational unit |
| 829 | Business partner &1 is not an employee |
| 830 | Field grouping data for relationship category & does not exist |
| 831 | Field grouping data for role definition category & does not exist |
| 832 | Relationship type & does not exist |
| 833 | Text for relationship type &1 does not exist in language &2 |
| 834 | Role definition type & does not exist |
| 835 | Text for role definition type &1 does not exist in language &2 |
| 836 | Relationship type &1 is not defined for relationship category &2 |
| 837 | Role definition type &1 is not defined for role definition category &2 |
| 838 | Assign company address to fill all required fields |
| 839 | HCM integration active: Relat. cat. can only be displayed in this system |
| 840 | Test: Company code & does not exist |
| 841 | Test: Purchasing organization & does not exist |
| 842 | Test: Distribution channel & does not exist |
| 843 | Test: Division & does not exist |
| 844 | Test: Sales area & & & is not defined |
| 845 | Test: Company code cannot be changed from &1 to &2 |
| 846 | Can be edited using organization management only |
| 847 | No authorization to maintain relationships of category &1 |
| 848 | No authorization to display relationships of category &1 |
| 849 | Business partner &1 is not &2 or &3 |
| 850 | * 850: Central messages |
| 851 | SYST: Error in Module &1 &2 &3 &4 |
| 852 | SYST: Error in routine &1 &2 &3 &4 |
| 853 | SYST: Error in Function &1 &2 &3 &4 |
| 854 | Error during number assignment f. scheduled addresses: Obj.&1 interval &2 |
| 855 | Error When Inserting Table &1 &2 &3 &4 |
| 856 | Error When Updating Table &1 &2 &3 &4 |
| 857 | Error When Deleting Table &1 &2 &3 &4 |
| 858 | Appl.Object &1:there is currently no visible screen in screen sequence &2 |
| 860 | Business partner &1 and data cleansing case &2 created |
| 861 | Check log: TA SLG1 with message object BDT_DYNPRO_GENERATE |
| 862 | Program &1 has been executed without errors |
| 863 | Required entry field "country/region key" is not filled. |
| 864 | Required entry field 'Mobile Telephone' is not filled in address &1 |
| 865 | Select at least one field |
| 866 | Node entry is incorrect |
| 867 | Error in update |
| 868 | The node entered does not exist |
| 869 | Do not delete this node otherwise data will be lost |
| 870 | Action not carried out |
| 871 | Data could not be loaded |
| 872 | More Than One Entry will be Changed With This Input Data |
| 873 | Additional information is only saved in the logon language |
| 874 | Only the additional information can be changed in a substitute node |
| 875 | Select at least one entry |
| 876 | Enter an Address for the External Address Number &1 |
| 877 | Required entry field 'mobile telephone' is not filled |
| 878 | ApplObj. &1: Assignment ObjTGrp. &2 for category &3 does not exist |
| 879 | ApplObj &1: Assignment object part &2 to category &3 does not exist |
| 880 | You cannot open note object with key (&1, &2) |
| 881 | Note object with key (&1, &2) does not exist |
| 882 | Note object with key (&1, &2) has no temporary number |
| 883 | Field group to view assignment for current note view not found |
| 884 | No or multiple field groups found for view &1 of note object |
| 885 | Specify a date |
| 886 | External and internal date are not the same |
| 887 | Application object &1: Screen sequence category &2 does note exist |
| 888 | Application Object &1: Screen Seq.Cat &2 Does Not Support Divisibility |
| 889 | Application object &1: Object part &2 does not exist |
| 890 | No suitable object part exists |
| 891 | Application Obj &1: Screen Configuration Deleted from Request &2 |
| 892 | Update run can only be conducted as a background run |
| 893 | Application Object &1: Screen Configuration Written in Request &2 |
| 894 | Error occurred when calling VCT method & |
| 895 | VCT control for screen configuration does not exist |
| 896 | Error when calling VCT control |
| 897 | The table of generated screen sequences does not contain any entries |
| 898 | Client & is not permitted |
| 899 | Maximum number of generated screen sequences exceeded |
| 901 | This Version of the Visual Configuration Tool is Not the Current Version |
| 902 | Gender &1 is not permitted |
| 905 | State a payment card details ID |
| 908 | Business Partner with GUID &1 already exists |
| 919 | This contact person relationship cannot contain data other than RELTYPE |
| 960 | No Authorization To Delete Partner without Authorization group &1 |