Forums
Lawson Business Intelligence/Reporting/Crystal
Record selection formula - unexpected results
Author
Messages
JonA
Veteran Member
Posts: 1162
9/26/2013 6:43 PM
I've got a report that links MMDIST ==> POLINE (ROJ) and POLINE ==> MAINVDTL (ROJ). I'm looking for all invoice payments for PO lines charged to our supply accounts, grouping the data by whether the line is associated with an agreement or not. The end result is a graph that shows contract/non-contract supply spend for the health system. My issue is that MMDIST has multiple posting types resulting in duplicate data. I found if I eliminate all data with a posting type of H1 I'm left with good data, however when I put {MMDIST.POSTING_TYPE} <> "H1" in the record selection formula editor all the inventory lines disappear from my results. I also tried suppressing the H1 data by entering the formula in the section expert. The details look good but the total spend summary and the graphs on the report footer do not exclude the H1 postings so the totals are inflated. I'm baffled.
JonA
Veteran Member
Posts: 1162
9/27/2013 1:09 PM
Sometimes it just takes a little talking through the process to figure it out. I changed the join between POLINE and MMDIST to "Enforced Both" and the inventory lines remained with {MMDIST.POSTING_TYPE} <> "H1" in the record selection formula.
marencas
New Member
Posts: 1
7/14/2015 6:55 PM
Hello I just wanted to know do you know what H1 stands for in MMDIST? What transaction creates an H1 and how is it different than PT or PO?
Donna Simkovic
Posts: 25
12/21/2015 8:05 PM
Did anyone find out what H1 stands for in the Posting Type and Doc type in MMDIST?
mikeP
Veteran Member
Posts: 151
12/21/2015 8:16 PM
From the KB:
MMDIST Table H1 Posting Type
Article ID:5425286
Description:
I'm looking at the MMDIST table and see POSTING-TYPE of H1. What is this new value?
Resolution:
The H1 POSTING-TYPE MMDIST records are only created for the drill backs from GL. These were created due to an issue that was discovered where the drill backs from GL were only working for the prior month and lost for existing drills (if the same MMDIST record was involved) from month prior to that due to the RNI-OBJ-ID being overwritten on each run of the PO135. Basically, the same MMDIST record was being used then the RNI-OBJ-ID was being overwritten and the drill was lost if the Receiver stayed RNI for more than 1 month. The H1 POSTING-TYPE will not be 'posted' anywhere but will retain the correct amount that was posted for that month. You will also notice that these records will have the COMPONENT-SEQ increment monthly - this is to keep the record unique.