NFE_CLOUD - Cloud NF-e Messages
The following messages are stored in message class NFE_CLOUD: Cloud NF-e Messages.
It is part of development package J1BNFE_OUT_CLOUD in software component CA-GTF-CSC-EDO-BR. This development package consists of objects that can be grouped under "Cloud NF-e Outbound".
It is part of development package J1BNFE_OUT_CLOUD in software component CA-GTF-CSC-EDO-BR. This development package consists of objects that can be grouped under "Cloud NF-e Outbound".
Message Nr ▲ | Message Text |
|---|---|
| 000 | The document &1 could not be read. Report an incident to LOD-LH-NFE. |
| 001 | Business place &1 &2 could not be read. Report an incident to LOD-LH-NFE. |
| 002 | An error occurred while the system tried to reach cloud services. |
| 003 | Could not generate request ID. Please try again later. |
| 004 | Review your implementation of BAdI NFE_CLOUD_REQUEST_EXTENSION, group &1. |
| 005 | An entry with the same data already exists. You can't create a new one. |
| 006 | &1 &2 was processed with status &3. |
| 007 | There are no pending documents for this selection. |
| 008 | Processing company code &1, business place &2, model &3, type &4. |
| 009 | Document model &1 is currently not supported. |
| 010 | Action &1 in &2 &3 is not recognized for status update. |
| 011 | &1 &2 is still in process by partner or tax authorities. |
| 012 | Error in the processing of request with HTTP status &1. |
| 013 | Result &1 in &2 &3 is not recognized for status update. |
| 014 | Invalid &1 in communication with cloud. Review communication settings. |
| 015 | File not found. Report an incident to LOD-LH-NFE. |
| 016 | Destination was created. |
| 017 | Destination was changed. |
| 018 | Destination was deleted. |
| 019 | Event &1 is not supported. The file could not be downloaded. |
| 020 | No authorization to &1. |
| 021 | Error while opening screen. Please try again later. |
| 022 | No extension values were found. |
| 023 | Could not authorize/connect to RFC Destination &1. Details: &2. |
| 024 | Test to RFC Destination &1 is not possible/not supported. Details: &2. |
| 025 | No electronic document data was found for processing. |
| 026 | Choose a valid upload source (GRC NF-e, BAdI, or local file). |
| 027 | Could not display result. |
| 028 | The file exceeds the limit size of 512 KB and cannot be uploaded. |
| 029 | The file was uploaded. |
| 030 | Select the entry and manually upload the corresponding file. |
| 031 | Fill one of the mandatory fields: Document Number, Created On, Access Key |
| 032 | Cannot process events for the "GRC NF-e" upload source. |
| 033 | The BAdI hasn't returned any files. |
| 034 | The file was processed in test run and is ready to be uploaded. |
| 035 | Document &1 is still in process by tax authorities. |
| 036 | Document &1 not found in SAP Document Compliance outbound nota fiscal. |
| 037 | Invalid &1 value &2. |
| 038 | SEFAZ server is inactive: document number &1 can't be numbered and sent |
| 039 | Create the OAuth2 Profile &1 in transaction OA2C_CONFIG and try again. |
| 040 | Enter a different document model. This report doesn't support model &1. |
| 041 | &1 &2 &3 &4 |
| 042 | Could not cancel document &1. For more information, see the log column. |