My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2 - 2008
Clerk
>
Contracts / Agreements
>
I
>
INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2 - 2008
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/28/2017 10:18:01 AM
Creation date
3/5/2008 9:54:40 AM
Metadata
Fields
Template:
Contracts
Company Name
INFOR (US) INC. (FORMERLY Lawson Software Americas, Inc.)
Contract #
A-2008-037
Agency
FINANCE & MANAGEMENT SERVICES
Council Approval Date
3/3/2008
Insurance Exp Date
11/1/2009
Destruction Year
0
Notes
NAME CHANGE AS OF 7/1/12 SEE LETTER AUTO & WORKER'S COMP EXP 11/1/09
Document Relationships
INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2A
(Amended By)
Path:
\Contracts / Agreements\I
INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2B
(Amended By)
Path:
\Contracts / Agreements\I
INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2C
(Amended By)
Path:
\Contracts / Agreements\I
INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2D -2010
(Amended By)
Path:
\Contracts / Agreements\I
INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2E -2008
(Amended By)
Path:
\Contracts / Agreements\I
INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2F
(Amended By)
Path:
\Contracts / Agreements\I
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
511
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
This over /under filled positions can be tracked in several ways, depending upon <br />the outcome that The City of Santa Ana desires. A factor in determining how <br />over /under filled position are processed is dependent upon how the budget check <br />flag is set (as described in the response to item #1). If the budget check flag is <br />set to "do not exceed" the system will not let you exceed an allocated budgeted <br />amount per position, so adjustments must be made to the budget to <br />accommodate the situation. If the budget check flag is set to NO and budgets <br />are not checked, users are allowed to assign employees to any position as <br />needed and can identify the assigned position as an over /under fill by a user field <br />on the position. <br />If the budget check is turned on, the most common method used to <br />accommodate over /under filled positions is to simply change the budget <br />allocation for both the filled and the lesser position. Lawson allows two different <br />budgeted amounts to be tracked for each position, 1) the original and 2) an <br />adjusted budget amount. Some cities chose to make the budget changes into <br />the adjusted budget amount and use that number for budget validation and <br />comparisons. This allows cities to track both the original planned budget and the <br />over /under filled activity. <br />For example: Position A (higher) and Position B (lower) were both originally <br />budgeted for 1 FTE each. Position A is vacant, Position B is filled. When the <br />decision is made to use the Position A budget to fill a second Position B, a <br />change is made in the adjusted budget amount to accommodate this. The <br />adjusted budget for Position A is changed to 0 and the adjusted budget for <br />Position B is changed to 2. This will allow you to assign the lesser position to the <br />employee and still meet your budget controls. The original budget is intact for <br />reports and inquires, while the adjusted budget shows the changes. Again, a <br />user field or reason code can be assigned to the position or the employee to <br />indicate a report upon any over /under filled status. <br />If the budgeted amounts cannot be changed (as described above), and you also <br />want the budget checking controls in place (as describe in item #1), you will need <br />to manipulate the employee's position assignments to work around the budget <br />edit controls or the edit controls themselves. Since Lawson allows an employee <br />to be assigned up to 98 active positions, you could assign the employee to 2 <br />positions, both the upper position they are filling and the lower position they are <br />actually performing. Assigning the employee to the upper position as their <br />primary position allocates the FTE to that budget properly. Rules can be set to <br />ignore the 2 — 981h positions in the budget checking controls. Other alternative <br />methods could be determined after a detailed discussion to understand the City's <br />desired outcome for reporting, etc. <br />4. If a position has the flexibility of hiring or promoting at different levels such as an <br />analyst to a senior analyst how would management be able to track this in your <br />system without having to identify a vacant position at the higher level? <br />Lawson Response: <br />If your budget controls are set to adhere to an exact budget match (see response <br />to item #1) , then a vacant position must be identified in order for the promotion <br />to take place and the new position to be assigned to the employee. <br />Lawson Software - Confidential <br />
The URL can be used to link to this page
Your browser does not support the video tag.