Table of Contents
Entity Payroll ICMA Element From Pay Issue Date To Pay Issue Date Payroll Date Interface Code Interface Directory File Name Write or Append Output Header and Trailer File Records Exception The form may also be accessed through the command window with ‘UPICMA’. ‘Create ICMA Interface File’ Usage and Examples Report Parameters Entity Mandatory, LOV available Limits the process to the entity specified. Payroll Mandatory, LOV available Multiple payrolls may be selected per execution of this function. Pay Run Number Optional, LOV available ICMA Element Mandatory, LOV available Pay element that contains the deduction pay components that qualify for ICMA From Pay Issue Date Optional, Date, LOV available To Pay Issue Date Optional, Date, LOV available The ‘Pay Issue' date range will be used to determine which pay components within the element to report on. Payroll Date Mandatory, Date, LOV available The ‘Payroll Date' is the date printed in the file. Interface Code Mandatory, LOV available Only those reports of the format “TMRS Contributions” will display. Choose from the report formats created. The format “HL$TMRS2” has been provided as a sample, but should be copied, and the copy edited, by the client before running this report. The report definition selected will determine the format of the output file (if any), as well as the columnar content of the report. Interface Directory Mandatory, text Must be a directory on the server for which the current user (as signed onto the client’s network) has write capability. For example the entry ‘C:\TEMP’ accesses the ‘TEMP’ directory on the server, not the local directory for the computer terminal being used. File Name Mandatory, text Enter the name of the file that will be created in the interface directory specified. Write or Append Mandatory, LOV available If the file already exists should the current information overwrite it or append to it? Output a Header and Trailer Mandatory, LOV available If the file is to contain a header and trailer record then indicate <Yes>. Exception Level Mandatory, LOV available A ‘trace’ report of exception messages may be produced to assist in the testing phase. If necessary, choose from 0 – 9 (highest) level of trace. Please note that this is a voluminous report and will cause very slow performance.