/SMB/CENTRALDATA - Messages for Centraldata
The following messages are stored in message class /SMB/CENTRALDATA: Messages for Centraldata.
It is part of development package /SMB/CENTRAL_DATA in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Central data handling and references".
It is part of development package /SMB/CENTRAL_DATA in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Central data handling and references".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 001 | Centraldata for "&1" is currently locked by user &2 |
| 002 | Database error when modifying centraldata |
| 003 | Database error when deleting centraldata |
| 004 | Centraldata Entity with key &1 &2 &3 does not exist |
| 005 | Duplicate Folder Name &1 |
| 006 | Duplicate Sequential Number &1 |
| 007 | Type Assignment &1 &2 &3 does not exist |
| 008 | Data was changed. Save changes? |
| 009 | File &1 is currently locked by user &2 |
| 010 | A system failure occurred when locking file &1 |
| 011 | Centraldata entity &1 is already locked by user &2 |
| 012 | Change Centraldata Entity &1 to edit mode first |
| 013 | Variant ID &1 cannot be used for ID &2, already used by ID &3 |
| 014 | The ID &1 cannot be created in Centraldata Entity &2 (used by variant &3) |
| 015 | The limit of IDs for Centraldata &1 has been reached, no new IDs possible |
| 016 | SQL exception when changing centraldata: &1 |
| 017 | Change Recording is currently locked by user &1 |
| 018 | Change Recording could not be locked due to a system error |
| 019 | Centraldata ID &1 of entity &2 cannot be changed due to inconsistency |
| 020 | Centraldata ID &1 (variant &2) of &3 is activated and cannot be changed |
| 021 | Centraldata variant &1 does not exist and therefore cannot be changed |
| 022 | Variant ID &1 can only be changed once per request |
| 023 | ID &1 is used in multiple variants, but can only be used in one |
| 024 | ID &1 is already used in variant &2 |
| 025 | The variant &1 cannot be deleted because it is inconsistent |
| 026 | Saving is currently not possible, try again later (locked by &1) |
| 027 | The variant &1 cannot be deleted because it is used |
| 028 | Variant &1 does not exist and therefore cannot be deleted |
| 029 | Variant &1 is standard content and cannot be deleted |
| 030 | An error occurred during change recording: &1 |
| 031 | You cannot add an initial ID in central data |
| 032 | You cannot change an ID to an initial value |
| 033 | Central data &1 cannot be maintained due to an inconsistency in TDC &1 |
| 034 | Central data entity with Org Type ID &1 does not exist |
| 035 | An unknown central data error occurred |
| 036 | Prerequisites for Unlock Change Recording not fulfilled |
| 037 | ID &1 is not allowed (only numbers with maximum length &2 allowed) |
| 038 | ID &1 is not allowed (numbers/characters with maximum length &2 allowed) |
| 039 | Only character/numeric character data types are allowed for central data |
| 040 | TDC &1 saved |
| 041 | TDC &1 was changed. Save before exiting? |
| 042 | &1 cannot be referenced in &2 (create ticket on SV-CLD-FRM-INF) |
| 043 | Lower case in &1 is not allowed in entity &2 |
| 044 | Switched to display mode |
| 045 | Switched to change mode |
| 046 | &1 variant(s) deleted |
| 047 | Variant &1/ID &2 is not used in any country or region |
| 048 | Variant &1/ID &2 is only used in country/region &3 |
| 049 | Maintain solutions in /SMB/SCOPE |
| 050 | You cannot add a second client currency |
| 051 | No ID selected |
| 052 | The selected IDs are not used |
| 053 | Download &1 failed: &2 |
| 054 | Upload &1 failed: &2 |
| 055 | No column selected |
| 056 | File &1 contains duplicate variant &2, only first occurence processed |
| 057 | &1 deletions processed |
| 058 | &1 changes of IDs processed |
| 059 | &1 new IDs processed |
| 060 | Showing &1 variants matching your filter of total &2 |
| 061 | Variant &1 is not allowed as a customer variant |
| 062 | No folder specified |
| 063 | New Central Data Maintenance must not be used in this system |
| 064 | TDC &1 was changed. Save before importing from file? |
| 065 | Entry &1 of &2 |
| 066 | TDC &1 was changed. Save before reloading from database? |
| 067 | All ID's of TDC &1 are already in use/activated and cannot be changed |
| 068 | Centraldata TDC &1 with &2 is not supported here for ID &3 in solution &4 |
| 069 | Variant &1 does not exist |
| 070 | No conflicts for the selected ID |
| 071 | Variant &1 per solution |
| 072 | Solution &1 must not be the customer solution - correct system setup |
| 073 | Failed to create a reference to &1 in solution &2 in TDC &3 - result &4 |
| 074 | ID &1 does not exist in centraldata entity &2 |
| 075 | Entity &1 &2 &3 cannot be converted in an activated system |
| 076 | Programming error: Access to entity before conversion in same session |
| 077 | No authorization to display TDC &1 (required for centraldata), check SU53 |
| 078 | '&1' not found |
| 079 | Hit &1 of &2 |
| 080 | Unsupported call to PME DB implementation of central data APIs |
| 081 | Central data entity with filename &1 does not exist |
| 082 | No entity key provided |
| 083 | Synchronizing entity &1 &2 &3 |
| 084 | Entity &1 &2 &3 cannot be synchronized |
| 085 | No building blocks are in scope |
| 086 | Field &1 is not part of the definition for subobject &2 |
| 087 | Field &1 does not reference central data in subobject &2 |
| 088 | Errors occurred retrieving the definition for &1 &2 &3 &4 |
| 089 | The requested entity is not in scope |
| 090 | New variant &1 created for customer ID &2 |
| 091 | New variant &1 created for customer ID &2 after renaming variant &3 |
| 092 | Variant &1 remapped from &2 to &3 |
| 093 | &1 entries on runtime PME updated (archive &2) |
| 094 | Errors occurred in updating centraldata, messages added to log |
| 095 | Changes have been saved |
| 096 | Update installation data for Solution &1 File &2 Variant &3 Parameter &4 |
| 097 | Value is kept as &1, reference changed from &2 to &3 due to cust. adapt. |
| 098 | Checking lifecycle status |
| 099 | Last lifecycle status of all solutions is ok |
| 100 | Scoping or lifecycle errors in solution(s) prevent the synchronization |
| 101 | Go to /SMB/TRANS_HIST and check the status as well as the application log |
| 102 | Check for existing health checks |
| 103 | Do not proceed with Add New Cntry/Reg / Scope Extens. until this is fixed |
| 104 | There are no changes to be saved |
| 105 | IMG Activity &1 with cust. obj. &2 (type &3) and sobj. &4 is not in scope |
| 106 | TDC &1 (&2) with parameter &3 is not in scope |
| 107 | Invalid reference &1. Variant &2 does not exist in TDC. |
| 108 | Automatic repair not possible, not all other cust. sol. are active |
| 109 | Automatic repair is not possible, solution is not activated |
| 110 | Variant &1 does not exist in other customer solutions |
| 111 | Variant &1 is not created by Finetuning |
| 112 | Automatic repair not possible due to lifecycle status of solutions |
| 113 | Variant &1, value &2 is not consistent, repair not possible |
| 114 | Variant &1 added with value &2 to solution &3 |
| 115 | Last value of variant &1 in &2 was &3, not consistent with &4 |
| 116 | Variant &1 was not added, instead variant &2 for value &3 |
| 117 | Error saving changes in &1, changes rolled back |