Below you can find collection of up-to-date information which could help you at your daily work with EDAG. This Wiki page will be updated and completed regularly.
Important information for the year 2020
ALTINN - Upgrade of network security level for HTTPS communication to TLS 1.2
Please read the following SAP KBA carefully:
Please forward this information to the person who is responsible for your PI/PO communication to Altinn for your company.
Altinn has decided to upgrade their network security level for HTTPS communications to TLS 1.2. All interfaces using the ACF framework such as the a-message reporting, receive of tax cards, sending of income forms etc. are affected. Please check the requirements below to ensure that your connection will still be working.
The effective date for the mentioned change in Altinn will be the 14th or the 15th of January 2020. That means that you have to be sure that TLS 1.2 is supported in your PI/PO system before that date.
One extra cipher suite is made available at Altinn so that our lower releases, when TLS 1.2 is made available, will work.
There is no confirmed date yet for how long the additional cipher suite (not Elliptic curve cryptography) will be available. That means that we do not know for how long you can run on the lower releases.
Downport of the Elliptic curve cryptography(ECC) functionality to lower releases is not an option because of the timeframe given here.
Elliptic curve cryptography functionality are supported from PO 7.50 SP 8 (Note 2708581) and onwards, and in Cloud Platform Integration (CPI).
The new requirements from Altinn are:
• The only transport layer protocol to be supported will be TLS1.2
• ECC (the strongest cryptography currently available) will be the only cipher supported
• For a limited period of time, GCM (SHA256) cipher suite will be supported
Available cipher suites from 14.1.2020:
TLS_RSA_WITH_AES_128_GCM_SHA256 (available until – here more details will follow)
=> UPDATE on 22.09.2020 : The Date has been set by the authority (ALTINN) 10th of October 2020
What to do depends on the status of your PI/PO system.
Ensure that you have one of the following in place before the 14th of January:
• Support for ECC over TLS 1.2 exists in Process Orchestration version 7.5 onwards(Note 2708581).
• If you are on lower releases of PI and not able to upgrade to PO 7.5 before 14th of January 2020, you have to implement and follow instructions in these notes:
TLS 1.2 is supported in lower releases of PI from the level mentioned in this note:
Title: Update of SSL library within NW Java server
Useful information is also to be find here:
Title: Enabling TLS 1.1 and 1.2 on NetWeaver AS Java for outgoing connections
• Migrate to CPI
The same set of interfaces are now available in CPI. As CPI uses the latest Java security libraries, support for TLS 1.2 and ECC is automatically available. Altinn Communication Framework (ACF) Integration Package for Norway Payroll will be available in CPI for subscription most probably within a couple of weeks. This is a possible option for customers running HCM on 6.08.
• Reverse proxy
A work around may be possible using a reverse proxy, where the SSL call is terminated at the web dispatcher and the web dispatcher continues the call to Altinn. For more information on this work around, please create an incident in the component BC-XI-CON-AFW-SEC.
To test the communication from your test system, you can switch your target URL for Altinn to TT02.altinn.no and run RPUACFV0_CHECK_SPROXY. IF you get an application error (User not authorized), this means that your TSL connection has been accepted by Altinn. However, if you get any other error, your connection has been refused because of the new requirements from Altinn
If any problem, please raise an incident to component BC-XI-CON-AFW-SEC.
We will inform you as soon as there is any end-date given for the availability of the additional cipher suite. Our recommendation to Altinn is the end of 2020, but this is out of our hands. So please consider upgrade to PO 7.5 or migrate to CPI as soon as possible.
General information – Year-end (legal) change 2014/2015 EDAG
The legal change called EDAG is regulated by a new law - A-opplysningsloven. A-opplysningsloven and its regulations are effective from 01.01.2015.
The main goal of EDAG is to simplify the employer’s communication with the different authorities in Norway. The a-message, which the employer is to submit at least once a month, must contain all the information that the employer is used to report regarding LTO, ERC, AA-register, reimbursement and statistics.
Public EDAG-project web page (non-SAP content):
SAP Service Market Place – Electronic Dialogue with Employer SAP solution overview
SAP Announcement Note – Legal Change EDAG & FAQ EDAG
The above SAP Note will no more updated after 1.1.2019.
- Overview of EDAG - business perspective.pdf
- Overview of EDAG - presentation of solution.pdf
- Valid combinations of income details with generation rules june 2014.xlsx
- Overview of EDAG -sharing of experience from pilot customer.pdf
- Veiledning for e-dag-oppsett per juli 2014.pdf
SAP Note - Frequently Asked Questions EDAG
ACF – Altinn Communication Framework
It is a prerequisite that the new Framework for communication with Altinn (ACF) is implemented. The instruction guide for implementing ACF is in note 1773369.
Latest EDAG Notes – Released for Customer
The minimum level till of SP/CLC is:
- from 1.1.2014 till 31.3.2015 - SP 600-A4 / 604-70 / 608-01
- from 1.4.2015 till 27.3.2016 - SP 600-B2 / 604-78 / 608-06
- from 28.3.2016 till 26.3.2017 - SP 600-C4 / 604-90 / 608-18
- from 27.3.2017 till 31.12.2017 - SP 600-D6 / 604-A3 / 608-31
- from 27.3.2018 till 31.12.2018- SP 600-F0 / 604-B6 / 608-44
Consulting SAP Notes (information SAP Notes which cannot be implemented by Note Assistant) - they are not part of any SP delivery
2428930 - EDAG- XML format of Income Recipient Data (RPCEDGV0, RPCEDGV0_CORR)(last change at 27.03.2017)
SP 600-J9 / 604-G5 / 608-93
SP 600-J8 / 604-G4 / 608-92
SP 600-J7 / 604-G3 / 608-91
SP 600-J6 / 604-G2 / 608-90
SP 600-J5 / 604-G1 / 608-89
SP 600-J4 / 604-G0 / 608-88
SP 600-J3 / 604-F9 / 608-87
SP 600-J2 / 604-F8 / 608-86
2982672 - EDAG - November 2020 [1/4] - DDIC
2982674 - EDAG - November 2020 [2/4] - Source code
2982675 - EDAG - November 2020 [3/4] - Maintenance View
2982994 - EDAG - November 2020 [4/4] - Customization
SP 600-I9 / 604-F5 / 608-83
SP 600-I8 / 604-F4 / 608-82
SP 600-I7 / 604-F3 / 608-81
SP 600-I6 / 604-F2 / 608-80
SP 600-I5 / 604-F1 / 608-79
SP 600-I4 / 604-F0 / 608-78
SP 600-I3 / 604-E9 / 608-77
SP 600-I2 / 604-E8 / 608-76
SP 600-I1 / 604-E7 / 608-75
SP 600-I0 / 604-E6 / 608-74
SP 600-H9 / 604-E5 / 608-73
SP 600-H7 / 604-E3 / 608-71
SP 600-H5 / 604-E1 / 608-69
SP 600-H4 / 604-E0 / 608-68
SP 600-H3 / 604-D9 / 608-67
SP 600-H2 / 604-D8 / 608-66
SP 600-G9 / 604-D5 / 608-63
SP 600-G8 / 604-D4 / 608-62
SP 600-G7 / 604-D3 / 608-61
SP 600-G5 / 604-D1 / 608-59
SP 600-G4 / 604-D0 / 608-58
SP 600-G1 / 604-C7 / 608-55
SP 600-G0 / 604-C6 / 608-54
SP 600-F9 / 604-C5 / 608-53
SP 600-F8 / 604-C4 / 608-52
2596543 - EDAG - March 2018 [1/4] - DDIC and XSLT
2596544 - EDAG - March 2018 [2/4] - Source code
2600558 - EDAG - March 2018 [3/4] - MAGNET_EDAG-254 correction after SAP Note 2585460
2596545 - EDAG - March 2018 [4/4] - Customization
SP 600-F7 / 604-C3 / 608-51
SP 600-F6 / 604-C2 / 608-50
SP 600-F5 / 604-C1 / 608-49
SP 600-F4 / 604-C0 / 608-48
SP 600-F3 / 604-B9 / 608-47
SP 600-F2 / 604-B8 / 608-46
SP 600-F1 / 604-B7 / 608-45
SP 600-F0 / 604-B6 / 608-44
SP 600-E9 / 604-B5 / 608-43
SP 600-E8 / 604-B4 / 608-42
SP 600-E7 / 604-B3 / 608-41 - following SAP Notes for EDAG solution are valid from SP 600-D6 / 604-A3 / 608-31
SP 600-E6 / 604-B2 / 608-40
Remark - Last SAP Notes for EDAG solution which will be valid from SP 600-C4 / 604-90 / 608-18 !!!
SP 600-E5 / 604-B1 / 608-39
SP 600-E4 / 604-B0 / 608-38
SP 600-E3 / 604-A9 / 608-37
SP 600-E2 / 604-A8 / 608-36
SP 600-E1 / 604-A7 / 608-35
SP 600-D9 / 604-A5 / 608-33
SP 600-D8 / 604-A4 / 608-32
SP 600-D7 / 604-A3 / 608-31
SP 600-D6 / 604-A2 / 608-30
SP 600-D5 / 604-A1 / 608-29
SP 600-D4 / 604-A0 / 608-28
SP 600-D3 / 604-99 / 608-27
SP 600-D2 / 604-98 / 608-26
SP 600-D1 / 604-97 / 608-25
SP 600-D0 / 604-96 / 608-24
SP 600-C8 / 604-94 / 608-22
SP 600-C7 / 604-93 / 608-21
SP 600-C6 / 604-92 / 608-20
SP 600-C5 / 604-91 / 608-19
SP 600-C4 / 604-90 / 608-18
SP 600-C3 / 604-89 / 608-17
SP 600-C2 / 604-88 / 608-16
SP 600-C1 / 604-87 / 608-15 (as it was previously announced these notes will require minimum SP/CLC level 600-B2 / 604-78 / 608-06)
SP 600-C0 / 604-86 / 608-14
SP 600-B9 / 604-85 / 608-13
SP 600-B8 / 604-84 / 608-12
SP 600-B7 / 604-83 / 608-11
The general recommendation is to use the latest SP/CLC plus notes that were released since latest SP/CLC release.
Known issues - Solutions:
- EDAG data mining program (RPCEDGV0) has long runtime because of huge number of processed Personnel Numbers
Solution: Collecting of data via program RPCEDGV0 can be shortened by running multiple parallel jobs.
- CA Root Certificate issuer and their certificates are changed by the Norwegian Tax Department
Solution: The issue is to be solved by adding the New certificates in TrustedCAs in java stack of PI system.
Message from Authority: Altinn have changed certificates.
If you got problem with the change of certificate in end-user-system, please download the certificate. Here is a guide of how to do it: https://altinn.brreg.no/sites/fagsystemer/Lists/Announcements/Attachments/451/nedlasting-sikkerhetssertifikat.pdf (Above link refers to a non-SAP Content)
After deploying the new certificates it is necessary to restart the communication channels.
- New NAV office address distribution list has been published in November 2016 by NAV for form NAV 08-30.01.
Solution: SAP Note 2207916 (Version 4) has been updated: