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
New System Code added
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:
48
Members:
0
Total:
48
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
Human Capital Management
Lawson S3 HR/Payroll/Benefits
New System Code added
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
69 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
slm4
Basic Member
Posts: 13
2/19/2013 3:40 PM
We recently added a new system code to keep our in-house written programs separate.
In writing the first program for that new system code I am encountering a message that does not give me enough information to determine problem. Error msg is:
Line 5 : Invalid Tran Code Found
Previous to that I had gotten valid errors and fixed those. Line 5 is a comment line.
Any ideas?
Lee
Posts: 37
4/17/2013 5:43 PM
Split
We have a number of custom system codes - don't know if our programmers ran into that one. Key is naming convention(s) that you adopt in the new system code. We quite often (not always) will prefix the field names with the system code followed by the name of the field (i.e. NAME=G1-NAME) in order to keep the custom code separate from Lawson code - which, potentially, could really mess up the rest of the Lawson tables that already use the field 'NAME' from the employee table, etc. Also, under LAUA, our biggest issue was activating 'drill-around' capabilities.
Please
login
to post a reply.