Hierarchy
FI-CA (Software Component) FI-CA⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable⤷
FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
| Data Element | XNEWBV_KK |
| Short Description | Reaction to Changed Bank Details Returns |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XNEWBV_KK | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Check Bk |
| Medium | 13 | Check Bk Chge |
| Long | 31 | Check Changed Bank Details |
| Heading | 10 | Check Bk |
Documentation
Definition
Triggers a check of whether the customers bank details have changed.
Use
The data from the payment run (bank number and account) is compared with the current data for the contract account (bank number and account).
Note
If the payment data has already been deleted, this check is not carried out.
If you have entered a different returns reason, the activities for this returns reason are carried out. If the field is empty, you can fill the new activities yourself in event 0293.
Note
Alternative returns reason:
Make sure that the alternative returns reason contains the same specifications in Customizing (company code, house bank, creditworthiness, number of returns, tolerance group).
Irrespective of this restriction, the returns charges are calculated according to the specifications defined in Customizing. If you do not want this, write an installation-specific function module and define it for event 0260. You can use the coding in the module FKR2_Activities_Process in form CHECK_BANK_CHANGES as a template.
Dependencies
Rules for returns charges for event 0260.
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 471 |
