DU - Daten�bernahme im SAP-EIS
The following messages are stored in message class DU: Daten�bernahme im SAP-EIS.
It is part of development package BKD in software component CA-GTF-DCM. This development package consists of objects that can be grouped under "Tools for (external) data transfer".
It is part of development package BKD in software component CA-GTF-DCM. This development package consists of objects that can be grouped under "Tools for (external) data transfer".
Message Nr ▲ | Message Text |
|---|---|
| 001 | & & & & |
| 002 | Derivation rules for aspect &1 not possible |
| 003 | Sender field receiver field may not agree |
| 004 | Enter a valid characteristic |
| 008 | For data type &1, the field length must be less than &2 |
| 009 | No authorization for sender structures |
| 010 | Convert field & from & to & |
| 011 | Check transfer rules for & Segment & Segment number & |
| 012 | Field type I cannot be converted -> Use field type P (length 6) |
| 013 | Delete transfer rules |
| 014 | Segment in user exit & changed |
| 015 | Delete conversion rules for IDOC segments |
| 016 | Enter sender structure or sender structure package |
| 017 | Logical file name & does not exist |
| 018 | File &1 could not be opened. Message: &2 |
| 019 | Repeat field &1 exists more than once |
| 020 | Segment name & and sender structure & are not compatible |
| 021 | Only files with a record length of < 4096 bytes can be imported |
| 022 | Definition of segment & is not correct |
| 023 | Enter a valid characteristic |
| 024 | You cannot maintain rules for characteristics with a fixed value |
| 025 | Enter a valid type for conversion |
| 026 | Field length &2 required for data type &1 |
| 027 | The file cannot be imported in this format |
| 028 | Sender field &1 could not be read |
| 029 | Enter a sender field or a unit |
| 030 | No suggestion could be created for some receiver fields |
| 031 | Enter a unit or reference field for &1 |
| 032 | Enter repeat fields |
| 033 | Enter a repitition factor |
| 034 | The index field cannot be contained in the repeat fields |
| 035 | Enter an index field |
| 036 | Enter an increment |
| 037 | Test the currency translation modality &1 for field &2 |
| 038 | The specification of decimal places is only permitted with type P |
| 039 | The rules for the field & are inconsistent |
| 040 | No further objects found |
| 041 | Note: The function displays the file system of the presentation server |
| 042 | Sender field &1 in aspect &2 not available. Maintain in another aspect |
| 043 | No batch input sessions can be created for this type of data |
| 044 | The sender structure &1 is not defined |
| 045 | Aspect &1 is not active |
| 046 | Summarization program not generated |
| 047 | Characteristic &1 is not in the field catalog |
| 048 | Summarization and updating failed |
| 049 | Initilization of data transfer unsuccessful |
| 050 | Data transfer completed without errors |
| 051 | Receiver structure is not in ABAP dictionary |
| 052 | No sender records exist |
| 053 | Field catalog is inconsistent |
| 054 | Receiver field no longer in ABAP dictionary |
| 055 | Maintain transfer rules |
| 056 | Check the log |
| 057 | Currency translation type has not been defined |
| 058 | Error in specified currency translation |
| 059 | Key figure formula has not been defined correctly |
| 060 | Error in transfer rules |
| 061 | The value &1 in sender field &2 is too big to be processed |
| 062 | Overlapping freedom cannot be checked |
| 063 | Errors occurred during validation |
| 064 | Maximum field length with type P is 16 bytes |
| 065 | The data is archived on the file system of the application server |
| 066 | Determine whether the numbers contain commas or decimal points |
| 067 | Structure &1 is not active |
| 068 | Enter sender structure |
| 070 | Generate the update routines for master data maintenance |
| 071 | Field name &1 is not correct |
| 072 | Field &1 is no longer used in an aspect |
| 073 | Master data table &1 could not be locked |
| 074 | No information from field catalog |
| 075 | Language &1 is not in the language table |
| 100 | *** Data transfer monitor *********************************************** |
| 101 | Error in graphic & |
| 102 | Error & occurred when the job was selected |
| 103 | Error when reading variant & for starter program RKCSUB00 |
| 104 | Job is planned but has not run yet |
| 105 | Error & when reading job log for job & |
| 106 | You have not selected any logs to delete |
| 200 | *** Communication ******************************************************* |
| 201 | Interface for function module & could not be created |
| 202 | Destination & does not exist |
| 203 | Error occurred in CPIC & communication |
| 204 | Transfer method & has not been created |
| 205 | Destination & has not been maintained |
| 206 | Sender structure & has not been maintained |
| 207 | Sender structure & has not been maintained in system & |
| 208 | System error occurred in system & |
| 209 | Error occurred during communication with & |
| 210 | Interface to function module & transferred to destination & |
| 211 | Interface to function module & could not be saved |
| 212 | No function module exists for sender structure & |
| 213 | Save the sender structure first |
| 214 | Maintain transfer rules for sender structure & |
| 215 | Function module & was generated |
| 216 | No function module could be generated for structure &. |
| 217 | The system parameter & & is not maintained in table T2420 |
| 218 | The sender structure-transfer path combination & & is not maintained |
| 219 | Entry & is missing in table TXCOM |
| 220 | Data could not be saved in & |
| 221 | Data saved in & |
| 222 | The sender structure & exists - do not use a model |
| 223 | Only enter a model or a reference |
| 224 | The data structure & is saved to sender structure & as a reference |
| 225 | No data structure is saved to sender structure & as a reference |
| 226 | Queue in the sender system is empty |
| 227 | Dictionary structure & is not used differently in the sender structure |
| 228 | Dictionary structure name & too long |
| 229 | Dictionary structue for sender structure & does not exist |
| 230 | Dictionary structure & alreday exists use a different name |
| 231 | Enter the dictionary structure name |
| 232 | Nonexistent dictionary structures were removed from the list |
| 233 | Select one row only |
| 234 | If & is changed the transfer rules could be inconsistent |
| 235 | Field &1 still being used - transfer rules will be inconsistent |
| 250 | Sender program & started in & |
| 251 | There is no sender structure for program & |
| 252 | Program & cannot be used to send data to another system |
| 253 | &2 is used as the sender structure name instead of &1 (see long text) |
| 301 | An external program can only be maintained as a receiver structure |
| 302 | You must have entered the target char. or transfer method (sender info.) |
| 303 | You must have entered the target aspect or transfer method (sender info.) |
| 350 | The DDIC-Structure & already exists -> use another name |
| 351 | DDIC-Structure & cannot be saved |
| 352 | DDIC-Structure & cannot be activated |
| 353 | & is blocked |
| 354 | Error while processing the DDIC-Structure & |
| 355 | Name & is not permitted |
| 356 | DDIC-Structure & saved |
| 357 | DDIC-Structure & deleted |
| 358 | DDIC-Structure & activated |
| 359 | The dictionary structure & was deleted |
| 360 | The dictionary structure & was not deleted |
| 361 | The dictionary structure & is still being used |
| 362 | Enter a block size between 100 and 100.000 |
| 363 | Sender fields contain invalid characters |
| 365 | Select a valid line |
| 366 | Specify a table or structure first |
| 367 | The structure must be a sender or receiver structure |
| 368 | Sender fields must be unique in a structure (&) |
| 369 | Select a row |
| 370 | The sender structure & already exist |
| 371 | The sender structure & was not saved |
| 372 | Save first |
| 373 | No free Dictionary structure name available for sender structure & |
| 374 | No dictionary structure was saved for sender structure & |
| 400 | Sender field & is too long |
| 401 | Enter only a program name or a registry entry |
| 402 | Enter the full registry entry (key and section) |
| 403 | Enter the program to be executed using the registry or program name |
| 404 | No registry entry was found |
| 500 | Call program using report-report interface only. |
| 550 | Only 9 DDIC structures can be processed |
| 551 | The position is not unique |
| 552 | Transfer method & does not exist |
| 553 | Characteristic &1 is not valid |
| 600 | ---- Flexible Excel upload ----- |
| 601 | The value assignment is not correct for the value area & |
| 602 | Key areas must encompass multiple cells of a row or column & |
| 603 | No value found for &1 &2 |
| 604 | Only one key area without a field name is allowed (value area &) |
| 605 | No sender field &3 exists for &2 &1 |
| 606 | Value area & does not exist |
| 607 | Key area and data area do not suit one another |
| 608 | The file description is consistent |
| 609 | File name & already exists |
| 610 | No log exists |
| 611 | Position the cursor |
| 612 | File name is locked by user & |
| 613 | File could not be opened |
| 614 | Invalid file type |
| 615 | File description is not free from overlap: Row & column & |
| 616 | File description & already exists |
| 617 | Either enter value area explicitly or use! '*' |
| 618 | Enter a generic file name |
| 619 | File description & was saved |
| 620 | The position details are inconsistent |
| 621 | Key blocks may have an extension in one direction only |
| 622 | File description & could not be saved |
| 623 | Value columns occupy different rows &1 &2 &3 &4 |
| 624 | Related keys and values occupy different rows |
| 625 | Key (row & column &) does not match the data area |
| 850 | ***** Messages for 3.0 XPRA ********************************************* |
| 851 | Receiver program & is not supported |
| 852 | Receiver routine & is not supported |
| 853 | Parameter & & & is not used |
| 854 | & SAP-EIS parameters were reorganized |
| 855 | SAP-EIS transfer parameters were reorganized |
| 885 | Sender field &2 is inconsistent in sender structure &1 |
| 886 | Sender field &2 is inconsistent in sender structure &1 |
| 901 | 3.0 - 4.0 conversion EC-EIS sender structures |