Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FREP (Package) RF reporting
Basic Data
| Data Element | FORDBEIN |
| Short Description | Payment Notice Information |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 0 | |
| Heading | 0 |
Documentation
Definition
The value in this field determines the information that the vendor receives with his bank transfer from your company.
If you pay more items than there are space for (too many items per payment document), the program issues the message "You will be sent more information by post".
The following fields and values are defined:
Value field, length (1)
1 reference number (2) 16
2 reference number and payment amount 16 + 10-12 + 1
3 reference number and payment date 16 + 6 +1
4 document number 10
5 segment text 50
6 user-determined text (selection screen) (maximal 90)
7 allocation 16
8 reference number (10 characters) 10
The maximum length of the message for domestic payments is 105 and for foreign payments 140. For domestic payments with a structured message, the reference number must always be entered in the format '+++1234567890XX', where XX must be a valid check digit from the ten preceeding digits. For payments to accounts that begin with 99x-, only 53 spaces are available for the message. On the basis of these figures, you can calculate how many items should be placed in each form in the company code payment method and then send all the messages by DME along with the payments.
(1) Each individual portion of information is separated from that preceeding it by a comma.
(2) If not given, the document number is supplied by the system.
History
| Last changed by/on | SAP | 19950401 |
| SAP Release Created in |
