Lawson Enhancement Request
Number 5800.
Contact Information:
Name: Penny Pierce
System Information:
Environment Release:
8.0
Application Release:
8.0
, Hardware: Windows
2000
Product: HUMAN RESOURCES
SUITE - BENEFITS ADMINISTRATION
, Program: Change Rules
BN16.3
Brief Description: When a personnel action is performed for pay frequency changes, a change rule should update the RS plan enrollments as it does for DC, DI, DL, EL, and HL plans.
Business Case: Since the change rules do not work for RS plan types we have to manually adjust the enrollments for all personnel actions performed that affect pay frequency. It is confusing for the end user since this manual process has to skip back and forth from addressing the benefit on BN32.1, back to PA52.1 for the personel action and then back again to BN32.1 to finish the change to the RS plan enrollments. If not done this way users get errors on the enrollment change either that the "Prem start date and group name does not match with benefit" (if the personnel action is done first) or "Cycles remaining cannot be greater that frequency table" (if the benefit change is done first)
Solution: The change rule should update the RS plans as it does for all other plans when a personnel action is done that affects the employee's pay frequency.
Current Review Period:
Start Date
End Date
04/01/2004
06/30/2004
******************************************************************************************************************************************
Contact Information: Name: Stacy Davis
System Information: Environment
Release: 8.0 , Application Release: 8.0
Hardware: Windows 2000 , Product: FINANCIAL
SUITE - ACCOUNTS PAYABLE
Program: MA63
Brief Description: On MA66.3 when you select Accept in the PO cost field, it puts the invoice cost in the amount field, and it does not allow you to change the amount. This seem very confusing if you are accepting the cost on the PO, but the invoice cost is the cost that appears in the amount field. When accepting the PO cost, it should default the PO cost in the amount box. Also on MA66.3 there should be a flag to create a chargeback like you can on MA66.2.
Business Case: Both of these enhancements would streamline the cost message process. The invoice message screen is used by many buyers that do not use Lawson on a daily basis, so the more intuitive this screen is the better. The first request of having the the PO cost appear in the amount field when you accept the PO cost is more logical that the way it works today. When the invoice cost appears in this field it is misleading because it appears as though you are acceepting that cost and not the PO cost. As for the auto creating a chargeback, it would allow the AP clerk to not handle the invoice a second time for errors that were a result of the supplier billing incorrectly.
Solution: On MA66.3 when you select Accept in the PO cost field,it should default the PO cost in the amount box. Also on MA66.3 there should be a flag to create a chargeback that works that same way as the create a chargeback on MA66.2.
Review Process Information: Your new
request will be reviewed and a status provided within 30 days following the
"Current Review" period end date.
Start
Date End Date
01/01/2004
03/31/2004
******************************************************************************************************************************************
Contact Information: Name: Stacy Davis
System Information: Environment
Release: 7.3.1
Application Release: 7.2
, Hardware: AS400
Product: FINANCIAL
SUITE - ACCOUNTS PAYABLE , Program: MA01.1
Brief Description: The PO Cost Messaging rule group needs to be able to be set at the vendor level and not just at the company level.
Business Case: We have many suppliers for raw materials that invoice for well over 100,000 lbs of an item at a time and the unit cost for many of these items is under $1. For these suppliers we do not want any unit cost tolerances for PO Cost Messages, but for suppliers of office supplies for example we would not want to receive a cost message if the unit cost on an invoice for one pen was off by $.05 per unit.
Solution: There would need to be a "Y or N" field added to the messaging tab on MA01.1 to allow PO cost message tolerances to be based on the rule groups assigned to the Match Table assigned to the vendor. If there was not a Match Table assigned to the vendor, then it would use the company default rule group from MA01.1. This would allow some vendors for smaller qty items to have invoices processed without cost messages on small discrepancies, but vendors for large qty items would be able to have zero or extremely low tolerances.
******************************************************************************************************************************************Contact Information: Name: Stacy Davis
System Information: Environment
Release: 8.0
Application Release: 8.0 , Hardware: UNIX
Product: PROCUREMENT SUITE -
REQUISITIONS, Program: RQ10
Brief Description: There should be an option on RQ to add comments that print on BOTH the requisition and the PO. Many times the comments are a continuation of the item description and this needs to print on both documents.
Business Case: Most comments are necessary on both the PO and the Req so they have to be added twice in order for them to print in both doucments.
Solution: Add another option to the comments on RQ10 for comments to print on both the req and the PO.
Current Review Period:04/01/2004
06/30/2004
Current Review Period:
Start
Date End Date
01/01/2004
03/31/2004
Your Request will be reviewed in the next
Review Period:
Start Date End Date
Lawson Enhancement Request
Number 5663.
Contact Information:
Don Zoz
System Information:
Environment Release:
8.0
Application Release:
8.0
Hardware: UNIX
Product: HUMAN RESOURCES
SUITE - PAYROLL
Program: PR113
Brief Description: Allow users to selectively choose which errors print in the Error reports.
Business Case:
We ran through the PR113
on our final test upgrade, and receive 400 pages of errors. These
errors generate for all types of employee and employer taxes that we do
not utilize. It will take a significant effort to review these errors
to filter out what is pertinant.
Solution:
Build a table or list of
error codes that the user can choose to not print. This would put
control of the error print and review in the user hands. This would
allow the user to select to review only certian errors generated within
a severity level.
Current Review Period:
Start Date
End Date
04/01/2004
06/30/2004
****************************************************************************************************************************************
ER
Entered Product -
Program
Hardware - Env - App Status
5371
03/04/2004 Human Resources Suite - Employee
& Manager Self Service - Savings Plan Modeling UNIX - 7.3.3 - 8.0 New
Request
Request Information
ER NUMBER: 5371
ER Status: New Request
Select the product for enhancement
Program/Product/Tool (ex. AP10, ags, dbdef)
Human Resources Suite -
Employee & Manager Self Service Savings Plan Modeling
Provide a Brief Description
for the enhancement.
Need to change language
on the input screen for Company Contributions.
Needs to indicate that the
intended percent is of EE Contribution, not EE Salary.
****************************************************************************************************************************************
ER 5014 (Brief Description: Request to not have company paid deductions expense to noncash pay.)
Contact: Joe Edmiston
The status of Lawson Enhancement Request Number 5014 has been updated.
NEW STATUS: Considered for Future
Lawson will consider it for future development but this does not imply or guarantee it will happen.
Current Review Period:
Start Date End Date
04/01/2004 06/30/2004
****************************************************************************************************************************************
Enhancement Request Number 5967.
Contact Information: Name: Joe Edmiston
System Information: Environment Release: 8.0
Application Release: 8.0
Hardware: UNIX, Product: HUMAN RESOURCES SUITE - PAYROLL
Program: PR280
Brief Description:
Include the user id of the person who made a change to an employee's deduction on the PR280-Deduction Audit Report.
Business Case:
We allow employees to update their w/holding exemptions using
the employee portal; however, we have no way of knowing if they changed
their own information or if someone in payroll keyed the change.
Our employees often don't recall making the change and feel that we
should pay any additional taxes they owe if not enough tax was
withheld. They ask us to prove that they requested a change to
their withholding exemptions.
Solution:
Put the name of the user who made the change to an employee
deduction on the PR280 report so we can show them that payroll staff
did not make the change to their record.
Current Review Period:
Start Date End Date
04/01/2004 06/30/2004