FSCY - Generierung von Deckungsringen- Flexibles StammdatenStruktur
The following messages are stored in message class FSCY: Generierung von Deckungsringen- Flexibles StammdatenStruktur.
It is part of development package FMTMP in software component PSM-FM-BU-CE. This development package consists of objects that can be grouped under "IS-PS: Automatic Generation of Cover Pools".
It is part of development package FMTMP in software component PSM-FM-BU-CE. This development package consists of objects that can be grouped under "IS-PS: Automatic Generation of Cover Pools".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Generation not possible; generic entries exist in BS &1/&2 |
| 002 | Special characters are not allowed in the first & positions |
| 003 | The partial lengths have to be shorter than the complete substring |
| 004 | Enter a valid schema for partial lengths |
| 010 | Making entries in rule no. & not allowed; only contains special char. + |
| 015 | The same rule was already entered as rule number & |
| 019 | Rule &1: Subdivision ID &2 is invalid for the commitment item |
| 020 | Rule &1: Subdivision ID &2 is invalid for the funds center |
| 021 | Rule &1: Subdivision ID &2 is invalid for the fund |
| 022 | Rule &1: Subdivision ID &2 is invalid for the functional area |
| 023 | Entry &2 is invalid for the funds center in rule &1 |
| 024 | Entry &2 is invalid for the fund in rule &1 |
| 025 | Entry &2 is invalid for the commitment item in rule &1 |
| 026 | Entry &2 is invalid for the functional area in rule &1 |
| 027 | Rule &1: Entering substring &2 of the commitment item is not permitted |
| 028 | Rule &1: Entering substring &2 of the funds center is not permitted |
| 029 | Rule &1: Entering substring &2 of the fund is not permitted |
| 030 | Rule &1: Entering substring &2 of the functional area is not permitted |
| 034 | Rule &1: Substring &2 is too short; enter &3 character |
| 035 | Rule &1: Substring &2 is too long; enter &3 character |
| 036 | Rule &1: Enter the subdivision ID of the commitment item first |
| 037 | Rule &1: Enter the subdivision ID of the funds center first |
| 038 | Rule &1: Enter the subdivision ID of the fund first |
| 039 | Rule &1: Enter the subdivision ID of the functional area first |
| 040 | Rule &1: Entry &3 for substring &2 of the commitment item is invalid |
| 041 | Rule &1: Entry &3 for substring &2 of the funds center is invalid |
| 042 | Rule &1: Entry &3 for substring &2 of the fund is invalid |
| 043 | Rule &1: Entry &3 for substring &2 of the functional area is invalid |
| 044 | Rule &1: Enter substring &2 of the commitment item |
| 045 | Rule &1: Enter substring &2 of the funds center |
| 046 | Rule &1: Enter substring &2 of the fund |
| 047 | Rule &1: Enter substring &2 of the functional area |
| 050 | Generation of cover pools not possible; no rules exist |
| 051 | Budget Memo &1 does not exist; Customizing entry missing |
| 052 | Customizing for budget memos does not exist |
| 053 | Enter a valid fiscal year |
| 060 | Expenditure cover pools created manually and automatically are deleted |
| 070 | Changing an existing functional area is not permitted |
| 072 | Enter substring &1 of the functional area |
| 073 | Enter the subdivision ID and substring of the functional area |
| 075 | Functional area & does not exist |
| 100 | Entry &1 is too long; enter &2 character |
| 101 | Entry &1 is too short; enter &2 character |
| 102 | Maximum of &1 character for the account assignment element exceeded |
| 103 | Make an entry with the correct lengths; possible lengths: &1 |
| 104 | Enter a valid length; maximum length is 10 |
| 105 | Sequence &2 already exists for subdivision ID &1 |
| 106 | Substring cannot be created; only &1 substrings are permitted |
| 107 | Entering character &1 for substring is not permitted |
| 108 | Enter a maximum of &2 as items for &1 |
| 110 | It is not possible to create a substring here; Customizing entry missing |
| 113 | Copying to table carried out correctly |
| 114 | Entry not copied, a value already exists |
| 120 | Cancelled by user |
| 121 | Entry &1 has invalid characters |
| 130 | Substring &1 does not exist; check your entries |
| 131 | Subdivision &1 is not completely defined |
| 135 | It is not possible to delete the subdivision ID; &1 is used in &2 |
| 136 | Changing the subdivision ID is not possible; &1 is used in &2 |
| 137 | Deleting the substring is not possible; &1 and &2 are used |
| 138 | Changing substring &1 is not possible; master data exists |
| 139 | Deleting the subdivision ID is not possible; delete the substrings first |
| 140 | Deactivating the subdivision for &1 is not permitted |
| 141 | Deactivation is not possible; subdivision IDs exist |
| 142 | Generating master data prevents deactivation |
| 150 | & & & & |
| 160 | Structure &1 does not exist |
| 161 | Substrings &1 do not exist |
| 162 | Concatenation causes a different result: &1 not equal to &2 |
| 170 | Activation not possible; mask for commitment item key active |
| 171 | You cannot change the separator after creating master data |
| 172 | Deactivation is not possible after creating master data |
| 173 | Enter a valid separator in Customizing |
| 175 | Subdivision is not active. Usage in BCS is not possible. |