/SAPCE/IURU - Russia: error messages IS-U
The following messages are stored in message class /SAPCE/IURU: Russia: error messages IS-U.
It is part of development package /SAPCE/IURU in software component FI-LOC-UT. This development package consists of objects that can be grouped under "IS-U localization Russia".
It is part of development package /SAPCE/IURU in software component FI-LOC-UT. This development package consists of objects that can be grouped under "IS-U localization Russia".
Message Nr ▲ | Message Text |
---|---|
001 | RAO UES classifier &1 cannot be found |
002 | IESD &1 cannot be found |
003 | Local office &2 of IESD &1 cannot be found |
006 | OKOGU Code(7 Digit) is missing;Run the report /SAPCE/IURU_OKOGU_7_ENH. |
022 | |
100 | Number of entries selected for printing:_______ &1 |
101 | Number of successfully processed entries:____ &1 |
102 | Number of failed selections:________________&1 |
103 | Number of Payment Forms printed:___________&1 |
104 | Number of Print Documents updated:_________&1 |
105 | |
112 | Business Partner was not found &1 |
113 | Bank data for Business Partner &1 was not found in table BUT0BK |
116 | Contract Account &1 was not found for Business Partner &2 |
118 | Own Bank data was not found in table &1 |
122 | Payment condition missing for CA &1 |
123 | Document &1 is not related to the Own Bank &2 |
126 | Printing of Payment Request canceled due to error: &1 &2 |
127 | Update of table ERDK failed. Print Document &1 |
128 | Print Document header &1 updated with payment type &2 |
133 | Profile allocation for the installation &1 has gaps. |
158 | |
159 | |
160 | |
175 | You are not authorized to run the report |
176 | An error occurs in SQL statement; not possible to update DB table &1 |
177 | An error triggered in Customer BAdI call; Process skipped to next table |
178 | Customer BAdI /SAPCE/IURU_OKOGU_MIGR_BADI will be called |
179 | &1 &2 &3 &4 |
180 | Select at least one DB table for migration |
181 | Start processing DB table &1; migration of OKOGU field |
182 | DB table &1 not expected to be migrated; process skipped to next table |
183 | Old field &1 not found in DB table &2; migration not needed |
184 | New field &1 not found in DB table &2; migration not possible |
185 | DB table &1 with key &2 and value '&3' is locked by user &4 |
186 | SQL injection error - dynamic access to table &1 field &2 |
187 | SQL injection error - database table &1 not expected |
188 | An error occurs in SQL statement; not possible to select from DB table &1 |
189 | Number of selected lines from DB table &1: &2 |
190 | Line key: '&1' - Cannot be updated; new OKOGU 7 field not empty (&2) |
191 | Line key: '&1' - New OKOGU 7 field copied from old OKOGU 5 (&2) |
192 | Line key: '&1' - No OKOGU 7 found in Customizing for old OKOGU 5 (&2) |
193 | Line key: '&1' - New OKOGU 7 field (&2) set for old OKOGU 5 (&3) |
194 | Line key: '&1' - Multiple OKOGU 7 found in Cust. for old OKOGU 5 (&2) |
195 | Total updated OKOGU 7 fields in DB table &1: &2 |
196 | Number of migrated OKOGU 7 fields in DB table &1: &2 |
197 | Number of errors in migration of OKOGU 7 fields in DB table &1: &2 |
198 | SQL injection error - dynamic access to table &1 with value &2 |
200 | Forem flag has invalid value (Should be empty or X) |
201 | RAO UES classifier has invalid type |
250 | Installation &1 could not be found |
300 | Voltage level &1 is not permissible for division &2 |
500 | Enter date in synchronization with Per. repl.year |
501 | Invalid date |
502 | Year is not correct |
503 | Press 'ENTER' to calculate next replacement year |
600 | Rate &1 cannot be assigned to vol. level &2. It is already assigned to &3 |
601 | Could not determine voltage level for logical register number &1 &2 - &3 |
602 | Voltage levels of log. reg. &1 and &2 do not match (Timeslice &3 - &4) |
603 | Voltage levels of register &1 and &2 differ for period &3 - &4 |
604 | Could not determine votlage level for register &1 period &2 - &3 |