SAP ABAP Message Class FDM_MIRROR (Mirror System Messages)
Basic Data
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷
FIN-FSCM-COL-AR (Application Component) Accounts Receivable Accounting Process Integration
⤷
FDM_AR_COLL_MIRROR (Package) SAP Collections Management - Data from Non-SAP System
SAP_FIN (Software Component) SAP_FIN⤷
FIN-FSCM-COL-AR (Application Component) Accounts Receivable Accounting Process Integration⤷
FDM_AR_COLL_MIRROR (Package) SAP Collections Management - Data from Non-SAP System 
Attributes
| Message class |  |
FDM_MIRROR |
| Short Description |  |
Mirror System Messages |
| Changed On |  |
20100310 |
| Last Changed At |  |
181748 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  001 |
FI transaction data already exists | The short text describes the object sufficiently | |
| 2 | 002 |
Sample company code TMPL has already been created | The short text describes the object sufficiently | |
| 3 | 003 |
Field &1 has not been filled | The short text describes the object sufficiently | |
| 4 | 004 |
Make entries in all fields | The short text describes the object sufficiently | |
| 5 | 005 |
Target company code &1 already exists | The short text describes the object sufficiently | |
| 6 | 006 |
CoCd &1 of original system &2 has already been transferred to CoCd &3 | The short text describes the object sufficiently | |
| 7 | 007 |
A system with ID &1 already exists | The short text describes the object sufficiently | |
| 8 | 008 |
Logical name &1 for an original system has already been registered | Space: object requires documentation | |
| 9 | 009 |
There is already a similar address (&1) for a non-SAP system | The short text describes the object sufficiently | |
| 10 | 010 |
Error when updating table &1 | The short text describes the object sufficiently | |
| 11 | 011 |
FI customer master data already exists | The short text describes the object sufficiently | |
| 12 | 012 |
FI customer master contact persons already exist | The short text describes the object sufficiently | |
| 13 | 013 |
Sample company code TMPL has been created successfully | The short text describes the object sufficiently | |
| 14 | 014 |
Error &1 occurred when creating the sample company code | Space: object requires documentation | |
| 15 | 015 |
Application &1 activated | The short text describes the object sufficiently | |
| 16 | 016 |
An error occurred when activating application &1 | The short text describes the object sufficiently | |
| 17 | 017 |
The buffer has been reset | The short text describes the object sufficiently | |
| 18 | 018 |
Error changing table &1 | The short text describes the object sufficiently | |
| 19 | 019 |
Error inserting in table &1 | The short text describes the object sufficiently | |
| 20 | 020 |
Error when deleting in table &1 | The short text describes the object sufficiently | |
| 21 | 021 |
There is no entry &2 in table &1 | The short text describes the object sufficiently | |
| 22 | 022 |
Entry &2 in table &1 already exists | The short text describes the object sufficiently | |
| 23 | 023 |
Company code &1 has been deleted | The short text describes the object sufficiently | |
| 24 | 024 |
Company code &1 could not be deleted | The short text describes the object sufficiently | |
| 25 | 025 |
Company code TMPL has been activated | The short text describes the object sufficiently | |
| 26 | 026 |
Global parameters for company code TMPL have been adapted | The short text describes the object sufficiently | |
| 27 | 027 |
The tax category of the G/L accounts account sheets has been adapted | The short text describes the object sufficiently | |
| 28 | 028 |
The Customizing settings could not be saved | Space: object requires documentation | |
| 29 | 029 |
Function not supported in a substitute system | The short text describes the object sufficiently | |
| 30 | 030 |
The number range object customer has been adapted | The short text describes the object sufficiently | |
| 31 | 031 |
Automatic write off not supported in substitute system | Space: object requires documentation | |
| 32 | 032 |
The substitute system is currently being set up | Space: object requires documentation | |
| 33 | 033 |
Client settings have been adapted | The short text describes the object sufficiently | |
| 34 | 034 |
New company code &1 is currently being created by user &2 | The short text describes the object sufficiently | |
| 35 | 035 |
The document change rules have been adapted | The short text describes the object sufficiently | |
| 36 | 036 |
A new system with ID &1 is currently being created by user &2 | The short text describes the object sufficiently | |
| 37 | 037 |
A new system with log. system &1 is currently being created by user &2 | The short text describes the object sufficiently | |
| 38 | 038 |
Table &1 has been updated | The short text describes the object sufficiently | |
| 39 | 039 |
Company code &1 has been created successfully | The short text describes the object sufficiently | |
| 40 | 040 |
The 'Transfer of data from original system' function is not active | The short text describes the object sufficiently | |
| 41 | 041 |
There is no data to transfer | The short text describes the object sufficiently | |
| 42 | 042 |
Having deleted irrelevant data, there is no more data to transfer | The short text describes the object sufficiently | |
| 43 | 043 |
The message type of the IDoc is not &1 | The short text describes the object sufficiently | |
| 44 | 044 |
Partner profiles: the partner category of the sender system is not &1 | The short text describes the object sufficiently | |
| 45 | 045 |
The wizard has been successfully exited | The short text describes the object sufficiently | |
| 46 | 046 |
An error occurred while Customizing new company code &1 | Space: object requires documentation | |
| 47 | 047 |
The substitute system has been set up successfully | The short text describes the object sufficiently | |
| 48 | 048 |
Client has already been set up as substitute system | The short text describes the object sufficiently | |
| 49 | 049 |
Case types cannot be determined | Space: object requires documentation | |
| 50 | 050 |
System meets the requirements for substitute systems | The short text describes the object sufficiently | |
| 51 | 051 |
Logical system &1 does not have an RFC target | The short text describes the object sufficiently | |
| 52 | 052 |
Function &1 does not exist in original system (with logical system &2) | The short text describes the object sufficiently | |
| 53 | 053 |
Account group for substitute system has been created | The short text describes the object sufficiently | |
| 54 | 054 |
Payment methods for substitute system have been created | The short text describes the object sufficiently | |
| 55 | 055 |
Tab. FDM_ESYS_MIRROR: entries for original system &1 missing | The short text describes the object sufficiently | |
| 56 | 056 |
Tab. FDM_ESYS_MIRROR: entries for original system &1 incorrect | The short text describes the object sufficiently | |
| 57 | 057 |
Tab. FDM_ESYS_MIRROR: logical system &1 does not exist | The short text describes the object sufficiently | |
| 58 | 058 |
Tab. FDM_ESYS_MIRROR: logical system &1 exists more than once | The short text describes the object sufficiently | |
| 59 | 059 |
Tab. FDM_ESYS_MIRROR: system & has maintained EXT_LOGSYS and EXT_HOME | The short text describes the object sufficiently | |
| 60 | 060 |
Difference reasons for susbstitute system have been created | The short text describes the object sufficiently | |
| 61 | 061 |
Dunning block for substitute system has been created | The short text describes the object sufficiently | |
| 62 | 062 |
Payment block for susbstitute system has been created | The short text describes the object sufficiently | |
| 63 | 063 |
Enter a valid interval | The short text describes the object sufficiently | |
| 64 | 064 |
The controlling area assignment for company code &1 is active | The short text describes the object sufficiently | |
| 65 | 065 |
Number range objects for controlling area &1 have been deleted | The short text describes the object sufficiently | |
| 66 | 066 |
Controlling areas have been deleted | The short text describes the object sufficiently | |
| 67 | 067 |
Controlling areas could not be deleted | The short text describes the object sufficiently | |
| 68 | 068 |
New system &1 has been registered | Space: object requires documentation | |
| 69 | 069 |
Company code assignment has been registered | Space: object requires documentation | |
| 70 | 070 |
Process code for partner profile has been adapted | The short text describes the object sufficiently | |
| 71 | 071 |
Tab. FDM_COMP_MIRROR: assignment data for company code &1 missing | The short text describes the object sufficiently | |
| 72 | 072 |
Tab. FDM_COMP_MIRROR: assignment data for company code &1 incorrect | The short text describes the object sufficiently | |
| 73 | 073 |
Tab. FDM_COMP_MIRROR: external key (&1, &2, &3) not present | The short text describes the object sufficiently | |
| 74 | 074 |
Tab. FDM_COMP_MIRROR: external key (&1, &2, &3) is present more than once | The short text describes the object sufficiently | |
| 75 | 075 |
Master data exists for controlling area &1 | The short text describes the object sufficiently | |
| 76 | 076 |
Master data for controlling area has been deleted | The short text describes the object sufficiently | |
| 77 | 077 |
Master data/transaction data controlling area &1 has not been deleted | The short text describes the object sufficiently | |
| 78 | 078 |
You are not authorized to delete the controlling areas | The short text describes the object sufficiently | |
| 79 | 079 |
Transaction data for controlling area &1 has been deleted | The short text describes the object sufficiently | |
| 80 | 080 |
SAP system &1 has company codes with differing master data systems | The short text describes the object sufficiently | |
| 81 | 081 |
Tab. FDM_CUST_MIRROR: assignment data for customer &1 missing | The short text describes the object sufficiently | |
| 82 | 082 |
Tab. FDM_CUST_MIRROR: assignment data for customer &1 incorrect | The short text describes the object sufficiently | |
| 83 | 083 |
Tab. FDM_CUST_MIRROR: external key (&1, &2, &3) not present | The short text describes the object sufficiently | |
| 84 | 084 |
Tab. FDM_CUST_MIRROR: external key (&1, &2, &3) exists more than once | The short text describes the object sufficiently | |
| 85 | 085 |
Customizing for Dispute Management updated | Space: object requires documentation | |
| 86 | 086 |
Customizing for Collections Management updated | Space: object requires documentation | |
| 87 | 087 |
The controlling area assignment for &1 could not be deleted | The short text describes the object sufficiently | |
| 88 | 088 |
Controlling area assignment for &1 has been deleted | The short text describes the object sufficiently | |
| 89 | 089 |
Account determination for automatic postings has not been adapted | The short text describes the object sufficiently | |
| 90 | 090 |
Account determination for automatic postings has been adapted | The short text describes the object sufficiently | |
| 91 | 091 |
Tab. FDM_CONT_MIRROR: assignment data for contact person &1 missing | The short text describes the object sufficiently | |
| 92 | 092 |
Tab. FDM_CONT_MIRROR: assignment data for contact person &1 incorrect | The short text describes the object sufficiently | |
| 93 | 093 |
Tab. FDM_CONT_MIRROR: external key (&1, &2, &3) not present | The short text describes the object sufficiently | |
| 94 | 094 |
Tab. FDM_CONT_MIRROR: external key (&1, &2, &3) exists more than once | The short text describes the object sufficiently | |
| 95 | 095 |
Global company code &1 already exists in table &2 | The short text describes the object sufficiently | |
| 96 | 096 |
Global company codes have been deleted | The short text describes the object sufficiently | |
| 97 | 098 |
A new global company code &1 is currently being created by user &2 | The short text describes the object sufficiently | |
| 98 | 099 |
Table FDM_STAT_MIRROR: sample company code not maintained | The short text describes the object sufficiently | |
| 99 | 100 |
Table FDM_STAT_MIRROR: account group for customers not maintained | The short text describes the object sufficiently | |
| 100 | 101 |
Payment method &1 is not available for country &2 | The short text describes the object sufficiently | |
| 101 | 102 |
Distribution model for logical system &1 not maintained | Space: object requires documentation | |
| 102 | 103 |
There are no payment methods in original system &1 for country &2 | The short text describes the object sufficiently | |
| 103 | 104 |
Company code 0001 does not exist | The short text describes the object sufficiently | |
| 104 | 105 |
You are not authorized to set up the system | Space: object requires documentation | |
| 105 | 106 |
No RFC destination could be determined for logical system &1 | Space: object requires documentation | |
| 106 | 107 |
Business function FIN_FSCM_INTEGRATION is not active | Space: object requires documentation | |
| 107 | 108 |
Dunning procedure for substitute system has been created | The short text describes the object sufficiently | |
| 108 | 109 |
Validation (no manual document entry) entered for &1 | The short text describes the object sufficiently | |
| 109 | 110 |
Customer (&1, &2) from system &3 is currently being processed by user &4 | The short text describes the object sufficiently | |
| 110 | 111 |
Contact person (&1, &2) from syst. &3 is being processed by user &4 | The short text describes the object sufficiently | |
| 111 | 112 |
Account group &1 already exists | The short text describes the object sufficiently | |
| 112 | 113 |
Number range overlaps with existing number ranges | The short text describes the object sufficiently | |
| 113 | 114 |
Conversion of payment methods from a non-SAP system (&1) is not possible | The short text describes the object sufficiently | |
| 114 | 115 |
No number range interval could be determined | The short text describes the object sufficiently | |
| 115 | 116 |
Structure with the name &1 does not exist | The short text describes the object sufficiently | |
| 116 | 117 |
The structure specified is not of type &1 | The short text describes the object sufficiently | |
| 117 | 118 |
Not all of the structure fields can be set to the value &1 | The short text describes the object sufficiently | |
| 118 | 119 |
Inbound parameter values (combination) either unsuitable or not allowed | The short text describes the object sufficiently | |
| 119 | 120 |
Function module &1 exited with errors | The short text describes the object sufficiently | |
| 120 | 121 |
Internal error: required inbound parameter does not have a value | The short text describes the object sufficiently | |
| 121 | 122 |
Internal error: field &1 is not contained in table/structure &2 | The short text describes the object sufficiently | |
| 122 | 123 |
Data record not found in table &1 | The short text describes the object sufficiently | |
| 123 | 124 |
Data inconsistency in table &1 | The short text describes the object sufficiently | |
| 124 | 125 |
Field &1 in table / structure &2 does not have a value | The short text describes the object sufficiently | |
| 125 | 126 |
Fields required in the IDoc do not have a value | The short text describes the object sufficiently | |
| 126 | 127 |
System &1 does not manage customer master data A segment | The short text describes the object sufficiently | |
| 127 | 128 |
System &1 does not manage customer master data B segment | The short text describes the object sufficiently | |
| 128 | 129 |
System &1 does not manage either customer master data A or B segment | The short text describes the object sufficiently | |
| 129 | 130 |
Entry for the logical system of the original system missing | The short text describes the object sufficiently | |
| 130 | 131 |
Entry for the customers to be selected missing | The short text describes the object sufficiently | |
| 131 | 132 |
Entry for the company code to be selected is missing | The short text describes the object sufficiently | |
| 132 | 133 |
Entry for the contact person to be selected missing | The short text describes the object sufficiently | |
| 133 | 134 |
No data found for customer (&1, &2) in system &3 | The short text describes the object sufficiently | |
| 134 | 135 |
Customer (&1, &2) in system &3 is one-time customer and not transferred | The short text describes the object sufficiently | |
| 135 | 136 |
The maximum number (&1) of customers to be selected has been reached | The short text describes the object sufficiently | |
| 136 | 137 |
The customer types to be selected are below the lower limit & | The short text describes the object sufficiently | |
| 137 | 138 |
The customers to be selected are not greater than the lower limit & | The short text describes the object sufficiently | |
| 138 | 139 |
Contact partner data in original system &1 could not be determined | The short text describes the object sufficiently | |
| 139 | 140 |
This BAdI implementation only supports loading procedure &1 | The short text describes the object sufficiently | |
| 140 | 141 |
This BAdI implementation only supports customer type &1 | The short text describes the object sufficiently | |
| 141 | 142 |
This BAdI implementation only supports company code type &1 | The short text describes the object sufficiently | |
| 142 | 143 |
This BAdI implementation only supports contact person type &1 | The short text describes the object sufficiently | |
| 143 | 144 |
BAdI implementation is not compatible with the previous implementation | Space: object requires documentation | |
| 144 | 145 |
This BAdI implementation does not support the customer (&1, &2) | The short text describes the object sufficiently | |
| 145 | 146 |
This BAdI implementation does not support the company code (&1, &2) | The short text describes the object sufficiently | |
| 146 | 147 |
BAdI &1 does not have an active implementation for loading procedure &2 | The short text describes the object sufficiently | |
| 147 | 151 |
No test customer number still available | The short text describes the object sufficiently | |
| 148 | 152 |
No test contact person number still available | The short text describes the object sufficiently | |
| 149 | 161 |
Neither general nor company code data is transferred | The short text describes the object sufficiently | |
| 150 | 162 |
No customer in the substitute system corresponds to the selection entries | The short text describes the object sufficiently | |
| 151 | 163 |
No data in original system &1 corresponds to the selection criteria | The short text describes the object sufficiently | |
| 152 | 164 |
&1 is the sample company Code: no data transfer | The short text describes the object sufficiently | |
| 153 | 165 |
&1 is not a company code from an original system: no data transfer | The short text describes the object sufficiently | |
| 154 | 166 |
You have selected the transfer of general and company code data (&1) | The short text describes the object sufficiently | |
| 155 | 167 |
You have selected the transfer of general data only (&1) | The short text describes the object sufficiently | |
| 156 | 168 |
You have selected the transfer of company code data only (&1) | The short text describes the object sufficiently | |
| 157 | 169 |
A total of &1 company codes were selected for the data transfer | The short text describes the object sufficiently | |
| 158 | 170 |
(&1) No customer data transfer for sample company code &2 | The short text describes the object sufficiently | |
| 159 | 171 |
(&1) transfer of customer master data for company code &2 is starting ... | The short text describes the object sufficiently | |
| 160 | 172 |
... company code &1 has ID (&2, &3) in original system &4 | The short text describes the object sufficiently | |
| 161 | 173 |
... General and company code data transferred from original system &1 | The short text describes the object sufficiently | |
| 162 | 174 |
...... General data last transferred on &1 | The short text describes the object sufficiently | |
| 163 | 175 |
...... Company code data last transferred on &1 | The short text describes the object sufficiently | |
| 164 | 176 |
... the general data is transferred from original system &1 | The short text describes the object sufficiently | |
| 165 | 177 |
... The company code data is transferred from original system &1 | The short text describes the object sufficiently | |
| 166 | 178 |
...... They were last transferred on &1 | The short text describes the object sufficiently | |
| 167 | 179 |
... All customers in company code (&1, &2) / system &3 to be transferred | The short text describes the object sufficiently | |
| 168 | 180 |
... There are &1 customers in company code &2 to update | The short text describes the object sufficiently | |
| 169 | 181 |
... Reading the customer data from original system(s) starting ... | The short text describes the object sufficiently | |
| 170 | 182 |
....... Customer &1 not read, as has been deleted or archived | The short text describes the object sufficiently | |
| 171 | 183 |
... | The short text describes the object sufficiently | |
| 172 | 184 |
... Reading customer data from original system(s) terminates due to error | The short text describes the object sufficiently | |
| 173 | 185 |
... Reading customer data from original system(s) finished without error | The short text describes the object sufficiently | |
| 174 | 186 |
... The indicator for Complete Data does not yet have a value | The short text describes the object sufficiently | |
| 175 | 187 |
... Data conversion for customer (&1, &2) begins ... | The short text describes the object sufficiently | |
| 176 | 188 |
... Data conversion for customer (&1, &2) terminates due to error | The short text describes the object sufficiently | |
| 177 | 189 |
... Data conversion for customer (&1, &2) completed without errors | The short text describes the object sufficiently | |
| 178 | 190 |
... Updating customer &1 in substitute system fails | The short text describes the object sufficiently | |
| 179 | 191 |
... Update of customer &1 in substitute system finished without error | The short text describes the object sufficiently | |
| 180 | 192 |
... Check of customer &1 in substitute system results in error(s) | The short text describes the object sufficiently | |
| 181 | 193 |
... Check of customer &1 in substitute system does not produce an error | The short text describes the object sufficiently | |
| 182 | 194 |
... Customer data transfer for company code &1 terminates due to error | The short text describes the object sufficiently | |
| 183 | 195 |
... Customer data transfer for company code &1 finished without error | The short text describes the object sufficiently | |
| 184 | 200 |
Local currencies do not match &1 &2 &3 &4 | Space: object requires documentation | |
| 185 | 201 |
Client not set up as substitute system | Space: object requires documentation | |
| 186 | 202 |
Sample company code is missing in table FDM_STAT_MIRROR | The short text describes the object sufficiently | |
| 187 | 204 |
No customer could be determined in the original system for customer &1 | Space: object requires documentation | |
| 188 | 205 |
You canot call BAdI &1 with loading procedure &2 in company code &3 | Space: object requires documentation | |
| 189 | 206 |
No invoice information could be determined for customer &1/&2 | The short text describes the object sufficiently | |
| 190 | 207 |
Company code &1 was processed | The short text describes the object sufficiently | |
| 191 | 208 |
No data was selected | The short text describes the object sufficiently | |
| 192 | 209 |
Customer &1/&2 not included | The short text describes the object sufficiently | |
| 193 | 210 |
Error in customer implementation for BAdI &1 &2: No export parameter &1 | The short text describes the object sufficiently | |
| 194 | 211 |
For customer &1/&2 there is no customer &3/&4 in the original system | The short text describes the object sufficiently | |
| 195 | 212 |
Error in accessing function module: &1 parameters: &2 &3 &4 | The short text describes the object sufficiently | |
| 196 | 213 |
System &1 is not an FI system | The short text describes the object sufficiently | |
| 197 | 214 |
Implement SAP Note &1 in original system (&2) | The short text describes the object sufficiently | |
| 198 | 215 |
Function module &1 does not exist in the original system (&2) | Space: object requires documentation | |
| 199 | 216 |
Document &1 from original system: amounts must always be positive | The short text describes the object sufficiently | |
| 200 | 217 |
Document &1 from original system: debit/credit indicator missing | The short text describes the object sufficiently | |
| 201 | 218 |
Document &1 from original system: debit/credit indicator &2 not allowed | The short text describes the object sufficiently | |
| 202 | 219 |
Test run for complete data transfer has been started | The short text describes the object sufficiently | |
| 203 | 220 |
Update run for complete data transfer has been started | The short text describes the object sufficiently | |
| 204 | 221 |
Test run for transfer of changes has been started | The short text describes the object sufficiently | |
| 205 | 222 |
Update run for transfer of changes has been started | The short text describes the object sufficiently | |
| 206 | 223 |
Customer &1/&2: duplicate document information for &3, &4 | Space: object requires documentation | |
| 207 | 224 |
Customer &1/&2: inconsistent document information for &3, &4 | Space: object requires documentation | |
| 208 | 225 |
Processing terminated due to missing connection to system &1 | The short text describes the object sufficiently | |
| 209 | 226 |
Number of customers processed: &1 | The short text describes the object sufficiently | |
| 210 | 227 |
Number of line items processed: &1 | The short text describes the object sufficiently | |
| 211 | 228 |
Program started with the option Post Documents Immediately | The short text describes the object sufficiently | |
| 212 | 229 |
Branch account could not be determined with data &1, &2, &3 | The short text describes the object sufficiently | |
| 213 | 230 |
Error in customer implement. BAdI &1 &2: export parameters &3, &4 wrong | The short text describes the object sufficiently | |
| 214 | 231 |
Customer &1/&2 has either been deleted or archived in the original system | Space: object requires documentation | |
| 215 | 232 |
All open line items of customer &1/&2 reversed | The short text describes the object sufficiently | |
| 216 | 238 |
Data conversion of customer (&1, &2) from system &3 terminates with error | The short text describes the object sufficiently | |
| 217 | 239 |
System &1 does not manage the data to be transferred for CoCd (&2, &3) | The short text describes the object sufficiently | |
| 218 | 240 |
Data for company code &1 not transferred | Space: object requires documentation | |
| 219 | 241 |
Transfer of general and company code data from system &1 is starting | The short text describes the object sufficiently | |
| 220 | 242 |
Transfer of general data from system &1 is starting | The short text describes the object sufficiently | |
| 221 | 243 |
Transfer of company code data from system &1 is starting | The short text describes the object sufficiently | |
| 222 | 244 |
... &1: company code (&2, &3) = &4 in substitute system | The short text describes the object sufficiently | |
| 223 | 245 |
... error terminates customer data transfer from original system &1 | The short text describes the object sufficiently | |
| 224 | 246 |
... customer data transfer from original system &1 complete without error | The short text describes the object sufficiently | |
| 225 | 250 |
E1KNA1M data for customer &1 not included | The short text describes the object sufficiently | |
| 226 | 251 |
E1KNB1M data for company code &1 not included | The short text describes the object sufficiently | |
| 227 | 252 |
E1KNB5M data for dunning area &1 not included | The short text describes the object sufficiently | |
| 228 | 253 |
E1KNBKM data for bank details (&1, &2, &3) not included | The short text describes the object sufficiently | |
| 229 | 254 |
E1KNVKM data for contact person &1 not included | The short text describes the object sufficiently | |
| 230 | 300 |
Summary: &1 messages for customer &2/&3 | The short text describes the object sufficiently | |
| 231 | 301 |
You are not allowed to post manually in the substitute system | The short text describes the object sufficiently | |
| 232 | 302 |
Field status for residual items posting key has been changed | The short text describes the object sufficiently | |
| 233 | 500 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 234 | 501 |
System error: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 235 | 502 |
System error in function module &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 236 | 503 |
System error in method &1 of class &2 &3 &4 | The short text describes the object sufficiently | |
| 237 | 504 |
System error in form routine &1 of program &2 &3 &4 | The short text describes the object sufficiently | |
| 238 | 506 |
Internal error: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 239 | 507 |
Internal error in function module &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 240 | 508 |
Internal error in method &1 of class &2 &3 &4 | The short text describes the object sufficiently | |
| 241 | 509 |
Internal error in form routine &1 of program &2 &3 &4 | The short text describes the object sufficiently | |
| 242 | 510 |
Log display using transaction SLG1, object: FIDM | The short text describes the object sufficiently | |
| 243 | 511 |
Execute the program in the background | The short text describes the object sufficiently |
History
| Last changed on/by | |
20100310 | SAP |
| SAP Release Created in | 605 |
