Import Process
This process will automatically import the text file Input File or the table given in the field Import Table using the informed layout in the field Generator Model. This layout must be pre-prepared. For further information about the Import/Export models, consult documentation about this subject.
Like all other processes, the import process has its execution defined through the button Frequency.
Example
The weekly import of text file may be performed by other System for updating information.
Select the acronym for the People Management module | HCM that will be the owner of the task. Thus, when the task is run, it will be destined to the correct system.
Specify which processes will run on a specific server without these processes being run by the other servers that use this same database.
The Location code is not mandatory for running the process.
In this field is displayed information referring to the periodicity of execution of this process. To change these settings, use the Periodicity button.
Indicate if the process should be performed also on Saturdays, Sundays and holidays. It is considered as being holidays all the days registered in the table of holidays.
This field allows to indicate that this process will only be run after the end of running the other process. For this, it is necessary to report the type of predecessor process (if it is a Report process, Calculation, etc.) and its code. The predecessor process is run 1 minute before the main process.
Example
Process 1: Evaluation Calculation
Process 2: Evaluation Report
It is desired that the Process 2 only be run after running the Process 1. Then, in the registration of Process 2, the Type of predecessor 4 (Calculations) must be indicated, as well as the Code of predecessor 1. Thus, the process 2 will be run only if process 1 has been successfully completed.
If there is an error in the execution of the automatic process, inform whether the process should be deactivated or whether it should continue to be executed in the next periods.
Whether to generate a log message on the occurrence of an error in the execution of the automatic process.
Inform how the automatic process log should be generated:
- Generate log on Database: The log of the process running will be saved on the database, in the R300LOG table.
- Generate log in Text File: The log of the process running will be saved in a text file, in the directory of the input file.
If you want to send a log message when an error occurs in the execution of the automatic process, please inform the person responsible for the process.
Inform the source of the data to be imported: it can be a text file or a database table. According to the option chosen, the system enables/disables the corresponding fields.
Please tell us how the system should treat the previously generated file:
- Rename File. The previous file will be renamed. (Example: HR179142502 - HR - System Abbreviation, 17- Day, 9 - Month, 142502 Time in machine (hhmmss).
- Delete File. The previous file will be deleted and a new file will be generated;
- Keep File. The previous file will be overlapped by the new file.
Corresponds to the data file to be imported.
The complete path and the full name must be reported for the file identification.
Corresponds to the database table that will be imported. For further information, consult the file: Support Tools > Importer/Exporter of Text Files > General Information > Import of data via Database Table.
It corresponds to the model used to generate the report or to import the data. To select the file.
Report the code of the language in which the automatic process will be run.
Veja também:
English
Español
