century in univ.cfg file

Welcome to LawsonTalk. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.

Join our community!

If you're already a member please log in to your account to access all of our features:

century in univ.cfg file
Topic Started: Jan 14 2010, 09:39 AM (97 Views)
SAH	Jan 14 2010, 09:39 AM Post #1
Your Tax Dollars Hard at Work Posts: 378 Group: Members Member #416 Joined: February 7, 2006	It seems we're having non-stop issues with the century setting in order to display correctly in portal - we followed Lawson's KB article 5246202 and set the parm for 20, then we still had issues with the dates, and changed the field to 50. Now we're having more problems that get stranger by the minute - bad dates displaying on PA52 inquire (which do NOT match the dates on HR11 - very bizarre!!). It also seems to revolve around the PEM-I9-DOC-EXP-DT1 field, which is already an 8 character date field. If you've seen/experienced this, would you share your resolution? Please please don't make me open a call!!



schroncd	Jan 14 2010, 02:04 PM Post #2
Lawson Technorati Posts: 689 Group: Members Member #13 Joined: January 11, 2006	I've had some success at clients setting CENTURY to 25



Milo	Jan 19 2010, 09:35 AM Post #3
Rebmem Member Posts: 361 Group: Members Member #424 Joined: February 9, 2006	If you can tolerate a "CENTURY" setting set at 14, try removing the CENTURY setting entirely. With ESP7 I found that not using CENTURY at all was equivalent to a CENTURY setting of 15 (since the rollback occurs on the year listed, not on the year AFTER the year listed). Disclaimer: I only tested in the Financial suite of apps. We don't have PR or HR installed, and if there are issues there, I could not encounter them.


« Previous Topic · Coding, Program Errors and Bugs · Next Topic »