1J - BCA: Payment Order Dialog

The following messages are stored in message class 1J: BCA: Payment Order Dialog.
It is part of development package FKBP in software component IS-B-BCA-AM-IT. This development package consists of objects that can be grouped under "Bank Customer Accounts: Payment Item".
Message Nr
Message Text
001Bank key &1 for bank country/region &2 not found
002Internal no. / Role does not exist in table &1
003Cust. Amount Authorization incomplete for bank area &1, acct. type &2
004Acct. no. of ordering party and payee are identical
005Key fields cust. amount authorization incomplete for &1, acct. type &2
006Control of check digit for acct. no. &3, bank key &2, erroneous
007Enter account number
008Database error for BKK_PAYM_ORDER_UPDATE_ITEM
009Test ordering party
010Test payee position &1, account number &2
011Document type &1 does not exist
012No account holder found for account &1
013No authorization for release (account type &2, amount &4)
014Release not possible, must be done by another user
015Payment order &2 in bank area &1 already exists, error in no. assignment
016Transaction not allowed
017Activity &1 not found
018No authorization for release for account type &2
019Bank area for payee could not be determined
020No document group defined for document type &1
021Payment item &1 not found
022No trans. type for offsetting posting defined for trans. type &1
023Payment item &2 in bank area &1 can not be reversed
024Please choose a return reason
025Payment order &1 not found
026Payment order & locked for Postprocessing
027Error in testing payment item for ordering party
028Error in posting preparation of payment item for ordering party
029Error in posting payment item
030Error in testing payment item for recipient
031Error in posting preparation of payment item for recipient
032Error in external payment transactions system
033Dual control: Another user must release the payment order
034Error in issuing number for payment order
035Error in posting payment order
036Error in releasing payment order
037Payment item changed, save on CpD suspense account before posting
038Error in transfer of &1 &2 to &3 &4
039No valid return reason is defined for trans. type &1
040Payment order &2 in bank area &1 in postprocessing
041Payment order &2 in bank area &1 changed
042Payment order &2 in bank area &1 deleted
043Payment order &2 in bank area &1 released, all items posted
044Payment order &2 in bank area &1 - all items posted
045Payment order &2 in bank area &1 ready for release
046Posting preparation or posting of payment order was incorrect
047No errors arose during checks
048Payment order &2 in bank area &1 posted, item in postprocessing
049Payment order &2 in bank area &1 posted, item transf. to pay. transaction
050Payment item &2 in bank area &1 in postprocessing
051Payment item &2 in bank area &1 changed
052Payment item &2 in bank area &1 deleted
053Payment item &2 in bank area &1 released
054Payment item &2 in bank area &1 posted
055Payment item &2 in bank area &1 transferred for release
056Payment item &3 in bank area &1 reversed by reverse item &2
057Payment item &2 transfer posted and return posting created
058Payment item &2 in bank area &1 transfer posted, new payment item &3
059Payment item &2 in bank area &1 posted to CpD (suspense) account
060Return of payment item &2 in bank area &1 not possible
061Error occurred in payment transactions - no error message
062Due to the error, the document cannot be completely posted
063Function variant for document type &1 and activity &2 does not exist
064Return of payment item &2 is not possible (see long text)
065Return from partner account is not allowed for reason &1
066A return from the CpD (suspense) account is not allowed for reason &1
067Result of the Checks
068Error in notification of payment transaction module for item &1 &2
069Account holder of account &2 in bank area &1 could not be determined
070No direct debit order defined for transaction type &1
071Online entry of payment orders with transaction type &1 not allowed
072Online entry of payment item with transaction type &1 not allowed
073Payment order &2 in bank area &1 released, item in postprocessing
074Payment order &2 in bank area &1 released, item transferred to PT
075Return order &3 posted with all items for item &2
076Return order &3 for item &2 posted, item in postprocessing
077Return order &3 for item &2 posted, item transferred to PT
078Balance in payment order not zero. Please check customizing
079No Customizing of amount authorization for product &2, trans. type &3
080Payment order &2 posted in bank area &1 - communication error
081For transaction type &1 more than one offsetting trans. type determined
082Negative amounts not allowed in Customizing; Correct your entry
083Enter an amount between &1 and &2
084Payment order &2 in bank area &1 reversed
085Payment item &2 in bank area &1 rejected
086Account &1 is a CpD (suspense) account
087Value date changed: Original date &2 , new date &1
088Return not possible: Guarantee amount &2 is more than return amount &1
089System error in changing payment order &1 &2
090Enter another primary selection
091Selection area for account numbers too big; Restrict your selection
092Data selection terminated after &1 records
093Enter a selection condition
094Data selection terminated after &1 payment orders
095Return order &1 posted with all items
096Return reason &1 posted, item in postprocessing
097Return order &1 posted, item transferred to PT
098Return order &2 in bank area &1 transferred for release
099Return not possible as posting balance not cleared
100Error when writing change documents
101Error in updating payment order
102Recipient transaction type is missing
103Due to error, document cannot be posted
104&1 cannot be converted to &2
105Return order &1 posted - communication error
106Payment order &2 in bank area &1 released - communication error
107########Payment order &1
108######## Recipient item &1
109######## Ordering party: &1
110######## Recipient position &1: &2: Account number &3
111Error in changing payment order &1; You need to inform SAP
112You are not authorized to use this function in bank area &1
113No items exist for sending to the legacy system
114No external payment transaction system is connected
115There are no error messages
116Select a valid line
117Place the cursor on a valid column
118You are not authorized to process this payment order
119Planned item &1 entered in bank area &2
120Payment item &1 in bank area &2 in queue for posting later
121Enter account holder name
122& items were not processed
123Change not possible
124Forward order &2 entered in bank area &1
125Forward order &2 changed in bank area &1
126Forward order &2 transferred for release in bank area &1
127Forward order &2 in bank area &1 for release after change
128Forward order &2 deleted in bank area &1
129Forward order &2 in bank area &1 for release after deletion
130Forward order &2 released in bank area &1
131No tolerance period maintained in bank area &1 for forward orders
132Date &1 is under future tolerance date &2
133Date &1 is under future tolerance date &2
134Forward order &1 cannot be deleted
135Forward order &1 not in bank area &2
136Payment item &2 in bank area &1 transferred for release to be deleted
137Payment item &2 in bank area &1 transferred to be returned for release
138Payment item &2 in bank area &1 transferred for release to be reversed
139Payment item &2 in bank area &1 transferred for release for transfer post
140Payment order: Variant selection only allowed for account &1
141Account: &1 Certificate No./Notice No.- &2 -> No forward order
142Payment order &1: There is no header data
143Payment order &1: There is no position data for the recipient
144Payment order &1: There is no data for the payment notes
145Payment order &2 in bank area &1 transferred for release for reversal
146Payment order &2 in bank area &1 transferred for release to be deleted
147Payment order &2 in bank area &2 released for reversal
148Payment order &2 locked in bank area &1; Posting now not possible
149Payment order &2 in bank area &1 has a new status: Already posted
150Payment order &2 in bank area &1 released for deletion
151Partial returns are not allowed for return reason &
152Cannot reject release for payment order &1 bank area &2
153Release rejected for payment order &1 bank area &2; Status new - &3
154Error during rejection of release for payment order &1, bank area &2
155Release rejected for forward order &1, bank area &2; Status new: &3
156Error during rejection of release for forward order &1, bank area &2
157Deleting planned payment order &1 in bankarea &2 not successful
158Transf. data paym.item &1 &2 changed. Paym. Item transferred for release
159Forward order &1 &2 not executed with formal error
160Autom. payt order/forward order not maintained in BkAr &1 for prod. &2
161Balance in forward order &1 &2 not zero; Check Customizing settings
162Payment order &1 flagged for deletion; Cannot be changed
163Forward order &1 flagged for deletion; Cannot be changed
164No changes were made
165User cancelled the release
166# # # # # # # Forward Order &1 &2 # # # # # # #
167Forward Order &1 &2 executed
170Complete the recipient bank details
171There is no BIC number defined in the BNKA table for bank &1
172BIC &1 is not the same as the BIC defined for bank &2 &3
180Ext.Payment Order & / &: &. (Account &).
181Payment order &2 posted in bank area &1; See long text for transfer info.
190Account number contains invalid characters
199Payment amount contains invalid characters
200Error during conversion of standing order &1 account &2
201Standing order &1 for account &2 successfully converted
202&1 standing orders successfully converted
203&1 standing orders could not be converted
204*........... start euro conversion for standing orders
205*........... simulation run
206Transation amount and currency old: &1 &2 ; amount in euro &3
207Base amount and currency old: &1 &2 ; amount in euro &3
208Minimum amount and currency old: &1 &2 ; amount in euro &3
209&1 standing orders read for &2 accounts
210&1 standing orders successfully converted to euro
211&1 standing orders could not be converted
212Currency conversion &1 ended
220*........start of euro conversion for direct debit orders
221Direct debit order &1 for account &2 &3 could not be converted
222Direct debit orders for account &1 &2
223*------------------------------------------------------------------------
224Direct debit order &1 from &2 &3 converted to &4 euro
225&1 direct debit orders read
226&1 direct debit orders successfully changed
227&1 direct debit orders could not be converted
228You are not authorized to convert the currency for &1
240*........Start Direct Debit Orders
241The maximun number of direct debit orders has been reached
250No forward order that can be executed for amount notice &1
251No forward order that can be deleted for amount notice &1
280PO &2 in bank area &1 and its payment items sent to PTS
281PO &2 in bank area &1 sent to PTS; See long text for transfer information
282PO &2 in bank area &1 sent to PTS; Communication error
283PO &1, bank area &2, acct &3 and its payment items sent to PTS
284PO &1, bank area &2, acct &3 sent to PTS; PIs still to be sent to PTS
285PO &1 in bank area &2, acct &3 sent to PTS; Communication error
300*------ Start messages for standing orders
301# # # # # # # Account: &1, standing order number : &2 # # # # # # #
302Standing order &2 for account &1 is being processed by user &3
303# # # # # # # Selection of standing orders # # # # # # #
304# # # # # # # Result of processing # # # # # # #
305Standing order &1 deleted - display only possible
306Payment note line &1 not found
307Standing order &1, acct &2 has no trans. type for the offsetting posting
308Standing order &1 flagged for deletion - changing not possible
309A standing order is being created by user &1 for this account
310* Standing order BP tool
311Standing order data transferred
312No authorization to create standing order with authorization type &1
313No authorization to change standing order with authorization type &1
314No authorization to display standing order with authorization type &1
315Standing order number assigned during saving
316Change might not be taken into consideration today
317Standing order might not be posted today
318Next run date has changed
319Key date is invalid
320Error in calculating next run date
321No authorization to delete standing order with authorization type &1
322Activity category &1 is not planned for direct input
323The next run date does not correspond to the period data
324No authorization to release standing order with authorization type &1
325Recipient account &1 does not exist
326Standing order succesfully transfer posted
327# # # # # # Selektion Standing Orders - Packagebuilding # # # # #
329In &1 packages &2 standing orders selected
345Payment order &2 in bank area &1, items transferred to PTS
399* End of messages for standing orders
400Select an account
401You can only select one account
402No &2 could be selected in bank area &1
403No product has been assigned to bank area &1 (Customizing)
404No &1 could be selected in the chosen bank areas
405Missing import parameter &1
406Error in determining the posting date for bank area &1
407Different standing order number in range and standing order selection
408Enter valid bank area
409Select a partner bank from the list box
410PO &1 posted in bank area &2, account &3, item in postprocessing
411PO &1 posted in bank area &2, account &3, item transferred to PTS
412PO &1 posted in bank area &2, account &3, communication error
413PO &1 posted in bank area &2, account &3 with all items
414PO &1 posted in bank area &2, account &3. rcp.item transfer (PTS) pending
415Payment order &2 in bank area &1 released, item transfer to PTS pending
420Postprocessing not possible for current status
450Report &1 has already started
451Error during update of table &1
460Processing of parked payment items finished
491Enter an additional account selection parameter
492Maximum number of &1 data records read, &2 valid data records found
502Invalid value
509Error in recipient bank details
510Enter the bank key
511Enter a bank country/region
512Enter the SWIFT code
513Enter the IBAN
514SWIFT code &1 does not match bank country/region &2 or bank key &3
515Check (PF) number is missing
516Enter payment method
517Enter medium
518Creditor ID not transferred
519Item SWIFT code &1 does not match the mandate SWIFT code
520Mandate ID not transferred
521SWIFT code &1 does not match the SWIFT code of bank &2-&3 (&4)
570### SEPA CUSTOMIZING CHECKS ###
571Enter missing values for transaction type &1
572Select the 'SendTo PTS' checkbox
573SEPA Ordering party customizing not maintained for transaction type &1
574Missing customizing for transaction type &1 and mandate type &2
575SEPA Recipient party customizing not maintained
576Archiving period cannot be maintained for the object FIBA_ENRCH
600### SEPA Mandate Payment Order Checks ###
601Mandate reference &1 is the same for different recipients
602Mandate reference &1 is currently locked by user &2 for editing
603Mandate reference &1 uses a different UCI
604Enter the mandate reference
605Enter the creditor ID
606Status of mandate &1 is not active
607Global lock defined for creditor ID &1
608Mandate &1 with creditor ID &2 does not exist for IBAN &3
609Mandate checks failed; Payment order could not be created
610Mandate &1 is not valid on posting date &2
611Mandate &1 is not valid on due date &2
612The one-time mandate &1 has already been used
613Minimum number of days &1 more than maximum number of days &2
614Mandate order type for &1 should be recurring for a standing order
615Error in updating the usage for mandate &1
616Mandate checks failed; Standing order could not be created
617Mandate checks failed; Standing order could not be executed
618The BP of the ordering party &1 does not match the BP of mandate &2
619Internal error while updating the mandate usage
620Mandate check enabled for ordering party transaction type &1
621Only recurring mandates allowed for standing orders
622The mandate &1 is obsolete
623Mandate type &1 cannot be used with offsetting transaction type &2
624Customer validation of BIC and IBAN failed
625Enter a due date that is after the due date &1 of the first collection
626Payment order not Found
627Due date must be on or after the due date of the first collection (&1)
628Account currency should be EUR for collection with SEPA payment method
629Due date must be on or after &1 (first due date &2 plus time lag &3)
630Customer determination of SEPA mandate type failed
631Mandate &1 not valid on due date &2 calculated based on posting date &3
632Calculated due date based on closure dt &1 must be after 1st coll.date &2
633Mandate &1 is not valid on planned closure date &2
634Mandate &1 is not valid on due date &2 based on planned closure date &3
635Calculated due date based on posting dt &1 must be after 1st coll.date &2
636SDD checks use posting date &1 as planned closure date not entered
637Mandate checks use posting date &1 as planned closure date not entered
638SDD checks use posting date &1 as next balancing date not available
639Mandate checks use posting date &1 as next balancing date not available
640### SEPA Direct Debit Payment Order Checks ###
641Enter missing fields for payment method &1
642Number of minimum days cannot be greater than number of maximum days
643Payment control of payment method &1 not "According to SEPA" in Cust.
644Enter the due date of the SEPA direct debit order
645Due date &1 falls on a non-working day
646Processing days missing in Customizing for payment method &1
647Posting date &1 is before the earliest posting date &2
648Posting date &1 is after the latest posting date &2
649Enter transaction currency EUR for all SEPA direct debit orders
650Transaction currency is missing
651Earliest posting date &1 is after latest posting date &2
652The SEPA direct debit order cannot be posted until &1
653Next run date &1 is after the latest posting date &2
654Next run date &1 before the earliest posting date &2
655Due date &1 cannot be before posting date &2
656Due date &1 does not correspond to period data
657Error in calculating next run date and due date for subsequent run
658BAdI implementation not available for calculating next run and due date
659The reference variable for BAdI & was not instantiated
660Latest posting date could not be determined for due date &1
661Backdated posting is not allowed for SEPA direct debit orders
662System calculated next run date for &1 and due date for &2
663BIC and IBAN mandatory for recipient identification in SEPA direct debits
664Error occurred during calculation of next run date and due date
665System calculated next run date for &1
666Current posting date &1 is on or after the latest posting date &2
667### SEPA Standing Order Checks During Current Execution ###
668### SEPA Standing Order Checks During NextRun & DueDate Calculation ###
669Next run date &1 is on or after the latest posting date &2
670The earliest possible due date is &1 for posting date &2
671Enter a valid due date that considers the setting for maximum days of &1
672Enter a valid due date that considers the minimum days of &1
673The latest due date for posting date &1 can be &2
674A SEPA order cannot be created for an account not managed in euro
675Prenote could not be created
676The prenote is not for a credit transaction
677More than one active implementation of BAdI BADI_BKK_POPOSTPROC_DISPLAY
678Mandate not unique (MNDID = &1, UCI = &2)
679More than one active implementation of BAdI: Validation of IBAN and SWIFT
680### SEPA Direct Debit Forward Order Checks ###
681Forward order cannot be created on &1; Try to create a payment order
682Customer method deriving the BIC terminated with RC = &1
683Mandate &1 with creditor ID &2 not found
701Error preparing data for enrichment (MGUID = &1)
702Error mapping enrichment data (MND &1, UCI &2, PO_MGUID/MVERS &3/&4)
703Error sending enrichment data to external system
704Enrichment data could not be saved
705Error updating mandate frequency (MND = &1, UCI = &2, MGUID = &3)
706Mandate not found (MNDID = &1 UCI = &2)
730There is no default offsetting transaction type for transaction type &1
800IBAN &1 is not maintained in the recipient account for BP &2
898Selection: Place at which TCUR=ACUR is assumed (only for 1.0)
899System error: &1 &2 &3 &4
Privacy Policy