SAP ABAP Message Class CACSTGT (Commissions: Target Agreements)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ CACST4 (Package) ICM: Target Agreements Application
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ CACST4 (Package) ICM: Target Agreements Application
Attributes
Message class | CACSTGT | |
Short Description | Commissions: Target Agreements | |
Changed On | 20110908 | |
Last Changed At | 174940 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 001 | No selection made | The short text describes the object sufficiently | |
3 | 002 | Terminated by user | The short text describes the object sufficiently | |
4 | 003 | Contract &1 &2 not found - Start: effective &3 technical &4 | The short text describes the object sufficiently | |
5 | 004 | No versions of contract &1 &2 found | The short text describes the object sufficiently | |
6 | 005 | No classific.types for target type &1 &2 - start: effective &3 techn. &4 | The short text describes the object sufficiently | |
7 | 006 | Classification type &1 &2 not found - Start: effective &3 technical &4 | The short text describes the object sufficiently | |
8 | 007 | No field name is determined for classification type &1 &2 | The short text describes the object sufficiently | |
9 | 008 | Field &1 for classification type &2 &3 not defined in metastructure &4 | The short text describes the object sufficiently | |
10 | 009 | LOS not found for classification type &1 &2 - Start: effect. &3 techn. &4 | The short text describes the object sufficiently | |
11 | 010 | System error while calling &1 target &2 - message &3 | The short text describes the object sufficiently | |
12 | 011 | No implementation for BAdI: &1 | The short text describes the object sufficiently | |
13 | 012 | BAdI definition &1 cannot be created | The short text describes the object sufficiently | |
14 | 013 | No target rule found for contract &1 &2 and target type &3 - on &4 | The short text describes the object sufficiently | |
15 | 014 | No target rule - target type &1 &2 classification GUID &3 | The short text describes the object sufficiently | |
16 | 015 | Error while getting CS application | The short text describes the object sufficiently | |
17 | 016 | Unexpected tab page type &1 | The short text describes the object sufficiently | |
18 | 017 | You have not assigned an application | The short text describes the object sufficiently | |
19 | 018 | Error while determining commit counter: appl. &1 table &2 process &3 | The short text describes the object sufficiently | |
20 | 019 | Run log cannot be written to table CACS_TGTRNJO | The short text describes the object sufficiently | |
21 | 020 | Contract &1 &2 cannot be locked for target type &3 | The short text describes the object sufficiently | |
22 | 021 | Invalid period rule &1 &2 - Start: effective &3 technical &4 | The short text describes the object sufficiently | |
23 | 022 | No periods found for period rule &1 &2 version &3 | The short text describes the object sufficiently | |
24 | 023 | Inconsistent period rule; target rule &1, last processed rule &2 | The short text describes the object sufficiently | |
25 | 024 | Required field &1 (&3) is not defined in structure &2 | The short text describes the object sufficiently | |
26 | 025 | Actual value field is not defined in structure &1 | The short text describes the object sufficiently | |
27 | 026 | Target value field is not defined in structure &1 | The short text describes the object sufficiently | |
28 | 027 | Actual value: &1 field defined without a correct actual value field | The short text describes the object sufficiently | |
29 | 028 | Target value: &1 defined without a correct target value field | The short text describes the object sufficiently | |
30 | 029 | Cap: &1 field defined without a correct actual value field | The short text describes the object sufficiently | |
31 | 030 | Threshold value: &1 field defined without a correct actual value field | The short text describes the object sufficiently | |
32 | 031 | Elementary target &1 &2 not defined in TCACS_TGS for &3 and &4 | The short text describes the object sufficiently | |
33 | 032 | Elementary target &1 &2 has invalid type &3 | The short text describes the object sufficiently | |
34 | 033 | Elementary target &1 &2 is of type &3, without a correct actual value | The short text describes the object sufficiently | |
35 | 034 | Complex target &1 &2 is not defined in TCACS_TGT for &3 and &4 | The short text describes the object sufficiently | |
36 | 035 | Complex target &1 &2 has no assignment in TCACS_TGA for &3 and &4 | The short text describes the object sufficiently | |
37 | 036 | Complexity &1 is not supported for target agreements | The short text describes the object sufficiently | |
38 | 037 | No implementation found for BAdI &1 application &2 | The short text describes the object sufficiently | |
39 | 038 | Elementary trgt &1 not assigned to complex trgt &2: effect. &3 techn. &4 | The short text describes the object sufficiently | |
40 | 039 | Application is mandatory | The short text describes the object sufficiently | |
41 | 040 | Object type class is mandatory | The short text describes the object sufficiently | |
42 | 041 | LOS not found for business object category &1 &2 method &3 start &4 | The short text describes the object sufficiently | |
43 | 042 | Data was saved | The short text describes the object sufficiently | |
44 | 043 | Unexpected version status "&1" encountered | The short text describes the object sufficiently | |
45 | 044 | Unexpected Error | The short text describes the object sufficiently | |
46 | 045 | Versioning error "&1" - a versioning message will follow | The short text describes the object sufficiently | |
47 | 046 | A proposal was defaulted sucessfully | The short text describes the object sufficiently | |
48 | 047 | No proposal can be defaulted | The short text describes the object sufficiently | |
49 | 048 | Unchanged target types are not saved | The short text describes the object sufficiently | |
50 | 049 | Serious update error | The short text describes the object sufficiently | |
51 | 050 | Initialization is incomplete | The short text describes the object sufficiently | |
52 | 051 | No permitted units for elementary target &1 &2 - effective &3 techn. &4 | The short text describes the object sufficiently | |
53 | 052 | Unit &1 is not permitted for elementary target type &2 | The short text describes the object sufficiently | |
54 | 053 | Document header (DOCHDM) is not available in valuation | The short text describes the object sufficiently | |
55 | 054 | Value can be determined dynamically | The short text describes the object sufficiently | |
56 | 055 | No authorization to maintain values in target agreements | The short text describes the object sufficiently | |
57 | 056 | No authorization to simulate in target agreements | The short text describes the object sufficiently | |
58 | 057 | No authorization to maintain target agreements | The short text describes the object sufficiently | |
59 | 058 | No display authorization in target agreements | The short text describes the object sufficiently | |
60 | 059 | No target value found for elementary target type &1 &2 | The short text describes the object sufficiently | |
61 | 060 | Total weighting is not 100% (&1%) for complex tgt type &2 from &3 to &4 | The short text describes the object sufficiently | |
62 | 061 | No log exists | The short text describes the object sufficiently | |
63 | 062 | Enter a target type for determining the period rule | The short text describes the object sufficiently | |
64 | 063 | Target agreements only use absolute valuation; check valuation type &1 | The short text describes the object sufficiently | |
65 | 064 | Target type &1 is being processed for contract &2 and period rule &3 | The short text describes the object sufficiently | |
66 | 065 | Complex target type (CTGTTYPE) is not defined as a field in &1-CAS | The short text describes the object sufficiently | |
67 | 066 | No target value exists for calculation rule &1 &2 | The short text describes the object sufficiently | |
68 | 067 | Error in BAdI &1 implementation for application &2 calculation rule &3 | The short text describes the object sufficiently | |
69 | 068 | Error in BAdI &1 implementation for application &2 target value &3 | The short text describes the object sufficiently | |
70 | 069 | Error in BAdI &1 implementation for application &2 field name &3 | The short text describes the object sufficiently | |
71 | 070 | Complex tgt type &1 invalid in target evaluation for complex tgt type &2 | The short text describes the object sufficiently | |
72 | 071 | Elementary tgt type &1 is invalid in tgt eval. for complex tgt type &2 | The short text describes the object sufficiently | |
73 | 072 | Period rule &1 is invalid in target evaluation - period rule &2 expected | The short text describes the object sufficiently | |
74 | 073 | Period number &1 invalid in target evaluation - period no. &2 expected | The short text describes the object sufficiently | |
75 | 074 | Amounts are not permitted in quantity targets | The short text describes the object sufficiently | |
76 | 075 | Quantities are not permitted in amount targets | The short text describes the object sufficiently | |
77 | 076 | Valuation inconsistency - subobject &1 &2 does not exist | The short text describes the object sufficiently | |
78 | 077 | RFC-enabled function modules not permitted for target agreements | The short text describes the object sufficiently | |
79 | 078 | Required entry field &1 is not defined for subobject table | Space: object requires documentation | |
80 | 079 | Document posting for &1-DOCOBJ must be switched on | Space: object requires documentation | |
81 | 080 | Business partner is missing in target evaluation metastructure | The short text describes the object sufficiently | |
82 | 081 | Unexpected versioning error "&1" | The short text describes the object sufficiently | |
83 | 082 | More than one active version of target rule read | The short text describes the object sufficiently | |
84 | 083 | Correct the described error | The short text describes the object sufficiently | |
85 | 084 | Target rule ID can only be specified for external number assignment | The short text describes the object sufficiently | |
86 | 085 | Target rule ID is mandatory for external number assignment | The short text describes the object sufficiently | |
87 | 086 | Target rule already exists in the database | The short text describes the object sufficiently | |
88 | 087 | Select only one header to be inserted | The short text describes the object sufficiently | |
89 | 088 | Error in ALV tree control | The short text describes the object sufficiently | |
90 | 089 | Do not select any header to be deleted | The short text describes the object sufficiently | |
91 | 090 | Generic target rules not permitted for complex target type &1 | The short text describes the object sufficiently | |
92 | 091 | Trigger type &1 &2 is invalid at effective time-spot &3 | The short text describes the object sufficiently | |
93 | 092 | No complex target types assigned to trigger type &1 &2 | The short text describes the object sufficiently | |
94 | 093 | Different time periods for target type and trigger type; see long text | Space: object requires documentation | |
95 | 094 | Target rule ID is missing | The short text describes the object sufficiently | |
96 | 095 | No authorization to process target rules - target type &1 activity &2 | The short text describes the object sufficiently | |
97 | 096 | Invalid processing mode &1 for authorization check | The short text describes the object sufficiently | |
98 | 097 | No valid trigger type found for complex target type &1 and contract &2 | The short text describes the object sufficiently | |
99 | 098 | Error in calculation of target achievement level for elementary target &1 | The short text describes the object sufficiently | |
100 | 100 | Structure &1 is not defined in DDIC | The short text describes the object sufficiently | |
101 | 101 | Classification type &1 has no field name definition | The short text describes the object sufficiently | |
102 | 102 | Field name &1 is not defined in structure &2 | The short text describes the object sufficiently | |
103 | 103 | Error while reading fields of structure &1 | The short text describes the object sufficiently | |
104 | 104 | Serious error while creating metastructure of &1 and &2 | The short text describes the object sufficiently | |
105 | 105 | Structure &1 has no fields | The short text describes the object sufficiently | |
106 | 106 | Invalid command "&1" | The short text describes the object sufficiently | |
107 | 107 | No entry found to be deleted | The short text describes the object sufficiently | |
108 | 108 | No entry found to be changed | The short text describes the object sufficiently | |
109 | 109 | Entry for insertion already exists | The short text describes the object sufficiently | |
110 | 110 | A processing error has occurred | The short text describes the object sufficiently | |
111 | 111 | Enter a target type | The short text describes the object sufficiently | |
112 | 112 | Target agreement for target type &1 and period &2/&3 | The short text describes the object sufficiently | |
113 | 113 | Tgt achievement lvl &1 &2 for complex valuation &3 reached (tgt type &4) | The short text describes the object sufficiently | |
114 | 114 | Contra item (knock-out) &1 &2 calculated for complex valuation &3 | The short text describes the object sufficiently | |
115 | 115 | Multiplication (knock-out) &1 &2 used for complex valuation &3 | The short text describes the object sufficiently | |
116 | 116 | Level of target achievement after applying knock-out amounts to &1 &2 | The short text describes the object sufficiently | |
117 | 117 | Level of target achievement &1 &2 reached for valuation &3 (tgt type &4) | The short text describes the object sufficiently | |
118 | 118 | Level of target achievement &1 &2 reached for complex valuation &3 | The short text describes the object sufficiently | |
119 | 119 | Function module &1 is obsolete | The short text describes the object sufficiently | |
120 | 120 | Program &1 is obsolete | The short text describes the object sufficiently | |
121 | 121 | Valuation &1 &2 was calculated | The short text describes the object sufficiently | |
122 | 122 | Invalid business object category &1 - effective start &2 | The short text describes the object sufficiently | |
123 | 123 | Subobject structure for business object category &1 is inconsistent | The short text describes the object sufficiently | |
124 | 124 | No triggering method exists in application &1 for object type &2 | The short text describes the object sufficiently | |
125 | 125 | Several units of measure were found for target agreement values | Space: object requires documentation | |
126 | 126 | Several currencies were found for target agreement values | Space: object requires documentation | |
127 | 127 | Cannot determine end of period | The short text describes the object sufficiently | |
128 | 200 | Checking complex target &1 for application &2 | The short text describes the object sufficiently | |
129 | 201 | &1 not yet determined | The short text describes the object sufficiently | |
130 | 202 | Effective end &1 is before effective start &2 | The short text describes the object sufficiently | |
131 | 203 | Target start &1 is not start &2 of period (&3) for rule &4 | The short text describes the object sufficiently | |
132 | 204 | Target end &1 is not end &2 of period (&3) for rule &4 | The short text describes the object sufficiently | |
133 | 205 | Target type &1 &2 cannot be generated as an active version exists | The short text describes the object sufficiently | |
134 | 206 | Invalid object kind (entity) &1 for portfolio assignment | The short text describes the object sufficiently | |
135 | 207 | Invalid object type &1 for portfolio assignment | The short text describes the object sufficiently | |
136 | 208 | Invalid effective date &1 for portfolio assignment | The short text describes the object sufficiently | |
137 | 209 | Invalid technical date &1 for portfolio assignment | The short text describes the object sufficiently | |
138 | 210 | Invalid language &1 for portfolio assignment | The short text describes the object sufficiently | |
139 | 211 | Technical error in portfolio assignment | The short text describes the object sufficiently | |
140 | 212 | No contract assignments found in portfolio assignment | The short text describes the object sufficiently | |
141 | 213 | No values for segment type &1 in portfolio assignment | The short text describes the object sufficiently | |
142 | 214 | No PFO segment type for classification type &1 defined | The short text describes the object sufficiently | |
143 | 215 | No portfolio assignment role defined for classification type &1 | The short text describes the object sufficiently | |
144 | 216 | No value for contract &1 &2 classif.type &3 in portfolio assignment | The short text describes the object sufficiently | |
145 | 217 | Table maintenance &1 | The short text describes the object sufficiently | |
146 | 218 | Enter field name for classification type | The short text describes the object sufficiently | |
147 | 219 | Function is not required for ICM classification | The short text describes the object sufficiently | |
148 | 220 | Default portfolio assignment values not defined for comn ctrct category | The short text describes the object sufficiently | |
149 | 221 | Default portfolio assignment values not defined for comn contract type | The short text describes the object sufficiently | |
150 | 222 | No role for portfolio assignment determined | The short text describes the object sufficiently | |
151 | 223 | No segment type for portfolio assignment determined | The short text describes the object sufficiently | |
152 | 224 | Role &1 and segment type &2: Combination not defined in portf.assignment | The short text describes the object sufficiently | |
153 | 225 | Subset: Application &1 | The short text describes the object sufficiently | |
154 | 226 | Specify a category for the classification type | The short text describes the object sufficiently | |
155 | 227 | No tool for classification category &1 &2 | The short text describes the object sufficiently | |
156 | 228 | Specify a complex target type | The short text describes the object sufficiently | |
157 | 229 | Specify an elementary target type | The short text describes the object sufficiently | |
158 | 230 | Complex target period rule &1 does not match elementary target period &2 | The short text describes the object sufficiently | |
159 | 231 | Subset: Application &1 and object type class &2 | The short text describes the object sufficiently | |
160 | 232 | Invalid date selection, you must include the selection | The short text describes the object sufficiently | |
161 | 233 | Period &1 not found for period rule &2 &3 | The short text describes the object sufficiently | |
162 | 234 | Period not found for key date &1 period rule &2 &3 version &4 | The short text describes the object sufficiently | |
163 | 235 | Serious error while generating commission case | The short text describes the object sufficiently | |
164 | 236 | Target agreement run: run number &1 - runtime &2 | The short text describes the object sufficiently | |
165 | 237 | *** T E S T R U N *** | The short text describes the object sufficiently | |
166 | 238 | Processing target type &1 for contract &2 | The short text describes the object sufficiently | |
167 | 239 | Error in update of log for target type &1 contract &2 run number &3 | The short text describes the object sufficiently | |
168 | 240 | *** U P D A T E R U N *** | The short text describes the object sufficiently | |
169 | 241 | No commission cases exist for resetting | The short text describes the object sufficiently | |
170 | 242 | Commission case being created for target type &1 contract &2 period &3 &4 | The short text describes the object sufficiently | |
171 | 243 | Resetting of commission case for target type &1 contract &2 period &3 &4 | The short text describes the object sufficiently | |
172 | 244 | Commission case &1 &2 &3 does not exist in database | The short text describes the object sufficiently | |
173 | 245 | Commission case &1 &2 &3 already reset | The short text describes the object sufficiently | |
174 | 246 | No target agreement run for application &1 run number &2 | The short text describes the object sufficiently | |
175 | 247 | Key date or run number must be filled (last run date) | The short text describes the object sufficiently | |
176 | 248 | No target agreement run for application &1 run number &2 key date &3 | The short text describes the object sufficiently | |
177 | 249 | No target agreement run for application &1 key date &2 | The short text describes the object sufficiently | |
178 | 250 | Only the last run can be reversed; the last run is &1 &2 | The short text describes the object sufficiently | |
179 | 251 | Commission contract does not exist for commission case participant | The short text describes the object sufficiently | |
180 | 252 | Name of complex target type &1 &2 is not available | The short text describes the object sufficiently | |
181 | 253 | Name of elementary target type &1 &2 is not available | The short text describes the object sufficiently | |
182 | 254 | No data exists for resetting of target agreement run &1 &2 | The short text describes the object sufficiently | |
183 | 255 | Inconsistent periodicity of complex target type &1 &2 | The short text describes the object sufficiently | |
184 | 256 | Business object category is missing for complex target type &1 &2 | The short text describes the object sufficiently | |
185 | 257 | Complex target type &1 &2 is locked | The short text describes the object sufficiently | |
186 | 258 | Elementary target &1 is not permitted | The short text describes the object sufficiently | |
187 | 259 | Enter a unit of measure | The short text describes the object sufficiently | |
188 | 260 | &1 not defined as a currency | The short text describes the object sufficiently | |
189 | 261 | &1 not defined as unit of measure | The short text describes the object sufficiently | |
190 | 262 | Enter a currency | The short text describes the object sufficiently | |
191 | 263 | Enter the effective start date | The short text describes the object sufficiently | |
192 | 264 | Enter the effective end date | The short text describes the object sufficiently | |
193 | 265 | You cannot maintain target rule individually AND generically at same time | The short text describes the object sufficiently | |
194 | 266 | Target rule is mandatory for generic maintenance | The short text describes the object sufficiently | |
195 | 267 | Target rule start date is mandatory for generic maintenance | The short text describes the object sufficiently | |
196 | 268 | Target rule end date is mandatory for generic maintenance | The short text describes the object sufficiently | |
197 | 269 | A period must be specified for correction value processing | The short text describes the object sufficiently | |
198 | 270 | Specifications of value types are hidden | The short text describes the object sufficiently | |
199 | 271 | Effective start date &1 must be before period start &2 | The short text describes the object sufficiently | |
200 | 272 | Effective start date &1 must equal target rule start date &2 | The short text describes the object sufficiently | |
201 | 273 | Effective start &1 must equal elementary target type start &2 | The short text describes the object sufficiently | |
202 | 274 | Effective end &1 must be after period end &2 | The short text describes the object sufficiently | |
203 | 275 | Effective end &1 must equal target rule end &2 | The short text describes the object sufficiently | |
204 | 276 | Effective end &1 and elementary target type end &2 must be the same | The short text describes the object sufficiently | |
205 | 277 | An active entry already exists for elementary target type &1 | The short text describes the object sufficiently | |
206 | 278 | Simulation mode is not permitted for generic maintenance | The short text describes the object sufficiently | |
207 | 279 | You need to specify a period to process a commission contract | The short text describes the object sufficiently | |
208 | 280 | Name of classification type &1 &2 is not available | The short text describes the object sufficiently | |
209 | 281 | Simulation mode is not permitted for elementary maintenance | The short text describes the object sufficiently | |
210 | 282 | Target agreement run is completed | The short text describes the object sufficiently | |
211 | 283 | Commission log is being issued | The short text describes the object sufficiently | |
212 | 284 | Enter an amount (currency) | The short text describes the object sufficiently | |
213 | 285 | Enter a value (quantity) | The short text describes the object sufficiently | |
214 | 286 | Only the last period can be reversed for contract &1 and target type &2 | The short text describes the object sufficiently | |
215 | 287 | A serious error has occurred while resetting the commission case | The short text describes the object sufficiently | |
216 | 288 | Enter a value | The short text describes the object sufficiently | |
217 | 289 | Tool for target category &1 &2 is missing for method &3 | The short text describes the object sufficiently | |
218 | 290 | Elementary target type is assigned to more than one tgt admin. system | Space: object requires documentation | |
219 | 291 | Elementary target type &1 &2 is not assigned to a complex target type | The short text describes the object sufficiently | |
220 | 292 | Target type &1 "&2" - contract &3 "&4" | The short text describes the object sufficiently | |
221 | 299 | *** Rule Maintenance *** | The short text describes the object sufficiently | |
222 | 300 | Select a target type | The short text describes the object sufficiently | |
223 | 301 | A serious database error has occurred during update of target rule | The short text describes the object sufficiently | |
224 | 302 | Select a target rule | The short text describes the object sufficiently | |
225 | 303 | Complex valuation attr.of tgt agrmt specified relative to tgt assignment | The short text describes the object sufficiently | |
226 | 304 | Valuation type &1 &2 does not exist | The short text describes the object sufficiently | |
227 | 305 | Valuation type &1 &2 is not defined as being complex | The short text describes the object sufficiently | |
228 | 306 | Target rule already exists | The short text describes the object sufficiently | |
229 | 307 | Classification value does not match classification type | The short text describes the object sufficiently | |
230 | 308 | Text for target rule is missing | The short text describes the object sufficiently | |
231 | 309 | Start date for target rule is incorrect | The short text describes the object sufficiently | |
232 | 310 | End date for target rule is incorrect | The short text describes the object sufficiently | |
233 | 311 | Error when saving | The short text describes the object sufficiently | |
234 | 312 | Enter a classification type | The short text describes the object sufficiently | |
235 | 313 | Choose a classification value | The short text describes the object sufficiently | |
236 | 314 | A classification entry already exists | The short text describes the object sufficiently | |
237 | 315 | Target rule &1 is locked by &2 | The short text describes the object sufficiently | |
238 | 316 | Error while locking target rule &1 | The short text describes the object sufficiently | |
239 | 317 | Incorrect implementation of complex target type | The short text describes the object sufficiently | |
240 | 318 | Maintain periods for the target type for the selected period | The short text describes the object sufficiently | |
241 | 319 | First create complex target types | The short text describes the object sufficiently | |
242 | 322 | End date is before start date | The short text describes the object sufficiently | |
243 | 323 | Rule was deleted | The short text describes the object sufficiently | |
244 | 324 | Chosen start date is before validity start &1 of complex target type | The short text describes the object sufficiently | |
245 | 325 | Chosen end date is after validity end &1 of complex target type | The short text describes the object sufficiently | |
246 | 326 | No changes found | The short text describes the object sufficiently | |
247 | 327 | Classification type &1 not permitted for complex target type &2 | The short text describes the object sufficiently | |
248 | 331 | You are not authorized to display | The short text describes the object sufficiently | |
249 | 332 | You are not authorized to create | The short text describes the object sufficiently | |
250 | 333 | You are not authorized to delete | The short text describes the object sufficiently | |
251 | 334 | You are not authorized to change | The short text describes the object sufficiently | |
252 | 335 | You are not authorized to maintain actual/target values | The short text describes the object sufficiently | |
253 | 800 | Unexpected exception in &1 | The short text describes the object sufficiently | |
254 | 801 | Error while creating dynamic data for &1 | The short text describes the object sufficiently | |
255 | 802 | More than one (&1) version of table &2 read | The short text describes the object sufficiently | |
256 | 803 | No versions of table &1 for effective validity &2 to &3 for &4 | The short text describes the object sufficiently | |
257 | 899 | &1 &2 &3 &4 | The short text describes the object sufficiently |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 600 |