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