Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FBZ (Package) Payments
Basic Data
Data Element | XUZAW |
Short Description | Usage of Payment Method Supplements |
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 | 10 | Pyt mth su |
Medium | 15 | Pyt meth suppl. |
Long | 20 | Paymt method suppl. |
Heading | 0 |
Documentation
Definition
Means that payments are to be separated in the document according to a preset characteristic.
Use
If you select this option, a payment method supplement can be predefined in the customers and vendors of the company code. This supplement is used to group payments. Payments are separated according to payment method supplements and can be printed separately by these supplements or sorted by them for printing. The payment method supplement is defaulted during document entry and can be overwritten there.
Procedure
Select this option if you want to use payment method supplements.
Examples
Checks to be sent to trading partners are not sent by mail but by means of internal mail and from there are sent via different channels depending on the payee. This procedure can be supported by payment method supplements. That is, a payment method supplement represents an internal mail channel. In the U.S.A. and Canada, such supplements are referred to as "mail stop codes".
History
Last changed by/on | SAP | 19991014 |
SAP Release Created in |