This page (revision-8) 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
8 26-Nov-2021 10:22 3 KB jmyers to previous LOAD DATA FLDR ==> LOAD DATA FLDR(System_Preference)
7 26-Nov-2021 10:22 3 KB jmyers to previous | to last EXTRCT DATA FLDR ==> EXTRCT DATA FLDR(System_Preference)
6 26-Nov-2021 10:22 3 KB jmyers to previous | to last ATTACHMENTS FLDR ==> ATTACHMENTS FLDR(System_Preference)
5 26-Nov-2021 10:22 3 KB JEscott to previous | to last
4 26-Nov-2021 10:22 3 KB JEscott to previous | to last
3 26-Nov-2021 10:22 3 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 1 KB JEscott to last

Page References

Incoming links Outgoing links
XALP
XALP

Version management

Difference between version and

At line 5 removed one line
At line 15 changed one line
Before the XALP can be run there are [site preferences|SYSTEM PREFERENCE] 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.
Once the .xml and .data file have been created, it is suggested to review the .xml file to ensure the correct data was extracted.
At line 17 changed 9 lines
The extract directory is defined using the [EXTRCT DATA FLDR|EXTRCT DATA FLDR(System_Preference)] preference. The load directory is defined using the [LOAD DATA FLDR|LOAD DATA FLDR(System_Preference)] preference. The [ATTACHMENTS FLDR|ATTACHMENTS FLDR(System_Preference)] must be specified so the load functions know where to write the report exceptions log to.
Once the XALP 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.
[UserCalcs|USERCALC], [pay components|PAY COMPONENTS], and [elements|PAY ELEMENTS] are not extracted with the XALP. This means that prior to running the [LMDATA] to load the new attendance plan, any [UserCalcs|USERCALC], [pay components|PAY COMPONENTS] or [elements|PAY ELEMENTS] associated to the plan must already exist in the receiving database, otherwise the [LMDATA] will fail to load. User calcs may be extracted via the [XMUC] function. Once they have been extracted they must be loaded into the other database using the [LMDATA] prior to the new attendance plan being loaded. [Pay components|PAY COMPONENTS] or [elements|PAY ELEMENTS] will have to be entered manually.
The user will then load the .data file into the receiving database via the [LMDATA] process.
Once the file has been uploaded, the new leave policy will have to be added to the leave schedule to allow the employees access to the newly added leave policy.
You will then load the .data file into the receiving database via the LMDATA process described in UBEF section in chapter 5. You will then have to add an entry to the leave schedule to allow the employees access to the newly added leave policy.
At line 27 changed one line
!!Report Parameters & Filters
!!Report Parameters
At line 47 removed 5 lines
----
![Notes|Edit:Internal.XALP]
[{InsertPage page='Internal.XALP' default='Click to create a new notes page'}]
This page (revision-8) was last changed on 26-Nov-2021 10:22 by jmyersTop