SAP ABAP Data Element P01_SV_D3_GDMLD (Int.Reason for Creating German Data Entry Regulation Notif.)
Hierarchy
☛ SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR
   ⤷ PY-DE-NT-NI (Application Component) Social Insurance
     ⤷ P01S (Package) HR Germany: Social Insurance
Basic Data
Data Element P01_SV_D3_GDMLD
Short Description Int.Reason for Creating German Data Entry Regulation Notif.  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type P01_SV_D3_GDMLD    
Data Type CHAR   Character String 
Length 2    
Decimal Places 0    
Output Length 2    
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 CreatReas. 
Medium 19 Creation Reason 
Long 36 Reason for Creating Notification 
Heading 16 Creation Reason 
Documentation

Definition

This field contains the (internal) reason for the creation of the DEUEV notification.

Use

You can use this field to establish why a DEUEV notification has been canceled or created again. This field is filled for canceled notifications as well as for new notifications. The following values are possible:

  • 00 # New Notification Reason

    A notification reason is defined using the official submission reason of the notification and the period of the notification.

    Internal creation reason 00 is set in the following cases:

    • A notification reason is reported for the first time
      • The new DEUEV notification has internal creation reason 00.
    • A notification reason is changed
      • A cancellation is created for the old notification reason and a new notification is created for the new notification reason. Both have internal creation reason 00.
    • A notification reason becomes obsolete
      • A cancellation is created with the internal creation reason 00.

The following creation reasons are used when the reported notification reason remains valid but the data has been changed in at least one data module. In such cases, the system creates a cancellation and a new notification for the same notification reason.
If multiple data modules are changed, the creation reason with the lowest number is applied.

  • 10 # DSME Change

    The data in the data record DSME (notification) has changed.

  • 20 # DBME Change

    The data in the data record DBME (notification content) has changed.

  • 30 # DBGB Change

    The data in the data record DBGB (birth data) has changed.

  • 40 # DBEU Change

    The data in the data record DBEU (European insurance number) has changed.

  • 50 # DBKS Change

    The data in the data record DBKS (miners# and mine-employees# insurance) has changed.

  • 90 # DBUV Change

    The data in the data record DBUV (accident insurance) has changed.

Dependencies

Example

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