V6 - Interface to External Transportation Systems

The following messages are stored in message class V6: Interface to External Transportation Systems.
It is part of development package VTRI in software component LE-TRA. This development package consists of objects that can be grouped under "Interfaces to external transport systems".
Message Nr
Message Text
000----- area 000 to 499 reserved for messages from transport. planng system
500----- Area 500 to 999 reserved for messages from SAP system -----
501Shipment & has been saved
502Incorrect output type: &, routine: &, sender: & &
503Wrong action code ACTCD = & in segment E1TPACC
504Transportation planning point & does not exist
505Partner & for transptn plan. pnt & and send partner & are different
506Transportation planning point & has no partner for transportatn. planning
507Shipment & is currently being processed
508No unit of measure has been entered in &; own value is entered
509Transport. planning point & is not assigned to any external planning sys.
510No ext. planning systems have been maintained for trans. planning points
511Transportation planning point & is not defined.
512Number of transferred deliveries &; Number of found deliveries &
513Shipment & has not been saved
514Shipment number is either missing or invalid (&)
515There are no entries in transportation planning point &.
516Delivery & does not exist.
517Delivery & is not reported in any external transportation planning system
518Delivery was deallocated from planning systems &.
519When choosing 'fixed points' you must enter one point
520Shipment & was deleted
521Unit of measure for weight/volume/length is missing in shipping unit &
522Net weight/volume is greater than gross weight/vol. in shipping element &
523Shipping material type is missing from shipping unit &
524Material number & in shipping unit & does not exist
525Shipping material type missing in material master & for shipping unit &
526Shipping material type & in shipping unit & does not exist
527Shipping unit (s) without identification
528Identification of shipping units is not clear
529The shipment contains shipping units, that are not empty.
530Shipping unit is not empty and could not therefore be deleted.
531The document could be posted.
532The document could not be posted.
533The same delivery was specified more than once
534Serialization check: Shipment & exceeded
535Location substitution procedure & is not defined
536Transportation connection point & is not defined
537No available entries
538Combination of activity codes & & is not provided for
539Not processed; shipment & is processed in IDoc &
540Processing IDoc not required
541IDoc category & is not defined for communication with logical system &
542Transportation planning point & does not exist
543Transportation planning point & is assigned to an external system
544Delivery & is not registered at any transportation service agent
545Initialization of HU processing for shipment & did not process correctly
546Handling unit & could not be created
547Error during deletion of HU &
548Handling unit & not deleted since content still exists
549Error during read of handling unit data
550Reference to one location is not identified uniquely
551For this point, a reference to a location is already defined
552For this point, neither an address nor a reference is defined
553A route number must be specified for the route
554You must specify a transportation connection point
555Transportation connection point & does not exist
556Deletion of last point in single-column view not possible
557No maintenance authorization for one or several transport.planning points
558Location definition incorrect
559Transportation planning points exist for external planning systems only
560No maintenance authorization f. one or more transportation service agents
561Enter a forwarding agent
562There is no assignment to a logical system for forwarding agent &
563Delivery was canceled for & transportation service agents
564The parameters for assigning internal shipment numbers are missing
565The parameters for identifying the shipment are missing
566No shipment exists for external ID1 & and forwarding agent &
567More than 1 shipment exists for external ID1 & and forwarding agent &
568A transportation service agent has not been specified
569There is no status data for the selection criteria chosen
570No forwarding agent has been assigned for send partner & &
571Shipment & has been saved
572Status for rejected deliveries has not been set correctly
573Status for rejected deliveries has been set correctly
600Leg indicator & for shipment & does not require date determination
601Shipment & does not contain any deliveries
602Takeover of dates from a transportation chain was successful
603No takeover of dates from a transportation chain executed
604Shipment start taken from shipment & and delivery &
605Shipment end taken from shipment & and delivery &
606Shipment start not copied because date was already set
607Shipment end was not copied because date was already set
608Dates from transportation chain not copied completely
609No suitable date found for shipment start in transportation chain
610No suitable date found for shipment end in transportation chain
800IDoc & could not be created.
801Delivery & transferred to IDOC & as No. &
802ISO conversion incorrect: Del. no. &, location & &, country &
803ISO conversion incorrect: Dlv. no. &, dlve. item &, unit &
804ISO conversion incorrect: Del. no. &, packing element &, unit &
805ISO conversion incorrect: Del. no. &, pack. element &, item no. &, unit &
806ISO conversion incorrect: Location & &, country &
807& location descriptions sent to the transportation planning system
808No selection group activated
809Overflow with dlv.qty in ship.unit: Dlv.no. &1, ship.un.no. &2, unit &3
810Combinations of actions (e.g. Create + Delete) are not allowed per HU
811Changes to handling units in shipment & were not successful
812Creation of handling units was not successful
813Deletion of handling units in shipment & was not successful
814HU & successfully created
815Error: Could not create HU &
816Changes to HU & were not successful
817HU & successfully deleted
Privacy Policy