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