Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
IPA/ProcessFlow
Pulling correct reqline receipt date
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Wayne
Past 24 Hours:
0
Prev. 24 Hours:
1
Overall:
5120
People Online:
Visitors:
288
Members:
0
Total:
288
Online Now:
New Topics
Lawson S3 Financials
PO Matched Dollars and Matched Quantity
5/10/2024 6:51 PM
Can anyone share the Lawson calculation to determi
S3 Customization/Development
COBOL CSV file
5/10/2024 2:36 PM
We have a custom Cobol program ZU200 that creates
S3 Systems Administration
Using MFA for Lawson S3 Access
5/8/2024 1:23 PM
Does anyone use Multi Factor Authentication when u
Lawson Landmark
Executing IPA from PR160
5/3/2024 2:46 PM
We're facing a situation where we need to upda
IPA/ProcessFlow
Executing IPA from PR160
5/3/2024 2:46 PM
We're facing a situation where we need to upda
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
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
1354
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
IPA/ProcessFlow
Pulling correct reqline receipt date
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Normajean
New Member
Posts: 3
2/12/2013 9:41 PM
Hello Lawson folks;
I am a new member of the Enterprise data warehouse team and am working on the Lawson Supply Chain project.
Prior to my coming on board logic had been written to pull the received date for requisition line items by using the following process:
1. join to polinesrc to get the ponumber\poline number for the requisition line
(Join is polinesrc.source_doc_n = reqline.req_number and polinesrc.src_line_nbr = reqline.line_nbr)
2. join to porecline to get the received date for the po_number\po_line we found in #1 above (join is poreceive.po_number and poreceive.po_line_nbr.)
Comment: This logic is faulty as join #1 can produce multiples rows (there can be multiple polinesrc records associated with the same req_number\reqline_line_nbr.) AND join #2 can produce mulitple rows because the same po_number\po_line can be received multiple times.
So, now I need to find a clean, accurate way to find the receive date for each requisition line. I looked around and saw that there is a table called RQTRANS that looks like it might fill the bill.
The description of this table says "This file is the history of all deliveries for all requisitions. This file contains all requisition types: inventory, nonstock, special order, and services."
We don't currently bring this table into our enterprise data warehouse - and it will involve quite a bit of work to do so. We would for sure do this if it would fill the need but I thought I'd post something here to see if I could get some feedback prior to starting the project to let us know that we are on the right track.
Many thanks in advance for any feedback, tips or input you might be able to provide about this approach (or perhaps an even better one.)
JonA
Veteran Member
Posts: 1162
2/26/2013 7:43 PM
This is a good table to find the information you're looking for but you could still find multiple records if there are multiple receipts for the req line.
You are not authorized to post a reply.