MCEX SAP Message class Extraktionsschnittstelle LIS/BW
MCEX is a standard message class available within your SAP system (depending on your version and release level). Below is a list of all the messages available for within this class and a link to any long text associated with each message. These messages are very simple to use and can be implemented into your ABAP code using the MESSAGE statement and the following syntax.
MESSAGE I001(MCEX).
Note the value "I" represents an information messsage but can be replaced with E for error, W for warning, S for Status/Success, A for Abend/Termination and X for exit which does not display a message and causes a runtime error. Click here for more information about SAP Messages.
Messages can also contain the & symbol, this means custom values can be added to the message when it is displayed, this is done using the WITH statement
MESSAGE I001(MCEX) with ld_field1.
Message class details can be viewed directly within your SAP system by entering the object name MCEX into the relevant SAP transaction such as SE91 or SE80.
001 - Select a customer development class (e.g. Z001)
002 - MCS parameter not set. Do not transport append
003 - Unspecified error during table creation
004 - Communication structure &1 is used in extraction structure &2
Additional information exists about message 004 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 004 class mcex.005 - Field & exists more than once
006 - No field was selected from communication structure &
007 - Incorrect DataSource &
008 - Extractor only defined for the 'Full' and 'Init' modes
009 - Setup table & for DataSource & does not exist
010 - Place the cursor on the V3 update field
011 - Place the cursor on the 'Selection' field
012 - Place the cursor on the 'Maintenance' field
013 - Place the cursor on the field of a DataSource
014 - Place the cursor on the 'Active' or 'Inactive' field
015 - Communication structure is not maintained
016 - There is no corresponding header structure
017 - There are no additional fields to be maintained
018 - Communication structure does not have an append structure
019 - Header structure adjusted successfully
020 - Database problems with table &
021 - Application & is not yet linked
022 - Internal error during field assignment (report to SAP)
023 - Setup tables deleted successfully
024 - DataSource & contains data still to be transferred
025 - Error while changing structure & (see long text)
Additional information exists about message 025 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 025 class mcex.026 - Include changes in XPRA for &1 &2
Additional information exists about message 026 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 026 class mcex.027 - Extract structure &1 generated successfully, see long text
Additional information exists about message 027 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 027 class mcex.028 - You have not changed the extraction structure
029 - Update is activated. Note long text
Additional information exists about message 029 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 029 class mcex.030 - Log was successfully deleted
031 - DataSource & does not exist
Additional information exists about message 031 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 031 class mcex.032 - Field &1 cannot be selected because of unit field &2 -> see long text
Additional information exists about message 032 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 032 class mcex.101 - Messages not selected for reorganization. No message processing
102 - No events for processing inspection lots selected
Additional information exists about message 102 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 102 class mcex.103 - No extraction structure for event Q0: Messages active
104 - No extraction structure for event QE: Inspection results active
105 - No summarization result is selected
106 - No extraction structure for event I0: Messages active
Additional information exists about message 106 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 106 class mcex.107 - No extraction structure for event I0: Messages active
Additional information exists about message 107 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 107 class mcex.108 - Setup of inspection results finished (& documents read)
109 - Setup messages finished (& documents read)
110 - Setup for event I0: Messages finished
111 - & &
112 - Setup of inspection lot / usage decision finished (& lots read)
113 - There is no extraction structure for event QV: Inspection lot/VE active
Additional information exists about message 113 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 113 class mcex.114 - Orders not selected for setup. No order processing
Additional information exists about message 114 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 114 class mcex.115 - There is no extraction structure for event I3: Orders active
Additional information exists about message 115 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 115 class mcex.116 - Setup for event I3: Orders ended
117 - There is no extraction structure for event I3: Orders active
Additional information exists about message 117 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 117 class mcex.118 - SUBRC = &, Table & (data inconsistency) internal error
119 - Lead time for message & is negative and will be corrected to 0
120 - Event '&': Data for inspection lot & has not been extracted
Additional information exists about message 120 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 120 class mcex.140 - Struct. from appl. &1 due to open V3 proc. not changed -> Long text
Additional information exists about message 140 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 140 class mcex.141 - Struct. appl. &1 cannot be changed due to setup table -> Long text
Additional information exists about message 141 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 141 class mcex.142 - No active updates for extractors in appl. &1 -> Long text
Additional information exists about message 142 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 142 class mcex.143 - Structure &1 cannot be changed due to data in delta management ->Long txt
Additional information exists about message 143 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 143 class mcex.144 - Structure &1 is not intended to be an extraction structure
145 - Extraction structure &1 was changed -> See long text
Additional information exists about message 145 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 145 class mcex.146 - Update activated -> Always observe long text
Additional information exists about message 146 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 146 class mcex.147 - Reading of RFC queue &1 with destination &2 already started
Additional information exists about message 147 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 147 class mcex.148 - Extraction log of application &1 was deleted
149 - Entries still exist in system &1 in the table MC12_PUFFER ->
Additional information exists about message 149 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 149 class mcex.150 - Check of extract structure &1 successfully completed -> Long text
Additional information exists about message 150 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 150 class mcex.151 - Entries for application &1 still exist in the extraction queue ->
Additional information exists about message 151 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 151 class mcex.152 - Structure maintenance not provided for extraction structure &1 ->
Additional information exists about message 152 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 152 class mcex.153 - Queue processing started (&1, &2, &3, &4)
154 - Extraction queue processing started &1 with &2 LUWs
155 - Processing of extraction queue &1 successfully ended
156 - Queue &1 could not be started due to system problems
157 - Queue &1 could not be started due to resource problems
158 - Error in processing queue &1: &2
160 - Change of update mode not possible due to open V3 update -> Long text
Additional information exists about message 160 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 160 class mcex.161 - Change of update mode not possible due to queue entries -> Long text
Additional information exists about message 161 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 161 class mcex.162 - Update mode changed directly from delta -> Note long text
Additional information exists about message 162 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 162 class mcex.163 - Update mode changed for queued delta -> Note long text
Additional information exists about message 163 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 163 class mcex.164 - Update mode changed from unserialized V3 update -> Long text
Additional information exists about message 164 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 164 class mcex.165 - Update mode changed from serialized V3 update -> Long text
Additional information exists about message 165 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 165 class mcex.166 - Update mode changed from serialized V3 update -> Long text
Additional information exists about message 166 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 166 class mcex.167 - Update mode changed directly from delta -> Note long text
Additional information exists about message 167 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 167 class mcex.168 - Update mode changed from unserialized V3 update -> Long text
Additional information exists about message 168 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 168 class mcex.169 - Update mode changed for queued delta -> Note long text
Additional information exists about message 169 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 169 class mcex.171 - Multi-queue settings were changed for application &1
Additional information exists about message 171 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 171 class mcex.172 - Cannot make changes to multi-queue parameters for application &1
Additional information exists about message 172 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 172 class mcex.173 - Check the installed qRFC version -> Long text
Additional information exists about message 173 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 173 class mcex.180 - XPRA to switch update mode must be restarted
Additional information exists about message 180 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 180 class mcex.181 - 'Serialized V3 update' setting is obsolete ->long text
Additional information exists about message 181 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 181 class mcex.182 - Display mode chosen. Changes will not take place
183 - XPRA for activating extract structure must be restarted
Additional information exists about message 183 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 183 class mcex.184 - Error while reading tables TMCEXACT and TMCEXUPD
Additional information exists about message 184 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 184 class mcex.185 - Error while reading table TMCEXUPD
Additional information exists about message 185 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 185 class mcex.190 - Attachment '&1' for the PI release is syntactically incorrect
Additional information exists about message 190 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 190 class mcex.191 - There is already an entry for the data entered
192 - Specify an include for extract structure &1
Additional information exists about message 192 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 192 class mcex.193 - Internal error during hash code check (sy-subrc=&1)
194 - Structures have changed (sy-subrc=&1)
200 - No extraction structure active for application '05'
Additional information exists about message 200 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 200 class mcex.210 - In the EhP, you can make changes in the switch client only
222 - Faulty entry in table TMCEXPRA for extraction structure '&1'
Additional information exists about message 222 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 222 class mcex.250 - The size of the extraction queue &1 has not been reduced
Additional information exists about message 250 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 250 class mcex.260 - DataSource &1: Data access using 'Direct Access' not possible
Additional information exists about message 260 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 260 class mcex.300 - Function for application &1 is not possible; queue is locked
Additional information exists about message 300 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 300 class mcex.301 - You do not have authorization to change Customizing
302 - You do not have authorization to reconstruct the extraction queue
303 - You do not have authorization to display the backup table
304 - Logistics application &1 not found:
Additional information exists about message 304 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 304 class mcex.305 - Error while accessing queue &1 of application &2
Additional information exists about message 305 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 305 class mcex.306 - Customizing was changed for application &1
307 - No data was found for the selection; application: &1
308 - &1 is not a TABLES parameter of qRFC function module &2
309 - Select either using collective runs or time stamps
310 - Choose a start time stamp equal to or less than the end time stamp
Search for further information about these or an SAP related objects