UPGBA_IMPANA - Messages used by Upgrade Impact Analysis
The following messages are stored in message class UPGBA_IMPANA: Messages used by Upgrade Impact Analysis.
It is part of development package STBX_DATA in software component BC-UPG-TLS-TLA. This development package consists of objects that can be grouped under "SUM Toolbox Data Provider".
It is part of development package STBX_DATA in software component BC-UPG-TLS-TLA. This development package consists of objects that can be grouped under "SUM Toolbox Data Provider".
Message Nr ▲ | Message Text |
|---|---|
| 001 | ------------------------------------------------------------------------- |
| 002 | &1 |
| 003 | &1&2 |
| 004 | &1&2&3 |
| 005 | &1&2&3&4 |
| 006 | User &1 is not authorised to executed report &2 |
| 007 | Report &1 started |
| 008 | Report &1 successfully finished |
| 009 | Report &1 finished with errors |
| 010 | Function &1 can only be executed by user DDIC |
| 011 | Error opening file &1 in DIR_PUT with subdirectory &2 |
| 012 | Error accessing file &1 with mode &2 |
| 013 | Access denied. File not opened correctly |
| 014 | Start writing file &1 |
| 015 | Finished writing file &1 |
| 016 | Identifying download path failed with RC &1 |
| 017 | Open file dialog for file &1 failed with RC &2 |
| 018 | TABL &1 SLT replication requires initial reload after rollback &2 |
| 019 | TABL &1 SLT replication has to be paused or suspended &2 &3 |
| 020 | Invalid scenario: &1 |
| 021 | Cannot identify current upgrade scenario |
| 022 | Select from table PUTTB_SHD failed |
| 023 | Follow the steps described in the ZDO SUM guide or contact SAP Support. |
| 024 | TABL &1 is a XCLA table but has SLT triggers on ref. system &2. &3 &4 |
| 025 | ZIP Index Error while extracting PUTTBSHD FILE |
| 026 | Zip Decompression Error while extracting PUTTBSHD FILE |
| 027 | Others Error while extracting PUTTBSHD FILE |
| 028 | Filepath is empty |
| 029 | File does not exist |
| 030 | Scenario does not match PUTTB_SHD file |
| 100 | No table classification results available |
| 101 | Cannot open file &1. Please provide statistics according to SAP Note &2 |
| 102 | Access denied for file &1 |
| 103 | Data format error occurred while processing file &1 |
| 104 | Security check failed for filename &1. Please select a different name |
| 105 | Ignoring this error might lead to business impact in production update |
| 106 | Data conversion or transfer of file &1 failed |
| 107 | Statistics file &1 does not contain any relevant tables |
| 108 | Statistics file &1 does not contain any evaluation periods |
| 112 | Unknown error while reading file &1 |
| 120 | Parameter &1 := &2 (default = &3) |
| 121 | Header data: &1 |
| 122 | Evaluated period: &1 &2 &3 &4 |
| 130 | Meta data for &1: &2 &3 &4 |
| 131 | Cloned tables sum up to a total size of &1 exceeding the threshold |
| 132 | Table &1 will be cloned, but has &2 trigger on ref. system &3 |
| 133 | Table &1 was not classified, but has &2 trigger on ref. system &3 |
| 134 | Summary: &1 |
| 200 | &1 will become read-only, but has &2 changes/day on ref. system &3 |
| 201 | &1 has &2 SLT triggers on ref. system &3, &4 |
| 202 | &1 has &2 non-SLT triggers on ref. system &3, but must not have any |
| 203 | &1 will be copied, but has size of &2 GB on ref. system &3 |
| 204 | &1 will be smart-switched, but has &2 changes/second on ref. system &3 |
| 205 | Log table for &1 will grow by up to &2 GB/day on ref. system &3 |
| 206 | Cannot determine log growth for table &1 |
| 207 | &1 will get comp. view, but has &2 changes/second on ref. system &3 |
| 208 | &1 will be recorded, but has &2 million changes/day on ref system &3 |
| 209 | &1 will be converted in uptime, but has size of &2 GB on ref. system &3 |
| 220 | &1 not classified despite &2 changes/day on ref. system &3 |
| 221 | &1 not classified despite size of &2 GB on ref. system &3 |
| 222 | &1 not classified despite &2 SLT trigger(s) on ref. system &3 |
| 223 | &1 not classified despite &2 non-SLT trigger(s) on ref. system &3 |
| 300 | Results might be flawed due to imports during eval. period on system &1 |
| 301 | Cloned tables on ref. system &1 require add. DB space of &2 GB |
| 302 | Log tables on ref. system &1 will grow by up to &2 GB/day |
| 303 | Change rate of all recorded tables sums up to &2 million changes/day |
| 310 | Tables to become Readonly..: &1 tab(s), &2 err(s), &3 warn(s), &4 info(s) |
| 311 | Tables have to be cloned: &1 tab(s), &2 err(s), &3 warn(s), &4 info(s) |
| 312 | Tables with change recording: &1 tab(s), &2 err(s), &3 warn(s), &4 infos |
| 313 | Tables with database triggers: &1 tab(s), &2 err(s), &3 warn(s), &4 infos |
| 314 | Tables without classification: &1 tab(s), &2 err(s), &3 warn(s), &4 infos |
| 315 | Tables to be smart-switched..: &1 tab(s), &2 err(s), &3 warn(s), &4 infos |
| 316 | Tables with compensation view: &1 tab(s), &2 err(s), &3 warn(s), &4 infos |
| 317 | Tables converted in uptime: &1 tab(s), &2 err(s), &3 warn(s), &4 info(s) |
| 400 | Read-only restriction on &1 is considered uncritical |
| 401 | &1 will not work on &2 due to read-only restriction on &3 |
| 402 | &1 cannot be changed on &2 due to read-only restriction on &3 |
| 403 | &1 to avoid business impact on &2 due to read-only restriction on &3 |