SAP ABAP Data Element JHKUMGR (IS-M/AM: Cumulation Group for Contracts Found)
Hierarchy
IS-M (Software Component) SAP MEDIA
   IS-M (Application Component) SAP Media
     JAS (Package) Application development R/3 Publishing Advertising System***
Basic Data
Data Element JHKUMGR
Short Description IS-M/AM: Cumulation Group for Contracts Found  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type NUMC1    
Data Type NUMC   Character string with only digits 
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 10 Cumul.grp 
Medium 15 Cumulation grp 
Long 20 Cumulation group 
Heading Cumu 
Documentation

This field is only significant if accesses with Y or Z exclusivity are used.

Definition

Accesses in an access sequence with the same value in this field form a cumulation group.

Description

If an access has Y or Z exclusivity, the next access is only performed if no contract has been found previously in its cumulation group.

Example

ANo.    Order partner role     Contract partner role     Cumu    Excl

1     IS (Advertiser)     AI (Contract holder)     1     X

2     IS (Advertiser)     BG (Beneficiary)     0     Z

3     IS (Advertiser)     KO (Group subsidiary)    1    

In this access sequence, the third access sequence is only performed, if:

  • No contract could be assigned in the first two accesses and
  • No contract was found in the cumulation group for the third access (i.e. in cumulation group 1).

This means that the system only searches for group contracts if the advertiser does not have a contract (regardless of whether they are a beneficiary in a contract).

If the second access had the exclusivity X, the system would search for group contracts if the advertiser did have contracts but none of these could be assigned (i.e. none of these contracts were suitable).

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