Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBAS (Package) Financial accounting 'Basis'
Basic Data
| Data Element | XRRES |
| Short Description | Indicator: Type of notice according to reason code |
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 | 20 | Acc.to reason code |
| Long | 30 | According to reason code |
| Heading | 20 | Acc.to reason code |
Documentation
Definition
Indicator that the type of payment notice which is to be sent due to a residual item, is dependent on the reason code.
Use
You can formulate the payment notices to the customer individually by distinguishing according to reason code.
Procedure
Select the field if you have defined special payment notices for all or at least for several reason codes.
Dependencies
A payment notice is only created according to reason code if the same type of payment notice was agreed for all reason codes occurring in the clearing procedure. If reason codes occur with different types of payment notices, the type of payment notice defined for the tolerance group is sent. This should be organized so that you can deal with all types of reasons.
If reason codes occur without allocated payment notices, the system also accesses the type of notice defined for the tolerance group.
History
| Last changed by/on | SAP | 19950401 |
| SAP Release Created in |
