UPGBA - Upgrade compatible logging framework messages
The following messages are stored in message class UPGBA: Upgrade compatible logging framework messages.
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 | Report name ...: &1 |
| 006 | Log name ......: &1 |
| 007 | Start time ....: &1 &2 |
| 008 | End time ......: &1 &2 |
| 009 | The logfile name could not be generated |
| 010 | Logging Error: Message without message number and/or message ID provided |
| 011 | Invalid filename &1 |
| 012 | Logging Error: Filename "&1" longer than 32 characters |
| 013 | Logging Error: Log Message written at &1 without message type and/or ID |
| 014 | Logfile "&1" used for parallel process &2 and Package ID &3 |
| 015 | &1&2&3&4 |
| 016 | Logfile &1 already opened for this process |
| 017 | Abnormal termination at the log path, RC & |
| 018 | Error writing to file & |
| 019 | Logging Error: Cleanup operation can only be performed by the parent job |
| 020 | Duplicate instantiation of the logger class (LogID:&1, PID:&2, RUNID:&3) |
| 021 | The LogID value is empty. |
| 022 | Package ID: &1 is being processed |
| 023 | Error reading the Logfile &1 |
| 024 | Calling function module &1 with &2 parallel processes |
| 025 | === Start of process &1 log messages === |
| 026 | === End of process &1 log messages === |
| 027 | Error &2 from function module &1 |
| 028 | &1&2&3&4 |
| 029 | Invalid log message message with text "&1&2&3&4" raised |
| 030 | SQLexception was raised. Error code: &1 Error msg: &2 |
| 031 | Exception raised at &1, &2 line &3 |
| 032 | Logging Error: Message without severity and/or level provided |
| 033 | &1 &2 |
| 034 | &1 &2 &3 |
| 035 | &1 &2 &3 &4 |
| 036 | Starting to process package &1 at &2 &3 |
| 037 | Package &1 finished at &2 &3 |
| 038 | Package &1 finished at &2 &3 (runtime &4sec) |
| 039 | Process &1 started on host &2 work process &3 |
| 040 | Error retrieving lock information: &1 |
| 041 | Report name ...: &1 Component: &2 &3 |
| 050 | &1 |
| 051 | &1 &2 |
| 052 | &1 &2 &3 |
| 222 | Object R3TR &1 &2 (&3 &4) is still assigned to package |
| 303 | Object &1 &2 uses obsolete object &3 &4 |
| 500 | &1 started on &2 at &3 with number of tasks &4 |
| 501 | &1 finished successfully on &2 at &3 |
| 502 | &1 client &2 finished with error on &3 at &4 |
| 503 | SDM stops all migrations due to system failure or CPIC failure |
| 504 | &1: Records to be processed at start of migration: &2 |
| 505 | &1: Records still to be processed: &2 on &3 at &4 |
| 506 | &1: Records to be processed at end of migration: &2 |
| 507 | &1: Number of active tasks: &2 |
| 508 | See SAP note 2725109 describes how to analyse error during SDM Migration |
| 509 | SDM stops all migrations due to a migration error |
| 510 | &1: not started due to resource bottleneck |
| 511 | Start SDM Migration client &1 |
| 512 | Maximum number of concurrent SDM Migrations: &1 |
| 513 | &1: Troubleshooting: run SLG1 in client &2 with: |
| 514 | - object = SDMI_MIGRATION |
| 515 | - External ID = &1 |
| 516 | - Error Message: &1 |
| 517 | User &1 already exists in client &2 as SDMI stepuser |
| 518 | Generic user &1 already exists in client &2 |
| 519 | Generic user &1 registerd as SDMI stepuser for client &2 |
| 520 | Error: Registration of user &1 as SDMI stepuser failed for client &2 |
| 521 | Not found qualified migration for SUM |
| 522 | SDM stops all migrations due to exception of ssi on determining resources |
| 523 | SDM stops all migrations due to RFC Configuration Error: 0 RFC WP |
| 524 | SDM class is not found in active tasks |
| 525 | &1 does not migrate data at all after &2 tries on &3 at &4 |
| 526 | MIGR_FINISHED_CROSS_CLT of &1 finished with error on &2 at &3 |
| 527 | MIGR_FINISHED_CROSS_CLT &1 finished successfully on &2 at &3 |
| 528 | SDMI job for client &1 not found ((SY-SUBRC = &2) |
| 529 | Schedule SDMI event job for client &1 failed (see SLG1 - SDMI_MIGRATION) |
| 530 | Raise SDMI event for client &1 failed (SY-SUBRC = &2) |
| 531 | Raise SDMI event for client &1 was successful |
| 532 | &1 is set to error due to &2 |
| 533 | &1: not started after 3 attempts due to resource bottleneck |
| 534 | - It is a temporary issue or you could increase the number of resources |
| 535 | The responsible component for the migration error is &1 |
| 898 | No authorization for test execution |
| 899 | Insufficient authorization to execute the conversion program |