XDWR
Back to current versionRestore this version

EXTRACT WORK RULE DEFINITIONS#

Processing Information#

When a work rule is extracted from an Wiki system the following data that is tied to the work rule will also be extracted:

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.


Report Parameters & Filters#

Report Parameters
File NameMandatory
This is the name of the file that will be created by the XALP.
The name should be representative of the data that is to be extracted.
As of DateOptional
This is the date to be used to determine which date effective
records up to and including the specified date are to be extracted.
Exception LevelMandatory, LOV available
‘0 – 9’ available

Report Filters
Work RulesThis is the work rule code that is to be extracted.
If left blank, all work rules will be extracted.