S_CMI_ACT_CHK - Message class for Activation checks
The following messages are stored in message class S_CMI_ACT_CHK: Message class for Activation checks.
It is part of development package S_CMI_ACTIVATION_CHECKS in software component BC-INS-TC-CMI. This development package consists of objects that can be grouped under "CBC Pre-Staging (Old, Client Independent)".
It is part of development package S_CMI_ACTIVATION_CHECKS in software component BC-INS-TC-CMI. This development package consists of objects that can be grouped under "CBC Pre-Staging (Old, Client Independent)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No data to process FK checks |
| 001 | Error while populating staging table |
| 002 | Error while fetching the staging details |
| 003 | Error while inserting the data into staging table |
| 004 | Error while inserting the data into pre-staging table |
| 005 | Successfully populated pre-staging table |
| 006 | No data available in pre-staging for processing for client &1 |
| 007 | Error while parsing the XML string |
| 008 | &1 Records have been inserted successfully in staging table. |
| 009 | Exception raised while loading data into pre-staging, check log |
| 010 | Exception while triggering Multiplexer: &1 |
| 011 | Populated pre-staging data and triggered process for activation |
| 012 | No authorization for Object &1; Activity &2 |
| 013 | No records to check for Fk errors |
| 014 | Data for table &1 not available in the system to perform Fk checks |
| 015 | FK check completed succesful for table &1 field &2 |
| 016 | Exception raised while triggering Task List execution. Check log |
| 017 | Task List name missing. |
| 018 | Assigning a Run ID was not possible. |
| 019 | Call to &1 failed; return code &2 |
| 020 | Chunk &1 was written into Pre-Staging Table |
| 021 | Error while inserting the data into staging table for chunk &1 |
| 022 | Chunk &1 succesfully overwritten |
| 023 | &1 Chunks are still missing |
| 024 | Errorneous Activity &1. No Entry written into Pre Staging Table. |
| 025 | Error. No content was parsed from JSON / XML |
| 026 | Duplicate Keys during Insert into Staging Table. &1 Duplicates |
| 027 | Error while populating Pre-Staging. No Staging ID provided |
| 028 | Upgrade process triggered for staging ID &1 |
| 029 | Upgrade chunk &1 was written into Pre-Staging Table |
| 030 | Not Cloud Environment. No Changes made to SCMI_PRE_STAGING |
| 031 | Error while modyfing the SCMI_PRE_STAGING_TABLE. No changes made |
| 032 | Not Fine Tuning Data. No Changes made to SCMI_PRE_STAGING. |
| 033 | Process stopped. Wrong or missing Client Type, Check SCMI_CLIENT_INFO |
| 034 | No Data was inserted into Pre-Staging Table. |
| 035 | No Records were inserted into Staging Table. |
| 036 | No data was inserted into Pre-Staging Table due to duplicate keys |
| 037 | Upgrade not triggered. Chunks are missing. |
| 038 | Upgrade was already triggere for Staging ID &1 Process stopped. |
| 039 | Upgrade not triggered. Status &1 of chunks not recognized. |
| 040 | Timeout. It was not possible to write Chunk. Pre-Staging is locked |
| 041 | System Error: It was not possible to set a lock to Pre-Staging table |
| 042 | No activation logs found in client; &1 &2 |
| 043 | No activation logs found; invalid client type settings |
| 044 | Activation status is initial |
| 045 | Activation error in processing |
| 046 | Pre-staging status; resync to CBC |
| 047 | Pre-staging status; finetuning |
| 048 | Pre-staging status; send finetuning |
| 049 | Pre-staging status; incomplete, some chunks are still missing |
| 050 | CBC Call was successful |
| 051 | CBC Call was not successful |
| 052 | No Result was returned during CBC Call |
| 053 | BackSync Phase. Client Type: &1 |
| 054 | Client Type could not be determined. Check SCMI_CLIENT_INFO |
| 055 | CBC returned the following messages &1&2&3&4 |
| 056 | Unsupported format |
| 057 | Paylod Header written for Staging ID &1 |
| 058 | Payload table entry written for Staging ID &1 |
| 059 | Staging Mode: &1 retrieved |
| 060 | All Chunks present and ready for Upgrade. |
| 061 | Data for Staging ID &1 is already present. No new entries inserted. |
| 070 | Prepare Client List for Multiplexer |
| 071 | Client &1 with Client Type &2 was scheduled for Multiplexer Run. |
| 072 | No suitable Client for Multiplexer Run was found. |
| 073 | &1 LM Chunks and &2 Prod Chunks are missing |
| 074 | &1 LM Chunks are missing |
| 075 | &1 Prod Chunks are missing |
| 076 | X-Chunk without LM JSON was sent |
| 077 | Z-Chunk without PROD JSON was sent |
| 078 | G-Chunk without LM JSON was sent |
| 079 | F-Chunk without PROD JSON was sent |
| 080 | The Activation process was already triggered |
| 081 | Unexpected Final Chunk Activity &1 found |
| 082 | Unexpected Activity: &1 |
| 083 | Client &1 has not suitable client type &2 for Prod Content |
| 084 | No Lifecycle Client present in system for LM Content |
| 085 | 1S4HC-Scenario: Client &1 was scheduled for Multiplexer Run |
| 090 | LM content is ignored in client specific mode. |
| 091 | LM content part of chunk ignored. Only Prod Content is written. |
| 101 | Chunk &1 arrived, but Pre-Stag Phase was already processed |