SAP ABAP IMG Activity OHAAL16_0261 (Define Variants for ELDA Notification to Statistics Austria)
Hierarchy
☛
SAP_HRCAT (Software Component) Sub component SAP_HRCAT of SAP_HR
⤷ PY-AT (Application Component) Austria
⤷ P03C (Package) HR Customizing: Austria
⤷ PY-AT (Application Component) Austria
⤷ P03C (Package) HR Customizing: Austria
IMG Activity
ID | OHAAL16_0261 | Define Variants for ELDA Notification to Statistics Austria |
Transaction Code | S_L7D_24000557 | IMG Activity |
Created on | 20061222 | |
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_0261 |
Use
This Customizing activity describes how to configure selection screen variants for data medium packages that are sent to Statistics Austria. The ELDA data package information required for the transfer can be defined in the variants.
Activities
- Call transaction SA38.
- In the Program field, enter RPUELDA0.
- Choose Goto -> Variants.
- In the Variant field, enter the required standard variant SAPLOPAF_A and choose Create.
- Enter data in all of the necessary fields for the provision of an ELDA data package to Statistics Austria.
The data for the parameters in the Data transfer office and Information on data carrier group boxes is used in transaction PCALZ and the program Creation of Person-Based Wage-Specific Notifications (RPLGLZA0). Fill the parameter Notification Type with the value 'AD' for private sector employees and 'P5' for public sector employees. The parameter Test and all other parameters are automatically entered by the system. - Save the variant.
- If you require any additional variants, enter the relevant desired variant in the Variant field and choose Create.
- 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:
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 documentation for the Create Data Medium for Data Transfer with SI Medium (RPUELDA) program.
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 |