BORRT - Nachrichten Regeltoure

The following messages are stored in message class BORRT: Nachrichten Regeltoure.
It is part of development package ISAUTO_BOR in software component IS-A-GR. This development package consists of objects that can be grouped under "Cargo manifest".
Message Nr
Message Text
001Schedule & already exists
002Schedule & and route & do not match
003Schedule & does not exist
004Reference route & does not correspond to route &
005Not possible to adopt a delivery date
006User &1 is currently editing schedule &2
007The begin of the validity period must be before the end
008System error: Lock object &1, key &2
009Enter a new validity
010Select a day
011Maintain a goods receipt time
012Fill in all required entry fields
013Maintain the day for goods receipt
014Maintain the new validity
015The change affects all selected validity periods
016Point in time already exists; change is not adopted
017Select a vendor
018Select a material
019There are no materials for vendor &
020Maintain the transport data
021Maintain route schedule determination conditions for vendor &
022Schedule & created
023Schedule & changed
024Select the materials that you want to copy
025Maintain the shipping condition
026Maintain the material
027Maintain the plant
028Select a material
029Select a validity period
030Point & for route & does not contain a reference
031Route &1 has no stages
032Route & has no conn. points with reference to the receiving point
033Receiving point & is not the end point of route &
034Schedule & deleted
035Shipment &2 already exists for schedule &1
036Shipment &2 for schedule &1 created
037Select a goods receipt time
038Condition &1 &2 &3 &4 is already available. Change not transferred.
039System error: Unlock objekt &
040Maintain a validity
041Delivery date and route adjusted to route schedule
042Delivery date differs to that of the route schedule
043Table BORRTFI could not be updated
044Table BORRTTSID could not be updated
045Table BORRTTS could not be updated
046Table BORRTTI could not be updated
047Table VALW could not be updated
048Table BORRTTSIDT could not be updated
049Internal date & is incorrect
050The Customizing data for route & could not be read
051Internal error occurred
052Error reading the route data for route &
053No unique key could be given to schedule &
054Node &1 of route &2 does not refer to a receiving point
055Route adapted in accordance with route schedule
056Maintain a date type
057Maintain a validity period from
058Date & period & is not valid
059Date type & is invalid
060Select an inbound shipment type
061No GR defined for several selected schedules at &
062Initializing shipment: Log from &1, &2
063Schedule &
064Route schedule in this variant is not initial
065Route schedule & in shipment does not match route schedule of the variant
066Route schedule &1 from variant not transferred but &2 from shipment
067Determination criteria could not be deleted from table BORRTFI
068Int. shipping notification &1 copied to shipment &2
069Table VALWT could not be updated
070Transaction VL51A is obsolete (see note 2227568)
071Transaction VL52A is obsolete (see note 2227568)
072Transaction VL53A is obsolete (see note 2227568)
073
Privacy Policy