SAP ABAP Message Class /XNFE/APP (Messaging Application xNF-e)
Basic Data
Hierarchy
☛
SLL-NFE (Software Component) xNFE
⤷
SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷
/XNFE/APP (Package) NF-e: Application Functions
SLL-NFE (Software Component) xNFE⤷
SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring⤷
/XNFE/APP (Package) NF-e: Application Functions 
Attributes
| Message class |  |
/XNFE/APP |
| Short Description |  |
Messaging Application xNF-e |
| Changed On |  |
20141107 |
| Last Changed At |  |
192303 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  001 |
Error during update: &1 table &2 | The short text describes the object sufficiently | |
| 2 | 002 |
Number range for batch missing | The short text describes the object sufficiently | |
| 3 | 003 |
Version missing for query of service status | The short text describes the object sufficiently | |
| 4 | 004 |
Error in function &1 (RC = &2) | The short text describes the object sufficiently | |
| 5 | 005 |
Error determining the XML version | The short text describes the object sufficiently | |
| 6 | 006 |
Batch not sent successfully | The short text describes the object sufficiently | |
| 7 | 007 |
Batch sent successfully | The short text describes the object sufficiently | |
| 8 | 008 |
Error determining the service status | The short text describes the object sufficiently | |
| 9 | 009 |
Error sending the batch request (&1) | The short text describes the object sufficiently | |
| 10 | 010 |
Authority status not valid for batch (CSTAT &) | The short text describes the object sufficiently | |
| 11 | 011 |
Batch ID not available & | The short text describes the object sufficiently | |
| 12 | 012 |
Batch result received for invalid batch status &1: &2 | The short text describes the object sufficiently | |
| 13 | 013 |
Could not save the results of the service status checks | The short text describes the object sufficiently | |
| 14 | 014 |
No service status check needed | The short text describes the object sufficiently | |
| 15 | 015 |
Error loading file | The short text describes the object sufficiently | |
| 16 | 016 |
B | The short text describes the object sufficiently | |
| 17 | 017 |
Status updated | The short text describes the object sufficiently | |
| 18 | 018 |
Could not update status | The short text describes the object sufficiently | |
| 19 | 019 |
Entry was saved | The short text describes the object sufficiently | |
| 20 | 020 |
Error when saving | The short text describes the object sufficiently | |
| 21 | 021 |
Select a row | The short text describes the object sufficiently | |
| 22 | 022 |
Process &1 was started; refresh the display (NF-e &2) | The short text describes the object sufficiently | |
| 23 | 023 |
Error starting process &1 (NF-e &2) | The short text describes the object sufficiently | |
| 24 | 024 |
Error determining the version (NF-e &1) | The short text describes the object sufficiently | |
| 25 | 025 |
Error determining the XML (NF-e &1) | The short text describes the object sufficiently | |
| 26 | 026 |
No values found for selection | The short text describes the object sufficiently | |
| 27 | 027 |
Key storage data not maintained (NF-e &1) | The short text describes the object sufficiently | |
| 28 | 028 |
No RFC destination found for NF-e &1 (logical system &2) | The short text describes the object sufficiently | |
| 29 | 029 |
Error determining the XML version (NF-e &1) | The short text describes the object sufficiently | |
| 30 | 030 |
Error during call of SAP NetWeaver PI (NF-e &1) | The short text describes the object sufficiently | |
| 31 | 031 |
Error during XML download | The short text describes the object sufficiently | |
| 32 | 032 |
Error determining the version (batch ID &1) | The short text describes the object sufficiently | |
| 33 | 033 |
Process &1 was started; refresh the display (batch ID &2) | The short text describes the object sufficiently | |
| 34 | 034 |
Error starting process &1 (batch ID &2) | The short text describes the object sufficiently | |
| 35 | 035 |
Error when reading: &1 table &2 | The short text describes the object sufficiently | |
| 36 | 036 |
Report is already running in another process | The short text describes the object sufficiently | |
| 37 | 037 |
Error updating table &1 | The short text describes the object sufficiently | |
| 38 | 038 |
No NF-e found | The short text describes the object sufficiently | |
| 39 | 039 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 40 | 040 |
Error sending log to B2B partner (NF-e &1) | The short text describes the object sufficiently | |
| 41 | 041 |
Entry deleted | The short text describes the object sufficiently | |
| 42 | 042 |
Error when deleting | The short text describes the object sufficiently | |
| 43 | 043 |
Fill out all required-entry fields | The short text describes the object sufficiently | |
| 44 | 044 |
You cannot delete this line | The short text describes the object sufficiently | |
| 45 | 045 |
Web service is currently unavailable; batch will not be sent | The short text describes the object sufficiently | |
| 46 | 046 |
Entry already exists | The short text describes the object sufficiently | |
| 47 | 047 |
Batch status query sent successfully | The short text describes the object sufficiently | |
| 48 | 048 |
Validation Error: Field &1. &2 (Field &3, Field ID &4) | The short text describes the object sufficiently | |
| 49 | 049 |
NF-e &1 is already scheduled for ERP status update | The short text describes the object sufficiently | |
| 50 | 050 |
Error in ERP during NF-e status update (NF-e &1) | The short text describes the object sufficiently | |
| 51 | 051 |
Enter missing default values in table/XNFE/BATCUS; see SAP Note 1256697 | The short text describes the object sufficiently | |
| 52 | 052 |
NFe &1 with document status &2 is not permitted to be resent to ERP | The short text describes the object sufficiently | |
| 53 | 053 |
NF-e &1 was resent successfully | The short text describes the object sufficiently | |
| 54 | 054 |
NF-e &1 in parallel mode is not permitted to be resent to ERP | The short text describes the object sufficiently | |
| 55 | 055 |
Error during RFC call (NF-e &1) | The short text describes the object sufficiently | |
| 56 | 056 |
Validation Info: Field &1-&2 in Check &3 has been filled! | The short text describes the object sufficiently | |
| 57 | 057 |
NF-e &1 has an invalid status - start a "Status Query" | The short text describes the object sufficiently | |
| 58 | 058 |
NF-e document status &1 cannot coincide with authority status &2 | The short text describes the object sufficiently | |
| 59 | 059 |
Log number missing for NF-e &1 | The short text describes the object sufficiently | |
| 60 | 060 |
NF-e &1 with document status &2 cannot have a log number | The short text describes the object sufficiently | |
| 61 | 061 |
The entered time is not correct | The short text describes the object sufficiently | |
| 62 | 062 |
Specify the number of retries for update to ERP | The short text describes the object sufficiently | |
| 63 | 063 |
This program can only be used for background processing | The short text describes the object sufficiently | |
| 64 | 064 |
Fill in the "NF-e ID" field | The short text describes the object sufficiently | |
| 65 | 065 |
NF-e &1 from the selection is being edited in another process | The short text describes the object sufficiently | |
| 66 | 066 |
Error during status update in ERP | The short text describes the object sufficiently | |
| 67 | 067 |
Error merging and saving the XML file (NF-e &1) | The short text describes the object sufficiently | |
| 68 | 068 |
The entered date is incorrect | The short text describes the object sufficiently | |
| 69 | 069 |
The object is blocked; refresh the display (batch ID &1) | The short text describes the object sufficiently | |
| 70 | 070 |
The object is blocked; refresh the display (NF-e &1) | The short text describes the object sufficiently | |
| 71 | 071 |
An interruption of the archiving run was requested | The short text describes the object sufficiently | |
| 72 | 072 |
The object cannot be reloaded | The short text describes the object sufficiently | |
| 73 | 073 |
Enter an interval or date earlier than the minimum age &1 (&2 days) | The short text describes the object sufficiently | |
| 74 | 074 |
Document &1 is already in process | The short text describes the object sufficiently | |
| 75 | 075 |
Document &1 already exists | The short text describes the object sufficiently | |
| 76 | 076 |
Document &1: Customizing error: Key storage data not maintained | The short text describes the object sufficiently | |
| 77 | 077 |
Document &1: Customizing error: Official version not maintained | The short text describes the object sufficiently | |
| 78 | 078 |
Document &1: Customizing error: XML version not maintained | The short text describes the object sufficiently | |
| 79 | 079 |
Document &1: Signature service is not available | The short text describes the object sufficiently | |
| 80 | 080 |
Validation info: Field &1 in check &2 is filled | The short text describes the object sufficiently | |
| 81 | 081 |
Validation error: Field (&1) &2, &3 | The short text describes the object sufficiently | |
| 82 | 082 |
Status code &1 from authorities does not match current NF-e process: &2 | The short text describes the object sufficiently | |
| 83 | 083 |
The time difference between servers is greater than &1 seconds | Space: object requires documentation | |
| 84 | 084 |
URL not available | The short text describes the object sufficiently | |
| 85 | 085 |
Attempt to call browser failed | The short text describes the object sufficiently | |
| 86 | 086 |
Internal error in object &1 - processing canceled | The short text describes the object sufficiently | |
| 87 | 087 |
Error correcting XML | The short text describes the object sufficiently | |
| 88 | 088 |
No entry found in table &1 | The short text describes the object sufficiently | |
| 89 | 089 |
Error saving the corrected XML document in KPRO | The short text describes the object sufficiently | |
| 90 | 090 |
Error saving the old XML document | The short text describes the object sufficiently | |
| 91 | 091 |
The XML documents were corrected successfully | The short text describes the object sufficiently | |
| 92 | 092 |
Not all XML documents could be corrected - see application log | The short text describes the object sufficiently | |
| 93 | 093 |
XML documents could not be corrected - field &1 not found | The short text describes the object sufficiently | |
| 94 | 094 |
No incorrect XML documents found | The short text describes the object sufficiently | |
| 95 | 095 |
More than 10 NF-es selected; 10 entries processed | The short text describes the object sufficiently | |
| 96 | 096 |
No document ID found | The short text describes the object sufficiently | |
| 97 | 097 |
Validation error: Table (&1) &2 | The short text describes the object sufficiently | |
| 98 | 098 |
Initial message ID of Process Integration (PI/XI) | The short text describes the object sufficiently | |
| 99 | 099 |
Error reading the XML data | The short text describes the object sufficiently | |
| 100 | 100 |
Customizing error: Tax number &1 not defined | The short text describes the object sufficiently | |
| 101 | 101 |
Key storage data not maintained (BAdI for external signature is active) | The short text describes the object sufficiently | |
| 102 | 102 |
Customizing error: SSF application for tax number &1 not defined | The short text describes the object sufficiently | |
| 103 | 103 |
&1% (&2 of &3) data objects processed | The short text describes the object sufficiently | |
| 104 | 104 |
Error sending the cancellation | The short text describes the object sufficiently | |
| 105 | 105 |
Error sending the skip message | The short text describes the object sufficiently | |
| 106 | 106 |
Log number is not valid | The short text describes the object sufficiently | |
| 107 | 107 |
B2B transit is not active for CNPJ &1 | The short text describes the object sufficiently | |
| 108 | 108 |
B2B error, re-sending is not possible | Space: object requires documentation | |
| 109 | 109 |
No CNPJ of transporter exists in XML file | The short text describes the object sufficiently | |
| 110 | 110 |
Could not determine any data for NF-e &1 | The short text describes the object sufficiently | |
| 111 | 111 |
Could not determine any archive data for NF-e &1 | The short text describes the object sufficiently | |
| 112 | 112 |
Could not determine any XML data for NF-e &1 | The short text describes the object sufficiently | |
| 113 | 113 |
Error reading the data from KPro | The short text describes the object sufficiently | |
| 114 | 114 |
Previous B2B message has not been sent yet | The short text describes the object sufficiently | |
| 115 | 115 |
Process status &1 does not permit B2B shipping for NF-e &2 | The short text describes the object sufficiently | |
| 116 | 116 |
Message successfully sent to B2B partner | The short text describes the object sufficiently | |
| 117 | 117 |
Date and time: Time converted without time zone difference | The short text describes the object sufficiently | |
| 118 | 118 |
Date and time: The time zone you entered is not listed in table TTZZ | The short text describes the object sufficiently | |
| 119 | 119 |
Date and time: Input values are invalid (begin of daylight-saving time?) | The short text describes the object sufficiently | |
| 120 | 120 |
Program for CNPJ &1 is already being run in another process | The short text describes the object sufficiently | |
| 121 | 121 |
Cannot determine document category for access key &1 | The short text describes the object sufficiently | |
| 122 | 122 |
Number of read/archived CT-es: &/& | The short text describes the object sufficiently | |
| 123 | 123 |
Archiving completed | The short text describes the object sufficiently | |
| 124 | 124 |
Number of read or archived NF-e batches: &1 / &2 | The short text describes the object sufficiently | |
| 125 | 125 |
Search criteria entries are insufficient | Space: object requires documentation | |
| 126 | 126 |
Search criteria entries are insufficient | Space: object requires documentation | |
| 127 | 127 |
Search criteria entries are insufficient | Space: object requires documentation | |
| 128 | 128 |
Search criteria entries are insufficient | Space: object requires documentation | |
| 129 | 129 |
No B2B transit: transporter CNPJ &1 is your own CNPJ | The short text describes the object sufficiently | |
| 130 | 130 |
No XML with type &1 for NF-e &2 available in archive | The short text describes the object sufficiently | |
| 131 | 131 |
Incorrect call: Parameter &1 must not be initial | The short text describes the object sufficiently | |
| 132 | 132 |
NF-e successfully sent to buyer; message &1 | The short text describes the object sufficiently | |
| 133 | 133 |
Cancellation NF-e successfully sent to buyer; message &1 | The short text describes the object sufficiently | |
| 134 | 134 |
NF-e successfully sent to transporter; message &1 | The short text describes the object sufficiently | |
| 135 | 135 |
Cancellation NF-e successfully sent to transporter; message &1 | The short text describes the object sufficiently | |
| 136 | 136 |
Error while sending NF-e to buyer: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 137 | 137 |
Error while sending NF-e to transporter: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 138 | 138 |
Error while sending cancellation NF-e to buyer: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 139 | 139 |
Error while sending cancellation NF-e to transporter: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 140 | 140 |
Service check: Status &3 for region &1, environment &2 (took &4 seconds) | The short text describes the object sufficiently | |
| 141 | 141 |
SCAN service check status &3 for region &1, environment &2 (took &4 sec.) | The short text describes the object sufficiently | |
| 142 | 142 |
Service check: Error &3 for region &1, environment &2 (took &4 seconds) | The short text describes the object sufficiently | |
| 143 | 143 |
SCAN service check: Error &3 for region &1, environment &2 (took &4 sec.) | The short text describes the object sufficiently | |
| 144 | 144 |
No NF-es exist for batch ID &1 | The short text describes the object sufficiently | |
| 145 | 145 |
NF-e status updated by function /XNFE/STATUS_SYNC_ERP | The short text describes the object sufficiently | |
| 146 | 146 |
ERP update error deleted by user &1 | The short text describes the object sufficiently | |
| 147 | 147 |
Service check terminated; region &1 is blocked by another process | The short text describes the object sufficiently | |
| 148 | 150 |
NF-e status check started to query events for NF-e &1 | The short text describes the object sufficiently | |
| 149 | 151 |
Error in XML transformation in tag &1 | The short text describes the object sufficiently | |
| 150 | 152 |
Error during transformation: &1&2 program: &3 path: &4 | The short text describes the object sufficiently | |
| 151 | 153 |
Error during transformation: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 152 | 154 |
Error during transformation: &1 &2 &3; path: &4 | The short text describes the object sufficiently | |
| 153 | 199 |
&1 entries deleted in table /XNFE/CTE_SRVSTA | The short text describes the object sufficiently | |
| 154 | 200 |
&2 entries deleted from table &1 | The short text describes the object sufficiently | |
| 155 | 201 |
Customizing table /XNFE/TSRV: Status query data not maintained | The short text describes the object sufficiently | |
| 156 | 202 |
Signature of document &1: &2 | The short text describes the object sufficiently | |
| 157 | 203 |
Please make entries in all fields | The short text describes the object sufficiently | |
| 158 | 204 |
Customizing Table /XNFE/TCUF: Status query data not defined | The short text describes the object sufficiently | |
| 159 | 205 |
No valid version found (table /XNFE/XMLVERSION) | The short text describes the object sufficiently | |
| 160 | 206 |
Customizing table /XNFE/GOVPAR: Communication partner not defined | The short text describes the object sufficiently | |
| 161 | 207 |
No version exists for message &1, layout &2 in table XMLVERSDET | The short text describes the object sufficiently | |
| 162 | 210 |
Error while reading table &1 | The short text describes the object sufficiently | |
| 163 | 211 |
Error while reading table &1 with ID &2 | The short text describes the object sufficiently | |
| 164 | 212 |
Status code of CT-e is empty | The short text describes the object sufficiently | |
| 165 | 213 |
Status code of batch is empty | The short text describes the object sufficiently | |
| 166 | 214 |
Customizing error: XML version for message type &1 is not defined | The short text describes the object sufficiently | |
| 167 | 215 |
Incorrect call: Value &1 in parameter &2 is not supported | The short text describes the object sufficiently | |
| 168 | 216 |
Type &2 acknowledgment &1 is not supported | The short text describes the object sufficiently | |
| 169 | 217 |
NF-e batch &1 is being processed by user &2 | The short text describes the object sufficiently | |
| 170 | 218 |
Batch has been processed; batch status code &1; process step: BATCH | The short text describes the object sufficiently | |
| 171 | 219 |
Table &2 has no entry for NF-e batch &1 | The short text describes the object sufficiently | |
| 172 | 220 |
Batch req. has been processed; batch status code &1; process step: BATSR | The short text describes the object sufficiently | |
| 173 | 221 |
There are no ERP update errors; processing was terminated | The short text describes the object sufficiently | |
| 174 | 222 |
Processing was terminated | The short text describes the object sufficiently | |
| 175 | 223 |
For 'Max. No. of Repeats', enter a value greater than zero (0) | The short text describes the object sufficiently | |
| 176 | 224 |
Enter a document number | The short text describes the object sufficiently | |
| 177 | 225 |
Only one document can be processed | The short text describes the object sufficiently | |
| 178 | 226 |
Error during proxy transformation: &1 | The short text describes the object sufficiently | |
| 179 | 227 |
Bad call of signature module: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 180 | 228 |
Internal error when calling signature module: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 181 | 229 |
Error during signing of XML file: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 182 | 230 |
Processing not permitted for NF-e &1 with process step &2 | The short text describes the object sufficiently | |
| 183 | 231 |
Error while sending the skip request: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 184 | 232 |
Processing not permitted for batch &1 with process step &2 | The short text describes the object sufficiently | |
| 185 | 233 |
Call has an error: a parameter for &1 &2 &3 must be filled | The short text describes the object sufficiently | |
| 186 | 240 |
Processing not possible; NF-e is marked for archiving | The short text describes the object sufficiently | |
| 187 | 241 |
Processing not possible; process step is not relevant | The short text describes the object sufficiently | |
| 188 | 242 |
NF-e status is outdated; refresh the screen | The short text describes the object sufficiently | |
| 189 | 243 |
NF-e &1 does not have a batch ID | The short text describes the object sufficiently | |
| 190 | 244 |
Batch status is outdated; refresh the screen | The short text describes the object sufficiently | |
| 191 | 245 |
NF-e status is no longer current; a cancellation event exists | The short text describes the object sufficiently | |
| 192 | 246 |
Temporary ERP update error; error is resolved by ERP update report prog. | The short text describes the object sufficiently | |
| 193 | 247 |
Batch &1 with status &2 cannot be finished | The short text describes the object sufficiently | |
| 194 | 248 |
Batch &1 with status &2 (error status &3) cannot be finished | The short text describes the object sufficiently | |
| 195 | 249 |
Technical error while finishing the batch process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 196 | 250 |
Batch number &1 has been ended; NF-e documents ready for status check | The short text describes the object sufficiently | |
| 197 | 251 |
Batch process cannot be finished | The short text describes the object sufficiently | |
| 198 | 252 |
Status code for NF-e &1 is missing in batch replay | The short text describes the object sufficiently | |
| 199 | 253 |
Status code for NF-e is blank | The short text describes the object sufficiently | |
| 200 | 254 |
Status category cannot be determined | The short text describes the object sufficiently | |
| 201 | 255 |
Incorrect call: Parameter &1 cannot be &2 | The short text describes the object sufficiently | |
| 202 | 256 |
Incorrect call: Parameter &1 must not be initial | The short text describes the object sufficiently | |
| 203 | 257 |
Error while creating GUID: &1 | The short text describes the object sufficiently | |
| 204 | 258 |
Unable to determine NF-e &1 with type &2 | The short text describes the object sufficiently | |
| 205 | 259 |
Unable to resend NF-e &1 with type &2 and B2B error &3 | The short text describes the object sufficiently | |
| 206 | 260 |
Cannot determine service status: Job &1 not running or no Customizing | The short text describes the object sufficiently | |
| 207 | 300 |
**************************** DB Layer *********************************** | The short text describes the object sufficiently | |
| 208 | 301 |
Error in global table &1 | The short text describes the object sufficiently | |
| 209 | 302 |
No NF-e found in internal memory for GUID &1 | The short text describes the object sufficiently | |
| 210 | 303 |
No table entry found for GUID &1 | The short text describes the object sufficiently | |
| 211 | 400 |
**************************** BATCH PROCESS ****************************** | The short text describes the object sufficiently | |
| 212 | 401 |
Batch &1 successfully created | The short text describes the object sufficiently | |
| 213 | 402 |
Batch &1 sent to authority | The short text describes the object sufficiently | |
| 214 | 403 |
Error while creating batch &1 | The short text describes the object sufficiently | |
| 215 | 404 |
Batch rejected by authority; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
| 216 | 405 |
Error while sending batch; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
| 217 | 406 |
Batch &1 successfully sent to authority; status code &2 received | The short text describes the object sufficiently | |
| 218 | 407 |
Technical error during batch query: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 219 | 408 |
Batch query sent to authority (batch ID &1); message ID &2 | The short text describes the object sufficiently | |
| 220 | 409 |
Technical error while receiving batch reply: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 221 | 410 |
Batch status request successful; status code of batch is &1 | The short text describes the object sufficiently | |
| 222 | 411 |
Batch still in process; status code of batch is &1 | The short text describes the object sufficiently | |
| 223 | 412 |
Max. number in batch query reached; batch still in proc.; status code &1 | The short text describes the object sufficiently | |
| 224 | 413 |
Max. number in batch query reached; status code &1; reason: &2 &3 | The short text describes the object sufficiently | |
| 225 | 414 |
Temporary error in batch query; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
| 226 | 415 |
Error in batch query; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
| 227 | 416 |
Batch rejected by authority; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
| 228 | 417 |
Error in determining batch status category; status code &1 | The short text describes the object sufficiently | |
| 229 | 418 |
SAP NetWeaver PI reports an error while sending NF-e batch &1 | The short text describes the object sufficiently | |
| 230 | 419 |
Batch process manually canceled by user &1 | The short text describes the object sufficiently | |
| 231 | 420 |
Technical error while finishing the batch process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 232 | 421 |
Batch &1 successfully sent to authority; message ID &2 | The short text describes the object sufficiently | |
| 233 | 500 |
*************************NFE PROCESS LAYER ****************************** | The short text describes the object sufficiently | |
| 234 | 501 |
Error while validating NF-e; XML file cannot be created | The short text describes the object sufficiently | |
| 235 | 502 |
NF-e successfully validated and transformed | The short text describes the object sufficiently | |
| 236 | 503 |
NF-e successfully signed | The short text describes the object sufficiently | |
| 237 | 504 |
Message is ready for sending to authority | The short text describes the object sufficiently | |
| 238 | 505 |
Status code &1 successfully transmitted to ERP | The short text describes the object sufficiently | |
| 239 | 506 |
Status code &1 of document &2 successfully transferred to ERP | The short text describes the object sufficiently | |
| 240 | 507 |
Temporary error while transferring status code &1 from document &2 to ERP | The short text describes the object sufficiently | |
| 241 | 508 |
Error while transferring status code &1 from document &2 to ERP | The short text describes the object sufficiently | |
| 242 | 509 |
Temporary error while transferring status code &1 to ERP | The short text describes the object sufficiently | |
| 243 | 510 |
Error while transferring status code &1 to ERP | The short text describes the object sufficiently | |
| 244 | 511 |
NF-e number skipping successfully transformed | The short text describes the object sufficiently | |
| 245 | 512 |
NF-e number skipping successfully signed | The short text describes the object sufficiently | |
| 246 | 513 |
Step is waiting for reply from authority | The short text describes the object sufficiently | |
| 247 | 514 |
Message is ready for dispatch to business partner | The short text describes the object sufficiently | |
| 248 | 515 |
Reply from authority contains an error: field &1 is empty | The short text describes the object sufficiently | |
| 249 | 516 |
Reply from authority has an error: log for NF-e &1 is missing | The short text describes the object sufficiently | |
| 250 | 517 |
Batch &1 status received; status code of NF-e equals &2 | The short text describes the object sufficiently | |
| 251 | 518 |
Message is ready for sending to ERP | The short text describes the object sufficiently | |
| 252 | 519 |
Batch &1 status received; status code &2; reason: &3 &4 | The short text describes the object sufficiently | |
| 253 | 520 |
NF-e B2B process successfully started | The short text describes the object sufficiently | |
| 254 | 521 |
Batch rejected by authority; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
| 255 | 522 |
Step was unsuccessful; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | |
| 256 | 523 |
Step successfully executed; NF-e status code equals &1 | The short text describes the object sufficiently | |
| 257 | 524 |
Status check queried at SEFAZ; process is waiting for reply; message &1 | The short text describes the object sufficiently | |
| 258 | 525 |
Status check failed: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 259 | 526 |
PI: Acknowledgment contains system errors; message ID &1 | The short text describes the object sufficiently | |
| 260 | 527 |
Status synchronization of ERP requested | The short text describes the object sufficiently | |
| 261 | 528 |
Reply to status query received; NF-e status code equals &1 | The short text describes the object sufficiently | |
| 262 | 529 |
Step execution was unsuccessful; &1 | The short text describes the object sufficiently | |
| 263 | 530 |
Unexpected cancellation of NF-e &1: Execute the status request again | The short text describes the object sufficiently | |
| 264 | 531 |
Unexpected status code &1 for NF-e | The short text describes the object sufficiently | |
| 265 | 532 |
Step is not relevant | The short text describes the object sufficiently | |
| 266 | 533 |
Step is waiting for execution of B2B process | The short text describes the object sufficiently | |
| 267 | 534 |
Next step &1 cannot be executed automatically | The short text describes the object sufficiently | |
| 268 | 535 |
Step successfully executed; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | |
| 269 | 536 |
Step successfully executed | The short text describes the object sufficiently | |
| 270 | 537 |
PI: Acknowledgment contains system error; &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 271 | 538 |
Cancellation event received; NF-e moved into cancellation process | The short text describes the object sufficiently | |
| 272 | 539 |
NF-e allocation (step &1, status &2) to new batch is not permitted | The short text describes the object sufficiently | |
| 273 | 540 |
NF-e is being allocated to a new batch (previous batch ID &1) | The short text describes the object sufficiently | |
| 274 | 541 |
Step successfully completed by user &1; NF-e status code &2 | The short text describes the object sufficiently | |
| 275 | 542 |
Problem in called ERP system: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 276 | 543 |
Status of process step successfully changed by user &1 | The short text describes the object sufficiently | |
| 277 | 544 |
Web Service is momentarily not available; NF-e will not be sent | The short text describes the object sufficiently | |
| 278 | 545 |
Close event sent; MDF-e waiting for response | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141107 | SAP |
| SAP Release Created in | 100 |
