SAP ABAP Message Class IHC (IHC Messages)
Basic Data
Hierarchy
☛
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
⤷
FIN-FSCM-IHC (Application Component) FSCM In-House Cash
⤷
FIN_IHC (Package) Payment Order In-House Cash
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-IHC (Application Component) FSCM In-House Cash⤷
FIN_IHC (Package) Payment Order In-House Cash 
Attributes
| Message class |  |
IHC |
| Short Description |  |
IHC Messages |
| Changed On |  |
20130531 |
| Last Changed At |  |
122207 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
& & & & | Space: object requires documentation | |
| 2 | 001 |
Currency &1 in IDoc does not correspond to currency &2 of account &3 | Space: object requires documentation | |
| 3 | 002 |
Payment items & & read for reset | The short text describes the object sufficiently | |
| 4 | 003 |
More than one bank is assigned to bank ID &1 &2 | The short text describes the object sufficiently | |
| 5 | 004 |
Bank & & does not exist | Space: object requires documentation | |
| 6 | 005 |
Account of sender &1 does not exist in In-House Cash &2 | The short text describes the object sufficiently | |
| 7 | 006 |
Account of recipient &1 does not exist in In-House Cash &2 | Space: object requires documentation | |
| 8 | 007 |
Sender bank &1 &2 is not assigned to any bank area | Space: object requires documentation | |
| 9 | 008 |
Open log &1 no. &2 | Space: object requires documentation | |
| 10 | 009 |
Close log &1 no. &2 | Space: object requires documentation | |
| 11 | 010 |
Bank &1 &2 used for IHC &3 | The short text describes the object sufficiently | |
| 12 | 011 |
IHC payment order &1 was created | The short text describes the object sufficiently | |
| 13 | 012 |
Incorrect function module was called for message category &1 | The short text describes the object sufficiently | |
| 14 | 013 |
----- Clearing Partners Found ------- | The short text describes the object sufficiently | |
| 15 | 014 |
----- Routes Found ------- | The short text describes the object sufficiently | |
| 16 | 015 |
Clearing partner &1 was transferred | Space: object requires documentation | |
| 17 | 016 |
Break action &1 | The short text describes the object sufficiently | |
| 18 | 017 |
Document &1 &2 was created | The short text describes the object sufficiently | |
| 19 | 018 |
No payment request was created | Space: object requires documentation | |
| 20 | 019 |
No payment order was found for key &1 &2 &3 | Space: object requires documentation | |
| 21 | 020 |
Payment items were not created | Space: object requires documentation | |
| 22 | 021 |
Error mapping from IDoc to IHC payment order | The short text describes the object sufficiently | |
| 23 | 022 |
Enter a set of rules | Space: object requires documentation | |
| 24 | 023 |
Set of rules &1 does not exist | Space: object requires documentation | |
| 25 | 024 |
Set of rules &1 already exists | Space: object requires documentation | |
| 26 | 025 |
Missing route Customizing for bank area &1 | The short text describes the object sufficiently | |
| 27 | 026 |
Set of rules &1 was saved | The short text describes the object sufficiently | |
| 28 | 027 |
Node attributes &1 &2 were transferred | The short text describes the object sufficiently | |
| 29 | 028 |
Rule & was copied to the buffer | Space: object requires documentation | |
| 30 | 029 |
Rule &1 was inserted from the buffer | Space: object requires documentation | |
| 31 | 030 |
Only rules in the buffer can be copied | The short text describes the object sufficiently | |
| 32 | 031 |
The buffer is empty: No rules can be inserted | Space: object requires documentation | |
| 33 | 032 |
Update a rule with double-click | The short text describes the object sufficiently | |
| 34 | 033 |
No payment order &1 &2 &3 available | The short text describes the object sufficiently | |
| 35 | 034 |
Reset of payment order &1 &2 &3 was terminated | The short text describes the object sufficiently | |
| 36 | 035 |
Incorrect function module in ALE/IDoc for log. message &1 | The short text describes the object sufficiently | |
| 37 | 036 |
Error creating the payment requests | Space: object requires documentation | |
| 38 | 037 |
Transaction type &1 and IDoc refer to different payment categories | Space: object requires documentation | |
| 39 | 038 |
A transaction type could not be (uniquely) determined | The short text describes the object sufficiently | |
| 40 | 039 |
IDoc type &1 (credit memo) does not match transaction &2 (debit memo) | Space: object requires documentation | |
| 41 | 040 |
IDoc type &1 (debit memo) does not match transaction &2 (credit memo) | Space: object requires documentation | |
| 42 | 041 |
Error adding to database | The short text describes the object sufficiently | |
| 43 | 042 |
An error occurred during changes to the database | The short text describes the object sufficiently | |
| 44 | 043 |
Error when deleting on database | The short text describes the object sufficiently | |
| 45 | 044 |
Error when changing the status on the database | The short text describes the object sufficiently | |
| 46 | 045 |
Error saving the text info to the database | The short text describes the object sufficiently | |
| 47 | 046 |
Error deleting the text info on the database | The short text describes the object sufficiently | |
| 48 | 047 |
Error deleting the status on the database | The short text describes the object sufficiently | |
| 49 | 048 |
Error deleting partner info on the database | The short text describes the object sufficiently | |
| 50 | 049 |
Error deleting container fields on the database | The short text describes the object sufficiently | |
| 51 | 050 |
Error saving partner info on the database | The short text describes the object sufficiently | |
| 52 | 051 |
Error saving container fields on the database | The short text describes the object sufficiently | |
| 53 | 052 |
Payer item &1 in account management system posted successfully | The short text describes the object sufficiently | |
| 54 | 053 |
Offsetting item &1 posted successfully in account management system | The short text describes the object sufficiently | |
| 55 | 054 |
Settlement item &1 posted successfully in account management system | The short text describes the object sufficiently | |
| 56 | 055 |
BCA: & & & & | The short text describes the object sufficiently | |
| 57 | 056 |
BCA: Invalid data was transferred when &1 was posted | The short text describes the object sufficiently | |
| 58 | 057 |
BCA: You are not authorized to post &1 | The short text describes the object sufficiently | |
| 59 | 058 |
BCA: A system error occurred when you posted &1 | The short text describes the object sufficiently | |
| 60 | 059 |
BCA: &1 cannot be posted completely | The short text describes the object sufficiently | |
| 61 | 060 |
The IDoc with type &1 contains a check payment as a debit memo | Space: object requires documentation | |
| 62 | 061 |
Date &1 has an incorrect format | Space: object requires documentation | |
| 63 | 062 |
Value date &1 has an incorrect format | Space: object requires documentation | |
| 64 | 063 |
Invalid amount &1 or currency &2 | Space: object requires documentation | |
| 65 | 064 |
Inconsistent activity type &1: Check defined as debit memo | Space: object requires documentation | |
| 66 | 065 |
Transaction type &1 is not permitted for bank area &2 | The short text describes the object sufficiently | |
| 67 | 066 |
Receiving bank area &1 is known, define transaction type &2 as ext. paymt | The short text describes the object sufficiently | |
| 68 | 067 |
The system was unable to determine a clearing partner | The short text describes the object sufficiently | |
| 69 | 068 |
The system was unable to find a route | The short text describes the object sufficiently | |
| 70 | 069 |
BCA: Account for &1 does not exist | The short text describes the object sufficiently | |
| 71 | 070 |
IDoc communication Customizing is missing for clearing partner &1 | The short text describes the object sufficiently | |
| 72 | 071 |
Action &1 has already been carried out | The short text describes the object sufficiently | |
| 73 | 072 |
Action &1 cannot be carried out for payment with status &2 | The short text describes the object sufficiently | |
| 74 | 073 |
The system was unable to determine a bank for recipient bank area &1 | The short text describes the object sufficiently | |
| 75 | 074 |
An unknown error was triggered when posting &1 (RC = &2) | The short text describes the object sufficiently | |
| 76 | 075 |
Route &1 already exists: Enter a different name | The short text describes the object sufficiently | |
| 77 | 076 |
Rule &1 already exists under route &2 | The short text describes the object sufficiently | |
| 78 | 077 |
Set of rules &1, version &2 was copied to &3, version &4 | The short text describes the object sufficiently | |
| 79 | 078 |
Set of rules &1 was deleted | The short text describes the object sufficiently | |
| 80 | 079 |
Complete the attributes for the current route | The short text describes the object sufficiently | |
| 81 | 080 |
Complete the attributes for the current rule | The short text describes the object sufficiently | |
| 82 | 081 |
Only routes or rules can be deleted | The short text describes the object sufficiently | |
| 83 | 082 |
Bank area &1 does not exist | The short text describes the object sufficiently | |
| 84 | 083 |
Set of rules &1 was copied to transport request | The short text describes the object sufficiently | |
| 85 | 084 |
No customer/vendor account was found for &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 86 | 085 |
No payment method was found for bank area &1 and clearing partner &2 | The short text describes the object sufficiently | |
| 87 | 086 |
BTE &1 ( &2 &3) is run | The short text describes the object sufficiently | |
| 88 | 087 |
Limit for acct &1 &2 in process -> Limit check not possible at this time | The short text describes the object sufficiently | |
| 89 | 088 |
Transfer of &1 &2 from account &3 &4 exceeds the limit | The short text describes the object sufficiently | |
| 90 | 089 |
Generation of payment items - &1 - failed | The short text describes the object sufficiently | |
| 91 | 090 |
Payment order is forwarded to &1 for payment | The short text describes the object sufficiently | |
| 92 | 091 |
A clearing partner was not determined | The short text describes the object sufficiently | |
| 93 | 092 |
Accounts for clearing partner &1 / &2 are not maintained correctly in &3 | The short text describes the object sufficiently | |
| 94 | 093 |
The transaction amount has an incorrect format | The short text describes the object sufficiently | |
| 95 | 094 |
L/N account &1 for clearing partner &2 &3 in &4 is used for posting | The short text describes the object sufficiently | |
| 96 | 095 |
L/N acct &1 for clearing partner &2 &3 in &4 is used to update the limit | The short text describes the object sufficiently | |
| 97 | 096 |
Preliminary posting | The short text describes the object sufficiently | |
| 98 | 097 |
Final posting | The short text describes the object sufficiently | |
| 99 | 098 |
*--- &1: Internal payment order | The short text describes the object sufficiently | |
| 100 | 099 |
*--- &1: External payment order | The short text describes the object sufficiently | |
| 101 | 100 |
Incomplete Customizing for variant &1 for cash management data | Space: object requires documentation | |
| 102 | 101 |
Enter a valid start and end date | Space: object requires documentation | |
| 103 | 102 |
Transaction type &1 defined as internal: no recipient bank area found | The short text describes the object sufficiently | |
| 104 | 103 |
&1 records were copied to cash management | Space: object requires documentation | |
| 105 | 104 |
This selection variant already exists | The short text describes the object sufficiently | |
| 106 | 105 |
Error displaying the list. Contact SAP | The short text describes the object sufficiently | |
| 107 | 106 |
Error updating to cash management (BAdI) | Space: object requires documentation | |
| 108 | 107 |
Online processing is not possible in batch | The short text describes the object sufficiently | |
| 109 | 108 |
No authorization for cash management variant &1 and action &2 | The short text describes the object sufficiently | |
| 110 | 109 |
Simulation Run | The short text describes the object sufficiently | |
| 111 | 110 |
In-House Cash financial status from &1 through &2 | The short text describes the object sufficiently | |
| 112 | 111 |
Consistency check for cash management Customizing for variant &1 | The short text describes the object sufficiently | |
| 113 | 112 |
No alias was defined for variant &1 | The short text describes the object sufficiently | |
| 114 | 113 |
Alias &1 for variant &2 does not match any company code | The short text describes the object sufficiently | |
| 115 | 114 |
Alias for 'posted' status missing for variant &1 | The short text describes the object sufficiently | |
| 116 | 115 |
No planning level &2 exists for variant &1 | The short text describes the object sufficiently | |
| 117 | 116 |
Alias for internally planned status is missing for variant &1 | The short text describes the object sufficiently | |
| 118 | 117 |
Alias for externally planned status is missing for variant &1 | The short text describes the object sufficiently | |
| 119 | 118 |
Alias for group &1 is missing for variant &2 | The short text describes the object sufficiently | |
| 120 | 119 |
No cash management account &2 exists for variant &1 in company code &3 | The short text describes the object sufficiently | |
| 121 | 120 |
Cash management account &1 in company code &2 cannot be a G/L account | The short text describes the object sufficiently | |
| 122 | 121 |
Cash management Customizing is consistent | Space: object requires documentation | |
| 123 | 122 |
Posting was made to account &1 instead of offsetting account &2 in &3 | The short text describes the object sufficiently | |
| 124 | 123 |
Posting was made to account &1 instead of payer account &2 in &3 | The short text describes the object sufficiently | |
| 125 | 124 |
Original account &1 with &2 is used for updating the limit | The short text describes the object sufficiently | |
| 126 | 125 |
Posting &3 made to original account &1 &2 | The short text describes the object sufficiently | |
| 127 | 126 |
*++++: START OF POSTINGS TO ACCOUNT MANAGEMENT SYSTEM | The short text describes the object sufficiently | |
| 128 | 127 |
*++++: POSTINGS TO ACCOUNT MANAGEMENT SYSTEM | The short text describes the object sufficiently | |
| 129 | 128 |
*++++: REVERSALS IN ACCOUNT MANAGEMENT SYSTEM | The short text describes the object sufficiently | |
| 130 | 129 |
*++++: REVERSALS IN ACCOUNT MANAGEMENT SYSTEM | The short text describes the object sufficiently | |
| 131 | 130 |
=> Amount to be checked incl. provisional postings: &1 &2 &3 | The short text describes the object sufficiently | |
| 132 | 131 |
Payment order &1 has been deleted | The short text describes the object sufficiently | |
| 133 | 132 |
Payment order &1 has been reversed | The short text describes the object sufficiently | |
| 134 | 133 |
Payment order &1 has been finally posted | The short text describes the object sufficiently | |
| 135 | 134 |
Payment order &1 has been flagged for posting in the background | The short text describes the object sufficiently | |
| 136 | 135 |
Payment order &1 has been released | The short text describes the object sufficiently | |
| 137 | 136 |
Payment order &1 has been reset | The short text describes the object sufficiently | |
| 138 | 137 |
Payment order &1 was saved by user &2 | The short text describes the object sufficiently | |
| 139 | 138 |
A payment request (IDoc &1) was sent to system &2 | The short text describes the object sufficiently | |
| 140 | 139 |
Payment order &1 was sent to be checked (dual control) | The short text describes the object sufficiently | |
| 141 | 140 |
Payment order &1 has been parked (with clearing partner) | The short text describes the object sufficiently | |
| 142 | 141 |
Payment order &1 was provisionally posted | The short text describes the object sufficiently | |
| 143 | 142 |
Provisionally posted payment order &1 was posted to a prior period | The short text describes the object sufficiently | |
| 144 | 143 |
Recipient and sender bank areas the same: No clearing partner determin. | The short text describes the object sufficiently | |
| 145 | 144 |
Transaction type &1 was transferred | The short text describes the object sufficiently | |
| 146 | 145 |
Release must be triggered by a user other than &1 | The short text describes the object sufficiently | |
| 147 | 146 |
You are not authorized to carry out action &1 | The short text describes the object sufficiently | |
| 148 | 147 |
You do not have sufficient authorization; see the long message text | Space: object requires documentation | |
| 149 | 148 |
Worklist already exists | The short text describes the object sufficiently | |
| 150 | 149 |
BCA: Errors were recorded in the checks when you posted &1 | The short text describes the object sufficiently | |
| 151 | 150 |
Deleting of payment order &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 152 | 151 |
Deleting of payment order status &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 153 | 152 |
Deleting of payment order text info &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 154 | 153 |
Inserting payment order &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 155 | 154 |
Inserting payment order status &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 156 | 155 |
Inserting payment order attributes &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 157 | 156 |
Blocking of payment order &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 158 | 157 |
Reading payment order &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 159 | 158 |
Reading payment order GUID &1 / &2 / &3 failed | The short text describes the object sufficiently | |
| 160 | 159 |
Recipient bank &1 &2 is not assigned to any bank area | The short text describes the object sufficiently | |
| 161 | 160 |
Bank &1 &2 is assigned either to no bank area or to more than one | The short text describes the object sufficiently | |
| 162 | 161 |
The attributes of transaction type &1 were not determined | The short text describes the object sufficiently | |
| 163 | 162 |
Bank ID &1 &2 is unknown in the account management system | The short text describes the object sufficiently | |
| 164 | 163 |
Account &1 &2 &3 is unknown in the account management system | The short text describes the object sufficiently | |
| 165 | 164 |
The provisional settlement account for &1 &2 &3 has not been maintained | The short text describes the object sufficiently | |
| 166 | 165 |
Posting param. for provis. outbound paymts to &1 for &2 &3 not maintained | The short text describes the object sufficiently | |
| 167 | 166 |
Posting param. for provis. inbound paymnts to &1 for &2 &3 not maintained | The short text describes the object sufficiently | |
| 168 | 167 |
Posting param. for final outbound payments to &1 for &2 &3 not maintained | The short text describes the object sufficiently | |
| 169 | 168 |
Posting param. for final inbound payments to &1 for &2 &3 not maintained | The short text describes the object sufficiently | |
| 170 | 169 |
Exchange rate type for &1 is not (or is insufficiently) maintained | The short text describes the object sufficiently | |
| 171 | 170 |
FX translation &1 to &2, exchange rate type &3, failed on &4 | The short text describes the object sufficiently | |
| 172 | 171 |
Blocking of limit object &1 &2 failed | The short text describes the object sufficiently | |
| 173 | 172 |
Bank ID &1 &2 has not been assigned to a clearing area | The short text describes the object sufficiently | |
| 174 | 173 |
No account has been maintained for &1 credit memos of &2 from &3 | The short text describes the object sufficiently | |
| 175 | 174 |
Secondary debit amount &1 &2 is less than primary amount &3 &4 | The short text describes the object sufficiently | |
| 176 | 175 |
Secondary credit amount &1 &2 is more than the primary amount &3 &4 | The short text describes the object sufficiently | |
| 177 | 176 |
Check primary & and secondary rates &1 to &2 on &3 | The short text describes the object sufficiently | |
| 178 | 177 |
Curr. &1 of the settlement account is not the same as settlement curr. &2 | The short text describes the object sufficiently | |
| 179 | 178 |
Display of all payment orders for which you have authorization | Space: object requires documentation | |
| 180 | 179 |
BCA posting date for bank area &1 was not determined | The short text describes the object sufficiently | |
| 181 | 180 |
Currency &1 from settlement acct &2/&3 is not equal to &4 in orig. acct | The short text describes the object sufficiently | |
| 182 | 181 |
Curr. &1 from clearing partner acct &2/&3 is not equal to payment curr.&4 | The short text describes the object sufficiently | |
| 183 | 182 |
IHC credit memo amount &1 &2 greater than external credit memo amnt &1 &3 | The short text describes the object sufficiently | |
| 184 | 183 |
IHC debit amount &1 &2 less than external payment amount &1 &3 | The short text describes the object sufficiently | |
| 185 | 184 |
No bank key was found for bank &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 186 | 185 |
More than one bank key was found for bank &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 187 | 186 |
Transaction type &1 was transferred with posting attribute &2 | The short text describes the object sufficiently | |
| 188 | 187 |
Instruction key &1 is not permitted | The short text describes the object sufficiently | |
| 189 | 188 |
The recipient account &1/&2 determined is not located in bank area &3 | The short text describes the object sufficiently | |
| 190 | 189 |
The bank statement is not IHC relevant | The short text describes the object sufficiently | |
| 191 | 190 |
A value date was not determined for payment order &1/&2/&3 | The short text describes the object sufficiently | |
| 192 | 191 |
Incorrect Cust.: Two recipient accounts &1/&2 and &3/&4 were determined | The short text describes the object sufficiently | |
| 193 | 192 |
Segment &1 is incorrect; check SP version in subsidiary system | The short text describes the object sufficiently | |
| 194 | 193 |
Error in function module & | The short text describes the object sufficiently | |
| 195 | 194 |
No payment method delivered | The short text describes the object sufficiently | |
| 196 | 195 |
No payment parameters maintained | The short text describes the object sufficiently | |
| 197 | 196 |
Creation of header data failed | The short text describes the object sufficiently | |
| 198 | 197 |
Creation of individual payment requests failed | The short text describes the object sufficiently | |
| 199 | 198 |
IDoc check failed | The short text describes the object sufficiently | |
| 200 | 199 |
Inconsistent currencies (header <> line item): & & | The short text describes the object sufficiently | |
| 201 | 200 |
Unknown currency & | The short text describes the object sufficiently | |
| 202 | 201 |
IDoc check failed | The short text describes the object sufficiently | |
| 203 | 202 |
IHC payment request & posted by IDoc & | The short text describes the object sufficiently | |
| 204 | 203 |
Error generating numbers from payment order number range | The short text describes the object sufficiently | |
| 205 | 204 |
No valid clearing partner was found | The short text describes the object sufficiently | |
| 206 | 205 |
No parameters found for: & & & | The short text describes the object sufficiently | |
| 207 | 206 |
Error in function module & | The short text describes the object sufficiently | |
| 208 | 207 |
External payment order &1/&2/&3 in &4 must first be reversed | The short text describes the object sufficiently | |
| 209 | 208 |
Reversal of payment request &1 in &4 failed (&2/&3) | The short text describes the object sufficiently | |
| 210 | 209 |
No partner found | The short text describes the object sufficiently | |
| 211 | 210 |
IDoc Items: Fatal error | The short text describes the object sufficiently | |
| 212 | 211 |
Invalid massage type & | The short text describes the object sufficiently | |
| 213 | 212 |
Invalid segment type & | The short text describes the object sufficiently | |
| 214 | 213 |
Inconsistent amounts | The short text describes the object sufficiently | |
| 215 | 214 |
Segment &1 is incorrect; check SP version in subsidiary system | The short text describes the object sufficiently | |
| 216 | 215 |
Secondary rate type &1 is used for provisional account posting &2 | The short text describes the object sufficiently | |
| 217 | 216 |
Secondary rate type &1 is used for final account posting &2 | The short text describes the object sufficiently | |
| 218 | 217 |
Primary rate type &1 is used for provisional account posting &2 | The short text describes the object sufficiently | |
| 219 | 218 |
Primary rate type &1 is used for final account posting &2 | The short text describes the object sufficiently | |
| 220 | 219 |
Most recent exchange rate &2->&3 for rate type &1: &4 | The short text describes the object sufficiently | |
| 221 | 220 |
Conversion date used for currency conversion &1 -> &2: &3 | The short text describes the object sufficiently | |
| 222 | 221 |
Account currency amount &2 &3 to be posted for items - &1 | The short text describes the object sufficiently | |
| 223 | 222 |
Source transaction currency amount: &1 &2 | The short text describes the object sufficiently | |
| 224 | 223 |
Payment order &1 in system &2 was reversed (date &3/ reason &4) | The short text describes the object sufficiently | |
| 225 | 224 |
Payment order status &1/&2/&3 in &4: Reversed | The short text describes the object sufficiently | |
| 226 | 225 |
Payment order status &1/&2/&3 in &4: Deleted | The short text describes the object sufficiently | |
| 227 | 226 |
Reverse terminated due to executable payment order &1/&2/&3 in &4 | The short text describes the object sufficiently | |
| 228 | 227 |
Display of change documents failed | The short text describes the object sufficiently | |
| 229 | 228 |
Reset of item &1/&2 in the account management system failed | The short text describes the object sufficiently | |
| 230 | 229 |
Limit update for payment order &1/&2/&3 failed | The short text describes the object sufficiently | |
| 231 | 230 |
Bank area assignment in bank statement Customizing is missing | The short text describes the object sufficiently | |
| 232 | 231 |
The assignment of FI acct no. for &1 is missing in bank statement Cust. | The short text describes the object sufficiently | |
| 233 | 232 |
The assignment of the header acct is missing in bank statemnt Customizing | The short text describes the object sufficiently | |
| 234 | 233 |
Set of rules &1 was deleted by &2 on &3 at &4 | The short text describes the object sufficiently | |
| 235 | 234 |
Set of rules &1 was changed by &2 on &3 at &4 | The short text describes the object sufficiently | |
| 236 | 235 |
Set of rules &1 was created by &2 on &3 at &4 | The short text describes the object sufficiently | |
| 237 | 236 |
No posting behavior was determined for transaction type &1 | The short text describes the object sufficiently | |
| 238 | 237 |
Payment order with external payment cannot be reset | The short text describes the object sufficiently | |
| 239 | 238 |
Set of rules &1 was not saved | The short text describes the object sufficiently | |
| 240 | 239 |
No payment items were selected for reset | The short text describes the object sufficiently | |
| 241 | 240 |
The latest version of set of rules &1 was retrieved by &2 on &3 at &4 | The short text describes the object sufficiently | |
| 242 | 241 |
Internal error: Key fields are missing | The short text describes the object sufficiently | |
| 243 | 242 |
Internal error: Key field is missing | The short text describes the object sufficiently | |
| 244 | 243 |
Exchange rate is missing: & & & | The short text describes the object sufficiently | |
| 245 | 244 |
Rate types were transferred for clearing partner &1 and transactn type &2 | The short text describes the object sufficiently | |
| 246 | 245 |
Rate types were transferred for transaction type &1 | The short text describes the object sufficiently | |
| 247 | 246 |
Rate types were transferred for clearing partner | The short text describes the object sufficiently | |
| 248 | 247 |
Rate types transferred independent of clearing partner and trans. type | The short text describes the object sufficiently | |
| 249 | 248 |
External rate types are used for external payments | The short text describes the object sufficiently | |
| 250 | 249 |
Rate types used independent of the transaction type | The short text describes the object sufficiently | |
| 251 | 250 |
Time-To-Live &1 has been reached | The short text describes the object sufficiently | |
| 252 | 251 |
Error during document selection | The short text describes the object sufficiently | |
| 253 | 252 |
No IHC Customizing for creating external &1 payment orders in &2 | The short text describes the object sufficiently | |
| 254 | 253 |
Customizing incomplete for external &1 payment orders in &2 | The short text describes the object sufficiently | |
| 255 | 254 |
Transaction types &1 and &3 have the same +/- sign => Termination | The short text describes the object sufficiently | |
| 256 | 255 |
&1: Successful | The short text describes the object sufficiently | |
| 257 | 256 |
&1: Not successful | The short text describes the object sufficiently | |
| 258 | 257 |
&3 clearing item(s) for BCA payment order &1 &2 already posted | The short text describes the object sufficiently | |
| 259 | 258 |
Clearing items for BCA order &1 &2 cannot be posted | The short text describes the object sufficiently | |
| 260 | 259 |
Clearing item &1 for BCA order &2 &3 posted successfully | The short text describes the object sufficiently | |
| 261 | 260 |
IHC payment order &1 for BCA order &2 &3 posted successfully | The short text describes the object sufficiently | |
| 262 | 261 |
External forwarding of BCA order &1 &2 completed successfully | The short text describes the object sufficiently | |
| 263 | 262 |
External forwarding (BCA order &1 &2) | The short text describes the object sufficiently | |
| 264 | 263 |
External forwarding (BCA order &1 &2) | The short text describes the object sufficiently | |
| 265 | 264 |
More than one recipient for BCA order &1 &2; Forwarding is terminated | The short text describes the object sufficiently | |
| 266 | 265 |
No recipient for BCA order &1 &2 => Forwarding is terminated | The short text describes the object sufficiently | |
| 267 | 266 |
IHC payment order for BCA order &2 &3 cannot be posted | The short text describes the object sufficiently | |
| 268 | 267 |
Action call is inconsistent | The short text describes the object sufficiently | |
| 269 | 268 |
Outbound IDoc &1 is used for partner type &2 | Space: object requires documentation | |
| 270 | 269 |
No outbound IDoc exists | The short text describes the object sufficiently | |
| 271 | 270 |
ISO currency key & is not assigned (header). | The short text describes the object sufficiently | |
| 272 | 271 |
Partner category is unknown for outbound IDoc => Cancel | The short text describes the object sufficiently | |
| 273 | 272 |
No outbound IDoc exists for payment order &1 &2 &3 | The short text describes the object sufficiently | |
| 274 | 273 |
There are no external documents | The short text describes the object sufficiently | |
| 275 | 274 |
IDoc &4 is archived for payment order &1 &2 &3 | The short text describes the object sufficiently | |
| 276 | 275 |
Payment order &1: IDoc &2 has status &4 in target system &3 | The short text describes the object sufficiently | |
| 277 | 276 |
Unknown error occurred => Processing is terminated | The short text describes the object sufficiently | |
| 278 | 277 |
*++++: Reversals in Subsequent Payment System | The short text describes the object sufficiently | |
| 279 | 278 |
*++++: Reversals in Subsequent Payment System | The short text describes the object sufficiently | |
| 280 | 279 |
RFC call &1 failed in system &2 | The short text describes the object sufficiently | |
| 281 | 280 |
There are no valid documents for processing | The short text describes the object sufficiently | |
| 282 | 281 |
Payment order &1: Incoming IDoc missing in target system &3 for IDoc &2 | The short text describes the object sufficiently | |
| 283 | 282 |
Unknown payment method: &1 | The short text describes the object sufficiently | |
| 284 | 283 |
Exception in BADI implementation 'MODIFY_PAYMENT_ITEMS' => Cancel | The short text describes the object sufficiently | |
| 285 | 284 |
Payment order &1: BADI 'MODIFY_PAYMENT_ITEMS' is active | The short text describes the object sufficiently | |
| 286 | 285 |
Payment order &1: &2 &3 changed by BADI 'MODIFY_PAYMENT_ITEMS' | The short text describes the object sufficiently | |
| 287 | 286 |
Payment order &1: &2 missing | The short text describes the object sufficiently | |
| 288 | 287 |
Error creating set of rules &1 | The short text describes the object sufficiently | |
| 289 | 288 |
Only routes for bank area &1 can be processed | The short text describes the object sufficiently | |
| 290 | 289 |
Payment order &1 was supplied with external references | The short text describes the object sufficiently | |
| 291 | 290 |
Payment order &1 was not reversed | The short text describes the object sufficiently | |
| 292 | 291 |
Payment order &1 was not deleted | The short text describes the object sufficiently | |
| 293 | 292 |
Payment order &1 still contains errors | The short text describes the object sufficiently | |
| 294 | 293 |
Payment order &1 was not flagged for background posting | The short text describes the object sufficiently | |
| 295 | 294 |
Payment order &1 was not reset | The short text describes the object sufficiently | |
| 296 | 295 |
Payment order &1 was not saved | The short text describes the object sufficiently | |
| 297 | 296 |
Payment order &1 was not parked (with clearing partner) | The short text describes the object sufficiently | |
| 298 | 297 |
Payment order &1 was not released | The short text describes the object sufficiently | |
| 299 | 298 |
Payment order &1 was not posted | The short text describes the object sufficiently | |
| 300 | 299 |
Payment order &1 was not posted finally | The short text describes the object sufficiently | |
| 301 | 300 |
Payment order &1 was not supplied with external references | The short text describes the object sufficiently | |
| 302 | 301 |
Payment order &1 was not revaluated | The short text describes the object sufficiently | |
| 303 | 302 |
Payment order &1 could not be blocked | The short text describes the object sufficiently | |
| 304 | 303 |
Payment order &1 could not be read | The short text describes the object sufficiently | |
| 305 | 304 |
Paymnt order &1: BADI delivers several offsetting acct items => Terminate | The short text describes the object sufficiently | |
| 306 | 305 |
Payment order &1: &2 field &3 was changed => Termination | The short text describes the object sufficiently | |
| 307 | 306 |
No offsetting transaction type found for transaction type &1 | The short text describes the object sufficiently | |
| 308 | 307 |
&1 test run: changes are not saved | The short text describes the object sufficiently | |
| 309 | 308 |
&1 test run: changes were not saved | The short text describes the object sufficiently | |
| 310 | 309 |
Payment order &1 is blocked for further processing | The short text describes the object sufficiently | |
| 311 | 310 |
Payment order &1 is released for further processing | The short text describes the object sufficiently | |
| 312 | 311 |
Payment order &1 is already blocked | The short text describes the object sufficiently | |
| 313 | 312 |
Payment order &1 is already released | The short text describes the object sufficiently | |
| 314 | 313 |
No payment order for external reference &1 &2 &3 | The short text describes the object sufficiently | |
| 315 | 314 |
External reference &1 &2 &3 is not unique | The short text describes the object sufficiently | |
| 316 | 315 |
Unknown direction &1 in payment order &2 | The short text describes the object sufficiently | |
| 317 | 316 |
No planning group &2 exists for variant &1 | The short text describes the object sufficiently | |
| 318 | 317 |
IHC-BCA link: open FI component IHC not activated => Termination | The short text describes the object sufficiently | |
| 319 | 318 |
Payment order &1 was not blocked | The short text describes the object sufficiently | |
| 320 | 319 |
Payment order &1 was not unblocked | The short text describes the object sufficiently | |
| 321 | 320 |
Transaction type for activity category &1 and BTC &2 was not determined | The short text describes the object sufficiently | |
| 322 | 321 |
Database write error. Table: & | The short text describes the object sufficiently | |
| 323 | 322 |
An error occurred while reading from the database. Table: & | The short text describes the object sufficiently | |
| 324 | 323 |
Error during unblocking | The short text describes the object sufficiently | |
| 325 | 324 |
A database error occurred while saving | The short text describes the object sufficiently | |
| 326 | 325 |
Payment order & was revaluated | The short text describes the object sufficiently | |
| 327 | 326 |
Route & with priority & | The short text describes the object sufficiently | |
| 328 | 327 |
Clearing partner & for route & | The short text describes the object sufficiently | |
| 329 | 328 |
Status &1 of payment order &2 is not valid | The short text describes the object sufficiently | |
| 330 | 329 |
Unable to determine RFC connection for clearing partner & | The short text describes the object sufficiently | |
| 331 | 330 |
Creation of payment requests terminated. Exception triggered in BAdI | The short text describes the object sufficiently | |
| 332 | 333 |
Processing terminated, since number of bank areas larger than 36 | Space: object requires documentation | |
| 333 | 351 |
An upgrade is not running. The program is only for upgrade procedures | The short text describes the object sufficiently | |
| 334 | 352 |
Invalid version. The program is only for upgrades from ECC500 to 600 | The short text describes the object sufficiently | |
| 335 | 353 |
(IHC_TAB_DUAL_CTR) Error during UPDATE. Key: & / & / & | The short text describes the object sufficiently | |
| 336 | 354 |
(IHC_TAB_DUAL_CTR) Entry successfully adjusted: & / & / & | The short text describes the object sufficiently | |
| 337 | 357 |
Errors during upgrade. Customizing is incorrect | Space: object requires documentation | |
| 338 | 358 |
There are warnings from upgrade. Check Customizing | Space: object requires documentation | |
| 339 | 359 |
Upgrade: Adjusting Customizing was successful | The short text describes the object sufficiently | |
| 340 | 360 |
You attempted to process more than one IDoc simultaneously | The short text describes the object sufficiently | |
| 341 | 361 |
IHC inbound processing: Unknown message type & | The short text describes the object sufficiently | |
| 342 | 363 |
Exception in BADI Implementation 'MODIFY_PN' => Termination | The short text describes the object sufficiently | |
| 343 | 364 |
Payment order &1: BADI 'MODIFY_PN' is active | The short text describes the object sufficiently | |
| 344 | 365 |
Payment order &1: changed by BADI 'MODIFY_PN' | The short text describes the object sufficiently | |
| 345 | 366 |
Exception in BAdI implementation '&' | The short text describes the object sufficiently | |
| 346 | 400 |
Do not assign an amount if you do not enter a currency | The short text describes the object sufficiently | |
| 347 | 401 |
Error in workflow Customizing. Inform SAP | The short text describes the object sufficiently | |
| 348 | 402 |
Also assign a currency if you have assigned an amount | The short text describes the object sufficiently | |
| 349 | 410 |
No bank statement found in CoCd &, bank ID &, account &, number & | The short text describes the object sufficiently | |
| 350 | 411 |
Inconsistency between statemt & new starting balance and last end balance | Space: object requires documentation | |
| 351 | 412 |
Adjusted statements were saved successfully | The short text describes the object sufficiently | |
| 352 | 413 |
Error when writing to DB | The short text describes the object sufficiently | |
| 353 | 414 |
House bank account &/& does not exist in company code & | The short text describes the object sufficiently | |
| 354 | 450 |
Select variants | The short text describes the object sufficiently | |
| 355 | 451 |
No variants were found | The short text describes the object sufficiently | |
| 356 | 500 |
Create a number range for logs: & & | The short text describes the object sufficiently | |
| 357 | 550 |
Account does not exist: & & | The short text describes the object sufficiently | |
| 358 | 551 |
Bank area & does not exist | The short text describes the object sufficiently | |
| 359 | 600 |
Execution date is missing | The short text describes the object sufficiently | |
| 360 | 601 |
Transaction currency is missing | The short text describes the object sufficiently | |
| 361 | 602 |
Transaction amount is missing | The short text describes the object sufficiently | |
| 362 | 603 |
Transaction type is missing | The short text describes the object sufficiently | |
| 363 | 604 |
Input channel is missing | The short text describes the object sufficiently | |
| 364 | 605 |
Sender bank area is missing | The short text describes the object sufficiently | |
| 365 | 606 |
Sender account is missing | The short text describes the object sufficiently | |
| 366 | 607 |
Recipient name is missing (bank data) | The short text describes the object sufficiently | |
| 367 | 608 |
Recipient name is missing (address data) | The short text describes the object sufficiently | |
| 368 | 609 |
Postal code is missing | The short text describes the object sufficiently | |
| 369 | 610 |
City is missing | The short text describes the object sufficiently | |
| 370 | 611 |
Street and house number are missing | The short text describes the object sufficiently | |
| 371 | 612 |
Recipient country is missing | The short text describes the object sufficiently | |
| 372 | 613 |
Recipient account number/IBAN is missing | The short text describes the object sufficiently | |
| 373 | 614 |
Recipient account number is missing | The short text describes the object sufficiently | |
| 374 | 615 |
Recipient bank area and bank number/bank country do not match | The short text describes the object sufficiently | |
| 375 | 616 |
Recipient bank country is missing | The short text describes the object sufficiently | |
| 376 | 617 |
SWIFT code is missing | The short text describes the object sufficiently | |
| 377 | 618 |
Recipient bank number/SWIFT is missing | The short text describes the object sufficiently | |
| 378 | 619 |
Container field & is mandatory, screen: &2 | The short text describes the object sufficiently | |
| 379 | 620 |
Container field & is not defined | The short text describes the object sufficiently | |
| 380 | 621 |
Invalid posting date: & | The short text describes the object sufficiently | |
| 381 | 622 |
Invalid sender value date: & | The short text describes the object sufficiently | |
| 382 | 623 |
Invalid recipient value date: & | The short text describes the object sufficiently | |
| 383 | 624 |
Invalid amount: & | The short text describes the object sufficiently | |
| 384 | 625 |
Invalid sender exchange rate: & | The short text describes the object sufficiently | |
| 385 | 626 |
Invalid recipient exchange rate: & | The short text describes the object sufficiently | |
| 386 | 627 |
Invalid recipient IBAN: & | The short text describes the object sufficiently | |
| 387 | 628 |
Invalid SWIFT: & | The short text describes the object sufficiently | |
| 388 | 629 |
Invalid currency: & | The short text describes the object sufficiently | |
| 389 | 630 |
Sender account not found: & / & | The short text describes the object sufficiently | |
| 390 | 631 |
Recipient bank country not found: & | The short text describes the object sufficiently | |
| 391 | 632 |
Recipient country not found: & | The short text describes the object sufficiently | |
| 392 | 633 |
SWIFT does not exist: & | The short text describes the object sufficiently | |
| 393 | 634 |
Recipient bank number not found: & | The short text describes the object sufficiently | |
| 394 | 635 |
Bank number & in bank master does not correspond to SWIFT code & | The short text describes the object sufficiently | |
| 395 | 636 |
Clearing partner not permitted: & | The short text describes the object sufficiently | |
| 396 | 637 |
Recipient account not found: & / & | The short text describes the object sufficiently | |
| 397 | 638 |
Postal code is invalid: & | The short text describes the object sufficiently | |
| 398 | 639 |
IDoc & and determined transport type & do not match | The short text describes the object sufficiently | |
| 399 | 640 |
Error in container fields (user-defined check) | The short text describes the object sufficiently | |
| 400 | 641 |
Transaction amount negative: & | The short text describes the object sufficiently | |
| 401 | 642 |
Sender account amount negative: & | The short text describes the object sufficiently | |
| 402 | 643 |
Recipient account amount negative: & | The short text describes the object sufficiently | |
| 403 | 644 |
The sender exchange rate is negative: & | The short text describes the object sufficiently | |
| 404 | 645 |
Recipient exchange rate is negative: & | The short text describes the object sufficiently | |
| 405 | 646 |
Instructions key & is not permitted | The short text describes the object sufficiently | |
| 406 | 647 |
Instruction & does not correspond to instruction key & | The short text describes the object sufficiently | |
| 407 | 648 |
Instruction & is not defined | The short text describes the object sufficiently | |
| 408 | 649 |
Recipient bank key is missing | The short text describes the object sufficiently | |
| 409 | 650 |
Transaction type is external and clearing partner missing: inconsistency | The short text describes the object sufficiently | |
| 410 | 651 |
Clearing partner is missing | The short text describes the object sufficiently | |
| 411 | 652 |
Input channel IDoc, IDoc number is missing | The short text describes the object sufficiently | |
| 412 | 653 |
Input channel & is not valid | The short text describes the object sufficiently | |
| 413 | 654 |
Recipient bank area is missing | The short text describes the object sufficiently | |
| 414 | 655 |
Sender bank country is missing | The short text describes the object sufficiently | |
| 415 | 656 |
Transaction type (&) and payment direction (&) do not match | The short text describes the object sufficiently | |
| 416 | 657 |
Payment order &/&/& is being checked | The short text describes the object sufficiently | |
| 417 | 658 |
No error was found | The short text describes the object sufficiently | |
| 418 | 659 |
Transaction type & is not permitted in bank area & | The short text describes the object sufficiently | |
| 419 | 660 |
Account &1/&2 does not exist | The short text describes the object sufficiently | |
| 420 | 661 |
&1/&2/&3 | The short text describes the object sufficiently | |
| 421 | 662 |
Account &1/&2 is inactive | The short text describes the object sufficiently | |
| 422 | 700 |
Account & & does not exist | The short text describes the object sufficiently | |
| 423 | 740 |
&1 IHC payment orders were selected | The short text describes the object sufficiently | |
| 424 | 741 |
&1 IHC payment orders were successfully archived | The short text describes the object sufficiently | |
| 425 | 750 |
Error writing to archive: & / & / & Input structure: & | The short text describes the object sufficiently | |
| 426 | 751 |
Error writing to archive: & / & / & Table structure: & | The short text describes the object sufficiently | |
| 427 | 752 |
Archive file cannot be opened. Object: &, Create: &, Delete: & | The short text describes the object sufficiently | |
| 428 | 753 |
Archive object cannot be created. Payment order: & / & / & | The short text describes the object sufficiently | |
| 429 | 754 |
Change documents cannot be archived. PO: & / & / & Object: & | The short text describes the object sufficiently | |
| 430 | 755 |
Archive object cannot be saved. Payment order: & / & / & | The short text describes the object sufficiently | |
| 431 | 756 |
Archive index cannot be created. Variant: & | The short text describes the object sufficiently | |
| 432 | 757 |
Archive file cannot be saved. Object: & | The short text describes the object sufficiently | |
| 433 | 758 |
Payment order cannot be opened: & / & / & | The short text describes the object sufficiently | |
| 434 | 759 |
Error while reading payment order data: & / & / & | The short text describes the object sufficiently | |
| 435 | 760 |
Error while checking authorization: & / & / & | The short text describes the object sufficiently | |
| 436 | 761 |
Archive statistics could not be created | The short text describes the object sufficiently | |
| 437 | 762 |
Archive object &: Customizing information is missing | The short text describes the object sufficiently | |
| 438 | 763 |
Payment order & / & / & cannot be archived | The short text describes the object sufficiently | |
| 439 | 764 |
Archive file cannot be opened. Object: & Test mode: & | The short text describes the object sufficiently | |
| 440 | 765 |
Error reading archive. Stucture: & | The short text describes the object sufficiently | |
| 441 | 766 |
Archive object cannot be read | The short text describes the object sufficiently | |
| 442 | 767 |
Change documents cannot be read. Payment order: & / & / & | The short text describes the object sufficiently | |
| 443 | 768 |
Archived log cannot be read. Payment order: & / & / & | The short text describes the object sufficiently | |
| 444 | 769 |
Archive index cannot be changed, ID: & | The short text describes the object sufficiently | |
| 445 | 770 |
Archive statistics cannot be displayed | The short text describes the object sufficiently | |
| 446 | 771 |
Archive file cannot be closed | The short text describes the object sufficiently | |
| 447 | 772 |
Payment order data cannot be deleted. Structure: & | The short text describes the object sufficiently | |
| 448 | 773 |
Change documents cannot be deleted | The short text describes the object sufficiently | |
| 449 | 774 |
Archive variant & not found, only standard index is written | The short text describes the object sufficiently | |
| 450 | 775 |
Archive list & not found, only standard index is written | The short text describes the object sufficiently | |
| 451 | 776 |
Archive file &/& cannot be opened, reload canceled | The short text describes the object sufficiently | |
| 452 | 777 |
Error while reading the archive | The short text describes the object sufficiently | |
| 453 | 778 |
Archive statistics cannot be generated | The short text describes the object sufficiently | |
| 454 | 779 |
New archive file cannot be created, reload canceled | The short text describes the object sufficiently | |
| 455 | 780 |
Archive variants cannot be read | The short text describes the object sufficiently | |
| 456 | 781 |
Error adjusting the archive index | The short text describes the object sufficiently | |
| 457 | 782 |
Reloaded archive data cannot be saved, structure: & | The short text describes the object sufficiently | |
| 458 | 783 |
No archive was found for the selection | The short text describes the object sufficiently | |
| 459 | 784 |
Logs for payment order & / & / & cannot be archived | The short text describes the object sufficiently | |
| 460 | 785 |
Archive file & was opened at offset & | The short text describes the object sufficiently | |
| 461 | 786 |
Archived data read for payment order & / & / & | The short text describes the object sufficiently | |
| 462 | 787 |
& payment orders are reloaded | The short text describes the object sufficiently | |
| 463 | 788 |
A new archive is created for & payment orders | The short text describes the object sufficiently | |
| 464 | 789 |
A new archive was successfully created, the index is adjusted accordingly | The short text describes the object sufficiently | |
| 465 | 790 |
Index data for the new archive has been adjusted | The short text describes the object sufficiently | |
| 466 | 791 |
Reloaded payment orders were saved | The short text describes the object sufficiently | |
| 467 | 792 |
Old archive file was closed | The short text describes the object sufficiently | |
| 468 | 793 |
Reload was completed successfully | The short text describes the object sufficiently | |
| 469 | 794 |
New archive file was opened | The short text describes the object sufficiently | |
| 470 | 795 |
Payment order & / & / & was written to the archive | The short text describes the object sufficiently | |
| 471 | 796 |
Archive index is created/adjusted for variant & | The short text describes the object sufficiently | |
| 472 | 797 |
Archive index has been created/adjusted for variant & | The short text describes the object sufficiently | |
| 473 | 798 |
The new archive file was closed successfully | The short text describes the object sufficiently | |
| 474 | 799 |
Archiving was successful, variant: &, test mode: & | The short text describes the object sufficiently | |
| 475 | 800 |
Payment order &1 cannot be archived due to its status | Space: object requires documentation | |
| 476 | 801 |
FINSTA bank statement IDocs are not compared | The short text describes the object sufficiently | |
| 477 | 802 |
Error when reading bank data for bank area & | The short text describes the object sufficiently | |
| 478 | 803 |
No IDoc found for bank &, account &, statement & / & | The short text describes the object sufficiently | |
| 479 | 804 |
Account amount & (from account &) cannot be converted | The short text describes the object sufficiently | |
| 480 | 805 |
Transaction amount & (from account &) cannot be converted | The short text describes the object sufficiently | |
| 481 | 806 |
SAP currency code & cannot be converted to ISO code | The short text describes the object sufficiently | |
| 482 | 807 |
No FINSTA IDoc is generated | The short text describes the object sufficiently | |
| 483 | 808 |
Duplicate creation was started for bank area &, account &, statement &/& | The short text describes the object sufficiently | |
| 484 | 809 |
No payment orders to be archived for the selection specified | Space: object requires documentation | |
| 485 | 899 |
Undefined error in FM &1. Inform SAP | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 500 |
