/SCWM/LK - Messages for Linking WM -> Subsystem
The following messages are stored in message class /SCWM/LK: Messages for Linking WM -> Subsystem.
It is part of development package /SCWM/ASR_INTERFACE in software component SCM-EWM-IF. This development package consists of objects that can be grouped under "Interface for Warehouse Control Unit".
It is part of development package /SCWM/ASR_INTERFACE in software component SCM-EWM-IF. This development package consists of objects that can be grouped under "Interface for Warehouse Control Unit".
Message Nr ▲ | Message Text |
---|---|
001 | No function module defined for message type & |
002 | No definition of communication relationship for message type & |
003 | Transmission system not defined for link WM -> subsystem |
004 | No receiver found for message type & |
005 | Internal error during determination of relevant WTs for link to subsystem |
006 | No receiver defined for target system & |
007 | Segment & is not defined in IDOC (check IDOC syntax) |
008 | Multiple processing of IDOCs terminated; error during IDOC & |
009 | Inconsistency of data in the individual IDOC segments |
010 | Status of IDOCs & not determined |
011 | Parameters of return table for IDOC & not determined |
012 | Message type & cannot be processed in selected function module |
013 | No target system found for the WT item to be canceled |
014 | Message type "cancellation request" is not active for variant & |
015 | IDOC can only contain data from a warehouse task |
016 | For warehouse number &, link to external system is not activated |
017 | TR change not possible; reference to TR number missing |
018 | Transfer requirement & & does not exist |
019 | Inconsistency of data in segments /SCWM/E1LTCOX and /SCWM/E1LTCOH |
020 | Consistency problem: either block or unblock |
021 | Consistency problem: blocking entry already exists |
022 | Consistency problem: whse number / stor.type combination does not exist |
023 | Consistency problem: warehouse number authorization missing |
024 | Internal error occurred during update to LAGP. Contact system supervisor |
025 | Check your entries |
026 | Receiving and transmitting systems must be entered |
027 | Selection does not generate an IDOC |
028 | For confirmation of single items, you must select the WT number |
029 | Transfer requirement item to be cancelled cannot be found |
030 | For entering count data in storage type &, the SU number is required |
031 | Specify a unit of measure for the counted quantity |
032 | Check your entry. No inventory number found for storage bin & |
033 | Inventory count data could not be transferred |
034 | Transfer all data to function module L_INV_COUNT |
035 | Inventory number currently blocked by another user |
036 | Check your entries. Inventory count already complete or not available |
037 | Check your entries. Inventory number does not match storage bin |
038 | Either set the indicator for bin empty or a quantity |
039 | New entry required. Inventory number(s) not for inventory count |
040 | Inconsistency of data in segments /SCWM/E1LTCOX and /SCWM/E1LTCOI |
041 | Inconsistency of data in segments /SCWM/E1LTCOH and /SCWM/E1LTCOI |
042 | WT item & & is not intended for link to subsystem |
043 | No open WT items for confirmation by system & |
044 | Cancellation not possible: &&&& |
045 | Cancellation not possible: &&&& |
046 | In IDOC, no cancellation activated |
047 | Material movement could not be posted in the system |
048 | Several warehouse tasks in one IDOC for WT confirmation not possible |
049 | No authorization for transfer requirement change (Transaction LB02) |
050 | &1&2&3&4 |
051 | No authorization for transfer requirement creation (Transaction LB01) |
052 | Call update task only in connection with COMMIT WORK |
053 | To cancel transfer requirement, specify the reference number |
054 | Detailed display not possible at this level |
055 | Several inventory numbers cannot be processed simultaneously |
056 | Several recount versions per inventory number not allowed simultaneously |
057 | Double count records cannot be processed via the interface |
058 | New selection. No data was found for the parameters entered. |
059 | Segment E1MBXYJ could not be assigned to segment E1MBXYI |
060 | Segment E1LTCOG is in the wrong sequence or has the wrong WT number |
061 | Incorrect control of two-step confirmation in WCU interface |
062 | Separate confirmation with indicator '&1' triggered, '&2' is allowed |
063 | Either /SCWM/E1LTCOH or /SCWM/E1LTCOX has to be filled |
064 | Actual=target confirmation (SQUIT = X) with SN specification not possible |
065 | No means of transport found for packaging material &1 |
070 | Entry combination is not allowed. Select again. (Material reorganization) |
071 | There are no table entries in T320 (material reorganization) |
072 | Wrong form & was used for printing (posting change warehouse tasks) |
073 | Plant/storage location/warehouse number combination is incorrect |
074 | Several WTs with the KOMIM switch within one IDoc are not allowed |
080 | Consistency problem: storage bins not maintained, or storage type wrong |
100 | Warehouse order &1 does not exist |
101 | Warehouse order &1 does not contain any open warehouse tasks |
102 | Error while reading activity area &1 |
103 | Error while reading storage bin &1 |
104 | Error while changing HU attributes of HU &1 |
105 | Warehouse number and warehouse order must be transferred |
106 | Either the HU number of the packaging material must be transferred |
107 | IDocs can only be transferred for a warehouse number |
200 | IDoc data for creation of vehicle and TU is not correct |
201 | ERP shipment &1 already assigned to TU &2 / activity &3 |
202 | TU for delivery assignment &1 / &2 not found |
203 | IDoc segment E1EDT20 with number &1 already received |
204 | IDoc segment E1EDT20 with number &1 is missing |
205 | No mapping entries found for business system &1 and ERP partner role &2 |
206 | Partner roles not unique for business system &1 and ERP partner role &2 |
207 | No partner found for external number &1 and type &2 |
208 | No unique partner found for external number &1 and type &2 |
209 | Loading start (&1) is later than loading end (&2) |
210 | Planned start (&1) is later than planned end (&2) |
211 | External product &1 from system &2 could not be converted |
212 | No means of transport determined based on standard code &1 |
213 | IDoc segment E1EDL20 for delivery &1 already received |
214 | Reference not found for ERP delivery &1 from system &2 |
215 | Different direction of S&R activity (&1 / &2) within one IDoc |
216 | Delivery &1 is already assigned to TU &2 activity &3 |
217 | Mapping of logical system &1 to business system failed |
218 | Mapping of logical system &1 to business system is not unique and failed |
219 | No header information found |
220 | No vehicle and TU information found |
221 | No delivery information found |
222 | Warehouse number could not be determined from delivery |
223 | Transportation planning type &1 is not supported |
224 | Shipment reference missing |
225 | Outbound processing of IDoc & is not possible |
226 | Data container for PPF action &1 is not filled |
227 | Logical system must not be initial |
228 | IDoc message type must not be initial |
229 | Default values not maintained for business system &1 and message type &2 |
230 | Shipment type must not be initial |
231 | Transportation planning point must not be initial |
232 | HU &1 could not be clearly identified as a TU or a vehicle |
233 | Mapping of TU Route to the ERP system is not possible |
234 | Business system key must not be initial |
235 | Delivery &1 is blocked |
236 | Error during reading delivery &1 |
237 | Error during updating delivery &1 |