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

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

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
7 26-Nov-2021 10:22 2 KB JMyers to previous
6 26-Nov-2021 10:22 2 KB JMyers to previous | to last
5 26-Nov-2021 10:22 2 KB JMyers to previous | to last
4 26-Nov-2021 10:22 4 KB JMyers to previous | to last
3 26-Nov-2021 10:22 4 KB JMyers to previous | to last
2 26-Nov-2021 10:22 4 KB JMyers to previous | to last
1 26-Nov-2021 10:22 26 bytes JMyers to last

Page References

Incoming links Outgoing links
Deferred Compensation...nobody
Deferred Compensation

Version management

Difference between version and

At line 3 removed one line
Deferred Compensation (ICMA)
At line 5 changed 7 lines
"The International City/County Management Association created the ICMA Retirement Corporation (RC) as a separate, not-for-profit organization in 1972."
To execute the required report the only set up required is a pay element and the Interface Format form (IDIF).
The benefit plan may be set up with the standard benefit components documented in the Benefits Administration manual (see the Pension Sample Plan).
Pay Element - IPPE
One pay element must be created in order to execute the report:
ICMA Element Pay element that contains the deduction pay components that qualify for ICMA
"The International City/County Management Association created the ICMA Retirement Corporation (RC) as a separate, not-for-profit organization in 1972." \\
At line 13 changed 3 lines
Interface Format - IDIF
If not already defined in the Interface Formats Definition form (IDIF), load the standard interface file format using the starter_idif_hl$icma.sql script.
Modify the standard ICMA file to bank requirements using the IDIF function. Rename the code from HL$ICMA to a user-defined code.
!!ICMA Setup
To execute the required report the only set up required is a pay element and the Interface Format form ([IDIF]).
The benefit plan may be set up with the standard benefit components documented in the Benefits Administration section (see the Pension Sample Plan). \\ \\
----
!Pay Element - [IPPE]
One pay element must be created in order to execute the report:
ICMA Element Pay element that contains the deduction pay components that qualify for ICMA\\ \\
----
!Interface Format - [IDIF]
If not already defined in the Interface Formats Definition ([IDIF])form, load the standard interface file format using the starter_idif_hl$icma.sql script.\\
Modify the standard ICMA file to bank requirements using the [IDIF] function. Rename the code from HL$ICMA to a user-defined code.\\
At line 17 changed 18 lines
Rec Field Start Position Ending Position Name Variable Number Notes
1 1 1 55 Company Name Enter in Constant
2 1 1 11 Filler
2 2 12 15 Plan ID Enter in Constant
3 1 1 4 Filler
3 2 5 14 Company PIN Enter in Constant
4 1 1 4 Filler
4 2 5 15 Total Contribution Total Contribution ICMA Element from UPICMA
4 3 16 30 Filler
4 4 31 41 Calculated Amount Total Contribution ICMA Element from UPICMA
5 1 1 9 Filler
5 2 10 15 Pay Issue Date Pay Issue Date Pay Header Issue Date
6 1 1 55 Employee Name Employee Name Identity Name
6 2 56 64 Employee SSN Employee SSN Identity Government ID
6 3 65 72 Filler
6 4 73 83 Employee Contribution Employee Contribution ICMA Element on UPICMA
||Rec||Field||Start Position||Ending Position||Name||Variable Number||Notes
|1 |1 |1 |55 |Company Name| |Enter in Constant
|2 |1 |1 |11 |Filler | |
|2 |2 |12 |15 |Plan ID| |Enter in Constant
|3 |1 |1 |4 |Filler | |
|3 |2 |5 |14 |Company PIN| |Enter in Constant
|4 |1 |1 |4 |Filler| |
|4 |2 |5 |15 |Total Contribution|Total Contribution|ICMA Element from [UPICMA]
|4 |3 |16 |30 |Filler| |
|4 |4 |31 |41 |Calculated Amount|Total Contribution|ICMA Element from [UPICMA]
|5 |1 |1 |9 |Filler| |
|5 |2 |10 |15 |Pay Issue Date|Pay Issue Date|Pay Header Issue Date
|6 |1 |1 |55 |Employee Name|Employee Name|Identity Name
|6 |2 |56 |64 |Employee SSN|Employee SSN|Identity Government ID
|6 |3 |65 |72 |Filler| |
|6 |4 |73 |83 |Employee Contribution|Employee Contribution|ICMA Element on [UPICMA]
At line 36 changed one line
!!Create ICMA Interface File
At line 38 changed 36 lines
‘Create ICMA Interface File’ Highlights
‘Create ICMA Interface File’ may be found through the menu bar:
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.
[{InsertPage page='UPICMA' section=2}]
This page (revision-7) was last changed on 26-Nov-2021 10:22 by JMyersTop