Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Financial Management
Lawson S3 Financials
User Audit Trail? - AR82.1 - Returned Payment
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
267
Members:
0
Total:
267
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson S3 Financials
User Audit Trail? - AR82.1 - Returned Payment
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Garth Gerwing
Basic Member
Posts: 27
2/15/2013 7:18 PM
In evaluating the results of AR82.1 - Returned Payment - I am not seeing anything relating to a user/login audit trail on the resulting Debit Memo??
It would appear that Lawson is ignoring/breaking some of it's own data architecture rules in creating these results:
- does not enforce/write a Debit Memo Reason Code (even though this is a required value for any debit memos being entered into AR)
- does not write a corresponding TX Batch occurrence (BLINVHDR) - even though the Debit Memo is given a batch number (some incremental "dummy" value)
It is the TX Batch occurrence (BLINVHDR) that has an OPR-CODE (Operator Code) attribute - which would be the appropriate audit trail attribute - but since no TX batch occurrence is physically being written in the returned payment scenarios.......
Has anyone else tripped over this in thier travels - or perhaps has some words of wisdom I.E. am I missing something? Any feedback would be appreciated.
You are not authorized to post a reply.