SAP ABAP Message Class M! (Update Check in LIS)

Basic Data

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ MCS (Package) R/3 application development: Logistics Information Warehouse

Attributes

Message class	M!
Short Description	Update Check in LIS
Changed On	19970617
Last Changed At	223133

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	001	This field must be used for billing	Space: object requires documentation	☐
2	002	Caution: updating is only possible in specific circumstances	Space: object requires documentation	☐
3	003	This field is not filled when a credit memo is requested	Space: object requires documentation	☐
4	004	Client &1 has status 'not modifiable'	Space: object requires documentation	☐
5	005	SAP System has status 'not modifiable'	Space: object requires documentation	☐
6	050	********** 050...099 reserved for general notifications **********	Space: object requires documentation	☐
7	051	&1: &2-&3 were not filled for event &4	Space: object requires documentation	☐
8	052	&1: &2-&3 were not built for event &4	Space: object requires documentation	☐
9	053	&1: Date &2-&3 were not filled for event &4	Space: object requires documentation	☐
10	054	&1: Date &2-&3 were not build for event &4	Space: object requires documentation	☐
11	055	&1: &2-&3 have been updated according to data transport	Space: object requires documentation	☐
12	056	The summarization indicatior has not been set for field &1	Space: object requires documentation	☐
13	057	The summarization indicator has been set for field &1	Space: object requires documentation	☐
14	058	The characteristic &2 was not used	Space: object requires documentation	☐
15	059	Checks of standard information structures can display warnings	Space: object requires documentation	☐
16	060	&1: &2-&3 have not been filled by the source field and formula/program	Space: object requires documentation	☐
17	061	&1: &2-&3 should be filled by a user exit	Space: object requires documentation	☐
18	062	&1: &2-&3 has been built restrictively for event &4	Space: object requires documentation	☐
19	063	&1: Date &2-&3 is restrictively built for event &4	Space: object requires documentation	☐
20	064	&1: &2-&3 are updated according to data transport and conditions	Space: object requires documentation	☐
21	065	Unit &1 should not be used as a key figure	Space: object requires documentation	☐
22	066	You are using unit &1 and unit &2 in an info structure	Space: object requires documentation	☐
23	067	&1: &2 is not filled for event &4	Space: object requires documentation	☐
24	068	&1: &2 is not set up for event &4	Space: object requires documentation	☐
25	069	&1: &2 is set up restrictively fro event &4	Space: object requires documentation	☐
26	070	&1: &2 &3 use SELECT	Space: object requires documentation	☐
27	071	&1: &2 &3 use PERFORM	Space: object requires documentation	☐
28	072	&1: &2 &3 use CALL FUNCTION	Space: object requires documentation	☐
29	073	&1: The characteristic rules vary	Space: object requires documentation	☐
30	074	&1: Cumulative update without summation indicator	Space: object requires documentation	☐
31	075	&1: Update using data transport despite summation indicator	Space: object requires documentation	☐
32	076	&1: &2 &3 uses IMPORT/EXPORT	Space: object requires documentation	☐
33	077	The domain for field &1 has the output attribute 'Without +/- Sign'	Space: object requires documentation	☐
34	100	********** 100...124 reserved for application 04 (PPIS) **********	Space: object requires documentation	☐
35	101	&1: &2-&3 is not filled	Space: object requires documentation	☐
36	102	Update rule for &1 &2 &4 does not exist, but exists for &3	Space: object requires documentation	☐
37	103	You are using MCAFVG, MCCOMP und MCKALK in an info structure	Space: object requires documentation	☐
38	104	You are using unit &1	Space: object requires documentation	☐
39	105	&1: &2-&3 is updated for the period	Space: object requires documentation	☐
40	125	********** 125...149 reserved for application 03 (BCO) **********	Space: object requires documentation	☐
41	126	&1: Instead of using MCBEST-&2 use MCBEST-&3	Space: object requires documentation	☐
42	127	&1: MCBEST-&2 rather use a formula	Space: object requires documentation	☐
43	128	You are using values from the storage location	Space: object requires documentation	☐
44	129	&1: &2-&3 are updated only be event &4	Space: object requires documentation	☐
45	130	MCMSEG should not be accessed in the stock info structures	Space: object requires documentation	☐
46	200	********** 200...249 is reserved for application 01 (VIS) **********	Space: object requires documentation	☐
47	201	&1: Status fields &2-&3 have been changed without triggering &4	Space: object requires documentation	☐
48	202	&1: Conversion from &2 to &3 to &4 during set up is not possible	Space: object requires documentation	☐
49	203	&1: Date &2-&3 is INITIAL as long as no other changes have been made	Space: object requires documentation	☐
50	204	&1: Date &2-&3 is INITIAL as long as no other goods issue has been posted	Space: object requires documentation	☐
51	205	&1: Date &2-&3 is INITIAL if the schedule line has not been confirmed	Space: object requires documentation	☐
52	206	&1: Source field &2-&3 has not been filled for event VD	Space: object requires documentation	☐
53	207	&1: Updating in unit &2 creates problems	Space: object requires documentation	☐
54	208	&1: Updating with date field VDATU can be set up restrictively only	Space: object requires documentation	☐
55	209	WARNING: Changing the statistics currency causes data inconsistency	Space: object requires documentation	☐

History

Last changed on/by	19970617	SAP
SAP Release Created in