SAP ABAP Message Class OE (IS-Oil: ITA/TPI messages)

Basic Data

Hierarchy

☛ IS-OIL (Software Component) IS-OIL
   ⤷ IS-OIL-DS-TAS (Application Component) Interface to Terminal Automation System
     ⤷ OIK (Package) TAS/TPI Common Objects

Attributes

Message class	OE
Short Description	IS-Oil: ITA/TPI messages
Changed On	20081217
Last Changed At	135922

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	000	IS-Oil / TAS: Create SD/MM Calloff, Delivery, Goods issue (000-099)	The short text describes the object sufficiently	☐
2	001	Sales contract & does not exist	The short text describes the object sufficiently	☐
3	002	Delivery note & does not exist	The short text describes the object sufficiently	☐
4	003	Delivery note & does not have an item	The short text describes the object sufficiently	☐
5	004	Delivery note & has more than one item. TAS allows only one item	The short text describes the object sufficiently	☐
6	005	Purchase Calloff for delivery note & could not be created	The short text describes the object sufficiently	☐
7	006	Purchase Calloff item & & does not exist	The short text describes the object sufficiently	☐
8	007	Sales calloff was not created	The short text describes the object sufficiently	☐
9	008	Delivery note for sales calloff & was not created	The short text describes the object sufficiently	☐
10	009	Function OIK_LID_REFERENCE_GET abended: &	The short text describes the object sufficiently	☐
11	010	Function & does not exist	The short text describes the object sufficiently	☐
12	011	Function & is not active	The short text describes the object sufficiently	☐
13	012	Function OIK_LID_FUNCTIONS_GET abended: &	The short text describes the object sufficiently	☐
14	013	All functions for this IDOC succesfully processed	The short text describes the object sufficiently	☐
15	014	Idoc data changed	The short text describes the object sufficiently	☐
16	015	This Matchcode cannot be used by Transaction &	The short text describes the object sufficiently	☐
17	016	Material & cannot substitute material &	The short text describes the object sufficiently	☐
18	017	Unit of measure & is not an SAP unit of measure (is not in table 006)	The short text describes the object sufficiently	☐
19	018	Ship-to party & not maintained in contract &	The short text describes the object sufficiently	☐
20	019	Plant, storage location or shipping point is missing in E1OILT1	The short text describes the object sufficiently	☐
21	020	Purchase order no or item no is missing in E1OILT1	The short text describes the object sufficiently	☐
22	021	Function & does not process documents of type &	The short text describes the object sufficiently	☐
23	022	DB error during creation of LID Document Data Table OIK01	The short text describes the object sufficiently	☐
24	023	Error in Function OIK_CHANGEPTR_OILORD_CREATE (create change pointer)	The short text describes the object sufficiently	☐
25	024	Material temperatur and/or material temperatur unit is missing	The short text describes the object sufficiently	☐
26	025	Loading date in future (&) is not allowed	The short text describes the object sufficiently	☐
27	026	Batch and valuation type together are not allowed in E1OILT1	The short text describes the object sufficiently	☐
28	027	Shipping point & not allowed for plant & Storage location &	The short text describes the object sufficiently	☐
29	028	Items deleted from CVBAP in VBAP_KOPIEREN_PRUEFEN(FV45CF0V)	The short text describes the object sufficiently	☐
30	029	Error in exchange assignment.	The short text describes the object sufficiently	☐
31	030	& Idoc(s) with load information forwarded	The short text describes the object sufficiently	☐
32	031	Field &: '&' / First byte is not a valid character	The short text describes the object sufficiently	☐
33	032	Field &: '&' / Invalid character in field	The short text describes the object sufficiently	☐
34	033	Field &: '&' / Multiple decimal point is not allowed	The short text describes the object sufficiently	☐
35	034	Field &: '&' / Field is not fullfilled by spaces	The short text describes the object sufficiently	☐
36	035	Field &: '&' / Decimal point is not allowed	The short text describes the object sufficiently	☐
37	036	Field &: '&' / Minus sign is not allowed	The short text describes the object sufficiently	☐
38	037	Field &: Reserve	The short text describes the object sufficiently	☐
39	038	field &: Reserve	The short text describes the object sufficiently	☐
40	039	Field &: '&' / Unknown error	The short text describes the object sufficiently	☐
41	040	Error in function OIK_SD_DELIVERY_CREATE (&) _	The short text describes the object sufficiently	☐
42	041	Error in function OIK_EXTERNAL_ASTM_DATA_GET		☐
43	042	Program abended because of abnormal situation	The short text describes the object sufficiently	☐
44	043	Calloff & and delivery & have been saved.	The short text describes the object sufficiently	☐
45	044	Neither a calloff nor a delivery has been saved.	The short text describes the object sufficiently	☐
46	045	Calloff & has been saved.	The short text describes the object sufficiently	☐
47	046	Item & & is completely processed.	The short text describes the object sufficiently	☐
48	047	Undefined error during creation of purchase calloff (ROIALB02).	Space: object requires documentation	☐
49	048	This delivery was created by the TAS Interface and can only be displayed		☐
50	049	The number of calloff items differ from the number of load items	The short text describes the object sufficiently	☐
51	050	The number of delivery items differ from the number of calloff items	The short text describes the object sufficiently	☐
52	051	There are no deliveries selected	The short text describes the object sufficiently	☐
53	052	Function &1 not successfully carried out for IDoc &2	The short text describes the object sufficiently	☐
54	053	Shipment type & not defined for auto del conf at &	The short text describes the object sufficiently	☐
55	054	UoM conversion from ISO to SAP not possible for & &	The short text describes the object sufficiently	☐
56	055	Material conversion from EAN to SAP not possible for &	The short text describes the object sufficiently	☐
57	056	Shipment number missing	The short text describes the object sufficiently	☐
58	057	Changes to BAPI data not allowed for shipment type & at &	The short text describes the object sufficiently	☐
59	058	Changes to BAPI data not allowed for DCP in status &	The short text describes the object sufficiently	☐
60	059	DCP data & & currently locked	The short text describes the object sufficiently	☐
61	060	Update of delivery confirmation table not possible for & &	The short text describes the object sufficiently	☐
62	061	Trigger of BP Event & not possible for & &	The short text describes the object sufficiently	☐
63	062	Shipment & not yet scheduled	The short text describes the object sufficiently	☐
64	063	Shipment & closed > no more changes possible	The short text describes the object sufficiently	☐
65	064	Shipment & not loaded -> del. confirmation not possible	The short text describes the object sufficiently	☐
66	065	Shipment & nothing to do	The short text describes the object sufficiently	☐
67	066	Sales order & + delivery & created	The short text describes the object sufficiently	☐
68	067	Shipment & not completely confirmed	The short text describes the object sufficiently	☐
69	068	Previous shipment number is missing	The short text describes the object sufficiently	☐
70	069	No function group defined for delivery confirmation process	The short text describes the object sufficiently	☐
71	070	More than one function group defined for delivery confirmation process	The short text describes the object sufficiently	☐
72	071	No function group defined for TPI interface	The short text describes the object sufficiently	☐
73	072	More than one function group defined for TPI interface	The short text describes the object sufficiently	☐
74	073	Enhancement OIKSTRS1 must be migrated to OIKSTRS2 -> see long text	Space: object requires documentation	☐
75	074	The TPI relevancy has been moved to a new tool --> see long text	Space: object requires documentation	☐
76	080	Create delivery for order that has been passed to external TPI system?	Space: object requires documentation	☐
77	081	Create delivery due list for order that has been passed to TPI system?	Space: object requires documentation	☐
78	082	Assign delivery for TPI-relevant orders to TD shipments?	Space: object requires documentation	☐
79	083	Change shipment that has been created by the external TPI system?	Space: object requires documentation	☐
80	092	Function 'OIK_CUSTOMER_FUNCTION_EXAMPLE' not successfully carried out	The short text describes the object sufficiently	☐
81	093	Function 'OIK CUSTOMER FUNCTION EXAMPLE' successful	The short text describes the object sufficiently	☐
82	100		The short text describes the object sufficiently	☐
83	101	No driver IDoc created. No data selected.	The short text describes the object sufficiently	☐
84	102	No rack meter IDoc created. No data selected.	The short text describes the object sufficiently	☐
85	103	No compartment meter IDoc created. No data selected.	The short text describes the object sufficiently	☐
86	104	No transport unit IDoc created. No data selected.	The short text describes the object sufficiently	☐
87	105	No vehicle IDoc created. No data selected.	The short text describes the object sufficiently	☐
88	106	No IDoc created. No data selected.	The short text describes the object sufficiently	☐
89	149		The short text describes the object sufficiently	☐
90	150	Shipment number & does not exist.	The short text describes the object sufficiently	☐
91	151	Shipment & is already delivery confirmed. Process not possible.	The short text describes the object sufficiently	☐
92	152	No vehicle exists in shipment & in status 4 or 5.	The short text describes the object sufficiently	☐
93	153	Prior-to-load changes are allowed only for scheduled shipments	The short text describes the object sufficiently	☐
94	200	IS-OIL/TAS Data Maintenance (200-299)	The short text describes the object sufficiently	☐
95	201	Item not TAS relevant	The short text describes the object sufficiently	☐
96	202	Load-Id deactivated	The short text describes the object sufficiently	☐
97	203	Load-Id deleted	The short text describes the object sufficiently	☐
98	204	Load-Id already exists	The short text describes the object sufficiently	☐
99	205	Load-Id copied from Master-Data	The short text describes the object sufficiently	☐
100	206	Choose an entry	The short text describes the object sufficiently	☐
101	207	No TAS-Data maintained for item &	The short text describes the object sufficiently	☐
102	208	Data copied from Master-Data	The short text describes the object sufficiently	☐
103	209	Load-Id not found in Master-Data! Please use PF4 for help!	The short text describes the object sufficiently	☐
104	210	Validity period overlaps existing period in TAS Reference table	The short text describes the object sufficiently	☐
105	211	Item not TAS relevant - Data will be displayed	The short text describes the object sufficiently	☐
106	212	Copy-Flag active - Data will be displayed	The short text describes the object sufficiently	☐
107	213	The entered item &/& is not a purchase order or a purchase contract item	The short text describes the object sufficiently	☐
108	214	Purchase item & & is not exchange-related	The short text describes the object sufficiently	☐
109	215	Please enter MM-Document number	The short text describes the object sufficiently	☐
110	216	End of validity period must be 'greater or equal to' (later than) start	The short text describes the object sufficiently	☐
111	217	Validity period has to be within the contract start and end dates	The short text describes the object sufficiently	☐
112	218	No history data available	The short text describes the object sufficiently	☐
113	219	Invalid date &	The short text describes the object sufficiently	☐
114	220	Invalid time &	The short text describes the object sufficiently	☐
115	221	No valid Load-Id of LID type & found	Space: object requires documentation	☐
116	222	Error during INSERT & & &	The short text describes the object sufficiently	☐
117	223	Error during UPDATE & & &	The short text describes the object sufficiently	☐
118	224	Error during DELETE & & &	The short text describes the object sufficiently	☐
119	225	LID & - & is currently locked by user &	The short text describes the object sufficiently	☐
120	226	System error during locking procedure	The short text describes the object sufficiently	☐
121	227	Error during locking procedure	The short text describes the object sufficiently	☐
122	228	Already editing new record	The short text describes the object sufficiently	☐
123	229	Validity period changed! Please check Load IDs	The short text describes the object sufficiently	☐
124	230	Invalid adjustment of validation period! Please correct Load IDs.	The short text describes the object sufficiently	☐
125	231	Please maintain contract start/end date for Load-Id assignment	The short text describes the object sufficiently	☐
126	232	Valid Load IDs of type & exist but marked for deletion/blocking	The short text describes the object sufficiently	☐
127	240	Field & is not valid for TAS Relevance Pickup	The short text describes the object sufficiently	☐
128	241	Please maintain ranking for field &	The short text describes the object sufficiently	☐
129	242	Field & is not valid for TAS Relevance Shipment	The short text describes the object sufficiently	☐
130	250	Shipment &: Receiving plant & not scheduled	The short text describes the object sufficiently	☐
131	251	Shipment &: Document/Plant not unique	The short text describes the object sufficiently	☐
132	252	Shipment &: Document not found	The short text describes the object sufficiently	☐
133	253	Shipment &: Document type not supported	The short text describes the object sufficiently	☐
134	300	LID-type &1 already used. Please specify a unique LID-type	The short text describes the object sufficiently	☐
135	301	Control structure &1 already used! Please specify a unique Control Struc	The short text describes the object sufficiently	☐
136	302	LID-Type &1 entered twice! Enter a new LID Type.	The short text describes the object sufficiently	☐
137	303	Control Structure &1 entered twice ! Please enter a new Control Structure	The short text describes the object sufficiently	☐
138	304	No Entry for field &1! Please enter a value!	The short text describes the object sufficiently	☐
139	305	Entry &1 is not valid for field &2! Please use PF4 for help!	The short text describes the object sufficiently	☐
140	306	Lid-Type &1 not valid &2! Please use PF4 for help!	The short text describes the object sufficiently	☐
141	307	LID NO &1 is not active and can't be used!	The short text describes the object sufficiently	☐
142	308	SeqNo &1 already used for Function Group &2! Please choose a new Number.	The short text describes the object sufficiently	☐
143	309	Seq-No &1 entered twice in editor mode! Choose a different one!	The short text describes the object sufficiently	☐
144	310	Subsequent document type &1 is not valid for document category &2	The short text describes the object sufficiently	☐
145	311	For document category &1 no subsequent document type is available	The short text describes the object sufficiently	☐
146	312	The document type & is not valid for orders!	The short text describes the object sufficiently	☐
147	313	Enter a value for number range number! Field is mandatory!	The short text describes the object sufficiently	☐
148	314	Number range number &1 does not exist for object OIK_LID!	The short text describes the object sufficiently	☐
149	400	IS-Oil / TAS: Reports (400-499)	The short text describes the object sufficiently	☐
150	416	Please position cursor into a valid line in the list.	The short text describes the object sufficiently	☐
151	417	Place Cursor on a LID-Number, SD-DocNo or IdocNo to show their details.	The short text describes the object sufficiently	☐
152	418	No data found for LID & in tables OIKLID and OIKLIDW	The short text describes the object sufficiently	☐
153	419	Please position cursor on a valid SD-DocNo.	The short text describes the object sufficiently	☐
154	420	Please position cursor on a valid LID-Number.	The short text describes the object sufficiently	☐
155	421	Internal Error: List No &1	The short text describes the object sufficiently	☐
156	422	Int.Error: No equiv. entry to OIK02B in OIK01 SD-DocNo &, LIDNO &	The short text describes the object sufficiently	☐
157	423	Int.Error: No entry in VBAP for KDAUF &,ITEM &	The short text describes the object sufficiently	☐
158	424	Int.Err: More than 1 entry in VBAP for KDAUF &, ERDAT &	The short text describes the object sufficiently	☐
159	425	Int.Err: No entry in LIPS for Delivery &, Item &	The short text describes the object sufficiently	☐
160	426	Int.Err: More than 1 entry in LIPS for LIEFN &, ERDAT &	The short text describes the object sufficiently	☐
161	427	Int.Error: more than 1 entry in OIK01 for SD-DocNo &, LIDNO &	The short text describes the object sufficiently	☐
162	428	Int.Err: No entry in table OIKLRT for Spras &, Reatype &, Reacode &	The short text describes the object sufficiently	☐
163	429	Place Cursor on a LID-Number or SD-DocNo to display details	The short text describes the object sufficiently	☐
164	440	Could not find data for SD-DocNo & in VBAK or LIKP	The short text describes the object sufficiently	☐
165	441	Please position the cursor on a field that is not empty	The short text describes the object sufficiently	☐
166	442	Place Cursor on a valid LID	The short text describes the object sufficiently	☐
167	443	Place Cursor on a valid SD-DocNo	The short text describes the object sufficiently	☐
168	444	Place Cursor on a valid Idoc-Number	The short text describes the object sufficiently	☐
169	450	Number of Documents per Job recalculated !	The short text describes the object sufficiently	☐
170	451	&: IDOC: & - LID: & - MSG: &	The short text describes the object sufficiently	☐
171	452	& IDOCs selected	The short text describes the object sufficiently	☐
172	453	Recieve RFC failed: & & & &	The short text describes the object sufficiently	☐
173	454	Get Tasklist error: & & & &	The short text describes the object sufficiently	☐
174	455	Set Tasklist error: & & & &	The short text describes the object sufficiently	☐
175	456	Parallel processing canceled ( & RFCs failed = & % )	The short text describes the object sufficiently	☐
176	457	Goods issue: & & & &	The short text describes the object sufficiently	☐
177	458	Reset Tasklist: & - IDOC: & - LID: & - MSG: &	The short text describes the object sufficiently	☐
178	459	& & & &	The short text describes the object sufficiently	☐
179	508	No selection group activated	The short text describes the object sufficiently	☐
180	509	Transportation Planning Point & not assigned to external planning system		☐
181	510	There are no Transport Planning Points with external planning systems		☐
182	511	Transportation Planning Point & is not defined		☐
183	512	No receiving system defined	The short text describes the object sufficiently	☐
184	515	No receiving system defined	The short text describes the object sufficiently	☐
185	516	Compartments cannot be copied to new vehicle &1	Space: object requires documentation	☐
186	517	Compartments do not exist	The short text describes the object sufficiently	☐
187	518	Vehicle &1 has not been scheduled	The short text describes the object sufficiently	☐
188	519	No load-relevant data found for the shipment &1	The short text describes the object sufficiently	☐
189	520	No ext. planning systems have been maintained for trans. planning points	The short text describes the object sufficiently	☐
190	521	Specification SELECTION_SET and SELECT_OPTIONS are alternatives	The short text describes the object sufficiently	☐
191	522	Set checkbox	The short text describes the object sufficiently	☐
192	550	Changing Hierarchy causes the Relevance to be updated automatically.	The short text describes the object sufficiently	☐
193	555	ARRAY op error: DB table=&, op=&, rc=&, lines=&		☐
194	556	SAVE op error: & unknown entries on & posting table, key= & &		☐
195	559	Inconsistency in program &, global doc no = &, local doc no = &	The short text describes the object sufficiently	☐
196	600	& location descriptions sent to the transportation planning system	The short text describes the object sufficiently	☐
197	606	The OIL-TPI subsystem has been de-activated in this client	The short text describes the object sufficiently	☐
198	607	The OIL-TPI subsystem has been activated in this client	The short text describes the object sufficiently	☐
199	609	Table group authorization OIK is missing for this transaction	The short text describes the object sufficiently	☐
200	610	Order & is currently blocked by another user	The short text describes the object sufficiently	☐
201	611	Order & already transmitted to planning system &	The short text describes the object sufficiently	☐
202	612	No data determined for the selection.	The short text describes the object sufficiently	☐
203	613	& output records created. & could not be created.	The short text describes the object sufficiently	☐
204	614	No orders found for the selection specified	The short text describes the object sufficiently	☐
205	615	No message type combined with IDoc	The short text describes the object sufficiently	☐
206	616	No message type chosen for IDoc processing!	The short text describes the object sufficiently	☐
207	617	No TPI relevant item for order &.	The short text describes the object sufficiently	☐
208	620	IDoc category & is not defined for communication with logical system &	The short text describes the object sufficiently	☐
209	630	The selection log is empty		☐
210	640	&1 is an invalid date (choose a date between &2 and &3)	The short text describes the object sufficiently	☐
211	641	All subsequent lines after date &1 will be lost	The short text describes the object sufficiently	☐
212	642	Choosen times for date & are overlapping other times of the time table	The short text describes the object sufficiently	☐
213	643	The date &1 is more than one year behind the date &2	The short text describes the object sufficiently	☐
214	644	All lines with dates earlier than &1 will be lost	The short text describes the object sufficiently	☐
215	645	&1: No congruence concerning master data (&2 - &3)	The short text describes the object sufficiently	☐
216	646	&1: 'time from' and 'time to' can't be the same	The short text describes the object sufficiently	☐
217	647	&1: No overlap between time frame and master data (&2 - &3)	The short text describes the object sufficiently	☐
218	648		The short text describes the object sufficiently	☐
219	649	&1: Time frame data do not match the customer master data	The short text describes the object sufficiently	☐
220	650	Order & cannot be sent to TPS. It has exceeded the credit limit.	The short text describes the object sufficiently	☐
221	651	From Date must be earlier than To Date	The short text describes the object sufficiently	☐
222	652	From Time must be earlier than To Time	The short text describes the object sufficiently	☐
223	700	Vehicle & is not assigned to driver &	The short text describes the object sufficiently	☐
224	701	Consider the subsequent delivery documents (Refresh)	The short text describes the object sufficiently	☐
225	702	Deletion failed! Please refresh list!		☐
226	703	Log entry(-ies) deleted!	The short text describes the object sufficiently	☐
227	704	No table entries found for specified key	The short text describes the object sufficiently	☐
228	705	Delivery & already planned by foreign user - Replanning Shipment ...	The short text describes the object sufficiently	☐
229	706	Place cursor on a valid entry of the log table	The short text describes the object sufficiently	☐
230	707	No log table entry selected	The short text describes the object sufficiently	☐
231	708	Place cursor on a valid item line	The short text describes the object sufficiently	☐
232	710	Delivery & has different Load Plants (selection from first item)	The short text describes the object sufficiently	☐
233	711	Vehicle has to be maintained for shipments to be created	The short text describes the object sufficiently	☐
234	712	Collecting data ended with Warnings. Shipment->Check->Display Warnings	The short text describes the object sufficiently	☐
235	713	Drv./Veh.-Assignm. not maintained for Driver &1 at &2 Shift &3.	The short text describes the object sufficiently	☐
236	714	Check ended with Warnings. Shipment->Check->Display Warnings	The short text describes the object sufficiently	☐
237	715	Shipment & has already been &	The short text describes the object sufficiently	☐
238	716	Shipment & does not exist	The short text describes the object sufficiently	☐
239	717	Please enter document sequence number	The short text describes the object sufficiently	☐
240	718	Duplicate entries for document sequence within a trip	The short text describes the object sufficiently	☐
241	719	Please enter trip sequence number	The short text describes the object sufficiently	☐
242	720	Delivery & has already been assigned	The short text describes the object sufficiently	☐
243	721	Delivery & does not exist	The short text describes the object sufficiently	☐
244	722	Delivery & has already been &	The short text describes the object sufficiently	☐
245	723	Document & does not exist	The short text describes the object sufficiently	☐
246	724	Please choose Shipment from planning screen	The short text describes the object sufficiently	☐
247	725	Object Shipment & is in use by user &	The short text describes the object sufficiently	☐
248	726	System error during locking shipment &	The short text describes the object sufficiently	☐
249	727	Error during locking shipment &	The short text describes the object sufficiently	☐
250	728	Document & is assigned to shipment &. Generation will change assignment.	The short text describes the object sufficiently	☐
251	729	Duplicate entries for Trip sequence number	The short text describes the object sufficiently	☐
252	730	Trip number required for Shipments to be created	The short text describes the object sufficiently	☐
253	731	Vehicle & in Shipment & don't match the maintained Vehicle assignment	The short text describes the object sufficiently	☐
254	732	Nothing to generate	The short text describes the object sufficiently	☐
255	733	Shipment & has been deleted. Shipment will be removed from Planning	The short text describes the object sufficiently	☐
256	734	Shipment & has already been &	The short text describes the object sufficiently	☐
257	735	Vehicle & has already been assigned	The short text describes the object sufficiently	☐
258	736	The Vehicle assignment data for driver & was saved	The short text describes the object sufficiently	☐
259	737	The data was already saved	The short text describes the object sufficiently	☐
260	738	Driver &1 and Vehicle &2 do not match the location	The short text describes the object sufficiently	☐
261	739	Check performed successfully	The short text describes the object sufficiently	☐
262	740	Data is currently locked by user &. Display only	The short text describes the object sufficiently	☐
263	741	System error during locking procedure	The short text describes the object sufficiently	☐
264	742	Error during locking procedure	The short text describes the object sufficiently	☐
265	743	Enter planned start date for shipment	The short text describes the object sufficiently	☐
266	744	Shipment type does not exist	The short text describes the object sufficiently	☐
267	745	Only Shipments with matching Transp.Plann.Point & can be included	The short text describes the object sufficiently	☐
268	746	Include failed. Shipment &1 is already in Trip Planning	The short text describes the object sufficiently	☐
269	747	Generation executed successfully	The short text describes the object sufficiently	☐
270	748	Generation executed with warnings	The short text describes the object sufficiently	☐
271	749	Delivery & & &	The short text describes the object sufficiently	☐
272	750	Ranking of TAS Relevance fields not maintained	The short text describes the object sufficiently	☐
273	751	View is not designed for field &	The short text describes the object sufficiently	☐
274	752	Assignment for driver &, vehicle &, shift & and date & read from database	The short text describes the object sufficiently	☐
275	753	Assignment for vehicle & not possible. Wrong transport. planning point.	The short text describes the object sufficiently	☐
276	754	Driver vehicle assignment saved for transportation planning point &.	The short text describes the object sufficiently	☐
277	755	Vehicle & already assigned to driver & in same shift on same day.	The short text describes the object sufficiently	☐
278	756	Error during locking of driver vehicle assignment	The short text describes the object sufficiently	☐
279	757	No vehicle within specified range & to & for transp. planning point &.	The short text describes the object sufficiently	☐
280	758	Assignment for driver &, vehicle &, shift & and date & read from database	The short text describes the object sufficiently	☐
281	759	Duplicate key for vehicle & driver & loaddate & shift &.	The short text describes the object sufficiently	☐
282	760	Select at least one Shipment stage	The short text describes the object sufficiently	☐
283	801		The short text describes the object sufficiently	☐
284	806	Manual changes to ETA are not allowed as user exit OIKSHPPL is active	The short text describes the object sufficiently	☐
285	807	& location descriptions sent to the Transportation Planning System	The short text describes the object sufficiently	☐
286	808	No entry for message type & in edimsg found. No IDocs will be created.	The short text describes the object sufficiently	☐
287	809	No parallel use of application objects allowed	The short text describes the object sufficiently	☐
288	843	&1 entries of &2 selected entries have been deleted	The short text describes the object sufficiently	☐
289	844	Shipment & and the underlying documents have been re-created	The short text describes the object sufficiently	☐
290	845	Simultaneous use of swap deliveries and delivery item maintenance	Space: object requires documentation	☐
291	846	Sales order & created	The short text describes the object sufficiently	☐
292	847	Internal order & exists in SAP system	The short text describes the object sufficiently	☐
293	848	Document & unplanned from shipment & via IDoc &.	The short text describes the object sufficiently	☐
294	849	Referencing is not unique within the same qualifier	The short text describes the object sufficiently	☐
295	850	Messages for inbound shipment processing	The short text describes the object sufficiently	☐
296	851	Missing E1OILSQ segment for order & position &.	The short text describes the object sufficiently	☐
297	852	Shipment deletion is not possible, since no the creation was no success	The short text describes the object sufficiently	☐
298	853	Shipment & was already deleted via another IDoc	The short text describes the object sufficiently	☐
299	854	Shipment & deleted via IDoc &	The short text describes the object sufficiently	☐
300	855	Delivery & was already deleted via another position or IDoc	The short text describes the object sufficiently	☐
301	856	Delivery & deleted using IDoc &	The short text describes the object sufficiently	☐
302	857	No apropriate delivery for item & position & on shipment & (external no).	The short text describes the object sufficiently	☐
303	858	No apropriate order for item & position & on shipment & (external no's).	The short text describes the object sufficiently	☐
304	859	Order & deleted via IDoc &	The short text describes the object sufficiently	☐
305	860	Order & was already deleted via another position or IDoc.	The short text describes the object sufficiently	☐
306	861	No shipment was created for the external number &!	The short text describes the object sufficiently	☐
307	862	No entry within OIK29 with the right status for doc. & position &!	The short text describes the object sufficiently	☐
308	863	Shipment with external no. &: Change not possible, error with items!	The short text describes the object sufficiently	☐
309	864	No E1OILSI segment found for E1OILSP segment. Item no. & position no. &	The short text describes the object sufficiently	☐
310	865	Allocation of document & on shipment &, changed via IDoc &	The short text describes the object sufficiently	☐
311	866	Document & planned onto Shipment & via IDoc &.	The short text describes the object sufficiently	☐
312	867	Document & created via IDoc &.	The short text describes the object sufficiently	☐
313	868	Document & not planned onto a shipment (via IDoc &).	The short text describes the object sufficiently	☐
314	869	Document & unplanned via IDoc &.	The short text describes the object sufficiently	☐
315	870	Old deliveries deleted	The short text describes the object sufficiently	☐
316	871	No deletion of old deliv. for order & pos &. Missing related pos. in IDoc	The short text describes the object sufficiently	☐
317	872	No change of order for order & pos &. Delivery exists.	The short text describes the object sufficiently	☐
318	873	No change of order for order & pos &. Other docs than delivery exist.	The short text describes the object sufficiently	☐
319	874	No change of order for order & pos &. Internal Delivery exists.	The short text describes the object sufficiently	☐
320	875	Unknown change sign for order & position &.	The short text describes the object sufficiently	☐
321	876	Reference to non-existing order. External order & posnr &.	The short text describes the object sufficiently	☐
322	877	Wrong plant without change sign on incoming order & posnr &.	The short text describes the object sufficiently	☐
323	878	delivery recreated via IDoc &. New delivery no. & old no &.	The short text describes the object sufficiently	☐
324	879	Related order & position & changed by incoming IDoc &	The short text describes the object sufficiently	☐
325	880	Storage object assignment could not be saved for doc & on IDoc &!	The short text describes the object sufficiently	☐
326	881	Processing not possible. Missing data entry.	The short text describes the object sufficiently	☐
327	882	Specify only order or delivery.	The short text describes the object sufficiently	☐
328	883	Position on different deliveries.	The short text describes the object sufficiently	☐
329	884	No sold-to maintained for order & ship-to &.	The short text describes the object sufficiently	☐
330	885	Unit of measure conversion not possible for order & unit & Reason &	The short text describes the object sufficiently	☐
331	886	Too many sold-to's maintained for order & ship-to &.	The short text describes the object sufficiently	☐
332	887	Processing of Shipment abandonned by user & at &.	The short text describes the object sufficiently	☐
333	888	Automatic determination of Storage loc. not possible, multiple options.	The short text describes the object sufficiently	☐
334	889	Material not available at plant & storage location &.	The short text describes the object sufficiently	☐
335	890	Plant is not changed. No processing necessity.	The short text describes the object sufficiently	☐
336	891	Missing unit of measure for documenet with external no. & position &	The short text describes the object sufficiently	☐
337	892	Shipment type could not be determined for shipment & on IDoc &!	The short text describes the object sufficiently	☐
338	893	Internal update to segment numbering failed for shipment & on IDoc &!	The short text describes the object sufficiently	☐
339	894	Shipment & not created. Previous documents ended with errors.	The short text describes the object sufficiently	☐
340	895	IDoc processing failed. Check TPI flow log for error details.	The short text describes the object sufficiently	☐
341	896	Delivery & deleted. Substitute delivery & created.	The short text describes the object sufficiently	☐
342	897	Material &1 in Document &2 item &3 different from loaded material &4.	The short text describes the object sufficiently	☐
343	898	Select the shipment that you want to display	The short text describes the object sufficiently	☐
344	899	Deletion of the document & failed.	The short text describes the object sufficiently	☐
345	990	Ranking of TAS Relevance fields not maintained	The short text describes the object sufficiently	☐

History

Last changed on/by	20081217	SAP
SAP Release Created in