SAP ABAP Message Class /XNFE/APPB2B (Messages: NF-e Incoming)
Basic Data
Hierarchy
☛
SLL-NFE (Software Component) xNFE
⤷ SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷ /XNFE/APPB2B (Package) NF-e: Application Functions - Inbound
⤷ SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷ /XNFE/APPB2B (Package) NF-e: Application Functions - Inbound
Attributes
Message class | /XNFE/APPB2B | |
Short Description | Messages: NF-e Incoming | |
Changed On | 20141107 | |
Last Changed At | 192303 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 001 | Nota fiscal &1 is being processed by user &2 | The short text describes the object sufficiently | |
3 | 002 | Nota fiscal &1 already exists | The short text describes the object sufficiently | |
4 | 003 | Different business processes - &1 and &2 - determined for NF-e | The short text describes the object sufficiently | |
5 | 004 | Could not determine a unique business process for NF-e &1 | Space: object requires documentation | |
6 | 005 | No process flow found for business process &1 | The short text describes the object sufficiently | |
7 | 006 | Step &1 of proces &2 is not allowed for the NF-e document | The short text describes the object sufficiently | |
8 | 007 | Status &1 is not allowed for incoming NF-es | The short text describes the object sufficiently | |
9 | 008 | Error during determination of the business process for NF-e &1 | The short text describes the object sufficiently | |
10 | 009 | NF-e completed successfully | The short text describes the object sufficiently | |
11 | 010 | NF-e has not been assigned a logical system for further process handling | The short text describes the object sufficiently | |
12 | 011 | Could not determine a logical system for CNPJ &1 | The short text describes the object sufficiently | |
13 | 012 | No RFC destination could be determined for logical system &1 | The short text describes the object sufficiently | |
14 | 013 | The field for the CFOP code is blank in item &2 of NF-e &1 | The short text describes the object sufficiently | |
15 | 014 | Customizing: business process determ. not maintained for CFOP code &1 | The short text describes the object sufficiently | |
16 | 015 | Error during assignment of &1 | The short text describes the object sufficiently | |
17 | 016 | Process canceled | The short text describes the object sufficiently | |
18 | 017 | No NF-e found | The short text describes the object sufficiently | |
19 | 018 | Business process for NF-e &1 was determined independently of CFOP code | The short text describes the object sufficiently | |
20 | 019 | Text for reason for ending NF-e process cannot be blank | The short text describes the object sufficiently | |
21 | 020 | Implementation for process step &1 missing | Space: object requires documentation | |
22 | 021 | Status for process step &1 cannot be set manually | The short text describes the object sufficiently | |
23 | 022 | Status &1 cannot be set manually for step &2 in process &3 | The short text describes the object sufficiently | |
24 | 023 | Further processing or status change not possible for document &1 | The short text describes the object sufficiently | |
25 | 024 | Redetermination is not possible for this business process | Space: object requires documentation | |
26 | 025 | Business process &1 was redetermined | The short text describes the object sufficiently | |
27 | 026 | NF-e &1 cannot be processed (waiting for asynchronous reply) | The short text describes the object sufficiently | |
28 | 027 | NF-e &1 was rejected and cannot be set to completed | The short text describes the object sufficiently | |
29 | 028 | An error occurred in the called ERP system | Space: object requires documentation | |
30 | 029 | No table entry found for GUID &1 | Space: object requires documentation | |
31 | 030 | Error during assignment of a field symbol | The short text describes the object sufficiently | |
32 | 031 | No purchase orders were found | The short text describes the object sufficiently | |
33 | 032 | Error during RFC communication | The short text describes the object sufficiently | |
34 | 033 | Business process &1 is not suitable for the process flow | The short text describes the object sufficiently | |
35 | 034 | &1 | The short text describes the object sufficiently | |
36 | 035 | NF-e does not match the client role (test or live system) | The short text describes the object sufficiently | |
37 | 036 | The process step cannot be deactivated | The short text describes the object sufficiently | |
38 | 037 | Cancellation of NF-e was rejected | The short text describes the object sufficiently | |
39 | 038 | DANFE for NF-e &1 recorded in system | The short text describes the object sufficiently | |
40 | 039 | The process step cannot be executed automatically | Space: object requires documentation | |
41 | 040 | Process step &1 does not exist | The short text describes the object sufficiently | |
42 | 041 | The process step cannot be executed manually | The short text describes the object sufficiently | |
43 | 042 | Business process &1 cannot be used | The short text describes the object sufficiently | |
44 | 043 | Overall status reset after redetermination of business process | The short text describes the object sufficiently | |
45 | 044 | No authorization to change NF-e &1 | The short text describes the object sufficiently | |
46 | 045 | No authorization to execute process step &1 | The short text describes the object sufficiently | |
47 | 046 | No authorization to maintain NF-e &1 | The short text describes the object sufficiently | |
48 | 047 | No authorization to assign PO items for NF-e &1 | The short text describes the object sufficiently | |
49 | 048 | No authorization to modify simulation parameters | The short text describes the object sufficiently | |
50 | 049 | The NF-e was reset to its original process type | The short text describes the object sufficiently | |
51 | 050 | No authorization to enter DANFE for NF-e &1 in the system | The short text describes the object sufficiently | |
52 | 051 | Incorrect call: Parameter &1 must not be initial | The short text describes the object sufficiently | |
53 | 052 | Incorrect call: Parameter &1 cannot be &2 | The short text describes the object sufficiently | |
54 | 053 | No authorization to reject NF-e &1 | The short text describes the object sufficiently | |
55 | 054 | No authorization to reject cancellation of NF-e &1 | The short text describes the object sufficiently | |
56 | 055 | Cancellation message received - business process was stopped | The short text describes the object sufficiently | |
57 | 056 | The NF-e was moved to a cancellation process | The short text describes the object sufficiently | |
58 | 057 | Notification of rejection of NF-e sent | The short text describes the object sufficiently | |
59 | 058 | Notification could not be sent for NF-e &1 | Space: object requires documentation | |
60 | 059 | Incorrect call: Parameters &1 and &2 or &3 cannot be initial | The short text describes the object sufficiently | |
61 | 060 | The NF-e does not have a log or is not authorized | The short text describes the object sufficiently | |
62 | 061 | The cancellation NF-e does not contain a log or is not authorized | The short text describes the object sufficiently | |
63 | 062 | The cancellation NF-e does not fit the client role (test or live system) | The short text describes the object sufficiently | |
64 | 063 | No NF-e exists for the cancellation NF-e | The short text describes the object sufficiently | |
65 | 064 | Cancellation of NF-e &1 cannot be reset | The short text describes the object sufficiently | |
66 | 065 | The existing NF-e does not have a suitable type | The short text describes the object sufficiently | |
67 | 066 | The cancellation NF-e has a DANFE, but not an NF-e | The short text describes the object sufficiently | |
68 | 067 | No authorization to send notification for NF-e &1 | The short text describes the object sufficiently | |
69 | 068 | Cancellation of the NF-e was rejected by user &1 | The short text describes the object sufficiently | |
70 | 069 | NF-e &1 has already received a cancellation | The short text describes the object sufficiently | |
71 | 070 | Vendor notification was sent successfully | The short text describes the object sufficiently | |
72 | 071 | No XML exists in Workplace for NF-e &1; details not available | The short text describes the object sufficiently | |
73 | 072 | No XMLSTRING was passed on | The short text describes the object sufficiently | |
74 | 073 | The NF-e was manually set to completed: &1 &2 &3 &4 | The short text describes the object sufficiently | |
75 | 074 | The XML of the NF-e was received for the NF-e to cancel | The short text describes the object sufficiently | |
76 | 075 | The XML of the NF-e was received for the DANFE | The short text describes the object sufficiently | |
77 | 076 | Your query returned more than &1 items; display restricted to &1 | The short text describes the object sufficiently | |
78 | 077 | NF-e rejected: &1 &2 | The short text describes the object sufficiently | |
79 | 078 | Rejection of the NF-e was reset manually | The short text describes the object sufficiently | |
80 | 079 | The header status was set manually | The short text describes the object sufficiently | |
81 | 080 | Only your own CNPJ number can be used for local communication | Space: object requires documentation | |
82 | 081 | The name of the SSF application must lie in the customer namespace | The short text describes the object sufficiently | |
83 | 082 | NF-e &1 has already been written to an archive file | The short text describes the object sufficiently | |
84 | 083 | NF-e rejected | The short text describes the object sufficiently | |
85 | 084 | No matches for the specified search parameters | The short text describes the object sufficiently | |
86 | 085 | Documentation text not available in logon language &1 | The short text describes the object sufficiently | |
87 | 086 | Process type &1 does not exist | The short text describes the object sufficiently | |
88 | 087 | Notification of NF-e acceptance sent | The short text describes the object sufficiently | |
89 | 088 | Incorrect call: parameters &1 or &2 cannot be initial | The short text describes the object sufficiently | |
90 | 089 | PDF view of DANFE not available | The short text describes the object sufficiently | |
91 | 090 | Item category &1 is not allowed for business process category &2 | The short text describes the object sufficiently | |
92 | 091 | Component &1: Assigned PO does not match any main item | The short text describes the object sufficiently | |
93 | 092 | Tax rates &1 in document &2 and &3 do not match | The short text describes the object sufficiently | |
94 | 093 | Quantity-dependent taxes in documents &1 and &2 do not match | The short text describes the object sufficiently | |
95 | 094 | No suitable items found for comparison | The short text describes the object sufficiently | |
96 | 095 | No internal UoM determined for ISO code &1, item &2 | The short text describes the object sufficiently | |
97 | 096 | Enter CFOP code | The short text describes the object sufficiently | |
98 | 097 | The assignment of item &1 is incomplete | The short text describes the object sufficiently | |
99 | 098 | No authorization to display NF-e &1 | The short text describes the object sufficiently | |
100 | 099 | Requested XML file with type &1 is not available | The short text describes the object sufficiently | |
101 | 100 | **************************** DB ***************************************** | The short text describes the object sufficiently | |
102 | 101 | Error in global table &1 | The short text describes the object sufficiently | |
103 | 102 | No NF-e found in internal memory for GUID &1 | The short text describes the object sufficiently | |
104 | 103 | Incorrect call: Table &1 should only contain lines for GUID &2 | The short text describes the object sufficiently | |
105 | 104 | NF-e &1 does not exist in Fiscal Workplace | The short text describes the object sufficiently | |
106 | 105 | Could not determine any data for NF-e &1 | The short text describes the object sufficiently | |
107 | 106 | &1 is not a valid entry for the tax number (CNPJ) | Space: object requires documentation | |
108 | 107 | &1 is not a valid entry for the tax number (CPF) | Space: object requires documentation | |
109 | 108 | &1 is not a separate tax number (CNPJ) | The short text describes the object sufficiently | |
110 | 109 | No references could be determined | The short text describes the object sufficiently | |
111 | 110 | CFOP codes of the NF-e are not assigned to any business process | The short text describes the object sufficiently | |
112 | 111 | No archiving authorization for NF-es | The short text describes the object sufficiently | |
113 | 112 | Number of read/archived NF-es: &/& | The short text describes the object sufficiently | |
114 | 113 | Archiving completed | The short text describes the object sufficiently | |
115 | 114 | Rejection of NF-e &1 revoked | The short text describes the object sufficiently | |
116 | 115 | No NF-e list entry found for GUID &1 in internal memory | The short text describes the object sufficiently | |
117 | 116 | No NF-e list batch for GUID &1 found in internal memory | The short text describes the object sufficiently | |
118 | 117 | NF-e list download request batch &1 does not exist | The short text describes the object sufficiently | |
119 | 118 | No authorization for denying NF-e &1 | The short text describes the object sufficiently | |
120 | 119 | &1 is not a valid entry for a tax number (CNPJ or CPF) | The short text describes the object sufficiently | |
121 | 120 | Error while expanding NF-e &1 | The short text describes the object sufficiently | |
122 | 123 | Error during communication with authorities (negative acknowledgement) | The short text describes the object sufficiently | |
123 | 124 | PI: Acknowledgment contains system error; &1 &2 &3 &4 | The short text describes the object sufficiently | |
124 | 125 | Message digest &1 does not agree with computed message digest | The short text describes the object sufficiently | |
125 | 126 | PI: Acknowledgment contains system errors; message ID &1 | The short text describes the object sufficiently | |
126 | 127 | No XML exists in Workplace for CT-e &1; details not available | The short text describes the object sufficiently | |
127 | 128 | NF-e detail display supported only as of layout version 3.10 or higher | The short text describes the object sufficiently | |
128 | 130 | Error generating DANFE PDF preview | The short text describes the object sufficiently | |
129 | 131 | The entry &1 cannot be used as the value for activity &2 | The short text describes the object sufficiently | |
130 | 132 | Search help is not available; choose a valid activity first | The short text describes the object sufficiently | |
131 | 133 | Activity &1 cannot be chosen for process &2, process step &3 | The short text describes the object sufficiently | |
132 | 134 | Invalid status for transfer of XML file: Processing disallowed | The short text describes the object sufficiently | |
133 | 135 | No XML document for NF-e &1 has been downloaded yet from the authority | The short text describes the object sufficiently | |
134 | 136 | Error while assigning NF-e &1 | The short text describes the object sufficiently | |
135 | 137 | Setting the error status for NF-e entry &1 is not possible | The short text describes the object sufficiently | |
136 | 139 | Incorrect call: Parameters &1 and &2 must no be initial | The short text describes the object sufficiently | |
137 | 140 | Error reading mapping: &1, version &2, group &3 | The short text describes the object sufficiently | |
138 | 141 | Error reading mapping: &1, group &2 | The short text describes the object sufficiently | |
139 | 142 | Error reading structure &1 | The short text describes the object sufficiently | |
140 | 143 | Error reading mapping: &1, version &2 | The short text describes the object sufficiently | |
141 | 144 | Table &1 does not exist | The short text describes the object sufficiently | |
142 | 145 | Error while reading mapping data; no item data available | The short text describes the object sufficiently | |
143 | 146 | Error while preparing the data; group &1 cannot be loaded | The short text describes the object sufficiently | |
144 | 147 | Error while reading mapping assignments; no &1 XML version exists | The short text describes the object sufficiently | |
145 | 150 | Search criteria entries are insufficient | Space: object requires documentation | |
146 | 151 | Search criteria entries are insufficient | Space: object requires documentation | |
147 | 152 | Search criteria entries are insufficient | Space: object requires documentation | |
148 | 160 | No navigation information available for application &1 | The short text describes the object sufficiently | |
149 | 161 | Internal error: Related document cannot be loaded | The short text describes the object sufficiently | |
150 | 162 | A region cannot be determined for tax number &1 | Space: object requires documentation | |
151 | 170 | Type-&1 event created successfully | The short text describes the object sufficiently | |
152 | 171 | Type-&1 event not created successfully | The short text describes the object sufficiently | |
153 | 172 | No authorization for creating a type &1 event for NF-e &2 | The short text describes the object sufficiently | |
154 | 180 | 'Enter DANFE' step does not have the status 'OK' | The short text describes the object sufficiently | |
155 | 200 | Type &1 event not created; NF-e not authorized | The short text describes the object sufficiently | |
156 | 210 | NF-e was received again | The short text describes the object sufficiently | |
157 | 211 | NF-e rejected, can be overwritten: &1 &2 | The short text describes the object sufficiently | |
158 | 212 | NF-e overwritten | The short text describes the object sufficiently | |
159 | 213 | CNPJ number &1 of recipient is not your own tax number | The short text describes the object sufficiently | |
160 | 214 | Manually canceled; business process terminated | The short text describes the object sufficiently | |
161 | 215 | Enter at least one NF-e access key | The short text describes the object sufficiently | |
162 | 216 | Process for NF-e &1 can be continued in Logistics Worksplace only | The short text describes the object sufficiently | |
163 | 217 | Inbound NF-e &1 does not exist (Table /XNFE/INNFEHD) | The short text describes the object sufficiently | |
164 | 218 | Select the process type for the receipt of documents | The short text describes the object sufficiently | |
165 | 219 | Select the process type for the issue of documents | The short text describes the object sufficiently | |
166 | 300 | ****************************** NFE LIST ********************************* | The short text describes the object sufficiently | |
167 | 301 | Information about NF-e received | The short text describes the object sufficiently | |
168 | 302 | Information about NF-e cancellation received | The short text describes the object sufficiently | |
169 | 303 | Document is ready to be downloaded from authority | The short text describes the object sufficiently | |
170 | 304 | Document has been downloaded; checking by user is required | The short text describes the object sufficiently | |
171 | 305 | NF-e &1 denied | The short text describes the object sufficiently | |
172 | 306 | Received information about an NF-e that was rejected by the authority | The short text describes the object sufficiently | |
173 | 307 | Document unknown, but canceled | The short text describes the object sufficiently | |
174 | 308 | PI reports errors when sending the NF-e download query; message ID &1 | The short text describes the object sufficiently | |
175 | 309 | PI: Acknowledgment contains system error; &1 &2 &3 &4 | The short text describes the object sufficiently | |
176 | 310 | NF-e status check for cancellation event started | The short text describes the object sufficiently | |
177 | 311 | Processing of NF-e &1 with status &2, step &3 is not allowed | The short text describes the object sufficiently | |
178 | 312 | No XML document received from authority | The short text describes the object sufficiently | |
179 | 313 | Document denied; Operation Denial event created | The short text describes the object sufficiently | |
180 | 314 | Error while denying NF-e; Operation Denial event not created | The short text describes the object sufficiently | |
181 | 315 | Document &1 checked by user &2 | The short text describes the object sufficiently | |
182 | 316 | Document successfully accepted | The short text describes the object sufficiently | |
183 | 317 | Error while accepting the document: &1 &2 &3 &4 | The short text describes the object sufficiently | |
184 | 318 | Document not accepted; it already exists | The short text describes the object sufficiently | |
185 | 319 | Document with status code &1 received from authority | The short text describes the object sufficiently | |
186 | 320 | Document identified; status OK; inbound processing | The short text describes the object sufficiently | |
187 | 321 | Operation Acknowledgment event successfully created | The short text describes the object sufficiently | |
188 | 322 | Error while creating Operation Acknowledgment event: &1 &2 &3 &4 | The short text describes the object sufficiently | |
189 | 323 | Authorized "Operation Acknowledgment" event already exists | The short text describes the object sufficiently | |
190 | 324 | Operation Acknowledgment event created; error in process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
191 | 325 | Download of NF-e with query &1 started; waiting for asynchronous reply | The short text describes the object sufficiently | |
192 | 326 | XML download with status &1 rejected by authority; reason &2 &3 &4 | The short text describes the object sufficiently | |
193 | 327 | Operation not possible; the process can only deny the NF-e | The short text describes the object sufficiently | |
194 | 328 | Operation not possible; NF-e &1-&2 has meanwhile been received (via B2B) | The short text describes the object sufficiently | |
195 | 329 | "Operation Acknowledgment" event with status code &1 authorized | The short text describes the object sufficiently | |
196 | 330 | "Operation Acknowledgment" event with status code &1 rejected | The short text describes the object sufficiently | |
197 | 331 | "Operation Denied" event with status code &1 authorized | The short text describes the object sufficiently | |
198 | 332 | "Operation Denied" event with status code &1 rejected | The short text describes the object sufficiently | |
199 | 333 | Error while creating the "Operation Denied" event: &1 &2 &3 &4 | The short text describes the object sufficiently | |
200 | 334 | "Operation Denied" event created; error in the process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
201 | 335 | Authorized "Operation Denied" event already exists | The short text describes the object sufficiently | |
202 | 336 | Step &1 in status &2 is not possible for NF-e &3 | The short text describes the object sufficiently | |
203 | 337 | &1 entries deleted from table /xnfe/nfelisthd | The short text describes the object sufficiently | |
204 | 338 | &1 entries successfully deleted | The short text describes the object sufficiently | |
205 | 339 | &1 entries deleted from table /XNFE/NFELISTSTA | The short text describes the object sufficiently | |
206 | 340 | No authorization for querying the download of NF-e &1 | The short text describes the object sufficiently | |
207 | 341 | No authorization for transferring NF-e &1 | The short text describes the object sufficiently | |
208 | 342 | No authorization for denying NF-e &1 for CNPJ &2 | The short text describes the object sufficiently | |
209 | 343 | No authorization for querying events concerning NF-e &1 | The short text describes the object sufficiently | |
210 | 344 | Operation Acknowledgment event waiting for response from authority | The short text describes the object sufficiently | |
211 | 345 | NF-e &1 does not exist in the List and Download Monitor | The short text describes the object sufficiently | |
212 | 346 | NF-e &1 does not have a suitable status; XML download is not possible | The short text describes the object sufficiently | |
213 | 347 | Download of XML File to NF-e &1 has been triggered | The short text describes the object sufficiently | |
214 | 400 | Enter the name of the Web Dynpro component | The short text describes the object sufficiently | |
215 | 401 | Enter the name of the Web Dynpro interface | The short text describes the object sufficiently | |
216 | 402 | Enter the name of the start plug of the interface view | The short text describes the object sufficiently |
History
Last changed on/by | 20141107 | SAP | |
SAP Release Created in | 900 |