COD_BYD_ERP_INT -
The following messages are stored in message class COD_BYD_ERP_INT: .
It is part of development package CFC_COMMON in software component LO-INT-COD. This development package consists of objects that can be grouped under "C4C Integration Common".
It is part of development package CFC_COMMON in software component LO-INT-COD. This development package consists of objects that can be grouped under "C4C Integration Common".
Message Nr ▲ | Message Text |
---|---|
000 | Sales document &1 does not reference a Cloud for Customer document |
001 | Sales document items could not be assigned -> see long text. |
002 | Multiple source systems for opportunities referenced in document &1 |
003 | Copy Control for &1: Type of successor document is not unique |
004 | Type &1 of successor document is not supported |
005 | No successor document was created |
006 | Sales order &1 does not reference an external predecessor document |
007 | No logical system for external document found in sales order &1 |
008 | Pricing data could not be read |
009 | Import parameter is missing. Implement note 1984312 and 2220998. |
010 | Service Organisation is missing |
011 | Service Team is missing |
012 | Sales Organisation is missing. Company code can't be determined. |
013 | Contract is &1 and Contract Item is &2 |
014 | Internal order is &1 |
015 | Time Recording counter &1 |
016 | Contract document &1 is not in the database or has been archived |
017 | Internal Order &1 could not be read |
018 | Contract &1 modified successfully |
019 | No records selected |
020 | Change pointer is not active for message type HRMD_A_CFS |
021 | &1 needs to be completed |
022 | Illegal status change on Internal Order |
023 | Internal Order &1 is in status closed |
024 | Internal Order &1 is already Technically Completed |
025 | Error in creation of accounting document for object &1 |
026 | Equipment Number is missing |
027 | &1 of item &2 needs to be completed. |
028 | Length of document ID &1 is not valid. |
035 | Select an integration option |
036 | This report is deprecated. Please use report &1 instead. |
050 | System preconditions are not fulfilled. Wrong release. |
051 | Output condition type could not be determined |
100 | The ISO languageCode cannot be determined for the language &1 |
101 | The ISO currencyCode cannot be determined for the currency &1 |
102 | Error during coversion of field &1 content &2 |
103 | The ISO UnitCode cannot be determined for unit &1 |
104 | The content of the field &1 is too long |
105 | Account group &1 cannot be changed to &2 using IDoc inbound |
106 | Search Term defaulted to &1 |
200 | RFC dest. &1 already exists with different target (server &2, path &3) |
201 | Destination &1 of type &2 already exists |
202 | Error when creating destination &1 of type &2 |
203 | Destination &1 of type &2 has been created |
204 | Port &1 of type &2 already exists for another RFC destination |
205 | Port &1 of type &2 already exists |
206 | Error when creating port &1 of type &2 |
207 | Port &1 of type &2 has been created |
208 | Outbound message &1 has been inserted into partner profile for &2 |
209 | Outbound message &1 is already contained in the partner profil for &2 |
210 | Error when inserting outbound message &1 into partner profile for &2 |
211 | Condition &1 has been inserted for message type &2 |
212 | Condition &1 is already contained for message type &2 |
213 | Distribution model view &1 has been created |
214 | Message &1 has been inserted into distribution model view &2 |
215 | Message &1 is already defined for recipient &2 |
216 | Error when inserting message &1 into distribution model view &2 |
217 | BAPI &1 &2 has been inserted into distribution model view &3 |
218 | BAPI &1 &2 is already defined for recipient &3 |
219 | Error when inserting BAPI &1 &2 into distribution model view &3 |
220 | Error when creating distribution model view for outgoing messages |
221 | Inbound message &1 has been inserted into partner profile for &2 |
222 | Inbound message &1 is already contained in the partner profil for &2 |
223 | Error when inserting inbound message &1 into partner profile for &2 |
224 | Error when creating partner profile for &1 |
225 | Partner profile for &1 created |
226 | Partner profile for & already exists |
227 | Distribution model view &1 already exists |
228 | Please enter the target host |
229 | The combination of Message Type, Basic Type and Extension is not valid |
230 | Combination of Message Type, Basic Type, Extension and View is not valid |
231 | Message Type used for inbound processing is not valid |
232 | Host is mandatory |
233 | System Number is mandatory for connecting to SAP Netweaver PI |
234 | Service No. is mandatory for SAP HANA Cloud Integration |
235 | Either User/Password or SSL is mandatory for ABAP/HTTP connections |
236 | Error when creating port &1. No destination available |
237 | Error while creating IDOC for partner number &. |
238 | IDOC & created succesfully for partner number &. |
239 | Assignment for sales office & to sales area & has been discarded. |
240 | Assignment for sales group & to sales Office & has been discarded. |
241 | Assignment for sales office & to sales area & has been included. |
242 | Error while displaying error log. |
243 | Data processed sucessfully. |
244 | Assignment for sales group & to sales Office & has been included. |
245 | Details for & code & . |
246 | No implementation is found for BADI. |
247 | No data selected |
248 | Assignment for sales org & to company code & has been included. |
249 | No Country/Region ISO code exists for &. |
250 | Partner number not maintained. |
251 | No Text is maintained in language &.The text in & was exported. |
252 | Selected Company codes |
253 | Selected Sales org codes |
254 | Selected Sales office codes |
255 | Selected Sales group codes |
256 | Messages for idoc creation |
257 | Please maintain text in language &. |
258 | Cats record &1 maintained. |
259 | No Activity Type could be determined for Material & |
260 | Errors occurred. Please check application log HRALE in transaction SLG1 |
261 | Config. was created for inbound srv. &1 with profile DEFAULT_PROFILE |
262 | Config. for inbound srv. &1 already exists |
263 | Definition for inboun srv. &1 does not exist |
264 | Error when creating config for inbound srv. &1 |
265 | Error when accessing service APIs |
266 | Variant &1 for report &2 has been created |
267 | Variant &1 for report &2 already exists |
268 | Error when creating variant &1 for report &2 |
269 | Error when creating job &1 |
270 | Job &1 has been created |
271 | Report was executed for logical system & |
272 | Error when reading job &1 |
273 | Job &1 already exist |
274 | Condition &1 has been inserted with change flag for message type &2 |
275 | Condition &1 with change flag is already contained for message type &2 |
276 | Please change port assignment from &1 to &2 |
277 | Please change RFC destination from &1 to &2 |
278 | Outbound IDoc &1 created for Sales Document &2 |
279 | Sales Document &1 could not be processed for outbound |
280 | &1 Sales Documents successfully processed |
281 | No receiver system determined. |
282 | No Doc flow exists for anchor & |
283 | No Status exists for Document & in ERP |
284 | No date exists for Document & in ERP |
285 | No description exists for Document & in ERP |
286 | Document & does not exists in ERP system. |
287 | No plant for consignment process found |
288 | No consignment order provided |
289 | Job processing started for &1 Sales Documents |
290 | Price calculation failed for item &1 |
291 | &1 Sales Documents selected for processing |
292 | Error when creating config for outbound srv. &1 |
293 | Config. was created for outbound srv. &1 |
294 | Outbound IDoc &1 created for Contract &2. |
295 | Contract &1 could not be processed for outbound. |
296 | &1 Contract data successfully processed, |
297 | &1 Contract entries selected for processing. |
298 | &1 Contracts selected for processing |
299 | Job processing started for &1 Contracts |
300 | Default logical port for consumer proxy &1 not found |
301 | Technical error when creating consumer proxy object &1 |
302 | Error when requesting data from C4C. Proxy class &1. Usage: &2 |
303 | No data retreived for the chosen selection criterias from VBAK/VBUK |
304 | Error when trying to maintain data in C4C |
305 | UUID for account & not found |
306 | UUID GDT conversion error |
307 | Recent orders for &1 accounts transferred |
308 | Error in response from ManageRecentOrderData |
309 | No ID-Mapping received |
310 | No account ID mapping values available |
311 | Account &1 transferred with &2 sales documents |
312 | Update request rejected. ERP image is newer |
313 | Binary Relationship Creation Failed |
314 | Errors occured during extraction. No IDoc was created |
315 | Account &1 not considered because no ID mapping exists in C4C |
316 | Error during selection : &1 |
317 | Billing Plan Update Request Rejected; ERP Contract Not Created |
318 | ERP Contract was modified successfully. &1 &2 |
319 | Billing Plan Update Request Rejected; ERP Contract Changed |
320 | Modify request could not be performed; ERP Contract changed |
321 | Billing Plan update failed for Item &1. |
322 | Prices were calculated without considering new Billing Plan data |
323 | Error occured in updating covered objects for contract &1 item &2. |
324 | Outbound message &1 created for Contract &2 Call Off Statistics. |
325 | Outbound message for Call Off Statistics of Contract &1 not created. |
326 | Outbound message &1 created for Contract Call Off Statistics replication. |
327 | Logical port already exists for outbound service &1 |
330 | IDoc Type &1 added to white list table. See note 1560878. |
350 | &1 of Plant/Storage Location entries are selected for processing |
351 | Outbound IDoc &1 created for Stock Replication |
352 | Error creating IDOC for Stock Replication |
353 | Plant not maintained |
354 | &1 records selected for processing. |
355 | SERVICE_ORG SERVICE_TEAM SERVICE_TECH are mandatory parameters |
356 | Mandatory Paramter SERVICE_TEAM is not maintained |
357 | Mandatory Paramter SERVICE_TECH is not maintained |
358 | No Customer found for service technician &1, record ignored |
359 | Entry is not relevant for replication, record ignored. See Long Text |
360 | No Company Code for plant &1 Could be determined. Record Ignored |
361 | Neither Plant nor Sales Organisation is selected. |
362 | Select Either Sales Organisation or Plant. |
363 | Assignment of Plant & has been included. |
364 | Selected Plant data |
370 | Only first &1 Serial Numbers for Material &2 are transferred |
398 | Real Mode: &1 record(s) selected |
399 | No IDocs generated |
400 | Test Mode: &1 record(s) selected |
401 | IDoc &1 generated |
402 | &1 IDoc(s) generated for message type &2 |
403 | Error during call of function module &1 |
404 | Valid Loading group does not exist |
405 | Valid Shipping Point does not exist |
406 | &1: Conflicting entries in selection screen and distribution model |
407 | Product hierarchy option is selected |
408 | Material group option is selected |
409 | Complete transmission option is selected |
410 | Complete transmission option is not selected |
411 | There are two items which equal: & after suppressing the leading zeros |
412 | Entries might have been filtered out due to the distribution model |
500 | & & & & |
599 | Job Processing |
600 | Running in Test Mode |
601 | Parallel Processing Enabled |
602 | Input parameters not maintained |
610 | Internal Order for Service Ticket & cannot be determined |
611 | Generated document number &1 |
612 | No Internal Order determined for Service Ticket &1 |
613 | Error occurred in updating covered objects for &1 item &2 |
614 | Error during follow up Order creation for Quote &1 |
615 | Error while saving follow up Order for Quote &1 |
616 | Commit Failed |
700 | Outbound ALE Function Module for message type & not found. |