EDI_SD - Messages for EDI SD Integration

The following messages are stored in message class EDI_SD: Messages for EDI SD Integration.
 It is part of development package LOG_EDI_SD_REUSE in software component SD-SLS-EDI. This development package consists of objects that can be grouped under "EDI-Integration: SD specific Reuse Coding".
Message Nr ▲
Message Text
000***********************Order Processing Messages*************************
001Sales area cannot be determined
002Item category cannot be determined
003Business partner for role &1 cannot be determined
004No valid &1 party can be determined
005&1 must be provided in the source data
006Sales document type cannot be determined
007Internal GUID generation failure
008&1 &2 cannot be converted to SAP internal format
009Party type &1 is not supported
010The Source Party internal ID must be provided in the source data
011Pricing schema cannot be determined
012Pricing procedure cannot be determined
013Business partner cannot be uniquely determined by GLN &1
014Price conditions for customer expected price cannot be determined
015Internal unit of measure cannot be determined by ISO unit &1
016A more recent version of this EDI message has already been processed
017Sales order &1 cannot be found in the system
018Standard ID of the sender partner is not defined uniquely
019Purchase order &2 of customer &1 is referenced by multiple sales orders
020Purchase order &2 of customer &1 is currently being processed
021Local currency of purchase organization &1 cannot be determined
022Sales document items cannot contain Sold-To-Party information
023Schedule line requested delivery date must be provided in the source data
024Sales order processing failed
025&1 is not processed in the standard application logic
026Technical mapping failed
027External text ID &1 of object &2 is not assigned to an internal text ID
028The salutation text &1 is not supported.
029The text procedure cannot be determined
030The text ID for the received text type &1 cannot be determined
031The XML text type you have given is not supported!
032Order item &1 in the request can only have one reference document
033A single reference order could not be determined
034Order items in the request must have the same reference document
035Determined reference document &1 cannot be used for returns
036Reference document item cannot be determined
037Material discrepancy with determined reference document &1
038Order item &1 in the request is missing a reference document
039Attachment creation failed during update of sales order &1.
040Attachment deletion failed during update of sales order &1.
041Attachment creation failed during creation of sales order &1.
042The terms of payment key cannot be determined.
043The system cannot use term of payment key &1 due to discrepancies.
044The terms of payment key was not found in the system.
045The system used the terms of payment key in the customer master record.
046The system used terms of payment key &1 despite of discrepancies.
047Multiple terms of payment keys exist with the same details
048Terms of payment key cannot be determined
049Invalid address indicator.
050Variant config. for item &1 won't be updated. Changes are not supported.
051Variant config. for item &1 not support.
052Item &1 has already been rejected. Further changes are not possible.
054Address ID &1 is invalid for partner &2 with partner function &3.
055Address ID not editable for partner function &1
056Address ID is mandatory for partner function &1.
059Address ID &1 is invalid for external customer &2.
100Business system ID &1 not mntnd with type 'ARIBA' in config step 102450.
200********************Confirmation Processing Messages*********************
201An error occurred when mapping from SAP to XML format for field &1&2&3&4
202Data for sales order &1 could not be determined
400*********************Invoice Processing Messages*************************
401Data for billing document &1 could not be determined
403Pricing error in the billing document &1
404Raw structure and proxy structure do not match
405Payment Terms data could not be retrieved
406Header Tax data could not be retrieved
407Item Tax data could not be retrieved
408Amount conversion error
409Buyer Party ID is not found
410Supplier Party ID &1 is not found
411Global Location Number is not found
412Sales Organization Address is not found
413Company Code Address is not found
414Text could not be read
415Text does not exist
416Purchase Order reference is not found
417Delivery reference is not found
418
600***********************REUSE Processing Messages*************************
601An unexpected exception has been triggered by the application
602Unexpected input structure provided
800****************Scheduling Agreement Processing Messages*****************
801Invalid realease type &1. It must be 1 or 2.
802Multiple sales scheduling agreements found for sold-to party &1.
803No sales scheduling agreement found.
804The old delivery schedule &1 is not identical with delivery schedule &2.
805In delivery schedule &1, delivery schedule key must be 1, 2, or blank.
806No schedule line to be copied from the old JIT delivery schedule.
807Order quantities in schedule lines have been added.
808Order quantities in schedule lines have been deducted.
809Invalid date type &1. It must be D, W, or M.
810No forecast delivery schedule in sales scheduling agreement &1.
811No sales scheduling agreement found according to custom logic.
812The sales scheduling agreement found according to custom logic is invalid
813The determined sales scheduling agreement &1 does not exist.
814The determined sales scheduling agreement &1 item &2 does not exist.
820Customer reference &2 of customer &1 is currently being processed.
824Sales scheduling agreement processing failed.
825&1 must be provided in the source data.
826Customer reference &2 in &3 does not match purchase order number &1.
827Sales scheduling agreement &1 is found.
830Sales scheduling agreement &1 item &2 not found.
832SalesItemProposalDescription does not match in scheduling agreement &1.
833Sales area not found for customer &1.
834Delivery schedule processing option not found for sold-to party &1.
835Unloading point &1 does not match in sales scheduling agreement &2.
836Sold-to party assignment not found for supplier &1.
837JIT delivery schedule is not supported in sales scheduling agreement &1.
838The planned cumulative quanity is ignored.
839The planned cumulative quanity date is ignored.
840Material usage indicator &1 not matched in sales scheduling agreement &2.
841Zero or multiple items received.
842Sales scheduling agreement &1 not used. Supplier number not suitable.
843Zero or multiple delivery schedules received.
844Enter S, W, I, or E for the message type.
850No entry or no sales doc. type maintained for sold-to party &1 in T664A.
880****************Scheduling Agreement Fiori App Messages*****************
881Enter a valid sold-to party.
882This processing option already exists.
883You are not authorized to create records for sold-to party &1.
884Enter a valid supplier, partner description, or unloading point.
885This sold-to party assignment already exists.
886Sold-to party &1 is blocked.
887Sold-to party &1 is blocked.
888Enter a valid instruction for the planning delivery schedule.
889Cannot delete the selected instructions of &1.
890
891Cannot delete the selected splitting rules.
892You must assign parameter PARTNER_FUNCTION to this formula.
Privacy Policy