OPS_SE_WM_XI_PROXY - Message class for XI WM messages
The following messages are stored in message class OPS_SE_WM_XI_PROXY: Message class for XI WM messages.
It is part of development package OPS_SE_WM_XI_PROXY in software component LE-WM-IFC. This development package consists of objects that can be grouped under "".
It is part of development package OPS_SE_WM_XI_PROXY in software component LE-WM-IFC. This development package consists of objects that can be grouped under "".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Default implementation for user mapping: TRM code not found. |
| 001 | Warehouse & not found. |
| 002 | No site has been assigned to warehouse &. |
| 003 | Forklift driver of forklift & could not be determined. |
| 004 | BADI LE_WM_SE_HUMOVE has not been implemented -> stop the process. |
| 005 | HU/SU tag & could not be assigned to any HU/SU. |
| 006 | Bin tag (input &) could not be assigned to any storage bin. |
| 007 | Forklift ID could not be assigned to any user. |
| 008 | The storage bin tag has not been populated. |
| 009 | Movement type & does not exist in warehouse & -> TO cannot be created. |
| 010 | Removal: mismatch between source bin & & and current HU/SU bin & &. |
| 011 | Removal: open posting change exists for HU/SU &. |
| 012 | Removal:several open TO items for HU/SU & -> partial pick not supported. |
| 013 | Putaway: destination bin & doesn't match the destination of open TO &. |
| 014 | No storage unit has been found for &. |
| 015 | Transfer order & has been processed successfully. |
| 016 | Storage unit & cannot be found. |
| 017 | Partial pick TOs exist for SU &. Process was stopped after call of BAdI. |
| 018 | Posting change exists for SU &. Process was stopped after call of BAdI. |
| 019 | TO & has been found and the removal step has already been confirmed. |
| 020 | Removal: SU & is on bin of bulk storage. BAdI didn't find an open TO. |
| 021 | Putaway:SU & is on bin of bulk storage. No TO is available. |
| 022 | No first step confirmation for TO &, SU would get lost. |
| 023 | Putaway, SU &: no movement type was determined for the new TO. |
| 024 | Mismatch Destination bin &, TO &. Process was stopped after call of BADI. |
| 025 | Removal: mismatch source bin - current SU bin, process stopped after BAdI |
| 026 | Neutral bin input: no decision has been taken for removal or putaway. |
| 027 | Last TO & of SU & cannot be read. |
| 028 | Removal: mismatch between source bin & & and bin of open TO &. |
| 029 | exactly once request: enqueue failure: & |
| 030 | Problem in exactly once request: UUID &1, &2 |
| 031 | Internal error: failure at log creation. |
| 032 | Internal error:failure when initialising the application logic. |
| 033 | An error occured during the length check of the HU tag field &. |
| 034 | An error occured during the length check of the bin tag field &. |
| 035 | Both LOADED and UNLOADED indicator are selected in the message. |
| 036 | The HU tag field (AUTOMATIC_IDENTIFICATION_LABEL) is empty. |
| 037 | The bin tag field (LOGISTICS_AREA-ID) is empty. |
| 038 | HU &1 has been identified. |
| 039 | SU &1 has been identified. |
| 040 | Warehouse &1, storage type &2 and storage bin &3 have been identified. |
| 041 | User &1 has been identified. |
| 042 | Movement has been identified as removal. |
| 043 | Movement has been identified as putaway. |
| 044 | HU/SU tag assignment: several HUs/SUs have been found. |