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