SAP ABAP Message Class OPS_SE_WM_XI_PROXY (Message class for XI WM messages)

Basic Data

Hierarchy

☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ LE-WM-IFC (Application Component) Interfaces
     ⤷ OPS_SE_WM_XI_PROXY (Package) Web Service Proxies Warehouse Management

Attributes

Message class	OPS_SE_WM_XI_PROXY
Short Description	Message class for XI WM messages
Changed On	20100310
Last Changed At	200227

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	000	Default implementation for user mapping: TRM code not found.	Space: object requires documentation	☐
2	001	Warehouse & not found.	Space: object requires documentation	☐
3	002	No site has been assigned to warehouse &.	Space: object requires documentation	☐
4	003	Forklift driver of forklift & could not be determined.	The short text describes the object sufficiently	☐
5	004	BADI LE_WM_SE_HUMOVE has not been implemented -> stop the process.	Space: object requires documentation	☐
6	005	HU/SU tag & could not be assigned to any HU/SU.	The short text describes the object sufficiently	☐
7	006	Bin tag (input &) could not be assigned to any storage bin.	The short text describes the object sufficiently	☐
8	007	Forklift ID could not be assigned to any user.	The short text describes the object sufficiently	☐
9	008	The storage bin tag has not been populated.	The short text describes the object sufficiently	☐
10	009	Movement type & does not exist in warehouse & -> TO cannot be created.	The short text describes the object sufficiently	☐
11	010	Removal: mismatch between source bin & & and current HU/SU bin & &.	Space: object requires documentation	☐
12	011	Removal: open posting change exists for HU/SU &.	The short text describes the object sufficiently	☐
13	012	Removal:several open TO items for HU/SU & -> partial pick not supported.	The short text describes the object sufficiently	☐
14	013	Putaway: destination bin & doesn't match the destination of open TO &.	Space: object requires documentation	☐
15	014	No storage unit has been found for &.	The short text describes the object sufficiently	☐
16	015	Transfer order & has been processed successfully.	The short text describes the object sufficiently	☐
17	016	Storage unit & cannot be found.	The short text describes the object sufficiently	☐
18	017	Partial pick TOs exist for SU &. Process was stopped after call of BAdI.	The short text describes the object sufficiently	☐
19	018	Posting change exists for SU &. Process was stopped after call of BAdI.	The short text describes the object sufficiently	☐
20	019	TO & has been found and the removal step has already been confirmed.	The short text describes the object sufficiently	☐
21	020	Removal: SU & is on bin of bulk storage. BAdI didn't find an open TO.	The short text describes the object sufficiently	☐
22	021	Putaway:SU & is on bin of bulk storage. No TO is available.	The short text describes the object sufficiently	☐
23	022	No first step confirmation for TO &, SU would get lost.	The short text describes the object sufficiently	☐
24	023	Putaway, SU &: no movement type was determined for the new TO.	The short text describes the object sufficiently	☐
25	024	Mismatch Destination bin &, TO &. Process was stopped after call of BADI.	The short text describes the object sufficiently	☐
26	025	Removal: mismatch source bin - current SU bin, process stopped after BAdI	The short text describes the object sufficiently	☐
27	026	Neutral bin input: no decision has been taken for removal or putaway.	The short text describes the object sufficiently	☐
28	027	Last TO & of SU & cannot be read.	The short text describes the object sufficiently	☐
29	028	Removal: mismatch between source bin & & and bin of open TO &.	The short text describes the object sufficiently	☐
30	029	exactly once request: enqueue failure: &	The short text describes the object sufficiently	☐
31	030	Problem in exactly once request: UUID &1, &2	The short text describes the object sufficiently	☐
32	031	Internal error: failure at log creation.	The short text describes the object sufficiently	☐
33	032	Internal error:failure when initialising the application logic.	The short text describes the object sufficiently	☐
34	033	An error occured during the length check of the HU tag field &.	The short text describes the object sufficiently	☐
35	034	An error occured during the length check of the bin tag field &.	The short text describes the object sufficiently	☐
36	035	Both LOADED and UNLOADED indicator are selected in the message.	The short text describes the object sufficiently	☐
37	036	The HU tag field (AUTOMATIC_IDENTIFICATION_LABEL) is empty.	The short text describes the object sufficiently	☐
38	037	The bin tag field (LOGISTICS_AREA-ID) is empty.	The short text describes the object sufficiently	☐
39	038	HU &1 has been identified.	The short text describes the object sufficiently	☐
40	039	SU &1 has been identified.	The short text describes the object sufficiently	☐
41	040	Warehouse &1, storage type &2 and storage bin &3 have been identified.	The short text describes the object sufficiently	☐
42	041	User &1 has been identified.	The short text describes the object sufficiently	☐
43	042	Movement has been identified as removal.	The short text describes the object sufficiently	☐
44	043	Movement has been identified as putaway.	The short text describes the object sufficiently	☐
45	044	HU/SU tag assignment: several HUs/SUs have been found.	The short text describes the object sufficiently	☐

History

Last changed on/by	20100310	SAP
SAP Release Created in	605