Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Enterprise Resource Planning & Manufacturing
Lawson S3 Procurement
Refresh of Buyer Code
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
1
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
57
Members:
0
Total:
57
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Enterprise Resource Planning & Manufacturing
Lawson S3 Procurement
Refresh of Buyer Code
Please
login
to post a reply.
0 Replies
0
Subscribed to this topic
2 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Terry P
New Member
Posts: 0
6/10/2014 8:07 PM
On the BUYER table in our Production system the Operator ID field contains the users Portal Login ID. It is displayed as "LSFPROD\pickering" in PO04, but stored as "NT000002bc" (We are on Windows platform). On our Development system, in PO04, it is displayed at "LSFDEV/pickering", but stored as "NT00000154". My understanding is the NT# is assigned when the user is created on the server.
The problem occurs when we refresh from Production ----> Test, the value stored (the NT #) in test is now now the correct NT value it should be. The only work around is to go into PO04, change the Operator ID field, and let it generate the correct value, then save it.
Any suggestions on how we can instruct Infor Managed Services to fix or correct this? They handle all the administrative stuff for us.
Please
login
to post a reply.