Message Number list used by SAP ABAP Program LSDMXF02 (DD: Subroutines for TNMAP Screens)
SAP ABAP Program
LSDMXF02 (DD: Subroutines for TNMAP Screens) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | MX - 075 | Revised version does not exist | ||
| 2 | MX - 057 | Function "Delete and Copy Data" was terminated | ||
| 3 | MX - 063 | Insert identical mapping entry before activating | ||
| 4 | MX - 066 | Table & not in customer namespace | ||
| 5 | MX - 067 | Table & in customer namespace | ||
| 6 | MX - 068 | No subsequent mapping is selected | ||
| 7 | MX - 069 | Do not cut entries to be deleted: deletion has already begun | ||
| 8 | MX - 070 | Terminated merge jobs for table(s): &. Please repeat deletion | ||
| 9 | MX - 071 | Planned merge jobs for table(s): & | ||
| 10 | MX - 072 | Running merge jobs for table(s): & | ||
| 11 | MX - 073 | Table(s) without jobs to be deleted: & | ||
| 12 | MX - 045 | Header table & could not be written -> activation was terminated | ||
| 13 | MX - 076 | No entry selected | ||
| 14 | MX - 077 | No further entry for ID mapping exists: not possible to cut | ||
| 15 | MX - 078 | Only use one assignment for group & | ||
| 16 | MX - 079 | Term./running/scheduled jobs ex. for deletion procedure. Please check | ||
| 17 | MX - 087 | Not possible to sort according to this field | ||
| 18 | MX - 088 | Please check the deletion process with function "Check job states" | ||
| 19 | MX - 091 | Tables and view act. exited > Check multiplex log | ||
| 20 | MX - 092 | Tables and view act. with errors -> Check multiplex logs | ||
| 21 | MX - 094 | No job necessary for data transfer | ||
| 22 | MX - 032 | No active version exists. Reset not possible | ||
| 23 | MX - 010 | Multiplex table & does not yet have a local name | ||
| 24 | MX - 011 | No multiplex table selected | ||
| 25 | MX - 014 | Scrolling not possible | ||
| 26 | MX - 018 | Entries in table & could not be read | ||
| 27 | MX - 019 | Entry for group & already exists -> change ignored | ||
| 28 | MX - 023 | Table with name & already exists in the ABAP Dictionary | ||
| 29 | MX - 024 | An object with name & already exists in the same namespace | ||
| 30 | MX - 027 | Transaction lock could not be reset | ||
| 31 | MX - 028 | Multiplexing information on table & could not be written | ||
| 32 | MX - 031 | No entries exist yet. Reset not possible | ||
| 33 | MX - 009 | Invalid cursor position | ||
| 34 | MX - 033 | Mapping was reset to active version | ||
| 35 | MX - 034 | Reset to active version failed | ||
| 36 | MX - 035 | Table & already being used in mapping &1 -> &2 | ||
| 37 | MX - 036 | Reset not possible | ||
| 38 | MX - 037 | No valid selection made | ||
| 39 | MX - 038 | Display of revised version failed | ||
| 40 | MX - 039 | Save of mapping for table & failed -> activation process terminated | ||
| 41 | MX - 040 | Analysis of mapping for table & failed -> activation process terminated | ||
| 42 | MX - 044 | Header table & could not be read -> activation was terminated |