Before the XDIF 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 XDIF has completed 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, pay components, and elements are not extracted with the XDIF. This means that prior to running the LMDATA to load the new interface, any UserCalcs, pay components or elements associated to the interface 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 interface being loaded. Pay components or elements will have to be entered manually.
The user will then load this .data file into the receiving database via the LMDATA process.
Report Parameters | |
---|---|
Export File Name | Mandatory This is the name of the file that will be created by the XDAPP. The name should be representative of the data that is to be extracted. |
Interface Codes | Optional, LOV Available The user may select specific interfaces to extract. If the parameter is left blank, all interfaces will be extracted. |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation