FS_CORR_POST - Korrespondenznachbearbeitung
The following messages are stored in message class FS_CORR_POST: Korrespondenznachbearbeitung.
It is part of development package FS_CORR_POST in software component CA-GTF-COR. This development package consists of objects that can be grouped under "Correspondence Postprocessing".
It is part of development package FS_CORR_POST in software component CA-GTF-COR. This development package consists of objects that can be grouped under "Correspondence Postprocessing".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Parameter &1 in method &2 has unallowed value &3 |
| 002 | Error occurred during control processing |
| 010 | There is already a parameter &2 for the PDF-based form &1 |
| 100 | Termination: Action could not be carried out |
| 101 | Structure &1 not defined in ABAP Dictionary |
| 102 | No active PDF-based print form &1 found |
| 103 | Interface &1 has invalid interface type &2 |
| 104 | Not possible to extract an application form from the data |
| 105 | System could not extract a PDF-based print form from the data |
| 106 | No interface set |
| 107 | Not possible to create data area of data type &1 |
| 108 | Class &2 for data transfer from form &1 does not exist |
| 109 | Not possible to create object of data type &1 |
| 110 | No active interface &1 found |
| 111 | An error occurred when executing method &1 (class &2) |
| 112 | No RFC destination specified for ADS |
| 113 | Error when creating tree of fields of the parameters |
| 114 | Parser &1 found an error |
| 115 | Method &1 is not defined in class &2 |
| 116 | No class is defined for data transfer from form &1 |
| 117 | No method is defined for data transfer from form &1 |
| 118 | No data conversion, since field &1/&2 is not defined in DDIC |
| 119 | No type-related data conversion possible for field &1/&2 |
| 201 | No user name entered |
| 202 | No folder area specified |
| 203 | Folder area &1 is not supported |
| 205 | No PDF-based form specified |
| 700 | *** Trace *** |
| 701 | Context element &1 was assigned to field &2 |
| 702 | Context element &1 could not be assigned to field &2 |
| 703 | Tag &1 from the XML data was not found in the context |
| 704 | No data area is assigned to tag &1 from the XML data in the context |
| 705 | No table data area is assigned to loop tag &1 in the context |
| 706 | No table row was found in the context for loop tag &1 |
| 707 | No row data area is assigned to loop data tag &1 in the context |
| 708 | Initial table row was not added to loog tag &1 |
| 709 | Form &1 identified |
| 710 | Value of tag &2(&1) is initial |
| 711 | Value &3 of tag &2(&1) applied |
| 712 | Table row &1 was added to loop tag &2 |
| 713 | Node for form not found |
| 714 | Value for form not found |
| 715 | A data area was assigned to the parameter &1 |
| 716 | A data area was assigned to the global date &1 |
| 794 | ----- Determine Trace Form ----- |
| 795 | ----- Process Trace Context ----- |
| 796 | ----- Process Trace Interface ----- |
| 797 | ----- Extract Trace Data ----- |
| 798 | ***** Start of Trace ***** |
| 799 | ***** End of Trace ***** |
| 800 | *** Tests *** |
| 801 | Address change of business partner &1 was saved |
| 802 | No address change available for business partner &1 |
| 803 | No new address data available |
| 804 | The address change for business partner &1 was simulated successfully |