SAP ABAP Message Class FVD_SEPA (Message Class for SEPA Developments in CML)
Basic Data
Hierarchy
☛
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
⤷
FS-CML (Application Component) Loans Management
⤷
FVVD (Package) Treasury Loans
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FS-CML (Application Component) Loans Management⤷
FVVD (Package) Treasury Loans 
Attributes
| Message class |  |
FVD_SEPA |
| Short Description |  |
Message Class for SEPA Developments in CML |
| Changed On |  |
20131127 |
| Last Changed At |  |
181842 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  001 |
Remittance info cannot be processed (SEPA not active for comp. code &1) | The short text describes the object sufficiently | |
| 2 | 002 |
Please select only one row for entering SEPA remittance information. | The short text describes the object sufficiently | |
| 3 | 003 |
No valid mandate exists | The short text describes the object sufficiently | |
| 4 | 004 |
Mandat ID not entered if SEPA not active | The short text describes the object sufficiently | |
| 5 | 005 |
No mandate ID entered if payment method is not EDD | The short text describes the object sufficiently | |
| 6 | 006 |
Mandate ID not entered for payment method EDD | The short text describes the object sufficiently | |
| 7 | 007 |
Reference ID for selected mandate ID could not be saved | The short text describes the object sufficiently | |
| 8 | 008 |
Do not enter EDD payment if SEPA not active | The short text describes the object sufficiently | |
| 9 | 009 |
Mandate &1 for bank ID &2 is not valid | The short text describes the object sufficiently | |
| 10 | 010 |
Specify a payment method | The short text describes the object sufficiently | |
| 11 | 011 |
No input help exists for non-EDD payment method | The short text describes the object sufficiently | |
| 12 | 012 |
Table for SEPA mandate is locked | The short text describes the object sufficiently | |
| 13 | 013 |
Return reason &1 does not exist | The short text describes the object sufficiently | |
| 14 | 014 |
Company code &1/contract &2: BIC could not be determined | The short text describes the object sufficiently | |
| 15 | 015 |
Enter an IBAN determination type | The short text describes the object sufficiently | |
| 16 | 016 |
Enter a bank key | The short text describes the object sufficiently | |
| 17 | 017 |
No SWIFT code available for bank &1 &2 | The short text describes the object sufficiently | |
| 18 | 018 |
IBAN &1 is not valid (customer-spec. check) | The short text describes the object sufficiently | |
| 19 | 019 |
No SWIFT code available | The short text describes the object sufficiently | |
| 20 | 020 |
Company code &1/contract &2: IBAN could not be determined | The short text describes the object sufficiently | |
| 21 | 021 |
IBAN determination not supported for product category &1 | The short text describes the object sufficiently | |
| 22 | 022 |
IBAN determination type &2 not supported for product category &1 | The short text describes the object sufficiently | |
| 23 | 023 |
&1 is not a valid value for the mandate type | The short text describes the object sufficiently | |
| 24 | 024 |
Framework mandate; do not assign a contract number | The short text describes the object sufficiently | |
| 25 | 025 |
Mandate &1 (&2/&3) is not valid for contract status &4 | The short text describes the object sufficiently | |
| 26 | 026 |
Mandate &1 (&2/&3) is not valid on &4 | The short text describes the object sufficiently | |
| 27 | 027 |
Mandate lead time requires at least payment date &1 | The short text describes the object sufficiently | |
| 28 | 028 |
Mandate lead time requires at least payment date &1 (cond. type &2) | The short text describes the object sufficiently | |
| 29 | 029 |
Prenotification period requires at least payment date &1 (cond. type &2) | The short text describes the object sufficiently | |
| 30 | 030 |
Error in customer-specific check (sender BIC) (CoCode &1, contract &2) | The short text describes the object sufficiently | |
| 31 | 031 |
&1 could not be determined (&2) | The short text describes the object sufficiently | |
| 32 | 032 |
Enter the BIC or the country | The short text describes the object sufficiently | |
| 33 | 033 |
Specify the data for the prenotification period | The short text describes the object sufficiently | |
| 34 | 034 |
Prenotification period requires at least payment date &1 (cond. type &2) | The short text describes the object sufficiently | |
| 35 | 035 |
Specify a finance project | The short text describes the object sufficiently | |
| 36 | 036 |
Only mandate type 3 is permitted if a finance project is specified | The short text describes the object sufficiently | |
| 37 | 100 |
Payment not available | The short text describes the object sufficiently | |
| 38 | 101 |
Country or company code not available | The short text describes the object sufficiently | |
| 39 | 102 |
Payment method &1/country &2/partner &3; error in BAdI check | The short text describes the object sufficiently | |
| 40 | 103 |
No partner or FI customer available | The short text describes the object sufficiently | |
| 41 | 104 |
Payment method &1/country &2/partner &3; error during SEPA CT check | The short text describes the object sufficiently | |
| 42 | 105 |
IBAN not specified in bank data &1 for partner &2 | The short text describes the object sufficiently | |
| 43 | 106 |
No partner bank type available | The short text describes the object sufficiently | |
| 44 | 107 |
No IBAN available (&1 &2 &3 &4) | The short text describes the object sufficiently | |
| 45 | 108 |
Payment method &1/country &2; error in BAdI check | The short text describes the object sufficiently | |
| 46 | 109 |
Payment method &1 (country &2) can be used for SEPA returns only | The short text describes the object sufficiently | |
| 47 | 110 |
Use a payment method for SEPA returns | The short text describes the object sufficiently | |
| 48 | 111 |
No SEPA return reason available | The short text describes the object sufficiently | |
| 49 | 112 |
No SEPA transaction ID available | The short text describes the object sufficiently | |
| 50 | 113 |
No IBAN available | The short text describes the object sufficiently | |
| 51 | 114 |
Use a payment method for SEPA transfers | The short text describes the object sufficiently | |
| 52 | 115 |
Payment method can be used for SEPA transfers or returns but not both | The short text describes the object sufficiently | |
| 53 | 116 |
&1 could not be determined; check this manually | The short text describes the object sufficiently | |
| 54 | 150 |
Company code &1 / contract &2: change to SEPA-relevant data | The short text describes the object sufficiently | |
| 55 | 151 |
SEPA data could not be determined (&1, partner &2, customer &3) | The short text describes the object sufficiently | |
| 56 | 152 |
Change in &1 (partner &2, customer &3) | The short text describes the object sufficiently | |
| 57 | 153 |
Error during update (company code &1, contract &2, &3) | The short text describes the object sufficiently | |
| 58 | 154 |
Change to SEPA-relevant data (&1 &2 &3) | The short text describes the object sufficiently | |
| 59 | 155 |
Mandate &1 does not exist (customer &2, bank details &3) | The short text describes the object sufficiently | |
| 60 | 156 |
Mandate &1 (partner &2, customer &3) already used in contract &4 | The short text describes the object sufficiently | |
| 61 | 157 |
No data was selected to change | The short text describes the object sufficiently | |
| 62 | 160 |
Error while saving payment data (&1) | The short text describes the object sufficiently | |
| 63 | 161 |
Payment data was changed | The short text describes the object sufficiently | |
| 64 | 200 |
Repeated auto debit can only be used with active SEPA enhancements | The short text describes the object sufficiently | |
| 65 | 201 |
Data could not be saved (&1 &2 &3) | The short text describes the object sufficiently | |
| 66 | 202 |
Repeat auto debit (&1 - &2 - &3) | The short text describes the object sufficiently | |
| 67 | 203 |
Company code &1 / contract &2: &3 | The short text describes the object sufficiently | |
| 68 | 204 |
&1 data records to be checked (&2) | The short text describes the object sufficiently | |
| 69 | 205 |
Repeat auto debit is not active (company code &1) | The short text describes the object sufficiently | |
| 70 | 206 |
A payment block has not been specified for the repeat auto debit | The short text describes the object sufficiently | |
| 71 | 207 |
FI document does not exist (CML &1 &2 - FI &3 &4) | The short text describes the object sufficiently | |
| 72 | 208 |
FI document is not unique (CML &1 &2 - FI &3 &4) | The short text describes the object sufficiently | |
| 73 | 209 |
Error during update (contract &1, module &2) | The short text describes the object sufficiently | |
| 74 | 210 |
Item 1 &2 &3 saved for repeat auto debit (no. &4) | The short text describes the object sufficiently | |
| 75 | 211 |
Item 1 &2 &3 not saved (no. &4 >= max. number) | The short text describes the object sufficiently | |
| 76 | 212 |
Item &1 &2 &3 not processed (&4) | The short text describes the object sufficiently | |
| 77 | 213 |
An implementation does not exist for BAdI &1 | The short text describes the object sufficiently | |
| 78 | 214 |
Item &1 &2 &3 was processed | The short text describes the object sufficiently | |
| 79 | 215 |
Error during update (finance project &1, module &2) | The short text describes the object sufficiently | |
| 80 | 216 |
Company code &1 / finance project &2: &3 | The short text describes the object sufficiently | |
| 81 | 217 |
Maximum lead time could not be determined | The short text describes the object sufficiently | |
| 82 | 218 |
No flows found for returns (&1 &2) | The short text describes the object sufficiently | |
| 83 | 219 |
Company code &1 / finance project &2: &3 | The short text describes the object sufficiently | |
| 84 | 220 |
Item &1 &2 &3: correspondence created, collection date &4 | The short text describes the object sufficiently | |
| 85 | 221 |
Item &1 &2 &3 set to completed (&4) | The short text describes the object sufficiently | |
| 86 | 222 |
Item &1 &2 &3: payment block was removed | The short text describes the object sufficiently | |
| 87 | 223 |
Error while creating correspondence (method NAD_EVT_CORR_CREATE) | The short text describes the object sufficiently | |
| 88 | 224 |
&1 data records saved for the repeat auto debit | The short text describes the object sufficiently | |
| 89 | 225 |
No authorization (object &1, activity &2) | The short text describes the object sufficiently |
History
| Last changed on/by | |
20131127 | SAP |
| SAP Release Created in |
