SAP ABAP Message Class MCEX (Extraction Interface LIS/BW)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LO-LIS (Application Component) Logistics Information System (LIS)
⤷ MCEX (Package) Extraction Interface LIS-BW
⤷ LO-LIS (Application Component) Logistics Information System (LIS)
⤷ MCEX (Package) Extraction Interface LIS-BW
Attributes
Message class | MCEX | |
Short Description | Extraction Interface LIS/BW | |
Changed On | 20110908 | |
Last Changed At | 171543 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Select a customer development class (e.g. Z001) | Space: object requires documentation | |
2 | 002 | MCS parameter not set. Do not transport append | Space: object requires documentation | |
3 | 003 | Unspecified error during table creation | Space: object requires documentation | |
4 | 004 | Communication structure &1 is used in extraction structure &2 | Space: object requires documentation | |
5 | 005 | Field & exists more than once | Space: object requires documentation | |
6 | 006 | No field was selected from communication structure & | Space: object requires documentation | |
7 | 007 | Incorrect DataSource & | Space: object requires documentation | |
8 | 008 | Extractor only defined for the "Full" and "Init" modes | Space: object requires documentation | |
9 | 009 | Setup table & for DataSource & does not exist | Space: object requires documentation | |
10 | 010 | Place the cursor on the V3 update field | Space: object requires documentation | |
11 | 011 | Place the cursor on the "Selection" field | Space: object requires documentation | |
12 | 012 | Place the cursor on the "Maintenance" field | Space: object requires documentation | |
13 | 013 | Place the cursor on the field of a DataSource | Space: object requires documentation | |
14 | 014 | Place the cursor on the "Active" or "Inactive" field | Space: object requires documentation | |
15 | 015 | Communication structure is not maintained | Space: object requires documentation | |
16 | 016 | There is no corresponding header structure | Space: object requires documentation | |
17 | 017 | There are no additional fields to be maintained | Space: object requires documentation | |
18 | 018 | Communication structure does not have an append structure | Space: object requires documentation | |
19 | 019 | Header structure adjusted successfully | Space: object requires documentation | |
20 | 020 | Database problems with table & | Space: object requires documentation | |
21 | 021 | Application & is not yet linked | Space: object requires documentation | |
22 | 022 | Internal error during field assignment (report to SAP) | Space: object requires documentation | |
23 | 023 | Setup tables deleted successfully | Space: object requires documentation | |
24 | 024 | DataSource & contains data still to be transferred | Space: object requires documentation | |
25 | 025 | Error while changing structure & (see long text) | Space: object requires documentation | |
26 | 026 | Include changes in XPRA for &1 &2 | Space: object requires documentation | |
27 | 027 | Extract structure &1 generated successfully, see long text | Space: object requires documentation | |
28 | 028 | You have not changed the extraction structure | Space: object requires documentation | |
29 | 029 | Update is activated. Note long text | Space: object requires documentation | |
30 | 030 | Log was successfully deleted | Space: object requires documentation | |
31 | 031 | DataSource & does not exist | Space: object requires documentation | |
32 | 032 | Field &1 cannot be selected because of unit field &2 -> see long text | Space: object requires documentation | |
33 | 101 | Messages not selected for reorganization. No message processing | Space: object requires documentation | |
34 | 102 | No events for processing inspection lots selected | Space: object requires documentation | |
35 | 103 | No extraction structure for event Q0: Messages active | Space: object requires documentation | |
36 | 104 | No extraction structure for event QE: Inspection results active | Space: object requires documentation | |
37 | 105 | No summarization result is selected | Space: object requires documentation | |
38 | 106 | No extraction structure for event I0: Messages active | Space: object requires documentation | |
39 | 107 | No extraction structure for event I0: Messages active | Space: object requires documentation | |
40 | 108 | Setup of inspection results finished (& documents read) | Space: object requires documentation | |
41 | 109 | Setup messages finished (& documents read) | Space: object requires documentation | |
42 | 110 | Setup for event I0: Messages finished | Space: object requires documentation | |
43 | 111 | & & | Space: object requires documentation | |
44 | 112 | Setup of inspection lot / usage decision finished (& lots read) | Space: object requires documentation | |
45 | 113 | There is no extraction structure for event QV: Inspection lot/VE active | Space: object requires documentation | |
46 | 114 | Orders not selected for setup. No order processing | Space: object requires documentation | |
47 | 115 | There is no extraction structure for event I3: Orders active | Space: object requires documentation | |
48 | 116 | Setup for event I3: Orders ended | Space: object requires documentation | |
49 | 117 | There is no extraction structure for event I3: Orders active | Space: object requires documentation | |
50 | 118 | SUBRC = &, Table & (data inconsistency) internal error | Space: object requires documentation | |
51 | 119 | Lead time for message & is negative and will be corrected to 0 | Space: object requires documentation | |
52 | 120 | Event '&': Data for inspection lot & has not been extracted | Space: object requires documentation | |
53 | 140 | Struct. from appl. &1 due to open V3 proc. not changed -> Long text | Space: object requires documentation | |
54 | 141 | Struct. appl. &1 cannot be changed due to setup table -> Long text | Space: object requires documentation | |
55 | 142 | No active updates for extractors in appl. &1 -> Long text | Space: object requires documentation | |
56 | 143 | Structure &1 cannot be changed due to data in delta management ->Long txt | Space: object requires documentation | |
57 | 144 | Structure &1 is not intended to be an extraction structure | Space: object requires documentation | |
58 | 145 | Extraction structure &1 was changed -> See long text | Space: object requires documentation | |
59 | 146 | Update activated -> Always observe long text | Space: object requires documentation | |
60 | 147 | Reading of RFC queue &1 with destination &2 already started | Space: object requires documentation | |
61 | 148 | Extraction log of application &1 was deleted | Space: object requires documentation | |
62 | 149 | Entries still exist in system &1 in the table MC12_PUFFER -> | Space: object requires documentation | |
63 | 150 | Check of extract structure &1 successfully completed -> Long text | Space: object requires documentation | |
64 | 151 | Entries for application &1 still exist in the extraction queue -> | Space: object requires documentation | |
65 | 152 | Structure maintenance not provided for extraction structure &1 -> | Space: object requires documentation | |
66 | 153 | Queue processing started (&1, &2, &3, &4) | Space: object requires documentation | |
67 | 154 | Extraction queue processing started &1 with &2 LUWs | Space: object requires documentation | |
68 | 155 | Processing of extraction queue &1 successfully ended | Space: object requires documentation | |
69 | 156 | Queue &1 could not be started due to system problems | Space: object requires documentation | |
70 | 157 | Queue &1 could not be started due to resource problems | Space: object requires documentation | |
71 | 158 | Error in processing queue &1: &2 | Space: object requires documentation | |
72 | 160 | Change of update mode not possible due to open V3 update -> Long text | Space: object requires documentation | |
73 | 161 | Change of update mode not possible due to queue entries -> Long text | Space: object requires documentation | |
74 | 162 | Update mode changed directly from delta -> Note long text | Space: object requires documentation | |
75 | 163 | Update mode changed for queued delta -> Note long text | Space: object requires documentation | |
76 | 164 | Update mode changed from unserialized V3 update -> Long text | Space: object requires documentation | |
77 | 165 | Update mode changed from serialized V3 update -> Long text | Space: object requires documentation | |
78 | 166 | Update mode changed from serialized V3 update -> Long text | Space: object requires documentation | |
79 | 167 | Update mode changed directly from delta -> Note long text | Space: object requires documentation | |
80 | 168 | Update mode changed from unserialized V3 update -> Long text | Space: object requires documentation | |
81 | 169 | Update mode changed for queued delta -> Note long text | Space: object requires documentation | |
82 | 171 | Multi-queue settings were changed for application &1 | Space: object requires documentation | |
83 | 172 | Cannot make changes to multi-queue parameters for application &1 | Space: object requires documentation | |
84 | 173 | Check the installed qRFC version -> Long text | Space: object requires documentation | |
85 | 180 | XPRA to switch update mode must be restarted | Space: object requires documentation | |
86 | 181 | "Serialized V3 update" setting is obsolete ->long text | Space: object requires documentation | |
87 | 182 | Display mode chosen. Changes will not take place | Space: object requires documentation | |
88 | 183 | XPRA for activating extract structure must be restarted | Space: object requires documentation | |
89 | 184 | Error while reading tables TMCEXACT and TMCEXUPD | Space: object requires documentation | |
90 | 185 | Error while reading table TMCEXUPD | Space: object requires documentation | |
91 | 190 | Attachment '&1' for the PI release is syntactically incorrect | Space: object requires documentation | |
92 | 191 | There is already an entry for the data entered | Space: object requires documentation | |
93 | 192 | Specify an include for extract structure &1 | Space: object requires documentation | |
94 | 193 | Internal error during hash code check (sy-subrc=&1) | The short text describes the object sufficiently | |
95 | 194 | Structures have changed (sy-subrc=&1) | The short text describes the object sufficiently | |
96 | 200 | No extraction structure active for application '05' | Space: object requires documentation | |
97 | 210 | In the EhP, you can make changes in the switch client only | The short text describes the object sufficiently | |
98 | 222 | Faulty entry in table TMCEXPRA for extraction structure '&1' | Space: object requires documentation | |
99 | 250 | The size of the extraction queue &1 has not been reduced | Space: object requires documentation | |
100 | 260 | DataSource &1: Data access using 'Direct Access' not possible | Space: object requires documentation | |
101 | 300 | Function for application &1 is not possible; queue is locked | Space: object requires documentation | |
102 | 301 | You do not have authorization to change Customizing | The short text describes the object sufficiently | |
103 | 302 | You do not have authorization to reconstruct the extraction queue | The short text describes the object sufficiently | |
104 | 303 | You do not have authorization to display the backup table | The short text describes the object sufficiently | |
105 | 304 | Logistics application &1 not found: | Space: object requires documentation | |
106 | 305 | Error while accessing queue &1 of application &2 | Space: object requires documentation | |
107 | 306 | Customizing was changed for application &1 | The short text describes the object sufficiently | |
108 | 307 | No data was found for the selection; application: &1 | The short text describes the object sufficiently | |
109 | 308 | &1 is not a TABLES parameter of qRFC function module &2 | The short text describes the object sufficiently | |
110 | 309 | Select either using collective runs or time stamps | The short text describes the object sufficiently | |
111 | 310 | Choose a start time stamp equal to or less than the end time stamp | The short text describes the object sufficiently |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in |