Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Human Capital Management
Lawson S3 HR/Payroll/Benefits
Separate company or process levels in exisiting company?
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Kyle P.
Past 24 Hours:
1
Prev. 24 Hours:
0
Overall:
5177
People Online:
Visitors:
280
Members:
0
Total:
280
Online Now:
New Topics
Lawson S3 Procurement
Adding Std Comments to all PO's
9/17/2024 7:06 PM
Does anyone know of a way to get trailing comments
Lawson S3 Procurement
Missing po info
9/4/2024 3:34 PM
We are experiencing an issue where freight account
Lawson S3 Procurement
We need to charge multiple items to 1 dept no mattter who orders the items. Our POs are out of company 1000 and cost centers are set up in company 1300. Does anyone else have this issue and have a way around it?
8/16/2024 1:55 PM
We have 3 items that need to be charged to the lab
Infor CloudSuite
Dbimport - only importing 1st record of file
8/13/2024 3:51 PM
In FSM Cloudsuite, I've got a file containing
Lawson S3 Procurement
How does everyone charge an item to 1 dept no matter who orders the item?
8/12/2024 6:20 PM
We have 3 items that need to be charged to the lab
IPA/ProcessFlow
WFWORKUNIT table, WF-STATUS field value set
7/25/2024 8:51 PM
documentation I can find has values for this field
Lawson S3 HR/Payroll/Benefits
Benefit change/termination rules
7/23/2024 2:22 PM
Can old benefit change/termination rules be delete
IPA/ProcessFlow
this.bean is null
7/19/2024 5:42 PM
Getting this error when my IPA gets to the second
IPA/ProcessFlow
Converting UTC Date to EST Date using Javascript
7/16/2024 2:53 PM
I'm looking for how others are performing a co
S3 Systems Administration
Changing the orgs email domain
7/12/2024 8:44 PM
Hello! We're changing our email
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3291
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1360
Roger French
1315
mark.cook
1244
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Human Capital Management
Lawson S3 HR/Payroll/Benefits
Separate company or process levels in exisiting company?
Please
login
to post a reply.
4 Replies
0
Subscribed to this topic
226 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
abassett
New Member
Posts: 4
8/13/2010 4:47 PM
We are adding 4 small "companies" to our exisiting Lawson population. We were planning to set up 1 new company (because that has been the practice) with 4 process levels, but I wonder if that makes sense. All 4 of these new groups are actually part of the existing Company 1 organization and each has a separate tax id.
Any thoughts on pros/cons of creating/not creating a new company for this?
Thanks for any input!
John Henley
Posts: 3353
8/13/2010 6:22 PM
moving to HR forum...
stephanie
Veteran Member
Posts: 330
8/16/2010 8:58 AM
The answer depends on your own business practices - do you need to easily report all companies together? Although you can merge company data using Crystal, HR Writer, Add-Ins, etc., standard Lawson reports generally don't allow that. A bigger consideration - do your employees move between companies (term in one, get hired in the other), or work in both? If so, you'll be better served setting up process levels instead of companies. Except for a few codes, if you use multiple companies you'll need to set up positions, job codes, benefits, personnel actions, etc. etc. separately, which can be a maintenance nightmare. Since you can set up different tax IDs by PL, I've always been a fan of keeping one company instead of multiple ones.
abassett
New Member
Posts: 4
8/16/2010 12:47 PM
Thanks so much Stephanie for your input - that is pretty much what I was thinking too.
John-thanks for getting my message to the right place.
MARCO3535
Advanced Member
Posts: 25
8/27/2010 6:13 PM
Stephanie,
My thinking exactly. My previous employer had a 2 company setup- instead of 1 company and 2 P/L .
It was a reporting nightmare, as well as the inconsistencies in the dept code, pay codes, job codes, not to mention the headaches - when a current ee 'transfers' between companies - 'terming' in 1 company and 'hiring' into the other company.
Eventually, we went to a 1 company setup, some prep work, lots of testing, but definitely worth it.
Later
Marco3535
Please
login
to post a reply.