/SMB/CHECK_FRAMEWORK - Messages related to Check Framework
The following messages are stored in message class /SMB/CHECK_FRAMEWORK: Messages related to Check Framework.
It is part of development package /SMB/CHECK_FRAMEWORK in software component SV-CLD-FRM-APP. This development package consists of objects that can be grouped under "Consistency checks".
It is part of development package /SMB/CHECK_FRAMEWORK in software component SV-CLD-FRM-APP. This development package consists of objects that can be grouped under "Consistency checks".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Odata service &1 is not active |
| 001 | Productive client exists in the system. |
| 002 | System alias does not exist for service &1 |
| 003 | Local GUI not set to unicode page |
| 004 | Customer solution does not exist in the system |
| 005 | Developer key does not exist for the user |
| 006 | Set the default timeout for HTTP and HTTPS services to 300s or 600s |
| 007 | Initial phase in not Evaluate/In Progress |
| 008 | eCATT and CATT are not allowed |
| 009 | Changes to repository and cross-client customizing are not allowed |
| 010 | Language &1 is not installed in the system |
| 011 | User-specific documentation parameter not set for your user |
| 012 | RFC destination &1 maintained for target system &2 is not proper |
| 013 | RFC destination doesn't exist for target system &1 |
| 014 | Initial phase in Evaluate/In progress |
| 015 | OData service &1 is active |
| 016 | Customer solution is present in the system |
| 017 | Productive client does not exist in the system |
| 018 | Automatic changes and transport for client-specific objects allowed |
| 019 | ECATT and CATT are allowed |
| 020 | Changes to repository and cross-client customizing are allowed |
| 021 | The default timeout for HTTP and HTTPS services is set to 300s or 600s |
| 022 | System alias exist for service &1 |
| 023 | Local GUI is Set to unicode page |
| 024 | Developer key exists for the user |
| 025 | Documentation parameter exists |
| 026 | Language &1 is installed in the system |
| 027 | RFC destination &1 to target system present |
| 028 | Automatic changes and transport for client-specific objects not allowed |
| 029 | Variant saved successfully |
| 030 | Enter check variant |
| 031 | Please select atleast one check |
| 032 | Whitelist table doesn't exist in system. Can't perform the check |
| 033 | Table &1 of &2 activity &3 in solution &4 is present in whitelist table |
| 034 | Building block &1 has reference to local TDC &2 in the file &3 |
| 035 | Definition mismatch for file &1 of activity &2 in BB &3 |
| 036 | &1 |
| 037 | Different values for variant &1 in files &2 and &3 |
| 038 | Definition mismatch for file &1 of activity &2 in &3 |
| 039 | &1 |
| 040 | Variant name already exists |
| 041 | Tasks &1 &2 &3 &4 are circular referred. |
| 042 | Background job &1 has been scheduled. Check spool for the results |
| 043 | &1 : Checking &2 |
| 044 | All checks completed |
| 045 | ******** Check &1 started ******** |
| 046 | ******** Check &1 completed ******** |
| 047 | Duplicates found for variant &1 |
| 048 | Data saved |
| 049 | Duplicate check not be performed as more than 2 solutions were selected |
| 050 | Parameter &1 in file &2 has no/incorrect reference to central data |
| 051 | Mail sent |
| 052 | Data already present/not modified |
| 053 | The master data activity &1 should be marked as &3 |
| 054 | Error log is not present for logged in user |
| 055 | E-mail id's for BB owners not maintained |
| 056 | No error logs present to send mail |
| 057 | The filename &1 of activity &2 exists in multiple activities |
| 058 | Building block &1 of scope item &2 does not exist in scope item &3 |
| 059 | Table &1 with delivery class A is not transportable from Q to P system |
| 060 | Mandatory BB &1 not assigned to scope item &2 |
| 061 | Building block &1 is not in correct sequence, move from position &2 to &3 |
| 062 | No optional BB's assigned to activation group &1 in SI &2 |
| 063 | Table &1 belongs to activities whose demo flag status in not consistent |
| 064 | Scope Item &1 is not in correct sequence |
| 065 | Scope Item &1 should appear immediately after &2 |
| 066 | &1 appears at Sequence number &2 for the solution &3 |
| 067 | Unable to read the definition of the activity &1. |
| 068 | Master solution(DE cntry/reg. vers.) is not available to compare with &1 |
| 069 | Mandatory BB &1 will be assigned to scope item &2 |
| 070 | Building block &1 not maintained in BB overview list |
| 071 | Demo Data Changed for Solution &1, BB &2, Activity &3 |
| 072 | Building Block &1 of Scope item &2 Solution &3 has been updated |
| 073 | Building Block &1 of Scope item &2 Solution &3 has not been updated |
| 074 | Building Block sequence of scope item &1 solution &2 has been updated |
| 075 | Building Block sequence of scope item &1 solution &2 could not be updated |
| 076 | Sequence of Scope item &1 of the solution &2 is modified |
| 077 | Neither cntry/reg. version nor cross cntry/reg. version of BB &1 found |
| 078 | BB's &1 activation group &2 not assigned to scope item &3. |
| 079 | Scenario &1 of solution &2 cannot be changed |
| 080 | Circular Reference Error fixed for Solution &1, BB &2, Activity &3 |
| 081 | Scope item &1 is of different cntry/reg. vers.than that &3 of solution &2 |
| 082 | Scope item &1 does not have any country/region version |
| 083 | Solution uses non assigned scope item &1 |
| 084 | No changes detected, inst data reference consistency check skipped. |
| 085 | Buiding block &1 from &2 is not in correct sequence in solution |
| 086 | Mandatory BB &1 of &2 not assigned to scope item &3 |
| 087 | Kindly Enter Valid Solution ID |
| 088 | Record does not exist in configuration table |
| 089 | Activate the Customer Solution |
| 090 | Non key attribute values are different |
| 091 | File Does not exist in Current Customer Solution |
| 092 | No Data Found in Content file for this Service |
| 093 | No Discrepancies found between Content File and Configuration Tables |
| 094 | Ecatt &1 has changed parameters |
| 095 | Data doesn't exist in content file |
| 096 | FK table &1 with Delivery Class &2 is not present in solution &3 |
| 097 | Activation sequence is not maintained for the scope item &1 |
| 098 | &1&2 |
| 099 | Check for Scope item &1 was not executed because of missing master data |
| 100 | Scope Item &1 of Solution &2 has been updated |
| 101 | Scope Item &1 of Solution &2 could not be updated |
| 102 | Building Block &1 of Scope Item &2 of Solution &3 has been removed |
| 103 | Saving is disabled in this system |
| 104 | Invalid Namespace for field &1 |
| 105 | Value &1 Field &2 |
| 106 | Key field &1 is empty |
| 107 | Value &1 Field &2 |
| 108 | BB &1 of scope item &2 should not be assigned for country/region &3 |
| 109 | BB &1 will be unassigned from scope item &2 |
| 110 | &1 -> &2 -> &3 |
| 111 | Definiton not maintained for &1 |
| 112 | Value &1 not in partner namespace |
| 113 | Value &1 not in internal format |
| 114 | Value &1 not in external format |
| 115 | Unable to determine result. Conversion routine exception |
| 116 | Building Block &1 has been added to depreciated Scope Item &2 |
| 117 | Incorrect Buildng Block &1 has been assigned to depreciated Scope Item &2 |
| 118 | Cloud Building Block &1 assigned to On-Premise Scope Item &2 |
| 119 | On-Premise Building Block &1 assigned to Cloud Scope Item &2 |
| 120 | Cloud Building Block &1 will be unassigned from On-premise Scope Item &2 |
| 121 | On-Premise Building Block &1 will be unassigned from CLoud Scope Item &2 |
| 122 | Missing key fields for ecat &1 |
| 123 | IMG activity &1 and its Customizing object &2 is not in sync in Solution |
| 124 | Customizing object &1, Subobject &2 is not in sync in Solution Structure |
| 125 | BBID &1 for CheckTable &2 and BBID &3 for FK Table &4 are not in sequence |
| 126 | FK error detected: Table: &1 Fieldname: &2 CheckTable: &3 (FK Table) |
| 127 | FK error detected: Table: &1 Fieldname: &2 CheckTable: &3 (Check Table) |
| 128 | BB &1 / &2 assignmet to activation group is inconsistent in BB Overview |
| 129 | Parameter &1 in file &2 has no variant file reference to central data |