Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VEI (Package) Application development R/3 foreign trade
Basic Data
Data Element | SLNKA |
Short Description | Max. no. of key words for addresses of the Sanct. Party List |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DEC4 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 5 | |
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 | Addr.: KW |
Medium | 15 | Addr.: No. KW |
Long | 20 | Addr.: No. key words |
Heading | 40 | Addresses: Max. number of key words |
Documentation
Definition
In this field, you can determine the max. number of search terms to be generated per address for an SLS master date.
The more search terms you allow per address, the more precise the SLS check. But the system load grows correspondingly and the program takes longer to carry out the SLS check.
The lower the number of search terms you allow per address, the less precise the SLS check; the runtime of the check, however, decreases correspondingly.
Note
The runtime as well as the number of search terms are depending on the number of SLS entries and the number of the partner master records to be checked.
To realize an efficient SLS check, you should carry out some testruns of the SLS check with respectively different values for the number of search terms. You should select the value for which the SLS check runs fastest.
History
Last changed by/on | SAP | 19990827 |
SAP Release Created in |