!--a11y-->
Dimona Processes 
The Dimona processes in the SAP System are report-driven. In this chapter, you will find a detailed description of the most common Dimona processes in the SAP System.
Make sure you have been through the relevant customizing steps, as described in Dimona Declarations Infotype (0735).
Employers can report hiring/leaving events, cancellations and corrections either manually or automatically.
Employers can make a snapshot of the hiring and leaving events that start and end on a customizable key date before the official start date (01/01/2003).
You cannot delete the record of a hired worker who did not show up on his or her first workday. You must define a new personnel action instead in the relevant table (T5BO1), specify it is not Dimona-relevant and execute it on the hiring date to override the previous hiring action. On executing the Dimona preparation report, a cancellation declaration is generated.
The manual process consists of the following steps, as illustrated below:
· Report Dimona data via vocal server or website.
· Maintain declaration data in infotype Dimona declarations (0735) and, if not already maintained, Dimona data in the infotypes Personal data (0002) and Contract elements (0016).
Maintain the following information:
·
Personal data (0002)
SIS card number, SIS card indicator and SIS card serial number; certificates
for PBDF and ISDF directory.
·
Contract elements (0016)
External workplace and C3.2A cards.
You can report the data directly via vocal server or the Social Security portal (http://www.sociale-zekerheid.be). Once you have received the receipt file from the National Office for Social Security, you can maintain the declaration data.
MySAP HR Belgium has been enhanced with the infotype Dimona declarations (0735), which enables you to store the following Dimona-relevant information:
· Declaration type (hiring, leaving, modification or cancellation).
· Start and end date of contract, depending on the declaration type.
· Employer SI number.
· Dimona number, that is, a unique number sent to the employer by the National Office for Social Security once the declaration has been processed.
· Receipt number, that is, a unique number sent to the employer by the National Office for Social Security once it has received the declaration, on condition that it has not been rejected.
If you choose the automatic process, you must execute the reports described below.
This report reads the infotypes Actions (0000), Personal data (0001) and Dimona declarations (0735) for previously created declarations and generates new declarations with the status P (Planned), on condition that Dimona-relevant events have been detected.
Once you have completed the process successfully, you can generate the electronic Dimona declaration.
This report reads all records in Dimona declarations (0735) with the status P (Planned). The output is either a TemSE file or an on-screen ALV list.
The TemSE file is stored in the TemSE directory and all the declarations it contains are set to S (Sent to SI) in the corresponding infotype records.
If you choose to report the data manually instead, you must enter the receipt number, whereafter the Dimona infotype is automatically updated and the status is set to F (Formally accepted by SI).
This report reads the TemSE file. Note that the file number must be available if the previous step has been completed successfully.
In addition, you can download the file to your local PC and execute the SI file check program (formal check only). The result of this file, which you can view with report RPUDIRB0, is a temporary receipt file containing field level errors.
This report reads the TemSE file, adds a digital signature to the file (The digital signature of a certificate is your electronic identity card and makes you the unique sender of encrypted information.) and copies it to a local PC. You can choose to download either the TemSE file and the signature or the signature only. If you have run this report successfully, you can send the downloaded file to the National Office for Social Security via FTP.
A personal certificate, which is used to protect one’s identity on the Internet, is required by the Social Security portal to check your identity when you send Dimona information. It is issued by a certification authority (To find more about this topic, visit www.globalsign.be and www.e-trust.be.) and delivered with a public key. Only the owner knows the private key that enables him/her to decrypt or make a digital signature. By sending your certificate, you actually send your public key, so that the National Office for Social Security can return encrypted information which only you can decrypt with your private key.
To handle digital signatures successfully, do the following:
· Contact a certification authority to apply for a certificate. Note that this step is mandatory, otherwise the National Office for Social Security will not be able to check the validity of the signature.
· Perform the steps described in Digital Signatures.
In this step, you retrieve the file you have processed from your local PC and transfer it to the SI Inbox with an FTP program.
In this step, you retrieve the Dimona receipt files from the SI Outbox with an FTP program.
This report reads the receipt file you have retrieved in the previous step. The output is an ALV list (error log). In addition, the status of the relevant declaration is updated in the Dimona infotype (0735), that is, set from S (Sent to SI) to F (Formally accepted by SI), R (Rejected) or O (rejected due to errors at the levels 0 and 1 of the file).
In this step, you retrieve the Dimona confirmation files from the SI Outbox with an FTP program.
This report reads the previously retrieved confirmation file. The output is an ALV list containing the fields that have been corrected. In addition, the status of the relevant declaration is updated in the Dimona infotype (0735), that is, set from F (Formally accepted by SI) to either A (Accepted) or C (Corrected).
This process is identical to the automatic process with the only difference that no file is created. Execute the reports RPUDIPB0 and RPLDIDB0 and report any events. The declarations are not added to a Dimona file but displayed in ALV mode. By doing so, you can directly report declarations via vocal server or website and enter the receipt numbers on the spot.
