infor.com
concierge
infor u
developer portal
Home
Groups
Lawson - Supply Chain Management Customer Community [READ ONLY]
Matched, Not Received - PO136
Stace Webley
Could anyone tell me how to pull the PO136 Matched, Not Received data without having to actually run the report? I could do this with SQL, but I can't figure out which tables and columns are being used...Thanks in advance!
[Updated on 9/28/2015 10:53 AM]
Find more posts tagged with
Infor Lawson Supply Chain Management - Discussion
Comments
jon-athey
Hey Stace,
You should be able to get everything from the POLINE, PURCHORDER and MMDIST tables. The Matched Not Received quantity you see in the drill-around is a calculated number but everything else has it's own field.
Stace Webley
That's what is puzzling to me...the calculation I would think is:
SELECT SUM(ENT_UNIT_CST*(MATCHED_QTY-REC_QTY)) AS MNR FROM POLINE
WHERE MATCHED_QTY > REC_QTY
But this isn't returning anything even close to what PO136 shows.
jon-athey
I must have overlooked this but there is a matched not received field.
MATCHED-NO-REC
But yes, it's difficult to figure out sometimes. Our PO136 doesn't match what I pull with that formula either. But using the actual MNR field gets a lot closer. In the first couple years using Lawson we had a lot of issues with AP not matching lines or buyers doing chargebacks that messed up the data. Maybe if you looked at each PO and tried to identify what's missing or what's extra and modify your report to account for those..
Stace Webley
I must have looked over that column a dozen times...thanks for pointing that out. It does get me a lot closer, and I can live with that. The varience is very small. I surprised it still doesn't tie out though. When you use the PO line cost with or without tax it still doesn't match the PO136 report. Like I said though it is very close. I wonder if it is using an invoice cost that is different than the PO cost in some cases. I can check that in MMDIST. Thank you for the assistance, Jon.
unknown
FYI - you aren't crazy. It's a new field to v10 that got pushed back to older versions in CPT. It's also not always populating on my v9 data.
We're testing v10 now and it correctly populates for all lines I've checked so far.
Quick Links
All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Popular Tags
Infor Lawson Human Resources Group - Discussion
Infor Lawson Technology Group - Discussion
General Discussions
VISUAL - Enterprise General Discussions
Infor Lawson Supply Chain Management - Discussion
Process Automation (IPA) - General Discussions
Pegasus - Partner General Discussions
Infor Lawson Supply Chain Group - Discussion
Infor Lawson Financials Group - Discussion
Infor EPM Discussions