Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FBZ (Package) Payments
Basic Data
Data Element | FORDKEY2 |
Short Description | New Key for Table Access |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR15 | |
Data Type | CHAR | Character String |
Length | 15 | |
Decimal Places | 0 | |
Output Length | 15 | |
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 | Key |
Medium | 15 | Search key |
Long | 20 | Extra keys |
Heading | 15 | Search key |
Documentation
Definition
When a data medium is created in Great Britain, bank data is read from various tables:
- User number at the bank
- Bank transaction codes for each bank
- Bezeichner für Banktransaktionscodes
When accessing these tables, the standard system requires that the key field Bank number is blank. All the table entries should also be blank.
If you want to us the BACS multi user functionality, you must define a second user number in the table User numbers at the bank. To do so, specify a second key in the bank number field which should be entered when creating future data media.
All the table entries are maintained separately for several users. Copy the existing entries (bank transaction codes , Bezeichner) for the second search key and modify the data where necessary for the second user.
Effects on Customizing
The following entries must have been made for the search key specified:
- User number at the bank
- Bank transaction codes to be used
- Bezeichner für die Banktransaktionscodes in Landessprache
History
Last changed by/on | SAP | 19960115 |
SAP Release Created in |