SAP ABAP Message Class R11 (Business Partner and BDT)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-BP (Application Component) Business Partner Foundation
⤷
S_BUPA_GENERAL (Package) SAP Business Partner: Basic Components
⤷
⤷
Attributes
| Message class | R11 | |
| Short Description | Business Partner and BDT | |
| Changed On | 20140121 | |
| Last Changed At | 103746 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | * Organization: from 600: archiving | Space: object requires documentation | ||
| 2 | You don't have authorization to access the blocked business partner &1 | Space: object requires documentation | ||
| 3 | One or more blocked business partners are not displayed | Space: object requires documentation | ||
| 4 | Data privacy switch for business partner is not active | The short text describes the object sufficiently | ||
| 5 | You do not have authorization to perform block/unblock activity | Space: object requires documentation | ||
| 6 | Data maintenance for blocked business partners is not allowed. | Space: object requires documentation | ||
| 7 | No partners found for stated selection | The short text describes the object sufficiently | ||
| 8 | Do not enter parameters &1 and &2 at the same time | The short text describes the object sufficiently | ||
| 9 | Deletion of partner not possible; memory is inconsistent | The short text describes the object sufficiently | ||
| 10 | Details in &1 &2 &3 &4 not compatible | The short text describes the object sufficiently | ||
| 11 | No appropriate external grouping exists for partner number &1 | Space: object requires documentation | ||
| 12 | Industry system &1 not reserved for data exchange | Space: object requires documentation | ||
| 13 | No display variant exists | Space: object requires documentation | ||
| 14 | For customers only | Space: object requires documentation | ||
| 15 | Maximum search time exceeded, hit list incomplete | Space: object requires documentation | ||
| 16 | Enter other search criteria | Space: object requires documentation | ||
| 17 | No higher-level table was defined for table & | Space: object requires documentation | ||
| 18 | Specify the root of the tree | Space: object requires documentation | ||
| 19 | Enter one root table only | Space: object requires documentation | ||
| 20 | A table cannot be its own higher-level table | Space: object requires documentation | ||
| 21 | Selection limited to & hits | Space: object requires documentation | ||
| 22 | No variants exist | Space: object requires documentation | ||
| 23 | Error in & & when calling & & | Space: object requires documentation | ||
| 24 | No search possible | Space: object requires documentation | ||
| 25 | You cannot change the business partner grouping | Space: object requires documentation | ||
| 26 | Address number & does not exist | Space: object requires documentation | ||
| 27 | External business partner number is blank | Space: object requires documentation | ||
| 28 | Internal standard grouping &1 must not be deleted | Space: object requires documentation | ||
| 29 | External standard grouping &1 must not be deleted | Space: object requires documentation | ||
| 30 | No internal standard grouping exists | Space: object requires documentation | ||
| 31 | No external standard grouping exists | Space: object requires documentation | ||
| 32 | Business partner GUID is blank | Space: object requires documentation | ||
| 33 | Business partner &1 does not have GUID &2 | Space: object requires documentation | ||
| 34 | Business partner &1 does not have external number &2 | Space: object requires documentation | ||
| 35 | Business partner with GUID &1 does not have external number &2 | Space: object requires documentation | ||
| 36 | Specify at least one number for the business partner | Space: object requires documentation | ||
| 37 | Business partner with GUID &1 does not exist | Space: object requires documentation | ||
| 38 | Business partner &1 has not been assigned to any role | Space: object requires documentation | ||
| 39 | BP category &1 does not fit the data in category &2 | Space: object requires documentation | ||
| 40 | Contact person relationship already exists between partners &1 and &2 | Space: object requires documentation | ||
| 41 | Contact person relationship does not exist between partners &1 and &2 | Space: object requires documentation | ||
| 42 | Specify at least one number for the address | Space: object requires documentation | ||
| 43 | An address with GUID &2 does not exist for business partner &1 | Space: object requires documentation | ||
| 44 | Address &2 for business partner &1 does not have GUID &3 | Space: object requires documentation | ||
| 45 | Address &2 for business partner &1 does not have external number &3 | Space: object requires documentation | ||
| 46 | The address with GUID &2 for business partner &1 does not have ext.no.&3 | Space: object requires documentation | ||
| 47 | No address with external number &2 exists for business partner &1 | Space: object requires documentation | ||
| 48 | Specify an address number or address GUID | Space: object requires documentation | ||
| 49 | Address already exists for contact person relationship between &1 and &2 | Space: object requires documentation | ||
| 50 | Country key &1 does not match ISO code &2 | Space: object requires documentation | ||
| 51 | Language key &1 does not match ISO code &2 | Space: object requires documentation | ||
| 52 | There is no address with internal number &2 for partner &1 | Space: object requires documentation | ||
| 53 | No address usage found for business partner &1 and address type &2 | Space: object requires documentation | ||
| 54 | No address usages found | Space: object requires documentation | ||
| 55 | Business partner &1: No address usage for address &2, address type &3 | Space: object requires documentation | ||
| 56 | No bank details found | Space: object requires documentation | ||
| 57 | No credit card details found | Space: object requires documentation | ||
| 58 | Specify at least one number for a set of bank details | Space: object requires documentation | ||
| 59 | No contact person relationship exists for partner &1 | Space: object requires documentation | ||
| 60 | Business partner &1 does not (yet) have a GUID | Space: object requires documentation | ||
| 61 | No business partner found | Space: object requires documentation | ||
| 62 | Enter valid selection parameters | Space: object requires documentation | ||
| 63 | Employee relationship does not exist between partners &1 and &2 | Space: object requires documentation | ||
| 64 | Employee relationship between partners &1 and &2 already exists | Space: object requires documentation | ||
| 65 | Partner &1's bank details with ID &2 do not have external ID &3 | Space: object requires documentation | ||
| 66 | No BP role exists for partner &1 | Space: object requires documentation | ||
| 67 | No category &1 relationship exists for partner &2 | Space: object requires documentation | ||
| 68 | Transferred partner number &1 and partner number &2 found are not equal | Space: object requires documentation | ||
| 69 | Transferred partner GUID &1 and partner GUID &2 found are not equal | Space: object requires documentation | ||
| 70 | Transferred ext.BP no.&1 and ext.BP no. &2 found are not equal | Space: object requires documentation | ||
| 71 | Business partner with GUID &1 does not exist | Space: object requires documentation | ||
| 72 | The partner numbers that were transferred are inconsistent | Space: object requires documentation | ||
| 73 | No matching business partner found | Space: object requires documentation | ||
| 74 | Employee relationship between &1 and &2 does not exist | Space: object requires documentation | ||
| 75 | Contact person relationship between partners &1 and &2 already exists | Space: object requires documentation | ||
| 76 | Contact person relationship between partners &1 and &2 does not exist | Space: object requires documentation | ||
| 77 | Contact person relationship in the period from &1 to &2 is invalid | Space: object requires documentation | ||
| 78 | Relationship Between Partner &1 and &2 Does Not Exist | Space: object requires documentation | ||
| 79 | Relationship Between Partner &1 and &2 Already Exists | Space: object requires documentation | ||
| 80 | Error-Tolerant Search for Business Partners is Not Possible | Space: object requires documentation | ||
| 81 | This folder is still being used in filter view &1 | Space: object requires documentation | ||
| 82 | With Business Partner &1 There is No Address for Transaction &2 | Space: object requires documentation | ||
| 83 | You Must Not Delete View Because It is Still Being Used In Transactions | Space: object requires documentation | ||
| 84 | No Industry Data Found | Space: object requires documentation | ||
| 85 | Specify an industry system | Space: object requires documentation | ||
| 86 | Specify an industry | Space: object requires documentation | ||
| 87 | No Industry Data Found for Business Partner &1 | Space: object requires documentation | ||
| 88 | For Partner &1, Industry &2 Already Created With Industry Key &3 | Space: object requires documentation | ||
| 89 | No ID Numbers Found | Space: object requires documentation | ||
| 90 | No ID Number Found For Business Partner &1 | Space: object requires documentation | ||
| 91 | ID number &2 with ID type &3 already created for partner &1 | Space: object requires documentation | ||
| 92 | Industry &1 Not Defined for Industry Key System &2 | Space: object requires documentation | ||
| 93 | No Business Partner Matching the Search Criteria Found | Space: object requires documentation | ||
| 94 | The Where-Used List Does Not Have Any Reference | Space: object requires documentation | ||
| 95 | Partner &1: Industry &2 Does Not Exist for Industry Key System &3 | Space: object requires documentation | ||
| 96 | Text for Transaction &1 Does Not Exist in Language &2 | Space: object requires documentation | ||
| 97 | Business Partner May Not be Changed Because of Status & | Space: object requires documentation | ||
| 98 | Business partner &1 has status &2 | Space: object requires documentation | ||
| 99 | Number &1 Already Exists for ID Type &2 | Space: object requires documentation | ||
| 100 | Industry &1 Already Exists for Industry Key System &2 | Space: object requires documentation | ||
| 101 | Maximum of 5 industries permitted for ERP industry system | Space: object requires documentation | ||
| 102 | The standard industry is not unique for industry system &1 | Space: object requires documentation | ||
| 103 | Enter ID Type | Space: object requires documentation | ||
| 104 | Enter ID Number | Space: object requires documentation | ||
| 105 | Enter a Valid ID Type | Space: object requires documentation | ||
| 106 | Entries Included in Request &1 | Space: object requires documentation | ||
| 107 | Identification types do not exist | Space: object requires documentation | ||
| 108 | Identification type &1 is not defined for persons | Space: object requires documentation | ||
| 109 | Identificaton type &1 is not defined for organizations | Space: object requires documentation | ||
| 110 | Identification type &1 is not defined for groups | Space: object requires documentation | ||
| 111 | No Industries Exist | Space: object requires documentation | ||
| 112 | No Industries Exist for Industry System & | Space: object requires documentation | ||
| 113 | Validity End is Before Registration Date | Space: object requires documentation | ||
| 114 | Business partner & does not have any relationships | Space: object requires documentation | ||
| 115 | There is no address &3 for the relationship between partner &1 and &2 | Space: object requires documentation | ||
| 116 | Industry &1 Does Not Exist in Industry System &2 | Space: object requires documentation | ||
| 117 | There Must be At Least One Basic Node | Space: object requires documentation | ||
| 118 | Nothing May Refer to Itself | Space: object requires documentation | ||
| 119 | Parameter &1 has not been specified for name format check | Space: object requires documentation | ||
| 120 | Industry &1 may not be deleted because it is referred to | Space: object requires documentation | ||
| 121 | Industries &1 may not be deleted because they are referred to | Space: object requires documentation | ||
| 122 | Industry &1 for industry number system &2 already deleted | Space: object requires documentation | ||
| 123 | Shareholder relationship already exists between partners &1 and &2 | Space: object requires documentation | ||
| 124 | Shareholder relationship invalid in period from &1 to &2 | Space: object requires documentation | ||
| 125 | Shareholder relationship between partners &1 and &2 does not exist | Space: object requires documentation | ||
| 126 | Internet user for user &1 may not be intialized | Space: object requires documentation | ||
| 127 | Enter the Internet user | Space: object requires documentation | ||
| 128 | Number &1 already deleted for identification type &2 | Space: object requires documentation | ||
| 129 | Internet user &1 already assigned to user &2 | Space: object requires documentation | ||
| 130 | Internet user &1 already assigned to partner &2 | Space: object requires documentation | ||
| 131 | Password invalid | Space: object requires documentation | ||
| 132 | Password and repeat password must be identical | Space: object requires documentation | ||
| 133 | User group &1 does not exist | Space: object requires documentation | ||
| 134 | User role &1 already assigned | Space: object requires documentation | ||
| 135 | Roles of reference user &1 have already been transferred | Space: object requires documentation | ||
| 136 | User &1 of user &2 blocked | Space: object requires documentation | ||
| 137 | You are not authorized to maintain user data | Space: object requires documentation | ||
| 138 | Select one role only | Space: object requires documentation | ||
| 139 | You are not authorized to maintain user &1 | Space: object requires documentation | ||
| 140 | User &2 does not have authorization for assignment of user group &1 | Space: object requires documentation | ||
| 141 | Relationship in period from &1 to &2 not valid | Space: object requires documentation | ||
| 142 | No business partner exists for user &1 | Space: object requires documentation | ||
| 143 | No business partnerr exists for Internet user &1 | Space: object requires documentation | ||
| 144 | New planning date must be greater than current date | Space: object requires documentation | ||
| 145 | Old or new planning date invalid | Space: object requires documentation | ||
| 146 | New planning date must be different to the old planning date | Space: object requires documentation | ||
| 147 | There are conflicts with other plans for object &1 (&2) | Space: object requires documentation | ||
| 148 | No plans found for date &1 for object &2 (&3) | Space: object requires documentation | ||
| 149 | Postponement of planning for object &2 (&1) already marked | Space: object requires documentation | ||
| 150 | In the case of &1, no data for partner &2 found in memory | Space: object requires documentation | ||
| 151 | No BP relationship exists for differentiation type value &1 | Space: object requires documentation | ||
| 152 | Address type &1 may not be deleted | Space: object requires documentation | ||
| 153 | Address &1 already indicated as standard address | Space: object requires documentation | ||
| 154 | The move date occurs in the past | Space: object requires documentation | ||
| 155 | No move target address exists | Space: object requires documentation | ||
| 156 | Internal error when calling operation module &; a check table is missing | Space: object requires documentation | ||
| 157 | Error for validity periods of addresses | Space: object requires documentation | ||
| 158 | Error for validity periods of address usages | Space: object requires documentation | ||
| 159 | Conversion error; the date is invalid | Space: object requires documentation | ||
| 160 | No bank details exist for change | Space: object requires documentation | ||
| 161 | Change not possible; ID &1 would occur more than once in the change chain | The short text describes the object sufficiently | ||
| 162 | Cannot move; address &1 would then occur more than once in the move chain | The short text describes the object sufficiently | ||
| 163 | No address-independent communication data exists for business partner &1 | Space: object requires documentation | ||
| 164 | Communication data successfully transferred | Space: object requires documentation | ||
| 165 | Transfer of communication data not possible | Space: object requires documentation | ||
| 166 | Standard industry system was changed | Space: object requires documentation | ||
| 167 | The target ID does not exist in the bank details change | The short text describes the object sufficiently | ||
| 168 | No usages correspond to the selection criteria | The short text describes the object sufficiently | ||
| 169 | All applications selected are inactive | The short text describes the object sufficiently | ||
| 170 | No APIs exist for the selected active applications | Space: object requires documentation | ||
| 171 | There is no active distribution application (table TB048) | The short text describes the object sufficiently | ||
| 172 | Maintenance of time-dependent data not permitted,as schedules still exist | The short text describes the object sufficiently | ||
| 173 | No partners found for this selection | The short text describes the object sufficiently | ||
| 174 | Only &1 sections may be assigned! | Space: object requires documentation | ||
| 175 | Only &1 views may be assigned! | Space: object requires documentation | ||
| 176 | You may not enter any numbers in the dialog for ID type &1 | The short text describes the object sufficiently | ||
| 177 | You may not delete any numbers in the dialog for ID type &1 | The short text describes the object sufficiently | ||
| 178 | Validity period of the target bank details is not sufficient | Space: object requires documentation | ||
| 179 | Validity period not permitted; bank details are change target of ID &1 | Space: object requires documentation | ||
| 180 | Validity period of the target move address is not sufficient | Space: object requires documentation | ||
| 181 | Validity period not permitted; address is move target of other addresses | Space: object requires documentation | ||
| 182 | Selected address already assigned to address type &1 | The short text describes the object sufficiently | ||
| 183 | Telephone number &1 &2 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 184 | Telephone number &1 &2 already exists | Space: object requires documentation | ||
| 185 | Fax number &1 &2 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 186 | Fax number &1 &2 already exists | Space: object requires documentation | ||
| 187 | Teletex number &1 &2 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 188 | Teletex number &1 &2 already exists | Space: object requires documentation | ||
| 189 | Telex number &1 &2 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 190 | Teletex number &1 &2 already exists | Space: object requires documentation | ||
| 191 | SMTP &1 &2 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 192 | SMTP &1 already exists | Space: object requires documentation | ||
| 193 | Remote mail &1 &2 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 194 | Remote mail address &1 &2 already exists | Space: object requires documentation | ||
| 195 | X.400 &1 &2 &3 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 196 | X.400 &1 &2 &3 already exists | Space: object requires documentation | ||
| 197 | RFC &1 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 198 | RFC &1 already exists | Space: object requires documentation | ||
| 199 | Printer &1 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 200 | Printer &1 already exists | Space: object requires documentation | ||
| 201 | SSF address &1 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 202 | SSF address &1 already exists | Space: object requires documentation | ||
| 203 | URI address &1 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 204 | URI address &1 already exists | Space: object requires documentation | ||
| 205 | Pager address &1 &2 ambiguous; identification via CONSNUMBER | Space: object requires documentation | ||
| 206 | Pager address &1 &2 already exists | Space: object requires documentation | ||
| 207 | Gaps not permitted in the validity periods of the business partner data | The short text describes the object sufficiently | ||
| 208 | No validity gaps allowed | The short text describes the object sufficiently | ||
| 209 | Reference period insufficient | The short text describes the object sufficiently | ||
| 210 | No overlapping of validities allowed | The short text describes the object sufficiently | ||
| 211 | No update is defined for BP role &1 | Space: object requires documentation | ||
| 212 | Business partner &1 is a duplicate | Space: object requires documentation | ||
| 213 | Business partner &1 may not be deleted | Space: object requires documentation | ||
| 214 | Fatal error during attempted deletion of &1 | Space: object requires documentation | ||
| 215 | Transaction may be started only in development client | Space: object requires documentation | ||
| 216 | &1 &2 deleted | Space: object requires documentation | ||
| 217 | No dates that deviated from current date allowed | The short text describes the object sufficiently | ||
| 218 | Identification type &1, identification number &2 not available in BP &3 | Space: object requires documentation | ||
| 219 | Identification type &1, idenfication number &2 already deleted. | Space: object requires documentation | ||
| 220 | Bank details &1 of business partner &2 already deleted. | Space: object requires documentation | ||
| 221 | Address &1 of business partner &2 already deleted | Space: object requires documentation | ||
| 222 | BP &1 does not exist in role &2 diff. type &3 diff. type value &4 | Space: object requires documentation | ||
| 223 | Errors occurred during call of function module &1 | Space: object requires documentation | ||
| 224 | This language may be maintained only for persons | Space: object requires documentation | ||
| 225 | It is not possible to search using wildcards without specifying a country | Space: object requires documentation | ||
| 226 | There is no standard usage for addresss usage &1 | The short text describes the object sufficiently | ||
| 227 | Cannot search for fax numbers without specifying a country | Space: object requires documentation | ||
| 228 | Result of duplicate check incomplete | The short text describes the object sufficiently | ||
| 229 | Select exactly one business partner | The short text describes the object sufficiently | ||
| 230 | Select exactly one relationship | The short text describes the object sufficiently | ||
| 231 | The &1 &2 &3 &4 is a duplicate | The short text describes the object sufficiently | ||
| 232 | The function ( & ) is not supported in this case | The short text describes the object sufficiently | ||
| 233 | Time dependency of table &1 cannot be deactivated | Space: object requires documentation | ||
| 234 | Settings for development &1 not maintained for object &2 | The short text describes the object sufficiently | ||
| 235 | Activation settings not yet maintained | The short text describes the object sufficiently | ||
| 236 | Data set &1 for BP &2 maintained time-dependently,despite inact.time dep. | Space: object requires documentation | ||
| 237 | Several validity periods for BP &1 exist for selection | The short text describes the object sufficiently | ||
| 238 | Data of BP &1 from table &2 does not match the table's time constraint | The short text describes the object sufficiently | ||
| 239 | Valid-to and valid-from date necessary in order to change the validity | The short text describes the object sufficiently | ||
| 240 | Initial creation of a BP with restricted validity not allowed | The short text describes the object sufficiently | ||
| 241 | Creation of new validity period not possible | Space: object requires documentation | ||
| 242 | Choose a new validity period | The short text describes the object sufficiently | ||
| 243 | Creation of a validity period possible only with error-free data | The short text describes the object sufficiently | ||
| 244 | Deletion of currently displayed validity period not possible | The short text describes the object sufficiently | ||
| 245 | Validity change for currently displayed period not allowed | The short text describes the object sufficiently | ||
| 246 | Scheduling no longer possible via field VALDT | Space: object requires documentation | ||
| 247 | No central data for partner &1 in the required database activity &2 | Space: object requires documentation | ||
| 248 | *** BDT *** | Space: object requires documentation | ||
| 249 | Enter a value for field &1 | Space: object requires documentation | ||
| 250 | System unable to transfer values in field &1 | Space: object requires documentation | ||
| 251 | Application object &1: There is no BAPI field to screen field assignment | Space: object requires documentation | ||
| 252 | Generation of screen containers is locked by user &1 | Space: object requires documentation | ||
| 253 | No selection made | Space: object requires documentation | ||
| 254 | No change documents selected for your field selection | Space: object requires documentation | ||
| 255 | Use '+' for generic entries | Space: object requires documentation | ||
| 256 | Generic indicators for screen field and DB field only simultaneous | Space: object requires documentation | ||
| 257 | Generic indicators for DI field and DB field only simultaneous | Space: object requires documentation | ||
| 258 | No standard industry stated for standard industry number system &1 | Space: object requires documentation | ||
| 259 | Application Object &1: Application &2 not active. | Space: object requires documentation | ||
| 260 | DB field->screen field assignments missing for fields of field group &1 | Space: object requires documentation | ||
| 261 | Fields of field group &1 can be found on a different dynpro | Space: object requires documentation | ||
| 262 | DB field->screen field assignments incorrect for fields of field group &1 | Space: object requires documentation | ||
| 263 | Multiple assignment of field group &1 via DB field->screen field assgnmnt | Space: object requires documentation | ||
| 264 | No assignment exists for screen sequence category &1 to be transferred | Space: object requires documentation | ||
| 265 | Additional field groupings via criterion &1 exist. | Space: object requires documentation | ||
| 266 | Field grouping for field group &1 for &2 is: &3. | Space: object requires documentation | ||
| 267 | No authorizatio for &1 of field group &2. | Space: object requires documentation | ||
| 268 | No screen number stated for view &1. | Space: object requires documentation | ||
| 269 | No program name stated for view &1. | Space: object requires documentation | ||
| 270 | No screen number and program name stated for view &1. | Space: object requires documentation | ||
| 271 | BDT object &1 in language &2 not available. | Space: object requires documentation | ||
| 272 | BDT object &1 not available. | Space: object requires documentation | ||
| 273 | Application object &1 in client &2 not available | Space: object requires documentation | ||
| 274 | Language key &1 not available in system | Space: object requires documentation | ||
| 275 | No application objects available for client &1 | Space: object requires documentation | ||
| 276 | Client &1 does not exist | Space: object requires documentation | ||
| 277 | No application object texts available for client &1 | Space: object requires documentation | ||
| 278 | Application object &1: Results table of screen sequences is empty | Space: object requires documentation | ||
| 279 | Application object &1: Results table of screens is empty | Space: object requires documentation | ||
| 280 | Application object &1: Results table of screen texts is empty | Space: object requires documentation | ||
| 281 | Application object &1: Results table of sections is empty | Space: object requires documentation | ||
| 282 | Application object &1: Results table of sections texts is empty. | Space: object requires documentation | ||
| 283 | Application object &1: Results table of views is empty | Space: object requires documentation | ||
| 284 | Application object &1: Results table of view texts is empty | Space: object requires documentation | ||
| 285 | Application object &1: Results table of additional checks is empty | Space: object requires documentation | ||
| 286 | Applic.obj.&1:Results table of screen sequence screen assignment is empty | Space: object requires documentation | ||
| 287 | Application object &1:Results table of screen section assignment is empty | Space: object requires documentation | ||
| 288 | Application object &1: Results table of screen sequences is empty. | Space: object requires documentation | ||
| 289 | Application object &1: Results table of screen sequence texts is empty | Space: object requires documentation | ||
| 290 | Applicatn object &1:Results table of screen sequence categories is empty. | Space: object requires documentation | ||
| 291 | Application object &1: Results table of screen sequence texts is empty | Space: object requires documentation | ||
| 292 | Appl.obj.&1:Results table of scrn sequ.categ. scrn sequ assgnmnt is empty | Space: object requires documentation | ||
| 293 | Applicat. object &1:Results table of field group field assgnment is empty | Space: object requires documentation | ||
| 294 | Applic. object &1: Results table of view field group assignment is empty | Space: object requires documentation | ||
| 295 | Application object &1: Results table of field groups is empty | Space: object requires documentation | ||
| 296 | Application object &1: Results table of field group texts is empty | Space: object requires documentation | ||
| 297 | Application object &1: Results table of VCT usages is empty | Space: object requires documentation | ||
| 298 | Application object &1: Results table of object parts is empty | Space: object requires documentation | ||
| 299 | Application object &1: Results table of object part texts is empty | Space: object requires documentation | ||
| 300 | Appl. object &1: Results table of object part applic. assignment is empty | Space: object requires documentation | ||
| 301 | Appl. object &1: Results table of object part view assignment is empty | Space: object requires documentation | ||
| 302 | Application object &1: Results table of object part grouping is empty | Space: object requires documentation | ||
| 303 | Application object &1: Results table of obj. part grouping texts is empty | Space: object requires documentation | ||
| 304 | Appl. obj.&1: Results table obj.part grp. - obj.part assignment is empty | Space: object requires documentation | ||
| 305 | Appl. obj.&1: Results table obj.part group -scrn sequ. assignmnt is empty | Space: object requires documentation | ||
| 306 | Application object &1: Results table of data sets is empty | Space: object requires documentation | ||
| 307 | Application object &1: Results table of data set texts is empty | Space: object requires documentation | ||
| 308 | Application obj. &1: Results table of obj.part data set assgnmnt is empty | Space: object requires documentation | ||
| 309 | Applic. object &1: Results table of obj.part-scrn sequ. assignmt is empty | Space: object requires documentation | ||
| 310 | Application object &1: Results table of BDT applications is empty | Space: object requires documentation | ||
| 311 | Application object &1: Results table of BDT - application texts is empty | Space: object requires documentation | ||
| 312 | Application object &1: Results table of BDT activities is empty | Space: object requires documentation | ||
| 313 | Application object &1: Results table of BDT activity texts is empty | Space: object requires documentation | ||
| 314 | Application object &1: Results table of BDT table is empty | Space: object requires documentation | ||
| 315 | Events for application object &1 and BDT object &2 do not exist | Space: object requires documentation | ||
| 316 | Several application objects were transferred | Space: object requires documentation | ||
| 317 | Configured screen sequences defined for screen sequence category &1 | Space: object requires documentation | ||
| 318 | Incorrect assignment of screen sequence via table TBZ6. | Space: object requires documentation | ||
| 319 | External partner number &1 is ambiguous | The short text describes the object sufficiently | ||
| 320 | Print format &1 does not exist | The short text describes the object sufficiently | ||
| 321 | Higher-node role &1 may not be hidden | Space: object requires documentation | ||
| 322 | No texts available | The short text describes the object sufficiently | ||
| 323 | Too many places after decimal comma | Space: object requires documentation | ||
| 324 | No data transferred | Space: object requires documentation | ||
| 325 | Transferred table is too big | Space: object requires documentation | ||
| 326 | View &1 must be manually assigned to section &2 | Space: object requires documentation | ||
| 327 | Client &1 application object &2 screen &3: section &4: too many views | The short text describes the object sufficiently | ||
| 328 | Client &1 appl. object &2 screen &3: too many sections | The short text describes the object sufficiently | ||
| 329 | Client &1 appl.obj.&2 screen &3:Subscreen container could not be produced | The short text describes the object sufficiently | ||
| 330 | Client &1 appl.object &2 screen &3:Error during subscreen container gener | Space: object requires documentation | ||
| 331 | * BP roles: Customizing & dialog | The short text describes the object sufficiently | ||
| 332 | BP role category &1 is still in use and cannot be deleted | Space: object requires documentation | ||
| 333 | BP view &1 is still in use and cannot be deleted | Space: object requires documentation | ||
| 334 | Role &1 is assigned to exclusion group &2 and must be updated | Space: object requires documentation | ||
| 335 | Role not updated if a role category is not assigned | Space: object requires documentation | ||
| 336 | Enter a BP role | The short text describes the object sufficiently | ||
| 337 | BP role &1 not permitted | The short text describes the object sufficiently | ||
| 338 | Transition from BP role &1 to BP role &2 already exists | The short text describes the object sufficiently | ||
| 339 | Do not enter a disallowed transition | The short text describes the object sufficiently | ||
| 340 | BP role &1 already assigned to BP role exclusion group &2 | Space: object requires documentation | ||
| 341 | BP role exclusion group must contain at least two BP roles | Space: object requires documentation | ||
| 342 | Only update-relevant BP roles can be assigned | The short text describes the object sufficiently | ||
| 343 | &1 &2 in BP role &3 is &4 | The short text describes the object sufficiently | ||
| 344 | BP role category &1 not assigned to a transaction | The short text describes the object sufficiently | ||
| 345 | BP role category &1 not assigned to transaction &2 | The short text describes the object sufficiently | ||
| 346 | BP roles not assigned to relationship category &1 | The short text describes the object sufficiently | ||
| 347 | Relationship category &1 with assigned BP role &2 does not exist | The short text describes the object sufficiently | ||
| 348 | BP role &1 not assigned to any of the relevant BP role categories | The short text describes the object sufficiently | ||
| 349 | Only BP role grouping categories may be entered for SAP transactions | The short text describes the object sufficiently | ||
| 350 | Only BP role categories may be entered for SAP transactions | The short text describes the object sufficiently | ||
| 351 | Cannot simultaneously enter BP role grouping categ. and BP role grouping | The short text describes the object sufficiently | ||
| 352 | Cannot simultaneously enter BP role category and BP role | Space: object requires documentation | ||
| 353 | BP role grouping category &1 not assigned to BP role grouping &2 | Space: object requires documentation | ||
| 354 | Neither BP role grouping category nor BP role grouping transferred | Space: object requires documentation | ||
| 355 | Field grouping does not exist for BP role &1 | Space: object requires documentation | ||
| 356 | BP role &1 may not be deleted | Space: object requires documentation | ||
| 357 | No BP role exists | The short text describes the object sufficiently | ||
| 358 | Text for BP role &1 does not exist in language &2 | The short text describes the object sufficiently | ||
| 359 | No BP roles exist with BP role category &1 | The short text describes the object sufficiently | ||
| 360 | No BP role categories exist | The short text describes the object sufficiently | ||
| 361 | BP role category &1 does not exist | The short text describes the object sufficiently | ||
| 362 | Text for BP role category &1 does not exist in language &2 | The short text describes the object sufficiently | ||
| 363 | BP role &1 is not update-relevant | Space: object requires documentation | ||
| 364 | Transition to identical BP role &1 not possible | The short text describes the object sufficiently | ||
| 365 | BP role grouping &1 does not exist | The short text describes the object sufficiently | ||
| 366 | No BP role grouping exists with BP role grouping category &1 | The short text describes the object sufficiently | ||
| 367 | Text for BP role grouping &1 does not exist in language &2 | The short text describes the object sufficiently | ||
| 368 | Text for BP role grouping category &1 does not exist in language &2 | The short text describes the object sufficiently | ||
| 369 | BP role grouping category &1 does not exist | The short text describes the object sufficiently | ||
| 370 | No BP role groupings exist | The short text describes the object sufficiently | ||
| 371 | No BP role grouping categories exist | The short text describes the object sufficiently | ||
| 372 | No assignment exists for BP role grouping &1 | The short text describes the object sufficiently | ||
| 373 | BP role &1 is not assigned to a BP role grouping | The short text describes the object sufficiently | ||
| 374 | No BP role exclusion groups exist | The short text describes the object sufficiently | ||
| 375 | BP role exclusion group &1 does not exist | The short text describes the object sufficiently | ||
| 376 | Text for BP role exclusion group &1 does not exist in language &2 | The short text describes the object sufficiently | ||
| 377 | No assignment exists for BP role exclusion group &1 | The short text describes the object sufficiently | ||
| 378 | BP role &1 not assigned to a BP role exclusion group | The short text describes the object sufficiently | ||
| 379 | No permitted transitions exist from BP role &1 | The short text describes the object sufficiently | ||
| 380 | No permitted transitions exist to BP role &1 | The short text describes the object sufficiently | ||
| 381 | No standard assignment defined for BP role category &1 | Space: object requires documentation | ||
| 382 | Item number &1 already assigned for BP role &2 | The short text describes the object sufficiently | ||
| 383 | Select a BP role | The short text describes the object sufficiently | ||
| 384 | No assignment of BP role grouping categories to BP roles exists | The short text describes the object sufficiently | ||
| 385 | No valid BP roles exist for partner &2 at time &1 | The short text describes the object sufficiently | ||
| 386 | Conflict between BP role grouping &1 and BP role exclusion group &2 | Space: object requires documentation | ||
| 387 | A valid BP view is not assigned to BP role &1 | Space: object requires documentation | ||
| 388 | Move or change date 01.01.0001 is not allowed | The short text describes the object sufficiently | ||
| 389 | No assignments of BP role exclusion group to BP roles exist | The short text describes the object sufficiently | ||
| 390 | At least one initial role must be defined | The short text describes the object sufficiently | ||
| 391 | BP role &1 should not be defined as initial role | Space: object requires documentation | ||
| 392 | Assignment of BP role &1 not permitted because of disallowed transition | Space: object requires documentation | ||
| 393 | Validity of BP role &1 restricted to date &2 | Space: object requires documentation | ||
| 394 | BP role &1 deleted (&2 is valid BP role) | Space: object requires documentation | ||
| 395 | BP role &1 not created as subsequent role for &2 with start date &3 | The short text describes the object sufficiently | ||
| 396 | No BP roles exist with BP view &1 | The short text describes the object sufficiently | ||
| 397 | No BP role categories exist with differentiation type &1 | The short text describes the object sufficiently | ||
| 398 | BP roles of the BP role category &1 are mutually exclusive | The short text describes the object sufficiently | ||
| 399 | BP roles of the BP role category &1 already exist for partner &2 | The short text describes the object sufficiently | ||
| 400 | No changes were made to BP role &1 for partner &2 | The short text describes the object sufficiently | ||
| 401 | BP role &1 already assigned to status number &2 | The short text describes the object sufficiently | ||
| 402 | Table &1 converted successfully | The short text describes the object sufficiently | ||
| 403 | &1 records inserted in table &2 | The short text describes the object sufficiently | ||
| 404 | &1 records changed in table &2 | The short text describes the object sufficiently | ||
| 405 | Archive indicator not set for business partner &1 | Space: object requires documentation | ||
| 406 | Select filter and/or restrict BP selection | Space: object requires documentation | ||
| 407 | Not all time-dependent data has already been distributed for partner &1 | Space: object requires documentation | ||
| 408 | Setting a system status without deletion/archiving check not allowed | Space: object requires documentation | ||
| 409 | New archive file could not be created | The short text describes the object sufficiently | ||
| 410 | Error when reading address usage | The short text describes the object sufficiently | ||
| 411 | * BP Roles: BAPIs/ APIs | The short text describes the object sufficiently | ||
| 412 | "All BP roles" indicator allowed only in connection with BP role category | Space: object requires documentation | ||
| 413 | Do not transfer BP role category or BP role | The short text describes the object sufficiently | ||
| 414 | BP role &1 already exists for partner &2 | The short text describes the object sufficiently | ||
| 415 | Differentiation according to BP role &1 is not intended | The short text describes the object sufficiently | ||
| 416 | No BP roles exist for partner &1 | The short text describes the object sufficiently | ||
| 417 | BP role category &1 not assigned to BP role &2 | The short text describes the object sufficiently | ||
| 418 | BP role &1 does not exist for partner &2 | The short text describes the object sufficiently | ||
| 419 | Cannot delete BP role &1 | The short text describes the object sufficiently | ||
| 420 | Deletion of all BP roles only without entering differentiation type value | The short text describes the object sufficiently | ||
| 421 | BP role &1 w. differentiation type value &3 does not exist for partner &2 | The short text describes the object sufficiently | ||
| 422 | BP role &1 w. differentiation type value &3 already exists for partner &2 | The short text describes the object sufficiently | ||
| 423 | No BP role transferred | The short text describes the object sufficiently | ||
| 424 | No BP roles with BP role category &2 exist for partner &1 | The short text describes the object sufficiently | ||
| 425 | BP role grouping category &1 already assigned to BP role grouping &2 | The short text describes the object sufficiently | ||
| 426 | BP role &1 still in use; change to validity not allowed | The short text describes the object sufficiently | ||
| 427 | BP role &1 still in use; deletion not allowed | The short text describes the object sufficiently | ||
| 428 | Change type &1 of the BP role is not intended | Space: object requires documentation | ||
| 429 | Object &1 flagged for transport | The short text describes the object sufficiently | ||
| 430 | No Authorization To Delete Partner without Authorization group &1 | Space: object requires documentation | ||
| 431 | Enter selections | Space: object requires documentation | ||
| 432 | Key field &1 may not be changed in the case of an update / change | The short text describes the object sufficiently | ||
| 433 | Table &2 must have the same number of lines as &1 | The short text describes the object sufficiently | ||
| 434 | There is no standard address | Space: object requires documentation | ||
| 435 | Validity start is after validity end | The short text describes the object sufficiently | ||
| 436 | Address for address usage does not exist | The short text describes the object sufficiently | ||
| 437 | Validity period for the address usage not compatible with address | Space: object requires documentation | ||
| 438 | A standard address is not always specified | Space: object requires documentation | ||
| 439 | Standard usage has not been maintained for all required points in time | Space: object requires documentation |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in |