SAP ABAP Message Class /XNFE/APPMDFE (Outbound MDF-e Messages)
Basic Data
Hierarchy
☛
SLL-NFE (Software Component) xNFE
⤷ SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷ /XNFE/APPMDFE (Package) MDF-e: Application Functions
⤷ SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷ /XNFE/APPMDFE (Package) MDF-e: Application Functions
Attributes
Message class | /XNFE/APPMDFE | |
Short Description | Outbound MDF-e Messages | |
Changed On | 20141107 | |
Last Changed At | 192401 |
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 | 002 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
4 | 011 | MDF-e &1 is currently being processed by user &2 | The short text describes the object sufficiently | |
5 | 021 | No MDF-e found in database for GUID &1 | The short text describes the object sufficiently | |
6 | 022 | MDF-e &1 does not exist | The short text describes the object sufficiently | |
7 | 031 | Error in global table &1 | The short text describes the object sufficiently | |
8 | 032 | No MDF-e found for GUID &1 in internal memory | The short text describes the object sufficiently | |
9 | 034 | MDF-e with type &1 is unknown; MDF-e cannot be processed | The short text describes the object sufficiently | |
10 | 036 | Error while merging and saving XML file | The short text describes the object sufficiently | |
11 | 037 | Structure is missing for merging of XML data | The short text describes the object sufficiently | |
12 | 038 | Error during XML merge (concatenate) | The short text describes the object sufficiently | |
13 | 039 | No RFC destination found for logical system &1 | The short text describes the object sufficiently | |
14 | 041 | Error while creating GUID: &1 | The short text describes the object sufficiently | |
15 | 046 | No authorization for processing MDF-e &1 | The short text describes the object sufficiently | |
16 | 051 | Incorrect call: Parameter &1 must not be initial | The short text describes the object sufficiently | |
17 | 052 | Incorrect call: Parameter &1 cannot be &2 | The short text describes the object sufficiently | |
18 | 053 | Close event not authorized | The short text describes the object sufficiently | |
19 | 054 | Problem in called ERP system: &1 &2 &3 &4 | The short text describes the object sufficiently | |
20 | 055 | Incorrect call: Parameters &1 and &2 or &3 cannot be initial | The short text describes the object sufficiently | |
21 | 056 | Error reading mapping: &1, version &2 | The short text describes the object sufficiently | |
22 | 057 | Error reading mapping: &1, version &2, group &3 | The short text describes the object sufficiently | |
23 | 058 | Status code for MDF-e ist blank | The short text describes the object sufficiently | |
24 | 059 | Error during proxy transformation: &1 | The short text describes the object sufficiently | |
25 | 060 | Incorrect call: Value &1 in parameter &2 is not supported | The short text describes the object sufficiently | |
26 | 071 | No XML file exists in workplace for MDF-e &1; details unavailable | The short text describes the object sufficiently | |
27 | 110 | Message &1 was disregarded because the process step is not relevant | The short text describes the object sufficiently | |
28 | 111 | Unable to determine feeder system for updating the status | The short text describes the object sufficiently | |
29 | 150 | MDF-e status check for request of events for MDF-e &1 has started | The short text describes the object sufficiently | |
30 | 159 | No XML for MDF-e &1 found in database; no details available | The short text describes the object sufficiently | |
31 | 200 | *************************** Batch Process ******************************* | The short text describes the object sufficiently | |
32 | 213 | Batch &1 does not contain any MDF-es | The short text describes the object sufficiently | |
33 | 300 | Technical error while finishing the batch process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
34 | 301 | Finishing batch process is not permitted for step &1 with status &2 | The short text describes the object sufficiently | |
35 | 400 | ***********************MDFE PROCESS LAYER ****************************** | The short text describes the object sufficiently | |
36 | 401 | Reply from authority contains an error: field &1 is empty | The short text describes the object sufficiently | |
37 | 402 | Unexpected status code &1 for MDF-e | The short text describes the object sufficiently | |
38 | 403 | Error during validation of MDF-e; XML file cannot be created | The short text describes the object sufficiently | |
39 | 404 | MDF-e successfully validated and transformed | The short text describes the object sufficiently | |
40 | 405 | Further processing or status change not possible for document &1 | The short text describes the object sufficiently | |
41 | 406 | Step is waiting for reply from authority | The short text describes the object sufficiently | |
42 | 407 | Process step is deactivated (status was set to OK = 01) | The short text describes the object sufficiently | |
43 | 408 | Next step &1 cannot be executed automatically | The short text describes the object sufficiently | |
44 | 409 | Implementation for process step &1 missing | The short text describes the object sufficiently | |
45 | 410 | Document successfully signed with SSF application &1 | The short text describes the object sufficiently | |
46 | 411 | MDF-e allocated to new batch (previous batch ID &1) | The short text describes the object sufficiently | |
47 | 412 | Message is ready for sending to authority | The short text describes the object sufficiently | |
48 | 413 | Step executed successfully; MDF-e status code is &1 | The short text describes the object sufficiently | |
49 | 414 | Step was unsuccessful; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | |
50 | 415 | Step successfully executed; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | |
51 | 416 | Status code &1 successfully transmitted to ERP | The short text describes the object sufficiently | |
52 | 417 | Status code &1 of document &2 successfully transferred to SAP ERP | The short text describes the object sufficiently | |
53 | 418 | Temporary error while transferring status code &1 to SAP ERP | The short text describes the object sufficiently | |
54 | 419 | Temporary error while transferring status code &1 from document &2 to ERP | The short text describes the object sufficiently | |
55 | 420 | Error while transferring status code &1 to SAP ERP | The short text describes the object sufficiently | |
56 | 421 | Error while transferring status code &1 from document &2 to SAP ERP | The short text describes the object sufficiently | |
57 | 422 | MDF-e-allocation (step &1, status &2) to new batch not permitted | The short text describes the object sufficiently | |
58 | 423 | Status of process step successfully changed by user &1 | The short text describes the object sufficiently | |
59 | 424 | Status check failed: &1 &2 &3, message ID &4 | The short text describes the object sufficiently | |
60 | 425 | Status check queried at SEFAZ; process is waiting for reply; message &1 | The short text describes the object sufficiently | |
61 | 426 | Cancellation event received; NF-e moved into cancellation process | The short text describes the object sufficiently | |
62 | 427 | MDF-e process has been switched | The short text describes the object sufficiently | |
63 | 428 | Cancellation event received; MDF-e moved into cancellation process | The short text describes the object sufficiently | |
64 | 429 | Close event sent; MDF-e waiting for response | The short text describes the object sufficiently | |
65 | 430 | Message ID of process integration (PI/XI) is initial | The short text describes the object sufficiently | |
66 | 535 | Batch process manually canceled by user &1 | The short text describes the object sufficiently |
History
Last changed on/by | 20141107 | SAP | |
SAP Release Created in | 900 |