| 67_PAYMENTS511 |
Limit value missing in table TZB41 for key & / & / & / & |
| 67_PAYMENTS512 |
Error when creating a planned record for clearing a receivable |
| 67_PAYMENTS513 |
Error when creating a planned record for clearing a payable |
| 67_PAYMENTS514 |
No clearing for customer & due to check module & |
| 67_PAYMENTS515 |
No clearing for contract & due to check module & |
| 67_PAYMENTS516 |
Error when reading the master data for the product types |
| 67_PAYMENTS517 |
Error when reading the master data for the product types per BUKRS |
| 67_PAYMENTS518 |
Only product types with the same payment lock are processed |
| 67_PAYMENTS519 |
No account clearing in contract &1: Items total &2 &3 limit value &4 |
| 67_PAYMENTS520 |
No processing in contract &1 as remaining capital <> 0 |
| 67_PAYMENTS521 |
No clearing in contract &1 in &2 - item total &3 limit &4 |
| 67_PAYMENTS522 |
Company code &, loan &: function only possible for loans given |
| 67_PAYMENTS599 |
*** Reservation end account clearing up to 599 ************** |
| 67_RFC000 |
*** General RFC Messages************************************************* |
| 67_RFC001 |
An error has occurred but no message exists |
| 67_RFC002 |
Message &1 of message class &2 does not exist in language &3 |
| 67_RFC003 |
Error in application function &1 &2 &3 - message follows |
| 67_RFC004 |
Error when converting import parameters to SAP internal format |
| 67_RFC005 |
No authorization for authorization object &1 field &2 value &3 |
| 67_RFC006 |
Contradiction in transfer parameters - detailed message to follow |
| 67_RFC007 |
Mandatory field &1 is empty |
| 67_RFC008 |
Duplicate entry in table &1 lines &2 and &3 |
| 67_RFC009 |
Parameter & does not contain entries |
| 67_RFC011 |
Invalid value for &1: &2 - check table &3 |
| 67_RFC012 |
Invalid value for &1: &2 - Fixed value for domaine &3 |
| 67_RFC013 |
&1: Value &2 without sufficient validity check, &3 unknown |
| 67_RFC015 |
The number of data records found exceeds &1 - is reduced to &2 |
| 67_RFC016 |
No selection parameters specified |
| 67_RFC017 |
No data was selected |
| 67_RFC050 |
Processing has been executed in simultation mode |
| 67_RFC051 |
Customizing settings have been calculated again |
| 67_RFC052 |
Duplicate entries have been deleted |
| 67_RFC053 |
Data has not been selected for all entries |
| 67_RFC099 |
*** Application-Specific RFC Messages********************* |
| 67_RFC100 |
*** Partner relationships *********************************************** |
| 67_RFC101 |
Partner relationship was not created |
| 67_RFC102 |
SAP BP &1 does not exist |
| 67_RFC103 |
Role category &1 for application category &2: &3 does not exist |
| 67_RFC104 |
Role category &1 : &2 for SAP BP &3 does not exist |
| 67_RFC105 |
Role type &1 for role category &2 : &3 does not exist |
| 67_RFC106 |
Role type &1 : &2 for SAP BP &3 with role category &4 does not exist |
| 67_RFC107 |
Relationship start date &1 is after relationship end date &2 |
| 67_RFC200 |
***RFC Messages for Collaterals****************************************** |
| 67_RFC201 |
You have not entered a collateral number |
| 67_RFC202 |
No collateral found for collateral number &1 |
| 67_RFC203 |
Collateral type does not exist in the SAP system - no receation for &1 |
| 67_RFC204 |
The &3 must be transferred for collateral type &1 and collateral cat. &2 |
| 67_RFC205 |
Collateral type &1, category &2 and transfer structure &3 do not match |
| 67_RFC206 |
No structure &3 has been transferred for collateral type &1 and cat. &2 |
| 67_RFC207 |
Table TD01 for collateral types is not maintained in the SAP system |
| 67_RFC208 |
Contract start date &1 is after the contract end date &2 in structure &3 |
| 67_RFC209 |
A contract total must be entered for collateral &1 |
| 67_RFC210 |
Contract contribution/premium &1 > contract total &2 in structure &3 |
| 67_RFC211 |
Error when checking currency key &1 in &2 |
| 67_RFC212 |
An amount in &1 must be entered for collateral &2 |
| 67_RFC213 |
Securities ID number (display PRF5) missing in field &1 structure &2 |
| 67_RFC214 |
A short description must be entered in &1 for collateral &2 |
| 67_RFC215 |
A collateral type must be entered in &1 for collateral &2 |
| 67_RFC216 |
Do not use collateral type 1000/1001 here - used for encumbrances |
| 67_RFC217 |
Insured total &1 in &2 for expiry data &3 must be > 0.00 |
| 67_RFC218 |
Insured sum &1 in &2 in line &3 for expiry data &4 must be > 0.00 |
| 67_RFC219 |
Currency key &1 for &2 in line &3 for special arrangement &4 is missing |
| 67_RFC220 |
Assign partner in &1 line &2 for special arrangement &3 |
| 67_RFC221 |
Error in number range object for : Partner &1 line &2 sy-subcr &3 |
| 67_RFC400 |
***RFC Messages for Collateral Objects/Encumbrances ******************** |
| 67_RFC401 |
Collateral object &1 does not exist |
| 67_RFC402 |
Neither an 'object number' nor an 'old object number' has been specified |
| 67_RFC403 |
Old collateral object &1 does not exist |
| 67_RFC404 |
The master number for objects is not defined in Customizing |
| 67_RFC405 |
'Create Object Master Number' flag set and master number &1 transferred |
| 67_RFC406 |
Multiple instances of old collateral object &1 |
| 67_RFC411 |
Error when assigning land register with TR BP &1 |
| 67_RFC412 |
Land register &1 and location &2 are different for TR BP &3 |
| 67_RFC416 |
No object assignment exists |
| 67_RFC417 |
No unique contract assignment |
| 67_RFC418 |
Object &1 does not have an object class |
| 67_RFC419 |
Object relationship for object &1 terminated on &2 |
| 67_RFC421 |
Collateral category &1 is not assigned to collateral type &2 |
| 67_RFC422 |
Tables for encumbrance have unequal number of entries |
| 67_RFC430 |
*** RFC Messages for Collateral Values ********************************** |
| 67_RFC431 |
No collateral values exist for collateral object & |
| 67_RFC450 |
Object assignment has not been created |
| 67_RFC451 |
Object &1 with object class &2 may not refer to reference object &3 |
| 67_RFC452 |
Object assignment to &1 ended - object class &2 is deleted |
| 67_RFC453 |
Object assignment ended on &1 - reference object &2 is deleted |
| 67_RFC500 |
*** RFC messages for contract ******************************************* |
| 67_RFC501 |
Several main borrowers exist |
| 67_RFC502 |
Condition header is not supplied with data |
| 67_RFC503 |
Combination of disbursement amount - disbursement indicator is incorrect |
| 67_RFC504 |
Date of end of fixed period is not the end of the month |
| 67_RFC505 |
Plausibility error in the condition header |
| 67_RFC506 |
VDARL incomplete |
| 67_RFC507 |
Bank details without partner |
| 67_RFC508 |
Multiply assigned &1 has been deleted |
| 67_RFC509 |
No authorization for company code & |
| 67_RFC510 |
Condition type &1 not permitted for repayment type &2 |
| 67_RFC511 |
Entry (&) not found in table (&) |
| 67_RFC512 |
No conditions exist for entry &1 &2 |
| 67_RFC530 |
Condition item for formula is missing: &1 &2 &3 |
| 67_RFC531 |
Formula &1 &2 specified more than once |