CACSAPPK - Messages for Application Cloner
The following messages are stored in message class CACSAPPK: Messages for Application Cloner.
It is part of development package CACSMTD in software component ICM. This development package consists of objects that can be grouped under "ICM: TCACS_MTDTAB Environment".
It is part of development package CACSMTD in software component ICM. This development package consists of objects that can be grouped under "ICM: TCACS_MTDTAB Environment".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | No tables found for application &1 |
| 002 | Cross-client table &1 for application &2 is not empty |
| 003 | Client-specific table &1 is not empty for application &2 |
| 004 | Master data table &1 is not empty for application &2 |
| 005 | Transaction data table &1 is not empty for application &2 |
| 006 | Database table &1 does not exist |
| 007 | No application field exists for application-dependent table &1 |
| 008 | RFC destination client &1 is different from selected client &2 |
| 009 | RFC destination Sysid &1 is different from selected Sysid &2 |
| 010 | Error while generating application &2 in table &1 |
| 011 | Source application is identical to target application &1 |
| 012 | Application cloner: process was started |
| 013 | Cloning source application &1 to target application &2 |
| 014 | P R O D U C T I V E R U N |
| 015 | T E S T R U N |
| 016 | Strict consistency - tables must be identical |
| 017 | Weak consistency - "Move-corresponding" is used |
| 018 | Source application is read locally from client &1 |
| 019 | Source application is read from remote system &1 client &2 |
| 020 | Target application definition is edited locally in client &1 |
| 021 | Target application definition is edited in remote system &1 in client &2 |
| 022 | Target application may be used locally in client &1 |
| 023 | Cloning cross-client data |
| 024 | Checking that application data is empty |
| 025 | Checking that client-dependent data is empty |
| 026 | Checking that master data is empty |
| 027 | Checking that transaction data is empty |
| 028 | Checking that client-independent data is empty |
| 029 | Checking consistency of application tables |
| 030 | Checking consistency of client-independent tables |
| 031 | Source table &1 and target table &2 are both inactive - ignoring |
| 032 | Source table &1 is inactive and is being ignored |
| 033 | Source table &1 is inactive |
| 034 | Target table &1 is inactive and is being ignored |
| 035 | Target table &1 is inactive |
| 036 | No source table exists for target table &1 - ignoring |
| 037 | No source table exists for target table &1 |
| 038 | Source table &1 and target table &2 have different application dependency |
| 039 | External type of source table &1 and target table &2 are different |
| 040 | Source table &1 and target table &2 have weak consistency |
| 041 | Source table &1 and target table &2 are inconsistent |
| 042 | Source table &1 and target table &2 are strictly consistent |
| 043 | Checking consistency of client-dependent tables |
| 044 | Checking consistency of master data tables |
| 045 | Checking consistency of transaction data tables |
| 046 | Checking consistency of client-independent tables only |
| 047 | Cloning client-dependent data |
| 048 | Cloning master data |
| 049 | Cloning transaction data |
| 050 | Error in update of generation status in table &1 for application &2 |
| 051 | Source applic. &1 is being instantiated for client &2 (remote syst. "&3") |
| 052 | Tgt applic. &1 is being instantiated for client &2 (remote system "&3") |
| 053 | Source application and target application must be different |
| 054 | Target application &1 already exists |
| 055 | No selection made |
| 056 | Client-independent copying can only be executed separately |
| 057 | RFC error: &1 |
| 058 | Generating target application &1 - messages to follow... |
| 059 | Generation was not executed - test run |
| 060 | Cloning construction- and client-independent data |
| 061 | Copying data from table &1 to table &2 |
| 062 | &2 entries inserted in table &1 |
| 063 | Error while inserting table &1 |
| 064 | Generation of target application &1 is complete - read log |
| 065 | Copying number ranges from application &1 to application &2 |
| 066 | Copying PD-Org assignments from application &1 to application &2 |
| 067 | Copying condition records from application &1 to application &2 |
| 068 | Copying entries of condition table &1 |
| 069 | Condition table &1 is not application-specific - no data edited |
| 070 | Condition table &1 has no condition number field - no data edited |
| 071 | Condition table &1 has no condition type field - no data edited |
| 072 | Copying condition record &1 (condition type &2) |
| 073 | Condition type &1 is not valid for application &2 |
| 074 | Condition record &1 was not found |
| 075 | Copying application logs from application &1 to application &2 |
| 076 | Copying application log &1 &2 &3 |
| 077 | No messages found for application log (handle &1) |
| 078 | Copying copy services from application &1 to application &2 |
| 079 | Copying master data entries from application &1 to application &2 |
| 080 | Copying transaction data entries from application &1 to application &2 |
| 081 | Copying client-independent entries from application &1 to application &2 |
| 082 | Copying client-dependent entries from application &1 to application &2 |
| 083 | &1 PD-Org assignments copied |
| 084 | No detail found in source application &1 for condition record |
| 085 | Run was terminated by user |
| 086 | A non-current client of the target application requires an RFC |
| 087 | Application log error - no message could be added |
| 088 | Checking RFC destination &1 - log on if necessary |
| 089 | XML transformation error for table &1 |
| 090 | Application field exists for application-independent table &1 |
| 091 | Invalid table &1 - neither external nor application-dependent |
| 092 | Setting process information |
| 093 | Client-independent data must be copied first |
| 094 | Original source client &1 is not identical to the current source client |
| 095 | Original system ID &1 is not identical to current system ID |
| 096 | Original source applic. &1 is not identical to current source applic. &2 |
| 097 | Client-independent data was cloned first |
| 098 | Copying step of cross-client data is missing |
| 099 | Copying step of client-dependent data is missing |
| 100 | Copying step of master data is missing |
| 101 | Cannot update process data in table CACS_CLONE |
| 102 | Execute application cloner with transaction CACS_CLONE |
| 103 | No process information found for application &1 |
| 104 | Process steps of application &1 |
| 105 | Table filter is active |
| 106 | Instantiating commission application &1 |
| 107 | Application eraser: process was started |
| 108 | Deleting commission application &1 |
| 109 | Deleting table entries of transaction data from application &1 |
| 110 | Deleting data from table &1 |
| 111 | &2 entries deleted from table &1 - WHERE condition '&3' |
| 112 | Error while deleting entries of table &1 |
| 113 | Deleting application logs from commission application &1 |
| 114 | Deleting application log &1 &2 &3 |
| 115 | Deleting copy service from commission application &1 |
| 116 | Deleting transaction data |
| 117 | Master data will be deleted |
| 118 | Deleting master data entries from commission application &1 |
| 119 | Deleting PD-ORG assignments from commission application &1 |
| 120 | &1 PD-ORG assignment(s) deleted |
| 121 | Deleting condition records from commission application &1 |
| 122 | Deleting condition record &1 (condition type &2) |
| 123 | Error while deleting condition record &1 from table &2 |
| 124 | Deleting cross-client entries from commission application &1 |
| 125 | Deleting client-specific data |
| 126 | Deleting number ranges from commission application &1 |
| 127 | Deleting cross-client data |
| 128 | Deleting generation of commission application |
| 129 | Deleting cross-client entries from commission application &1 |
| 130 | Internal error in process step control |
| 131 | Deleting entries of conditions table &1 |
| 132 | Cannot delete client assignment &1 of commission application &2 |
| 133 | Deleting client assignment of commission application |
| 134 | Commission application will be deleted |
| 135 | Error while deleting commission application &2 from table &1 |
| 136 | Commission application &1 is not used in client &2 |
| 137 | Client &1 is defined as "productive" |
| 138 | Client &1 does not exist |
| 139 | You can only delete separately |
| 140 | Deleting generated objects from commission application &1 |
| 141 | Deleting generated views |
| 142 | Generated view &1 cannot be deleted |
| 143 | Generated view &1 was successfully deleted |
| 144 | Deleting generated tables and structures |
| 145 | Generated view &1 does not exist on database |
| 146 | Generated table &1 does not exist on database |
| 147 | Cannot delete generated table &1 |
| 148 | Generated table &1 was deleted successfully |
| 149 | Deleting DataSources |
| 150 | Generated DataSource &1 does not exist on database |
| 151 | Generation object &1 &2 does not exist |
| 152 | Check if generated objects are empty |
| 153 | Generated (construction) objects will be deleted |
| 154 | Generated objects can only be deleted in productive mode |
| 155 | Deletion of generated tables - generation level "&1" |
| 156 | Generated table type &1 does not exist on database |
| 157 | Cannot delete generated table type &1 |
| 158 | Generated table type &1 was successfully deleted |
| 159 | Deleting generated table type &1 (for table &2) |
| 160 | Cannot delete generated program &1 |
| 161 | Deleting generated programs |
| 162 | Generated program &1 does not exist |
| 163 | Program &1 was successfully deleted |
| 164 | Deleting generated function groups |
| 165 | Generated function group &1 does not exist |
| 166 | Cannot delete generated function group &1 |
| 167 | Generated function group &1 was successfully deleted |
| 168 | Deleting generated classes/interfaces |
| 169 | Generated classes/interfaces &1 do not exist |
| 170 | Unexpected class type '&1' for class &2 |
| 171 | Cannot delete generated class/interface &1 |
| 172 | Generated class/interface &1 was successfully deleted |
| 173 | Cloning cross-client data; generation will follow |
| 174 | Application language &1 does not match process language &2 |
| 175 | Generated table &1 will be deleted |
| 176 | Foreign key relationships will be deleted |
| 177 | Cannot delete foreign key relationships for table &1 |
| 178 | Generation of application can only be executed alone |
| 179 | Tables will be emptied for package &1 |
| 180 | Package &1 is not assigned to application &2 |
| 181 | Package builder will be started |
| 182 | Commission application &1 will be used to create package &2 |
| 183 | Entries for package &1 will be deleted |
| 184 | Package &1 is invalid |
| 185 | Package &1 will be generated |
| 186 | Entries for package &1 will be created |
| 187 | Cross-client entries for package &1 will be created |
| 188 | Client-specific entries for package &1 will be created |
| 189 | Master data entries for package &1 will be created |
| 190 | Transaction data entries will be created for package &1 |
| 191 | Entries for table &1 will be copied from application &2 to package &3 |
| 192 | &1 entries were copied |
| 193 | Key for entry &1 |
| 194 | Entries can only be transported for productive run |
| 195 | Generated table &1 will be ignored |
| 196 | Transport entry is not specified |
| 197 | Transport entry &1 is specified |
| 198 | Entries in table TCACS_DESFIELDS will be checked |
| 199 | Source structure &1 (in TCACS_DESFIELDS) does not exist |
| 200 | Number range object & would have been deleted for all applications |
| 201 | Missing authorization for user &1 for RFC (Module: &2) |