WRF_AT - Messages for Allocation Table RTFASH
The following messages are stored in message class WRF_AT: Messages for Allocation Table RTFASH.
It is part of development package WRF_AT_DDIC in software component LO-RFM-PUR-AL. This development package consists of objects that can be grouped under "RTFASH: Dictionary Objects for Allocation Table Enhancements".
It is part of development package WRF_AT_DDIC in software component LO-RFM-PUR-AL. This development package consists of objects that can be grouped under "RTFASH: Dictionary Objects for Allocation Table Enhancements".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Enter an allocation table or at least one header criterion |
| 002 | You are not authorized to execute transaction & |
| 003 | No node determined for article hierarchy &1, level &2 |
| 004 | Enter at least an activity status |
| 005 | Allocation table type &1 does not exist |
| 006 | Material group &1 does not exist |
| 007 | Supplier &1 does not exist |
| 008 | Enter a hierarchy ID |
| 009 | Selection conflict; system will ignore recipient restrictions |
| 010 | No detail data found |
| 011 | Position the cursor in a valid line or select a line |
| 014 | Enter at least a maintenance status |
| 020 | There is no allocation instruction for allocation table &1 |
| 050 | Select an item |
| 060 | In the SLS case, single changes to the delivery date are not synchronized |
| 098 | No changes to allocation tables received for updating |
| 099 | System error: Table GT_PLAUSI_ERROR is not empty; no update |
| 104 | Alloc. table &1, item &2; order-optimized qty not equal to reduced PO qty |
| 105 | Planned qty of the alloc. table item was to be < 0; it will be set to 0 |
| 106 | Planned qty of distribution center was to be < 0; it will be set to zero |
| 107 | Order-optimized quantity of DC was to be < 0; it will be set to 0 |
| 108 | Quantity of a DC delivery phase was to be < 0; it will be set to 0 |
| 109 | Allocation table &1 no longer exists; no synchronization is required |
| 110 | Cannot read allocation table &1 |
| 111 | Relationship between alloc. table (&1, item &2) and PO is not unique |
| 112 | Allocation table &1 from prepack alloc. plan. cannot be synchronized |
| 113 | Error allocating overall quantity to single quantities per plant |
| 114 | Follow-on docs already exist for recipients for alloc. table &1, item &2 |
| 115 | Allocation table &1 is blocked by user &2 |
| 116 | Bundeling of multiple alloc. table items for synchronization not allowed |
| 117 | Order unit is different from stock transfer unit |
| 118 | System error; allocation-table-relevant indicator set to "Not Relevant" |
| 119 | Following exceptions during incompleteness check of alloc.tab. &1,itm &2: |
| 120 | --- Messages for customer BAdI for allocation table &1, item &2: |
| 121 | Allocation table &1 was deleted |
| 123 | Order &1 contains changes that will not be synchronized |
| 124 | System error while accessing already read allocation table data |
| 125 | Inconsistent data in purchase order &1, item &2 |
| 126 | Distribution center &4 is not valid for action &3 (allocation table &2) |
| 127 | Error checking action &4 (allocation table &2, item &3) |
| 128 | Simultaneous change of DC and UoM not possible (PO &1, item &2) |
| 129 | New distribution center &3 is not valid (alloc. table &1, item &2) |
| 130 | No entry for DC &3 nd in plant master data (alloc. table &1, item &2) |
| 131 | System error determining the new DC &3 (alloc. table &2, item &1) |
| 132 | Processing method &1 is not allowed for DC &2 (material &3) |
| 133 | Processing method &1 cannot be checked (material &2) |
| 134 | Inconsistent data (routine: &3); processing method &1 for DC &2 |
| 135 | The relevant distribution data is being processed by another user |
| 136 | Could not block the relevant distribution data (system error) |
| 137 | Could not block the relevant distribution data; other error |
| 138 | Processing method alloc. table relevance "&1" is not allowed for DC &2 |
| 139 | AUREL change not permitted, because PO split for alloc. table item (FBG) |
| 140 | Synchronization not possible; enter permitted value f. deletion indicator |
| 142 | Change of DC to &1 not allowed (DC is already assigned to another item) |
| 143 | No synchronization; allocation table &1, item &2 not relevant for dist. |
| 144 | System error while changing DC &3 (alloc. table &1,item &2) |
| 145 | Synchronization is not possible when purchase order UoMs differ |
| 146 | Synchronization is not possible when purchase order UoMs differ |
| 147 | Inconsistent data (routine: &1) when changing AT relevancy indicator |
| 148 | Change of DC to &3 not possible in allocation table &1, item &2 |
| 149 | System error: No supply source assigned to recipients (AT &1, &2) |
| 150 | System error while updating distribution data (delete data record) |
| 151 | System error while updating distribution data (alloc. table item data) |
| 152 | System error while updating the distribution data (alloc. table DC data) |
| 153 | System error while updating distribution data (UoM conversion) |
| 154 | System error when updating the distribution data (Change Alloc. Table) |
| 155 | System error when updating the distribution data (Delete alloc. table) |
| 158 | Synchronization with allocation table &1, item &2 is not possible |
| 159 | The recipient referenced in purchase order &3, item &4 no longer exists |
| 160 | There is no valid message type in Customizing for message WRF_AT 104 |
| 161 | Error while reading the Cusomizing table T160AT |
| 164 | New DC delivery date not synchronized with allocation table &1, item &2 |
| 165 | Synchronization terminated, allocation table &1 was not changed |
| 199 | System error; plausibility errors still exist before alloc. table posting |
| 200 | Select an item in the Allocation Instruction list |
| 201 | Goods receipt date is not valid. Check this in the site delivery phase |
| 899 | Quantities are too large (quantity field overflow) |