MDG_TR - MDG: Transporttool
The following messages are stored in message class MDG_TR: MDG: Transporttool.
It is part of development package MDG_TRANSPORT_TOOL in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Transport Tool".
It is part of development package MDG_TRANSPORT_TOOL in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Transport Tool".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Internal error &1 &2 &3 &4 |
| 001 | SOBJ object &1 has already been used |
| 002 | The transport object name cannot contain underscores (_) |
| 003 | Container has structure information for object &1(&2) |
| 004 | Transport object not yet initialized -> double-click on the object |
| 005 | The container has no structure information for object &1(&2) |
| 006 | The container has no data information for object &1(&2) |
| 007 | The container has data information for object &1(&2) |
| 008 | Application &1 not created in table FINB_TR:TAPPL |
| 009 | Before-export handling started for object &1(&2) |
| 010 | Before-export handling completed for object &1(&2) |
| 011 | After-import handling started for object &1(&2) |
| 012 | After-import handling completed for object &1(&2) |
| 013 | Export: Table &1 with &2 keys |
| 014 | Errors occurred during export of container object &1(&2) |
| 015 | Table &1: &2 data records deleted |
| 016 | Table &1: &2 data records added |
| 019 | Not all records could be added |
| 020 | Table &1: Error during UPDATE of an individual record (&2) |
| 021 | Table &1: Error during INSERT of an individual record (&2) |
| 022 | Table &1: Key &2 does not specify an individual record |
| 023 | Import processing for table &1 stopped |
| 024 | Import processing for object &1(&2) stopped |
| 025 | Structure information in container differs from that in table &1 |
| 027 | Key information for table &1 contains errors |
| 028 | No text table defined for application &1 |
| 029 | Text table &1 in application &2 has not been activated |
| 030 | Data type &1 is not supported |
| 031 | Object &1(&2) contains no table keys |
| 032 | No suitable RFC destination could be found |
| 033 | Import carried out using RFC destination &1 |
| 034 | There is no ranges table in the container for a key |
| 035 | RFC destination &1 points to the wrong client &2 |
| 036 | Specify an existing RFC destination |
| 037 | Translation is only possible in logon clients |
| 038 | Import table &1: Key &2 contains errors |
| 040 | Request type &1 not supported |
| 041 | Table key does not contain a client condition |
| 042 | RFC error with destination &1 -> see long text |
| 043 | Table &1: &2 data records exported |
| 044 | Table &1 in application &2 is not active |
| 045 | No transport objects for postprocessing |
| 046 | The export is executed with RFC destination &1 |
| 047 | Communication error: Destination &1 -> long text |
| 048 | Object &1(&2) has been excluded from the client copy |
| 049 | Structure information table &2 object &1 checked |
| 050 | No key information for object &1(&2) in the container |
| 052 | Job &1 scheduled -> Long text |
| 053 | Access class &1 generated |
| 054 | Access class &1 is current |
| 055 | Analysis phase of client copy terminated - see long text |
| 056 | The client copy needs to be post-processed - see long text |
| 057 | Copy: Table &1 with &2 keys |
| 058 | Copy: Table &1 &2 data records from client &3 |
| 059 | Error during generation of a program - see long text |
| 060 | Error during dynamic method call |
| 061 | Start the deletion method for object &1 |
| 062 | End of deletion method of object &1 |
| 063 | Copying of table &1 terminated |
| 064 | You not authorized to perform this action - see long text |
| 065 | Table pair for object &1(&2) contains errors and will be ignored |
| 066 | The key fields in the tables are not the same (&1, &2) |
| 067 | Target table &2 does not contain field &1 |
| 068 | Field &1 has a different data type in target table &2 |
| 069 | Field &1 is shorter in target table &2 - data could be lost |
| 070 | Start of deletion methods for client &1 |
| 071 | Function is only supported for container objects |
| 072 | Object &1(&2) does not support any test mode |
| 073 | Execute method in test mode (without DB update) |
| 074 | This table key already exists |
| 075 | Selection option already exists |
| 076 | Data has been saved |
| 077 | Error or termination in target client: &1 |
| 078 | Target client: &1 user: &2 RFC dest.: &3 |
| 079 | Transport request has already been released. Changes are not possible |
| 080 | Internal error where( )-tab: table: &1, key: &2 |
| 081 | RFC connection &1 does not point to local system &2 but to &3 |
| 082 | Table &1: Export &2 data records (&3 / &4) |
| 083 | Table &1: INS(&2) DEL(&3) UPD(&4) |
| 084 | Detail for table &1: see long text |
| 085 | Field &1 is new in target table &2 |
| 086 | Start processing object &1(&2) |
| 087 | Finish processing object &1(&2) |
| 088 | Automatic postprocessing of client &1 was incorrect; see long text |
| 089 | Automatic postprocessing of client &1 was successful -> long text |
| 090 | Automatic postprocessing of client &1 was terminated -> long text |
| 091 | Last transport object: &1 (component &2) |
| 092 | Client is protected against postprocessing |
| 093 | No data available for client copy |
| 094 | Destination &1 entered for client &2 in table MDG_TR_DEST |
| 095 | |
| 098 | Role Generation not possible: Upgrade in progress |
| 099 | Client Copy not possible: Upgrade in progress |
| 100 | Table: &1 key &2 deleted |
| 101 | At present this function is not supported |
| 201 | Fatal error during import of transport object &1 / &2 / &3 / &4 |
| 300 | *** Messages for "MDG_TRANSPORT_CLASSIC" *** |
| 301 | Internal error creating transport object |