Kontakt

Ansicht
Dokumentation

RPLAAMV0 - AA-register - electronic version

RPLAAMV0 - AA-register - electronic version

CL_GUI_FRONTEND_SERVICES - Frontend Services   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Title

AA-register - electronic version

Purpose

This report enables electronic reporting of AA-registeret to NAV. It can be used both for Status control (Status kontroll) and Continuous reporting (Løpende rapportering).

Statuskontrollen collects all RTV relevant data over a period of the last 12 months for each selected person. It can only be reported one record per employee per judicial organizational number. Message type for Status control is '88'.

Continuous reporting should be started on a regular basis - at least once a month, but biweekly or weekly is also possible. This reports all changes in master data compared to what has already been reported to NAV. Depending on the current situation, different message types are created. The different types are:

- '8I': Entry message

- '8O': Leaving message

Note
The system generates this message only if the Run Date of the report is 2 months later than the End Date of this message for hourly employees (customizable). The system performs this action to facilitate the entry of working hours for the employee, for example, if you maintain the working hours of the employee for January in February, this report should not generate a leaving message.

- '8E': Change message.

For a detailed description of the message types, please refer to document Kravspesifikasjon - Elektronisk rapportering til AA-registeret fra lønns- og personalsystemer v3.02 from July 07, 2009.

It is recommended to run the report in test mode and verify the list output before creating a file for the authorities. See output section for further details.

For examples of scenarios applicable for Status Control and Continuous reporting run modes, see Scenario Examples.

Integration

The report is started with transaction PC00_M20_LAAM, which is situated in the menu under Human Resources -> Payroll -> Europe -> Norway -> Subsequent Activities -> Other Periods -> Reporting -> Bi-Weekly Report

You can access the report documentation in the following IMG path:

Payroll Norway -> Statistical Reporting -> AA Register Reporting

Prerequisites

Ensure that the relevant employee records exist in the following infotypes:

  • Master data infotypes:
  • Actions (IT0000)

  • Organizational Assignment (IT0001)

  • Planned Working Time (IT0007)

  • Absences (IT2001)

All changes of the listed infotypes are recorded using a dynamic event. This means that the report will select master data between the date of the earliest, relevant MD change and rundate from the selection screen. See release note on AA-registeret for details on the activation of the dynamic event.
For employees on full time leave, the report generates 8I and 😯 messages. In case of employees on part time leave, the report generates an 8E message, with reduced number of working hours.
  • Employee Remuneration infotype (2010)
In this infotype, you can store the actual number of working hours for an employee on Hourly Employment contract. By default, the system reads employee work hours from Planned Working Time infotype (0007). However, for employees on hourly contract, the report reads Employee Remuneration infotype (2010).
  • Attendances (2002) infotype
In this infotype, you can store the working hours of hourly paid employees. You can maintain these details for the main position that an employee works in.
The report reads the attendance details of hourly paid employees from this infotype based on the return date that you maintain in Solution Change-Over Date(Norway) (20SOL) feature.
Note
You can also create this record through Cross Application Time Sheet( CATS) time recording maintained by an employee

  • Activity with Higher Rate of Pay infotype (0509)
In this infotype, you can maintain the employee's additional position. This is applicable for both monthly and hourly employment contracts.
The report output displays data on the position, for which the employee works the maximum number of hours. The maximum number of working hours could be either the main position or the additional position. The data is generated for employees on monthly as well as hourly work contracts.
Note
All changes of the listed infotypes are recorded using a dynamic event. This means that the report will select data between last reported rundate (or the date of the earliest relevant Master Data change if this is before the previous rundate) and rundate from the selection screen (including the rundate). See release note on AA-registeret for details on the activation of the dynamic event. Example: Previous rundate was 31.01.2008, new rundate is 15.02.2008. If there is no new master data change before 31.01.2008, the interval will be 01.02.2008 to 15.02.2008.

Ensure that you check the job code catalogue :

Check the job codes (yrkeskoder STYRK) stored in your system. Table T5V5A is delivered with (at the time of delivery) the complete catalogue of job codes as delivered by SSB. If you notice missing entries, please write an OSS message and let us know. This is not used by public sector, where the position code is used instead.

Tables in use:

  • T5v5a job code
  • T5v5b connection between job code and job
  • T5VPPS_TMA PA/PS to report/not report for hourly employees
  • RPDLGA20, kl.14_01 wage types for hourly employees.
  • T5V5M result table holding all previous reporting since last status report
  • For Public Sector use job code = job in T5V5A, and T5V5B would then have job and cob code=job

Example

The codes are stored in the following structure:

1210 153 01.01.2000 31.12.9999 RIKSANTIKVAR

1210 154 01.01.2000 31.12.9999 OLJEDIREKTØR

1210 155 01.01.2000 31.12.9999 KONSERNDIREKTØR

Standard settings

The standard is delivered with all possible job codes.

Recommendation

It will be more convenient to only store the job codes used in your company. Ask SSB for support in deciding which codes are relevant for your use, and delete the obsolete codes from the table. If you do so, store the table content before an upgrade and before applying an HRSP (LCP) containing table entries from T5V5A..

Further notes

You can upload the 'yrkeskoder' form the internet using report RPUYRKV0. The report is situated in the Norwegian menu under the label 'Upload of yrkeskoder', found on path Subsequent activities -> Period-independent -> Other. Please refer to the documentation allocated to the report for further information.

Features

Selection

  • All standard HR selections are accessible on the selection screen. We however recommend you to use either company code or explicitly selected persons for your selection.
  • You select status report or continuous reporting using the radio buttons.
  • You select the Legal org. number (judicial organization number):
This legal organisation number of a company defines the legal entity of the company. Each company has only one legal organization number. Norwegian term: "juridisk nummer".
  • Rundate is per default "today", but can be changed as needed. However, if a rundate is chosen which lays before the rundate of an updated report run, only test run is possible due to data consistency reasons. Even if you start the report in update mode, no temse is created and no table update is done.
  • Hourly paid employees:Working Hours from IT2002:
  • Attendance Types - Select the relevant attendance type for the employee's main position.

Note
The attendance types that you maintain for hourly paid employees under Customizing for Time Management --> Time Data Recording and Administration --> Attendances/ Actual Working Times --> Define Attendance Types is available for selection here.
  • Hourly Employees: Waiting Period to Show Messages
Specify the time period before the report must generate 😯 message for hourly paid employees. For more information, see Limit for months without working hours.
  • You select the Test run (no update)check box as a default, which means that no update is done.

Output

Test mode: A list of the data to be reported is presented, with the corresponding personnel numbers. Please verify the contents of this list with your master data before starting the report in update mode. This list is also presented when running the report in update mode.

Update mode: When running in update mode, the report creates a TemSe file named HR_LAAMVS_xxx for a status run and HR_LAAMVL_xxx for løpende meldinger (xxx is a counter). Please use transaction PC00_M20_LTEM (report RPLTEMV0) to create a file on your frontend or application server of the corresponding TemSe file. This file can be sent to NAV.

Internally, all messages sent to NAV is stored on database table T5V5M. This table consists of all messages for all persons selected for the period between the last Status Control and the current rundate. Please notice that this message table is refreshed when running a statuskontroll in update mode (all existing entries are deleted and replaced with the new status records).

Activities

  • Import the customizing neccessary for triggering the dynamic event as described in the AA-registeret release note. The new entries in table T588Z must be imported form client 000. Please check for interference with already existing dynamic events if you have implemented customer specific dynamic events.
  • Ensure that job codes (yrkeskoder) are maintained for all employees. We recommend you to contact SSB for questions on how to handle the (immense number of) yrkeskoder in your company. For public sector customers, the position code is used, and not job codes from SSB.
  • NAV is interested in average, planned working hours for each salaried employee. Be sure to insert the according number of hours in Planned Working Time (0007) infotype. For hourly employees, hours from Employee Remuneration Info (2010) infotype is read, and compared to average limit of 4 weekly hours, to decide if to be reported.
  • Entry date (Ansatt-dato) is per default read as the first entry action (IT0000) of a person. If you use other information sources for the entry date like IT 0041 or IT0016, please customize this using feature "ENTRY".
This only applies if you do not want the system to read IT0000 for finding the entry date.
Effects on Customizing
You can also customize view table. Via the job key in the organizational assignment, the yrkeskode (job code) is read. Each job key must be assigned to a job code in table T5V5B, which is accessed via maintenance view V_T5V5B. Temporary Agreement codes (T5VPPS_TMA) table needs to be maintained with the PA/PSA to report/not report for hourly employees. Table RPDLGA20, kl.14_01 need to be maintained for wage types for hourly employees.
Note
For public sector other rules apply, and they are reporting public sector position code instead.
  • If you want the report to read the attendance details of hourly paid employees, ensure that you maintain the Solution Change-Over Date (Norway) (20SOL) feature. Based on the return date that you maintain in this feature for Change type 003, the report reads the working hours for the hourly employee's main position. We suggest that you do not maintain the return date for Change type 003 for data that you have already submitted to authorities in the past.

Example






PERFORM Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 14409 Date: 20240520 Time: 104219     sap01-206 ( 260 ms )