SAP ABAP Message Class V4 (Sales messages (variable messages and EDI messages))
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷
VA (Package) Application development R/3 Sales
⤷
⤷
Attributes
| Message class | V4 | |
| Short Description | Sales messages (variable messages and EDI messages) | |
| Changed On | 20131127 | |
| Last Changed At | 174354 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | No scheduling agreement could be determined | |||
| 2 | The delivery entered does not exist in the document flow | |||
| 3 | The delivery date entered does not correspond to the document date | |||
| 4 | The production go-ahead start time lies after the prod.go-ahead end time | |||
| 5 | The material go-ahead start time lies after the mat.go-ahead end time | |||
| 6 | The production go-ahead period is longer than the mat.go-ahead period | Space: object requires documentation | ||
| 7 | The beginning of the val.period of the dlv.sched.lies after its end | |||
| 8 | The cust.mat.no.in the sched.agreement differs from the one selected | |||
| 9 | The customer no. in the sched.agreement differs from the one selected | |||
| 10 | The customer plant in the sched. agreement differs from the one selected | Space: object requires documentation | ||
| 11 | The unloading point in the sched.agreement differs form the one selected | |||
| 12 | The usage indicator in the sched.agreement differs from the one selected | |||
| 13 | The PO numbers in the sched. agreement differ from the ones selected | Space: object requires documentation | ||
| 14 | No description was assigned to the usage indicator & | |||
| 15 | The current cml.delivered quantity is smaller than the cml.received qty | |||
| 16 | Save your changes first | |||
| 17 | No deliveries could be determined | |||
| 18 | The cml.received quantity does not correspond with specified delivery | |||
| 19 | The cumulative received quantity was reduced without a change of year | |||
| 20 | The scheduling agreement does not exist | |||
| 21 | The scheduling agreement item does not exist | |||
| 22 | The cml.received qty does not correspond with the specified withdrawal | |||
| 23 | For this function, two delivery schedules must be selected | |||
| 24 | Select only one SA release for this function | |||
| 25 | Select one to five SA releases for this function | |||
| 26 | Invalid function for selection | |||
| 27 | No schedule lines exist for this SA release | |||
| 28 | Usage & is not defined | |||
| 29 | The delivery quantity specified does not correspond with the delivery | |||
| 30 | Scheduling agreement &1 for IDoc &2 has been processed | Space: object requires documentation | ||
| 31 | The customer for this scheduling agreement does not exist | |||
| 32 | No record exists in T661W for vendor &1, plant &2, unloading point &3 | Space: object requires documentation | ||
| 33 | No special rule exists in T663A for sold-to party & | |||
| 34 | No scheduling agreement could be found | |||
| 35 | No unique scheduling agreement could be determined | |||
| 36 | No old schedule lines existed to be copied | |||
| 37 | In table T663A the ID for first run was set for sold-to party & | |||
| 38 | Unknown delivery number. Check the proposal for the inbound progr. count | Space: object requires documentation | ||
| 39 | Partner number & is unknown | |||
| 40 | The material go-ahead was reduced | |||
| 41 | The production go-ahead was reduced | |||
| 42 | The delivery go-ahead was reduced | |||
| 43 | Customer material &1 does not exist in scheduling agreement &2 | Space: object requires documentation | ||
| 44 | IDoc no. &1 was not processed up to the final save | Space: object requires documentation | ||
| 45 | Scheduling agreement &1 found during planning was manually set to &2 | Space: object requires documentation | ||
| 46 | In table T663A the dlv.schedule test run ID was set for customer & | |||
| 47 | In table T663A the JIT test run ID was set for customer & | |||
| 48 | SA release ID & in the IDoc cannot be processed | |||
| 49 | Forecast delivery schedule key & in the IDoc cannot be processed | |||
| 50 | An invalid date exists in IDoc & | |||
| 51 | An invalid period ID was transferred | |||
| 52 | An invalid week was determined during IDOC processing | |||
| 53 | Scheduling agreement &1 &2 with a reason for rejection was found | Space: object requires documentation | ||
| 54 | No text could be inserted in IDoc &1 and scheduling agreement &2 | Space: object requires documentation | ||
| 55 | No text could be saved for IDoc &1 and scheduling agreement &2 | Space: object requires documentation | ||
| 56 | Release no. &2 has already been allowed for in scheduling agreement &1 | Space: object requires documentation | ||
| 57 | IDoc &2 was already planned in scheduling agreement &1 | Space: object requires documentation | ||
| 58 | The old dlv. sched no. &1 in IDoc &2 <> than current delivery sched.no.&3 | Space: object requires documentation | ||
| 59 | An error occurred during CALL TRANSACTION processing | |||
| 60 | IDoc & could not be opened | |||
| 61 | Mandatory segment & does not exist in the IDoc | |||
| 62 | The IDoc segment sequence is incorrect | |||
| 63 | IDoc number is not known | |||
| 64 | Error &1 = &2 has been transmitted by the translator | Space: object requires documentation | ||
| 65 | The scheduling agreement determined & has no special stock ID | |||
| 66 | The delivery entered is not an external agent withdrawal | |||
| 67 | Generated ESA consignment issue & is incomplete (see incompletion log) | Space: object requires documentation | ||
| 68 | Ext. service agt consignment issue &1 for IDoc &2 has been processed | Space: object requires documentation | ||
| 69 | No external agent delivery was entered as a starting point | |||
| 70 | Error reading internal table: Contact programmers | |||
| 71 | Check item &, quantity change exceeds the change tolerance | |||
| 72 | Dlv.sched. &1 deviates from dlv.sched. &2 on &3 in the timeframe by &4 % | Space: object requires documentation | ||
| 73 | Scheduling agrmt &1, material, customer &2, sold-to party &3, plant &4 | Space: object requires documentation | ||
| 74 | Unloading point &1, usage ID &2, sales org. &3, distribution channel &4 | Space: object requires documentation | ||
| 75 | Division &1, order type &2, completion number &3 | Space: object requires documentation | ||
| 76 | Vendor number &2 has not been saved for customer &1 | Space: object requires documentation | ||
| 77 | More than one item exists in IDoc & | |||
| 78 | Index VLPKM: found sched.agreement no. & does not exist (VBAK) | Space: object requires documentation | ||
| 79 | Packing material no. changed from &1 in the old IDoc to &2 | Space: object requires documentation | ||
| 80 | The previous IDoc for the packing material check could not be closed | |||
| 81 | Consider delivery unit &2 &3 in item &1 | Space: object requires documentation | ||
| 82 | Take minimum order quantity &1 &2 into account in item &3 | Space: object requires documentation | ||
| 83 | Item &1: Order quantity smaller than delivery quantity: &2 &3 | Space: object requires documentation | ||
| 84 | Eng.change statuses are either dep. on cml.qties and fiscal year or date | |||
| 85 | Header text for scheduling agreement & has been copied from IDoc | |||
| 86 | Item text for scheduling agreement & has been copied from the IDoc | |||
| 87 | For sold-to party & there is no special rule for ext.agt proc. in T664A | |||
| 88 | Packing materials have been sent using an ext.agent delivery | |||
| 89 | The first run ID has been set for sold-to party & in T664A | |||
| 90 | There is a header text for sales order & in the IDoc | |||
| 91 | There is an item text for sales order & in the IDoc | |||
| 92 | The withdrawal quantity specified does not match the withdrawals | |||
| 93 | Text ID &1 in IDoc &2 is not allowed for order type &3 | Space: object requires documentation | ||
| 94 | The delivery schedule type &1 in IDoc &2 is not allowed | Space: object requires documentation | ||
| 95 | The delivery schedule date lies in the future | |||
| 96 | Delivery of &2 &3 has already been made for item &1 | Space: object requires documentation | ||
| 97 | Delivery number &1 replaced by internal number &2 | Space: object requires documentation | ||
| 98 | Special rule for self-billing doc. missing for sold-to party & in T665A | |||
| 99 | Delivery note no. from the credit advice is missing in the document flow | Space: object requires documentation | ||
| 100 | Several deliveries with external document numbers have been found | Space: object requires documentation | ||
| 101 | Quantity &1 in the credit advice does not equal &2 in the delivery | Space: object requires documentation | ||
| 102 | Customer material &2 is not available in delivery &1 | Space: object requires documentation | ||
| 103 | There is no billing document for item &2 in the delivery note | Space: object requires documentation | ||
| 104 | Clearing values <> credit advice for item &2 in the delivery note | Space: object requires documentation | ||
| 105 | The amounts for item &2 in the delivery note are not the same | Space: object requires documentation | ||
| 106 | Self-billing doc. &1 could not be copied to open items in bill. doc. &2 | Space: object requires documentation | ||
| 107 | There are more items in delivery &1 than in the credit advice | Space: object requires documentation | ||
| 108 | Surcharge value for the delivery is &1, &2 in the self-billing document | Space: object requires documentation | ||
| 109 | Cash discount amount for the delivery is &1, &2 in the self-billing doc. | Space: object requires documentation | ||
| 110 | Total value for the delivery is &1, &2 in the self-billing document | Space: object requires documentation | ||
| 111 | VAT amount for the delivery is &1, &2 in the self-billing document | Space: object requires documentation | ||
| 112 | Credit/debit memo &1 for billing document &2 has been updated | Space: object requires documentation | ||
| 113 | TVCPA-POSVO is not maintained for document type &1 and billing type &2 | Space: object requires documentation | ||
| 114 | Credit/debit memo & has not been completely updated | |||
| 115 | Purchase order number in document number: & already exists | |||
| 116 | Delivery scedule &1 &2 & 3missing for table YVBLB | Space: object requires documentation | ||
| 117 | Sched. agreement item &1 &2 does not have a forecast delivery schedule | Space: object requires documentation | ||
| 118 | Goods issue has not yet been posted for selected delivery & | |||
| 119 | Deliveries due for posting to goods issue still exist for sched. agrmnt & | |||
| 120 | There is no IDOC for this & | |||
| 121 | An invalid weekday was determined in processing IDOC & | |||
| 122 | An eng. change status with the same deadline/cum. qty. already exists | |||
| 123 | Select the required engineering change status | |||
| 124 | Engineering change status &1 &2 is missing in table YVBSN | Space: object requires documentation | ||
| 125 | There is no engineering change status for item & | Space: object requires documentation | ||
| 126 | There can only be one valid engineering change status per delivery date | |||
| 127 | There can only be one valid engineering change status per cml. dlv. qty. | |||
| 128 | Enter the serial number | |||
| 129 | No JIT del. sched. exists for this item | |||
| 130 | No del. sched. exists for this item | |||
| 131 | Requested dlv. date cannot be met for sched. line(s) &2 &3 in item &1 | Space: object requires documentation | ||
| 132 | There is no active JIT schedule line for the item | Space: object requires documentation | ||
| 133 | Quantity comparison: Error in date determination | |||
| 134 | Caution: SD document & is blocked due to credit checks | Space: object requires documentation | ||
| 135 | Sum of invoice value differs from item value. Confirm | Space: object requires documentation | ||
| 136 | Sum of percentages does not add up to 100%. Confirm | Space: object requires documentation | ||
| 137 | You have not maintained material &1 in proposed plant &2 | Space: object requires documentation | ||
| 138 | There is already a scheduling agreement with this same data | |||
| 139 | Transferring old schedule lines is not possible | |||
| 140 | For reasons of cost management, item & cannot be deleted | |||
| 141 | The figures set to 0 date does not fit customer's fiscal/previous year | |||
| 142 | Reference document &1, &2 has batch &3. | Space: object requires documentation | ||
| 143 | &1: Figures set to 0 date (&2) is not current and will be ignored | Space: object requires documentation | ||
| 144 | Validity period and periods can only be entered together | |||
| 145 | Prodtn go-ahead validity period is larger than matl go-ahead validity pd | |||
| 146 | Pickup window is in past - please check | Space: object requires documentation | ||
| 147 | Cumulative quantity received by customer does not match delivery order | Space: object requires documentation | ||
| 148 | Current order cumul. qty is smaller than cumul. qty received by customer | Space: object requires documentation | ||
| 149 | The specified delivery quantity does not match delivery order | Space: object requires documentation | ||
| 150 | The delivery order is not available in the document flow | Space: object requires documentation | ||
| 151 | A new planning del. sched. has been automatically generated for item & | Space: object requires documentation | ||
| 152 | Item &: Customer plant in scheduling agreement differs from that selected | Space: object requires documentation | ||
| 153 | Item & does not contain any planning delivery schedule instructions | Space: object requires documentation | ||
| 154 | Item &:Unloading point in scheduling agreement differs from that selected | Space: object requires documentation | ||
| 155 | An exchange rate of &3 is defined for conversion from &1 to &2 | Space: object requires documentation | ||
| 156 | Sch.lines in plang dely sched. are still available (pl.del.sched.instr&) | Space: object requires documentation | ||
| 157 | Planning delivery schedule instruction & is not defined | Space: object requires documentation | ||
| 158 | Check use of planning delivery schedule instruction & | Space: object requires documentation | ||
| 159 | Split rule &1 is assigned to planning delivery schedule instruction (&2) | Space: object requires documentation | ||
| 160 | Minimum quantity & & of free goods has not been reached | Space: object requires documentation | ||
| 161 | A delivery order could not be determined | Space: object requires documentation | ||
| 162 | The billing document was not created correctly for external document &1 | Space: object requires documentation | ||
| 163 | Error on calling up billing document interface | Space: object requires documentation | ||
| 164 | Invalid paramter (field: &2, content: &3) | Space: object requires documentation | ||
| 165 | Different sales organizations have been billed | Space: object requires documentation | ||
| 166 | The billing document for external document &1 has not been created | Space: object requires documentation | ||
| 167 | Customer material &1: Billed quantity does not correspond to open qty | Space: object requires documentation | ||
| 168 | The pickup date should only be changed in agreement with the customer | Space: object requires documentation | ||
| 169 | Customer material &1: The system did not find the transferred delivery | Space: object requires documentation | ||
| 170 | The transmitted currency &1 is invalid | Space: object requires documentation | ||
| 171 | &2 billing documents were created for external document &1 | Space: object requires documentation | ||
| 172 | Customer material &1: The billed item does not exist | Space: object requires documentation | ||
| 173 | Customer material &1: The system could not determine a material | Space: object requires documentation | ||
| 174 | Customer material &1: The sales unit is different | Space: object requires documentation | ||
| 175 | &2 billing document was created for external document &1 | Space: object requires documentation | ||
| 176 | Entry &1 in table T665A is not maintained for sales promotion &2 | Space: object requires documentation | ||
| 177 | There are deviating conditions: Internal &1 &2, external &3 &4 | Space: object requires documentation | ||
| 178 | Transmitted language &1 is invalid | Space: object requires documentation | ||
| 179 | The system could not determine the collective processing number | Space: object requires documentation | ||
| 180 | Customer material &1: The value-added tax code is different | Space: object requires documentation | ||
| 181 | Customer material &1: The transmitted billing document cannot be used | Space: object requires documentation | ||
| 182 | Item &: The pick-up date is not a work day in the shipping point calendar | Space: object requires documentation | ||
| 183 | External document &1 is already being used | Space: object requires documentation | ||
| 184 | Customer material &1: The transmitted order is invalid | Space: object requires documentation | ||
| 185 | Customer material &1: The order has a different currency | Space: object requires documentation | ||
| 186 | A billing document could not be created for external document &1 | Space: object requires documentation | ||
| 187 | No valid delivery date in schedule line - distribution function | Space: object requires documentation | ||
| 188 | There is no delivery date in the week | Space: object requires documentation | ||
| 189 | An exception has been triggered in user exit & | Space: object requires documentation | ||
| 190 | The transmitted unit of measure &1 is invalid | Space: object requires documentation | ||
| 191 | The system cannot create a billing document without a value | Space: object requires documentation | ||
| 192 | Item &: Requested quantity is greater than sched. agreement requirements | Space: object requires documentation | ||
| 193 | There is more than one reference for creating a delivery | Space: object requires documentation | ||
| 194 | &1 billing documents were created | Space: object requires documentation | ||
| 195 | Planned cumulative quantity: Schedule line has been added or increased | Space: object requires documentation | ||
| 196 | Planned cumulative qty: Schedule line qty/qties has (have) been reduced | Space: object requires documentation | ||
| 197 | &1 &2 should be selected for deletion | Space: object requires documentation | ||
| 198 | The requested number of billing document items was not created | Space: object requires documentation | ||
| 199 | The value-added tax ID for the vendor is different | Space: object requires documentation | ||
| 200 | The customer value-added sales tax ID is different | Space: object requires documentation | ||
| 201 | Enter the required quantity | Space: object requires documentation | ||
| 202 | This material ist not configurable | Space: object requires documentation | ||
| 203 | The customer number you have entered is invalid | Space: object requires documentation | ||
| 204 | SIMULATE: & | |||
| 205 | CREATE: & | |||
| 206 | A delivering plant could not be determined | Space: object requires documentation | ||
| 207 | The customer order number you have entered does not exist | Space: object requires documentation | ||
| 208 | Item &1 contains delivery schedules without schedule line quantities | Space: object requires documentation | ||
| 209 | Enter a lower quantity for item & | Space: object requires documentation | ||
| 210 | No accounting data is maintained for the material &1 | Space: object requires documentation | ||
| 211 | Data was not found for the document | Space: object requires documentation | ||
| 212 | Please enter complete data | Space: object requires documentation | ||
| 213 | No data found | Space: object requires documentation | ||
| 214 | Maintain a valid serial number for the engineering change status | Space: object requires documentation | ||
| 215 | The transmitted date qualifier &1 is invalid | Space: object requires documentation | ||
| 216 | Billing documents can only be canceled completely | Space: object requires documentation | ||
| 217 | Several billing documents are affected by the cancellation | Space: object requires documentation | ||
| 218 | The configuration has set value &1 | Space: object requires documentation | ||
| 219 | Sales document &1 was not changed | Space: object requires documentation | ||
| 220 | Field &1 is not in VBAK or VBKD | Space: object requires documentation | ||
| 221 | Sales document &1 was changed | Space: object requires documentation | ||
| 222 | Service order & should be blocked | Space: object requires documentation | ||
| 223 | Error in BAPI configuration | Space: object requires documentation | ||
| 224 | Missing item number when you changed the schedule line | Space: object requires documentation | ||
| 225 | Schedule line number missing when you changed the schedule line | Space: object requires documentation | ||
| 226 | There are open quotations for material & | Space: object requires documentation | ||
| 227 | There ae open contracts for material & | Space: object requires documentation | ||
| 228 | There are open quotations/contracts for material & | Space: object requires documentation | ||
| 229 | Item &1: Order quantity (&2) greater than billed quantity (&3) | Space: object requires documentation | ||
| 230 | Item &1 cannot be deleted | Space: object requires documentation | ||
| 231 | Material &1 does not exist in plant &2. New plant: &3 | Space: object requires documentation | ||
| 232 | Forecast delivery schedule is incompatible with the JIT delivery schedule | Space: object requires documentation | ||
| 233 | &1 has been processed successfully | Space: object requires documentation | ||
| 234 | The received cumulative quantity from the delivery schedule is negative | Space: object requires documentation | ||
| 235 | Cumulative received quantity is missing and is automatically determined | Space: object requires documentation | ||
| 236 | IDoc was processed in prestep | Space: object requires documentation | ||
| 237 | IDoc was processed in prestep. There are &3 errors. | Space: object requires documentation | ||
| 238 | End to posting transmission &1 | Space: object requires documentation | ||
| 239 | Posting transmission &1 was terminated: Status &2 | Space: object requires documentation | ||
| 240 | Transmission &1 is blocked | Space: object requires documentation | ||
| 241 | Ext.serv.agt carryf. in item &1 - two correction deliveries are necessary | Space: object requires documentation | ||
| 242 | The current cumul.issued quant. is less than cumul. quant. rec. by cust. | Space: object requires documentation | ||
| 243 | Sales unit in IDoc is different from the sales unit in scheduling agrmnt | Space: object requires documentation | ||
| 244 | Scheduling agreements were found with differing sales units | Space: object requires documentation | ||
| 245 | Function not possible. Item &1 has been rejected. | Space: object requires documentation | ||
| 246 | &1 is not allowed for LOGIC_SWITCH-PRICING | Space: object requires documentation | ||
| 247 | Availability check for material & is not possible | Space: object requires documentation | ||
| 248 | Error in &1 &2 | Space: object requires documentation | ||
| 249 | MSR - Message #1 for Viktor | The short text describes the object sufficiently | ||
| 250 | MSR - Message #2 for Viktor | The short text describes the object sufficiently | ||
| 251 | Dummy message for Note 356656 | Space: object requires documentation | ||
| 252 | Dummy Message for Note 390577 | Space: object requires documentation | ||
| 253 | Document no longer modifiable; purch. orders in doc. flow are archived | Space: object requires documentation | ||
| 254 | The document flow contains various currencies | Space: object requires documentation | ||
| 255 | Currency &1 is not an ISO code | Space: object requires documentation | ||
| 256 | The ISO code is missing for currency &1 | Space: object requires documentation | ||
| 257 | Different currency | Space: object requires documentation | ||
| 258 | Currency translation could not be carried out | Space: object requires documentation | ||
| 259 | Currency translation from &1 (ISO) to &2 (ISO) has been carried out | Space: object requires documentation | ||
| 260 | The scheduling agreement &1 could not be blocked | Space: object requires documentation | ||
| 261 | The scheduling agreement &1 could not be unlocked | Space: object requires documentation | ||
| 262 | The scheduling agreement &1 has been blocked by another user (&2) | Space: object requires documentation | ||
| 263 | Batch &1 in plant &2 does not exist | Space: object requires documentation | ||
| 264 | Batch & expires on & | Space: object requires documentation | ||
| 265 | Schedule line is already ordered - you need to create a new schedule line | Space: object requires documentation | ||
| 266 | Note: Production orders exist for this item | Space: object requires documentation | ||
| 267 | Delivery plan &1 not used (vendor number not suitable) | Space: object requires documentation | ||
| 268 | Correction delivery for sched. agreement &1 &2 qty &3 is not automatic | Space: object requires documentation | ||
| 269 | The changes could not be copied to sales order & | Space: object requires documentation | ||
| 270 | Process the original document in the CRM system | Space: object requires documentation | ||
| 271 | Preceding item &1 has status 'fully invoiced'. | Space: object requires documentation | ||
| 272 | Dummy: Switch for direct update of sales documents | The short text describes the object sufficiently | ||
| 273 | Dummy: Switch for special posting date logic (SAP Note 680937) | The short text describes the object sufficiently | ||
| 274 | Dummy: Switch for equal distribution of difference amounts | The short text describes the object sufficiently | ||
| 275 | Dummy: Switch for Accrual Closeout in Rebate Arrangement Currency | The short text describes the object sufficiently | ||
| 276 | Dummy: Switch for old distribution logic (Note 1752423) | The short text describes the object sufficiently | ||
| 277 | Reloading is officially not supported (Note 373568) | Space: object requires documentation | ||
| 278 | Scheduling agreement &1 was processed in system &2 | Space: object requires documentation | ||
| 279 | Scheduling agreement &1 could not be processed in system &2 | Space: object requires documentation | ||
| 280 | First corr. delivery on &3: +&1 &2; Second corr. delivery on &4: -&1 &2 | Space: object requires documentation | ||
| 281 | The planning delivery schedule could not be created automatically | Space: object requires documentation | ||
| 282 | Enter a delivery date | Space: object requires documentation | ||
| 283 | The schedule line &1 for item &2 cannot be deleted. | Space: object requires documentation | ||
| 284 | Scheduling agreements &1 &2 belong to several active integration models | Space: object requires documentation | ||
| 285 | JIT delivery schedule horizon not created for item &1 | Space: object requires documentation | ||
| 286 | APO Sales Scheduling Agrmnt.: Releases can only be created/changed in APO | Space: object requires documentation | ||
| 287 | Schedule line for &1 in plant &2 was not confirmed | Space: object requires documentation | ||
| 288 | Item &2 contains a plnd deliv. sched. instr. &3 but no plnd deliv. sched. | Space: object requires documentation | ||
| 289 | Fiscal year change is inconsistent | Space: object requires documentation | ||
| 290 | Fiscal year start is inconsistent | Space: object requires documentation | ||
| 291 | Scheduling agreement &1, item &2: Planning delivery schedule incomplete | Space: object requires documentation | ||
| 292 | Scheduling Agreement Item &1 &2: Invalid Type for Fiscal Year Change | Space: object requires documentation | ||
| 293 | The cumulative received quantity was reduced without a change of year | Space: object requires documentation | ||
| 294 | JIT del. sched. horizon &1 smaller than release date &2 (see long text) | Space: object requires documentation | ||
| 295 | No BOM explosion occurs in scheduling agreements for suppliers | Space: object requires documentation | ||
| 296 | Original document in CRM system: No update in Funds Management | Space: object requires documentation | ||
| 297 | Index VLPKM: found scheduling agreement item &1/&2 does not exist (VBAP) | Space: object requires documentation | ||
| 298 | Plant &1: Company code is different to that of main item | Space: object requires documentation | ||
| 299 | External document number &1 does not match reference document number &2 | Space: object requires documentation | ||
| 300 | No handover location is available for handover date &1 | The short text describes the object sufficiently | ||
| 301 | No handover location is available for handover time &1 | The short text describes the object sufficiently | ||
| 302 | Date of transfer &1 is later than the delivery date | The short text describes the object sufficiently | ||
| 303 | Time of transfer &1 is later than the time of the delivery date | The short text describes the object sufficiently | ||
| 304 | Date of transfer &1 is earlier or the same as the goods issue date | The short text describes the object sufficiently | ||
| 305 | Time of transfer &1 is earlier than the time of the goods issue | The short text describes the object sufficiently | ||
| 306 | Handover location &1 does not exist | The short text describes the object sufficiently | ||
| 307 | Select a valid line | |||
| 308 | Do not select an empty forecast delivery schedule / JIT delivery schedule | The short text describes the object sufficiently |
History
| Last changed on/by | 20131127 | SAP | |
| SAP Release Created in |