SAP ABAP Data Element /SAPSLL/LLNSKW (Search Term for LLNS)
Hierarchy
☛
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation
⤷ SLL (Application Component) Global Trade Services
⤷ /SAPSLL/CORE (Package) Legal & Logistics Services: Global Basis
⤷ SLL (Application Component) Global Trade Services
⤷ /SAPSLL/CORE (Package) Legal & Logistics Services: Global Basis
Basic Data
Data Element | /SAPSLL/LLNSKW |
Short Description | Search Term for LLNS |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /SAPSLL/LLNSKW | |
Data Type | CHAR | Character String |
Length | 40 | |
Decimal Places | 0 | |
Output Length | 40 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | SPL_KEYWORD | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | SearchTerm |
Medium | 15 | Search Term |
Long | 20 | Search Term |
Heading | 7 | SrchTrm |
Documentation
Definition
To reduce the runtime of the sanctioned party list screening, the SPL master data is broken down into search terms internally. During the corresponding check of SPL entries against the partner address, partner information is also broken down into these internal search terms. The system only compares the search terms generated during the actual check.
You can define the level of detail with which search terms are created, or the terms (such as AG) for which no search terms are to be generated in Customizing.
Search terms are saved in the database and can be updated as required (if new SPL data is included or existing data is changed). This means you do not have to determine the search terms for each SPL check.
History
Last changed by/on | SAP | 20141106 |
SAP Release Created in | 100 |