SAP ABAP Message Class /XNFE/APPCTE (Messages for CT-e Outbound)
Basic Data
Hierarchy
☛
SLL-NFE (Software Component) xNFE
⤷
SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷
/XNFE/APPCTE (Package) CT-e: Application Functions

⤷

⤷

Attributes
Message class | ![]() |
/XNFE/APPCTE |
Short Description | ![]() |
Messages for CT-e Outbound |
Changed On | ![]() |
20141107 |
Last Changed At | ![]() |
192115 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | ![]() |
Error determining the business process for CT-e &1 | The short text describes the object sufficiently | |
2 | ![]() |
CT-e &1 is being edited by user &2 | The short text describes the object sufficiently | |
3 | ![]() |
CT-e &1 already exists | The short text describes the object sufficiently | |
4 | ![]() |
Insufficient authorization to display all CT-es | The short text describes the object sufficiently | |
5 | ![]() |
Error while creating GUID: &1 | The short text describes the object sufficiently | |
6 | ![]() |
Error while creating batch ID; see long text | Space: object requires documentation | |
7 | ![]() |
CT-e could not be determined for batch ID &1 | The short text describes the object sufficiently | |
8 | ![]() |
Incorrect call: Parameter &1 must not be initial | The short text describes the object sufficiently | |
9 | ![]() |
Incorrect call: Parameter &1 cannot be &2 | The short text describes the object sufficiently | |
10 | ![]() |
XML data cannot be determined for CT-e &1 | The short text describes the object sufficiently | |
11 | ![]() |
Error while determining XML version (CT-e &1) | The short text describes the object sufficiently | |
12 | ![]() |
******************************* DB LAYER ******************************** | The short text describes the object sufficiently | |
13 | ![]() |
Error in global table &1 | The short text describes the object sufficiently | |
14 | ![]() |
No CT-e found in internal memory for GUID &1 | The short text describes the object sufficiently | |
15 | ![]() |
CT-e &1 does not exist | The short text describes the object sufficiently | |
16 | ![]() |
No batch found in internal memory for GUID &1 | The short text describes the object sufficiently | |
17 | ![]() |
CT-e batch &1 is currently being processed by user &2 | The short text describes the object sufficiently | |
18 | ![]() |
CT-e status check for query of events concerning CT-e &1 has started | The short text describes the object sufficiently | |
19 | ![]() |
**************************** PROCESS LAYER ****************************** | The short text describes the object sufficiently | |
20 | ![]() |
The overall status &1 of the CT-e does not allow further processing | The short text describes the object sufficiently | |
21 | ![]() |
The status &1 of the last step &2 does not allow further processing | The short text describes the object sufficiently | |
22 | ![]() |
No data can be detected for CT-e &1 | The short text describes the object sufficiently | |
23 | ![]() |
The B2B overall status &1 of the CT-e does not allow further processing | The short text describes the object sufficiently | |
24 | ![]() |
The B2B status &1 of the last step &2 does not allow further processing | The short text describes the object sufficiently | |
25 | ![]() |
CT-e successfully validated and transformed | The short text describes the object sufficiently | |
26 | ![]() |
Error during validation of CT-e; XML file cannot be created | The short text describes the object sufficiently | |
27 | ![]() |
Status &2 of process step &1 does not allow overwriting of the CT-e | The short text describes the object sufficiently | |
28 | ![]() |
CT-e cancellation successfully transformed | The short text describes the object sufficiently | |
29 | ![]() |
CT-e number skipping successfully transformed | The short text describes the object sufficiently | |
30 | ![]() |
CT-e successfully signed with SSF application &1 | The short text describes the object sufficiently | |
31 | ![]() |
CT-e cancellation successfully signed with SSF application &1 | The short text describes the object sufficiently | |
32 | ![]() |
Error during signing of XML file | The short text describes the object sufficiently | |
33 | ![]() |
Message is ready for sending to authority | Space: object requires documentation | |
34 | ![]() |
CT-e number skipping successfully signed with SSF application &1 | The short text describes the object sufficiently | |
35 | ![]() |
Error while sending the cancellation: &1 &2 &3 &4 | The short text describes the object sufficiently | |
36 | ![]() |
CT-e cancellation successfully sent; status code &1 received | The short text describes the object sufficiently | |
37 | ![]() |
Status &1 of process step &2 does not permit sending of cancellation | The short text describes the object sufficiently | |
38 | ![]() |
Error while sending number skipping request: &1 &2 &3 &4 | The short text describes the object sufficiently | |
39 | ![]() |
Status &1 of process step &2 does not permit sending the skipping request | The short text describes the object sufficiently | |
40 | ![]() |
CT-e number skipping request successfully sent; status code &1 received | The short text describes the object sufficiently | |
41 | ![]() |
Message is ready for sending to ERP | The short text describes the object sufficiently | |
42 | ![]() |
Message is ready for dispatch to business partner | The short text describes the object sufficiently | |
43 | ![]() |
CT-e B2B process successfully launched | The short text describes the object sufficiently | |
44 | ![]() |
CT-e with message &1 has been sent to B2B partner | The short text describes the object sufficiently | |
45 | ![]() |
Cancellation CT-e with message &1 has been sent to B2B partner | The short text describes the object sufficiently | |
46 | ![]() |
Cancellation CT-e B2B process successfully launched | The short text describes the object sufficiently | |
47 | ![]() |
CT-e successfully sent internally | The short text describes the object sufficiently | |
48 | ![]() |
Cancellation CT-e successfully sent internally | The short text describes the object sufficiently | |
49 | ![]() |
Technical error in B2B process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
50 | ![]() |
Status &2 of process step &1 does not permit cancellation of CT-e | The short text describes the object sufficiently | |
51 | ![]() |
Error during determination of RFC destination for logical system &1 | The short text describes the object sufficiently | |
52 | ![]() |
Error during back-end status transfer: &1 &2 &3 &4 | The short text describes the object sufficiently | |
53 | ![]() |
Status &1 of process step &2 does not allow for back-end status transfers | The short text describes the object sufficiently | |
54 | ![]() |
Status &1 of process step &2 does not permit a CT-e status check | The short text describes the object sufficiently | |
55 | ![]() |
Error during CT-e status check: &1 &2 &3 &4 | The short text describes the object sufficiently | |
56 | ![]() |
CT-e status check successfully sent; status code &1 received | The short text describes the object sufficiently | |
57 | ![]() |
Error during internal dispatch of CT-e | The short text describes the object sufficiently | |
58 | ![]() |
Error during internal dispatch of cancellation CT-e | The short text describes the object sufficiently | |
59 | ![]() |
B2B communication deactivated (status set to OK = 01) | The short text describes the object sufficiently | |
60 | ![]() |
CT-e number skipping has already been processed | The short text describes the object sufficiently | |
61 | ![]() |
Cancellation CT-e has already been processed | The short text describes the object sufficiently | |
62 | ![]() |
Technical error while finishing the batch process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
63 | ![]() |
Finishing batch process is not permitted for step &1 with status &2 | The short text describes the object sufficiently | |
64 | ![]() |
**************************** TRANSFORMATION ***************************** | The short text describes the object sufficiently | |
65 | ![]() |
Mapping error: Error while mapping the structure &1 | The short text describes the object sufficiently | |
66 | ![]() |
Mapping error: Error while mapping the field &1 in structure &2 | The short text describes the object sufficiently | |
67 | ![]() |
Mapping error: Field &1 in structure &2 must be filled | The short text describes the object sufficiently | |
68 | ![]() |
Error during transformation: &1 &2 &3 &4 | The short text describes the object sufficiently | |
69 | ![]() |
Mapping error: One of the parameters &1, &2, &3 must be filled | The short text describes the object sufficiently | |
70 | ![]() |
Mapping error: Error while mapping the structure &1; parameter &2 missing | The short text describes the object sufficiently | |
71 | ![]() |
**************************** BATCH PROCESS ****************************** | The short text describes the object sufficiently | |
72 | ![]() |
Error while creating the CT-e batch: &1 &2 &3 &4 | The short text describes the object sufficiently | |
73 | ![]() |
CT-e added to batch ID &1 | The short text describes the object sufficiently | |
74 | ![]() |
No CT-e found for batch ID &1 (GUID &2) | The short text describes the object sufficiently | |
75 | ![]() |
Batch ID &1 not found | The short text describes the object sufficiently | |
76 | ![]() |
CT-e of batch ID &1 is blocked | The short text describes the object sufficiently | |
77 | ![]() |
Technical error while sending batch: &1 &2 &3 &4 | The short text describes the object sufficiently | |
78 | ![]() |
Batch &1 successfully sent to authority; status code &2 received | The short text describes the object sufficiently | |
79 | ![]() |
Batch rejected by authority; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
80 | ![]() |
Technical error during batch query: &1 &2 &3 &4 | The short text describes the object sufficiently | |
81 | ![]() |
Batch status request successful; status code of batch is &1 | The short text describes the object sufficiently | |
82 | ![]() |
Error during batch status query; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | |
83 | ![]() |
Batch still in process; status code of batch is &1 | The short text describes the object sufficiently | |
84 | ![]() |
Batch &1 status received; status code of CT-e is &2 | The short text describes the object sufficiently | |
85 | ![]() |
Batch &1 successfully created | The short text describes the object sufficiently | |
86 | ![]() |
Batch &1 ready for sending | The short text describes the object sufficiently | |
87 | ![]() |
Batch &1 ready for batch status query | The short text describes the object sufficiently | |
88 | ![]() |
Batch &1 status received; status code &2; reason: &3 &4 | The short text describes the object sufficiently | |
89 | ![]() |
Error during batch status request; run a CT-e status check | The short text describes the object sufficiently | |
90 | ![]() |
Reply from authority contains an error: field &1 is empty | The short text describes the object sufficiently | |
91 | ![]() |
Status code &1 of document &2 successfully transferred to ERP | The short text describes the object sufficiently | |
92 | ![]() |
Temporary error while transferring status code &1 from document &3 to ERP | The short text describes the object sufficiently | |
93 | ![]() |
Error while transferring status code &1 from document &3 to ERP | The short text describes the object sufficiently | |
94 | ![]() |
Technical error while transferring status code &1 from document &3 to ERP | The short text describes the object sufficiently | |
95 | ![]() |
Status code &1 successfully transmitted to ERP | The short text describes the object sufficiently | |
96 | ![]() |
Technical error during cancellation: &1 &2 &3 &4 | The short text describes the object sufficiently | |
97 | ![]() |
Reply to cancellation request received: status code is &1 | The short text describes the object sufficiently | |
98 | ![]() |
Reply to number skipping received; status code is &1 | The short text describes the object sufficiently | |
99 | ![]() |
The status &1 of process step &2 does not allow sending of the batch | The short text describes the object sufficiently | |
100 | ![]() |
The status &1 of process step &2 does not allow a batch query | The short text describes the object sufficiently | |
101 | ![]() |
The current status &1 of process step &2 does not allow this action | The short text describes the object sufficiently | |
102 | ![]() |
Error during proxy call: &1 &2 &3 &4 | The short text describes the object sufficiently | |
103 | ![]() |
Error while sending batch: &1 &2 &3 &4 | The short text describes the object sufficiently | |
104 | ![]() |
Error during batch query: &1 &2 &3 &4 | The short text describes the object sufficiently | |
105 | ![]() |
Status code of batch is empty | The short text describes the object sufficiently | |
106 | ![]() |
Batch process manually canceled by user &1 | The short text describes the object sufficiently | |
107 | ![]() |
Error during proxy call: &1 | The short text describes the object sufficiently | |
108 | ![]() |
Reply from authority contains an error: log for CT-e &1 is missing | The short text describes the object sufficiently | |
109 | ![]() |
Error while sending batch; status code &1; reason: &2 &3 &4 | The short text describes the object sufficiently | |
110 | ![]() |
Status code of CT-e is empty | The short text describes the object sufficiently | |
111 | ![]() |
Number of CT-e batches read / archived: & / & | The short text describes the object sufficiently | |
112 | ![]() |
PI: Acknowledgment contains system error; message ID &1 | The short text describes the object sufficiently | |
113 | ![]() |
XML version &1 is not supported | The short text describes the object sufficiently | |
114 | ![]() |
PI: Acknowledgment contains system error; &1 &2 &3 &4 | The short text describes the object sufficiently | |
115 | ![]() |
Batch ID &1 is blocked | The short text describes the object sufficiently | |
116 | ![]() |
Message ID of Process Integration (PI/XI) is initial | The short text describes the object sufficiently | |
117 | ![]() |
Temporary error during status transfer from document &1 to ERP: &2 &3 &4 | The short text describes the object sufficiently | |
118 | ![]() |
Error during status transfer from document &1 to ERP: &2 &3 &4 | The short text describes the object sufficiently |
History
Last changed on/by | ![]() |
20141107 | SAP |
SAP Release Created in | 900 |