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
Posted transactions' time stamp
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
chaoticist
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5185
People Online:
Visitors:
195
Members:
0
Total:
195
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
Posted transactions' time stamp
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Lawson Beginner
Basic Member
Posts: 6
7/24/2014 6:16 PM
Hi,
We needed to send some GL update reports on a daily basis to a few third party vendors. In order to avoid duplication of the records sent, we ideally liked to filter the GL transactions in the DB based on the posted time stamp and schedule a job to run once a day. However, we developed a circuitous work-around to meet this requirement.
Currently, we are trying to eliminate the work-around and send the list of GL transactions based on the posted time stamp (please note that it is not transaction time stamp or release time stamp) directly from Lawson to the third parties.
We discovered that such a time stamp is non-existent with the GL records. We do not know if either Lawson (version details given below) does not have the provision to append posted time stamp to the GL records or if the feature was not enabled when it was implemented a few years ago.
Is this doable in the version stated below? And if yes, then by enabling that feature are we compromising on the performance of the system in the long run?
Application version: 9.0.1.3,
Foundation: 9.0.1.7
Thanks for your time and input.
Vicki
Basic Member
Posts: 10
7/24/2014 7:04 PM
We are doing a similar thing and ended up using the object id. We keep a compare file going back 7 days and compare the new file we extract to the compare file matching on object id and if it exists in the compare file, we know it would be a duplicate to resend.
Deron
Advanced Member
Posts: 25
7/24/2014 8:53 PM
What Vicki wrote sounds like your best bet. OBJ_ID is unique. Assuming you're sending only posted transactions to your vendors, make sure to specify GLTRANS.R_STATUS = 9, otherwise you could get some of the memo transactions created with intercompany journals as well as released and unreleased journals.
Lawson Beginner
Basic Member
Posts: 6
7/28/2014 2:44 PM
Thanks Vicki & Deron. We'll give the proposed solution a try.
Lawson Beginner
Basic Member
Posts: 6
6/5/2015 3:28 PM
Hello,
We finally are in the implementation phase for replacing the work-around and came across a two more tables that are being used presently. These tables are GLSCCAT and GTMXVALUE
1. These tables have a relation with GLTRANS table . Can someone please tell what is the functional significance of this relationship
2. Which processes update the GLSCCAT and GTMXVALUE.
3. If we are trying to send a Transactions balance report from GLTRANS using Object ID and Status=9. Is there any other field we need to consider ?
Thanks
Lawson Beginner
Basic Member
Posts: 6
6/9/2015 12:44 PM
Hello,
It would be great if some one can help me understand the doubts I have.
Thanks
You are not authorized to post a reply.