Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBM (Package) Dunning 
Attribute
| Message class |  |
F0 | |
| Short Description |  |
FI batch program messages | |
| Message Number |  |
468 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20130531 |
Message Text
Help Document
Diagnosis
There is a check routine defined in the system for country . When this routine was used for the entry , it found an error.
The error may be the result of an incorrect check digit. Other causes may be an incorrect field length (the number is too great, or the value too short) or the use of a character which is not permitted (an alphanumeric value in a numeric field, for example).
With the bank checking account procedure in Sweden, a 'hard' check is allowed, but also a 'soft' check is allowed.
'Hard' Check
The bank rejects an incorrect payment reference and a missing payment reference.
'Soft' Check
The bank also accepts an incorrect payment reference or a different, alternative payment reference.
Accordingly, this message is an error message in the standard system (-> 'hard' check), but you can change it in transaction OBA5 to a warning message (-> 'soft' check), so that when entering an incoming invoice with an incorrect payment reference, the user receives a warning message stating that the payment recipient expects a correct payment reference when they check. As a result, the user should possibly change the payment reference. However, the posting of the incoming invoice can still be made if the payment reference is not changed.
System Response
Procedure
Check whether the number was transferred correctly from the original document.
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in |
