SAP ABAP Message Class JJ (IS-M/AM: Master Data)
Basic Data
Hierarchy
☛
IS-M (Software Component) SAP MEDIA
⤷ IS-M (Application Component) SAP Media
⤷ JAS (Package) Application development R/3 Publishing Advertising System***
⤷ IS-M (Application Component) SAP Media
⤷ JAS (Package) Application development R/3 Publishing Advertising System***
Attributes
Message class | JJ | |
Short Description | IS-M/AM: Master Data | |
Changed On | 20130531 | |
Last Changed At | 112515 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | & & & & | ||
2 | 001 | -------- 001 - 100 reserved for booking unit/publication messages | ||
3 | 002 | Booking unit & already exists | ||
4 | 003 | Booking unit & does not exist | Space: object requires documentation | |
5 | 004 | Please choose at least one valid item type | The short text describes the object sufficiently | |
6 | 005 | Booking unit & does not exist | ||
7 | 006 | Booking unit group & does not exist | ||
8 | 007 | Date-specific booking unit & from & does not exist | The short text describes the object sufficiently | |
9 | 008 | Reference BU is not of the same type | ||
10 | 009 | Booking unit & specified is not a basic booking unit | The short text describes the object sufficiently | |
11 | 010 | Error occured when creating booking unit & | The short text describes the object sufficiently | |
12 | 011 | Error occured when changing booking unit & | The short text describes the object sufficiently | |
13 | 012 | Error occured when deleting booking unit & | The short text describes the object sufficiently | |
14 | 013 | Error when reading BU grouping content & | ||
15 | 014 | No texts found for BU grouping content & in language & | ||
16 | 015 | Elements already exist for BU & | The short text describes the object sufficiently | |
17 | 016 | The booking unit & is not assigned to a planned production unit | The short text describes the object sufficiently | |
18 | 017 | No elements exist for template BU & | The short text describes the object sufficiently | |
19 | 018 | Please select at least one media type | The short text describes the object sufficiently | |
20 | 019 | Radio programs already exist as elements for BU & | The short text describes the object sufficiently | |
21 | 020 | The date specific booking unit & from & already exists | The short text describes the object sufficiently | |
22 | 021 | Planned PU & has already been entered as an element | The short text describes the object sufficiently | |
23 | 022 | Planned production unit & already exists | The short text describes the object sufficiently | |
24 | 023 | Error occured when reading planned production unit & | The short text describes the object sufficiently | |
25 | 024 | Period must be in the future | The short text describes the object sufficiently | |
26 | 025 | Entry &, &, ISSUE TYPE & & overlaps with the previous entry | ||
27 | 026 | Please specify publication, edition and at least one variant type | The short text describes the object sufficiently | |
28 | 027 | Production unit variant type is missing | The short text describes the object sufficiently | |
29 | 028 | From-date must fall before to-date. | The short text describes the object sufficiently | |
30 | 029 | No date specific booking unit exists for the selected interval | The short text describes the object sufficiently | |
31 | 030 | Error occured when creating planned production unit & | The short text describes the object sufficiently | |
32 | 031 | Error occured when changing planned production unit & | The short text describes the object sufficiently | |
33 | 032 | Error occured when deleting planned production unit & | The short text describes the object sufficiently | |
34 | 033 | Error occured when reading planned production unit & | The short text describes the object sufficiently | |
35 | 034 | Error occured when reading element & for issue & | The short text describes the object sufficiently | |
36 | 035 | No content components have been maintained for the planned prod. unit & | The short text describes the object sufficiently | |
37 | 036 | No content components have been maintained for the planned prod.unit & | The short text describes the object sufficiently | |
38 | 037 | Issues exist without elements | The short text describes the object sufficiently | |
39 | 038 | No issues were found | The short text describes the object sufficiently | |
40 | 039 | Please only select one line to expand | The short text describes the object sufficiently | |
41 | 040 | *------- Booking unit hierarchy-----------------------------------------* | ||
42 | 041 | No BU hierarchy of type & valid on & was found | ||
43 | 042 | The booking unit & is not a combination | The short text describes the object sufficiently | |
44 | 043 | Error in booking unit hierarchy of type &, valid on & | The short text describes the object sufficiently | |
45 | 044 | The booking unit & already exists in one of the sales hierarchy versions | ||
46 | 045 | BU & has already been entered as a lower level BU | The short text describes the object sufficiently | |
47 | 046 | Hierarchy of type &, version & was not found | ||
48 | 047 | No active BU hierarchy version found of type & in period & to & | ||
49 | 048 | BU hierarchy versions of type & in the period & to & are incomplete | The short text describes the object sufficiently | |
50 | 049 | Error in booking unit hierarchy type & version & | The short text describes the object sufficiently | |
51 | 050 | Type area width + gutter <= leaf width required | The short text describes the object sufficiently | |
52 | 051 | Type area height + header < Leaf height required | The short text describes the object sufficiently | |
53 | 052 | *-----------------BU content-------------------------------------------* | ||
54 | 053 | Content component & has already been assigned. Please only assign once | The short text describes the object sufficiently | |
55 | 054 | Entry PUVarType &, cont.comp. & with trans.period already exists | The short text describes the object sufficiently | |
56 | 055 | Entry & & with overlapping period already exists | ||
57 | 056 | Content component & does not exist in the & variant of BU & | The short text describes the object sufficiently | |
58 | 057 | Content component hierarchy from & is not in the given time period | The short text describes the object sufficiently | |
59 | 058 | Ad insert element & & & & already exists | The short text describes the object sufficiently | |
60 | 059 | No content components exist in booking unit & on & | ||
61 | 060 | Booking unit & is not published on the given dates | ||
62 | 061 | No issues were found in the period & to & | The short text describes the object sufficiently | |
63 | 062 | No valid publication date was selected | The short text describes the object sufficiently | |
64 | 063 | No production units exist for PPU & in the period & to & | The short text describes the object sufficiently | |
65 | 064 | No copy found for edition & & with copy number & | The short text describes the object sufficiently | |
66 | 065 | Both data as well as a from-date or a copy number were entered | The short text describes the object sufficiently | |
67 | 066 | Page/column format & does not exist | The short text describes the object sufficiently | |
68 | 067 | No production units were found in the period from & - & | The short text describes the object sufficiently | |
69 | 068 | &1 content component not published in &2 BU on the selected dates | Space: object requires documentation | |
70 | 069 | The valid-from date & is later than the valid-to date & | ||
71 | 070 | & & outside content component hierarchy version date & | ||
72 | 071 | Error occured when creating content components & | The short text describes the object sufficiently | |
73 | 072 | Error occured when changing content components & | The short text describes the object sufficiently | |
74 | 073 | Content component type & does not exist | The short text describes the object sufficiently | |
75 | 074 | Content component group & does not exist | The short text describes the object sufficiently | |
76 | 075 | Texts for content component type & in language & do not exist | ||
77 | 076 | Texts for content component group & in language & do not exist | The short text describes the object sufficiently | |
78 | 077 | Content components & already exist | The short text describes the object sufficiently | |
79 | 078 | Error occured when reading content comp. & | ||
80 | 079 | No content component hierarchy of type &, variant &, valid on & exists | The short text describes the object sufficiently | |
81 | 080 | Content component & does not have other subordinate content components | The short text describes the object sufficiently | |
82 | 081 | Error in content component hierarchy of type &, variant &, on & | The short text describes the object sufficiently | |
83 | 082 | Error in content component hierarchy of type &, version &, variant & | The short text describes the object sufficiently | |
84 | 083 | Error when reading content component hierarchy variant & of type & | The short text describes the object sufficiently | |
85 | 084 | No texts found for cont.comp.hierarchy variant & of type & in language & | The short text describes the object sufficiently | |
86 | 085 | Content component hierarchy type & does not exist | The short text describes the object sufficiently | |
87 | 086 | Text for content component hierarchy type & in language & does not exist | ||
88 | 087 | Cont.comp.hier.version (type: & / var: & / vers : &) does not exist | The short text describes the object sufficiently | |
89 | 088 | Cont.comp.hier.variant (type: & / var: & ) does not exist | The short text describes the object sufficiently | |
90 | 089 | Text for content component hierarchy (& /&) in language & does not exist | ||
91 | 090 | Error when creating object: & & & & | The short text describes the object sufficiently | |
92 | 091 | Error when changing object: & & & & | The short text describes the object sufficiently | |
93 | 092 | Error when deleting object: & & & & | The short text describes the object sufficiently | |
94 | 093 | SYST: Error when creating table: & | The short text describes the object sufficiently | |
95 | 094 | SYST: Error while changing. Table & | The short text describes the object sufficiently | |
96 | 095 | SYST: Error while deleting. Table & | The short text describes the object sufficiently | |
97 | 096 | SYST: Prohibited program status | The short text describes the object sufficiently | |
98 | 097 | Content component hierarchy of type &, variant & on & is not unique | The short text describes the object sufficiently | |
99 | 098 | & & is not in period for higher level | ||
100 | 099 | Please delete existing ad insert elements first | ||
101 | 100 | Template BU does not have same use | ||
102 | 101 | No alias exists for business partner & | ||
103 | 102 | Insufficient publication dates for the number required | Space: object requires documentation | |
104 | 103 | No text found for & in language & | ||
105 | 104 | Please do not enter a root, only a column, section or spec.publication | The short text describes the object sufficiently | |
106 | 105 | No production units found for selection criteria specified | ||
107 | 106 | 'Saleable from' must be before 'Saleable to' | The short text describes the object sufficiently | |
108 | 107 | No lower level booking units assigned | ||
109 | 108 | No edition elements were maintained | The short text describes the object sufficiently | |
110 | 109 | No & active with this variant | ||
111 | 110 | & already exists | The short text describes the object sufficiently | |
112 | 111 | & does not exist | ||
113 | 112 | Only one standard requirement type allowed | The short text describes the object sufficiently | |
114 | 113 | You have not defined a standard requirement type | The short text describes the object sufficiently | |
115 | 114 | Requirement type & has not been defined | ||
116 | 115 | BU contents (sales view) already exist - copying not possible | The short text describes the object sufficiently | |
117 | 116 | PPU contents (tech.view) do not exist - copying not possible | The short text describes the object sufficiently | |
118 | 117 | BU contents (sales view) not maintained in & - copying not possible | The short text describes the object sufficiently | |
119 | 118 | Difference in structural hierarchy variant - copying not possible | ||
120 | 119 | Difference in price hierarchy variant - copy will be made | ||
121 | 120 | Frequency rule & not found | The short text describes the object sufficiently | |
122 | 121 | No texts found for period unit rule & in language & | The short text describes the object sufficiently | |
123 | 122 | No issues matching & were found | The short text describes the object sufficiently | |
124 | 123 | BU contents (techn.view) already exist - copying not possible | The short text describes the object sufficiently | |
125 | 124 | BU contents (techn.view) not maintained in & - copying not possible | The short text describes the object sufficiently | |
126 | 125 | Booking unit & is still being used in a valid order | ||
127 | 126 | Booking unit &1 is not valid for item type &2 | Space: object requires documentation | |
128 | 127 | Booking unit &1 can no longer be sold on &2 | Space: object requires documentation | |
129 | 128 | Changing structure hierarchy variant not allowed -> see long text | ||
130 | 129 | No special publications exist in booking unit & | The short text describes the object sufficiently | |
131 | 130 | *-------------- BU date specification ------------------------------* | ||
132 | 131 | Date specification & does not exist | ||
133 | 132 | No texts found for date specification & in language & | ||
134 | 133 | Copying sub-tree was cancelled | The short text describes the object sufficiently | |
135 | 134 | Nodes do not exist in the hierarchy, copying is not possible | ||
136 | 135 | Please only select sub-trees with at least one lower level cont.comp. | ||
137 | 136 | First screen reached | Space: object requires documentation | |
138 | 137 | Final screen reached | Space: object requires documentation | |
139 | 138 | Please specify both the contract and the requirement | Space: object requires documentation | |
140 | 139 | Date rule &1 could not be read | Space: object requires documentation | |
141 | 140 | *--- Next 30 reserved for agent contract -------------------------------* | ||
142 | 141 | The element you entered already exists | ||
143 | 142 | No entries required in field '& (&)' | ||
144 | 143 | No entries allowed in field '& (&)' | ||
145 | 144 | The requirement you just entered already exists | ||
146 | 145 | Agent contract & was saved | ||
147 | 146 | Valid-to date should not be before valid-from date | ||
148 | 147 | When entering the VAT indicator you must maintain the country | ||
149 | 148 | Please specify a sales agent | Space: object requires documentation | |
150 | 149 | Specify a purchasing organization | Space: object requires documentation | |
151 | 150 | No created by data exists | ||
152 | 151 | Contract & already exists | ||
153 | 152 | Contract & does not exist | ||
154 | 153 | Contract & between purch.organization & and sales agent & already exists | ||
155 | 154 | Block unsuccessful: & requirements could not be copied | ||
156 | 155 | You do not have creation authorization in purchasing organization & | ||
157 | 156 | You do not have change authorization in purchasing organization & | ||
158 | 157 | You do not have display authorization in purchasing organization & | ||
159 | 158 | Please specify a requirement type | ||
160 | 159 | You do not have change authorization in sales area &/&/& | The short text describes the object sufficiently | |
161 | 160 | You do not have display authorization in sales area &/&/& | The short text describes the object sufficiently | |
162 | 161 | Booking unit &1 still references booking unit &2. | The short text describes the object sufficiently | |
163 | 162 | No (additional) entry was found | Space: object requires documentation | |
164 | 163 | Please specify at least one attribute value | Space: object requires documentation | |
165 | 164 | At least one requirement has an unsuitable validity period (long text) | Space: object requires documentation | |
166 | 165 | Short text is mandatory | Space: object requires documentation | |
167 | 166 | No contract exists with agent & in purchasing organization & | ||
168 | 167 | You must enter at least one inclusion element | ||
169 | 168 | Contract with number & is an occasional agent contract | ||
170 | 169 | No general agent settings found in table TJJA5 for client & | ||
171 | 170 | Only quantity dependent commission can be increased | ||
172 | 171 | Inclusive condition & for sales area & & & does not exist | ||
173 | 172 | Standard settings have not been maintained for purchasing organization & | ||
174 | 173 | Please enter a contract | ||
175 | 174 | No requirement type with content & and purchasing organization & found. | Space: object requires documentation | |
176 | 175 | Please select at least one sales area | ||
177 | 176 | Sales call reports cannot be requested without a sales activity type | ||
178 | 177 | The changed sales activity type has an effect on existing contracts | ||
179 | 178 | Elements already exist with advertiser &1 | ||
180 | 179 | Please place the cursor on a contract or sales agent | Space: object requires documentation | |
181 | 180 | *Booking units part 2--------------------------------------------------- | ||
182 | 181 | Error occurred while reading BU statistics group & | The short text describes the object sufficiently | |
183 | 182 | No text found for BU statistics group & in language & | The short text describes the object sufficiently | |
184 | 183 | No text found for local window group & in language & | The short text describes the object sufficiently | |
185 | 184 | Error occurred while reading positioning type & | ||
186 | 185 | No positioning data can be maintained for BU & at schedule line level | ||
187 | 186 | No positioning data can be maintained for BU & at sub-item level | ||
188 | 187 | No entries marked as relevant to generation | ||
189 | 188 | BU hierarchy type & not maintained in customizing | The short text describes the object sufficiently | |
190 | 189 | Hierarchy type & and version & already exist - copying not possible | The short text describes the object sufficiently | |
191 | 190 | No production units exist for the plan.PU & with the copy no. & | The short text describes the object sufficiently | |
192 | 191 | The PU on & for the planned prod.unit & does not have the copy number & | ||
193 | 192 | Please specify publication and edition | The short text describes the object sufficiently | |
194 | 193 | You are not authorized to & booking unit & | ||
195 | 194 | You are not authorized to & ad insert & division & | ||
196 | 195 | Entry & & already exists | The short text describes the object sufficiently | |
197 | 196 | Change content per IsVar.type/PU variant type not allowed -> see long txt | ||
198 | 197 | Booking unit & is marked for deletion | ||
199 | 198 | Booking unit & is marked for deletion | ||
200 | 199 | Error when reading booking unit hierarchy (type &, version &,&/&) | ||
201 | 200 | * 200 - 240 individual maintenance of content components | ||
202 | 201 | Content component & does not exist (please check your entry) | ||
203 | 202 | Content component $ already exists | ||
204 | 203 | Content component $ flagged for deletion | ||
205 | 204 | Content component $ marked for deletion | ||
206 | 205 | Template content component $ does not exist | ||
207 | 206 | There should be at least one use for each content component | ||
208 | 207 | Cont.component w/o sales area restriction: Cannot access sales area scrn | ||
209 | 208 | Sales area $/$/$ does not exist. Please check your entry | ||
210 | 209 | Sales area $/$/$ already created for content component | ||
211 | 210 | Sales area $/$/$ not created for content component | ||
212 | 211 | Sales areas will be deleted if cont.comp.is valid for all sales areas | ||
213 | 212 | Update error while creating content component & | ||
214 | 213 | Update error while changing content component & | ||
215 | 214 | Update error while deleting content component & | ||
216 | 215 | Inconsistencies determined in sales areas for content component & | ||
217 | 216 | Error while deleting sales areas for content component & | ||
218 | 217 | Content component & was deleted | ||
219 | 218 | Content component & was created | ||
220 | 219 | Content component & was changed | ||
221 | 220 | Content component cannot be deleted in dialog | The short text describes the object sufficiently | |
222 | 221 | Content component & has already been blocked by user & | ||
223 | 222 | Content components have already been blocked by user & | ||
224 | 223 | Content component & cannot be deleted, it is used in the hierarchy | The short text describes the object sufficiently | |
225 | 224 | No content component & exists below content component & | ||
226 | 225 | Root & is not of the "root node" type | The short text describes the object sufficiently | |
227 | 226 | Content components of the 'root node' type cannot be copied | ||
228 | 227 | The new content component cannot be of the 'root node' type | ||
229 | 228 | Content comp.hier. has already been locked by user & | ||
230 | 229 | No content components exist in the area selected | ||
231 | 230 | Identical cont.components exist more than once on the first hier.level | ||
232 | 231 | Identical content components exist more than once in a sub tree | ||
233 | 232 | You are not authorized to & content component & | ||
234 | 233 | You are not authorized to & content component hierarchies | ||
235 | 234 | Content compoents cannot be deleted. They are used in BUs | The short text describes the object sufficiently | |
236 | 235 | There is no space in the booking unit & on the dates determined | ||
237 | 236 | Error occurred when interpreting date information | Space: object requires documentation | |
238 | 237 | Booking unit &1 is not valid for the current sales area &2/&3/&4 | Space: object requires documentation | |
239 | 238 | Production unit & already exists for basic booking unit & on & | Space: object requires documentation | |
240 | 239 | PU & with copy number & already exists for basic booking unit & | Space: object requires documentation | |
241 | 240 | Production units update not necessary | Space: object requires documentation | |
242 | 241 | * 241 - 280 Collective entry/processing of content components | ||
243 | 242 | Unauthorized call up of collective entry/processing of content components | ||
244 | 243 | Entry without content component identification not allowed | The short text describes the object sufficiently | |
245 | 244 | Entry without content component type not allowed | The short text describes the object sufficiently | |
246 | 245 | Content component & does not exist in the selection entries | ||
247 | 246 | Content component & already exists. Creation not allowed | The short text describes the object sufficiently | |
248 | 247 | Entry without content component short text not allowed | The short text describes the object sufficiently | |
249 | 248 | Sales area details are only allowed for a selected content component | ||
250 | 249 | Cursor is positioned on a blank line. Sales area details not possible | ||
251 | 250 | Content component & in collective entry is not unique. Please correct | ||
252 | 251 | Cursor position invalid. Sales area details and doc. mgmt not possible | Space: object requires documentation | |
253 | 252 | No sales area exists for the selection entries | ||
254 | 253 | Please select content components before executing the function | ||
255 | 254 | Cursor is positioned on a blank line. Content compts cannot be deleted | ||
256 | 255 | Cursor positioned incorrectly. Content component cannot be deleted | ||
257 | 256 | An error occured when deleting the sales area for the content components | The short text describes the object sufficiently | |
258 | 257 | Content components were created | The short text describes the object sufficiently | |
259 | 258 | Content components were changed | The short text describes the object sufficiently | |
260 | 259 | Update error when creating content components | The short text describes the object sufficiently | |
261 | 260 | Update error when changing content components | The short text describes the object sufficiently | |
262 | 261 | No content components exist for the selection entries | ||
263 | 262 | No external number assignment set up. Collective entry not possible | ||
264 | 263 | Please maintain short text or long text | The short text describes the object sufficiently | |
265 | 264 | Content component does not exist as a first level node in the hierarchy | ||
266 | 265 | Content component & already exists in the given hierarchy | ||
267 | 266 | If booking unit update is required, please enter templates | ||
268 | 267 | Templates/booking unit/content component do not exist | ||
269 | 268 | No date-specific template booking unit/content components exist | ||
270 | 269 | Service performance dates could not be determined from calendar &1 | Space: object requires documentation | |
271 | 270 | Planned circulation quantities for &1/&2 cannot be moved from &3 to &4 | Space: object requires documentation | |
272 | 271 | Date-specific capacities for &1 cannot be moved from &2 to &3 | Space: object requires documentation | |
273 | 272 | Planned circulation quantities for &1/&2 moved from &3 to &4 | Space: object requires documentation | |
274 | 273 | Date-specific capacity for &1 moved from &2 to &3 | Space: object requires documentation | |
275 | 274 | The system only supports the day and month units | The short text describes the object sufficiently | |
276 | 281 | * 281 - 320 Content component hierarchy | ||
277 | 282 | Unauthorized call up of content component hierarchy maintenance/display | ||
278 | 283 | Cursor positioned incorrectly. Please position on content component | The short text describes the object sufficiently | |
279 | 284 | Displaying/processing content component hier.is currently unavailable | The short text describes the object sufficiently | |
280 | 285 | Cont.comp.hier. for type: &, var.: &, vers.: & already exists | The short text describes the object sufficiently | |
281 | 286 | Cont.comp.hier.for type: &, var.: &, vers.: & does not exist | ||
282 | 287 | Update error when deleting cont.comp.hier (type &, var.&, vers.&) | ||
283 | 288 | Content component hierarchy for type: & , vers.: & was saved | The short text describes the object sufficiently | |
284 | 289 | Error when saving cont.comp.hier.for type: &, var.: & ,vers.: & | The short text describes the object sufficiently | |
285 | 290 | Content component hierarchy for type: &, vers.: & was deleted | The short text describes the object sufficiently | |
286 | 291 | Error when deleting cont.comp.hier.for type: &, var.: &, vers.: & | The short text describes the object sufficiently | |
287 | 292 | Entries for copy template (type/variant/version) must be complete | The short text describes the object sufficiently | |
288 | 293 | Structural hier.type requires structural cont.components as root nodes | The short text describes the object sufficiently | |
289 | 294 | Hier.type rel.to pricing requires pricing cont.comp. as root nodes | The short text describes the object sufficiently | |
290 | 295 | Statistical hier.type requires statistical cont.comps as root nodes | The short text describes the object sufficiently | |
291 | 296 | No hierarchy exists for template (type &, var. &, vers. &) | The short text describes the object sufficiently | |
292 | 297 | Template(type &, var. &, vers. &) is inconsistent. Please inform per.res. | The short text describes the object sufficiently | |
293 | 298 | Root node & is assgnd at a lower lev. in the template (ty.& var.& vers.&) | ||
294 | 299 | Content component & is not a structural content component | Space: object requires documentation | |
295 | 300 | CComp & has no structural use. Hierarchy level 2 not allowed | ||
296 | 301 | CComp & not used for price. Hierarchy level 2 not allowed | ||
297 | 302 | CComp & does not have statistical use. Hierarchy level 2 not allowed | ||
298 | 303 | Content component & is a root node. Deletion is not allowed | The short text describes the object sufficiently | |
299 | 304 | There are cont.comps on level 2 of the hierarchy template w/o.struct. use | ||
300 | 305 | There are cont.comps on lev. 2 of the hier. template, not used for price | ||
301 | 306 | There are cont.comps on level 2 of the hierarchy template w/o.stat.use | ||
302 | 307 | Template (type &, var.&, vers.&) has repeated use. Not allowed here | ||
303 | 308 | Please only select end nodes in the hierarchy | The short text describes the object sufficiently | |
304 | 309 | Please only select nodes from the first level | The short text describes the object sufficiently | |
305 | 310 | Please do not select roots in the hierarchy | The short text describes the object sufficiently | |
306 | 311 | Special publications not at level 2 of the structural hierarchies | Space: object requires documentation | |
307 | 312 | CC hierarchy is inconsistent: Node & not available for end node & | The short text describes the object sufficiently | |
308 | 321 | * 321 - 340 Maintain service material | Space: object requires documentation | |
309 | 322 | Update error when creating service number & | The short text describes the object sufficiently | |
310 | 323 | Update error when changing service number & | The short text describes the object sufficiently | |
311 | 324 | Update error when deleting service number & | The short text describes the object sufficiently | |
312 | 325 | Service & does not exist | The short text describes the object sufficiently | |
313 | 326 | Service & is marked for deletion. It cannot be edited | The short text describes the object sufficiently | |
314 | 327 | Quantity for service & does not exist | The short text describes the object sufficiently | |
315 | 328 | Service & already exists in table & | The short text describes the object sufficiently | |
316 | 329 | Service & has been marked for deletion | The short text describes the object sufficiently | |
317 | 330 | No tax classification exists for service & | The short text describes the object sufficiently | |
318 | 331 | No tax classification exists for tax type & | The short text describes the object sufficiently | |
319 | 332 | Tax classification has not been maintained | The short text describes the object sufficiently | |
320 | 333 | Country already exists for service (Please check entries) | The short text describes the object sufficiently | |
321 | 334 | Country does not exist for service (Please check entries) | The short text describes the object sufficiently | |
322 | 335 | Service type & does not exist | The short text describes the object sufficiently | |
323 | 336 | You have no authorization to & service & | ||
324 | 337 | Contract & has been flagged for deletion | Space: object requires documentation | |
325 | 338 | Contract & has been flagged for deletion | Space: object requires documentation | |
326 | 339 | Product hierarchy & has been flagged for deletion | Space: object requires documentation | |
327 | 340 | Product hierarchy & has been selected for deletion | Space: object requires documentation | |
328 | 341 | Advertiser & has been flagged for deletion | Space: object requires documentation | |
329 | 342 | Advertiser & has been selected for deletion | Space: object requires documentation | |
330 | 343 | Agency & has been flagged for deletion | Space: object requires documentation | |
331 | 344 | Agency & has been selected for deletion | Space: object requires documentation | |
332 | 345 | Service & has been selected for deletion | Space: object requires documentation | |
333 | 346 | Service & has been flagged for deletion | Space: object requires documentation | |
334 | 347 | Advertiser & is blocked | Space: object requires documentation | |
335 | 348 | Agency & is blocked | Space: object requires documentation | |
336 | 360 | &1 &2 could not be deleted from requirement &4 in sales agent contract &3 | Space: object requires documentation | |
337 | 361 | * 361 - 380 Maintenance view | ||
338 | 362 | Value has already been assigned in requirement type &. Please change | ||
339 | 363 | Enter a value | The short text describes the object sufficiently | |
340 | 364 | Value has already been assigned to field &. Please change | The short text describes the object sufficiently | |
341 | 365 | Please enter at least one value for the exclusion requirement | The short text describes the object sufficiently | |
342 | 366 | Entry is not unique | ||
343 | 367 | No authorization for activity & in sales area & & & | ||
344 | 368 | Only one default booking unit can be entered for BU &1 | Space: object requires documentation | |
345 | 380 | * 380 - 419 Business partner hierarchy | ||
346 | 381 | Specify a business partner | Space: object requires documentation | |
347 | 382 | Date & is invalid | ||
348 | 383 | From-date cannot be later than to-date | ||
349 | 384 | Error when creating business partner & | ||
350 | 385 | Same super/subordinate business partner not possible | ||
351 | 386 | The hierarchy node cannot be deleted | ||
352 | 387 | Please do not enter a percentage value equal to zero | ||
353 | 388 | Selected business partner does not exist | ||
354 | 389 | BP hierarchy has been locked by another user. Changes are not possible | ||
355 | 390 | System error when blocking tree | ||
356 | 391 | No business partner hierarchy exists for the key date & | Space: object requires documentation | |
357 | 392 | Please do not enter a percentage value greater than 100 | ||
358 | 393 | From-date is later than key date, rel.does not appear on current tree | ||
359 | 394 | From-date cannot be earlier than the selection date | ||
360 | 395 | Time slice already exists: Bpsub: & Dat_frm: & Dat_to & | ||
361 | 396 | TO_DATE must not be earlier than selection date | ||
362 | 397 | FROM_DATE is earlier than higher level relationship, new time slice | ||
363 | 398 | Changes cannot be made in the past | ||
364 | 399 | Time slice already exists: Bpsup: & Bpsub: & Dat_frm: & Dat_to & | ||
365 | 400 | The 'from date' must not be earlier than the selection date | ||
366 | 401 | Hierarchy type & not found in table & | The short text describes the object sufficiently | |
367 | 402 | Hierarchy type & with language & does not exist in table & | The short text describes the object sufficiently | |
368 | 403 | No relationship was selected | ||
369 | 404 | The BP cannot be selected | ||
370 | 405 | The validity period of the lower level elements was adjusted | ||
371 | 406 | Validity period is not between &1 and &2 | ||
372 | 407 | Value &1 is not allowed in data field &2 | ||
373 | 408 | Standard contract indicator caanot be selected | ||
374 | 409 | Field &1 is a checkbox | ||
375 | 410 | The field &1 is not an agent contract field | ||
376 | 411 | No contract was updated | ||
377 | 412 | The validity period of the elements was adjusted | ||
378 | 413 | The element validity is outside the requirement validity | ||
379 | 414 | The BP hierarchy is currently being modified. Display possible only | The short text describes the object sufficiently | |
380 | 415 | Your selection does not contain any elements for the evaluation | Space: object requires documentation | |
381 | 416 | Validity end &2 defined for &1 elements | Space: object requires documentation | |
382 | 417 | Elements overlap: Insertion is not possible (long text) | Space: object requires documentation | |
383 | 418 | Elements in the clipboard have a different requirement type (long text) | Space: object requires documentation | |
384 | 421 | Do not maintain agency attributes unless the agency indicator is set | The short text describes the object sufficiently | |
385 | 422 | Make sure that the COA indicator is set before maintaining COA attributes | The short text describes the object sufficiently | |
386 | 423 | Agency type must be entered if the agency indicator is selected | ||
387 | 450 | * 450 - 470 Format definitions | ||
388 | 451 | Page format & does not exist | ||
389 | 452 | Fixed format for page/column format & and format proposal & not found | ||
390 | 470 | * Technical system | ||
391 | 471 | Error calling the technical system with destination & | ||
392 | 472 | System error in technical system | ||
393 | 473 | No editor maintained for design ad type & and BU & | ||
394 | 474 | Cannot read front-end ID | ||
395 | 475 | No destination maintained for technical system &1 and front-end ID &2 | ||
396 | 476 | BU grouping positioning system & does not exist | ||
397 | 477 | The technical interface has not been maintained in the current clients | ||
398 | 478 | No order update system was found for sales area &/&/& | ||
399 | 479 | No destination has been maintained for technical system & | ||
400 | 480 | No technical system has been maintained for positioning information | ||
401 | 500 | * Batch input PAM screens in JAM | ||
402 | 501 | & & does not exist in table & | ||
403 | 502 | & & not allowed | ||
404 | 503 | If agency indicator is not selected, field & should be initial | ||
405 | 504 | Only numeric entries allowed in field & | The short text describes the object sufficiently | |
406 | 505 | Business partner already exists in table JJTVM ( database error) | The short text describes the object sufficiently | |
407 | 529 | * 530 - 550 Maintain master data for contact person | ||
408 | 530 | Contact person & for business partner & does not exist | Space: object requires documentation | |
409 | 531 | Contact person & is already being edited | The short text describes the object sufficiently | |
410 | 532 | Please enter ref.BP number or the contact person name | The short text describes the object sufficiently | |
411 | 533 | Date is in the future | The short text describes the object sufficiently | |
412 | 534 | Inadmissible time period | The short text describes the object sufficiently | |
413 | 535 | Assign number from the critical area | The short text describes the object sufficiently | |
414 | 536 | Assign last number in range | The short text describes the object sufficiently | |
415 | 537 | Number range & has not been defined for object & | The short text describes the object sufficiently | |
416 | 538 | Error in insert tab & ( RC= &) | ||
417 | 539 | Error in update tab & ( RC = &) | ||
418 | 540 | Form of address key does not exist | The short text describes the object sufficiently | |
419 | 541 | Contact person is not a person according to the form of address key | The short text describes the object sufficiently | |
420 | 542 | Update of contact person & performed successfully | The short text describes the object sufficiently | |
421 | 543 | Business address /private address have already been entered | The short text describes the object sufficiently | |
422 | 544 | Start and end date are compulsory | The short text describes the object sufficiently | |
423 | 545 | Contact & is flagged for deletion | Space: object requires documentation | |
424 | 546 | Contact & has a deletion indicator | Space: object requires documentation | |
425 | 547 | Contact person & does not exist | Space: object requires documentation | |
426 | 548 | Private and/or business address has not been created | The short text describes the object sufficiently | |
427 | 549 | End date is earlier than start date | The short text describes the object sufficiently | |
428 | 550 | Publication / edition & / & does not exist | The short text describes the object sufficiently | |
429 | 551 | Fill all entry fields | The short text describes the object sufficiently | |
430 | 552 | Only natural persons are admissible as reference business partners | The short text describes the object sufficiently | |
431 | 553 | Address with number & for contact person does not exist | The short text describes the object sufficiently | |
432 | 554 | Business address does not exist | The short text describes the object sufficiently | |
433 | 555 | Private address does not exist | The short text describes the object sufficiently | |
434 | 556 | Specify a contact | Space: object requires documentation | |
435 | 557 | Business partner & does not have a contact | Space: object requires documentation | |
436 | 569 | * 570 - 620 Sales activity maintenance | ||
437 | 570 | Sales activity type & is not defined | The short text describes the object sufficiently | |
438 | 571 | Reason for sales activity & is not defined | The short text describes the object sufficiently | |
439 | 572 | Sales activity outcome & is not defined | The short text describes the object sufficiently | |
440 | 573 | Sales activity status & is not defined | The short text describes the object sufficiently | |
441 | 574 | Outcome analysis & is not defined | The short text describes the object sufficiently | |
442 | 575 | Outcome analysis & is not allowed for customer outcome & | The short text describes the object sufficiently | |
443 | 576 | Sales activity status & (&) cannot be set manually | The short text describes the object sufficiently | |
444 | 577 | Sales activity status & (&) is only allowed for complete sales activities | The short text describes the object sufficiently | |
445 | 578 | Sales organization & does not exist | The short text describes the object sufficiently | |
446 | 579 | Distribution channel & is not defined | The short text describes the object sufficiently | |
447 | 580 | Division & is not defined | The short text describes the object sufficiently | |
448 | 581 | Sales office & is not defined | The short text describes the object sufficiently | |
449 | 582 | Sales group & is not defined | The short text describes the object sufficiently | |
450 | 583 | Enter a distribution channel and a division | The short text describes the object sufficiently | |
451 | 584 | Enter a division | The short text describes the object sufficiently | |
452 | 585 | Sales area & & & does not exist | The short text describes the object sufficiently | |
453 | 586 | Sales office & is not allowed for sales area & & & | The short text describes the object sufficiently | |
454 | 587 | Sales group & is not allowed for sales office & | The short text describes the object sufficiently | |
455 | 588 | Enter a sales office | The short text describes the object sufficiently | |
456 | 589 | The from-time & must be eariler than the to-time & | The short text describes the object sufficiently | |
457 | 590 | Enter a business partner | The short text describes the object sufficiently | |
458 | 591 | Contact person & does not exist for business partner & | The short text describes the object sufficiently | |
459 | 592 | Follow-up sales activity type & is not defined | The short text describes the object sufficiently | |
460 | 593 | Copying function & is not defined to follow & | The short text describes the object sufficiently | |
461 | 594 | Edit all incomplete fields | The short text describes the object sufficiently | |
462 | 595 | Specify a partner role | The short text describes the object sufficiently | |
463 | 596 | Please enter contact person /agent in another block | The short text describes the object sufficiently | |
464 | 597 | Partner & already exists for function & | The short text describes the object sufficiently | |
465 | 598 | Contact person & already exists | The short text describes the object sufficiently | |
466 | 599 | Media agent contract number & does not exist | The short text describes the object sufficiently | |
467 | 600 | Media agent contract requirement & for contract number & does not exist | The short text describes the object sufficiently | |
468 | 601 | Enter a sales activity number | The short text describes the object sufficiently | |
469 | 602 | Sales activity &1 is currently being processed by user &2 | Space: object requires documentation | |
470 | 603 | Sales activity & cannot be blocked | The short text describes the object sufficiently | |
471 | 604 | Sales activity & does not exist | The short text describes the object sufficiently | |
472 | 605 | You do not have an authorization to create a sales activity | The short text describes the object sufficiently | |
473 | 606 | You do not have an authorization to change sales activity & | The short text describes the object sufficiently | |
474 | 607 | You do not have an authorization to display sales activity & | The short text describes the object sufficiently | |
475 | 608 | Sales activity & has been added | The short text describes the object sufficiently | |
476 | 609 | Sales activity & has been changed | The short text describes the object sufficiently | |
477 | 610 | Media agent & with contract no & and condition & already exists | The short text describes the object sufficiently | |
478 | 611 | The date for follow-up sales activity & cannot be in the past | The short text describes the object sufficiently | |
479 | 612 | Enter a valid sales organization | ||
480 | 613 | Define the selection range for the addresses | The short text describes the object sufficiently | |
481 | 614 | Define the selection range for the customer/sales prospect | The short text describes the object sufficiently | |
482 | 615 | Cancel with return code = & during EXPORT of object & to database & | The short text describes the object sufficiently | |
483 | 616 | Selection was performed between & and & | The short text describes the object sufficiently | |
484 | 617 | Enter a customer or partner number | The short text describes the object sufficiently | |
485 | 618 | Do not enter a customer and partner number | The short text describes the object sufficiently | |
486 | 619 | Specify which address you want to use | The short text describes the object sufficiently | |
487 | 620 | Sales activity & is not a direct mailing, so it has no address list. | The short text describes the object sufficiently | |
488 | 621 | No addresses were selected | The short text describes the object sufficiently | |
489 | 622 | The requested range of addresses is already being processed | The short text describes the object sufficiently | |
490 | 623 | Error blocking & | The short text describes the object sufficiently | |
491 | 624 | The administrative data for the addresses is currently being processed | The short text describes the object sufficiently | |
492 | 625 | No addresses exist | The short text describes the object sufficiently | |
493 | 626 | No address changes have been made | The short text describes the object sufficiently | |
494 | 627 | No new addresses exist | The short text describes the object sufficiently | |
495 | 628 | Please use the values 'x' or ' ' for selection | The short text describes the object sufficiently | |
496 | 629 | Select the lines you want to process | ||
497 | 630 | No output has been issued for & | The short text describes the object sufficiently | |
498 | 631 | The selected addresses have been copied | The short text describes the object sufficiently | |
499 | 632 | The address was not found in the current address area | The short text describes the object sufficiently | |
500 | 633 | The address has been copied | The short text describes the object sufficiently | |
501 | 634 | The address has already been selected | The short text describes the object sufficiently | |
502 | 635 | Invalid selection: All and open sales activity | The short text describes the object sufficiently | |
503 | 636 | Entry & does not exist (Please check) | The short text describes the object sufficiently | |
504 | 637 | & & & & | The short text describes the object sufficiently | |
505 | 638 | Agent '&' does not exist | The short text describes the object sufficiently | |
506 | 639 | Please remove the standard indicator in contract &1 first | ||
507 | 640 | Place cursor on a contract | ||
508 | 641 | Please select at least one contract | ||
509 | 642 | Place cursor on a requirement | ||
510 | 643 | Select one or more requirements | Space: object requires documentation | |
511 | 644 | You cannot delete this data since follow-up activities exist | The short text describes the object sufficiently | |
512 | 645 | According to USER EXIT checks, the sales activity cannot be deleted | The short text describes the object sufficiently | |
513 | 646 | Sales activity & has been deleted | The short text describes the object sufficiently | |
514 | 647 | Please create business partner & as a partner | The short text describes the object sufficiently | |
515 | 648 | Partner role & cannot be deleted here | The short text describes the object sufficiently | |
516 | 649 | Text for sales activity type & does not exist in language & | The short text describes the object sufficiently | |
517 | 650 | * Media agent requirement types | ||
518 | 651 | The field catalog does not contain the allowed signs: &1 | The short text describes the object sufficiently | |
519 | 652 | The field catalog is too short with &1 entries | The short text describes the object sufficiently | |
520 | 653 | The field catalog is too long with &1 entries | The short text describes the object sufficiently | |
521 | 654 | Field &1 was not found | The short text describes the object sufficiently | |
522 | 655 | Field &1 has not been defined | The short text describes the object sufficiently | |
523 | 656 | Internal error: Invalid placement combination: '&1', '&2', '&3' | The short text describes the object sufficiently | |
524 | 657 | Contract req. &: commission key &: No text exists in language & | The short text describes the object sufficiently | |
525 | 658 | The sales agent code ID & does not exist | ||
526 | 659 | No condition type has been maintained in the customizing table TJJ73 | ||
527 | 660 | No entries exist in the system table TJJ75 | ||
528 | 661 | Contract req. &/& was excluded due to missing inclusions | The short text describes the object sufficiently | |
529 | 662 | Requirement type &1: Will be skipped due to missing entries | ||
530 | 663 | Requirement type &1: Required field &2: The field is initial | ||
531 | 664 | Requirement type &1: Required field &2: The table is initial | ||
532 | 665 | Requirement type &1: &2 valid contract requirements | ||
533 | 666 | Requirement type &1: &2 suitable contract req. without inclusive element | ||
534 | 667 | Requirement type &1: &2 contract req.to be checked with excluded element | ||
535 | 668 | Requirement type &1: &2 excluded contract requirements | ||
536 | 669 | Requirement type &1: &2 assigned contract requirements | Space: object requires documentation | |
537 | 670 | Contract req. &1: No longer found | ||
538 | 671 | Field &1 = &2 | ||
539 | 672 | Field &1(&2) = &3 | ||
540 | 673 | Field &1: The field is initial | ||
541 | 674 | Field &1: The table is initial | ||
542 | 675 | Field &1(&2): The entry is initial | ||
543 | 676 | Manual assignment: Agent &1, contract type &2, renumeration &3 | ||
544 | 677 | Contract requirement &1: Check manual sales agent assignment: Level: &2 | Space: object requires documentation | |
545 | 678 | Automatic agent determination is being performed | ||
546 | 679 | Contract req.&1: Validity start date &2 after &3 | ||
547 | 680 | Contract req.&1: Validity end date &2 before &3 | ||
548 | 681 | Contract req. &1: Invalid commission category: &2 | ||
549 | 682 | Default order data | ||
550 | 683 | Contract req. &1: The assignment was deleted due to errors | ||
551 | 684 | Contract req. &1: Assignment is correct and will be retained | ||
552 | 685 | Requirement type &1: &2 suitable contract req.without element | ||
553 | 686 | Further checking of requirement types not performed due to cancel.indic. | ||
554 | 687 | Contract req. &1: Check manual change | ||
555 | 688 | Please enter date or delete time | ||
556 | 689 | Contract req.&1: Requirement type &2 no longer exists. | ||
557 | 690 | Contract & is already being processed by another user | ||
558 | 691 | Contract req. &1: No sales activity found | ||
559 | 692 | Contract req. &1/sales activity &2: Start of validity period &3 before &4 | ||
560 | 693 | Contract req. &1/sales activity &2: End of validity period &3 before &4 | ||
561 | 694 | Contract Req. &1/Sales act.&2: SAct.type &3 is not suitable for SAt.ty.&4 | ||
562 | 695 | Contract req. &1/Sales activity &2: The sales activity was added | ||
563 | 696 | Contract req. &1/sales activity &2: The sales activity was modified | ||
564 | 697 | Contract req. &1/ Sales activity &2: Sales activity was deleted | ||
565 | 698 | Contract req. &1: Was skipped due to sales activity data | ||
566 | 699 | Contract req. &1: Was kept for commission type &2 without being checked | ||
567 | 700 | * 700 - 750 Sales activity maintenance | ||
568 | 701 | Text for sales activity type in languages & and & does not exist | The short text describes the object sufficiently | |
569 | 702 | Text for sales activity status & in language & does not exist | The short text describes the object sufficiently | |
570 | 703 | Text for sales activity & in languages & and & does not exist | The short text describes the object sufficiently | |
571 | 704 | Suitable inclusive element &4 in contract req. &1/&2 (reqmnt type &3) | Space: object requires documentation | |
572 | 705 | Suitable exclusive element &4 in contract req. &1/&2 (reqmnt type &3) | Space: object requires documentation | |
573 | 706 | &1 address(es) selected | Space: object requires documentation | |
574 | 710 | * Agent determination 3. part | ||
575 | 711 | Requirement type &1: &2 contract req. found for sales area &3 | ||
576 | 712 | Contract req. &1: No sales activity occured with BP &2 | ||
577 | 713 | No log data for agent determination exists. | ||
578 | 714 | Contract req. &1: Commission key &2 caused the following error &3 | Space: object requires documentation | |
579 | 715 | Contract requirement &1: Was deactivated due to missing data | Space: object requires documentation | |
580 | 716 | Preliminary requirement would produce circular requirements | Space: object requires documentation | |
581 | 717 | Preliminary requirement &1 does not have any elements | Space: object requires documentation | |
582 | 718 | You are deleting all elements of a requirement which is part of a chain. | Space: object requires documentation | |
583 | 719 | You have selected a requirement number without a sales agent contract | Space: object requires documentation | |
584 | 720 | Extra commission &3 '&4' cannot be granted (see long text) | Space: object requires documentation | |
585 | 730 | Form &1 does not exist in program &2 | Space: object requires documentation | |
586 | 740 | * 740 - 749 distribution elements | Space: object requires documentation | |
587 | 741 | Only carrier routes admissible (route &1 is not a carrier route) | Space: object requires documentation | |
588 | 751 | *751 - 799 AI elements | ||
589 | 752 | AI elements must be defined as homogeneous districts, geo.units or routes | ||
590 | 753 | All delivery viability entries for the edition are blank | The short text describes the object sufficiently | |
591 | 754 | Double entries were deleted | The short text describes the object sufficiently | |
592 | 755 | Cust.group, SOrg.and dstChn. can only be defined initially for the route | The short text describes the object sufficiently | |
593 | 756 | Delivery type is not an order delivery type | The short text describes the object sufficiently | |
594 | 757 | Delivery type is not valid | The short text describes the object sufficiently | |
595 | 758 | No explicit customer group can be defined for deliverer delivery type | The short text describes the object sufficiently | |
596 | 759 | Blank entries were deleted | The short text describes the object sufficiently | |
597 | 760 | *-760-780 BU Master data------------------------------------------------* | ||
598 | 761 | Gen.tech.data: No page format was entered | The short text describes the object sufficiently | |
599 | 762 | Elements were/are not consistent. Saving is not possible | The short text describes the object sufficiently | |
600 | 763 | You must specify a printing works | Space: object requires documentation | |
601 | 764 | The AI elements were saved without check | Space: object requires documentation | |
602 | 765 | Flyer delivery types are not allowed | The short text describes the object sufficiently | |
603 | 766 | Delivery types for pick up are not allowed | The short text describes the object sufficiently | |
604 | 767 | A district must be entered for this delivery type | The short text describes the object sufficiently | |
605 | 768 | No district can be entered for this delivery type | The short text describes the object sufficiently | |
606 | 769 | A geographical unit must be entered for this delivery type | The short text describes the object sufficiently | |
607 | 770 | A geographical unit cannot be entered for this delivery type | The short text describes the object sufficiently | |
608 | 771 | Delta coverage can not be performed for all elements | The short text describes the object sufficiently | |
609 | 772 | Checks were successful | ||
610 | 773 | Elements could not be changed. Basic booking unit contains PSD elements | The short text describes the object sufficiently | |
611 | 774 | Public.,Edit w/o printing works in the elem. <> BBU. Please save again | Space: object requires documentation | |
612 | 775 | No PSD deliveries exist for this selection | ||
613 | 776 | No PSD deliveries exist for this edition | ||
614 | 777 | Entry &: Customer group can only be specified for postal ship.del.type | ||
615 | 778 | Entry &: Either distr./geo.unit/route or generic entries | ||
616 | 779 | Entry &: If carrier route/del.type defined, must have del.type home del. | ||
617 | 780 | Entry &: Postal ship./direct delivery obligatory for geo.unit/del.type | Space: object requires documentation | |
618 | 781 | Entry &: If geo.unit/customer grp specified, you must also spec.del.type | ||
619 | 782 | Additional specific entries are not required for a generic entry | ||
620 | 783 | The AI elements were saved without being exploded | ||
621 | 784 | Elements saved in spite of missing M/SD delivery viability for &1 | Space: object requires documentation | |
622 | 785 | Rules for defining AI M/SD elements | Space: object requires documentation | |
623 | 786 | Please specify reference publication and reference edition | Space: object requires documentation | |
624 | 787 | Please specify the positioning system grouping | Space: object requires documentation | |
625 | 788 | Please specify publication, edition and printing works | Space: object requires documentation | |
626 | 789 | Elements are inconsistent or blank. Errored elements were selected | The short text describes the object sufficiently | |
627 | 790 | This function is not available in the current release | The short text describes the object sufficiently | |
628 | 791 | The validity period does not overlap with the filter period | Space: object requires documentation | |
629 | 792 | The content component is of an inadmissible type | Space: object requires documentation | |
630 | 793 | Start &1 of Internet publication period is later than end &2 | Space: object requires documentation | |
631 | 801 | * 801 to 820 document flow/archiving | ||
632 | 802 | No document flow exists for object & & & & | Space: object requires documentation | |
633 | 803 | Object detail display for object type '&' is not supported | ||
634 | 804 | Detail display is not possible for temporary objects | ||
635 | 805 | This function is only possible for log entries with reference object | ||
636 | 806 | You cannot navigate in the current document | Space: object requires documentation | |
637 | 807 | This object cannot be displayed | Space: object requires documentation | |
638 | 808 | Display not possible | Space: object requires documentation | |
639 | 809 | This document has already been archived | Space: object requires documentation | |
640 | 840 | ISBN is incorrect (incorrect check digit) | Space: object requires documentation | |
641 | 841 | ISBN is incorrect (incorrect numbers or length) | The short text describes the object sufficiently | |
642 | 900 | Check digit for the ISBN is incorrect | Space: object requires documentation |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |