SAP ABAP Data Element ICL_LOCK_WHOLE_CLAIM (With Change Claim, Always Lock Complete Claim)
Hierarchy
INSURANCE (Software Component) SAP Insurance
   FS-CM (Application Component) Claims Management
     ICL_CDC (Package) FS-CM: Data Capture
Basic Data
Data Element ICL_LOCK_WHOLE_CLAIM
Short Description With Change Claim, Always Lock Complete Claim  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type XFELD    
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  
Medium  
Long  
Heading 55 With Change Claim, Always Lock Complete Claim 
Documentation

Definition

Use

The system always locks the whole claim as soon as you call the claim in change mode. Locking the whole claim means that the claim header and all associated subclaims are locked as well. Other users are unable to call the claim header or any associated subclaim in change mode.

Background: When you use transaction ICLCDC02 (Change Claim (Expert Mode)) to call up a claim, the whole claim is always locked, regardless of whether you have set this indicator or not. However, this is not the case if you use another method to navigate to change mode of a subclaim, such as:

  • If you are in display mode of a subclaim and then navigate to change mode of the subclaim, only the current subclaim is locked, and not the whole claim.
  • Likewise, if you are working in the Business Workplace and navigate directly to processing of a subclaim, only the current subclaim is locked.

This can lead to the following problems in subsequent claims processing if you need further locks (for the claim header, for example):

  • The data needs to be read again from the database, or
  • The system cannot set the locks because the locks are already being held by another user.

Dependencies

Example

History
Last changed by/on SAP  20070917 
SAP Release Created in