SAP ABAP Message Class IL (PM: ILOM - Functional Locations)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-MSE (Application Component) Mobile Service
⤷ ILOM (Package) Application Development R/3 Location Management
⤷ CRM-MSE (Application Component) Mobile Service
⤷ ILOM (Package) Application Development R/3 Location Management
Attributes
Message class | IL | |
Short Description | PM: ILOM - Functional Locations | |
Changed On | 20100310 | |
Last Changed At | 182156 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 098 | User &1 is editing functional location &2 | ||
2 | 099 | User &1 is editing reference location &2 | ||
3 | 100 | Functional location & does not exist | ||
4 | 101 | Functional location & already exists | ||
5 | 102 | Reference functional location & does not exist | ||
6 | 103 | Reference functional location & already exists | ||
7 | 104 | No functional location found | ||
8 | 105 | No reference functional location found | ||
9 | 106 | No functional locations are allocated to the reference location | ||
10 | 107 | Superior location & has not yet been saved | Space: object requires documentation | |
11 | 108 | There are several locations with sortfield = & | ||
12 | 109 | Superior location & has not yet been saved | Space: object requires documentation | |
13 | 110 | & functional locations created | ||
14 | 111 | & functional locations changed | ||
15 | 112 | & functional locations deleted | ||
16 | 113 | & reference functional locations created | ||
17 | 114 | & reference functional locations changed | ||
18 | 115 | & reference functional locations deleted | ||
19 | 120 | Functional location & created | ||
20 | 121 | Functional location & changed | ||
21 | 122 | Functional location & deleted | ||
22 | 123 | Reference functional location & created | ||
23 | 124 | Reference functional location & changed | ||
24 | 125 | Reference functional location & deleted | ||
25 | 130 | Enter structure indicator | ||
26 | 131 | Enter functional location | ||
27 | 132 | 'Install equipment' must be allowed if 'Single installation' requested | ||
28 | 133 | Superior functional location goes against the generic name or structure | ||
29 | 134 | Superior functional location not allowed (recursivity) | ||
30 | 135 | Enter reference functional location | ||
31 | 136 | Superior functional location was set according to structure | ||
32 | 137 | At FunctLoc. & there are & pieces of equip. installed already | ||
33 | 138 | Functional location address not maintained | ||
34 | 139 | The superior locations from location & are defined retrospectively | ||
35 | 140 | Superior location should be automatically determined - no entry | The short text describes the object sufficiently | |
36 | 188 | Authorization group & could not be transferred | ||
37 | 189 | Authorization group & could not be transferred from the reference copy | ||
38 | 190 | The copy reference was not changed | ||
39 | 191 | Enter either reference location or copy reference | ||
40 | 192 | Enter only the highest functional location in the hierarchy | ||
41 | 193 | Enter copy reference | ||
42 | 194 | Enter reference location | ||
43 | 195 | Enter new functional location | ||
44 | 196 | &1 locations disregarded because of the name structure | Space: object requires documentation | |
45 | 197 | FunctLocation & disregarded on account of the name structure | ||
46 | 198 | Change only the last hierarchy level | ||
47 | 199 | Superior functional location & does not exist (Edit --> F9 again) | ||
48 | 200 | Save the superior functional location & first | ||
49 | 201 | Customer-specific check showed that save is not permitted | Space: object requires documentation | |
50 | 202 | &1 locations already existed | Space: object requires documentation | |
51 | 203 | &1 locations already existed -> Renaming not possible | Space: object requires documentation | |
52 | 204 | &1 locations have already been created, renaming not possible | Space: object requires documentation | |
53 | 205 | &1 location labels could not be converted | Space: object requires documentation | |
54 | 206 | Permitted number of hierarchy levels exceeded | Space: object requires documentation | |
55 | 207 | Location & does have any higher-level location (no display) | Space: object requires documentation | |
56 | 208 | Location &1 belongs to the higher-level location &2 (generic name) | Space: object requires documentation | |
57 | 209 | New location & has no higher-level location (no display) | Space: object requires documentation | |
58 | 210 | Error while location &1 under location &2 | Space: object requires documentation | |
59 | 211 | The renaming delivers identical labels & for several locations | Space: object requires documentation | |
60 | 212 | Functional location was overwritten and saved without checking | Space: object requires documentation | |
61 | 213 | Lines were deleted in a forbidden way and saved immediately | Space: object requires documentation | |
62 | 299 | Category & not available for object links | ||
63 | 300 | Category & not defined for functional locations | ||
64 | 301 | Category & not supported for reference functional locations | ||
65 | 302 | No reference location defined --> data transfer not possible | ||
66 | 303 | No superior functional location defined --> data transfer not possible | ||
67 | 304 | Change to cat. & not poss.: partner determ. procedure different | ||
68 | 305 | No change documents generated for type & | ||
69 | 310 | You will change the interrelation of the functional location hierarchy | ||
70 | 311 | The FunctLoc.will become the uppermost FunctLoc. in its own hierarchy | ||
71 | 312 | The new reference location data will be transferred if applicable | ||
72 | 313 | You will explode the allocation to the reference location | ||
73 | 314 | Data will be copied from the new superior functional location | ||
74 | 315 | Data will be copied from the new reference location | ||
75 | 316 | Data was copied from the superior FunctLocation and the RefLocation | ||
76 | 317 | Data was copied from the superior functional location | ||
77 | 318 | Data was copied from the reference location | ||
78 | 320 | Data transfer to & ref. locations, & funct.locations, and & equipment | Space: object requires documentation | |
79 | 321 | Data transfer to & ref. locations, & funct.locations, & meas.pts, & equi. | Space: object requires documentation | |
80 | 324 | Catch up on data transfer. Termination of data transfer at techn. objects | Space: object requires documentation | |
81 | 350 | Data copied to & FunctLoc(s) and & piece(s) of equip. | ||
82 | 351 | Data copied to & RefLocs, & FunctLocs and & pieces of equip. | ||
83 | 352 | Data was copied to & pieces of equipment | ||
84 | 353 | There is no data to be copied | ||
85 | 354 | Data was transferred to & measuring points | ||
86 | 355 | Data copied to &1 RefLocs, &2 FunctLocs, &3 pcs. equip., 4& MeasPoints | ||
87 | 356 | There are no more data transfers to make up | ||
88 | 400 | Functional location & still has no status | ||
89 | 401 | Reference functional location & does not have a status | ||
90 | 402 | Check user status | ||
91 | 403 | The status profile of the location must be changed manually if necessary | Space: object requires documentation | |
92 | 410 | Functional location & is inactive | ||
93 | 411 | RefFunct. location & is inactive | ||
94 | 412 | RefFunct. location & is flagged for deletion | ||
95 | 413 | RefFunct. & is flagged for deletion | ||
96 | 414 | Functional location & has a deletion flag. Can only be displayed | ||
97 | 415 | RefFunct. location & has a deletion flag. Can only be displayed | ||
98 | 416 | The superior location & is inactive | ||
99 | 417 | The superior location & is flagged for deletion | ||
100 | 418 | The superior RefFunctLocation & is flagged for deletion | ||
101 | 420 | Equipment &2 is still installed at location &1 | ||
102 | 421 | Check status of subordinate location &2 | ||
103 | 422 | Check status of subordinate reference location &2 | ||
104 | 423 | The assigned functional location &2 is not flagged for deletion | ||
105 | 499 | Labeling system &1 is not available. (Check entry) | ||
106 | 500 | Labeling systems for functional locations do not exist | Space: object requires documentation | |
107 | 501 | System settings for alternative labeling do not exist | Space: object requires documentation | |
108 | 502 | Not all functional locations could be processed | Space: object requires documentation | |
109 | 503 | Access to all functional locations has been optimized | Space: object requires documentation | |
110 | 504 | The program has already been executed successfully | Space: object requires documentation | |
111 | 505 | Alternative labels for functional locations are not active | Space: object requires documentation | |
112 | 506 | Enter a label | Space: object requires documentation | |
113 | 507 | Not all changes could be saved | Space: object requires documentation | |
114 | 508 | A search cannot be performed for this column | Space: object requires documentation | |
115 | 509 | You have reached the end of the table | Space: object requires documentation | |
116 | 510 | Labeling system &1 does not exist | Space: object requires documentation | |
117 | 511 | &1 is a historical label of location &2 | Space: object requires documentation | |
118 | 512 | Label &1 is already being used in labeling system &3 | Space: object requires documentation | |
119 | 513 | The labeling system cannot be changed at the moment | Space: object requires documentation | |
120 | 514 | Alternative labels for functional locations are not active | Space: object requires documentation | |
121 | 515 | No functional locations were selected based on the criteria entered | Space: object requires documentation | |
122 | 516 | No primary labeling system exists for functional location & | Space: object requires documentation | |
123 | 517 | No user profile exists for user & | Space: object requires documentation | |
124 | 518 | Alternative labeling: not all functional locations have been converted | Space: object requires documentation | |
125 | 550 | Functional location & already has a superior functional location | The short text describes the object sufficiently | |
126 | 551 | Error converting the time stamp | The short text describes the object sufficiently | |
127 | 552 | Functional location & does not have a superior functional location | The short text describes the object sufficiently | |
128 | 553 | General error when trying to make up for inheritance terminations | The short text describes the object sufficiently | |
129 | 554 | Values for functional location & copied from superior functional loc. & | The short text describes the object sufficiently | |
130 | 555 | Error assigning inheritance indicator to functional location & | The short text describes the object sufficiently | |
131 | 556 | Error reading out structure & | The short text describes the object sufficiently | |
132 | 557 | No authorization to change the fields of a functional location | The short text describes the object sufficiently | |
133 | 558 | Invalid data origin character & | The short text describes the object sufficiently | |
134 | 559 | Invalid data origin as no functional reference location | The short text describes the object sufficiently | |
135 | 560 | Invalid data origin as no superior functional location | The short text describes the object sufficiently | |
136 | 561 | Data transfer & not permitted for field & | The short text describes the object sufficiently | |
137 | 562 | Internal error in method & of class & | The short text describes the object sufficiently | |
138 | 563 | Inheritance & for field & requires inheritance indicator & for field & | The short text describes the object sufficiently | |
139 | 564 | Inheritance of maint. planner grp directly or identical to planning plant | The short text describes the object sufficiently | |
140 | 565 | & is not supported -> use & as an alternative | The short text describes the object sufficiently | |
141 | 566 | Error transferring data from superior functional location | The short text describes the object sufficiently | |
142 | 567 | & was not executed successfully | The short text describes the object sufficiently | |
143 | 700 | PP work center has plant &. Maintenance plant is & | ||
144 | 703 | Inconsistency: plant & is in company code & | ||
145 | 704 | Cost center & & is a statistical cost center | ||
146 | 740 | Table &1 change started: &1 &2 | Space: object requires documentation | |
147 | 741 | Table &1 change: Client &2 started | Space: object requires documentation | |
148 | 742 | Table &1 change finished: &2 &3 | Space: object requires documentation | |
149 | 743 | Table &1 change: Start Program &2 manually | Space: object requires documentation | |
150 | 744 | Table &1 change: &2 entries changed | Space: object requires documentation | |
151 | 745 | Table &1: Language &2 not installed. &3 records affected | Space: object requires documentation | |
152 | 800 | Edit mask must only contain edit characters | ||
153 | 801 | Edit mask must not begin with a hyphen | ||
154 | 802 | Edit mask must not end with a hyphen | ||
155 | 803 | You cannot have two hyphens directly after one another | ||
156 | 810 | Invalid character in hierarchy levels | ||
157 | 811 | The numbering of the hierarchy levels is incorrect | ||
158 | 812 | There are levels outside the area of the edit mask | ||
159 | 813 | A hierarchy level must be under the last character of a block | ||
160 | 814 | A hierarchy level must not end with a separator | ||
161 | 820 | Change level entered is greater than the number of hierarchy levels | ||
162 | 821 | ConvLevel entered is greater than the no. of hierarchy levels | ||
163 | 831 | & structure indicator(s) is/are in use and could not be deleted | ||
164 | 833 | The structure indicator is already being used | Space: object requires documentation | |
165 | 839 | Location label is too long | Space: object requires documentation | |
166 | 840 | Entry length allowed in the edit mask has been exceeded | ||
167 | 841 | Only letters and figures are allowed at the present cursor position | ||
168 | 842 | Functional location label must not end with a separator | Space: object requires documentation | |
169 | 843 | Functional location label must not be initial in the first block | Space: object requires documentation | |
170 | 844 | Separator corrected in functional location label | Space: object requires documentation | |
171 | 845 | Only letters are allowed at the present cursor position | ||
172 | 846 | Only figures are allowed at the present cursor position | ||
173 | 847 | Invalid character at current cursor position (&1) | Space: object requires documentation | |
174 | 848 | Customer-specific check showed: Location label not allowed | Space: object requires documentation | |
175 | 849 | Location label changed by customer-defined program | Space: object requires documentation | |
176 | 850 | Only figures, letters or special characters allowed at cursor position | Space: object requires documentation | |
177 | 895 | No errors found | The short text describes the object sufficiently | |
178 | 896 | No status profile is assigned | Space: object requires documentation | |
179 | 897 | Functional location &1 has been changed | Space: object requires documentation | |
180 | 898 | Function & under development; not currently available | ||
181 | 899 | No entry can be made in field & as field cannot be checked |
History
Last changed on/by | 20100310 | SAP | |
SAP Release Created in |