BNK_GENERAL - Common messages for Bank communication
The following messages are stored in message class BNK_GENERAL: Common messages for Bank communication.
It is part of development package FIN_BNK_COM_CORE in software component FIN-FSCM-BNK. This development package consists of objects that can be grouped under "Bank Communication: Core Objects".
It is part of development package FIN_BNK_COM_CORE in software component FIN-FSCM-BNK. This development package consists of objects that can be grouped under "Bank Communication: Core Objects".
Message Nr ▲ | Message Text |
---|---|
000 | Update error encountered on table &1 |
001 | Update error encountered in delete operation on table &1 |
002 | No rule found in the database. |
003 | Rule &1 not found |
004 | No rule found for structurename &1 |
005 | Select a valid line |
006 | Update error encountered in insert operation on table &1 |
007 | Application FI-BNK is not active |
008 | An internal error has occurred in function module &1; contact sys admin |
009 | Matching rule not found. |
010 | No sufficient authorizations to read all the existing batches. |
011 | Rule: &1 &2 |
012 | Save the rule &1 before you maintain it. |
013 | No authorization for line items. |
014 | Date should be greater than current date |
015 | No payment items for the selected batches |
016 | No batch rule applies to &1 &2 in &3 &4. |
017 | Maintain Grouping Field 1 before 2. |
018 | Grouping fields &2 &3 too long (&4 > &1) |
019 | No automatic transport for Batching Rules (use RBNK_RULE_TRANSPORT) |
020 | Message processing is not successful |
021 | No Incoming Status Message for the batch &1 |
022 | No Recent Status Reason Codes for the batch &1 |
023 | Codepage for format &1 not defined |
024 | No Additional Remittance Infor for the batch &1 |
025 | Rule &1 must be unique |
026 | No authorization to display the file |
030 | No authorization to create an HMAC key |
031 | Sender SWIFT code is missing or last characters not 'XXX' |
032 | Receiving house bank SWIFT code is missing |
033 | Entry &1 is missing in table &2 |
034 | Entry is missing in table SSFAPPLIC |
112 | Error when creating the collector & & |
114 | Collector &1 &2 was created or updated |
118 | Collector program is started in separate job |
120 | Batches are created for Collector &1 &2 |
121 | Batches are created for &1 Collectors |
122 | HMAC Key successfully set |
123 | No Batch created in Format &2 |
124 | Not all batches are created: Check application log |
200 | Approve Batch &1 &2 |
201 | Resubmit Batch &1 (new &3) &2 |
202 | Reject Batch &1 &2 |
203 | Resubmit Payment &1 (Batch &2)(new &4) &3 |
204 | Reject Payment &1 (Batch &2) &3 |
205 | Some of the batches chosen are locked for further processing |
206 | No file created yet |
207 | No suitable records were found |
208 | Reason: &1 |
209 | No reason was given |
210 | Return Batch &1 &2 |
211 | Refresh not possible: Changes must be saved |
212 | Mark exactly one line |
213 | Returned batch &1: Batch must be processed individually |
214 | Payment &1 &2 should be manually reversed (FBRA) |
215 | Batch &1 taken over from user &2 |
216 | No authorization to maintain signature users |
217 | Instruction code changed for &1 (Batch &2): Old &3 New &4. |
218 | Batch &1: No processing w/o prior drilldown |
219 | No signature user is assigned to &1. |
220 | No due date in Batch &1. |
221 | Continue and enter a reason for returning batches |
222 | No authorization to confirm signature users |
223 | Attention Batch &1 : File &2 &3 not yet created |
224 | Reject Batch &1 by using transaction BNK_APP directly |
225 | Unable to resubmit a SEPA direct debit |
226 | Payment(s) rejected in BCM; trigger follow-on activities in HR |
227 | You have already edited batch &1 in the approval process |
228 | Returned batch &1: All payments must be processed together |
229 | Delete the line on the detail screen of the dynamic selection |
230 | Do not change value date or instructions after first approval |
231 | Batch &1 cannot be returned: Same user in next step |
232 | You can't resubmit batches created in ext.system. Change your selection. |
233 | You can't resubmit batch &1, because it was created in external system. |
234 | You can't change the instruc.key of batch &1 created in external system. |
235 | Resending is not possible for batch &1 created in &2. |
236 | Resending is not possible for batch &1 because of status: &2. |
237 | Action was cancelled by user. |
238 | You have no authorization for resending this payment batch. |
239 | Application log for payment batch &1 was not found. |
240 | User &1 has triggered resending of payment batch &2. |
241 | Check possible risk of additional payments for already paid transactions. |
242 | Payment medium creation was scheduled as a background job. |
243 | Payment medium was created for payment batch &1. |
244 | Error occurred during payment medium creation for payment batch &1. |
245 | Payment medium will be created for payment run &1 with ID &2. |
246 | User &1 has triggered the sending of payment batch &2. |
247 | Open jobs exists for for batch &1 (check SM37 PAYM:&2/&3*). |
280 | Maximum posting amount is 13 digits 2 decimals. |
281 | The FI-BNK can process documents with amount of 13 digits at maximum. |
282 | The amount in Payment Doc.No. &1 in company code &2 is too high. |
283 | The Appl. FI-BNK is active. Maximum amount is 13 digits including 2 dec. |
301 | Data not saved. Check company code &1 and house bank ID &2. |