SPC02 - Messages for 2nd phase of SPEC2000
The following messages are stored in message class SPC02: Messages for 2nd phase of SPEC2000.
It is part of development package AD_SPC_PH2_GEN in software component IS-AD-SPC. This development package consists of objects that can be grouped under "All central objects for 2nd phase of SPEC2000".
It is part of development package AD_SPC_PH2_GEN in software component IS-AD-SPC. This development package consists of objects that can be grouped under "All central objects for 2nd phase of SPEC2000".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Message &1 with code &2 and function &3 not defined in table SPCPORTFUN |
| 002 | Function module &1 does not exist |
| 003 | Partner profile for the message &1 is not set with EDISTD as 'A' |
| 004 | Minimun/maximum length violation in field '&' in segment number '&' |
| 005 | Initial Inbound S1BOOKED idoc '&1' cannot be opened for Sales Order '&2'. |
| 401 | Material & couldn't be assigned to FFF class & |
| 550 | No SPEC2K IDocs were found based on your selection criteria |
| 551 | Only one discount percent (DIS or PDP) should be present |
| 552 | No IDOCs to display |
| 553 | Select one IDOC to display |
| 600 | File '&' could not be opened for output |
| 601 | Mandatory field check failed for field '&' in segment number '&' |
| 602 | SPEC2K IDoc and SPEC2K flatfile structure are not consistent |
| 603 | Related fields not maintained for field '&' in segment number '&' |
| 604 | Type violation in field '&' in segment number '&' or max length violation |
| 605 | Decimal places violation in field '&' in segment number '&' |
| 606 | Minimun/maximum length violation in field '&' in segment number '&' |
| 607 | Tables 'SPCFILE' and 'SPCDTEL' are not consistent |
| 608 | No entries in table SPCFILE for key MESTYP '&', MESFCT '&' and MESCOD '&' |
| 609 | Unable to identify message function |
| 610 | Field '&' should not occur in message type '&' with message function '&' |
| 611 | Structure of inbound SPEC2K flatfile is not valid |
| 612 | Underlying basic type not found for message type '&' in table 'EDIMSG' |
| 613 | Receiver/sender address information missing in SPEC message header |
| 614 | Partner profile not maintained in table 'SPCPRTNRINF' for rcvr &, sndr & |
| 615 | Rcvr/sndr not maintained in table 'SPCPRTNRINF' for given partner profile |
| 616 | No entries found in table 'IDOCSYN' for IDOCTYP '&' |
| 617 | Command acknowledgment received successfully |
| 618 | Too late acknowledgement of the command |
| 619 | Source IDoc could not be located |
| 620 | Maximum length violation in field '&' |
| 621 | Either the first or the last character of field '&' is a '-' |
| 622 | '-' does not occur between two numerals in field '&' |
| 623 | SPEC2K IDoc could not be opened for edit |
| 624 | SPEC2K IDoc could not be changed |
| 625 | SPEC2K IDoc could not be closed for edit |
| 626 | Data set group '&' is not maintained properly |
| 627 | INA or PAY check failed; inconsistent S1NVOICE message |
| 628 | POC or QTL check failed; inconsistent S1ORDEXC message |
| 629 | S1NVOICE acknowledgement could not be sent out; internal error |
| 630 | S1ORDEXC acknowledgement could not be sent out; internal error |
| 631 | More than 10 remarks (REM) are not allowed in SPEC 2000 |
| 632 | ERP maximum field length for price is exceeded |
| 633 | Related field '&' is missing |
| 634 | Quantity discrepancy between business document and SPEC message |
| 635 | Price unit in PO & item & and SPEC message differ |
| 636 | Table 'SPCINMAP' is inconsistent ('&' and '&') are filled |
| 701 | Invalid command code |
| 702 | Unavailable command code |
| 703 | Improper use of slash |
| 704 | Embedded TEI |
| 705 | Unknown TEI & |
| 706 | Invalid & |
| 707 | Missing & |
| 708 | Duplicate order number |
| 709 | Non recorded order number |
| 710 | Batch control reject & |
| 711 | Unauthorized user |
| 712 | Security violation |
| 713 | Field too long & |
| 714 | Expected continuation not received |
| 798 | Invalid format |
| 799 | & & & & |
| 800 | Do not maintain orders with more than & & |
| 801 | Sales order exists for the Purchase Order &1 for the customer &2 |
| 802 | Sales order was created without a reference S1BOOKED from the customer |
| 803 | Statistical item & in PO & cannot be referenced |
| 804 | Changes via EDI are not supported for PO & |
| 805 | No S1BOOKED order acknowledgement sent out (Reason: Group of Orders) |
| 806 | No material change possible since there already exists subitems |
| 807 | Material change to PNR & without RPN is not SPEC 2000 compliant |
| 808 | No automatic changes to Purchase Order & item & possible |
| 809 | Material & is not subitem of purchase order & item & |
| 810 | Shipping notification & exists; change to purchase order & & not allowed |
| 811 | Goods receipt & exists; change to purchase order & & not allowed |
| 812 | Material & not present in the PO & |
| 813 | Sales Order & does not contain any confirmed quantity |
| 814 | Unit '&' from the IDoc differs from unit '&' from Purchase Order '&' |
| 815 | No price in inforecord '&' for material '&' and vendor '&' |
| 816 | Purchasing document '&' item '&' cannot be identified |
| 817 | MPN & cannot be identified for the part number in the inquiry |
| 818 | Document currency '&' differs from condition currency '&'. |
| 819 | Condition currency '&' differs from scales currency '&'. |
| 820 | Invoice receipt & exists - change to purchase order & & not allowed |
| 821 | Invoice already exists for the parameters mentioned in the flat file |
| 822 | No SPEC2000 relevant Purchase Order changes were made |
| 823 | Material change not possible.IPN '&1' not same as partnumber '&2' in RFQ |
| 824 | Shipping notification & exists - material change to PO & & not allowed |
| 825 | Goods receipt & exists - material change to PO & & not allowed |
| 826 | Purchase Order &1 from vendor &3 does not exist (S1BOOKBK) |
| 827 | INV too long. |