SAP ABAP Message Class MDGBP (Master Data Governance: Business Partner specific messages)
Basic Data
Hierarchy
☛
MDG_FND (Software Component) MDG Foundation
⤷
CA-MDG-APP-BP (Application Component) MDG Business Partner (Central Part)
⤷
MDG_BS_BP_MAPPING (Package) MDG: Business Partner - Mappings
⤷
⤷
Attributes
| Message class | MDGBP | |
| Short Description | Master Data Governance: Business Partner specific messages | |
| Changed On | 20130531 | |
| Last Changed At | 123600 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Archiving object &1 is not assigned to any application object | Space: object requires documentation | ||
| 2 | Application object &1: No assignment exists for BP role grouping &2 | Space: object requires documentation | ||
| 3 | Number &2 already assigned to partner &3 for ID type &1 | Space: object requires documentation | ||
| 4 | DiffType for BP role BP1 must be the same as DiffType for RelCat | Space: object requires documentation | ||
| 5 | DiffType for BP role BP1 must be the same as DiffType for RoleDefCat | Space: object requires documentation | ||
| 6 | DiffType for BP role BP2 must be the same as DiffType for RelCat | Space: object requires documentation | ||
| 7 | DiffType for BP role BP2 must be the same as DiffType for RoleDefCat | Space: object requires documentation | ||
| 8 | Authorization group &1 does not exist | Space: object requires documentation | ||
| 9 | You cannot create more than one usage for address type &1 | Space: object requires documentation | ||
| 10 | Existing interval does not match time constraint & & & & | Space: object requires documentation | ||
| 11 | Data set &1 for BP &2 maintained time-dependently,despite inact.time dep. | Space: object requires documentation | ||
| 12 | No standard assignment defined for BP role category &1 | Space: object requires documentation | ||
| 13 | Assignment of BP role &1 not permitted because of disallowed transition | Space: object requires documentation | ||
| 14 | Version indicator & is not defined | Space: object requires documentation | ||
| 15 | Version indicator & is not activated | Space: object requires documentation | ||
| 16 | Title key & is not defined in language & | Space: object requires documentation | ||
| 17 | Please enter a valid form of address | Space: object requires documentation | ||
| 18 | Reason for undeliverability & is not valid | Space: object requires documentation | ||
| 19 | Number range 01 for object ADRV does not exist or is not internal | Space: object requires documentation | ||
| 20 | No SMS service has been defined | Space: object requires documentation | ||
| 21 | Key & is not defined as name format for country & | Space: object requires documentation | ||
| 22 | Value &1 is invalid for indicator 'Display initial screen' | Space: object requires documentation | ||
| 23 | Business partner category cannot be changed | The short text describes the object sufficiently | ||
| 24 | There is no relevant data screen; all fields are hidden | Space: object requires documentation | ||
| 25 | Field &1-&2 not ready for input due to Customizing settings | Space: object requires documentation | ||
| 26 | Field &1-&2 cannot be scheduled | Space: object requires documentation | ||
| 27 | During activation, you must enter the field group for each field group | The short text describes the object sufficiently | ||
| 28 | Function &1 is controlled by the field group; navigation is not possible | Space: object requires documentation | ||
| 29 | You can only delete screen containers if all screens are re-generated | Space: object requires documentation | ||
| 30 | Function module &2 already assigned to event &1 | The short text describes the object sufficiently | ||
| 31 | Function module &2 is already assigned to event &1 | The short text describes the object sufficiently | ||
| 32 | Assignment for field &1 in structure &2 is not possible; no data transfer | Space: object requires documentation | ||
| 33 | Parameter & is blank | The short text describes the object sufficiently | ||
| 34 | Standard industry number system &1 must not be deleted | Space: object requires documentation | ||
| 35 | There is no industry number system | The short text describes the object sufficiently | ||
| 36 | Industry number system &1 does not exist | The short text describes the object sufficiently | ||
| 37 | Identification category &1 is assigned to several identification types | Space: object requires documentation | ||
| 38 | Text for industry key system &1 does not exist in language &2 | The short text describes the object sufficiently | ||
| 39 | Identification category &1 does not exist | The short text describes the object sufficiently | ||
| 40 | Identification category &1 is not assigned to any identification type | The short text describes the object sufficiently | ||
| 41 | Bank details &1 are still being used and must not be deleted | Space: object requires documentation | ||
| 42 | Bank details &1 are still being used, but can be deleted | Space: object requires documentation | ||
| 43 | Payment card &1 is still being used and must not be deleted | Space: object requires documentation | ||
| 44 | Payment card &1 is still being used, but can be deleted | Space: object requires documentation | ||
| 45 | Web address with sequential number &1 does not exist | The short text describes the object sufficiently | ||
| 46 | Cannot change or delete web address because &1 &2 does not exist | The short text describes the object sufficiently | ||
| 47 | Cannot create web address because &1 &2 already exists | The short text describes the object sufficiently | ||
| 48 | Validity intervals no longer correspond to the time constraint | Space: object requires documentation | ||
| 49 | Enter the relationship number or relationship category | The short text describes the object sufficiently | ||
| 50 | Enter the relationship number or role determination category | The short text describes the object sufficiently | ||
| 51 | Differentiation criterion &1 &2 is not in work area | The short text describes the object sufficiently | ||
| 52 | You may only change validity dates | Space: object requires documentation | ||
| 53 | There is no valid relationship | The short text describes the object sufficiently | ||
| 54 | There is no valid role determination | The short text describes the object sufficiently | ||
| 55 | Enter at least one change document type | Space: object requires documentation | ||
| 56 | Percentage is too high (max. 100%); correct percentage | The short text describes the object sufficiently | ||
| 57 | Update was not successful | The short text describes the object sufficiently | ||
| 58 | The node entered does not exist | The short text describes the object sufficiently | ||
| 59 | More than one entry will be changed with this input data | Space: object requires documentation | ||
| 60 | Enter an address for the external address number &1 | The short text describes the object sufficiently | ||
| 61 | ApplObj. &1: assignment ObjTGrp. &2 for ScrnSeqCat &3 does not exist | The short text describes the object sufficiently | ||
| 62 | ApplObj &1: assignment object part &2 to ScrnSeqCat &3 does not exist | The short text describes the object sufficiently | ||
| 63 | Application object &1: screen sequence category &2 does not exist | The short text describes the object sufficiently | ||
| 64 | Application object &1: screen seq.cat. &2 does not support divisibility | The short text describes the object sufficiently | ||
| 65 | Application object &1: object part &2 does not exist | The short text describes the object sufficiently | ||
| 66 | Application obj. &1: screen configuration deleted from request &2 | The short text describes the object sufficiently | ||
| 67 | Application object &1: screen configuration written in request &2 | The short text describes the object sufficiently | ||
| 68 | This version of the visual configuration tool is not the current version | Space: object requires documentation | ||
| 69 | Relationship between partner &1 and &2 does not exist | The short text describes the object sufficiently | ||
| 70 | Relationship between partner &1 and &2 already exists | The short text describes the object sufficiently | ||
| 71 | Error-tolerant search for business partners is not possible | Space: object requires documentation | ||
| 72 | You must not delete view because it is still being used in transactions | The short text describes the object sufficiently | ||
| 73 | No industry data found | The short text describes the object sufficiently | ||
| 74 | No industry data found for business partner &1 | The short text describes the object sufficiently | ||
| 75 | For partner &1, industry &2 already created with industry key & | The short text describes the object sufficiently | ||
| 76 | No ID numbers found | The short text describes the object sufficiently | ||
| 77 | No ID number found for business partner &1 | The short text describes the object sufficiently | ||
| 78 | Industry &1 not defined for industry key system &2 | The short text describes the object sufficiently | ||
| 79 | No business partner matching the search criteria found | The short text describes the object sufficiently | ||
| 80 | The where-used list does not have any reference | The short text describes the object sufficiently | ||
| 81 | Partner &1: industry &2 does not exist for industry key system &3 | The short text describes the object sufficiently | ||
| 82 | Text for transaction &1 does not exist in language &2 | The short text describes the object sufficiently | ||
| 83 | Business partner may not be changed because of status & | The short text describes the object sufficiently | ||
| 84 | Number &1 already exists for ID type &2 | The short text describes the object sufficiently | ||
| 85 | Industry &1 already exists for industry key system &2 | The short text describes the object sufficiently | ||
| 86 | Enter ID type | The short text describes the object sufficiently | ||
| 87 | Enter ID number | The short text describes the object sufficiently | ||
| 88 | Enter a valid ID type | The short text describes the object sufficiently | ||
| 89 | Entries included in request &1 | The short text describes the object sufficiently | ||
| 90 | No industries exist | The short text describes the object sufficiently | ||
| 91 | No industries exist for industry system & | The short text describes the object sufficiently | ||
| 92 | Industry &1 does not exist in industry system &2 | The short text describes the object sufficiently | ||
| 93 | There must be at least one basic node | The short text describes the object sufficiently | ||
| 94 | Nothing may refer to itself | The short text describes the object sufficiently | ||
| 95 | No business partner exists for internet user &1 | The short text describes the object sufficiently | ||
| 96 | Only &1 sections may be assigned | The short text describes the object sufficiently | ||
| 97 | Only &1 views may be assigned | The short text describes the object sufficiently | ||
| 98 | Identification type &1, idenfication number &2 already deleted | The short text describes the object sufficiently | ||
| 99 | Bank details &1 of business partner &2 already deleted | The short text describes the object sufficiently | ||
| 100 | Additional field groupings via criterion &1 exist | The short text describes the object sufficiently | ||
| 101 | Field grouping for field group &1 for &2 is: &3 | The short text describes the object sufficiently | ||
| 102 | No authorization for &1 of field group &2 | The short text describes the object sufficiently | ||
| 103 | No screen number stated for view &1 | The short text describes the object sufficiently | ||
| 104 | No program name stated for view &1 | The short text describes the object sufficiently | ||
| 105 | No screen number and program name stated for view &1 | The short text describes the object sufficiently | ||
| 106 | BDT object &1 in language &2 not available | The short text describes the object sufficiently | ||
| 107 | BDT object &1 not available | The short text describes the object sufficiently | ||
| 108 | Incorrect assignment of screen sequence via table TBZ6 | Space: object requires documentation | ||
| 109 | BP role &1 may not be deleted | Space: object requires documentation | ||
| 110 | Change type &1 of the BP role is not intended | Space: object requires documentation | ||
| 111 | There are no web addresses maintained for this address | The short text describes the object sufficiently | ||
| 112 | Not all URI addresses could be read | The short text describes the object sufficiently | ||
| 113 | You cannot enter a note for the communication type | Space: object requires documentation | ||
| 114 | Delete web address with the function 'Delete Row' & | The short text describes the object sufficiently | ||
| 115 | Invalid combination of address type, address number and person number | The short text describes the object sufficiently | ||
| 116 | Search string & contains more than & characters unequal '*' | The short text describes the object sufficiently | ||
| 117 | System lock error | Space: object requires documentation | ||
| 118 | Addresses with version & are not compared | The short text describes the object sufficiently | ||
| 119 | Regional data deleted without link to new values (object &) | The short text describes the object sufficiently | ||
| 120 | Parameters & and & are inconsistent | The short text describes the object sufficiently | ||
| 121 | Time zone & is invalid in country & (several options) | Space: object requires documentation | ||
| 122 | Invalid archiving structure: & | The short text describes the object sufficiently | ||
| 123 | Internal error - reference to AEService does not exist | The short text describes the object sufficiently | ||
| 124 | & hits in table ADR7 for system & client & | The short text describes the object sufficiently | ||
| 125 | Data records updated in table ADR7: & | The short text describes the object sufficiently | ||
| 126 | Report RS5ADRCL successfully run | The short text describes the object sufficiently | ||
| 127 | Only user addresses were updated | The short text describes the object sufficiently | ||
| 128 | Error in report RS5ADRCL | The short text describes the object sufficiently | ||
| 129 | Source system or source client not specified | The short text describes the object sufficiently | ||
| 130 | Test run, ADR7 records not updated: & | The short text describes the object sufficiently | ||
| 131 | Web address type '&' is invalid | The short text describes the object sufficiently | ||
| 132 | Specify a web address type | The short text describes the object sufficiently | ||
| 133 | Serious function module & call error | Space: object requires documentation | ||
| 134 | Address tables in client & not converted | Space: object requires documentation | ||
| 135 | Address tables in client & not converted | Space: object requires documentation | ||
| 136 | Address number: &, address handle: & | The short text describes the object sufficiently | ||
| 137 | Address number/handle: &, person number: &, SO_KEY: &, person handle: & | The short text describes the object sufficiently | ||
| 138 | Select a supplier | The short text describes the object sufficiently | ||
| 139 | Select an existing supplier | The short text describes the object sufficiently | ||
| 140 | Select an existing supplier of category organization | The short text describes the object sufficiently | ||
| 141 | Enter a value for field & | The short text describes the object sufficiently | ||
| 142 | Relationship cannot be processed due to missing partner | Space: object requires documentation |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in | 702 |