DADS-U standard import - Implementation 

Prerequisites

  • It is mandatory that the source file comply with the last two known standards (standards N and N-1), accepted by Net-Entreprises.
  • In the case of a data import concerning only the employees, it is preferable to have created the necessary Company and Site information beforehand.
  • The social security number of the employee must be complete.
  • The "Profile", "Service", "Collective agreement" and "Risk code" default values, defined by Site, will be retrieved for each employee associated with the site in question.
  • Table 607 must be filled and is used to setup:
    • the start reason code to use by default when a period start code of the DADS-U file corresponds to multiple entry reason code in Sage HRM.
      For example, in Sage HRM, DADS-U code "001" can correspond to:
      • Recruitment: Parameter defined by default,
      • Mandate start.
        By entering the EMB entry reason code in the "Entry reason" column of DADS-U code "001", the program will affect the "EMB" code each time it finds the code 001 in structure S41.G01.00.002.001 of the DADS-U file.
    • the end reason code to use by default when a period end code of the DADS-U file corresponds to multiple issue reason code in Sage HRM.
      In Sage HRM, DADS-U code "008" can correspond to:
      • the end of a fixed-term contract,
      • the end of an apprenticeship contract,
      • the end of a temporary mission,
      •  …
        By entering the issue reason code FCD in the "Issue reason" column of DADS-U code "008", the program will affect the "FCD" code each time if finds the code 008 in structure S41.G01.00.004.001 of the DADS-U file.
    • for the employees concerned by the multi-contract, it is possible to define the start reason codes for which a new contract chrono must be created in the Contract record.
      Thus, if DADS-U code "901" is "Yes" in the "Created contract", the program will created as many contract records as there are activity periods that start with DADS-U code "901".
  • The companies (company ID tax numbers) and sites (site tax ID numbers) of the DADS-U employee data to import must exist.
  • The file to import must comply with the DADS-U standard of the current or previous year.
    For example: Import in in 2010: Accepted DADS-U standards V08R10 (2010) V08R09 (2009).
  • The structure of the DADS-U standard of the file to import must be described in the GESFTD function (Menu: Payroll Statements\EDI declarations\File structure DADS-U\DNA).
  • Initialize DADS-U parameters DADYEA & IDADAT (PAY chapter, DDC group).

Activity codes

Tables used

No table is used by this function.