Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Supply Chain Management
Lawson S3 Supply Chain
OE53 and OE10 and OE90
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:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
74
Members:
0
Total:
74
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
Supply Chain Management
Lawson S3 Supply Chain
OE53 and OE10 and OE90
Please
login
to post a reply.
0 Replies
0
Subscribed to this topic
40 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
golfer24
New Member
Posts: 0
4/22/2011 9:10 PM
We're testing an MSP update (9.0.1 MSP4), and we use Order Entry quite extensively. This week, I've gotten this message or a similar message in both OE10 and OE90 when I try to do a change or an inquire action. So, I initially added my network login name into OE53, and that seemed to fix the issue with OE10. When I tried to change a hold code in OE90.1, I got the same error message. I added the NT name from listusermap like NT00230 or something similar to that, and that seems to have resolved the issue. To me, this is weird. Has anyone come across this issue within the 901 Applications for Order Entry?
Please
login
to post a reply.