SAP ABAP Message Class /XNFE/APP_STATUS_ERP (Messages for Communication with ERP)
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
Attributes
Message class /XNFE/APP_STATUS_ERP
Short Description Messages for Communication with ERP  
Changed On 20141107 
Last Changed At 192303 
Messages
# Message Message Short Text Documentation status Authorization check
1 000 ****************** NF-e messages from NFE to ERP ************************ The short text describes the object sufficiently
2 001 Document &1 is already in process The short text describes the object sufficiently
3 002 NF-e &1 already exists The short text describes the object sufficiently
4 003 Document &1: Customizing error: Key storage data not maintained The short text describes the object sufficiently
5 004 Document &1: Customizing error: Official version not maintained The short text describes the object sufficiently
6 005 Document &1: Customizing error: XML version not maintained The short text describes the object sufficiently
7 006 Document &1: An error occurred during signing The short text describes the object sufficiently
8 007 Validation info: Field &1 in check &2 is filled The short text describes the object sufficiently
9 008 Validation error: Field (&1) &2, &3 The short text describes the object sufficiently
10 009 No entry for NF-e &1 exists in table /XNFE/NFE_HIST The short text describes the object sufficiently
11 010 Problem in called ERP system (message class &1, number &2) The short text describes the object sufficiently
12 011 No RFC destination found for logical system &1 The short text describes the object sufficiently
13 012 Document &1: XML version &2 is not supported The short text describes the object sufficiently
14 013 NF-e status &1 does not allow cancellation/skipping The short text describes the object sufficiently
15 014 Document &1: Error during proxy transformation The short text describes the object sufficiently
16 015 Table &2 has no entry for NF-e &1 The short text describes the object sufficiently
17 016 NF-e &1 already archived The short text describes the object sufficiently
18 017 NF-e &1 is still being processed The short text describes the object sufficiently
19 018 No cancellation event found for NF-e &1 The short text describes the object sufficiently
20 019 Cancellation event already exists for NF-e &1 The short text describes the object sufficiently
21 020 Cancellation event for NF-e &1 is still being processed The short text describes the object sufficiently
22 021 Error while calling the NF-e status check The short text describes the object sufficiently
23 022 Reply from authority is invalid: Log number is blank or not numeric The short text describes the object sufficiently
24 023 Reply from authority is invalid: Cancellation event is missing The short text describes the object sufficiently
25 024 Status code &1 received (temporary SEFAZ error); try again later The short text describes the object sufficiently
26 025 Error updating table &1 The short text describes the object sufficiently
27 026 Error while merging and writing the XML file (NF-e &1) The short text describes the object sufficiently
28 027 Error while reading document &1 The short text describes the object sufficiently
29 028 SEFAZ database contains a cancellation event for NF-e &1 The short text describes the object sufficiently
30 029 SEFAZ database does not contain a cancellation event for NF-e &1 The short text describes the object sufficiently
31 030 Function does not support a 'classic' cancellation The short text describes the object sufficiently
32 031 Error in function &1 (RC = &2) The short text describes the object sufficiently
33 032 Function not allowed for skipped NF-es The short text describes the object sufficiently
34 033 Document &1; error in global table The short text describes the object sufficiently
35 034 Error while creating GUID: &1 The short text describes the object sufficiently
36 035 Error during status update The short text describes the object sufficiently
37 036 Status &2 of process step &1 does not allow overwriting of the NF-e The short text describes the object sufficiently
38 037 System environm. &1 (test or update mode) does not agree with Customizing The short text describes the object sufficiently
39 038 ERP RFC version &1 not supported The short text describes the object sufficiently
40 039 NF-e XML version &1 not supported The short text describes the object sufficiently
41 100 **************** NF-e & CT-e messages from ERP to NFE ******************* The short text describes the object sufficiently
42 101 Incorrect NF-e document status for document &1 The short text describes the object sufficiently
43 102 Document number and access key are blank The short text describes the object sufficiently
44 103 No table entry exists for document number &1 / access key &2 The short text describes the object sufficiently
45 104 Log number is required for NF-e &1 The short text describes the object sufficiently
46 105 NF-e document status &1 is not defined The short text describes the object sufficiently
47 106 No status code received for NF-e &1 The short text describes the object sufficiently
48 107 Doc. status &3 not allowed for NF-e &1 with system comm. status &2 The short text describes the object sufficiently
49 108 Current status &1 does not allow follow-on status &2 for document &3 The short text describes the object sufficiently
50 109 New system communication status &1 is not allowed for previous &2 The short text describes the object sufficiently
51 110 Log number is not numeric The short text describes the object sufficiently
52 111 DB error during insert of NF-e with &1, &2, &3 in J_1BNFE_HISTORY The short text describes the object sufficiently
53 112 Nota fiscal &1 not found The short text describes the object sufficiently
54 113 Table &1 is locked by another user The short text describes the object sufficiently
55 114 New system communication status &1 not allowed for message status &2 The short text describes the object sufficiently
56 116 XML for nota fiscal &1 has already been processed The short text describes the object sufficiently
57 200 ****************** Messages from NFE to ERP (CT-e) ********************** The short text describes the object sufficiently
58 201 Mapping error: Error while mapping the structure &1 The short text describes the object sufficiently
59 202 Mapping error: Error while mapping the field &1 in structure &2 The short text describes the object sufficiently
60 203 Mapping error: Field &1 in structure &2 must be filled The short text describes the object sufficiently
61 204 Error during XML transformation: &1, &2, &3 The short text describes the object sufficiently
62 205 Mapping error: One of the parameters &1, &2, &3 must be filled The short text describes the object sufficiently
63 206 Mapping error: Error while mapping the structure &1; parameter &2 missing The short text describes the object sufficiently
64 207 Mapping error: Value &1 in field &2 of structure &3 is not permitted The short text describes the object sufficiently
65 208 Mapping error: No partner found for structure &1 The short text describes the object sufficiently
66 209 Mapping error: No tax found for structure &1 The short text describes the object sufficiently
67 210 Mapping error: No rows found in table &1 The short text describes the object sufficiently
68 211 Mapping error: No texts found for structure &1 The short text describes the object sufficiently
69 212 Mapping error: No values found for structure &1 The short text describes the object sufficiently
70 213 Status &2 of process step &1 does not allow overwriting of the CT-e The short text describes the object sufficiently
71 214 Customizing error: XML version for message type &1 is not defined The short text describes the object sufficiently
72 215 Validation error: field &1: &2. Content is invalid (&3) The short text describes the object sufficiently
73 216 Validation error: field &1: &2. Negative value is invalid (&3) The short text describes the object sufficiently
74 217 Validation error: ID does not have the format of the authority (&1) The short text describes the object sufficiently
75 218 System environm. &1 (test or update mode) does not agree with Customizing The short text describes the object sufficiently
76 219 Customizing error: Connected government system is not defined The short text describes the object sufficiently
77 220 CT-e &1 is being edited by user &2 The short text describes the object sufficiently
78 221 CT-e &1 already exists The short text describes the object sufficiently
79 222 ERP RFC version &1 not supported The short text describes the object sufficiently
80 223 Mode of transport &1 not supported The short text describes the object sufficiently
81 224 Combination of XML version of CT-e &1 and modal &2 not supported The short text describes the object sufficiently
82 225 CT-e XML version &1 not supported The short text describes the object sufficiently
83 226 Validation error: Field &1: Field no. &2 must be filled The short text describes the object sufficiently
84 236 NF-e will be moved into the skipping process The short text describes the object sufficiently
85 237 NF-e will be moved into the issueing process The short text describes the object sufficiently
86 238 NF-e will be moved into the cancellation process The short text describes the object sufficiently
87 250 Mapping error: Parameter &1 must be filled The short text describes the object sufficiently
88 251 Mapping error: No values found for row ID &1 in parameter &2 The short text describes the object sufficiently
89 252 Status &1 of process step &2 does not permit sending the skipping request The short text describes the object sufficiently
90 253 Status &1 of step &2 does not allow acceptance of cancellation rejection The short text describes the object sufficiently
91 400 **** Do not use higher numbers! ERP needs them for event messages ***** The short text describes the object sufficiently
92 600 *********************** Messages from MDFe to ERP ********************** The short text describes the object sufficiently
93 601 Status &2 of process step &1 does not permit overwriting of MDF-e The short text describes the object sufficiently
94 602 MDF-e &1 already exists The short text describes the object sufficiently
95 603 Process type &1 is not compatible with process flow The short text describes the object sufficiently
History
Last changed on/by 20141107  SAP 
SAP Release Created in   100