J1B_NFE_ERP_GRC - Message Class for NFe ERP-GRC Communication
The following messages are stored in message class J1B_NFE_ERP_GRC: Message Class for NFe ERP-GRC Communication.
It is part of development package J1BNFE in software component CA-GTF-CSC-EDO-BR. This development package consists of objects that can be grouped under "Brazil Eletronic Nota Fiscal".
It is part of development package J1BNFE in software component CA-GTF-CSC-EDO-BR. This development package consists of objects that can be grouped under "Brazil Eletronic Nota Fiscal".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** Messages 001-099 are defined in GRC, 100-199 in ERP / do not use |
| 001 | Document &1 is already in process |
| 002 | Document &1 already exists |
| 003 | Document &1: Customizing error: Key storage data not maintained |
| 004 | Document &1: Customizing error: Official version not maintained |
| 005 | Document &1: Customizing error: XML version not maintained |
| 006 | Document &1: Signature service is not available |
| 007 | Validation info: Field &1 in check &2 is filled |
| 008 | Validation error: Field &2: &3 (Field &1) |
| 009 | No entry for NF-e &1 exists in table /XNFE/NFE_HIST |
| 010 | |
| 012 | Document &1: The XML version &2 is not supported |
| 013 | Status of NF-e &1 does not allow cancellation/skipping |
| 014 | Error occurred for document &1 during proxy transformation |
| 034 | |
| 040 | NF-e &1 does not exist |
| 041 | NF-e &1 with validation error, no XML available |
| 044 | No XML available for NF-e &1 |
| 101 | Wrong message type for document &1 |
| 102 | Document number and Access key are empty |
| 103 | No entry exists in the NF-e table for document number &1 / access key &2 |
| 104 | A protocol number is required for NF-e &1 |
| 105 | Message type &1 is not defined |
| 106 | No status code was received for NF-e &1 |
| 107 | Document status &3 is not allowed for NF-e &1 with sys.comm.status &2 |
| 108 | Current status &1 does not allow next status &2 for document &3 |
| 109 | New system communication status &1 is not allowed for previous SCS &2 |
| 110 | Protocol number &1 is not numeric |
| 111 | DB error: insert of NF-e with key &1, &2, &3 into J_1BNFE_HISTORY failed |
| 112 | Nota Fiscal &1 not found |
| 113 | Table &1 is locked by another user |
| 114 | New system communication status &1 is not allowed for MsgStatus &2 |
| 115 | |
| 116 | XML for Nota Fiscal &1 has already been processed |
| 200 | *** Messages 201-299 are defined in GRC for CT-e******************** |
| 201 | Mapping error: Error during mapping of structure &1 |
| 202 | Mapping error: Error during mapping of the &1 field in structure &2 |
| 203 | Mapping error: Field &1 in structure &2 must be filled |
| 204 | Error during XML transformation: &1, &2, &3 |
| 205 | Mapping error: One of the parameters &1, &2, &3 must be filled |
| 206 | Mapping error: Error during mapping of structure &1; parameter &2 missing |
| 207 | Mapping error: Value &1 in field &2 of structure &3 is not allowed |
| 208 | Mapping error: No partner was found for structure &1 |
| 209 | Mapping error: No taxes were found for structure &1 |
| 210 | Mapping error: No lines were found in table &1 |
| 211 | Mapping error: No texts were found for structure &1 |
| 212 | Mapping error: No values were found for structure &1 |
| 213 | Status &2 of the proccess step &1 does not allow overwriting of CT-e |
| 214 | Customizing error: XML version for message type &1 not defined |
| 215 | Validation error: field &1: &2. Content not allowed (&3) |
| 216 | Validation error: field &1: &2. Negative value not allowed (&3) |
| 217 | Valid. error: CT-e ID does not match the format of tax authorites (&1) |
| 218 | System environm. &1 (Homologation or Production) differs from customizing |
| 219 | Customizing error: No entry found for specified tax authority system |
| 220 | CT-e &1 is being edited by user &2 |
| 221 | CT-e &1 already exists |
| 222 | ERP RFC version &1 not supported |
| 223 | Mode of transport &1 not supported |
| 224 | Combination of XML version of CT-e &1 and modal &2 not supported |
| 225 | CT-e XML version &1 not supported |
| 226 | Validation error: Field &1: Field no. &2 must be filled |
| 227 | CT-e &1 does not exist |
| 228 | CT-e &1 with validation error, no XML available |
| 229 | No XML available for CT-e &1 |
| 230 | Model &1 is not supported for NF-e |
| 231 | Model &1 is not supported for CT-e |
| 250 | Mapping error: The parameter & 1 must be filled |
| 251 | Mapping Error: No values found for row ID &1 in parameter &2 |
| 252 | Status &1 of process step &2 does not permit sending the skipping request |
| 300 | *** Messages 301-399 are defined in ERP for CT-e specific messages** |
| 400 | *** Messages 401-499 are defined in GRC for events |
| 401 | No suitable NF-e found |
| 402 | Corresponding NF-e event already exists |
| 403 | Error during processing of NF-e event string |
| 404 | NF-e is locked; NF-e event cannot be created |
| 405 | Official NF-e event code does not correspond to expected value |
| 406 | NF-e event cannot be created; retry or contact system administrator |
| 407 | Event has been saved before RFC terminated. Resend not allowed |
| 408 | Error in the global table &1 |
| 409 | Error during reading event data |
| 410 | Validation error: Text is too short or too long |
| 411 | Validation error in CC-e: Sequence number is greater than 20 |
| 412 | Validation error in CC-e: NF-e &1 is older than 30 days |
| 413 | NF-e &1 is not authorized |
| 414 | Error during proxy transformation: &1 |
| 415 | XML schema error; invalid time zone for NF-e event creation |
| 416 | Time zone could not be determined |
| 417 | Not possible to process the event or change its status |
| 418 | Event could not be signed |
| 419 | No suitable entry in customizing for CNPJ &1 |
| 420 | NF-e &1 has already been archived |
| 421 | Events cannot be created at this time; the CT-e is blocked |
| 422 | CT-e &1 is not authorized |
| 423 | Could not find a suitable CT-e |
| 424 | CT-e &1 already written to archive file |
| 438 | Valid. error EPEC: field content &2 (&3) &1 does not match NF-e (&4) |
| 500 | *** Messages 501-599 are defined in ERP for events |
| 501 | NF-e event &1 not assigned to an event code in Customizing |
| 502 | Nf-e event &1 not defined as electronic correction letter in Customizing |
| 503 | Database error; system could not update NF-e Event Table with key &1 |
| 504 | No electronic correction letter with sequence no. &2 found for NF-e &1 |
| 505 | NF-e event &1 not assigned to an event group &2 in Customizing |
| 506 | No corresponding NF-e event found for document &1 event &2 int. seqno. &3 |
| 507 | NF-e event &2 internal seqno. &3 for doc. &1 has already been processed |
| 508 | NF-e event &2 (&3) for &1 has already been processed with different data |
| 509 | NF-e event &2 (&3) for document &1 has no authorization timestamp |
| 515 | Field & not found in table & |
| 516 | Value & is invalid for field & in table & |
| 517 | Synchronization not possible, error while locking document |
| 518 | Document & not found |
| 519 | Document not loaded |
| 520 | Document & not locked |
| 521 | Error while locking document |
| 522 | Synchronization not possible, document locked by another user |
| 523 | Exception: & |
| 604 | MDF-e &1 with validation error, no XML available |
| 608 | &1 is not supported in Scenario &2 |
| 609 | &1 is not a valid document type |
| 611 | &1 with ID &2 is cancelled |
| 612 | MDF-e &1 does not exist |
| 614 | No XML available for MDF-e &1 |