SAP ABAP Message Class USMD6 (Messages for Data Transfer)
Basic Data
Hierarchy
☛
MDG_FND (Software Component) MDG Foundation
⤷
CA-MDG-AF (Application Component) Application Framework
⤷
USMD6 (Package) Replication (Upload/Download, Monitor, ...)
⤷
⤷
Attributes
| Message class | USMD6 | |
| Short Description | Messages for Data Transfer | |
| Changed On | 20131127 | |
| Last Changed At | 184253 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Program error | The short text describes the object sufficiently | ||
| 2 | Specify a data model | The short text describes the object sufficiently | ||
| 3 | Data model &1 is not active | The short text describes the object sufficiently | ||
| 4 | Specify an entity type | The short text describes the object sufficiently | ||
| 5 | Upload of hierarchies currently not supported | The short text describes the object sufficiently | ||
| 6 | Entity type &2 not defined for data model &1 | The short text describes the object sufficiently | ||
| 7 | Data model &1: Define lower-level entity type &3 for &2 | The short text describes the object sufficiently | ||
| 8 | Data model &1: Entity type &2 has unsuitable storage and use type | The short text describes the object sufficiently | ||
| 9 | Data model &1 and data transfer variant &2 do not exist | The short text describes the object sufficiently | ||
| 10 | Data model &1, transfer &2, variant &3: Specify file system | The short text describes the object sufficiently | ||
| 11 | Data model &1, transfer &2, variant &3: Specify separator | The short text describes the object sufficiently | ||
| 12 | Variant &1: Attribute &2 is not a valid field | The short text describes the object sufficiently | ||
| 13 | Data transfer &1 already exists | The short text describes the object sufficiently | ||
| 14 | Data transfer &1 cannot be created | The short text describes the object sufficiently | ||
| 15 | Download to &1 not executed because of error or termination | The short text describes the object sufficiently | ||
| 16 | Error in output conversion of field &1: value &2, row &3 | The short text describes the object sufficiently | ||
| 17 | Error while calling BAdI USMD_DATA_TRANSFER: &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 18 | Logical file &1 not found | The short text describes the object sufficiently | ||
| 19 | File &1 could not be opened; message: &2 | The short text describes the object sufficiently | ||
| 20 | Error in input conversion of field &1: value &2 | The short text describes the object sufficiently | ||
| 21 | User &2 is using variant &1 | Space: object requires documentation | ||
| 22 | Variant &1 for the data transfer of data model &2 already exists | The short text describes the object sufficiently | ||
| 23 | Technical settings do not exist for data model &1, variant &2 | The short text describes the object sufficiently | ||
| 24 | Key field &1 missing in transfer structure for download or upload | Space: object requires documentation | ||
| 25 | Edition &1 is already released | The short text describes the object sufficiently | ||
| 26 | Entity &1 is located in change request &2 | Space: object requires documentation | ||
| 27 | Change request is missing | The short text describes the object sufficiently | ||
| 28 | &2 not contained in object list of change request &1 | Space: object requires documentation | ||
| 29 | Edition &1 does not exist (for data model &2) | Space: object requires documentation | ||
| 30 | Entity type &2 not contained in edition type &1 | Space: object requires documentation | ||
| 31 | Error while writing to application Log | The short text describes the object sufficiently | ||
| 32 | Error while saving application Log | The short text describes the object sufficiently | ||
| 33 | Edition &1 is invalid or cannot be used | The short text describes the object sufficiently | ||
| 34 | Field &1: Value &2 has an invalid internal format | The short text describes the object sufficiently | ||
| 35 | Name &1 of variant is invalid | Space: object requires documentation | ||
| 36 | Name for &1 is too long and will be cut off; value in file: &2 | Space: object requires documentation | ||
| 37 | &1: Data record with key &2 exists more than once in the file | The short text describes the object sufficiently | ||
| 38 | &1: Part of the key &2 contains an initialized value | The short text describes the object sufficiently | ||
| 39 | Data model &1, entity type &2: No hierarchy agreed upon | The short text describes the object sufficiently | ||
| 40 | Delta mode not supported for entity types &1 | Space: object requires documentation | ||
| 41 | Selection condition &1 is being processed by user &2 | The short text describes the object sufficiently | ||
| 42 | Download started: data model &1, variant &2 | The short text describes the object sufficiently | ||
| 43 | Download finished: data model &1, variant &2 | The short text describes the object sufficiently | ||
| 44 | BAdI called for data model &1, variant &2 | The short text describes the object sufficiently | ||
| 45 | &1 data rows transferred | The short text describes the object sufficiently | ||
| 46 | Upload started: data model &1, variant &2 | The short text describes the object sufficiently | ||
| 47 | Upload finished: data model &1, variant &2 | The short text describes the object sufficiently | ||
| 48 | There is no suitable change request | Space: object requires documentation | ||
| 49 | An unsuitable change request &1 is being used | The short text describes the object sufficiently | ||
| 50 | Upload carried out | The short text describes the object sufficiently | ||
| 51 | Field &1 of transfer structure is unknown | The short text describes the object sufficiently | ||
| 52 | Download in delta mode not possible for entity type &1 | Space: object requires documentation | ||
| 53 | Data model &1: Variant &2 does not exist | The short text describes the object sufficiently | ||
| 54 | Data model &1, variant &2: File name &3 is blank or invalid | The short text describes the object sufficiently | ||
| 55 | Data model &1, variant &2: Error while openning file &3 | The short text describes the object sufficiently | ||
| 56 | Data model &1, variant &2: Error while writing to file &3 | The short text describes the object sufficiently | ||
| 57 | Error: &1, &2, &3, &4 | The short text describes the object sufficiently | ||
| 58 | Data model &1, variant &2: Logical file name &3 is invalid | The short text describes the object sufficiently | ||
| 59 | Error while creating transport request | The short text describes the object sufficiently | ||
| 60 | Transfer structure must contain the language key field (LANGU) | Space: object requires documentation | ||
| 61 | Selection &3 for data model &1 and entity type &2 is invalid | The short text describes the object sufficiently | ||
| 62 | Field name &1 of the selection is invalid | The short text describes the object sufficiently | ||
| 63 | Value &2 is invalid for field name &1 | The short text describes the object sufficiently | ||
| 64 | Field name &1: From-value &2 is less than To-value &3 | The short text describes the object sufficiently | ||
| 65 | Specify name of variant | The short text describes the object sufficiently | ||
| 66 | Variant &1 saved | The short text describes the object sufficiently | ||
| 67 | Value &1 for &2 is not permitted | The short text describes the object sufficiently | ||
| 68 | Change request &1 cannot be used | Space: object requires documentation | ||
| 69 | Comment character &1 poses problems | Space: object requires documentation | ||
| 70 | Select at least one attribute | The short text describes the object sufficiently | ||
| 71 | No file was specified | The short text describes the object sufficiently | ||
| 72 | Select one row only for this action | The short text describes the object sufficiently | ||
| 73 | Conversion error | The short text describes the object sufficiently | ||
| 74 | File &1 cannot be opened | The short text describes the object sufficiently | ||
| 75 | Development class &1 is invalid | The short text describes the object sufficiently | ||
| 76 | Objects of development class &1 cannot be transported | The short text describes the object sufficiently | ||
| 77 | System properties cannot be determined | The short text describes the object sufficiently | ||
| 78 | Changes are not allwed according to system setting (SCC4) | The short text describes the object sufficiently | ||
| 79 | Client cannot be changed | The short text describes the object sufficiently | ||
| 80 | Data model &1: Create/change/delete master data has been started | The short text describes the object sufficiently | ||
| 81 | File is ready for download | The short text describes the object sufficiently | ||
| 82 | File uploaded | The short text describes the object sufficiently | ||
| 83 | Variant &1 deleted | The short text describes the object sufficiently | ||
| 84 | Data model &1: Create/change/delete master data is finished | The short text describes the object sufficiently | ||
| 85 | Writing will not take place; see error messages | The short text describes the object sufficiently | ||
| 86 | &1: Entity type &2: Writing of master data finished with &3 errors | The short text describes the object sufficiently | ||
| 87 | Upload will not take place because of errors | The short text describes the object sufficiently | ||
| 88 | Data record is not located in the data slice of edition &1 | The short text describes the object sufficiently | ||
| 89 | Field &1 of transfer structure used more than once | Space: object requires documentation | ||
| 90 | Could not determine higher-level node using the data row | The short text describes the object sufficiently | ||
| 91 | Hierarchy node &1 is located in change request &2 | The short text describes the object sufficiently | ||
| 92 | Different hierarchy versions &2 and &1 being used | Space: object requires documentation | ||
| 93 | Different hierarchies &2 and &1 being used | Space: object requires documentation | ||
| 94 | File to be uploaded does not contain any data records | The short text describes the object sufficiently | ||
| 95 | Node &1 cannot be included in a change request | The short text describes the object sufficiently | ||
| 96 | Higher-level node &1 cannot be included in change request | The short text describes the object sufficiently | ||
| 97 | Only SAP defines structures generated with view cluster VC_USMD005 | Space: object requires documentation | ||
| 98 | Hierarchy version must be further restricted | Space: object requires documentation | ||
| 99 | Enter the required fields | The short text describes the object sufficiently | ||
| 100 | Data element &1 does not exist | The short text describes the object sufficiently | ||
| 101 | * Messages 100 - 200 reserved for Distribution Monitor | The short text describes the object sufficiently | ||
| 102 | Edition &1 does not exist with master data package &2, target system &3 | The short text describes the object sufficiently | ||
| 103 | Distributions with status &1 cannot be confirmed | Space: object requires documentation | ||
| 104 | Distributions with status &1 cannot be skipped | Space: object requires documentation | ||
| 105 | Edition &1 does not exist | The short text describes the object sufficiently | ||
| 106 | Edition &1 already transmitted to distribution | The short text describes the object sufficiently | ||
| 107 | Class &1 does not exist | The short text describes the object sufficiently | ||
| 108 | Interface &2 in class &1 is not implemented | The short text describes the object sufficiently | ||
| 109 | No master data packages are created in Customizing | The short text describes the object sufficiently | ||
| 110 | Definition of master data package &1 in Customizing is incomplete | The short text describes the object sufficiently | ||
| 111 | Select one row only for each data distribution | The short text describes the object sufficiently | ||
| 112 | Select a row | The short text describes the object sufficiently | ||
| 113 | No application log exists for distribution step &1 | The short text describes the object sufficiently | ||
| 114 | Specify a required input field &1 | The short text describes the object sufficiently | ||
| 115 | Master data package &1 does not exist in edition &2 | The short text describes the object sufficiently | ||
| 116 | The specified logical system is not assigned to master data package &1 | The short text describes the object sufficiently | ||
| 117 | No distribution service assigned to master data package &1, step &2 | The short text describes the object sufficiently | ||
| 118 | Distribution of master data to logical system &1 started | The short text describes the object sufficiently | ||
| 119 | Distribution system &1 is new and not defined in the SLD | The short text describes the object sufficiently | ||
| 120 | No authorization to distribute master data package &1 to log. system &2 | The short text describes the object sufficiently | ||
| 121 | Distribution service still used in master data package &1 | The short text describes the object sufficiently | ||
| 122 | Deleted master data package still assigned to system &1 | The short text describes the object sufficiently | ||
| 123 | Entity type &1 not assigned to model &2 | The short text describes the object sufficiently | ||
| 124 | Master data package in status &1 cannot be distributed | The short text describes the object sufficiently | ||
| 125 | Mapping for entity type &1 is not specified | The short text describes the object sufficiently | ||
| 126 | For downloads, class CL_USMD_TRANSF_DT must be assigned to distribution | The short text describes the object sufficiently | ||
| 127 | For downloads, class CL_USMD_TRANSF_DT is assigned to distribution | The short text describes the object sufficiently | ||
| 128 | Edition &1 not yet passed to distribution | The short text describes the object sufficiently | ||
| 129 | &1 entries modified for Customizing | The short text describes the object sufficiently | ||
| 130 | Data is in accordance with Customizing settings | The short text describes the object sufficiently | ||
| 131 | Distibution step 0 is invalid | The short text describes the object sufficiently | ||
| 132 | Initialized entry not permitted | The short text describes the object sufficiently | ||
| 133 | Field &1 is not contained in table &2 | The short text describes the object sufficiently | ||
| 134 | No entries found in check table for entity type &1 | The short text describes the object sufficiently | ||
| 135 | RFC destination &1 does not exist | The short text describes the object sufficiently | ||
| 136 | Entity type &1, check table: Different number of key fields | The short text describes the object sufficiently | ||
| 137 | RFC communication error | The short text describes the object sufficiently | ||
| 138 | Data for entity type &1 has been imported | The short text describes the object sufficiently | ||
| 139 | Entity type &1: Import using domain fixed values is not possible | The short text describes the object sufficiently | ||
| 140 | Data element 'MANDT' is not allowed | The short text describes the object sufficiently | ||
| 141 | Entity type &2: Field length of source data element &1 is too short | Space: object requires documentation | ||
| 142 | Enter an edition or a change request for entity type &1 | The short text describes the object sufficiently | ||
| 143 | Error when calling BAdI USMD_DATA_TRANSFER_UPL: &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 144 | &1: Key &2 does not exist in master data table | The short text describes the object sufficiently | ||
| 145 | Field &1: Value &4 is too long: (&2 is greater than &3) | Space: object requires documentation | ||
| 146 | Upload cannot be performed because of errors | The short text describes the object sufficiently | ||
| 147 | Either the hierarchy to be uploaded or the fragment contains cycles | The short text describes the object sufficiently | ||
| 148 | A lower-level node could not be determined from the data row | The short text describes the object sufficiently | ||
| 149 | Specify a data element for all entity types to be imported | Space: object requires documentation | ||
| 150 | You cannot use this application with enhancement package 5 | The short text describes the object sufficiently | ||
| 151 | Instance &2 of Entitytype &1 is a hierarchynode: Deletion not possible | Space: object requires documentation | ||
| 152 | * Messages 300 - 399 reserved for Upload/Download | The short text describes the object sufficiently | ||
| 153 | Select only fields that are under the same higher-level node | The short text describes the object sufficiently | ||
| 154 | Select only one node as the target node | The short text describes the object sufficiently | ||
| 155 | Node &1 cannot be moved | The short text describes the object sufficiently | ||
| 156 | &1 can be moved only under &2 | The short text describes the object sufficiently | ||
| 157 | &1 can be placed only under &2 because it was previously under &3 | The short text describes the object sufficiently | ||
| 158 | In hierarchies, fields cannot be placed directly under &1 | Space: object requires documentation | ||
| 159 | &1 is not a hierarchy attribute | Space: object requires documentation | ||
| 160 | &1 cannot be moved further upward | The short text describes the object sufficiently | ||
| 161 | &1 cannot be moved further downward | The short text describes the object sufficiently | ||
| 162 | Data transfer variant &1 does not exist | The short text describes the object sufficiently | ||
| 163 | Only a fragment of the hierarchy will be uploaded | Space: object requires documentation | ||
| 164 | Action canceled by user | The short text describes the object sufficiently | ||
| 165 | Specify fields for the higher-level node and lower-level node | Space: object requires documentation | ||
| 166 | Field &1 contains invalid characters &2 | The short text describes the object sufficiently | ||
| 167 | Edge with higher-level node &1 and lower node &2 will not be output | Space: object requires documentation | ||
| 168 | Cannot determine hierarchy name; an entry for &1 is missing | Space: object requires documentation | ||
| 169 | Field &1: Value &2 is not the same as &3 | Space: object requires documentation | ||
| 170 | Download of FIN-MDM Entities using DRD is not supported | The short text describes the object sufficiently | ||
| 171 | &1 more error messages are no longer being displayed | Space: object requires documentation | ||
| 172 | More errors exist: work area &1, number &2 | The short text describes the object sufficiently | ||
| 173 | Application &1 has no data model | The short text describes the object sufficiently | ||
| 174 | Node cannot be derived because fields &1 and &2 are filled | Space: object requires documentation | ||
| 175 | Selection condition does not overlap the data slice of the edition | Space: object requires documentation | ||
| 176 | Selection of application server with physical file name not supported | The short text describes the object sufficiently | ||
| 177 | Field &1 will not be uploaded because it is not governed | Space: object requires documentation | ||
| 178 | File download does not support parallel processing | The short text describes the object sufficiently | ||
| 179 | Application &1 uses business object &2 with different model &3 | Space: object requires documentation | ||
| 180 | Application &1 uses business object &2 with incompatible entity type &3 | The short text describes the object sufficiently | ||
| 181 | Transfer variant &1 is defined for incompatible entity type &2 | The short text describes the object sufficiently | ||
| 182 | System settings do not permit a transport | The short text describes the object sufficiently | ||
| 183 | Upload mode &1 cannot be used for entity &2 | Space: object requires documentation | ||
| 184 | The maximum row length of 4096 characters is exceeded in row &1 | The short text describes the object sufficiently | ||
| 185 | &1 is chosen as header field, but the selection is not single value | Space: object requires documentation | ||
| 186 | * Messages 500 - 899 reserved for eSOA | |||
| 187 | * Messages 500 - 899 reserved for SOA | The short text describes the object sufficiently | ||
| 188 | Service processing &1 for pkg. &2, step &3, target system &4 started | The short text describes the object sufficiently | ||
| 189 | Data selection for package &1, step &2 successfully finished | The short text describes the object sufficiently | ||
| 190 | Field mapping for package &1, step &2 successfully finished | The short text describes the object sufficiently | ||
| 191 | BAdI calls for package &1, step &2 started | The short text describes the object sufficiently | ||
| 192 | Proxy calls for package &1, step &2, service class &3 started | The short text describes the object sufficiently | ||
| 193 | Message for chart of accounts &1 sent to outbound proxy | The short text describes the object sufficiently | ||
| 194 | Error in call of outbound proxy for service &1, chart of accounts &2 | The short text describes the object sufficiently | ||
| 195 | Initialized status entries created for package &1, step &2, system &3 | The short text describes the object sufficiently | ||
| 196 | Error during SMT mapping &1, mapping step &2, target structure &3 | The short text describes the object sufficiently | ||
| 197 | &1 messages sent for package &2, step &3, system &4 | The short text describes the object sufficiently | ||
| 198 | Error during initial status update for package &1, step &2, system &3 | The short text describes the object sufficiently | ||
| 199 | Error during update of status tables due to competing access | The short text describes the object sufficiently | ||
| 200 | No status entry found for message with GUID &1 | The short text describes the object sufficiently | ||
| 201 | Status entry of message &1 has incorrect target system (&2 instead of &3) | The short text describes the object sufficiently | ||
| 202 | Status entry of message &1 has invalid reference GUID (&2 instead of &3) | The short text describes the object sufficiently | ||
| 203 | Status entry of message &1 has incorrect status (&2 instead of &3) | The short text describes the object sufficiently | ||
| 204 | Entry of a From-edition (&1) not possible when distribution complete | The short text describes the object sufficiently | ||
| 205 | Period information cannot be derived from editions &1 and &2 | The short text describes the object sufficiently | ||
| 206 | Error while creating instance of SMT mapping &1, mapping step &2 | Space: object requires documentation | ||
| 207 | Error in status update of messages for edition &1, package &2, system &3 | The short text describes the object sufficiently | ||
| 208 | Error in update of aggregate status f. edtn &1, pkg &2, sys &3, step &4 | The short text describes the object sufficiently | ||
| 209 | Customizing error: No SMT mapping created for data model &1 | The short text describes the object sufficiently | ||
| 210 | A maximum of 10 characters is allowed for accounts (entity type &1) | Space: object requires documentation | ||
| 211 | Bulk message sent to outbound proxy | The short text describes the object sufficiently | ||
| 212 | Error while calling outbound proxy for service &1 | The short text describes the object sufficiently | ||
| 213 | Bulk message contains &1 individual messages | The short text describes the object sufficiently | ||
| 214 | Processing terminated (error in data selection for package &1, step &2) | The short text describes the object sufficiently | ||
| 215 | BAdI call(s) for package &1, step &2, chart of accounts &3 started | The short text describes the object sufficiently | ||
| 216 | BAdI call(s) for package &1, step &2, fin. reporting structure &3 started | The short text describes the object sufficiently | ||
| 217 | Error while reading message &1 (edition &2, package &3, system &4) | The short text describes the object sufficiently | ||
| 218 | &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 219 | &1 &2 &3 | The short text describes the object sufficiently | ||
| 220 | &1 &2 | The short text describes the object sufficiently | ||
| 221 | Message for financial reporting structure &1 sent to outbound proxy | The short text describes the object sufficiently | ||
| 222 | Error during call to outbound proxy for service &1, fin.rep.structure &2 | The short text describes the object sufficiently | ||
| 223 | Error during status update for edition &2, package &2, system &3, step &4 | The short text describes the object sufficiently | ||
| 224 | Blank bulk message in package &1, step &2; processing terminated | The short text describes the object sufficiently | ||
| 225 | No customer BAdI implemented for service processing &1 | The short text describes the object sufficiently | ||
| 226 | No data found for package &1, step &2; processing &3 terminated | The short text describes the object sufficiently | ||
| 227 | Service processing &1 started | The short text describes the object sufficiently | ||
| 228 | Inbound mapping for service &1 started | The short text describes the object sufficiently | ||
| 229 | Inbound mapping for service &1 ended | The short text describes the object sufficiently | ||
| 230 | Error in inbound mapping for service &1 | The short text describes the object sufficiently | ||
| 231 | Status update for service &1, message &2 started | The short text describes the object sufficiently | ||
| 232 | Error in status update for message &1 (edition &2, package &3, system &4) | The short text describes the object sufficiently | ||
| 233 | BAdI call for service processing &1 started (if BAdI implemented) | The short text describes the object sufficiently | ||
| 234 | No SMT mapping found for entity type &1 in package &2, step &3 | Space: object requires documentation | ||
| 235 | Updating status of distrib. monitor (edtn &1, pkg. &2, sys. &3, step &4) | The short text describes the object sufficiently | ||
| 236 | Mandatory attribute "Category_Code" is blank for &1 | Space: object requires documentation | ||
| 237 | No hierarchy-bearing entity type found for distribution of package &1 | Space: object requires documentation | ||
| 238 | &1 | The short text describes the object sufficiently | ||
| 239 | Starting distribution step &1 of master data package &2 (edtn &3, sys.&4) | The short text describes the object sufficiently | ||
| 240 | No authorization for distribution of master data package &1 to system &2 | Space: object requires documentation | ||
| 241 | Consolidation area is still blank in replication message for &1 | Space: object requires documentation | ||
| 242 | Status successfully updated for message &1 (edtn &2, package &3, sys. &4) | The short text describes the object sufficiently | ||
| 243 | Delta distribution not possible for entity type &1 | Space: object requires documentation | ||
| 244 | Updating status of distribution monitor (edt.&1, app.&2, sys.&3, step &4) | The short text describes the object sufficiently | ||
| 245 | Error while updating aggregate status f. edt.&1, app.&2, sys.&3, step &4 | The short text describes the object sufficiently | ||
| 246 | Error while updating status of notification f. edition &1, app.&2, sys.&3 | The short text describes the object sufficiently | ||
| 247 | Errors occured during the distribution; check the appropriate log | The short text describes the object sufficiently | ||
| 248 | No application has been created in Customizing | The short text describes the object sufficiently | ||
| 249 | This edition contains no data to be distributed | The short text describes the object sufficiently | ||
| 250 | Master data package &1 does not exist in Customizing | The short text describes the object sufficiently | ||
| 251 | No distribution step assigned to master data package &1 | The short text describes the object sufficiently | ||
| 252 | No target system assigned to master data package &1 in Customizing | The short text describes the object sufficiently | ||
| 253 | Master data package &1 has no distribution step &2 in Customizing | The short text describes the object sufficiently | ||
| 254 | Application &1 does not exist | The short text describes the object sufficiently | ||
| 255 | Application &2 does not have a distribution step &1 | The short text describes the object sufficiently | ||
| 256 | Outbound implementation &1 does not exist | The short text describes the object sufficiently | ||
| 257 | Business system &1 does not exist | The short text describes the object sufficiently | ||
| 258 | Field name &1 no longer exists in active data model &2 | The short text describes the object sufficiently | ||
| 259 | No object type code assigned to entity type &1 of data model &2 | The short text describes the object sufficiently | ||
| 260 | Change request &1 does not contain objects to be replicated | Space: object requires documentation | ||
| 261 | Change request &1, OTC &2: Error &3 while generating structure | The short text describes the object sufficiently | ||
| 262 | Change request &1 cannot be directly replicated | The short text describes the object sufficiently | ||
| 263 | You are not authorized to distribute all master data packages | Space: object requires documentation | ||
| 264 | Replication not configured with data model &1 | The short text describes the object sufficiently | ||
| 265 | &1 &2 already assigned to change request &3 with edition &4 | The short text describes the object sufficiently |
History
| Last changed on/by | 20131127 | SAP | |
| SAP Release Created in | 604 |