SAP ABAP Message Class SPC02 (Messages for 2nd phase of SPEC2000)

Basic Data

Hierarchy

☛ ECC-DIMP (Software Component) DIMP
   ⤷ IS-AD-SPC (Application Component) Specification 2000
     ⤷ AD_SPC_PH2_GEN (Package) All central objects for 2nd phase of SPEC2000

Attributes

Message class	SPC02
Short Description	Messages for 2nd phase of SPEC2000
Changed On	20110810
Last Changed At	071312

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	001	Message &1 with code &2 and function &3 not defined in table SPCPORTFUN	The short text describes the object sufficiently	☐
2	002	Function module &1 does not exist	The short text describes the object sufficiently	☐
3	003	Partner profile for the message &1 is not set with EDISTD as 'A'	The short text describes the object sufficiently	☐
4	004	Minimun/maximum length violation in field '&' in segment number '&'	The short text describes the object sufficiently	☐
5	401	Material & couldn't be assigned to FFF class &	The short text describes the object sufficiently	☐
6	550	No SPEC2K IDocs were found based on your selection criteria	The short text describes the object sufficiently	☐
7	551	Only one discount percent (DIS or PDP) should be present	The short text describes the object sufficiently	☐
8	552	No IDOCs to display	The short text describes the object sufficiently	☐
9	553	Select one IDOC to display	The short text describes the object sufficiently	☐
10	600	File '&' could not be opened for output	The short text describes the object sufficiently	☐
11	601	Mandatory field check failed for field '&' in segment number '&'	The short text describes the object sufficiently	☐
12	602	SPEC2K IDoc and SPEC2K flatfile structure are not consistent	The short text describes the object sufficiently	☐
13	603	Related fields not maintained for field '&' in segment number '&'	The short text describes the object sufficiently	☐
14	604	Type violation in field '&' in segment number '&' or max length violation	The short text describes the object sufficiently	☐
15	605	Decimal places violation in field '&' in segment number '&'	The short text describes the object sufficiently	☐
16	606	Minimun/maximum length violation in field '&' in segment number '&'	The short text describes the object sufficiently	☐
17	607	Tables 'SPCFILE' and 'SPCDTEL' are not consistent	The short text describes the object sufficiently	☐
18	608	No entries in table SPCFILE for key MESTYP '&', MESFCT '&' and MESCOD '&'	The short text describes the object sufficiently	☐
19	609	Unable to identify message function	The short text describes the object sufficiently	☐
20	610	Field '&' should not occur in message type '&' with message function '&'	The short text describes the object sufficiently	☐
21	611	Structure of inbound SPEC2K flatfile is not valid	The short text describes the object sufficiently	☐
22	612	Underlying basic type not found for message type '&' in table 'EDIMSG'	The short text describes the object sufficiently	☐
23	613	Receiver/sender address information missing in SPEC message header	The short text describes the object sufficiently	☐
24	614	Partner profile not maintained in table 'SPCPRTNRINF' for rcvr &, sndr &	The short text describes the object sufficiently	☐
25	615	Rcvr/sndr not maintained in table 'SPCPRTNRINF' for given partner profile	The short text describes the object sufficiently	☐
26	616	No entries found in table 'IDOCSYN' for IDOCTYP '&'	The short text describes the object sufficiently	☐
27	617	Command acknowledgment received successfully	The short text describes the object sufficiently	☐
28	618	Too late acknowledgement of the command	The short text describes the object sufficiently	☐
29	619	Source IDoc could not be located	The short text describes the object sufficiently	☐
30	620	Maximum length violation in field '&'	The short text describes the object sufficiently	☐
31	621	Either the first or the last character of field '&' is a '-'	The short text describes the object sufficiently	☐
32	622	'-' does not occur between two numerals in field '&'	The short text describes the object sufficiently	☐
33	623	SPEC2K IDoc could not be opened for edit	The short text describes the object sufficiently	☐
34	624	SPEC2K IDoc could not be changed	The short text describes the object sufficiently	☐
35	625	SPEC2K IDoc could not be closed for edit	The short text describes the object sufficiently	☐
36	626	Data set group '&' is not maintained properly	The short text describes the object sufficiently	☐
37	627	INA or PAY check failed; inconsistent S1NVOICE message	The short text describes the object sufficiently	☐
38	628	POC or QTL check failed; inconsistent S1ORDEXC message	The short text describes the object sufficiently	☐
39	629	S1NVOICE acknowledgement could not be sent out; internal error	The short text describes the object sufficiently	☐
40	630	S1ORDEXC acknowledgement could not be sent out; internal error	The short text describes the object sufficiently	☐
41	631	More than 10 remarks (REM) are not allowed in SPEC 2000	The short text describes the object sufficiently	☐
42	632	ERP maximum field length for price is exceeded	The short text describes the object sufficiently	☐
43	633	Related field '&' is missing	The short text describes the object sufficiently	☐
44	634	Quantity discrepancy between business document and SPEC message	The short text describes the object sufficiently	☐
45	635	Price unit in PO & item & and SPEC message differ	The short text describes the object sufficiently	☐
46	636	Table 'SPCINMAP' is inconsistent ('&' and '&') are filled	The short text describes the object sufficiently	☐
47	701	Invalid command code	Space: object requires documentation	☐
48	702	Unavailable command code	Space: object requires documentation	☐
49	703	Improper use of slash	Space: object requires documentation	☐
50	704	Embedded TEI	Space: object requires documentation	☐
51	705	Unknown TEI &	Space: object requires documentation	☐
52	706	Invalid &	Space: object requires documentation	☐
53	707	Missing &	Space: object requires documentation	☐
54	708	Duplicate order number	Space: object requires documentation	☐
55	709	Non recorded order number	Space: object requires documentation	☐
56	710	Batch control reject &	Space: object requires documentation	☐
57	711	Unauthorized user	Space: object requires documentation	☐
58	712	Security violation	Space: object requires documentation	☐
59	713	Field too long &	Space: object requires documentation	☐
60	714	Expected continuation not received	Space: object requires documentation	☐
61	798	Invalid format	Space: object requires documentation	☐
62	799	& & & &	Space: object requires documentation	☐
63	800	Do not maintain orders with more than & &	The short text describes the object sufficiently	☐
64	801	Sales order exists for the Purchase Order &1 for the customer &2	The short text describes the object sufficiently	☐
65	802	Sales order was created without a reference S1BOOKED from the customer	The short text describes the object sufficiently	☐
66	803	Statistical item & in PO & cannot be referenced	Space: object requires documentation	☐
67	804	Changes via EDI are not supported for PO &	Space: object requires documentation	☐
68	805	No S1BOOKED order acknowledgement sent out (Reason: Group of Orders)	Space: object requires documentation	☐
69	806	No material change possible since there already exists subitems	The short text describes the object sufficiently	☐
70	807	Material change to PNR & without RPN is not SPEC 2000 compliant	The short text describes the object sufficiently	☐
71	808	No automatic changes to Purchase Order & item & possible	Space: object requires documentation	☐
72	809	Material & is not subitem of purchase order & item &	Space: object requires documentation	☐
73	810	Shipping notification & exists; change to purchase order & & not allowed	The short text describes the object sufficiently	☐
74	811	Goods receipt & exists; change to purchase order & & not allowed	The short text describes the object sufficiently	☐
75	812	Material & not present in the PO &	Space: object requires documentation	☐
76	813	Sales Order & does not contain any confirmed quantity	The short text describes the object sufficiently	☐
77	814	Unit '&' from the IDoc differs from unit '&' from Purchase Order '&'	Space: object requires documentation	☐
78	815	No price in inforecord '&' for material '&' and vendor '&'	Space: object requires documentation	☐
79	816	Purchasing document '&' item '&' cannot be identified	Space: object requires documentation	☐
80	817	MPN & cannot be identified for the part number in the inquiry	Space: object requires documentation	☐
81	818	Document currency '&' differs from condition currency '&'.	Space: object requires documentation	☐
82	819	Condition currency '&' differs from scales currency '&'.	Space: object requires documentation	☐
83	820	Invoice receipt & exists - change to purchase order & & not allowed	The short text describes the object sufficiently	☐
84	821	Invoice already exists for the parameters mentioned in the flat file	The short text describes the object sufficiently	☐
85	822	No SPEC2000 relevant Purchase Order changes were made	The short text describes the object sufficiently	☐
86	823	Material change not possible.IPN '&1' not same as partnumber '&2' in RFQ	Space: object requires documentation	☐
87	824	Shipping notification & exists - material change to PO & & not allowed	Space: object requires documentation	☐
88	825	Goods receipt & exists - material change to PO & & not allowed	Space: object requires documentation	☐

History

Last changed on/by	20110810	SAP
SAP Release Created in