This page (revision-6) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
6 26-Nov-2021 10:22 2 KB jmyers to previous LOAD DATA FLDR ==> LOAD DATA FLDR(System_Preference)
5 26-Nov-2021 10:22 2 KB jmyers to previous | to last EXTRCT DATA FLDR ==> EXTRCT DATA FLDR(System_Preference)
4 26-Nov-2021 10:22 2 KB jmyers to previous | to last ATTACHMENTS FLDR ==> ATTACHMENTS FLDR(System_Preference)
3 26-Nov-2021 10:22 2 KB JEscott to previous | to last
2 26-Nov-2021 10:22 2 KB JEscott to previous | to last
1 26-Nov-2021 10:22 1019 bytes JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 13 removed one line
The XDWR will not extract any shift patterns, change reasons, or time codes that are associated to a leave policy.
At line 14 added 9 lines
The XDWR will not extract any shift patterns, change reasons, or leave policy type time codes that are associated to the work rule being extracted. These must already exist in the receiving database prior to running the [LMDATA] function to load the new work rule. They must be entered manually.
Before the XDWR can be run there are site preferences that must be defined. Within the [IMST] screen, the administrator must define where the Extract and Load files are located and where the load functions are to write the exception files to. These locations are used by the functions to create and retrieve information. The customer can modify these values to represent any directory on their system.
The extract directory is defined using the EXTRCT DATA FLDR preference. The load directory is defined using the LOAD DATA FLDR preference. The ATTACHMENTS FLDR must be specified so the load functions know where to write the report exceptions log to.
Once the XDWR function has been run, it will have created an .xml and .data file, it is suggested that the user reviews the .xml file to ensure the correct data was extracted.
The user will then load the .data file into the receiving database via the [LMDATA] process.