Ansicht
Dokumentation
RPUNSHA0 - Transfer of External NSchG Data to Cluster NS
Fill RESBD Structure from EBP Component Structure General Data in Customer MasterThis documentation is copyright by SAP AG.
Use
You use this report to read the data for personnel numbers that you previously saved in view variant VV_558A_RPUNSHA0 (Payroll Account Transfer) and use it to generate records in cluster NS for a number of consecutive months. This allows you to meet the prerequisite for using evaluation report RPTNSHA0 (Nightshift Heavy Labor Law - NSchG), which reads the data from the cluster records and uses it to create the data relating to nightshifts of heavy labor.
The following scenarios are examples of how the report can be used:
- Until now, you have always saved employee-specific data relating to nightshifts of heavy labor in a third-party system or your own legacy system. This data is relevant for the Nightshift Heavy Labor Law (NSchG) or the Leave Entitlement Act (UrlG). As of a certain key date, you want to have the data relating to nightshifts of heavy labor created in the SAP system and to use report RPTNSHA0 for this purpose. To allow the report to also generate correct data in cluster NS for those persons for which data relating to nightshifts of heavy labor already exists in your legacy system, you need to transfer the data from your legacy system into the SAP system.
- You hire an employee who worked nightshifts of heavy labor for his previous employer and will also do so for your company (see the Heavy Labor Position in the detail view of table T528B (Positions - Work Centers). The previous employer has already provided the personnel data relating to nightshifts of heavy labor that you want to import into your SAP system.
Integration
The report uses view variant VV_558A_RPUNSHA0 of table T558A (Payroll Account Transfer) as the transfer interface.
If you want to transfer data from your legacy system to the SAP system, you need to execute the report once before the live start in the SAP system.
If you want to transfer the data for a new employee from a previous employer, you need to copy the relevant information manually to view variant VV_558A_RPUNSHA0 and then execute the report for the personnel number in question.
If incorrect entries are generated in cluster NS, you can run the report again for the records that contain errors. Once a cluster record is generated, it cannot be deleted. It can only be overwritten by an empty (initial) record using the function to update the database. An empty record in cluster NS is regarded as a deleted record by report RPTNSHA0 (Nightshift Heavy Labor Law - NSchG).
The report does not evaluate data from personnel time management or from the Social Insurance A (0044), Absence Quotas (2006), and Leave Entitlement(0005) infotypes. Neither does it generate a batch input session to update the infotype records.
If you use this report, you must first ensure that any required SI change notifications are implemented in the legacy system before the data transfer is completed. SI change notifications and ELDA data records are not generated for the data transfer period.
Prerequisites
Before you can execute this report, the following conditions must have been met:
- Using the Hiring personnel action, you have entered the employees
for which the data is to be copied to cluster NS into the SAP system and created the Organizational
Assignment (0001) and Personal Data (0002) infotypes.
The start of the leave year is defined in the Date Specifications (0041) infotype. If a date type is not specified, the leave year starts with the calendar year.
- The legacy data relating to the nightshifts of heavy labor has been copied as wage types to view variant VV_558A_RPUNSHA0 (Payroll Account Transfer) or to table T558A (Payroll Account Transfer) with the country grouping 03. The report selects only those personnel numbers from table T558A for which at least one of these wage types exists in the transfer period.
Overview of Wage Types for Data Transfer and Applicable Value Ranges
| Wage Type | Number . | Amount/Unit | Amount . | |
|---|---|---|---|---|
| /UGM (nsN=ZUDMO;R=NSVMO;A=GFIMO) | ||||
| Number . | Amount/Unit | Amount . | ||
| 00 .... 31 (1) | 0 ...... 1 . | 00 .... 31 (1) | ||
| /USM (nsN=SRGMO;R=NSMON;A=_____ ) | ||||
| Number . | Amount/Unit | Amount . | ||
| 000 ... 999(2) | 0 ...... 1 (3) | reserved (4) | ||
| /UGY (nsN=ZUDJA;R=_____;A=_____ ) | ||||
| Number . | Amount/Unit | Amount . | ||
| 000 ... 366(2) | reserved (4) | reserved (4) | ||
| /UKT (nsN=KTOV1;R=KTOV2;A=KTOV3) | ||||
| Number . | Amount/Unit | Amount . | ||
| 000...366(2,5) | 000...366(2,5) | 000...366(2,5) | ||
| /UN0 (nsN=ANNS1;R=ANNSB;_______ ) | ||||
| Number . | Amount/Unit | Amount . | ||
| 000...366(2,5) | 000...366(2,5) | reserved (4) | ||
| /UN1 (nsN=KTNS1;R=KTNSB;A=_____ ) | ||||
| Number . | Amount/Unit | Amount . | ||
| 000...366(2,5) | 000...366(2,5) | reserved (4) | ||
| /USY (nsN=ZUJAR;R=_____;A=URLJJ) | ||||
| Number . | Amount/Unit | Amount . | ||
| 000 ... 999(2) | reserved (4) | 0000...9999(2) | ||
| /UZA (nsN=ANZU1;R=ANZUA;A=ANZU0) | ||||
| Number . | Amount/Unit | Amount . | ||
| 000 ... 999(2) | 000...999(2,5) | 000...999(2,5) | ||
| /UZB (nsN=ANZUB;R=KTZUB;A=_____ ) | ||||
| Number . | Amount/Unit | Amount . | ||
| 000...999(2,5) | 000...999(2,5) | reserved (4) |
- (1) The upper threshold for the validity area depends on the number of days in that particular month. If the data in the Organizational Assignment (0001) infotype indicates that the employee was employed in Austria for just some of the period, the upper threshold for the validity area may be less.
- (2) If you have selected the Auto. Entry in Subseq. Months checkbox on the report selection screen, this wage type field must not be filled in subsequent months (in other words, it must be blank). A subsequent month is a month for which data relating to nightshifts of heavy labor already exists in a previous month in the selection period. The cluster record fields are filled directly by the report.
- (3) This wage type field must always be filled for the first month in which data relating to nightshifts of heavy labor is to be copied to cluster NS as well as for the following 4 months. If you have selected the Auto. Entry in Subseq. Months checkbox in the report, the wage type field must no longer be filled for the 5th subsequent period. When the field is filled automatically, the system assumes that the employee was in a position of heavy labor throughout the data transfer period.
- (4) Reserved wage type fields must not be filled.
- (5) Before the start of leave year 2000, the wage type field must not be filled with values other than zero.
- View variant VV_558A_RPUNSHA0 (Payroll Account Transfer) supports table entries with 15 places before and 2 places after the decimal point. Since only whole number fields are currently used in cluster NS, decimal places after the decimal point are truncated. The transfer report checks the table entries for the value range that can be saved in cluster NS. (cf. report RPCLSTNS Display Cluster NS.) If the range is exceeded, the personnel number is rejected with an error message.
- Note that certain fields for data transfer wage types that are not currently used must not be filled and are reserved for later use by SAP.
- The following parameters are maintained in the Payroll Parameters view (V_T511K) with the country grouping 03.
- NSJA1 Years of nightshift worked 1
- If less than "NSJA1" years of nightshifts of heavy labor were worked to date, entitlement to additional leave of "NSJA1" exists. If at least "NSJA1" years have been worked, this entitlement increases to "NSJA2".
- NSJA2 Years of nightshift worked 2
- If there has been at least "NSJA2" years of nightshifts of heavy labor, entitlement to additional leave of "NSUA3" exists.
- NSJAR Annual nightshifts
- Entitlement to additional leave in accordance with UrlG §10a para. 1 exists if at least "NSJAR" nightshifts of heavy labor were worked in the working year. Entitlement to additional leave in accordance with UrlG §10a para. 1b and para. 1c exists if in addition to the previously granted additional leave, at least "NSJAR" nightshifts of heavy labor were worked in the current leave year and in the previous three leave years for which no entitlement to additional leave has existed.
- NSJR2 Nightshifts - 2 each year
- This specifies the number of nightshifts of heavy labor an employee must have worked in total in the current and previous leave year in order to be entitled to an additional day of leave (in accordance with § 10a para. 1a UrlG).
- NSMIN Min. nightshifts for para. 1a
- This specifies the minimum number of nightshifts of heavy labor an employee must have worked in a leave year in order to be entitled to additional leave in this year (in accordance with § 10a para. 1a UrlG).
- NSMO1 Nightshifts in one month
- For a month to be considered a month with nightshifts of heavy labor in line with the Nightshift Heavy Labor Law (NSchG), at least "NSMO1" nightshifts must be worked in the current month.
- NSMO2 Nightshifts in two months
- For a month to be considered a month with nightshifts of heavy labor in line with NSchG, at least "NSMO1" nightshifts must be worked in the current month or "NSMO2" nightshifts in the current and the previous month.
- NSMO3 Nightshifts in three months
- For a month to be considered a month with nightshifts of heavy labor in line with NSchG, at least "NSMO1" nightshifts must be worked in the current month or "NSMO2" nightshifts in the current and the previous month, or "NSMO3" nightshifts in the two previous months.
- NSMO6 Nightshifts in six months
- This specifies the number of nightshifts of heavy labor that an employee must have worked in the current calendar month and the previous five calendar months in total in order to be considered a worker of nightshifts of heavy labor (Art. XI, Para.6 NSchG).
- NSUA1 Additional leave entitlement level 1 (in acc. with UrlG §10a Para. 1 or Para. 1a)
- This entitlement exists if less than "NSJA1" years of nightshifts of heavy labor have been worked to date.
- NSUA2 Additional leave entitlement level 2 (in acc. with UrlG §10a para. 1 or para. 1a)
- This entitlement exists if at least "NSJA1" and less than "NSJA2" years of nightshifts of heavy labor have been worked to date.
- NSUA3 Additional leave entitlement level 3 (in acc. with UrlG §10a para. 1 or para. 1a)
- This entitlement exists if at least "NSJA2" years of nightshifts of heavy labor have been worked to date.
- NSUB1 Additional leave entitlement (in acc. with UrlG §10a para. 1b.)
Features
Selection
- On the selection screen, enter a date in the End of External Data Transfer field. This date must be the last day of a month. Since the End of External Data Transfer date is selected in the transfer report, only those entries are selected from table T558A for which the start date is the first day of the month, for which the end date is the last day of the same month, and for which the validity end date falls within the selected time interval for the data transfer. Entries with a mid-month date are ignored. This ensures that a unique proposal record can be generated per month for each personnel number.
- Before you execute the report, you need to specify in the No. of Data Transfer Periods field on the selection screen for the report the maximum number of consecutive months for which cluster records are to be generated.
- Ensure that the number of months of nightshifts of heavy labor in accordance with NSchG art. XI para. 6 are determined correctly by creating multiple monthly averages.
- You should fill all wage types provided (if required) for the first (earliest) period for which you have information relating to nightshifts of heavy labor and for which you want to create a cluster record by means of the report. The report then checks the consistency of the data to be transferred for this month.
- If you want to transfer multiple months of data to cluster NS (due to the requirement for multiple monthly averages to be created as stipulated by NSchG, for example), you can choose from the following options:
- If you select the Auto. Entry in Subseq. Months checkbox on the report selection screen, you only need to transfer the fields for wage type /UGM and the Amount per Unit field of wage type /USM up to the 4th subsequent period, for the subsequent months for which cluster records are also to be created. You must not specify values for the remaining fields of the transfer wage types. In this case, the report automatically fills the remaining cluster fields with the correct values derived from the proposed and previous cluster records. The system assumes that the employee was in a position of heavy labor throughout the data transfer period.
- If you do not select the Auto. Entry in Subseq. Months checkbox, you need to specify values for all required wage types fields in the subsequent months. The report checks the consistency of values across multiple periods. Wage type fields for which you do not specify values are filled with blank values. This setting allows you to transfer data for employees who were not employed in a position of heavy labor continuously throughout the data transfer period. You must not enter values other than zero in wage type fields for the months in which the employee was not employed in a position of heavy labor. The system would otherwise assume that the employee was in a position of heavy labor. If the wage type entries for a month are all blank, the system issues a warning indicating that the proposed, empty cluster record does not match the record that would be expected if the employee were employed in a position of heavy labor during that month.
Output
Before the system writes the proposed NS cluster records to the database, it provides a list of all proposed and rejected records.
- If cluster records do not exist in the selected interval for a personnel number, the generated and displayed proposed records are proposed for the database insert only. The DB Ins. Only pushbutton is activated in this case.
- If cluster records already exist in the selected interval for a personnel number, the generated and displayed proposed records are proposed for the database update only. The DB Upd. Only pushbutton is activated in this case.
- Proposed records that are eligible for inclusion in a database insert or update are assigned a yellow traffic light status icon in the list. The database modification type is set to II or UU. To be able to save the proposed records for a personnel number in the cluster, you must place the cursor on one of the proposed records for this personnel number and then add it to the selection for the database insert or update by choosing the F2 function key. You can also do this by double-clicking one of the proposed records for this personnel number. The selected records are then selected in the Insert Selection or Update Selection list fields. If you repeat this process, the selection is reversed.
- Proposed records that already match the cluster data records cannot be written to the database again. The original record with all relevant cluster information is then displayed in the output list. The record is assigned a green traffic light status icon in the list and is locked for selection for the database modification. If the cluster record was already generated in a previous program run, or there is no NSchG-relevant data in the period, which is why an additional 'empty' cluster record is not required, this is indicated in the list by the database modification types IO or UO. If the database entries were modified in the same program run, this is indicated in the list by the database modification types IM or UM.
- If an error occurs for a personnel number in the current period due to a data inconsistency or a value range being exceeded, all proposed records for this personnel number (including the consistent records) are locked for selection and cannot be written to cluster NS. The rejected proposed records are indicated by the red traffic light status icon and the database modification type RR. A corresponding error message and a short description of its cause are logged. To obtain a detailed description of what caused the error, place the cursor on the record that triggered the error or on the error message displayed, and press F2. You can also display the detailed error description by double-clicking the record with the error or double-clicking the error message.
- If the personnel number is not active in the selected interval, a warning is issued. The final decision
as to whether a cluster record for nightshifts of heavy labor is to be generated is a decision made
by the administrator. This check allows cluster records for nightshifts of heavy labor to be created
before an employee actually starts work in your company, thereby allowing NSchG-relevant data from previous employers to be transferred.
Activities
If you make changes to individual wage types after you create the proposal records using report RPUNSHA0, you need to run the report again to ensure that your latest changes are reflected in the proposed records.
- Select the checked proposed records for the database insert or database update in the results list - as described above - by pressing F2 or double-clicking the records.
- Then choose the DB Ins. Only or DB Upd. Only pushbutton to start the insert or update process to write the selected proposed records to cluster NS.
- Execute the processes sequentially to write all proposed records.
-
Once the data is written to the cluster, the system displays a list of all successful database modifications
and the current cluster information. The statistics list indicates the number of times data modification
was successful or unsuccessful. If a database modification was unsuccessful for certain personnel numbers
(due to an authorization error or a database lock, for example), these remain selected for the database insert or update.
The DB Ins. Only pushbutton remains active as long as proposed records for the database insert appear in the list, which means the write process can be repeated.
The DB Upd. Only pushbutton remains active as long as proposed records for the database update appear in the list, which means the write process can be repeated.
- When records are written successfully to cluster NS, you must manually maintain the indicator for nightshifts of heavy labor (contribution in acc. with NSchG) in the Social Insurance A (0044) infotype. (See the report documentation for report RPTNSHA0).
- When records are written successfully to cluster NS, you also need to manually maintain the records in the Leave Entitlement (0005) infotype, or, if time accounts are used, the records in the Absence Quotas (2006) infotype.
Example
Selection screen
Details for Program Execution
End of External Data Transfer 30.04.2001
Data Transfer Start: 01.11.2000
No. of Data Transfer Periods 6
Date Type Entry Leave Year 25
X Auto. Entry in Subseq. Months
Sample Entries in View Variant VV_558A_RPUNSHA0
| PersNo. | Start . | End . | WGType | Amt/Unit | Number | Amount |
|---|---|---|---|---|---|---|
| 9999999 | 01.11.2000 | 30.11.2000 | /UGM | 0.00 | 7.00 | 7.00 |
| 9999999 | 01.11.2000 | 30.11.2000 | /UGY | 0.00 | 69.00 | 0.00 |
| 9999999 | 01.11.2000 | 30.11.2000 | /UN0 | 0.00 | 50.00 | 0.00 |
| 9999999 | 01.11.2000 | 30.11.2000 | /USM | 1.00 | 9.00 | 0.00 |
| 9999999 | 01.11.2000 | 30.11.2000 | /USY | 0.00 | 1.00 | 2,000.00 |
| 9999999 | 01.11.2000 | 30.11.2000 | /UZA | 0.00 | 2.00 | 0.00 |
| 9999999 | 01.12.2000 | 31.12.2000 | /UGM | 0.00 | 8.00 | 8.00 |
| 9999999 | 01.12.2000 | 31.12.2000 | /USM | 1.00 | 0.00 | 0.00 |
| 9999999 | 01.02.2001 | 28.02.2001 | /UGM | 0.00 | 9.00 | 9.00 |
| 9999999 | 01.02.2001 | 28.02.2001 | /USM | 1.00 | 0.00 | 0.00 |
| 9999999 | 01.03.2001 | 31.03.2001 | /UGM | 0.00 | 5.00 | 5.00 |
| 9999999 | 01.03.2001 | 31.03.2001 | /USM | 1.00 | 0.00 | 0.00 |
| 9999999 | 01.04.2001 | 30.04.2001 | /UGM | 0.00 | 5.00 | 5.00 |
Addresses (Business Address Services) General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 39032 Date: 20240601 Time: 134518 sap01-206 ( 673 ms )
