SAP ABAP Data Element /SAPSLL/SPPSZ (Package Size for Mass Sanctioned Party List Screening)
Hierarchy
☛ SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation
   ⤷ SLL-LEG (Application Component) Global Trade Services
     ⤷ /SAPSLL/LEGAL_CON_SPL (Package) Legal Services: Legal Control - Sanctioned Party List
Basic Data
Data Element /SAPSLL/SPPSZ
Short Description Package Size for Mass Sanctioned Party List Screening  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SYST_LONG    
Data Type INT4   4-byte integer, integer number with sign 
Length 10    
Decimal Places 0    
Output Length 11    
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 Packg Size 
Medium 15 Package Size 
Long 37 Package Size for SPL Screening 
Heading 37 Package Size for SPL Screening 
Documentation

Definition

In this field you define the package size for mass sanctioned party list screening.

Use

In mass screening of sanctioned party lists, the data quantity to be screened is split into packages of a defined size. Full sanctioned party list screening is performed for each package and the result is updated in the database. The package-by-package processing of the objects to be screened can optimize sanctioned party list screening with regard to the following parameters:

  • Minimized runtime for screening and update
  • Optimum use of buffer mechanisms
  • Optimum use of the enqueue server
  • Prevention of memory overflows

The value to be specified (default = 1,000) strongly depends on the system properties. The greater the resources available, the higher the value that can be applied.

The higher the number of objects to be screened that can be assigned to a package, the shorter the runtime for each object due to buffering mechanisms. However, this increases the risk of memory overflows or of other processes being affected due to the locking of the partners or documents to be checked.

Dependencies

Example

You define a package size of 1,000. During periodic sanctioned party list screening, you screen 50,000 business partners using the B1M screening scenario (periodic mass screening of the sanctioned party list). The program splits the 50,000 business partners into 50 packages, each with 1,000 partners, and performs screening for each package.

History
Last changed by/on SAP  20141106 
SAP Release Created in 700