Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBZ (Package) Payments
Basic Data
| Data Element | XKIDS |
| Short Description | Separate Payment for each Payment Reference |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 30 | Separate payment for each ref. |
| Heading | 0 |
Documentation
Use
This indicator means that only invoices and credit memos which have the same payment reference can be settled with one payment.
Procedure
You should set this indicator if payment methods are used in your country where a payment reference is to be given for each payment.
Examples
Norway: Payment reference = KID number
Finland: Payment reference = Reference number
Dependencies
When dividing up payments by reference number, you should note that an outgoing payment cannot be generated for payment references which only refer to credit memos.
When payments are made by payment reference, offsetting between customers and vendors does not usually occur, unless the payment reference in a customer line item becomes the same as the payment reference in a vendor line item as a result of a change in the document.
History
| Last changed by/on | SAP | 19991014 |
| SAP Release Created in |
