NJIT_O_MSG -
The following messages are stored in message class NJIT_O_MSG: .
It is part of development package NJIT_MODEL_O in software component LE-JIT-S2P. This development package consists of objects that can be grouped under "NJIT: Data Model/ CDS (Outbound Solution)".
It is part of development package NJIT_MODEL_O in software component LE-JIT-S2P. This development package consists of objects that can be grouped under "NJIT: Data Model/ CDS (Outbound Solution)".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Enter required fields &1 |
002 | Control cycle released before planned release date |
003 | Lock date cannot be before release date |
004 | Lock date cannot be before creation date |
005 | Release date cannot be before creation date |
006 | Release date cannot be in the past |
007 | Lock date cannot be in the past |
008 | Plant &1 does not exist |
009 | Supply area &1 does not exist |
010 | Enter valid value |
011 | Control cycle &1 exists for material, plant, and supply area combination |
012 | Storage location &1 must be maintained for material &2 |
013 | Failed to update control cycle &1 status. Try again |
014 | Object updated |
015 | Storage bin &1 does not exist |
016 | JIT call profile &1 does not exist |
017 | Container &1 does not exist |
018 | Material &1 does not exist |
019 | Replenishment strategy &1 does not exist |
020 | Source storage location &1 does not exist |
021 | Replenishment lead time cannot be more than 23:59 |
022 | Lower tolerance must be between 0 and 100 |
023 | Supply area is WM managed but not extended for EWM |
024 | Action control &1 does not exist |
025 | You are not authorized to edit this control cycle |
026 | You are not authorized to create control cycle |
027 | Control cycle &1 deleted |
028 | You are not authorized to delete this control cycle |
029 | Control cycle &1 contains JIT calls; cannot be deleted |
030 | Container quantity must be greater than 0 for a control cycle |
031 | Goods receipt line item has missing EWM warehouse number/storage bin |
032 | Goods receipt line item is not EWM-relevant |
033 | Verify the EWM mapping |
034 | Enter a valid delivery quantity |
035 | Negative input is not allowed |
036 | No authorization to transfer stock for plant &1 |
037 | No authorization to create JIT call for control cycle &1 |
038 | Control cycle &1 is not in released status |
039 | Action '&1' not applicable for internal status '&2' |
040 | Material picking failed for JIT Call &1 |
041 | Stock transfer failed for JIT Call &1 |
042 | Action control not maintained for control cycle |
043 | Control cycle released |
044 | Control cycle locked |
045 | Control cycle changed to created |
046 | JIT Call &1 is picked |
047 | JIT Call &1 is posted |
048 | No movement type maintained for Replenishment Strategy of JIT call &1 |
049 | Enter time in format hh:mm from 00:00 to 23:59 |
050 | Plant and material combination exists for the new record |
051 | Control cycle &1 is locked by &2 |
052 | Direct transfer failed for JIT Call &1 |
053 | Two-step stock transfer is not supported with EWM destination |
054 | Control cycle saved |
055 | Cannot use replenishment strategy &1 for EWM managed PSA |
056 | Cannot use replenishment strategy &1 for MM-IM managed PSA |
057 | Enter line structure |
058 | Enter plant |
059 | Planning procedure &1 does not exist |
060 | No control cycles found for the selection |
061 | No APO demands found for the selection |
062 | Source and destination storage location must belong to same warehouse |
063 | Technical error. Please contact administrator |
064 | No APO planned orders found for the selection |
065 | No replenishment requests created for the selection |
066 | Life cycle status update error for JIT Call & |
067 | JIT call & canceled |
068 | Enter either current date or date that is in future |
069 | Supply date/time is in past for component group &1 |
070 | Specify a reference type |
071 | Reference type &1 already exists at &2 level |
072 | Enter a valid reference text at & level |
073 | Reference type &1 does not exist; specify valid value |
074 | & must be maintained |
075 | Enter storage bin that belongs to the specified storage location |
076 | Enter a storage bin that belongs to specified source storage location |
077 | Invalid planning procedure |
078 | Enter a planning horizon long enough to cover the replenishment time |
079 | You cannot delete a JIT call |
080 | Control cycle &1 does not exist |
081 | Create a JIT call with header, component group, and material |
082 | You cannot create a JIT component group |
083 | You cannot create a JIT component material |
084 | You cannot delete a JIT component group |
085 | You cannot delete a JIT component material |
086 | Specify a control cycle |
087 | Specify a reference type at JIT header level |
088 | Specify a reference type at component group level |
089 | Specify a reference type at component material level |
090 | Specify a valid JIT header reference type |
091 | Same JIT header reference type is specified more than once |
092 | Specify a valid component group reference type |
093 | Same component group reference type is specified more than once |
094 | Specify a valid component material reference type |
095 | Same component material reference type is specified more than once |
096 | Specify requested quantity for the component material &1 |
097 | Specify a valid JIT call number |
098 | No record found for JIT call &1, component group &2, and control cycle &3 |
099 | No record found for JIT Call &1, component group &2, and item &3 |
100 | Supply date/time changed for component group material & |
101 | Requested quantity changed for component material & |
102 | JIT call number &1 is created |
103 | JIT Component group number &1 is created |
104 | JIT component group number &1 and material item number &2 is created |
105 | Header reference type &1 reference text is changed to &2 |
106 | JIT component group's &1 reference type &2 reference text &3 is &4 |
107 | JIT component material's &1 reference type &2 reference text &3 is &4 |
108 | Invalid JIT life cycle status &1 |
109 | Specify a valid JIT lifecycle status |
110 | Priority type changed from &1 to &2 for JIT call &3 |
111 | JIT call &1 is updated |
112 | JIT call status changed from &1 to &2 |
113 | Failed to change status of control cycle &1. Try again |
114 | Material &1 is not available in source storage location |
115 | Invalid JIT priority type &1 |
116 | Header reference type &1 is deleted |
117 | Specify valid component Group &1 |
118 | No REM planned orders found for the selection |
119 | No DM production orders found for the selection |
120 | Enter source supply area different from production supply area |
121 | Secondary control cycle does not exist for given configuration |
122 | Enter a value between 0 and 100 for requested quantity upper tolerance |
123 | Enter a value between 0 and 100 for requested quantity lower tolerance |
124 | No implementation for control cycle category and JIT action combination |
125 | Action control failed; PROCESS_BEFORE_ACTION method not implemented |
126 | Action control failed; DO_ACTION method not implemented |
127 | Action control failed; PROCESS_AFTER_ACTION method not implemented |
128 | No vehicle planned orders found |
129 | No component group material found for component material &1, order &2 |
130 | No control cycle found for component group material &1, order &2 |
131 | JIT update failed;Insufficient information or data inconsistency |
132 | No further hierarchy possible for this control cycle |
133 | Failed to cancel JIT call & |
134 | Number of load carriers cannot be less than 1 |
135 | Plant & supports a maximum of & active urgent priority JIT calls |
136 | Plant & supports a maximum of & active missing parts JIT calls |
137 | Supply date &1 updated ; JIT call &2 ; order &3 ; Control Cycle &4 |
138 | &1 active JIT calls already exists for this control cycle |
139 | No demands found |
140 | End date cannot be before the start date |
141 | End time cannot be before the start time |
142 | Start time and end time must be different |
143 | Reference type &1 already exists for &2 &3; enter a new type |
144 | Just in sequence call number &1 is created |
145 | Replenishment time must be greater than that of primary control cycle &1 |
146 | Maintain communication group for the control cycle &1 |
147 | JIT call number &1 is created for control cycle &2 |
148 | Demand time is adjusted considering shift sequence |
149 | Planning procedure maintained is not relevent for sets |
150 | EWM relevant JIT calls not found during JIT call creation |
151 | Just in sequence call number &1 is created with new control cycle &2 |
152 | Enter a valid value to &1 field |
153 | Loading point &1 does not exist |
154 | No schedule agreement found for plant &1, stor.loc. &2, and material &3 |
155 | JIT request to supplier &1 failed due to communication failure |
156 | Message partner &1 is blocked;hence cannot be added |
157 | Communication group &1 not blocked; hence cannot be archived |
158 | Date will be adjusted considering break and shift sequences |
159 | Goods receipt posted with material document &1 &2 |
160 | No communication group according to user�s selection criteria |
161 | Enter/select valid communication group |
162 | Enter a valid message partner |
163 | Message partner &1 is marked for archiving; hence cannot be added |
164 | JIT call creation failed for control cycle &1 |
165 | Demand date/time changed for component group & |
166 | Reorder quantity for all component materials cannot be zero |
167 | JIT call &1 item &2 changed to status &3 |
168 | JIT Call &1 item &2 quantity updated from EWM |
169 | Control cycle &1 has &2 active JIT calls. Supply area cannot be changed |
170 | JIT call &1 is cancelled, JIT call update not allowed |
171 | JIT call &1 is completed, JIT call update not allowed |
172 | Invalid requested quantity value |
173 | Demand date and time cannot be in the past |
174 | JIS control cycle does not exist for component &1 of order &2 |
175 | JIS calls already created for sales order &1 |
176 | In-House production strategy does not exist for plant &1 |
177 | Control cycle &1 is locked for JIT call creation |
178 | Source and destination must have same warehouse management |
179 | Demand date and time cannot be changed for urgent JIT call |
180 | JIT call cannot be created immediately for control cycle &1 |
181 | Control cycle exists for component material &1 |
182 | Secondary control cycle &1 must be consumption-based |
183 | Sequenced JIT call &1 created for control cycle &2 |
184 | Control cycle exists for component group material &1 |
185 | JIT call &1 canceled for control cycle &2 |
186 | Cancelation of JIT call &1 failed for control cycle &2 |
187 | Primary control cycle &1 cannot be consumption-based |
188 | JIT call &1 is updated for control cycle &2 |
189 | Cannot enter call item number for reference type &1 at level &2 |
190 | Enter call item number |
191 | Entry with reference type &1 reference text &2 exists for the item |
192 | Enter a valid call item number from the JIT call |
193 | Enter a valid reference type |
194 | JIT call &1 is locked by user &2 |
195 | &1 JIT call(s) updated |
196 | Supply date/time is updated from &4 to &1 &2 for JIT call &3 |
197 | Destination bin &1 also used for production supply area &2 |
198 | Primary control cycle &1 of the control cycle &2 is locked by &3 |
199 | Demand date/time is updated from &4 to &1 &2 for JIT call &3 |
200 | Reference type &1 already exists |
201 | JIT call priority set to urgent |
202 | Control cycle &1 is updated and control cycle &2 is created |
203 | Invalid configuration control key in scheduling agreement &1 |
204 | Control cycle &1 deleted for material:&2, plant:&3, and PSA:&4 |
205 | Lifecycle status changed from &1 to &2 for control cycle &3 |
206 | Control cycle &1 can be deleted for material:&2, plant:&3, PSA:&4 |
207 | At least one lifecycle status must be selected |
208 | Planned order &1 has no sales order; JIS calls cannot be created |
209 | No suitable control cycle found, select correct scheduling parameters |
210 | Can delete only locked control cycle; select correct lifecycle status |
211 | Not possible to modify JIT calls for external replenishment |
212 | Inbound delivery already created for JIT call: &1 |
213 | Invalid scheduling agreement &1 &2 for CC's, plant, and Sloc |
214 | Enter value |
215 | Sender technical ID &1, control cycle category &2 is not supported |
216 | Control cycle with sender technical ID &1 created |
217 | Control cycle with sender technical ID &1 validated |
218 | Communication group created |
219 | Communication group validated |
220 | Enter valid supplier |
221 | Warehouse request for JIT call &1 is blocked for demand date/time updates |
222 | Enter valid status |
223 | Message partner &1 already added to communication group |
224 | Scheduling agreement &1 and item &2 already exist in control cycle &3 |
225 | Enter valid communication group &1 |
226 | You cannot create scheduling agreement for control cycle |
227 | You cannot delete scheduling agreement for control cycle |
228 | You cannot set external replenishment flag for control cycle &1 |
229 | Select purchasing scheduling agreement status |
230 | No suitable purchasing scheduling agreements found |
231 | Scheduling agreement &1 is blocked; cannot be archived |
232 | &1 objects archived |
233 | Supplier &1 is blocked for control cycle &2. Not possible to edit |
234 | Draft deleted |
235 | Failed to delete draft |
236 | Failed to delete control cycle |
237 | You are not authorized to create JIS calls |
238 | You are not authorized to edit this JIT Call |
239 | No authorization to schedule job for plant &1 |
240 | Not possible to cancel JIT/JIS call for external replenishment |
241 | No plant and storage location exists for the warehouse &1 |
242 | No control cycles found for the &1 &2 &3 combination |
243 | For control cycle &2, Order &1 is confirmed or has no requirement |
244 | Calculated deviation quantity is &1 for order &2 in control cycle &3 |
245 | Control cycle not updated |
246 | Control cycle &1 has active JIT calls. Cannot change status |
247 | Safety stock quantity cannot be empty |
248 | Enter valid production supply area |
249 | No control cycle found for scheduing agreement &1 item &2 |
251 | Storage type of primary and secondary control cycles should be different |