SAP ABAP IMG Activity OHAAL16_0175 (Define Variants for ELDA Notification to GKK)
Hierarchy
☛ SAP_HRCAT (Software Component) Sub component SAP_HRCAT of SAP_HR
   ⤷ PY-AT (Application Component) Austria
     ⤷ PC03 (Package) HR Payroll: Austria
IMG Activity
ID OHAAL16_0175 Define Variants for ELDA Notification to GKK  
Transaction Code S_L6B_69001355   (empty) 
Created on 20051011    
Customizing Attributes OHAAL16_0000   Attributes L16 (Mandatory/Critical) 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAAL16_0175    

Use

This Customizing activity describes how to configure selection screen variants for data medium packages that are sent to the regional health insurance funds (GKK). The ELDA data package information required for the transfer to the appropriate GKK can be defined in the variants.

Activities

  1. Call transaction SA38.
  2. In the Program field, enter RPUELDA0.
  3. Choose Goto -> Variants.
  4. In the Variant field, enter the required standard variant SAPLOPAF_M and choose Create.
  5. Enter data in all of the necessary fields for the provision of an ELDA data package to the GKK.
    The data for the parameters in the Data transfer office and Information on data carrier group boxes is used in transaction PCALZ and program RPLGLZA0. The parameter Test and all other parameters are automatically entered by the system.
  6. Save the variant.
  7. If you require any additional variants, enter the relevant desired variant in the Variant field and choose Create.
  8. Repeat steps 5 - 6 for each additional required variant.

Result: Each variant is created and can be selected when you next call transaction PCALZ or program RPLGLZA0.


Note:

If you want to provide payslip notifications to both the GKK and the Insurance Institution for Public Service Wage and Salary Earners (BVA), you need to define the structure of the physical file name on the basis of the logical file name specified in such a way that the names are not identical (see also Customizing activity Define Variants for ELDA Notification to BVA).

You can define logical and physical file names in transaction FILE. To ensure that the physical file name is unique, make sure that the structure of the physical file name contains the data medium number <PARAM_1> .
For more information, see the program documentation RPUELDA0.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20071105 
SAP Release Created in 470