SAP ABAP Message Class /XNFE/APPNFE (Outbound NF-e Messages)
Basic Data
Hierarchy
☛
SLL-NFE (Software Component) xNFE
⤷ SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷ /XNFE/APPNFE (Package) NF-e: Application Functions
⤷ SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷ /XNFE/APPNFE (Package) NF-e: Application Functions
Attributes
Message class | /XNFE/APPNFE | |
Short Description | Outbound NF-e Messages | |
Changed On | 20141107 | |
Last Changed At | 192303 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | *************************** GENERAL PROBLEMS **************************** | The short text describes the object sufficiently | |
2 | 001 | Error during update: &1 table &2 | The short text describes the object sufficiently | |
3 | 011 | NF-e &1 is currently being processed by user &2 | The short text describes the object sufficiently | |
4 | 012 | NF-e batch &1 is currently being processed by user &2 | The short text describes the object sufficiently | |
5 | 021 | No NF-e found in database for GUID &1 | The short text describes the object sufficiently | |
6 | 022 | NF-e &1 does not exist | The short text describes the object sufficiently | |
7 | 029 | No table entry found for GUID &1 | The short text describes the object sufficiently | |
8 | 031 | Error in global table &1 | The short text describes the object sufficiently | |
9 | 032 | No NF-e found in internal memory for GUID &1 | The short text describes the object sufficiently | |
10 | 033 | Process type &1 is not compatible with process flow | The short text describes the object sufficiently | |
11 | 034 | NF-e with type &1 is unknown; NF-e cannot be processed | The short text describes the object sufficiently | |
12 | 035 | Further processing or status change for NF-e is not possible | The short text describes the object sufficiently | |
13 | 036 | Error while merging and saving XML file | The short text describes the object sufficiently | |
14 | 037 | Structure is missing for merging of XML data | The short text describes the object sufficiently | |
15 | 038 | Error during XML merge (concatenate) | The short text describes the object sufficiently | |
16 | 039 | No RFC destination found for logical system &1 | The short text describes the object sufficiently | |
17 | 040 | Customizing error: XML version for message type &1 is not defined | The short text describes the object sufficiently | |
18 | 041 | Error while creating GUID: &1 | The short text describes the object sufficiently | |
19 | 043 | No batch found in internal memory for GUID &1 | The short text describes the object sufficiently | |
20 | 051 | Incorrect call: Parameter &1 must not be initial | The short text describes the object sufficiently | |
21 | 052 | Incorrect call: Parameter &1 cannot be &2 | The short text describes the object sufficiently | |
22 | 053 | Error while obtaining service status; region &1, vers. &2, issue type &3 | The short text describes the object sufficiently | |
23 | 054 | Call failed: Parameter &1 could not be determined | The short text describes the object sufficiently | |
24 | 060 | NF-e belongs to batch &1 | The short text describes the object sufficiently | |
25 | 100 | NF-e not authorized; NF-e cannot be sent | The short text describes the object sufficiently | |
26 | 101 | Step waiting for PI acknowledgment | The short text describes the object sufficiently | |
27 | 102 | Step successfully executed; no response requested from B2B partner | The short text describes the object sufficiently | |
28 | 103 | Step was executed successfully | The short text describes the object sufficiently | |
29 | 104 | Step was not executed successfully | The short text describes the object sufficiently | |
30 | 105 | Status &1 does not allow B2B transit for the NF-e | The short text describes the object sufficiently | |
31 | 106 | NF-e XML file successfully sent to NF-e recipient | The short text describes the object sufficiently | |
32 | 107 | NF-e XML file successfully sent to NF-e transporter | The short text describes the object sufficiently | |
33 | 108 | Processing not allowed for NF-e &1 with B2B scenario &2 | The short text describes the object sufficiently | |
34 | 109 | Document successfully signed with SSF application &1 | The short text describes the object sufficiently | |
35 | 110 | Message &1 was disregarded because the process step is not relevant | The short text describes the object sufficiently | |
36 | 111 | Status &1 of process step &2 does not permit sending the skipping request | The short text describes the object sufficiently | |
37 | 112 | Status check failed: &1 &2 &3, message ID &4 | The short text describes the object sufficiently | |
38 | 113 | Error while sending number skip: &1 &2 &3, message ID &4 | The short text describes the object sufficiently | |
39 | 114 | Number skip successfully sent to authority; message ID &1 | The short text describes the object sufficiently | |
40 | 115 | Status &1 of process step &2 does not allow B2B transit for NF-e | The short text describes the object sufficiently | |
41 | 116 | NF-e with message &1 sent to B2B partner | The short text describes the object sufficiently | |
42 | 117 | Data for NF-e skipping successfully transferred | The short text describes the object sufficiently | |
43 | 118 | Error during synchronous sending of NF-e: &1 &2 &3, message ID &4 | The short text describes the object sufficiently | |
44 | 119 | Error during synchronous sending of NF-e: &1 &2 &3, &4 | The short text describes the object sufficiently | |
45 | 152 | Search criteria entries are insufficient | Space: object requires documentation | |
46 | 159 | No XML exists in the database for NF-e &1; details not available | The short text describes the object sufficiently | |
47 | 160 | No archiving authorization for NF-es | The short text describes the object sufficiently | |
48 | 161 | Number of read/archived NF-es: &/& | The short text describes the object sufficiently | |
49 | 162 | Archiving completed | The short text describes the object sufficiently | |
50 | 163 | Number of read/archived batches: &/& | The short text describes the object sufficiently | |
51 | 200 | *************************** Batch Process ******************************* | The short text describes the object sufficiently | |
52 | 201 | Batch ID &1 not found | The short text describes the object sufficiently | |
53 | 202 | The status &1 of the last step &2 does not allow further processing | The short text describes the object sufficiently | |
54 | 203 | Batch &1 successfully created | The short text describes the object sufficiently | |
55 | 204 | Batch &1 ready for sending | The short text describes the object sufficiently | |
56 | 205 | XML version &1 is not supported | The short text describes the object sufficiently | |
57 | 206 | Batch &1 successfully sent to authority; message ID &2 | The short text describes the object sufficiently | |
58 | 207 | Batch &1 successfully sent to authority; status code &2 received | The short text describes the object sufficiently | |
59 | 208 | Error while sending batch; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
60 | 209 | Batch rejected by authority; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
61 | 210 | Error in determining batch status category; status code &1 | The short text describes the object sufficiently | |
62 | 211 | Batch request successfully sent to authority; message ID &1 | The short text describes the object sufficiently | |
63 | 212 | Time for batch request not yet reached | The short text describes the object sufficiently | |
64 | 213 | Batch &1 does not contain any documents | The short text describes the object sufficiently | |
65 | 214 | Step &1 is not relevant | The short text describes the object sufficiently | |
66 | 215 | Batch request successfully sent to authority; status code &1 received | The short text describes the object sufficiently | |
67 | 216 | Batch request rejected; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
68 | 217 | Batch still in process; status code of batch is &1 | The short text describes the object sufficiently | |
69 | 218 | NF-e log is not contained in reply to batch &1 | The short text describes the object sufficiently | |
70 | 219 | Maximum number of batch requests has been reached; status code &1 | The short text describes the object sufficiently | |
71 | 220 | Further processing of batch &1 is not possible | The short text describes the object sufficiently | |
72 | 221 | Send option &1 not supported; check your batch customizing settings | The short text describes the object sufficiently | |
73 | 222 | Batch &1 successfully sent to authority as a compressed file; msg. ID &2 | The short text describes the object sufficiently | |
74 | 250 | *************************** Analytics *********************************** | The short text describes the object sufficiently | |
75 | 251 | Enter the date | The short text describes the object sufficiently |
History
Last changed on/by | 20141107 | SAP | |
SAP Release Created in | 900 |