SAP ABAP Message Class VC (SD Customizing)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
VS0C (Package) Customizing R/3 Sales and Distribution master data
⤷
⤷
⤷
Attributes
| Message class | VC | |
| Short Description | SD Customizing | |
| Changed On | 20110908 | |
| Last Changed At | 172038 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | ******* 001-009 : hierarchical display of product hierarchy ******* | |||
| 2 | The product hierarchy is too long, please shorten it | |||
| 3 | Definition of hierarchy levels for the product hierarchy is not valid | |||
| 4 | Please enter a product hierarchy without empty groups | |||
| 5 | Please maintain the Group definition & (level: &) | |||
| 6 | Please select the entry to be copied | |||
| 7 | Select one entry only | |||
| 8 | First delete the dependent subgroups for hierarchy & | |||
| 9 | You must select a line for this function | |||
| 10 | Country & in shipping point & and country & in the address do not match | |||
| 11 | 'Item rel. for delivery' only allowed from item categories A and B | Space: object requires documentation | ||
| 12 | Check the country key for the address | Space: object requires documentation | ||
| 13 | There are no hierarchy nodes available for display! | Space: object requires documentation | ||
| 14 | Specify restrictions for nodes (or country) | Space: object requires documentation | ||
| 15 | ******** 015-099: Customer hierarchy ********************************** | |||
| 16 | You have no authorization to change hierarchy data | Space: object requires documentation | ||
| 17 | You have no authorization to display hierarchy data | Space: object requires documentation | ||
| 18 | ******* 021-099 : Customer hierarchy ***** | |||
| 19 | Sales area & & & is not defined for customer | |||
| 20 | Higher-level sales area & & & not defined for customer | |||
| 21 | Specify dependent and higher-level sales area | |||
| 22 | You only have authorization for displaying class & | |||
| 23 | You have no authorization for Classification & | |||
| 24 | Data can only be displayed because it is blocked by another user | |||
| 25 | System error blocking Table & | |||
| 26 | Data has been saved | |||
| 27 | Hierarchy type &: There are no active assignments for & | |||
| 28 | No errors were found in the assignments | |||
| 29 | Inconsistent sales areas cannot be assigned | |||
| 30 | Errors have been found in the assignments | |||
| 31 | No assignments have been changed | |||
| 32 | Error inserting Assignment & | |||
| 33 | Error deleting Assignment & | |||
| 34 | Hierarchy type is missing: Assignments cannot be made | |||
| 35 | Error updating Assignment & | |||
| 36 | Node cannot be deleted: invalid assignments would occur | |||
| 37 | Customer & for Sales area & & & does not exist | |||
| 38 | Validity date is missing: Hierarchy will be determined for today's date | |||
| 39 | Selection date lies in the past: Data will only be displayed | |||
| 40 | Customer & has not been created | |||
| 41 | Assignment of customer & to & is not defined | |||
| 42 | Sales area (VKORG/VTWEG/SPART) is incomplete | |||
| 43 | Sales area without customer number is not defined | |||
| 44 | Specify customer number | |||
| 45 | Assignment cannot be made: Higher-level customer & does not exist | |||
| 46 | Assignment of sales areas is not defined (THIOZ) | |||
| 47 | Assignment cannot be made: Higher-level sales area is incomplete | |||
| 48 | Valid-from date cannot lie in the past | |||
| 49 | Validity period is not allowed (From-date lies after the to-date) | |||
| 50 | The assignment is also active outside of the given time period | |||
| 51 | The assignment is already active in the given time period | |||
| 52 | Different higher-level assignments exist outside of the given time period | |||
| 53 | Incorrect assignments cannot be processed | |||
| 54 | Select hierarchy node | |||
| 55 | Assignment not possible: Customer & does not exist | |||
| 56 | Node & will be assigned to the same level | |||
| 57 | Select hierarchy header nodes for higher-level assignment | |||
| 58 | Selected sub-hierarchy contains all nodes and cannot be extended | |||
| 59 | Nodes cannot be added: unpermitted assignments would occur | |||
| 60 | Hierarchy contains no allowed alternative higher-level assignments | |||
| 61 | Higher-level node already maintained as a subordinate node | |||
| 62 | Assigned node is also a higher-level node | |||
| 63 | You cannot assign node to itself | |||
| 64 | Assignment has different attributes outside of the given time period | |||
| 65 | No authorization for displaying customers | |||
| 66 | No authorization for maintaining customers | |||
| 67 | No display authorization for Customer & in Sales area & & & | |||
| 68 | No maintenance authorization for Customer & in Sales area & & & | |||
| 69 | Partner determination error: Function not possible | |||
| 70 | Customer & is not created for Sales area & & & | |||
| 71 | There are no hierarchy nodes to be displayed | |||
| 72 | Function not possible: Maximum number of hierarchy steps (26) exceeded | |||
| 73 | Lowest hierarchy level reached (26): lower steps will be ignored | |||
| 74 | Hierarchy node cannot be removed as invalid assignments would arise | |||
| 75 | Selected hierarchy node is a header node: subhierarchy cannot be removed | |||
| 76 | Select incorrect hierarchy nodes | |||
| 77 | Pricing and rebate indicators updated | |||
| 78 | Attributes (pricing, rebate) are up-to-date for all assignments | |||
| 79 | Date cannot be changed (inconsistent validity periods) | |||
| 80 | Hierarchy type & is not defined | |||
| 81 | Node & is not active or not available for selection date | |||
| 82 | Node & is not available in the hierarchy | |||
| 83 | Hierarchy level & cannot be transferred due to inconsistencies | |||
| 84 | Hierarchy level assignment(s) updated | |||
| 85 | Hierarchy level assignment not updated or not updated for all points | |||
| 86 | Assignment not allowed: incorrect hierarchy structure assignment | |||
| 87 | 'Reassigning' can lead to inconsistencies in the hierarchy lvl assignmnt | |||
| 88 | Initial Date Limit(s): a new validity period has been proposed | |||
| 89 | Existing assignments for new nodes are being checked. | |||
| 90 | Node & & & & cannot be allocated, so it has not been selected | |||
| 91 | Assign. can only be displayed: transportation points & & & & not selected | |||
| 92 | Processing subtree for nodes & & & & not possible | |||
| 93 | Processing nodes & & & & not possible because not selected | |||
| 94 | Selection date is in the past: Please select new date | |||
| 95 | Error when posting the customer hierarchy data | |||
| 96 | Please specify selected nodes for node-specific display | |||
| 97 | Sales document types control | |||
| 98 | Saving is not necessary: no changes were made | |||
| 99 | Parameters for Document type & & have been changed | |||
| 100 | Document type & & created | |||
| 101 | Error & blocking &: & & | |||
| 102 | Document & already exists | |||
| 103 | Item category & changed | |||
| 104 | Error & changing &: & & | |||
| 105 | Error & planning &: & & | |||
| 106 | Error & deleting &: & & | |||
| 107 | New schedule line categories should begin with 'Z' | |||
| 108 | Combination not allowed | |||
| 109 | Item usage 'TEXT' is only allowed for item category group 'Blank' | |||
| 110 | Table & cannot be blocked | |||
| 111 | Document type & & deleted | |||
| 112 | Item category & & deleted | |||
| 113 | Schedule line category & & deleted | |||
| 114 | Default indicator for & & & & cannot be reset | |||
| 115 | The new default item category for & & & is & | |||
| 116 | The new default schedule line category for & & is & | |||
| 117 | Default indicator for & & & cannot be reset | |||
| 118 | The new default item category for & & is & | |||
| 119 | Deletion unnecessary: no assignments exist | |||
| 120 | Enter a usage for structure configuration for BOM explosion | |||
| 121 | Internal error creating assignment table: Item categ & (ret code &) | |||
| 122 | No changes made to item category assignments | |||
| 123 | Changed item category assignments saved | |||
| 124 | Partner group & does not contain any payers who cannot be changed | |||
| 125 | Entry & & & missing in table & | |||
| 126 | Item usage must be specified for item category group 'Blank' | |||
| 127 | Defaults for Item category & & changed | |||
| 128 | Customer-specific document types should begin with 'Z or Y' | |||
| 129 | Customer-specific item categories should begin with 'Z or Y' | |||
| 130 | Item category & already exists | |||
| 131 | Item category & & has been created | |||
| 132 | No changes made to the schedule line category assignments | |||
| 133 | Changes to schedule line category assignments have been saved | |||
| 134 | System blocking error for Table & | |||
| 135 | If a storage location is required, a batch check must be carried out | |||
| 136 | Related tables have not been transferred into the transfer order | Space: object requires documentation | ||
| 137 | The selected table entries have been transferred to correction | |||
| 138 | A condition type's access sequence in the pricing procedure is incorrect | |||
| 139 | Enter item category | Space: object requires documentation | ||
| 140 | An assignment for & already exists | |||
| 141 | Item category & is not allowed as a higher-level item category | |||
| 142 | Possible entries can only be displayed once the doc.type has been entered | |||
| 143 | Possible entries can only be displayed if a matl item category exists | |||
| 144 | Schedule line category & deleted from Table TVEP: please enter it again | |||
| 145 | Defaults for schedule line category & & changed | |||
| 146 | Schedule line category & & has been created | |||
| 147 | Schedule line category & already exists | |||
| 148 | Availability check without transfer of requirements is not allowed | |||
| 149 | Only condition types used for 'Pricing' are allowed | |||
| 150 | The entry & & cannot be deleted | |||
| 151 | No assignment possible as business data are not allowed | |||
| 152 | Deactivation not possible as billing plan is assigned | |||
| 153 | Billing plan only possible if business data active at item | |||
| 154 | The sales document indicator & is not allowed | Space: object requires documentation | ||
| 155 | Item categories 7, J, T and g are provided for deliveries | Space: object requires documentation | ||
| 156 | The date proposal is not allowed for delivery orders | Space: object requires documentation | ||
| 157 | Enter a condition for the individual items overall | Space: object requires documentation | ||
| 158 | The conditions must be different | Space: object requires documentation | ||
| 159 | Document type & is not allowed as an alternative sales document type | Space: object requires documentation | ||
| 160 | Alternative sales document type & is the same as current document type | Space: object requires documentation | ||
| 161 | No allowed alternative order types could be determined | Space: object requires documentation | ||
| 162 | The system status '&' is not available. | Space: object requires documentation | ||
| 163 | The user status '&' for the diagram '&' is not available. | Space: object requires documentation | ||
| 164 | Please maintain at first with number '&'. | Space: object requires documentation | ||
| 165 | Delivery item numbers could be too big | Space: object requires documentation | ||
| 166 | Enter schedule line category | Space: object requires documentation | ||
| 167 | Country and transportation zone copied from the address data | Space: object requires documentation | ||
| 168 | Address data maintenance only possible in the detail screen | Space: object requires documentation | ||
| 169 | External capacity planning is not allowed for item category &1 | The short text describes the object sufficiently | ||
| 170 | Text control | |||
| 171 | Please select a text object | |||
| 172 | You can only select one text object | |||
| 173 | System error occurred reading Internal table ( & ) | |||
| 174 | The entry already exists | |||
| 175 | Text determination procedure & has not been specified | |||
| 176 | Sales document type & does not exist | |||
| 177 | System error posting an internal table ( & ) | |||
| 178 | Access sequence & does not exist | |||
| 179 | Item category & does not exist | |||
| 180 | Delivery type & does not exist | |||
| 181 | Billing type & does not exist | |||
| 182 | Account group & does not exist | |||
| 183 | Text type & not yet created | Space: object requires documentation | ||
| 184 | The language must be clearly specified | |||
| 185 | Include & does not exist | |||
| 186 | No access sequences can be defined for text object '&' | Space: object requires documentation | ||
| 187 | Only text types can be defined for contact persons | |||
| 188 | No separate text procedures can be defined for text object '&' | Space: object requires documentation | ||
| 189 | Deletion not allowed (text ID & used in procedure &, client &) | Space: object requires documentation | ||
| 190 | Only special text objects are allowed | |||
| 191 | The language does not come from the partner function AG for MVKE | |||
| 192 | This combination (&,&) already exists | |||
| 193 | Language & is not defined | |||
| 194 | Partner function & not defined | |||
| 195 | This combination (&,&) is not defined | |||
| 196 | Access generated | |||
| 197 | Text determination procedure & already exists | |||
| 198 | Enter a number for the text determination procedure | |||
| 199 | Access sequence & already exists | |||
| 200 | Enter a number for the access sequence | |||
| 201 | Copying control module & does not exist | |||
| 202 | Text ID & in Procedure & & does not exist in TTXID | |||
| 203 | Text determination procedure & does not exist in Table & | |||
| 204 | Text ID & is already present in the text determination procedure | Space: object requires documentation | ||
| 205 | A unit must be assigned to the time period entered | |||
| 206 | Please maintain the unit only in the existing time period | |||
| 207 | Calendar ID and time period cannot be maintained at the same time | |||
| 208 | Calendar ID and time period cannot be maintained at the same time | |||
| 209 | The cancellation period can only be assigned a positive value | |||
| 210 | Deleting not allowed: the entry is being used in another position | |||
| 211 | There are no pop-up windows for billing document texts | |||
| 212 | The FORM routine & is not active or not available | |||
| 213 | 'Last of month' field and calendar ID cannot be maintained at one time | |||
| 214 | The rule for the contract start date refers to the contract start date | |||
| 215 | The rule for the contract end date refers to the contract end date | |||
| 216 | The cancellation base date cannot result from the contract end date | |||
| 217 | Please process table entry transfer manually | |||
| 218 | Text type & is not defined for text determination procedure & | Space: object requires documentation | ||
| 219 | No text edit control possible for order type & | Space: object requires documentation | ||
| 220 | Partner control | |||
| 221 | Please select a partner object | |||
| 222 | You have selected more than one object: please select only one | |||
| 223 | System error occurred reading Internal table ( & ) | |||
| 224 | The entry already exists | |||
| 225 | Partner determination procedure & does not exist | |||
| 226 | Sales document type & does not exist | |||
| 227 | System error posting an internal table ( & ) | |||
| 228 | Partner determ. procedure & already used in partner object & | |||
| 229 | Item category & does not exist | |||
| 230 | Transport into delivery system is only possible using & | |||
| 231 | Maintaining new partner functions in & is only possible in central functn | |||
| 232 | Please process table entry transfer manually | |||
| 233 | Partner function & has not been created | |||
| 234 | Partner function & cannot be used for partner procedures | |||
| 235 | Only customer partner functions can be defined as sources | |||
| 236 | Origin & is not provided for partner type & | Space: object requires documentation | ||
| 237 | Partner function does not exist in the customer partner determtn procdr | |||
| 238 | Origin & is not permitted for partner function & | Space: object requires documentation | ||
| 239 | Deletion not allowed: Function & is used elsewhere | |||
| 240 | Partner determination procedure & not defined for customer master | |||
| 241 | Partner determination procedure & not defined for sales document headers | |||
| 242 | Partner determination procedure & not defined for sales document items | |||
| 243 | Partner determination procedure & is not defined for deliveries | |||
| 244 | Partner determination procedure & not defined for billing header(s) | |||
| 245 | Partner determination procedure & is not defined for billing items | |||
| 246 | Partner determination procedure & is not defined for sales activities | |||
| 247 | Partner determination procedure & is not available for shipments | Space: object requires documentation | ||
| 248 | Shipping type & not yet created | Space: object requires documentation | ||
| 249 | Shipments must have a forwarding agent | Space: object requires documentation | ||
| 250 | Sales documents require a sold-to party that cannot be changed | |||
| 251 | Sales document items may not have a sold-to party | |||
| 252 | Deliveries require a ship-to party that cannot be changed | |||
| 253 | Billing items may not have a payer | |||
| 254 | A payer which cannot be changed is required for billing documents | |||
| 255 | 'Ship-To Party' is a mandatory partner function for outbound deliveries | Space: object requires documentation | ||
| 256 | Assignment only makes sense for customer functions | |||
| 257 | Another partner function has already been converted to & | |||
| 258 | Function & is not used in Procedure & | |||
| 259 | Function & is a higher-level function than Function & | |||
| 260 | Partner function & does not exist | |||
| 261 | Object & cannot be blocked: It will be displayed | |||
| 262 | Entries saved | |||
| 263 | Partner & is not defined | |||
| 264 | Please maintain the field 'Sequence' | Space: object requires documentation | ||
| 265 | Sort sequences of previously determined partners are inconsistent | Space: object requires documentation | ||
| 266 | Conditions, Pricing | |||
| 267 | Function & does not exist | |||
| 268 | Initialization error for View & | |||
| 269 | Maintenance error for view & | |||
| 270 | Both groups need to be defined | |||
| 271 | Procedure & requires two groups | |||
| 272 | Date function no available for partner type & | Space: object requires documentation | ||
| 273 | Accrual billing document type & does not exist | |||
| 274 | Only accrual billing document types w/o cancellation billing type allowed | |||
| 275 | Number range & is an internal number range | Space: object requires documentation | ||
| 276 | Number range & is not available | |||
| 277 | Number range & is an external number range | |||
| 278 | The most recently used billing date is & | |||
| 279 | Every date in the billing due list is less than & | |||
| 280 | Copy control, Graphics | |||
| 281 | Table & is blocked. It can only be displayed. | |||
| 282 | ABEND due to system error | |||
| 283 | Incompletion log | |||
| 284 | Procedure & does not exist | |||
| 285 | Procedure & already exists | |||
| 286 | Procedure & saved | |||
| 287 | Procedure & deleted | |||
| 288 | Procedure & referred to elsewhere | |||
| 289 | & | |||
| 290 | Procedure & is already assigned to item category & | |||
| 291 | Procedure & is already assigned to Schedule line category & | |||
| 292 | Procedure & is already assigned to Partner function & | |||
| 293 | Procedure & already has texts assigned to it | |||
| 294 | Procedure & is already assigned to Sales document type & | |||
| 295 | Procedure & will be deleted when you press 'Enter' | |||
| 296 | Select one object only for processing | |||
| 297 | Enter an incompletion procedure for editing | |||
| 298 | Incompletion procedure & is already defined for another object | |||
| 299 | Enter an incompletion procedure | |||
| 300 | Incompletion procedure & is not defined for sales document types | |||
| 301 | Incompletion procedure & is not defined for items | |||
| 302 | Incompletion procedure & is not defined for schedule lines | |||
| 303 | Changes will not be saved when you press 'Enter' | |||
| 304 | Procedure is still being used: Object & cannot be blocked | |||
| 305 | Procedure is still being used: usages will be deleted | |||
| 306 | Incompletion procedure & is not defined for sales activities | |||
| 307 | Status group & does not exist | |||
| 308 | * 450-499 Direct-Input Cusotmer | Space: object requires documentation | ||
| 309 | Currency & does not exist (TCURC) | Space: object requires documentation | ||
| 310 | Currency & is no longer valid (TCURC) | Space: object requires documentation | ||
| 311 | You do not have authorization for mass changes of currencies | Space: object requires documentation | ||
| 312 | No customer data found for the selection criteria | Space: object requires documentation | ||
| 313 | The new currency must differ from the old currency | Space: object requires documentation | ||
| 314 | The selected customers could not be blocked | Space: object requires documentation | ||
| 315 | Select customers and / or sales organizations | Space: object requires documentation | ||
| 316 | Conversion to currency & successfully completed | Space: object requires documentation | ||
| 317 | There are no data for currency conversion. | Space: object requires documentation | ||
| 318 | There is no master data for currency conversion available. | Space: object requires documentation | ||
| 319 | Currency conversion finished | Space: object requires documentation | ||
| 320 | For non-specified vendors it is only possible to have an old currency | Space: object requires documentation | ||
| 321 | Vendor & could not be blocked | Space: object requires documentation | ||
| 322 | You can only enter an old currency if the customer is not registered | Space: object requires documentation | ||
| 323 | Route definition/determination | |||
| 324 | Leg & and leg & are not compatible | |||
| 325 | Leg & is not defined | |||
| 326 | Leg & is already part of the route | |||
| 327 | Leg & already exists | |||
| 328 | Legs are not compatible - please correct | |||
| 329 | Warning: Incorrect leg saved in the route | |||
| 330 | Warning: No shipping conditions exist | |||
| 331 | Warning: No transportation groups exist | |||
| 332 | Shipping point & is not defined | |||
| 333 | Shipping point &2 cannot be used for plant &1 | Space: object requires documentation | ||
| 334 | Office of exit & is not specified | |||
| 335 | Please process table entry transfer manually | |||
| 336 | No routes found for the selection specified. | |||
| 337 | Maintain Table TFRM | |||
| 338 | Only group numbers up to 99 are allowed for routines in this class | |||
| 339 | Text module & could not be created | |||
| 340 | Place the cursor on a valid group number | |||
| 341 | There is no long text | |||
| 342 | All routines have been successfully activated | |||
| 343 | You can only delete deactivated routines | |||
| 344 | Include number & either does not exist or is not active | |||
| 345 | You can only make changes in client 0 | |||
| 346 | You do not have the authorization to create SAP standard routines | |||
| 347 | TADIR entry could not be created | |||
| 348 | Choose an entry | Space: object requires documentation | ||
| 349 | Text modules have been changed to document text modules | |||
| 350 | ******* 500-550 : EDI in SD ****************************************** | |||
| 351 | New key assignment for partner type & has not been maintained | |||
| 352 | Enter a customer number | |||
| 353 | Standard partner function & cannot be deleted | |||
| 354 | Partner function & is not defined for use in EDI | |||
| 355 | ************************ Contracts processing *************************** | |||
| 356 | Maintain either percentage rate or percentage rate table access | |||
| 357 | Please maintain condition type | |||
| 358 | Please maintain the baseline date rule for the price increase cycle | |||
| 359 | Please maintain the price increase cycle | |||
| 360 | ******************** Product hierarchy 700 - 720 ************************ | |||
| 361 | The product hierarchy structure has an unallowable number of levels | |||
| 362 | The template should contain only ' ' or separators other than ' ' | |||
| 363 | The template is smaller than a possible value entry | |||
| 364 | Node is followed by spaces: not allowed | |||
| 365 | Please create the preceding node first | |||
| 366 | A product hierarchy node cannot contain spaces | |||
| 367 | The node cannot be inserted | |||
| 368 | Please delete the succeeding node first | |||
| 369 | You have created too many levels (a maximum of 9 levels is allowed) | |||
| 370 | The data element must have the prefix 'PRODH' | |||
| 371 | The node includes editing mask characters | |||
| 372 | The mask is too long, layout does not look good | |||
| 373 | Deletions will be saved immediately to the data bank | |||
| 374 | The product hierarchy struture length is &, but must be & | |||
| 375 | Account assignment group &1 does not exist | |||
| 376 | ************* Scheduled shipping date 721 - 750 ************************* | |||
| 377 | The function is not possible without a number range | |||
| 378 | ************* Potential planning 751 - 770 ****************************** | |||
| 379 | Client & is not a competitor | |||
| 380 | Please maintain routine POTENTIAL_PROT_SET in program & | |||
| 381 | Select a valid line | |||
| 382 | ************* Repairs processing 771-820 ******************************** | Space: object requires documentation | ||
| 383 | You must also enter a procedure for the point in time | Space: object requires documentation | ||
| 384 | A repair indicator can only be assigned once per point in time | Space: object requires documentation | ||
| 385 | Repair indicator &2 is not required at time &1 | Space: object requires documentation | ||
| 386 | Procedure -&1- only possible manually | Space: object requires documentation | ||
| 387 | Manual flag only possible in combination with the report back indicator | Space: object requires documentation | ||
| 388 | No value help supported for this field | Space: object requires documentation | ||
| 389 | Access sequence exists for text & in text determination procedure & | Space: object requires documentation | ||
| 390 | Text edit control does not work for & ! | Space: object requires documentation | ||
| 391 | Pricing date proposal C only needed if contract data are allowed | Space: object requires documentation | ||
| 392 | Valid from date is proposed from the contract data | Space: object requires documentation | ||
| 393 | ****** _Reference det. for consumer master 821 - 850 ****************** | Space: object requires documentation | ||
| 394 | No company code exists for sales area &1 &2 &3 | Space: object requires documentation | ||
| 395 | Problems when executing out dialog boxes | Space: object requires documentation | ||
| 396 | Problems when reading the sales area data | Space: object requires documentation | ||
| 397 | Problems when adding a reference customer to the company code | Space: object requires documentation | ||
| 398 | Problems when reading the customer master data | Space: object requires documentation | ||
| 399 | The reference customer & cannot be a consumer | Space: object requires documentation | ||
| 400 | Company code & does not exist | Space: object requires documentation | ||
| 401 | Company code & does not exist with reference customer & | Space: object requires documentation | ||
| 402 | Problems when reading the sales area data | Space: object requires documentation | ||
| 403 | No reference customer maintained | Space: object requires documentation | ||
| 404 | Reference customer &2 already exists for company code &1 | Space: object requires documentation | ||
| 405 | Enter the sales organization | Space: object requires documentation | ||
| 406 | Enter the distribution channel | Space: object requires documentation | ||
| 407 | Customer &1 for sls org. &2 dist. chnl &3 division &4 not created | Space: object requires documentation | ||
| 408 | Problems deleting the sales area data | Space: object requires documentation | ||
| 409 | Problems deleting the company code data | Space: object requires documentation | ||
| 410 | Reference customer is not current reference customer ->not deleted | Space: object requires documentation | ||
| 411 | Problems inserting the reference customers for the sales area | Space: object requires documentation | ||
| 412 | At least one sales area should be maintained for reference customer & | Space: object requires documentation | ||
| 413 | At least one company code must be maintained for reference customer & | Space: object requires documentation | ||
| 414 | Reference customer & does not exist | Space: object requires documentation | ||
| 415 | Reference customer & deleted | Space: object requires documentation | ||
| 416 | Reference customer & created | Space: object requires documentation | ||
| 417 | A reference customer has been created | Space: object requires documentation | ||
| 418 | Reference customer & will not be deleted | Space: object requires documentation | ||
| 419 | & can not be used as a reference customer | Space: object requires documentation | ||
| 420 | Transaction VOTX is outdated. Use VOTXN instead | Space: object requires documentation | ||
| 421 | Text ID & already exists. Enter a new text ID | Space: object requires documentation | ||
| 422 | Run number & already exists. Enter a new run number | Space: object requires documentation | ||
| 423 | Enter both run number and text ID | Space: object requires documentation | ||
| 424 | First enter a run number and a text ID | Space: object requires documentation | ||
| 425 | Enter a text ID | Space: object requires documentation | ||
| 426 | Enter a run number | Space: object requires documentation |
History
| Last changed on/by | 20110908 | SAP | |
| SAP Release Created in |