SAP ABAP Message Class /XNFE/APPEVENTSTEPS (Messages for Event Process Steps)
Basic Data
Hierarchy
☛
SLL-NFE (Software Component) xNFE
⤷
SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring
⤷
/XNFE/APPEVENT (Package) Events: Application Functions
⤷
⤷
Attributes
| Message class | /XNFE/APPEVENTSTEPS | |
| Short Description | Messages for Event Process Steps | |
| Changed On | 20141107 | |
| Last Changed At | 192115 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Step is not relevant for event | The short text describes the object sufficiently | ||
| 2 | Import parameter event GUID is missing | The short text describes the object sufficiently | ||
| 3 | Event is not authorized and, therefore, cannot be dispatched | The short text describes the object sufficiently | ||
| 4 | Step was executed successfully | The short text describes the object sufficiently | ||
| 5 | Step was not executed successfully | The short text describes the object sufficiently | ||
| 6 | Event of the type &1 is not permitted | The short text describes the object sufficiently | ||
| 7 | Sequence number does not match | The short text describes the object sufficiently | ||
| 8 | Event in NF-e List Workplace does not send a message to partners | The short text describes the object sufficiently | ||
| 9 | *************************Header Action*********************************** | The short text describes the object sufficiently | ||
| 10 | Event refreshed | The short text describes the object sufficiently | ||
| 11 | Event received again | The short text describes the object sufficiently | ||
| 12 | *************************Step ADDTOBAT*********************************** | The short text describes the object sufficiently | ||
| 13 | Step is waiting for reply from authority | The short text describes the object sufficiently | ||
| 14 | Event belongs to batch &1 | The short text describes the object sufficiently | ||
| 15 | Step was successful; event status code equals &1 | The short text describes the object sufficiently | ||
| 16 | Step was unsuccessful; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | ||
| 17 | No version for layout &1 was found in table TXMLVERS | The short text describes the object sufficiently | ||
| 18 | Status check queried at SEFAZ; process is waiting for reply; message &1 | The short text describes the object sufficiently | ||
| 19 | Step successfully executed; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | ||
| 20 | *************************Step RECBATCH*********************************** | The short text describes the object sufficiently | ||
| 21 | Step is waiting for reply from authority | The short text describes the object sufficiently | ||
| 22 | *************************Step RESPOPCO*********************************** | The short text describes the object sufficiently | ||
| 23 | Event is not authorized; therefore, the step is incorrect | The short text describes the object sufficiently | ||
| 24 | Step was executed successfully | The short text describes the object sufficiently | ||
| 25 | *************************Step EVENTSIN*********************************** | The short text describes the object sufficiently | ||
| 26 | Event successfully signed with SSF application &1 | The short text describes the object sufficiently | ||
| 27 | No suitable entry in Customizing available for CNPJ &1 | The short text describes the object sufficiently | ||
| 28 | Event could not be signed | The short text describes the object sufficiently | ||
| 29 | *************************Step SIGNVALI*********************************** | The short text describes the object sufficiently | ||
| 30 | Signature successfully validated | The short text describes the object sufficiently | ||
| 31 | Signature error in validation | The short text describes the object sufficiently | ||
| 32 | *************************Step ERPUPDAT*********************************** | The short text describes the object sufficiently | ||
| 33 | No RFC destination found for logical system &1 | The short text describes the object sufficiently | ||
| 34 | Status code &1 for cancel event (GUID &2) successfully transferred to ERP | The short text describes the object sufficiently | ||
| 35 | Error during status transfer of cancel event (GUID &1) to ERP: &2 &3 &4 | The short text describes the object sufficiently | ||
| 36 | Technical error during status transfer &1 of Cancel Event (GUID &2)to ERP | The short text describes the object sufficiently | ||
| 37 | *************************Step AUTHEVNT*********************************** | The short text describes the object sufficiently | ||
| 38 | Event has been authorized with status &1 | The short text describes the object sufficiently | ||
| 39 | Event is not authorized | The short text describes the object sufficiently | ||
| 40 | Status check failed; status code &1, reason: &2 &3 &4 | The short text describes the object sufficiently | ||
| 41 | Status check failed; reply from authority does not contain the event | The short text describes the object sufficiently | ||
| 42 | Event does not exist at authority; current status code &1 applied | The short text describes the object sufficiently | ||
| 43 | Event does not exist at authority; batch status code &1 applied | The short text describes the object sufficiently | ||
| 44 | Status check: NF-e rejected by authority; status code &1 | The short text describes the object sufficiently | ||
| 45 | Status check: CT-e rejected by authority with status code &1 | The short text describes the object sufficiently | ||
| 46 | *************************Step B2BOUTBD*********************************** | The short text describes the object sufficiently | ||
| 47 | Step waiting for reply from B2B partner | The short text describes the object sufficiently | ||
| 48 | Step successfully executed; no reply from B2B partner has been requested | The short text describes the object sufficiently | ||
| 49 | *************************Step EVCTAUTH ********************************** | The short text describes the object sufficiently | ||
| 50 | Event authorized with status &1 | The short text describes the object sufficiently | ||
| 51 | Event rejected with status &1; reason: &2 &3 &4 | The short text describes the object sufficiently | ||
| 52 | Step waiting for authorization of event | The short text describes the object sufficiently | ||
| 53 | *************************Step WAUTHBAT ********************************** | The short text describes the object sufficiently | ||
| 54 | Event processed for authorization by background job | The short text describes the object sufficiently | ||
| 55 | *************************Step EVTRGB2B ********************************** | The short text describes the object sufficiently | ||
| 56 | Step is irrelevant; event is not authorized | The short text describes the object sufficiently |
History
| Last changed on/by | 20141107 | SAP | |
| SAP Release Created in | 900 |