SAP ABAP Message Class /XNFE/APPEVENT (Event Messages)
Basic Data
Hierarchy
☛
SLL-NFE (Software Component) xNFE
⤷
SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷
/XNFE/APPEVENT (Package) Events: Application Functions
⤷
⤷
Attributes
| Message class | /XNFE/APPEVENT | |
| Short Description | Event Messages | |
| Changed On | 20141107 | |
| Last Changed At | 192303 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | &1 | The short text describes the object sufficiently | ||
| 2 | Event &1 of type &2 for &3 already exists | The short text describes the object sufficiently | ||
| 3 | Event &1 is currently being edited by user &2 | The short text describes the object sufficiently | ||
| 4 | Error during update: &1 table &2 | The short text describes the object sufficiently | ||
| 5 | No database entry with ID &1 found | The short text describes the object sufficiently | ||
| 6 | There is already an open event for &1 with type &2 | The short text describes the object sufficiently | ||
| 7 | No details available for selected type &1 event | The short text describes the object sufficiently | ||
| 8 | Event with type &1 is unknown and cannot be processed | The short text describes the object sufficiently | ||
| 9 | Prior event &1 is currently being processed by user &2 | The short text describes the object sufficiently | ||
| 10 | Event with type &1 for &2 created with sequence number &3 | The short text describes the object sufficiently | ||
| 11 | Another event of type &1 for &2 created with sequence number &3 | The short text describes the object sufficiently | ||
| 12 | Some events cannot be displayed due to insufficient authorization | The short text describes the object sufficiently | ||
| 13 | Internal error selecting an event | The short text describes the object sufficiently | ||
| 14 | Internal error; application ID &1 is unknown | The short text describes the object sufficiently | ||
| 15 | No matching RFC destination found for logical system &1 | The short text describes the object sufficiently | ||
| 16 | No XML document exists in the database for event &1 | The short text describes the object sufficiently | ||
| 17 | Incorrect call: Parameter &1 must not be initial | The short text describes the object sufficiently | ||
| 18 | Incorrect call: Parameter &1 cannot be &2 | The short text describes the object sufficiently | ||
| 19 | Current event has no error status; cannot be created again | The short text describes the object sufficiently | ||
| 20 | Current event has no SEFAZ status; new creation not possible | The short text describes the object sufficiently | ||
| 21 | Search criteria entries are insufficient | Space: object requires documentation | ||
| 22 | Error in global table &1 | The short text describes the object sufficiently | ||
| 23 | No entry found in main memory for event &1 | The short text describes the object sufficiently | ||
| 24 | Event &1 of type &2 for &3 does not exist | The short text describes the object sufficiently | ||
| 25 | No event of type &1 for &2 found | The short text describes the object sufficiently | ||
| 26 | No event possible: NF-e &1 does not exist or is not authorized | The short text describes the object sufficiently | ||
| 27 | No suitable entry in Customizing available for CNPJ &1 | The short text describes the object sufficiently | ||
| 28 | Event could not be signed | The short text describes the object sufficiently | ||
| 29 | Log number missing for event GUID &1 | The short text describes the object sufficiently | ||
| 30 | Event of the type &1 with sequence number &2 for &3 not found | The short text describes the object sufficiently | ||
| 31 | Registration time from SEFAZ is missing for event GUID &1 | The short text describes the object sufficiently | ||
| 32 | Communication/system error during ERP status update for event GUID &1 | The short text describes the object sufficiently | ||
| 33 | PI: Acknowledgment contains system error; &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 34 | Error during proxy call: &1 | The short text describes the object sufficiently | ||
| 35 | Message ID of Process Integration (PI/XI) is initial | The short text describes the object sufficiently | ||
| 36 | Event query failed; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | ||
| 37 | Event status &1 does not allow B2B transit for the event | The short text describes the object sufficiently | ||
| 38 | Message successfully sent to B2B partner | The short text describes the object sufficiently | ||
| 39 | Event XML successfully sent to event receiver | The short text describes the object sufficiently | ||
| 40 | Event XML successfully sent to transporter | The short text describes the object sufficiently | ||
| 41 | Scenario &1 is not supported | The short text describes the object sufficiently | ||
| 42 | Assignment of event &1 (step &2, status &3) to new batch is not allowed | The short text describes the object sufficiently | ||
| 43 | Assigning event &1 to new batch (old batch ID &2) | The short text describes the object sufficiently | ||
| 44 | Query of events started by user &1; message &2 | The short text describes the object sufficiently | ||
| 45 | &1 event(s) of type &2 transferred; &3 already exist; message &4 | The short text describes the object sufficiently | ||
| 46 | No events transferred; message &1 | The short text describes the object sufficiently | ||
| 47 | ****** New Event Process Flow ****************************************** | The short text describes the object sufficiently | ||
| 48 | No process flow found for business process &1 | The short text describes the object sufficiently | ||
| 49 | Further processing or status change of the event is not possible | The short text describes the object sufficiently | ||
| 50 | Implementation for process step &1 missing | The short text describes the object sufficiently | ||
| 51 | Event is waiting for a reply | The short text describes the object sufficiently | ||
| 52 | Event &1 cannot be processed; waiting for asynchronous reply | The short text describes the object sufficiently | ||
| 53 | Process step &1 is not intended for event | The short text describes the object sufficiently | ||
| 54 | Event B2B process successfully launched | The short text describes the object sufficiently | ||
| 55 | **************************** BATCH PROCESS ****************************** | The short text describes the object sufficiently | ||
| 56 | Batch ID error; check the number range interval | The short text describes the object sufficiently | ||
| 57 | No entry found in main memory for event batch &1 | The short text describes the object sufficiently | ||
| 58 | Event batch &1 is being processed by user &2 | The short text describes the object sufficiently | ||
| 59 | Sending again is not allowed with the current batch status | The short text describes the object sufficiently | ||
| 60 | Error while creating the event batch | The short text describes the object sufficiently | ||
| 61 | No batch event exists with ID &1 | The short text describes the object sufficiently | ||
| 62 | Error reading batch data ID &1 | The short text describes the object sufficiently | ||
| 63 | Error during status update of event batch &1 | The short text describes the object sufficiently | ||
| 64 | Event is added to event batch &1 | The short text describes the object sufficiently | ||
| 65 | Error sending event batch &1 | The short text describes the object sufficiently | ||
| 66 | SAP NetWeaver PI reports error while sending event batch &1 | The short text describes the object sufficiently | ||
| 67 | SAP NetWeaver PI reports error while sending event to B2B partner | The short text describes the object sufficiently | ||
| 68 | SAP NetWeaver PI reports error while sending event status query | The short text describes the object sufficiently | ||
| 69 | PI: Acknowledgment contains system errors; message ID &1 | The short text describes the object sufficiently | ||
| 70 | Error in assigning answer from authorities; event batch ID &1 | The short text describes the object sufficiently | ||
| 71 | Rejected: &1 | The short text describes the object sufficiently | ||
| 72 | Batch &1 successfully sent to authority; message ID &2 | The short text describes the object sufficiently | ||
| 73 | Technical error while sending batch: &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 74 | Status code of batch is empty | The short text describes the object sufficiently | ||
| 75 | Reply from authority contains an error: field &1 is empty | The short text describes the object sufficiently | ||
| 76 | Batch event received by authority; status code of batch equals &1 | The short text describes the object sufficiently | ||
| 77 | Error while sending batch; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | ||
| 78 | Batch rejected by authority; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | ||
| 79 | Event status code is empty | The short text describes the object sufficiently | ||
| 80 | Batch ID &1 not found | The short text describes the object sufficiently | ||
| 81 | Technical error while finishing the batch process: &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 82 | Finishing batch process is not permitted for step &1 with status &2 | The short text describes the object sufficiently | ||
| 83 | Batch process manually canceled by user &1 | The short text describes the object sufficiently | ||
| 84 | Further processing or status change for event batch is not possible | The short text describes the object sufficiently | ||
| 85 | Response from authority has error: Field &1 of event is blank | The short text describes the object sufficiently | ||
| 86 | No matching NF-es found | The short text describes the object sufficiently | ||
| 87 | A corresponding event already exists | The short text describes the object sufficiently | ||
| 88 | Error during event string processing: &1 | The short text describes the object sufficiently | ||
| 89 | No event can be created right now because the NF-e is blocked | The short text describes the object sufficiently | ||
| 90 | The event type is not the expected type | The short text describes the object sufficiently | ||
| 91 | The event could not be created | The short text describes the object sufficiently | ||
| 92 | Event was saved prior to the RFC termination; resending is not permitted | The short text describes the object sufficiently | ||
| 93 | Error in global table &1 | The short text describes the object sufficiently | ||
| 94 | Error while reading event data | The short text describes the object sufficiently | ||
| 95 | Validation error: Text is too short or too long | The short text describes the object sufficiently | ||
| 96 | CC-e validation error: Sequence number is greater than 20 | The short text describes the object sufficiently | ||
| 97 | CC-e validation error: NF-e &1 is too old | The short text describes the object sufficiently | ||
| 98 | NF-e &1 is not authorized | The short text describes the object sufficiently | ||
| 99 | Error during proxy transformation: &1 | The short text describes the object sufficiently | ||
| 100 | Scheme violation: Incorrect time zone | The short text describes the object sufficiently | ||
| 101 | Timezone could not be determined | The short text describes the object sufficiently | ||
| 102 | Further processing or status change of the event is not possible | The short text describes the object sufficiently | ||
| 103 | Event could not be signed | The short text describes the object sufficiently | ||
| 104 | No suitable entry in Customizing available for CNPJ &1 | The short text describes the object sufficiently | ||
| 105 | NF-e &1 has already been written to an archive file | The short text describes the object sufficiently | ||
| 106 | Events cannot be created at this time; the CT-e is blocked | The short text describes the object sufficiently | ||
| 107 | CT-e &1 is not authorized | The short text describes the object sufficiently | ||
| 108 | Could not find a suitable CT-e | The short text describes the object sufficiently | ||
| 109 | CT-e &1 already written to archive file | The short text describes the object sufficiently | ||
| 110 | Error during update of NF-e data | The short text describes the object sufficiently | ||
| 111 | Error while updating MDF-e data | The short text describes the object sufficiently | ||
| 112 | Close events are not premitted for MDF-e process | The short text describes the object sufficiently | ||
| 113 | MDF-e process does not permit cancellation event | The short text describes the object sufficiently | ||
| 114 | Driver cannot be added for MDF-e &1; MDF-e already closed | The short text describes the object sufficiently | ||
| 115 | No suitable MDF-e found | The short text describes the object sufficiently | ||
| 116 | At the moment no events can be created; the MDF-e is blocked | The short text describes the object sufficiently | ||
| 117 | MDF-e &1 not authorized | The short text describes the object sufficiently | ||
| 118 | MDF-e &1 already written to archive file | The short text describes the object sufficiently | ||
| 119 | MDF-e mode of transport is not road; driver cannot be added for MDF-e &1 | The short text describes the object sufficiently | ||
| 120 | No event code is assigned to event &1 in Customizing | The short text describes the object sufficiently | ||
| 121 | Event &1 is not maintained as a correction letter in Customizing | The short text describes the object sufficiently | ||
| 122 | DB error: Update of event table for key &1 failed | The short text describes the object sufficiently | ||
| 123 | Document number &1: Correction letter with sequence no. &2 not found | The short text describes the object sufficiently | ||
| 124 | Event &1 is not assigned to event group &2 in Customizing | The short text describes the object sufficiently | ||
| 125 | No event found for document &1, event type &2, internal sequence no. &3 | The short text describes the object sufficiently | ||
| 126 | Event with type &2 and int. seq. no. &3 already processed for document &1 | The short text describes the object sufficiently | ||
| 127 | Event with type &2 (&3) for document &1 processed with different data | The short text describes the object sufficiently | ||
| 128 | Event with type &2 (&3) for document &1 has no timestamp from SEFAZ | The short text describes the object sufficiently | ||
| 129 | Field &1 not found in table &2 | The short text describes the object sufficiently | ||
| 130 | Value &1 is not valid for field &2 in table &3 | The short text describes the object sufficiently | ||
| 131 | Synchronization not possible; error while locking document | The short text describes the object sufficiently | ||
| 132 | Document &1 not found | The short text describes the object sufficiently | ||
| 133 | Document not loaded | The short text describes the object sufficiently | ||
| 134 | Document &1 not locked | The short text describes the object sufficiently | ||
| 135 | Error while unlocking document | The short text describes the object sufficiently | ||
| 136 | Synchronization not possible; document locked by another user | The short text describes the object sufficiently |
History
| Last changed on/by | 20141107 | SAP | |
| SAP Release Created in | 900 |