SAP ABAP Message Class DU (Data transfer to SAP-EIS)
Basic Data
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
CA-GTF-DCM (Application Component) Data Transfer
⤷
BKD (Package) Tools for (external) data transfer
⤷
⤷
Attributes
| Message class | DU | |
| Short Description | Data transfer to SAP-EIS | |
| Changed On | 20110908 | |
| Last Changed At | 160550 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | & & & & | |||
| 2 | Derivation rules for aspect &1 not possible | |||
| 3 | Sender field receiver field may not agree | |||
| 4 | Please enter a valid characteristic | |||
| 5 | For data type &1, the field length must be smaller than &2 | Space: object requires documentation | ||
| 6 | No authorization for sender structures | |||
| 7 | Convert field & from & to & | |||
| 8 | Check transfer rules for & Segment & Segment number & | |||
| 9 | Field type I cannot be converted -> Use field type P (length 6) | |||
| 10 | Delete transfer rules | |||
| 11 | Segment in user exit & changed | |||
| 12 | Delete conversion rules for IDOC segments | |||
| 13 | Enter sender structure or sender structure package | Space: object requires documentation | ||
| 14 | Logical file name & does not exist | |||
| 15 | File &1 could not be opened. Message: &2 | |||
| 16 | Repeat field &1 exists more than once | |||
| 17 | Segment name & and sender structure & are not compatible | |||
| 18 | Only files with a record length of < 4096 bytes can be imported | |||
| 19 | Definition of segment & is not correct | |||
| 20 | Enter a valid characteristic | |||
| 21 | You cannot maintain rules for characteristics with a fixed value | |||
| 22 | Enter a valid type for conversion | |||
| 23 | Field length &2 required for data type &1 | |||
| 24 | The file cannot be imported in this format | |||
| 25 | Sender field &1 could not be read | |||
| 26 | Enter a sender field or a unit | |||
| 27 | No suggestion could be created for some receiver fields | |||
| 28 | Enter a unit or reference field for &1 | |||
| 29 | Enter repeat fields | |||
| 30 | Enter a repitition factor | |||
| 31 | The index field cannot be contained in the repeat fields | |||
| 32 | Enter an index field | |||
| 33 | Enter an increment | |||
| 34 | Test the currency translation modality &1 for field &2 | |||
| 35 | The specification of decimal places is only permitted with type P | |||
| 36 | The rules for the field & are inconsistent | |||
| 37 | No further objects found | |||
| 38 | Note: The function displays the file system of the presentation server | |||
| 39 | Sender field &1 in aspect &2 not available. Maintain in another aspect | |||
| 40 | No batch input sessions can be created for this type of data | |||
| 41 | The sender structure &1 is not defined | |||
| 42 | Aspect &1 is not active | |||
| 43 | Summarization program has not been generated | |||
| 44 | Characteristic &1 is not in the field catalog | |||
| 45 | Summarization and updating failed | |||
| 46 | Initilization of data transfer unsuccessful | |||
| 47 | Data transfer completed without errors | |||
| 48 | Receiver structure is not in ABAP dictionary | |||
| 49 | No sender records available | |||
| 50 | Field catalog is inconsistent | |||
| 51 | Receiver field no longer in ABAP dictionary | |||
| 52 | Maintain transfer rules | |||
| 53 | Check the log | |||
| 54 | Currency translation type has not been defined | |||
| 55 | Entries for currency translation are incorrect | |||
| 56 | Key figure formula has not been defined correctly | |||
| 57 | Transfer rules are incorrect | |||
| 58 | The value &1 in sender field &2 is too large for processing | |||
| 59 | Overlapping freedom cannot be checked | |||
| 60 | Errors have occured during validation | |||
| 61 | Maximum field length with type P is 16 bytes | |||
| 62 | The data is archived on the file system of the application server | |||
| 63 | Please establish, whether the figures contain commas or decimal points | |||
| 64 | Structure &1 is not active | The short text describes the object sufficiently | ||
| 65 | Enter sender structure | Space: object requires documentation | ||
| 66 | Please generate the update routines for the master data maintenance | Space: object requires documentation | ||
| 67 | Field name &1 is not correct | Space: object requires documentation | ||
| 68 | Field &1 is no longer used in an aspect | Space: object requires documentation | ||
| 69 | Master data table &1 could not be locked | Space: object requires documentation | ||
| 70 | No information from field catalog | Space: object requires documentation | ||
| 71 | Language &1 is not in the language table | Space: object requires documentation | ||
| 72 | *** Data transfer monitor *********************************************** | |||
| 73 | Error in graphic & | |||
| 74 | Error & occurred when the job was selected | |||
| 75 | Error when reading variant & for starter program RKCSUB00 | |||
| 76 | Job is planned but has not run yet | |||
| 77 | Error & when reading job log for job & | |||
| 78 | You have not selected any logs to delete | |||
| 79 | *** Communication ******************************************************* | |||
| 80 | Interface for function module & could not be created | |||
| 81 | Destination & does not exist | |||
| 82 | Error occurred in CPIC & communication | |||
| 83 | Transfer method & has not been created | |||
| 84 | Destination & has not been maintained | |||
| 85 | Sender structure & has not been maintained | |||
| 86 | Sender structure & has not been maintained in system & | |||
| 87 | System error occurred in system & | |||
| 88 | Error occurred during communication with & | |||
| 89 | Interface to function module & transferred to destination & | |||
| 90 | Interface to function module & could not be saved | |||
| 91 | No function module exists for sender structure & | |||
| 92 | Save the sender structure first | |||
| 93 | Maintain transfer rules for sender structure & | |||
| 94 | Function module & was generated | |||
| 95 | No function module could be generated for structure &. | Space: object requires documentation | ||
| 96 | The system parameter & & is not maintained in table T2420 | |||
| 97 | The sender structure-transfer path combination & & is not maintained | |||
| 98 | Entry & is missing in table TXCOM | |||
| 99 | Data could not be saved in & | |||
| 100 | Data saved in & | |||
| 101 | The sender structure & exists - do not use a model | |||
| 102 | Only enter a model or a reference | |||
| 103 | The data structure & is saved to sender structure & as a reference | |||
| 104 | No data structure is saved to sender structure & as a reference | |||
| 105 | Queue in the sender system is empty | |||
| 106 | Dictionary structure & is not used differently in the sender structure | Space: object requires documentation | ||
| 107 | Dictionary structure name & too long | Space: object requires documentation | ||
| 108 | Dictionary structue for sender structure & does not exist | Space: object requires documentation | ||
| 109 | Dictionary structure & alreday exists use a different name | Space: object requires documentation | ||
| 110 | Enter the dictionary structure name | Space: object requires documentation | ||
| 111 | Non-existing dictionary structures are removed from list | Space: object requires documentation | ||
| 112 | Select one row only | Space: object requires documentation | ||
| 113 | If & is changed the transfer rules could be inconsistent | Space: object requires documentation | ||
| 114 | Field &1 still being used - transfer rules will be inconsistent | Space: object requires documentation | ||
| 115 | Sender program & started in & | |||
| 116 | There is no sender structure for program & | |||
| 117 | Program & cannot be used to send data to another system | |||
| 118 | &2 is used as the sender structur name instead of &1 (see long text) | Space: object requires documentation | ||
| 119 | An external program can only be maintained as a receiver structure | |||
| 120 | You must have entered the target char. or transfer method (sender info.) | |||
| 121 | You must have entered the target aspect or transfer method (sender info.) | |||
| 122 | The DDIC-Structure & already exists -> use another name | |||
| 123 | DDIC-Structure & cannot be saved | |||
| 124 | DDIC-Structure & cannot be activated | |||
| 125 | & is blocked | |||
| 126 | Error while processing the DDIC-Structure & | Space: object requires documentation | ||
| 127 | Name & is not permitted | |||
| 128 | DDIC-Structure & saved | |||
| 129 | DDIC-Structure & deleted | |||
| 130 | DDIC-Structure & activated | |||
| 131 | The dictionary structure & was deleted | Space: object requires documentation | ||
| 132 | The dictionary structure & was not deleted | Space: object requires documentation | ||
| 133 | The dictionary structure & is still being used | Space: object requires documentation | ||
| 134 | Enter a block size between 100 and 100.000 | Space: object requires documentation | ||
| 135 | Sender fields contain invalid characters | Space: object requires documentation | ||
| 136 | Please select a valid line | Space: object requires documentation | ||
| 137 | Specify a table or structure first | Space: object requires documentation | ||
| 138 | The structure must be a sender or receiver structure | Space: object requires documentation | ||
| 139 | Sender fields must be unique in a structure (&) | Space: object requires documentation | ||
| 140 | Select a row | Space: object requires documentation | ||
| 141 | The sender structure & already exist | Space: object requires documentation | ||
| 142 | The sender structure & was not saved | Space: object requires documentation | ||
| 143 | Save first | Space: object requires documentation | ||
| 144 | No free Dictionary structure name available for sender structure & | Space: object requires documentation | ||
| 145 | No dictionary structure was saved for sender structure & | Space: object requires documentation | ||
| 146 | Sender field & is too long | |||
| 147 | Please enter just the prg. name or the registry entry | |||
| 148 | Please enter the registry entry completely (key and section) | The short text describes the object sufficiently | ||
| 149 | Please enter the program to be entered using the registry or prg name | |||
| 150 | No registry entry was found | |||
| 151 | Call program using report-report interface only. | |||
| 152 | Only 9 DDIC structures can be processed | Space: object requires documentation | ||
| 153 | The position is not unique | Space: object requires documentation | ||
| 154 | Transfer method & does not exist | Space: object requires documentation | ||
| 155 | Characteristic &1 is not valid | Space: object requires documentation | ||
| 156 | ---- Flexible Excel upload ----- | Space: object requires documentation | ||
| 157 | The value assignment is not correct for the value area & | Space: object requires documentation | ||
| 158 | Key areas must encompass several cells of a row or column & | Space: object requires documentation | ||
| 159 | No value found for &1 &2 | Space: object requires documentation | ||
| 160 | Only one key area without a field name is allowed (value area &) | Space: object requires documentation | ||
| 161 | No sender field &3 exists for &2 &1 | Space: object requires documentation | ||
| 162 | Value area & does not exist | Space: object requires documentation | ||
| 163 | Key area and data area do not suit one another | Space: object requires documentation | ||
| 164 | The file description is consistent | Space: object requires documentation | ||
| 165 | File name & already exists | Space: object requires documentation | ||
| 166 | No log exists | Space: object requires documentation | ||
| 167 | Please position the cursor | Space: object requires documentation | ||
| 168 | File name is locked by user & | Space: object requires documentation | ||
| 169 | File could not be opened | Space: object requires documentation | ||
| 170 | Nonallowed file type | Space: object requires documentation | ||
| 171 | File description is not free from overlap: Row & column & | Space: object requires documentation | ||
| 172 | File description & already exists | Space: object requires documentation | ||
| 173 | Either enter value area explicitly or use! '*' | Space: object requires documentation | ||
| 174 | Enter a generic file name | Space: object requires documentation | ||
| 175 | File description & was saved | Space: object requires documentation | ||
| 176 | The position details are inconsistent | Space: object requires documentation | ||
| 177 | Key blocks may have an extension in one direction only | Space: object requires documentation | ||
| 178 | File description & could not be saved | Space: object requires documentation | ||
| 179 | Value columns occupy different rows &1 &2 &3 &4 | Space: object requires documentation | ||
| 180 | Related keys and values occupy different rows | Space: object requires documentation | ||
| 181 | Key (row & column &) does not match the data area | Space: object requires documentation | ||
| 182 | ***** Messages for 3.0 XPRA ********************************************* | |||
| 183 | Receiver program & is not supported | |||
| 184 | Receiver routine & is not supported | |||
| 185 | Parameter & & & is not used | |||
| 186 | & SAP-EIS parameters were reorganized | |||
| 187 | SAP-EIS transfer parameters were reorganized | |||
| 188 | Sender field &2 is inconsistent in sender structure &1 | Space: object requires documentation | ||
| 189 | Sender field &2 is inconsistent in sender structure &1 | Space: object requires documentation | ||
| 190 | 3.0 - 4.0 conversion EC-EIS sender structures | Space: object requires documentation |
History
| Last changed on/by | 20110908 | SAP | |
| SAP Release Created in |