JITOUT - Nachrichten zum JIT-Outbound
The following messages are stored in message class JITOUT: Nachrichten zum JIT-Outbound.
It is part of development package DI_JITOUT in software component IS-A-JIT. This development package consists of objects that can be grouped under "JIT Outbound".
It is part of development package DI_JITOUT in software component IS-A-JIT. This development package consists of objects that can be grouped under "JIT Outbound".
Message Nr ▲ | Message Text |
---|---|
000 | ********** MESSAGES FOR FUNCTIONGROUP JITOUT01 *********** |
001 | Error during internal number assignment |
002 | No JIT calls outbound have been found for the selection criteria |
003 | Select delivery confirmations for processing |
004 | &1 delivery confirmations have been completed |
005 | The delivery confirmations selected no longer exist |
006 | Select incomplete delivery confirmations only |
007 | Delivery confirmation &1 has already been sent |
008 | There are no delivery confirmations for selection |
009 | Action not executed because delivery confirmation has changed |
010 | Each vendor can only have one incomplete delivery confirmation |
011 | Select only one delivery confirmation per vendor |
012 | &1 Delivery Confirmations have been sent successfully |
013 | Time definition &1 has not been found |
014 | Complete all fields for the item data |
015 | Delivery confirmation &1 has been generated |
016 | No unique component group for production number &1 and supplier &2 |
017 | XML file &2 saved with &1 component groups |
018 | Action &1 is only inbound-relevant |
019 | JIT call does not match vendor &1 |
020 | Call does not match internal processing status &1 |
021 | More than one JIT call was found for external call number &1 |
022 | &1 alerts for error message &2 &3 by &4 |
023 | In total &1 alerts to &2 different errors to &3 components by &4 |
024 | Maitain storage location |
100 | ********** MESSAGES FOR FUNCTIONGROUP JITOUT03 *********** |
101 | Call (internal call number &1, vendor &3) is locked |
102 | System error while (un-)locking a call |
103 | Production supply area &1 in plant &2 has not been found |
104 | No source list entry found |
105 | Specify an outline agreement number in source list |
106 | There can be no more than 9999 call items in components group &1 |
107 | You do not have the authorization to execute this action |
108 | No source list entry exists for material &1 in plant &2 |
109 | Control cycle &1 is not a JIT control cycle |
110 | No call type could be determined for number &1 |
111 | There are still JIT Outbound Calls for Control Cycle &1 |
112 | Item &2 of scheduling agreement &1 is not suitable for JIT calls |
113 | No goods receipt can be posted for scheduling agreement item &1 &2 |
114 | No source list entry exists for scheduling agreement &1 &2 |
115 | Call &1 contains call items relating to different warehouse numbers |
116 | Production supply area &2 is not defined in plant &1 |
117 | Error when reading storage location control |
118 | Inconsistency in the plant data |
119 | Inconsistency in the storage location data |
120 | Link between JIT call and transfer order not saved |
121 | Inconsistency between JIT call and generated transfer order |
123 | Source list entry is not a scheduling agreement |
124 | Transfer order (warehouse &1, transfer order &2) locked |
125 | System error occurred during (un-)locking |
126 | Call &1 locked |
127 | System error occurred during (un-)locking |
128 | A transfer order has already been generated for JIT call &1 |
129 | The system was not able to create a delivery item for SumJC item &1 &2 |
130 | Scheduling agreement &1 item &2 is not valid |
149 | ***************** DPP-RELATED MESSAGES ******************************** |
150 | Vendor is locked; see long text |
300 | ********** MESSAGES FOR FUNCTIONGROUP JITOUT04 *********** |
301 | There are no JIT outbound calls among the selected calls |
302 | No message has been created for outbound call &1 to vendor &2 |
303 | Error during message generation |
304 | Call profile &1 not found |
305 | IDoc for components group &1 to vendor &2 has already been sent |
306 | Do not leave the internal status initial |
307 | Select all JIT calls for material document &1 |
308 | No call profile has been maintained for control cycle &1 |
309 | No output partner could be found for components group &1 |
310 | Goods receipt posting is not possible with differing call types |
311 | Message for component group &1 to supplier &2 already generated |
312 | Delivery can only be created for summarized JIT calls |
313 | Goods receipt can only be canceled for sequenced JIT call |
314 | Components group &1 missing for delivery confirmation &2 item &3 |
315 | No message was processed for components group &1 |
316 | No components were copied |
317 | To cancel the goods receipt, use transaction VL09 |
318 | No message could be sent to supplier &2 for call-off &1 |
319 | Message for Release &1. Message Class, Number, Type: &2, &3, &4 |
320 | Error in Control Cycle &1. Message Class, Number, Type: &2, &3, &4 |
321 | All components must have the same partner |
400 | *** Messages for JITOUT04 *** |
401 | Transfer data for executing action is not correct |
402 | No action has been executed |
403 | Selection limit has been reached |
404 | Unknown Entry in Customizing Table &1 |
405 | Status: &1 Calls, &2 Components Groups, &3 Components, Selection Limit &4 |
406 | Requirements time does not fall within associated time definition |
407 | Delivery &1 has not yet been processed completely |
408 | Correct the error before saving |
409 | Variance - item &1: Field '&2' has value '&3' instead of '&4' |
410 | Error in components group &1 |
411 | No goods receipt documents exist for the call |
412 | You have not selected a material document |
413 | Not all components groups can be deleted |
414 | Only life cycle status 'released' is allowed |
500 | ********** MESSAGES FOR FUNCTIONGROUP JITOUT06 *********** |
501 | Error while posting goods movements; Posting was not carried out |
502 | No IDOCs have yet been found for the selected calls |
503 | No data has been found for selected calls |
511 | No goods receipt has been booked yet by &3 &4 for requirement time &1 &2 |
512 | Unfortunately you cannot branch from here |
513 | Error reading the application log |
514 | Maintain the tolerance profile & |
515 | Error &1 &2 creating a delivery schedule for control cycle &3 by &4 |
516 | Qty tolerance breached for &1; release qty &2, deliv.qty &3; profile &4 |
517 | Alert for JIT Outbound Call &1 |
518 | Choose how you want to display or create alerts |
519 | Tolerance period breached for JIT call &1; JIT date &2, JIT time &3 |
520 | The tolerance profile & is still being used; deletion is not possible |
521 | JIT call &1 is set to: Quantity &2, delivery date &3, delivery time &4 |
522 | Choose at least one type of alert |
600 | ********** MESSAGES FOR FUNCTIONGROUP JITOUT07 *********** |
601 | Inconsistent data for components group &1 |
602 | No IDoc has been created for delivery confirmation &1 from vendor &2 |
603 | No data has been found for delivery confirmation |
604 | SAP unit of measure &1 cannot be converted into ISO display |
605 | No plant has been found for delivery confirmation &1 |
606 | Delivery confirmation &1 to vendor &2 has status 'sent' |
700 | ********** GENERAL MESSAGES FOR DI_JITOUT *********** |
701 | Internal program error |
702 | Incorrect call parameter, see BAPI documentation |
703 | No delivery confirmation according to the user�s selection criteria found |
704 | Delivery confirmation no is not archivable, because it is not completed |
705 | Parts of the requested data is blocked. They are not displayed. |
800 | ********** MESSAGES FOR FUNCTIONGROUP JITOUT09 *********** |
801 | Vendor & has an invalid source list entry |
802 | Goods receipt posting for summarized JIT call &1 is not possible |
803 | Different MRP supply areas and supplier scheduling agreement storage loc. |
804 | Part GR already posted. For additional GR postings use transaction PJWE |
805 | Summarized JIT Call & changed successfully |
806 | Replenishment strategy &1 does not exist in plant &3 |
807 | Change to delivery date is valid for the entire JIT call |
808 | Cancelation of goods receipt is not possible for summarized JIT call &1 |
809 | Available quantity from stock determination is too small |
810 | Available quantity from batch determination is too small |
811 | No JIT calls exist for this material document |
812 | GR posting for SumJC &1 &2 must be done with reference to a confirmation |
813 | The status of call &1 has already been updated |
814 | Material &1 in plant &2 is not assigned to a batch class |
815 | One message was processed manually |
816 | No item data or messages have been changed |
817 | The requirements time cannot lie in the past |
818 | To cancel the goods receipt use the automotive goods receipt transaction |
819 | An error occurred when copying the characteristic value assigment |
820 | Inconsistent data for JIT call &1 |
821 | Transfer order not (completely) confirmed |
822 | Not all transfer orders for call &1 have been confirmed |
823 | Transfer order &3 in warehouse number &2 was processed |
824 | No transfer order has been created yet for call &1 |
825 | Not all transfer orders for call &1 have been canceled |
826 | Transfer order &3 in warehouse number &2 not processed |
827 | Inconsistent WM data |
828 | Inconsistent JIT outbound data |
829 | Inconsistent WM data |
830 | There are no items to be confirmed/canceled |
831 | Select a line |
832 | No valuation exists for summarized JIT call item &1 |
833 | No summarized JIT call was found for delivery &1 &2 |
834 | Error when storing the data in the memory. SumJC: &1 &2 CUOBJ: &3 |
835 | Action &1 is not permitted for summarized JIT call &2 |
838 | Replenishment strategy type for control cycle for stock transfer changed |
840 | A shipping notification is needed for delivery schedule &1 &2 here |
842 | Delivery date/time could not be determined. Time stream error |
844 | External material field length should be less than 35 characters. |