SAP ABAP Data Element RSDMDHANDLEDUPREC (Indicator: Duplicated Data Record Handling)
Hierarchy
SAP_BW (Software Component) SAP Business Warehouse
   BW-WHM-DBA (Application Component) Data Basis
     RSDMD (Package) Master Data Update
Basic Data
Data Element RSDMDHANDLEDUPREC
Short Description Indicator: Duplicated Data Record Handling  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type RS_BOOL    
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 Handle D. 
Medium 19 Handle Duplicates 
Long 29 Handle Duplicated Keys 
Heading 29 Handle Duplicated Keys 
Documentation

Definition

Use

If you set this indicator, duplicate data records are handled during an update in the order in which they occur in a data package.

  • For time-independent attributes of a characteristic, the last data record with the corresponding key within a data package defines the valid attribute value for the update for a given data record key.
  • For time-dependent attributes, the validity ranges of the data record values are calculated according to their order (see example).

If the indicator is not set and error handling is deactivated, the request terminates once data records with the same key are detected. If error handling is activated, data records that have the same key are written to the error stack of the DTP.

Note:

If during your data quality measures you want to make sure that the data packages delivered by the DTP are not modified by the master data update, you must not set this indicator.

Dependencies

Notethat for time-dependent master data, the semantic key of the DTP is not allowed to contain the field of the data source that contains the DATETO information.

Example

Handling of time-dependent data records

  • Data record 1 is valid from 01.01.2006 to 31.12.2006
  • Data record 2 has the same key but is valid from 01.07.2006 to 31.12.2007

The system corrects the time interval for data record 1 to 01.01.2006 to 30.06.2006. As of 01.07.2006, the next data record in the data package (data record 2) is valid.

History
Last changed by/on SAP  20130604 
SAP Release Created in 710