USMD6 - Nachrichten Datentransfer
The following messages are stored in message class USMD6: Nachrichten Datentransfer.
It is part of development package USMD6 in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Replication (Upload/Download, Monitor, ...)".
It is part of development package USMD6 in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Replication (Upload/Download, Monitor, ...)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Program error |
| 001 | Specify a data model |
| 002 | Data model &1 is not active |
| 003 | Specify an entity type |
| 004 | Upload of hierarchies currently not supported |
| 005 | Entity type &2 not defined for data model &1 |
| 006 | Data model &1: Define lower-level entity type &3 for &2 |
| 007 | Data model &1: Entity type &2 has unsuitable storage and use type |
| 008 | Data model &1 and data transfer variant &2 do not exist |
| 009 | Data model &1, transfer &2, variant &3: Specify file system |
| 010 | Data model &1, transfer &2, variant &3: Specify separator |
| 011 | Variant &1: Attribute &2 is not a valid field |
| 012 | Data transfer &1 already exists |
| 013 | Data transfer &1 cannot be created |
| 014 | Download to &1 not executed because of error or termination |
| 015 | Error in output conversion of field &1: value &2, row &3 |
| 016 | Error while calling BAdI USMD_DATA_TRANSFER: &1 &2 &3 &4 |
| 017 | Logical file &1 not found |
| 018 | File &1 could not be opened; message: &2 |
| 019 | Error in input conversion of field &1: value &2 |
| 020 | User &2 is using variant &1 |
| 021 | Variant &1 for the data transfer of data model &2 already exists |
| 022 | Technical settings do not exist for data model &1, variant &2 |
| 023 | Key field &1 missing in transfer structure for download or upload |
| 024 | Edition &1 is already released |
| 025 | Entity &1 is located in change request &2 |
| 026 | Change request is missing |
| 027 | &2 not contained in object list of change request &1 |
| 028 | Edition &1 does not exist (for data model &2) |
| 029 | Entity type &2 not contained in edition type &1 |
| 030 | Error while writing to application Log |
| 031 | Error while saving application Log |
| 032 | Edition &1 is invalid or cannot be used |
| 033 | Field &1: Value &2 has an invalid internal format |
| 034 | Name &1 of variant is invalid |
| 035 | Name for &1 is too long and will be cut off; value in file: &2 |
| 036 | &1: Data record with key &2 exists more than once in the file |
| 037 | &1: Part of the key &2 contains an initialized value |
| 038 | Data model &1, entity type &2: No hierarchy agreed upon |
| 039 | Delta mode not supported for entity types &1 |
| 040 | Selection condition &1 is being processed by user &2 |
| 041 | Download started: data model &1, variant &2 |
| 042 | Download finished: data model &1, variant &2 |
| 043 | BAdI called for data model &1, variant &2 |
| 044 | &1 data rows transferred |
| 045 | Upload started: data model &1, variant &2 |
| 046 | Upload finished: data model &1, variant &2 |
| 047 | There is no suitable change request |
| 048 | An unsuitable change request &1 is being used |
| 049 | Upload carried out |
| 050 | Field &1 of transfer structure is unknown |
| 051 | Download in delta mode not possible for entity type &1 |
| 052 | Data model &1: Variant &2 does not exist |
| 053 | Data model &1, variant &2: File name &3 is blank or invalid |
| 054 | Data model &1, variant &2: Error while openning file &3 |
| 055 | Data model &1, variant &2: Error while writing to file &3 |
| 056 | Error: &1, &2, &3, &4 |
| 057 | Data model &1, variant &2: Logical file name &3 is invalid |
| 058 | Error while creating transport request |
| 059 | Transfer structure must contain the language key field (LANGU) |
| 060 | Selection &3 for data model &1 and entity type &2 is invalid |
| 061 | Field name &1 of the selection is invalid |
| 062 | Value &2 is invalid for field name &1 |
| 063 | Field name &1: From-value &2 is less than To-value &3 |
| 064 | Specify name of variant |
| 065 | Variant &1 saved |
| 066 | Value &1 for &2 is not permitted |
| 067 | Change request &1 cannot be used |
| 068 | Comment character &1 poses problems |
| 069 | Select at least one attribute |
| 070 | No file was specified |
| 071 | Select one row only for this action |
| 072 | Conversion error |
| 073 | File &1 cannot be opened |
| 074 | Development class &1 is invalid |
| 075 | Objects of development class &1 cannot be transported |
| 076 | System properties cannot be determined |
| 077 | Changes are not allwed according to system setting (SCC4) |
| 078 | Client cannot be changed |
| 079 | Data model &1: Create/change/delete master data has been started |
| 080 | File is ready for download |
| 081 | File uploaded |
| 082 | Variant &1 deleted |
| 083 | Data model &1: Create/change/delete master data is finished |
| 084 | Writing will not take place; see error messages |
| 085 | &1: Entity type &2: Writing of master data finished with &3 errors |
| 086 | Upload will not take place because of errors |
| 087 | Data record is not located in the data slice of edition &1 |
| 088 | Field &1 of transfer structure used more than once |
| 089 | Could not determine higher-level node using the data row |
| 090 | Hierarchy node &1 is located in change request &2 |
| 091 | Different hierarchy versions &2 and &1 being used |
| 092 | Different hierarchies &2 and &1 being used |
| 093 | File to be uploaded does not contain any data records |
| 094 | Node &1 cannot be included in a change request |
| 095 | Higher-level node &1 cannot be included in change request |
| 096 | Only SAP defines structures generated with view cluster VC_USMD005 |
| 097 | Hierarchy version must be further restricted |
| 098 | Enter the required fields |
| 099 | Data element &1 does not exist |
| 100 | * Messages 100 - 200 reserved for Distribution Monitor |
| 101 | Edition &1 does not exist with master data package &2, target system &3 |
| 102 | Distributions with status &1 cannot be confirmed |
| 103 | Distributions with status &1 cannot be skipped |
| 104 | Edition &1 does not exist |
| 105 | Edition &1 already transmitted to distribution |
| 106 | Class &1 does not exist |
| 107 | Interface &2 in class &1 is not implemented |
| 108 | No master data packages are created in Customizing |
| 109 | Definition of master data package &1 in Customizing is incomplete |
| 110 | Select one row only for each data distribution |
| 111 | Select a row |
| 112 | No application log exists for distribution step &1 |
| 113 | Specify a required input field &1 |
| 114 | Master data package &1 does not exist in edition &2 |
| 115 | The specified logical system is not assigned to master data package &1 |
| 116 | No distribution service assigned to master data package &1, step &2 |
| 117 | Distribution of master data to logical system &1 started |
| 118 | Distribution system &1 is new and not defined in the SLD |
| 119 | No authorization to distribute master data package &1 to log. system &2 |
| 120 | Distribution service still used in master data package &1 |
| 121 | Deleted master data package still assigned to system &1 |
| 122 | Entity type &1 not assigned to model &2 |
| 123 | Master data package in status &1 cannot be distributed |
| 124 | Mapping for entity type &1 is not specified |
| 125 | For downloads, class CL_USMD_TRANSF_DT must be assigned to distribution |
| 126 | For downloads, class CL_USMD_TRANSF_DT is assigned to distribution |
| 127 | Edition &1 not yet passed to distribution |
| 128 | &1 entries modified for Customizing |
| 129 | Data is in accordance with Customizing settings |
| 130 | Distibution step 0 is invalid |
| 131 | Initialized entry not permitted |
| 132 | Field &1 is not contained in table &2 |
| 133 | No entries found in check table for entity type &1 |
| 134 | RFC destination &1 does not exist |
| 135 | Entity type &1, check table: Different number of key fields |
| 136 | RFC communication error |
| 137 | Data for entity type &1 has been imported |
| 138 | Entity type &1: Import using domain fixed values is not possible |
| 139 | Data element 'MANDT' is not allowed |
| 140 | Entity type &2: Field length of source data element &1 is too short |
| 141 | Enter an edition or a change request for entity type &1 |
| 142 | Error when calling BAdI USMD_DATA_TRANSFER_UPL: &1 &2 &3 &4 |
| 143 | &1: Key &2 does not exist in master data table |
| 144 | Field &1: Value &4 is too long: (&2 is greater than &3) |
| 145 | Upload cannot be performed because of errors |
| 146 | Either the hierarchy to be uploaded or the fragment contains cycles |
| 147 | A lower-level node could not be determined from the data row |
| 148 | Specify a data element for all entity types to be imported |
| 149 | You cannot use this application with enhancement package 5 |
| 150 | Instance &2 of entity type &1 is a hierarchy node: deletion not possible |
| 151 | File is uploaded and distributed to multiple change requests |
| 152 | File is uploaded in change request &1 |
| 153 | All data in the file will be saved to change request &1 |
| 300 | * Messages 300 - 399 reserved for Upload/Download |
| 301 | Select only fields that are under the same higher-level node |
| 302 | Select only one node as the target node |
| 303 | Node &1 cannot be moved |
| 304 | &1 can be moved only under &2 |
| 305 | &1 can be placed only under &2 because it was previously under &3 |
| 306 | In hierarchies, fields cannot be placed directly under &1 |
| 307 | &1 is not a hierarchy attribute |
| 308 | &1 cannot be moved further upward |
| 309 | &1 cannot be moved further downward |
| 310 | Data transfer variant &1 does not exist |
| 311 | Only a fragment of the hierarchy will be uploaded |
| 312 | Action canceled by user |
| 313 | Specify fields for the higher-level node and lower-level node |
| 315 | Field &1 contains invalid characters &2 |
| 316 | Edge with higher-level node &1 and lower node &2 will not be output |
| 317 | Cannot determine hierarchy name; an entry for &1 is missing |
| 318 | Field &1: Value &2 is not the same as &3 |
| 319 | Download of FIN-MDM Entities using DRD is not supported |
| 320 | &1 more error messages are no longer being displayed |
| 321 | More errors exist: work area &1, number &2 |
| 322 | Application &1 has no data model |
| 323 | Node cannot be derived because fields &1 and &2 are filled |
| 324 | Selection condition does not overlap the data slice of the edition |
| 325 | Selection of application server with physical file name not supported |
| 326 | Field &1 will not be uploaded because it is not governed |
| 350 | File download does not support parallel processing |
| 351 | Application &1 uses business object &2 with different model &3 |
| 352 | Application &1 uses business object &2 with incompatible entity type &3 |
| 353 | Transfer variant &1 is defined for incompatible entity type &2 |
| 354 | System settings do not permit a transport |
| 355 | Upload mode &1 cannot be used for entity &2 |
| 356 | The maximum row length of 4096 characters is exceeded in row &1 |
| 357 | &1 is chosen as header field, but the selection is not single value |
| 358 | Only one Download Variant can be used for automatic file download |
| 499 | * Messages 500 - 899 reserved for eSOA |
| 500 | * Messages 500 - 899 reserved for SOA |
| 501 | Service processing &1 for pkg. &2, step &3, target system &4 started |
| 502 | Data selection for package &1, step &2 successfully finished |
| 503 | Field mapping for package &1, step &2 successfully finished |
| 504 | BAdI calls for package &1, step &2 started |
| 505 | Proxy calls for package &1, step &2, service class &3 started |
| 506 | Message for chart of accounts &1 sent to outbound proxy |
| 507 | Error in call of outbound proxy for service &1, chart of accounts &2 |
| 508 | Initialized status entries created for package &1, step &2, system &3 |
| 509 | Error during SMT mapping &1, mapping step &2, target structure &3 |
| 510 | &1 messages sent for package &2, step &3, system &4 |
| 511 | Error during initial status update for package &1, step &2, system &3 |
| 512 | Error during update of status tables due to competing access |
| 513 | No status entry found for message with GUID &1 |
| 514 | Status entry of message &1 has incorrect target system (&2 instead of &3) |
| 515 | Status entry of message &1 has invalid reference GUID (&2 instead of &3) |
| 516 | Status entry of message &1 has incorrect status (&2 instead of &3) |
| 517 | Entry of a From-edition (&1) not possible when distribution complete |
| 518 | Period information cannot be derived from editions &1 and &2 |
| 519 | Error while creating instance of SMT mapping &1, mapping step &2 |
| 520 | Error in status update of messages for edition &1, package &2, system &3 |
| 521 | Error in update of aggregate status f. edtn &1, pkg &2, sys &3, step &4 |
| 522 | Customizing error: No SMT mapping created for data model &1 |
| 523 | A maximum of 10 characters is allowed for accounts (entity type &1) |
| 524 | Bulk message sent to outbound proxy |
| 525 | Error while calling outbound proxy for service &1 |
| 526 | Bulk message contains &1 individual messages |
| 527 | Processing terminated (error in data selection for package &1, step &2) |
| 528 | BAdI call(s) for package &1, step &2, chart of accounts &3 started |
| 529 | BAdI call(s) for package &1, step &2, fin. reporting structure &3 started |
| 530 | Error while reading message &1 (edition &2, package &3, system &4) |
| 531 | &1 &2 &3 &4 |
| 532 | &1 &2 &3 |
| 533 | &1 &2 |
| 534 | Message for financial reporting structure &1 sent to outbound proxy |
| 535 | Error during call to outbound proxy for service &1, fin.rep.structure &2 |
| 536 | Error during status update for edition &2, package &2, system &3, step &4 |
| 537 | Blank bulk message in package &1, step &2; processing terminated |
| 538 | No customer BAdI implemented for service processing &1 |
| 539 | No data found for package &1, step &2; processing &3 terminated |
| 540 | Service processing &1 started |
| 541 | Inbound mapping for service &1 started |
| 542 | Inbound mapping for service &1 ended |
| 543 | Error in inbound mapping for service &1 |
| 544 | Status update for service &1, message &2 started |
| 545 | Error in status update for message &1 (edition &2, package &3, system &4) |
| 546 | BAdI call for service processing &1 started (if BAdI implemented) |
| 547 | No SMT mapping found for entity type &1 in package &2, step &3 |
| 548 | Updating status of distrib. monitor (edtn &1, pkg. &2, sys. &3, step &4) |
| 549 | Mandatory attribute "Category_Code" is blank for &1 |
| 550 | No hierarchy-bearing entity type found for distribution of package &1 |
| 551 | &1 |
| 552 | Starting distribution step &1 of master data package &2 (edtn &3, sys.&4) |
| 553 | No authorization for distribution of master data package &1 to system &2 |
| 554 | Consolidation area is still blank in replication message for &1 |
| 555 | Status successfully updated for message &1 (edtn &2, package &3, sys. &4) |
| 556 | Delta distribution not possible for entity type &1 |
| 557 | Updating status of distribution monitor (edt.&1, app.&2, sys.&3, step &4) |
| 558 | Error while updating aggregate status f. edt.&1, app.&2, sys.&3, step &4 |
| 559 | Error while updating status of notification f. edition &1, app.&2, sys.&3 |
| 560 | Errors occured during the distribution; check the appropriate log |
| 561 | No application has been created in Customizing |
| 562 | This edition contains no data to be distributed |
| 563 | Master data package &1 does not exist in Customizing |
| 564 | No distribution step assigned to master data package &1 |
| 565 | No target system assigned to master data package &1 in Customizing |
| 566 | Master data package &1 has no distribution step &2 in Customizing |
| 567 | Application &1 does not exist |
| 568 | Application &2 does not have a distribution step &1 |
| 569 | Outbound implementation &1 does not exist |
| 570 | Business system &1 does not exist |
| 571 | Field name &1 no longer exists in active data model &2 |
| 572 | No object type code assigned to entity type &1 of data model &2 |
| 573 | Change request &1 does not contain objects to be replicated |
| 574 | Change request &1, OTC &2: Error &3 while generating structure |
| 575 | Change request &1 cannot be directly replicated |
| 576 | You are not authorized to distribute all master data packages |
| 577 | &1 &2 already assigned to change request &3 with edition &4 |
| 578 | Company &1 replicated successfully |
| 579 | Financial Reporting Structure &1 replicated successfully |
| 580 | Fields cannot be uploaded and are removed from the selection: &1 &2 &3 &4 |
| 581 | Failed to determine standard hierarchy for profit center &1 / &2 |
| 582 | Profit Center &1/&2 not assigned in MDG hierarchy, standard hier. used |
| 583 | Failed to determine standard hierarchy for cost center &1 / &2 |
| 584 | Cost Center &1/&2 not assigned in MDG hierarchy, standard hier. used |
| 585 | Object "&1" in edition "&2" is not replicated |
| 586 | Error due to background RFC Customizing for business object type &1 |
| 587 | Queue &1 contains a failed unit |
| 588 | Queue &1 is currently locked |
| 589 | There are duplicate values in company codes assigned to profit center &1 |