Some additional resources:

• Sales Order Processing (SOP) SQL views
• Sales Order Processing (SOP) commonly used tables
• Other GP Reporting links

create view view_Sales_Qty_by_Item_Site_Month
as

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
--view_Sales_Qty_by_Item_Site_Month
--Created Jun 14, 2013 by Victoria Yudin - Flexible Solutions Inc
--For updates see http://victoriayudin.com/gp-reports/
--Returns total sales quantities fulfilled (SOP invoices less
--  returns) for each item by month for hardcoded year
--Calendar months and Document Dates are used
--Only posted invoices and returns are included
--Quantity is calculated by multiplying by QTYBSUOM column in
--  case other UofM's are used on transations
--Voided transations are excluded
--Item Description is taken from Inventory Item Maintenance
--  for all inventory items
--  and from SOP line items for non-inventory items
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

select
d.ITEMNMBR Item_Number, d.Item_Description,
d.LOCNCODE Site_ID,
sum(case when month(d.DOCDATE) = 1
    then d.Qty else 0 end) as Jan_Qty,
sum(case when month(d.DOCDATE) = 2
    then d.Qty else 0 end) as Feb_Qty,
sum(case when month(d.DOCDATE) = 3
    then d.Qty else 0 end) as Mar_Qty,
sum(case when month(d.DOCDATE) = 4
    then d.Qty else 0 end) as Apr_Qty,
sum(case when month(d.DOCDATE) = 5
    then d.Qty else 0 end) as May_Qty,
sum(case when month(d.DOCDATE) = 6
    then d.Qty else 0 end) as Jun_Qty,
sum(case when month(d.DOCDATE) = 7
    then d.Qty else 0 end) as Jul_Qty,
sum(case when month(d.DOCDATE) = 8
    then d.Qty else 0 end) as Aug_Qty,
sum(case when month(d.DOCDATE) = 9
    then d.Qty else 0 end) as Sep_Qty,
sum(case when month(d.DOCDATE) = 10
    then d.Qty else 0 end) as Oct_Qty,
sum(case when month(d.DOCDATE) = 11
    then d.Qty else 0 end) as Nov_Qty,
sum(case when month(d.DOCDATE) = 12
    then d.Qty else 0 end) as Dec_Qty,
sum(d.Qty) Total_Qty

from
(select sh.DOCDATE, sd.ITEMNMBR, sd.LOCNCODE,
 coalesce(I.ITEMDESC, sd.ITEMDESC) Item_Description,
 case sd.SOPTYPE
     when 3 then sd.QTYFULFI*QTYBSUOM
     when 4 then sd.QUANTITY*QTYBSUOM*-1
     end Qty
 from SOP30200 sh
 inner join SOP30300 sd
     on sd.SOPNUMBE = sh.SOPNUMBE
     and sd.SOPTYPE = sh.SOPTYPE
 left outer join IV00101 I
     on I.ITEMNMBR = sd.ITEMNMBR
 where sh.VOIDSTTS = 0
     and sh.SOPTYPE in (3,4)
	 and year(sh.DOCDATE) = 2013 --change year as needed
     and sd.ITEMNMBR not like 'XXXXXXXXXXXXXXX%') d

group by d.ITEMNMBR, d.Item_Description, d.LOCNCODE

go
grant select on view_Sales_Qty_by_Item_Site_Month to DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

create view view_Sales_by_Customer_by_Month
as

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_Sales_by_Customer_by_Month
-- Created June 7, 2013
--    by Victoria Yudin - Flexible Solutions, Inc.
-- For updates see http://victoriayudin.com/gp-reports/
-- Returns total sales (invoices - returns) for each customer
--    by month (for the specified year)
-- Amount used is the invoice total (including freight,
--    taxes, discounts, etc.)
-- Only posted invoices and returns are included
-- Shows functional currency
-- Voided transactions are excluded
-- Document Date is used (not GL Posting Date)
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

select
d.CUSTNMBR Customer_ID,
d.CUSTNAME Customer_Name,
sum(case when month(d.DOCDATE) = 1
  then d.SALES else 0 end) Jan_Sales,
sum(case when month(d.DOCDATE) = 2
  then d.SALES else 0 end) Feb_Sales,
sum(case when month(d.DOCDATE) = 3
  then d.SALES else 0 end) Mar_Sales,
sum(case when month(d.DOCDATE) = 4
  then d.SALES else 0 end) Apr_Sales,
sum(case when month(d.DOCDATE) = 5
  then d.SALES else 0 end) May_Sales,
sum(case when month(d.DOCDATE) = 6
  then d.SALES else 0 end) Jun_Sales,
sum(case when month(d.DOCDATE) = 7
  then d.SALES else 0 end) Jul_Sales,
sum(case when month(d.DOCDATE) = 8
  then d.SALES else 0 end) Aug_Sales,
sum(case when month(d.DOCDATE) = 9
  then d.SALES else 0 end) Sep_Sales,
sum(case when month(d.DOCDATE) = 10
  then d.SALES else 0 end) Oct_Sales,
sum(case when month(d.DOCDATE) = 11
  then d.SALES else 0 end) Nov_Sales,
sum(case when month(d.DOCDATE) = 12
  then d.SALES else 0 end) Dec_Sales,
sum(d.SALES) Yearly_Total

from
(select s.DOCDATE, s.CUSTNMBR, c.CUSTNAME,
 case s.SOPTYPE
   when 3 then s.DOCAMNT
   when 4 then s.DOCAMNT*-1
   end SALES
 from SOP30200 s
 left outer join RM00101 c
   on s.CUSTNMBR = c.CUSTNMBR
 where s.VOIDSTTS = 0
   and s.SOPTYPE in (3,4)
   and year(s.DOCDATE) = 2013 --change year as needed
 ) d

group by d.CUSTNMBR, d.CUSTNAME

-- add permissions for DYNGRP
go
grant select on view_Sales_by_Customer_by_Month to DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

Here is an example of an SOP transaction in GP:

Using the following SQL code you can see this data in SQL:

select SOPTYPE, SOPNUMBE, LNITMSEQ, ITEMNMBR
from SOP10200 where SOPNUMBE = 'ORDST2227'

The results look like this:

The LNITMSEQ column is what determines the order of the lines. If you wanted to know which line is 1st, 2nd, 3rd, that would be a little difficult. The code below will add a sequential line number to this data using the line item sequence to determine the order of the lines:

select
row_number() over (partition by SOPNUMBE, SOPTYPE
 order by LNITMSEQ) LineNumber,
SOPTYPE, SOPNUMBE, LNITMSEQ, ITEMNMBR
from SOP10200
where SOPNUMBE = 'ORDST2227'

Now your results will include a line number column:

For more tips like this sign up for the GP Reports Viewer newsletters. You can see past newsletters on the GP Reports Viewer website.

• Current
• 31 to 60 Days
• 61 to 90 Days
• 91 and Over

If you would like to use different aging buckets, just follow the examples in my code and change the labels and number of days.

Additional resources:

• Receivables SQL views
• Receivables module commonly used tables
• Other Dynamics GP reporting links

create view view_Current_Receivables_Aging_Detail
as

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_Current_Receivables_Aging_Detail
-- Created May 1, 2012 by Victoria Yudin, Flexible Solutions Inc
-- For updates see http://victoriayudin.com/gp-reports/
-- Shows current AR aging in detail w/ hard-coded aging buckets
-- Tables used:
--     CM - RM00101 - Customer Master
--     RM - RM20101 - Open Transactions
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

select
CM.CUSTNMBR Customer_ID,
CM.CUSTNAME Customer_Name,
CM.PYMTRMID Customer_Terms,
CM.CUSTCLAS Customer_Class,
CM.PRCLEVEL Price_Level,
case RM.RMDTYPAL
  when 1 then 'Sale / Invoice'
  when 3 then 'Debit Memo'
  when 4 then 'Finance Charge'
  when 5 then 'Service Repair'
  when 6 then 'Warranty'
  when 7 then 'Credit Memo'
  when 8 then 'Return'
  when 9 then 'Payment'
  else 'Other'
  end Document_Type,
RM.DOCNUMBR Document_Number,
RM.DOCDATE Document_Date,
RM.DUEDATE Due_Date,
case
  when RM.RMDTYPAL < 7 then RM.ORTRXAMT
  else RM.ORTRXAMT * -1
  end Document_Amount,
case
  when RM.RMDTYPAL < 7 then RM.CURTRXAM
  else RM.CURTRXAM * -1
  end Unapplied_Amount,
case
  when DATEDIFF(d, RM.DUEDATE, getdate()) < 31
     and RM.RMDTYPAL < 7 then RM.CURTRXAM
  when DATEDIFF(d, RM.DOCDATE, getdate()) < 31
     and RM.RMDTYPAL > 6 then RM.CURTRXAM *-1
  else 0
  end [Current],
case
  when DATEDIFF(d, RM.DUEDATE, getdate()) between 31 and 60
     and RM.RMDTYPAL < 7 then RM.CURTRXAM
  when DATEDIFF(d, RM.DOCDATE, getdate()) between 31 and 60
     and RM.RMDTYPAL > 6 then RM.CURTRXAM * -1
  else 0
  end [31_to_60_Days],
case
  when DATEDIFF(d, RM.DUEDATE, getdate()) between 61 and 90
     and RM.RMDTYPAL < 7 then RM.CURTRXAM
  when DATEDIFF(d, RM.DOCDATE, getdate()) between 61 and 90
     and RM.RMDTYPAL > 6 then RM.CURTRXAM * -1
  else 0
  end [61_to_90_Days],
case
  when DATEDIFF(d, RM.DUEDATE, getdate()) > 90
     and RM.RMDTYPAL < 7 then RM.CURTRXAM
  when DATEDIFF(d, RM.DOCDATE, getdate()) > 90
     and RM.RMDTYPAL > 6 then RM.CURTRXAM *-1
  else 0
  end [91_and_Over]

from RM20101 RM

inner join RM00101 CM
     on RM.CUSTNMBR = CM.CUSTNMBR

where RM.VOIDSTTS = 0 and RM.CURTRXAM <> 0

-- add permissions for DYNGRP
GO
grant select on view_Current_Receivables_Aging_Detail to DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

• Current
• 31 to 60 Days
• 61 to 90 Days
• 91 and Over

If you would like to use different aging buckets, just follow the examples in my code and change the labels and number of days.

Additional resources:

• Payables SQL views
• Payables module commonly used tables
• Other Dynamics GP reporting links

create view view_Current_Payables_Aging_Detail
as

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_Current_Payables_Aging_Detail
-- Apr 24, 2013 - Victoria Yudin, Flexible Solutions, Inc.
-- Shows current AP aging
-- Functional currency only
-- Aging by due date
-- For updates please see:
--	 http://victoriayudin.com/gp-reports/
-- For other payables SQL scripts:
--	 http://victoriayudin.com/gp-reports/payables-sql-views/
-- Updated Apr 25, 2013 to fix aging buckets for credit docs
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

select
VM.VendORID Vendor_ID,
VM.VendNAME Vendor_Name,
VM.VNDCLSID Vendor_Class,
VM.PYMTRMID Vendor_Terms,
case P.DOCTYPE
  when 1 then 'Invoice'
  when 2 then 'Finance Charge'
  when 3 then 'Misc Charge'
  when 4 then 'Return'
  when 5 then 'Credit Memo'
  when 6 then 'Payment'
  end Document_Type,
P.DOCNUMBR Document_Number,
P.DOCDATE Document_Date,
P.PSTGDATE GL_Posting_Date,
P.DUEDATE Due_Date,

P.TRXDSCRN [Description],

case
  when P.DOCTYPE < 4 then P.DOCAMNT
  else P.DOCAMNT * -1
  end Document_Amount,

case
  when P.DOCTYPE < 4 then P.CURTRXAM
  else P.CURTRXAM * -1
  end Unapplied_Amount,

case
  when datediff(d, P.DUEDATE, getdate()) < 31
       and P.DOCTYPE < 4 then P.CURTRXAM
  when datediff(d, P.DOCDATE, getdate()) < 31
       and P.DOCTYPE > 3 then P.CURTRXAM * -1
  else 0
  end [Current],

case
  when datediff(d, P.DUEDATE, getdate()) between 31 and 60
       and P.DOCTYPE < 4 then P.CURTRXAM
  when datediff(d, P.DOCDATE, getdate()) between 31 and 60
       and P.DOCTYPE > 3 then P.CURTRXAM * -1
  else 0
  end [31_to_60_Days],

case
  when datediff(d, P.DUEDATE, getdate()) between 61 and 90
       and P.DOCTYPE < 4 then P.CURTRXAM
  when datediff(d, P.DOCDATE, getdate()) between 61 and 90
       and P.DOCTYPE > 3 then P.CURTRXAM * -1
  else 0
  end [61_to_90_Days],

case
  when datediff(d, P.DUEDATE, getdate()) > 90
       and P.DOCTYPE < 4 then P.CURTRXAM
  when datediff(d, P.DOCDATE, getdate()) > 90
       and P.DOCTYPE > 3 then P.CURTRXAM * -1
  else 0
  end [91_and_Over]

from PM00200 VM  --vendor master
inner join PM20000 P  --open payables
   on P.VENDORID = VM.VENDORID

where P.CURTRXAM <> 0 and P.VOIDED = 0

-- add permissions for DYNGRP
GO
grant select on view_Current_Payables_Aging_Detail to DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

REPLACE(YourString, ‘text to replace’, ‘replace with text’)

Below is a practical example of how useful this can be.

Mass Modify in Dynamics GP allows you to quickly create new General Ledger accounts by copying from existing accounts. However, the names of the accounts either get created from the segment setup, which is not always optimal or correct, or the existing account names get copied. Most of the time, I use the latter option and have the account names copy from the exiting accounts. Here is an example of a list of account numbers for the Sales department (first segment 300) in the Dynamics GP sample company:

If you copy all of these accounts to create a new accounts for the Marketing department (first segment 350) choosing ‘Use Account Description From Existing Accounts’ the account numbers will be new, but the account names will still be the same:

Using REPLACE in SQL Server, you can quickly update the account names to reflect the correct department name. If you want to preview what the new account names will be, you can execute this script against your GP company database:

select b.ACTNUMST Account, a.ACTDESCR Old_Name,
REPLACE(a.ACTDESCR, 'Sales', 'Marketing') New_Name
from GL00100 a
inner join GL00105 b
on a.ACTINDX = b.ACTINDX
where a.ACTNUMBR_1 = '350'

Below are the results using my example:

If you’re ready to make the change, execute the following script against the company database:

update GL00100
set ACTDESCR = REPLACE(ACTDESCR, 'Sales', 'Marketing')
where ACTNUMBR_1 = '350'

Your new account numbers now have updated names in GP:

To see more tips and tricks for GP Reports Viewer, SQL , SSRS and Crystal Reports, take a look at the GP Reports Viewer newsletters. There are also more SQL Server coding tips on this blog.

Some additional resources:

• Sales Order Processing (SOP) SQL views
• Sales Order Processing (SOP) commonly used tables
• Other GP Reporting links

CREATE VIEW view_Sales_Qty_by_Item_Site_Year
AS

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_Sales_Qty_by_Item_Site_Year
-- Created Feb 28, 2013 by Victoria Yudin, Flexible Solutions Inc
-- For updates see http://victoriayudin.com/gp-reports/
-- Returns total sales quantities fulfilled (invoices less 
--    returns) for each item by site by year
-- Only posted invoices and returns are included
-- Quantity is calculated by multiplying by QTYBSUOM column in 
--    case other UofM's are used on transactions
-- Voided transactions are excluded
-- Item Description is taken from Inventory Item Maintenance  
--    for all inventory items and from SOP line items  
--    for non-inventory items
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 

select
D.ITEMNMBR Item_Number, 
D.Item_Description, 
D.LOCNCODE Site_ID,
sum(case when year(D.DOCDATE) = 2006 
    then D.Qty else 0 end) [2006_Qty],
sum(case when year(D.DOCDATE) = 2007 
    then D.Qty else 0 end) [2007_Qty],
sum(case when year(D.DOCDATE) = 2008 
    then D.Qty else 0 end) [2008_Qty],
sum(case when year(D.DOCDATE) = 2009 
    then D.Qty else 0 end) [2009_Qty],
sum(case when year(D.DOCDATE) = 2010 
    then D.Qty else 0 end) [2010_Qty],
sum(case when year(D.DOCDATE) = 2011 
    then D.Qty else 0 end) [2011_Qty],
sum(case when year(D.DOCDATE) = 2012 
    then D.Qty else 0 end) [2012_Qty],
sum(case when year(D.DOCDATE) = 2013 
    then D.Qty else 0 end) [2013_Qty],
sum(D.Qty) Total_Qty

from 
(select SH.DOCDATE, SD.ITEMNMBR, SD.LOCNCODE,
 coalesce(I.ITEMDESC, SD.ITEMDESC) Item_Description,
 case SD.SOPTYPE
 when 3 then SD.QTYFULFI*QTYBSUOM
 when 4 then SD.QUANTITY*QTYBSUOM*-1
 end Qty
 from SOP30200 SH
 inner join SOP30300 SD
   on SD.SOPNUMBE = SH.SOPNUMBE
   and SD.SOPTYPE = SH.SOPTYPE
 left outer join IV00101 I
   on I.ITEMNMBR = SD.ITEMNMBR
 where SH.VOIDSTTS = 0
   and SH.SOPTYPE IN (3,4)
   and SD.ITEMNMBR not like 'XXXXXXXXXXXXXXX%') D

group by D.ITEMNMBR, D.Item_Description, D.LOCNCODE

go
grant select on view_Sales_Qty_by_Item_Site_Year to DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

Related code and table information:

• General Ledger tables
• Variable Allocation Accounts
• GP Reports (there is a section for General Ledger reports under Dynamics GP SQL Scripts)

create view view_Fixed_Allocation_Accounts
as

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_Fixed_Allocation_Accounts
-- Created on Jan. 23, 2013 by Victoria Yudin - Flexible Solutions, Inc.
-- For updates please see http://victoriayudin.com/gp-reports/
-- Shows only active fixed allocation accounts
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

select
an.ACTNUMST Fixed_Allocation_Account,
a.ACTDESCR Fixed_Allocation_Account_Name,
da.ACTNUMST Distribution_Account,
dn.ACTDESCR Distribution_Account_Name,
f.PRCNTAGE Distribution_Percentage

from GL00100 a --account master

inner join GL00105 an --account number
on a.ACTINDX = an.ACTINDX

inner join GL00103 f --fixed allocation account setup
on a.ACTINDX = f.ACTINDX

inner join GL00105 da --distribution account
on f.DSTINDX = da.ACTINDX

inner join GL00100 dn --distribution account name
on f.DSTINDX = dn.ACTINDX

where a.ACCTTYPE = 3 and a.ACTIVE = 1
and a.ACTINDX not in (select ACTINDX from GL00104)

go
grant select on view_Fixed_Allocation_Accounts to DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

I just got that email I was waiting for, letting me know that I have received the 2013 Microsoft® MVP Award for Dynamics GP! This makes my 9th year as a Dynamics GP MVP and I am honored. Thank you to everyone reading this - I could not have done it without you, so this award is for you, as well.

For those curious, the Microsoft MVP program has been in place since the early 1990′s and currently has about 4,000 MVPs worldwide. You can search for MVPs or take a look at the list of current Dynamics GP MVPs.

Happy, healthy and prosperous 2013 to all of you!

By Mickie Stamm:

In the last GP Reports Viewer newsletter I wrote about using rectangles as containers in SQL Server Reporting Services reports. In this post I would like to demonstrate another example of using rectangles in conjunction with something that I think adds a lot of punch to reports – sparklines. Sparklines were introduced with SSRS 2008 R2, however you can simulate them in 2008 and 2005 by using a regular line chart and removing a lot of the surrounding elements like the chart title, legend, category and value axes, etc.

Sparklines are great little charts that help you to see the trend of your data over a period of time. They are useful in a table, matrix or list because you can view them together and compare them to more easily see which rows in your data are performing better than the others.

The steps below will walk you through building an SSRS report with a sparkline in the 2008 R2 Business Intelligence Development Studio (BIDS).

Our report is going to use the following query to get data from a Dynamics GP company database:

SELECT DATENAME(m, SH.DOCDATE) Month_Name, MONTH(SH.DOCDATE) as Month_Number,
       SD.ITEMNMBR Item_Number, COALESCE(I.ITEMDESC, SD.ITEMDESC) Item_Description,
       SUM(CASE SD.SOPTYPE
          WHEN 3 THEN SD.XTNDPRCE
          WHEN 4 THEN SD.XTNDPRCE*-1
          END) Sales
FROM SOP30200 SH
INNER JOIN
     SOP30300 SD
     ON SD.SOPNUMBE = SH.SOPNUMBE
     AND SD.SOPTYPE = SH.SOPTYPE
LEFT OUTER JOIN
     IV00101 I
     ON I.ITEMNMBR = SD.ITEMNMBR
WHERE SH.VOIDSTTS = 0
     AND SH.SOPTYPE IN (3,4)
     AND SD.XTNDPRCE <> 0
     AND SD.ITEMNMBR not like 'XXXXXXXXXXXXXXX%'
     AND YEAR(SH.DOCDATE) = @year
GROUP BY DATENAME(m, SH.DOCDATE), MONTH(SH.DOCDATE), SD.ITEMNMBR,
         COALESCE(I.ITEMDESC, SD.ITEMDESC)

To create the report:

1. Start by right-clicking on your report project and choose Add New Report to start the Report Wizard: 
2. Select an existing shared data source or enter in new datasource information and click Next.
3. Enter in the query string above on the following screen and click Next.
4. For the report type on the next screen choose the radio button for Matrix.
5. Design the Matrix as follows: 
6. Choose a style for the matrix on the following screen (I chose the Corporate theme) and click Finish.
7. Give your report a Name (I chose Sales by Item) and click Finish.
8. Run the report and your results should look like this: 
9. Make the columns for Item Number and Item Description wider.
10. Click on the textbox for Sum(Sales) and then right-click and choose Add Total > Column. 
11. Click on the Month_Name column header to select the column and then right-click and choose Insert Column > Outside Group – Right. 
12. Click on the Month_Name column header to select the column and then right-click and choose Delete Columns.  Choose Yes when prompted if you want to delete columns and associated groups.
13. Click on the textbox in the header row of the new column you added in Step 11 and then right-click and choose Expression…and enter the following expression:  

     =Parameters!year.Value & " Sales" 

14. Click on the textbox in the details row of the new column you added in Step 11 and then right-click and choose Insert > Rectangle. 
15. Next, right-click on the rectangle you added in the last step and choose Insert > Sparkline.
16. Choose a chart type (I chose the default column chart type) and click OK.
17. Set your chart Values to be Sales and Category Groups to be Month_Number. 
18. Make the chart wider and shorter and adjust the row height to be shorter as well so that it looks something like this: 
19. Now, when you run the report you will notice that the sparkline chart doesn’t look quite right if the items don’t have sales in certain months. To resolve this issue, go back to design mode, right-click on your sparkline and choose Horizontal Axis Properties… and mark the checkbox for Align axes in: and select the name of your matrix (in my case it is the default name matrix1) from the dropdownlist and click OK.
20. This will make the bars line up in the right places horizontally, however the next issue we run into is that the vertical maximum is the same height in each row no matter what the sales amount is. To resolve this issue, go back to design mode, right-click on your sparkline and this time choose Vertical Axis Properties… and mark the checkbox for Align axes in: and select the name of your matrix (in my case it is the default name matrix1) from the dropdownlist. Set the Minimum value to 0 (zero) and click OK.
21. To add tooltips for the individual bars of the sparkline, in design mode click on one of the bar columns of the Sales Chart Series and enter in the following expression the under ToolTip property: 

     =Fields!Month_Name.Value & " : " & Format(Fields!Sales.Value,"C2") 

Those are the basics to setting up a sparkline embedded in a rectangle in your SSRS report. You can explore the other chart properties and tweak things like colors, markers, etc. and even provide actions such as jumping to a detail report for a given line item. The report created with the steps above can be downloaded here.

For more GP Reports Viewer news and Dynamics GP reporting tips, sign up for the GP Reports Viewer newsletter. For additional SQL code, take a look at the GP Reports page on this blog.

The issue is that when you go to void a partially applied Payables transaction you receive the following message:

Your only option here is to click OK. So is it possible to void a partially applied Payables transaction? The short answer is no. The long answer is that there is a workaround by following the steps below:

1. Fully apply the transaction. (This might involve creating a ‘dummy’ invoice if there is nothing else to apply it to.)
2. Void the now historical transaction. (And void the ‘dummy’ invoice if you had to create one.)

Below are details on these steps:

Step 1: Fully apply the transaction

In my example, I have a credit memo for $200 and $142.32 of it is still unapplied:

Let’s look at the more complicated option, where I do not have anything else open for this vendor and I need to void this credit memo. To be able to fully apply this credit memo, I first need to create a ‘dummy’ invoice for the unapplied amount on the credit memo:

• Go to  Transactions | Purchasing | Transaction Entry
• Select either Invoice or Misc Charge for the Document Type
• Enter the Vendor and Doc. Date  (the date doesn’t much matter, as we will be voiding this a few steps down)
• Enter the unapplied amount of the credit memo under Purchases (in my example, $142.32)
• The GL distributions do not matter here either, as again, we will be voiding this, however you do want to make sure they are all there so there is no issue with posting this transaction

• Post this transaction

Now you can fully apply the credit memo:

• Go to Transactions | Purchasing | Apply Payables Documents
• Select the Vendor
• Click on the looking glass icon next to the Document No. at the top right and select the credit memo
• Apply it to the invoice you just posted: 
• Click OK to close the Apply window and now we’re ready for step 2:

Step 2: Void

Since the credit memo is now fully applied, it is in history. To void it:

• Go to Transactions | Purchasing | Void Historical Transactions
• Select the transaction, change the date(s) if needed, and Void:

Now the ‘dummy’ invoice is unapplied (and is thus Open), to void it:

• Go to Transactions | Purchasing | Void Open Transactions
• Select the Vendor and the ‘dummy’ invoice and Void

That should do it on the Payables side. Depending on your settings, you might have some General Ledger postings to complete from transactions this generated.

Now you have a reference for the steps to follow next time you have to void a partially applied Payables transaction in Dynamics GP.

Please note that eOne has always sold a more advanced version of Extender, called Extender Enterprise. Everything in this post is talking about the Extender module that is currently sold by Microsoft as a Dynamics GP module. This is sometimes referred to as ‘Extender Standard’, however, I am simply calling it ‘Extender’ since that is how most partners and customers refer to it.

I think this announcement is a pretty big deal because there are many Microsoft Dynamics GP users out there with Extender and because Extender is such a terrific and useful module. For Dynamics GP Partners who want to see all the details and Q&A, you can read the entire Microsoft announcement on PartnerSource. I have not been able to find a similar announcement on CustomerSource yet. For those who do not have PartnerSource access, or just want a few highlights, they are below:

• Effective February 1, 2013, the Extender module for Microsoft Dynamics GP will no longer be sold by Microsoft and will be removed from the Microsoft Dynamics GP price lists.
• eOne Solutions will continue to support existing Extender customers.
• New or existing customers who wish to purchase Extender can purchase it from eOne through their GP Partner. (Customers not working with a partner can work with eOne directly.)
• Starting February 1, 2013, Microsoft Dynamics GP customers who previously obtained a license for Extender from Microsoft will receive a reduction in their Protected List Price and will not be charged annual maintenance fees for Extender on their next Dynamics GP renewal. The license keys for Extender will remain on existing customers’ accounts, allowing the continued use of Extender.
• Any customer that owns Extender as of December 1, 2012 and is current on a maintenance plan will get license rights for Extender for Dynamics GP 2013. However, registration keys and the installation media will need to be obtained from eOne. After Dynamics GP 2013 customers will need to be on an eOne maintenance plan to receive new Extender versions and updates.

I spoke to Abbey Cooper from eOne Solutions and she was wonderful about explaining all the options for partners and customers and answering all the questions I had. If you are a partner supporting customers with Extender, email eOne Solutions to get signed up with them. If you are a customer using Extender or considering it for the future, talk to your GP Partner about any concerns or questions you might have.

The situation where I last needed this was when I was creating a Crystal Report and wanted to hide a date field if it returns ’1/1/1900′, the equivalent of a NULL in Dynamics GP data. To do this, follow the steps below:

1. Right click on the date field on the report and choose Format Field
2. On the Common tab click on the formula button next to Suppress: 
3. Add the following formula, replacing DateField with yours: {DateField} = #1/1/1900#
4. Click Save and Close, then OK.

If you would like to receive monthly tips like this, please subscribe to the GP Reports Viewer newsletter. And if you are looking to use Crystal Reports with Microsoft Dynamics GP, please check out GP Reports Viewer – it can make using Crystal Reports (or SSRS) in Dynamics GP a breeze.

Related code and table information:

• Sales Order Processing (SOP) tables
• Inventory tables
• Sales Order Processing (SOP) SQL views
• Inventory SQL views
• GP Reports (there is a section for General Ledger reports under Dynamics GP SQL Scripts)

create view view_Rolling_12_Mo_Sales_by_Item
as

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_Rolling_12_Mo_Sales_by_Item
-- Created Aug 27, 2012 by Victoria Yudin, Flexible Solutions
-- For updates see http://victoriayudin.com/gp-reports/
-- Returns total sales (invoices - returns) for each item for 
--   the last 12 months. Current month is not included, 
--   even if it is the last day of the month.
-- Only posted invoices and returns are included.
-- Voided transactions are excluded.
-- Item Description is taken from Inventory Item Maintenance 
--   for all inventory items, and from SOP line items
--   for non-inventory items.
-- Document Date is used (not GL Posting Date).
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 

SELECT
D.ITEMNMBR Item_Number,
D.Item_Description,
D.Generic_Description,
D.Item_Class,
D.User_Category_1,
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -12, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -12, GETDATE()))
  then D.SALES else 0 end) as [Sales_12_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -11, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -11, GETDATE()))
  then D.SALES else 0 end) as [Sales_11_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -10, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -10, GETDATE()))
  then D.SALES else 0 end) as [Sales_10_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -9, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -9, GETDATE()))
  then D.SALES else 0 end) as [Sales_9_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -8, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -8, GETDATE()))
  then D.SALES else 0 end) as [Sales_8_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -7, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -7, GETDATE()))
  then D.SALES else 0 end) as [Sales_7_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -6, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -6, GETDATE()))
  then D.SALES else 0 end) as [Sales_6_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -5, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -5, GETDATE()))
  then D.SALES else 0 end) as [Sales_5_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -4, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -4, GETDATE()))
  then D.SALES else 0 end) as [Sales_4_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -3, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -3, GETDATE()))
  then D.SALES else 0 end) as [Sales_3_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -2, GETDATE()))
  and year(D.DOCDATE) = year(DATEADD(m, -2, GETDATE()))
  then D.SALES else 0 end) as [Sales_2_mo_ago],
sum(case when month(D.DOCDATE) = 
  month(DATEADD(m, -1, GETDATE()))
  and YEAR(D.DOCDATE) = year(DATEADD(m, -1, GETDATE()))
  then D.SALES else 0 end) as [Sales_1_mo_ago]

FROM
(SELECT SH.DOCDATE, SD.ITEMNMBR,
 coalesce(I.ITEMDESC, SD.ITEMDESC) Item_Description,
 coalesce(I.ITMGEDSC, '') Generic_Description,
 coalesce(I.ITMCLSCD,'') Item_Class,
 coalesce(I.USCATVLS_1,'') User_Category_1,
 case SD.SOPTYPE
     WHEN 3 THEN SD.XTNDPRCE
     WHEN 4 THEN SD.XTNDPRCE*-1
     END SALES
 FROM SOP30200 SH  -- SOP header
 INNER JOIN
     SOP30300 SD  -- SOP lines
     ON SD.SOPNUMBE = SH.SOPNUMBE
     AND SD.SOPTYPE = SH.SOPTYPE
 LEFT OUTER JOIN
     IV00101 I  -- item master
     ON I.ITEMNMBR = SD.ITEMNMBR
 WHERE SH.VOIDSTTS = 0   -- not voided
     AND SH.SOPTYPE IN (3,4) -- only invoices and returns
     AND SD.XTNDPRCE <> 0   -- excludes zero price
     AND SD.ITEMNMBR not like 'XXXXXXXXXXXXXXX%'  
     ) D

GROUP BY D.ITEMNMBR, D.Item_Description, 
  D.Generic_Description, D.Item_Class, D.User_Category_1

-- add permissions for DYNGRP
GO
GRANT SELECT ON view_Rolling_12_Mo_Sales_by_Item TO DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

Related code and table information:

• General Ledger tables
• Fixed Allocation Accounts
• GP Reports (there is a section for General Ledger reports under Dynamics GP SQL Scripts)

create view view_Variable_Allocation_Accounts
as

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_Variable_Allocation_Accounts
-- Created on Aug. 23, 2012 by Victoria Yudin - Flexible Solutions, Inc.
-- For updates please see http://victoriayudin.com/gp-reports/
-- Shows only active variable allocation accounts
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

select
an.ACTNUMST Variable_Allocation_Account,
a.ACTDESCR Variable_Allocation_Account_Name,
d.ACTNUMST Distribution_Account,
dn.ACTDESCR Distribution_Account_Name,
b.ACTNUMST Breakdown_Account,
bn.ACTDESCR Breakdown_Account_Name

from GL00100 a --account master

inner join GL00105 an --account number
on a.ACTINDX = an.ACTINDX

inner join GL00104 v --variable allocation account setup
on a.ACTINDX = v.ACTINDX

inner join GL00105 d --distribution acct number
on v.DSTINDX = d.ACTINDX

inner join GL00100 dn --distribution account name
on v.DSTINDX = dn.ACTINDX

inner join GL00105 b --breakdown account number
on v.BDNINDX = b.ACTINDX

inner join GL00100 bn --breakdown account name
on v.BDNINDX = bn.ACTINDX

where a.ACCTTYPE = 3 and a.ACTIVE = 1

go
grant select on view_Variable_Allocation_Accounts to DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

The view below returns all the commissions from the SOP (Sales Order Processing) module and also includes commissions from RM (Receivables Management) transactions that did not come from SOP. Both posted and unposted transactions are included, but I have added a column called Posted to show the posting status so you can easily exclude the unposted transactions if you need to. More notes are found in the comments in the view. This code was tested on a few different sets of data, however, it may be that this will not work for your specific data – before using this to base commissions on, please test the results.

Related code and table information:

• Receivables Management tables
• Sales Order Processing tables
• Receivables SQL views
• SOP SQL views

CREATE VIEW view_Commissions_Details
AS

--***********************************************************************************
-- view_Commissions_Details
-- Created July 19, 2012 by Victoria Yudin - Flexible Solutions, Inc.
-- For updates see http://victoriayudin.com/gp-reports/
-- Returns all commissions details for SOP transactions (invoices and returns only)
--     and also adds in non-SOP transactions commissions from RM tables
-- Only shows functional amounts
-- Excludes voided transactions
--***********************************************************************************

select CUSTNMBR Customer_ID, DOCDATE Document_Date, GLPOSTDT GL_Posting_Date, Data_Source,
case RMDTYPAL 
 when 1 then 'Invoice'
 when 3 then 'Debit Memo'
 when 5 then 'Service / Repair'
 when 7 then 'Credit Memo'
 when 8 then 'Return'
 end Document_Type,
DOCNUMBR Document_Number, SEQNUMBR Sequence_Number,
TRXSORCE Trx_Source, SLPRSNID Salesperson, SALSTERR Territory, 
case when RMDTYPAL < 7 then Sales_Amount else Sales_Amount*-1 end Sales_Amount, 
case when RMDTYPAL < 7 then Non_Comm_Amount else Non_Comm_Amount*-1 end Non_Comm_Amount,
cast(PRCTOSAL as numeric)/100 Percent_of_Sale, 
case when RMDTYPAL < 7 then Commission_Amount else Commission_Amount*-1 end Commission_Amount,
cast(COMPRCNT as numeric)/100 Commission_Percent, 
case POSTED when 0 then 'No' else 'Yes' end Posted
 
from

(select r.CUSTNMBR, r.DOCDATE, r.GLPOSTDT, c.*
from
(select 
 Data_Source = 'RM History', RMDTYPAL, DOCNUMBR, SEQNUMBR, TRXSORCE, SLPRSNID, 
 SALSTERR, SLSAMNT Sales_Amount, NCOMAMNT Non_Comm_Amount, PRCTOSAL, 
 COMDLRAM Commission_Amount, COMPRCNT, POSTED
 from RM30501 -- RM Commission History
 where left(TRXSORCE,5) <> 'SLSTE'
  union all
 select 
 Data_Source = 'RM Work', RMDTYPAL, DOCNUMBR, SEQNUMBR, TRXSORCE, SLPRSNID, 
 SALSTERR, SLSAMNT Sales_Amount, NCOMAMNT Non_Comm_Amount, PRCTOSAL, 
 COMDLRAM Commission_Amount, COMPRCNT, POSTED
 from rm10501 -- RM Commission Work 
 where left(TRXSORCE,5) <> 'SLSTE') c -- RM commissions

inner join 
(select RMDTYPAL, DOCNUMBR, DOCDATE, GLPOSTDT, CUSTNMBR 
 from RM10301 --RM Work
  union 
 select RMDTYPAL, DOCNUMBR, DOCDATE, GLPOSTDT, CUSTNMBR 
 from RM20101 --RM Open
 where VOIDSTTS = 0
  union 
 select RMDTYPAL, DOCNUMBR, DOCDATE, GLPOSTDT, CUSTNMBR 
 from RM30101 --RM History
 where VOIDSTTS = 0) r --all RM transactions
 on r.RMDTYPAL = c.RMDTYPAL and r.DOCNUMBR = c.DOCNUMBR

union all
select
s.CUSTNMBR, s.DOCDATE, s.GLPOSTDT, Data_Source = 'SOP',  
case c.SOPTYPE when 3 then 1 else 8 end RMDTYPAL,
c.SOPNUMBE DOCNUMBR, c.SEQNUMBR, c.TRXSORCE, c.SLPRSNID, 
c.SALSTERR, c.ACTSLAMT Sales_Amount, c.NCOMAMNT Non_Comm_Amount, 
c.PRCTOSAL, c.COMMAMNT Commission_Amount, c.COMPRCNT, 
case c.TRXSORCE when '' then 0 else 1 end POSTED
from SOP10101 c --SOP commissions (work and history)

inner join 
(select SOPTYPE, SOPNUMBE, DOCDATE, GLPOSTDT, CUSTNMBR
 from SOP10100 
 where SOPTYPE in (3,4) and VOIDSTTS = 0
  union 
 select SOPTYPE, SOPNUMBE, DOCDATE, GLPOSTDT, CUSTNMBR
 from SOP30200
 where SOPTYPE in (3,4) and VOIDSTTS = 0) s --SOP transactions
 on s.SOPTYPE = c.SOPTYPE and s.SOPNUMBE = c.SOPNUMBE
where c.SOPTYPE in (3,4)) a --all data

GO
GRANT SELECT ON view_Commissions_Details to DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

For more Dynamics GP SOP scripts please visit my SOP SQL Views page. Or take a look at my GP Reports page for additional reporting links. SOP table information can be found on this page.

CREATE VIEW view_SOP_Line_Items_Serial
AS

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_SOP_Line_Items_Serial
-- Created on June 4, 2012 by Victoria Yudin - Flexible Solutions, Inc.
-- For updates please see http://victoriayudin.com/gp-reports/
-- All line items for posted and unposted SOP transactions with serial and/or lot numbers
-- Returns Functional amounts only
-- Component Items are not taken into consideration
-- Fields that can have different values on the document header and
-- line item are both returned prefaced by 'Header' or 'Line'
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

SELECT S.*,
coalesce(C.CMMTTEXT,'') Line_Item_Comment,
coalesce(SN.Serial_Lot_Numbers,'') Serial_Lot_Numbers,
coalesce(HC.CMMTTEXT,'') Header_Comment

FROM  --sop lines
(SELECT Doc_Status = 'Open',
H.SOPNUMBE SOP_Number, H.SOPTYPE SOP_Type,
H.DOCDATE Document_Date, H.GLPOSTDT GL_Posting_Date,
H.ORDRDATE Order_Date, H.DUEDATE Due_Date,
H.MSTRNUMB Master_Number,
CASE H.PSTGSTUS
  WHEN 0 THEN 'Unposted'
  WHEN 2 THEN 'Posted'
  ELSE 'Error'
  END Posting_Status,
H.CUSTNMBR Customer_ID, H.CUSTNAME Customer_Name,
H.CSTPONBR Customer_PO, H.BACHNUMB Batch_Number,
H.LOCNCODE Header_Site_ID, L.LOCNCODE Line_Site_ID,
CASE H.VOIDSTTS
  WHEN 0 THEN 'Not Voided'
  WHEN 1 THEN 'Voided'
  ELSE ''
  END Void_Status,
H.SLPRSNID Header_Salesperson, L.SLPRSNID Line_Salesperson,
H.SALSTERR Header_Territory, L.SALSTERR Line_Territory,
H.PYMTRMID Payment_Terms_ID,
H.SHIPMTHD Header_Shipping_Method, L.SHIPMTHD Line_Shipping_Method,
H.PRBTADCD Bill_To_Address_ID,
H.PRSTADCD Header_Ship_To_Address_ID, H.ShipToName Header_Ship_To_Name,
H.ADDRESS1 Header_Address_1, H.ADDRESS2 Header_Address_2,
H.ADDRESS3 Header_Address_3, H.CITY Header_City,
H.[STATE] Header_State, H.ZIPCODE Header_Zip_Code,
H.COUNTRY Header_Country,
L.PRSTADCD Line_Ship_To_Address_ID, L.ShipToName Line_Ship_To_Name,
L.ADDRESS1 Line_Address_1, L.ADDRESS2 Line_Address_2,
L.ADDRESS3 Line_Address_3, L.CITY Line_City,
L.[STATE] Line_State, L.ZIPCODE Line_Zip_Code,
L.COUNTRY Line_Country,
H.DOCAMNT Total_Document_Amount, H.MRKDNAMT Total_Markdown_Amount,
H.SUBTOTAL Document_Subtotal,
H.FRTAMNT Freight_Amount, H.MISCAMNT Misc_Amount,
H.TAXAMNT Tax_Amount, H.CURNCYID Currency_ID,
H.ReqShipDate Header_ReqShipDate, L.ReqShipDate Line_ReqShipDate,
H.USER2ENT User_to_Enter,
H.COMMNTID Header_Comment_ID, L.COMMNTID Line_Comment_ID,
L.LNITMSEQ Line_Item_Sequence, L.CMPNTSEQ Component_Sequence,
CASE L.NONINVEN
  WHEN 0 THEN 'Inventory'
  WHEN 1 THEN 'Non-Inventory'
  ELSE ''
  END Item_Type,
L.ITEMNMBR Item_Number, L.ITEMDESC Item_Description,
L.QUANTITY Quantity, L.UOFM U_of_M, L.QTYBSUOM Qty_in_Base_U_of_M,
L.QTYREMAI Qty_Remaining, L.UNITPRCE Unit_Price,
L.XTNDPRCE Extended_Price,
CASE L.MRKDNTYP
  WHEN 0 THEN 'Percentage'
  WHEN 1 THEN 'Amount'
  ELSE ''
  END Markdown_Type,
L.MRKDNAMT Markdown_Amount, L.MRKDNPCT/100 Markdown_Percentage,
L.TRDISAMT Trade_Discount_Amount,
L.UNITCOST Unit_Cost, L.EXTDCOST Extended_Cost

FROM SOP10100 H
INNER JOIN SOP10200 L
	ON H.SOPTYPE = L.SOPTYPE AND H.SOPNUMBE = L.SOPNUMBE

UNION

SELECT Doc_Status = 'History',
H.SOPNUMBE SOP_Number, H.SOPTYPE SOP_Type,
H.DOCDATE Document_Date, H.GLPOSTDT GL_Posting_Date,
H.ORDRDATE Order_Date, H.DUEDATE Due_Date,
H.MSTRNUMB Master_Number,
CASE H.PSTGSTUS
  WHEN 0 THEN 'Unposted'
  WHEN 2 THEN 'Posted'
  ELSE 'Error'
  END Posting_Status,
H.CUSTNMBR Customer_ID, H.CUSTNAME Customer_Name,
H.CSTPONBR Customer_PO, H.BACHNUMB Batch_Number,
H.LOCNCODE Header_Site_ID, L.LOCNCODE Line_Site_ID,
CASE H.VOIDSTTS
  WHEN 0 THEN 'Not Voided'
  WHEN 1 THEN 'Voided'
  ELSE ''
  END Void_Status,
H.SLPRSNID Header_Salesperson, L.SLPRSNID Line_Salesperson,
H.SALSTERR Header_Territory, L.SALSTERR Line_Territory,
H.PYMTRMID Payment_Terms_ID,
H.SHIPMTHD Header_Shipping_Method, L.SHIPMTHD Line_Shipping_Method,
H.PRBTADCD Bill_To_Address_ID,
H.PRSTADCD Header_Ship_To_Address_ID, H.ShipToName Header_Ship_To_Name,
H.ADDRESS1 Header_Address_1, H.ADDRESS2 Header_Address_2,
H.ADDRESS3 Header_Address_3, H.CITY Header_City,
H.[STATE] Header_State, H.ZIPCODE Header_Zip_Code,
H.COUNTRY Header_Country,
L.PRSTADCD Line_Ship_To_Address_ID, L.ShipToName Line_Ship_To_Name,
L.ADDRESS1 Line_Address_1, L.ADDRESS2 Line_Address_2,
L.ADDRESS3 Line_Address_3, L.CITY Line_City,
L.[STATE] Line_State, L.ZIPCODE Line_Zip_Code,
L.COUNTRY Line_Country,
H.DOCAMNT Total_Document_Amount, H.MRKDNAMT Total_Markdown_Amount,
H.SUBTOTAL Document_Subtotal,
H.FRTAMNT Freight_Amount, H.MISCAMNT Misc_Amount,
H.TAXAMNT Tax_Amount, H.CURNCYID Currency_ID,
H.ReqShipDate Header_ReqShipDate, L.ReqShipDate Line_ReqShipDate,
H.USER2ENT User_to_Enter,
H.COMMNTID Header_Comment_ID, L.COMMNTID Line_Comment_ID,
L.LNITMSEQ Line_Item_Sequence, L.CMPNTSEQ Component_Sequence,
CASE L.NONINVEN
  WHEN 0 THEN 'Inventory'
  WHEN 1 THEN 'Non-Inventory'
  ELSE ''
  END Item_Type,
L.ITEMNMBR Item_Number, L.ITEMDESC Item_Description,
L.QUANTITY Quantity, L.UOFM U_of_M, L.QTYBSUOM Qty_in_Base_U_of_M,
L.QTYREMAI Qty_Remaining, L.UNITPRCE Unit_Price,
L.XTNDPRCE Extended_Price,
CASE L.MRKDNTYP
  WHEN 0 THEN 'Percentage'
  WHEN 1 THEN 'Amount'
  ELSE ''
  END Markdown_Type,
L.MRKDNAMT Markdown_Amount, L.MRKDNPCT/100 Markdown_Percentage,
L.TRDISAMT Trade_Discount_Amount,
L.UNITCOST Unit_Cost, L.EXTDCOST Extended_Cost

FROM SOP30200 H
INNER JOIN SOP30300 L
	ON H.SOPTYPE = L.SOPTYPE AND H.SOPNUMBE = L.SOPNUMBE) S --sop lines

LEFT OUTER JOIN
(SELECT p.SOPNUMBE, p.SOPTYPE, p.LNITMSEQ,
LEFT(p.serial_numbers, len(p.serial_numbers)-1) Serial_Lot_Numbers
FROM
 (SELECT p1.SOPNUMBE, p1.SOPTYPE, p1.ITEMNMBR, p1.LNITMSEQ,
  (SELECT coalesce(rtrim(SERLTNUM) + ', ','')
   FROM SOP10201 p2
   WHERE p1.SOPNUMBE = p2.SOPNUMBE and p1.SOPTYPE = p2.SOPTYPE
      and p1.ITEMNMBR = p2.ITEMNMBR and p1.LNITMSEQ = p2.LNITMSEQ
   ORDER BY SOPNUMBE
   FOR XML PATH('')) serial_numbers
  FROM SOP10201 p1
 GROUP BY SOPNUMBE, SOPTYPE, ITEMNMBR, LNITMSEQ) p) SN --serial/lot numbers
ON SN.SOPNUMBE = S.SOP_Number AND SN.SOPTYPE = S.SOP_Type AND SN.LNITMSEQ = S.Line_Item_Sequence

LEFT OUTER JOIN SOP10202 C --line item comments
ON C.SOPNUMBE = S.SOP_Number AND C.SOPTYPE = S.SOP_Type AND C.LNITMSEQ = S.Line_Item_Sequence

LEFT OUTER JOIN SOP10106 HC --header comments
ON HC.SOPNUMBE = S.SOP_Number AND HC.SOPTYPE = S.SOP_Type

--add permissions
GO
GRANT SELECT ON view_SOP_Line_Items_Serial TO DYNGRP

Disclaimer: I tested this on limited data, if you find an issue or have a suggestion for improvement, please let me know and I will post the update here for everyone.

One way GP Reports Viewer aids in this task is by allowing for three different options for parameter lookups: Dynamics GP Lookups, Custom Static Lookups and Custom Dynamic Lookups. I will go over these three options below in more detail.

Dynamics GP Lookups

Out of the box, GP Reports Viewer includes default lookups for a number of common parameters including Customer ID, Vendor ID and Item Number:

Choosing one of these will point to the default Dynamics GP lookup window for each option, with all the standard GP functionality enabled. The idea here is that when users are printing reports, they have a familiar look and feel for selecting their report parameters. For example, if you have a report with Customer ID as the parameter, you can choose the Customer ID Lookup when setting up your report in GP Reports Viewer. The users, when printing the report, simply click on the looking glass icon:

And are then presented with a window they already know for selecting a customer:

One new addition GP Reports Viewer created for this is the Calendar Lookup, choosing this will result in the following pop up when users click the looking glass icon:

Custom Static Lookups

Sometimes, a parameter is a Yes/No choice, or something else requiring a short list of static options. For situations like this, you can create a Custom Static Lookup in GP Reports Viewer. Steps to do this:

1. Navigate to GP | Tools | GP Reports Viewer | Lookups.
2. The Lookup ID will automatically populate with the next available number.
3. Type in a Lookup Name. This is what you will see when assigning lookups to parameters on reports and what the users will see as the name of the lookup window.
4. Choose a Lookup Series – this is simply for categorizing lookups, all lookups will be available on all reports.
5. Select Static for Lookup Type.
6. Enter column Display Headings and Types for your lookup – only the first one is required, you can leave the others blank.
7. Enter Values for your columns, below is a lookup with only one column and a Yes/No option: 
8. If you click Test Lookup you will be prompted to Save and then shown the lookup you have just created:

Custom Dynamic Lookups

Now for the really cool option – with GP Reports Viewer you can create your own custom lookups that can be based on a SQL table, view or stored procedure. You can even point to data in a different database, it does not have to be the one that users are logged into.

This option is often useful for setting up parameter choices where the data may change. Since this option is so robust, I would like to show two different examples of this. One is going to point directly to data in a table, another one will use a SQL view that is created specifically for this lookup.

Example – using data directly from a table

This example will create a parameter lookup with a list of departments in GP. Department in this case is the third segment of the chart of accounts and it is assumed that the department names are populated in the GL already.

1. Navigate to GP | Tools | GP Reports Viewer | Lookups.
2. The Lookup ID will automatically populate with the next available number.
3. Type in a Lookup Name. This is what you will see when assigning lookups to parameters on reports and what the users will see as the name of the lookup window.
4. Choose a Lookup Series – this is simply for categorizing lookups, all lookups will be available on all reports.
5. Select Dynamic for Lookup Type. 
6. Under Database select Current Company Database.
7. Query Type will default to Select statement. (If you’re curious, the other option there is Stored procedure.)
8. For Table type in GL40200. (This is the Segment Description Master table.) 
9. You must have at least one column defined in your lookup and you can have up to three columns.  In this case, it makes sense to have two columns: department number and name. Below is what this would look like. Note that I deleted the Display Heading for Column 3, so that it simply shows up blank: 
10. We also need to restrict this to only look at the third segment, so add SGMTNUMB = 3 to the SQL Where Clause field: 
11. Click Test Lookup, choose Yes to save and you can now preview your lookup: 

Lookups that have more than one column will have a drop down option enabled to allow users to search by any of the available columns: 

Example – using a SQL view

Another common example where you might want to have a custom lookup is a list of all SOP invoices. There is a Dynamics GP lookup for SOP Numbers that is available in GP Reports Viewer, but if your report only has invoices, users may find it easier to have a shorter list to look through. I don’t think it is necessary to go through all the steps in detail, as they will be almost identical to the steps above, so I will simply show you what the setup looks like: 

The results of this lookup are as follows:

Below is the code for the SQL view I used in this lookup:

CREATE VIEW view_Sales_Invoices
AS
SELECT SOPNUMBE, CUSTNAME, DOCDATE
FROM SOP10100
WHERE VOIDSTTS = 0 AND SOPTYPE = 3
UNION
SELECT SOPNUMBE, CUSTNAME, DOCDATE
FROM SOP30200
WHERE VOIDSTTS = 0 AND SOPTYPE = 3
GO
GRANT SELECT ON view_Sales_Invoices TO DYNGRP

Now that you can create any lookups you need for your reports, you can make generating reports more user friendly by making sure each parameter on your GP Reports Viewer reports has a lookup.

For more information about GP Reports Viewer, please take a look at the GP Reports Viewer demo video.

Disclaimer: GP Reports Viewer is an add-on product for Dynamics GP that is created and sold by my company, Flexible Solutions. I may be slightly biased, but I think it is the best thing since sliced bread.

A request that we have seen many times when creating SOP invoices for Dynamics GP is to concatenate serial numbers.  So if there is an item with serial numbers, instead of showing a list with one serial number per line under the item, which would look a little unwieldy with long list of serial numbers:

we want to show all the serial numbers on one line, separated by a comma. Below is the SQL code that will do this in SQL 2005 and 2008:

SELECT
p.SOPNUMBE SOP_Number, p.SOPTYPE SOP_Type, p.ITEMNMBR Item, 
p.LNITMSEQ Line_Item_Sequence,
LEFT(p.serial_numbers, len(p.serial_numbers)-1) Serial_Numbers
FROM
 (SELECT p1.SOPNUMBE, p1.SOPTYPE, p1.ITEMNMBR, p1.LNITMSEQ,
  (SELECT coalesce(rtrim(SERLTNUM) + ', ','')
   FROM SOP10201 p2
   WHERE p1.SOPNUMBE = p2.SOPNUMBE 
      and p1.SOPTYPE = p2.SOPTYPE
      and p1.ITEMNMBR = p2.ITEMNMBR 
      and p1.LNITMSEQ = p2.LNITMSEQ
   ORDER BY SOPNUMBE
   FOR XML PATH('')) serial_numbers
  FROM SOP10201 p1
 GROUP BY SOPNUMBE, SOPTYPE, ITEMNMBR, LNITMSEQ) p

Using this code, the line item and serial numbers shown above can look like this:

This code can also be changed slightly for other uses, for example, to concatenate a list of invoices paid by a check in payables. Here is the code to do that using my Payables Apply Detail view:

SELECT
p.Vendor_ID, p.Payment_Voucher_Number, 
p.Payment_Date, p.Payment_Type,
p.Payment_Document_Number, 
LEFT(p.apply_docs, len(p.apply_docs)-1) Applied_To_Docs
FROM
 (SELECT p1.Vendor_ID, p1.Payment_Voucher_Number, 
  p1.Payment_Date, p1.Payment_Type,
  p1.Payment_Document_Number,
  (SELECT coalesce(rtrim(Apply_To_Doc_Number) + ', ','')
   FROM view_Payables_Apply_detail p2
   WHERE p1.Vendor_ID = p2.Vendor_ID
     and p1.Payment_Voucher_Number = p2.Payment_Voucher_Number
   ORDER BY Payment_Voucher_Number
   FOR XML PATH('')) apply_docs
  FROM view_Payables_Apply_detail p1
  GROUP BY Vendor_ID, Payment_Voucher_Number, Payment_Date, 
    Payment_Type, Payment_Document_Number) p

For more tips like this, take a look at my SQL Server Coding Tips page. To receive new tips as soon as they are published, sign up for the GP Reports Viewer newsletter.

One of the reasons I originally started this blog was to create a place to keep and organize all these resources. Since there are a lot of new versions coming out (GP, SQL, MR) I have been updating the lists on this blog and wanted to post a little refresher for all my readers on how to find these resources.

I have tried to organize by product and then version where applicable. I have also tried to put cross-links and menus everywhere I can. One of the easiest ways to find resources on my blog is to click on the Resources link at the top of this blog:

From here, if you are looking for a particular product, you can quickly choose an option and go directly to the page with links for it:

If you’re looking for more generic Dynamics GP links, choose Dynamics GP Resources from the menu. There is also a page of links for SQL Server and another for Management Reporter & FRx.

I will keep adding new useful links as I find them and adding new build numbers as they come out, but if you have useful links that you’d like to add to these lists, please let me know. In the meantime, some new, updated and useful links:

• Dynamics GP support lifecycle
• Dynamics GP 2013 links
• SQL Server service packs and versions
• SQL Server support lifecycle
• SQL 2012 edition comparison
• SQL 2012 hardware and software requirements
• Management Reporter 2012 downloads
• Management Reporter 2012 installation, migration and configuration guides
• Management Reporter versions