money-bags

SQL view for Payables payment apply detail in GP


I have published SQL views that return all posted Payables payments in Dynamics GP and Payables apply information to help identify what payments (or credits) paid off an invoice, however another frequent request is for a list of payments and their apply information.  Below is a view that returns a list of all posted payments with details on how they were applied.  Any payment that was applied to more than one transaction will show up as multiple lines.

For other SQL views on GP data, please visit my GP Reports page.

create view view_Payables_Apply_Detail
as

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
-- view_Payables_Apply_Detail
-- Created Oct 22 2009 by Victoria Yudin, Flexible Solutions Inc
-- For updates see http://victoriayudin.com/gp-reports/
-- Does not take Multicurrency into account.
-- Will return multiple lines for payments that were applied to
--   more than one transaction.
-- Tables Used:
-- PM20000 – Open/Posted Transactions
-- PM30200 – Historical/Paid Transactions
-- PM00200 – Vendor Master
-- PM10200 – Apply To Work/Open
-- PM30300 – Apply To History
-- Updated Nov 19 2013 to add apply to doc due date
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

select
P.VENDORID Vendor_ID,
V.VENDNAME Vendor_Name,
V.VNDCHKNM Vendor_Check_Name,
case P.PYENTTYP
  when 0 then 'Check'
  when 1 then 'Cash'
  when 2 then 'Credit Card'
  when 3 then 'EFT'
  else 'Other'
  end Payment_Type,
case when P.PYENTTYP in (0,1,3) then P.CHEKBKID 
  else '' end Checkbook_ID,
case P.PYENTTYP when 2 then P.CARDNAME 
  else '' end Credit_Card_ID,
P.DOCDATE Payment_Date,
P.PSTGDATE Payment_GL_Date,
P.VCHRNMBR Payment_Voucher_Number,
P.DOCNUMBR Payment_Document_Number,
P.DOCAMNT Payment_Functional_Amount,
coalesce(PA.APTVCHNM,'') Apply_To_Voucher_Number,
case PA.APTODCTY
  when 1 then 'Invoice'
  when 2 then 'Finance Charge'
  when 3 then 'Misc Charge'
  else ''
  end Apply_To_Doc_Type,
coalesce(PA.APTODCNM,'') Apply_To_Doc_Number,
coalesce(PA.APTODCDT,'1/1/1900') Apply_To_Doc_Date,
coalesce(PA.ApplyToGLPostDate,'1/1/1900') Apply_To_GL_Date,
coalesce(AD.DUEDATE,'1/1/1900') Apply_To_Due_Date,
coalesce(PA.APPLDAMT,0) Applied_Amount

from
 (select VENDORID, DOCTYPE, DOCDATE, VCHRNMBR, DOCNUMBR,
 DOCAMNT, VOIDED, TRXSORCE, CHEKBKID, PSTGDATE,
 PYENTTYP, CARDNAME
 from PM30200
union
 select VENDORID, DOCTYPE, DOCDATE, VCHRNMBR, DOCNUMBR,
 DOCAMNT, VOIDED, TRXSORCE, CHEKBKID, PSTGDATE,
 PYENTTYP, CARDNAME
 from PM20000) P

inner join PM00200 V
 on P.VENDORID = V.VENDORID

left outer join
 (select VENDORID, VCHRNMBR, DOCTYPE, APTVCHNM, APTODCTY,
 APTODCNM, APTODCDT, ApplyToGLPostDate, APPLDAMT
 from PM10200
union
 select VENDORID, VCHRNMBR, DOCTYPE, APTVCHNM, APTODCTY,
 APTODCNM, APTODCDT, ApplyToGLPostDate, APPLDAMT
 from PM30300) PA
 on P.VCHRNMBR = PA.VCHRNMBR and P.VENDORID = PA.VENDORID
 and P.DOCTYPE = PA.DOCTYPE

left outer join -- added for due date
 (select DOCTYPE, VCHRNMBR, DUEDATE from PM30200
union
 select DOCTYPE, VCHRNMBR, DUEDATE from PM20000) AD 
 on PA.APTODCTY = AD.DOCTYPE and PA.APTVCHNM = AD.VCHRNMBR

where P.DOCTYPE = 6 and P.VOIDED = 0

-- add permissions for DYNGRP
go
grant select on view_Payables_Apply_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

60 Responses to “SQL view for Payables payment apply detail in GP”

  1. Hi Victoria,
    Nice script indeed, but can you add the multicurrency info by any chance?

    Thanks,
    Ben

    Like

  2. How does this script deal with partial payments? Our customer is comparing it to the check distribution report out of Dynamics, and they are not matching. Is there any way to do the same thing that report does, or will it only show the total invoice distribution amounts?

    Like

    • Phil,

      This was not meant to replace the Check Distribution report. While I have never compared the two, one difference I know of is that my code will show ALL payments, whereas the GP report will show only checks. Have you tried filtering on the Payment_Type column in my code to include only checks?

      That said, I am not sure of the exact logic used by the Check Distribution report, so I am not sure if that is the only difference, if you are finding others and need help tracking them down, please write back with more details.

      -Victoria

      Like

  3. Hi Victoria,

    I was just looking at this query and run into a question:
    I believe this query lists all payments with documents they applied to.
    If you are listing all payments in PM20000, don’t you have to use PM20100 for apply information instead of PM10200, which is for unposted transactions?

    Please tell me if I’m going crazy here.
    Thank you!

    Like

    • Hi Takeshi,

      PM20100 is a Temporary table, which I try to stay away from when coding reports. PM10200 has the apply information for WORK and OPEN transactions. PM30300 has the apply information for HISTORY transactions. So the combination of PM10200 and PM30300 should be sufficient for the data needed. Are you finding that this view is not giving you correct results?

      Out of curiosity, I tested replacing PM10200 with PM20100. In my data set, I get the same number of results with either. However PM20100 has a much larger amount of records than PM10200. So all other things being equal, using a table with less records should make the query faster. I have also seen data issues in the past where records get stuck in PM20100 and need to be cleared out manually for various reasons. Just another reason I would not use this table for reporting if I have other options.

      -Victoria

      Like

      • Thanks for the quick response, Victoria.
        I guess my assumption about PM10200 was wrong.
        I haven’t run it against our live data yet, but I will let you know if I find any incorrect results (hopefully not).

        Thanks again!

        Like

  4. Victoria

    I am using your AP Apply view in SLB and was wondering if you can or have created a GO To for it. I would like to be able to drill into the original AP Transastion entry winow or zoom.

    Thanks!

    Like

    • Hi Tami,

      I have not tried this myself, but I would think you’d need to add a column for Document Type (to either the payments, or the apply to docs, or both, depending on what you wanted to be able to zoom to) and then use the Payables Transaction Inquiry under Advanced Go Tos.

      -Victoria

      Like

    • Hello Victoria,

      Thank you for responding back so qucikly. My bad, I said I was using your AP_APPLY script and not getting the intended resuilts. I was actually using the Payables_Apply_Detail script whcih was not returning CM’s. I have swithched to your AP_APPLY script and it’s is giving me both CM’s as well as not returning voided transactions.

      Thanks for your time and efforts!!

      ~Tami

      Like

  5. Dear Victoria,

    I’m Noraini. This view is so helpful. Thanks. For your information, one of my customer need to show payments which apply to original document invoice amount and original credit memos amount. How do I get this information?

    Regards,
    Noraini

    Like

  6. Hey Victoria,

    We have been using the query for some time, and from output of the query we are getting:
    Payment_Document_Number = ‘REMIT000000000000002′ with Payment_Document_Type = 6 (where 6 is the checks type).
    However, all the other Payment_Document_Type = 6 cases are coming always having numeric ids rather then alphanumeric data.

    Do you know what type of activity will reproduce this case?

    From looking at the data where the $ amount is zero on that row it look like something it may be ok to ignore.
    But I want to be able to replicate it to clearly validate we’re doing the right thing.

    Thanks much,

    Amir

    Like

    • Hi Amir,

      The ‘REMIT’ transactions are generated by Dynamics GP during a check run when a remittance needs to be printed, based on rules set up in GP for the payables subledger. Here is one example of when this might happen:
      1. You cut a check for vendor A on 1/2/11.
      2. You enter a credit memo for vendor A on 1/3/11.
      3. You enter an invoice for vendor A on 1/4/11 and apply the credit memo from step 2 to the invoice.
      4. On 1/5/11 you do a check run and include all your vendors, or some vendor range that would include vendor A. In the Payables module setup you have the ‘Print Previously Applied Documents on Remittance’ selected. As part of the check run a remittance document for vendor A will be generated by GP showing apply information since the last time you have cut a check to vendor A. It will not use up a check number, but a ‘transaction’ is created for GP to be able to print the remittance.

      These remittance transactions will always have an amount of zero and should be fine to ignore, as you suspect.

      Hope that helps,
      -Victoria

      Like

  7. Victoria,

    I need to obtain the voucher number and check information for an invoice that is entered into the Receivings Transaction Entry screen. I know there is information in the PM30300 table, but it doesn’t include the receipt number. Do you have a way to collect this information via the receipt number?

    Thanks for all of your posts…they have saved me on a few projects :-)
    Jerri

    Like

  8. Victoria, I have received immense knowledge from your site, and I sincerely thank you for posting this information out there.

    I have a question related to Payables Apply. We had a situation where we were applying payments to invoices and received an out of memory error on the database server that is running GP. We were left with a batch that had half applied that we cannot unapply, or recover the batch on.

    Now, the batch is no longer available in batch recovery and I cannot find the apply details or distributions in the work, open or historical tables. Is there a way we can unapply this batch so that we can attempt to repost?

    Like

    • Hi Jason,

      Thanks for the kind words. I have run into similar situations before. First step is to run check links and reconcile on the purchasing series. Sometimes that will clear up the issue. If that does not help, then you will need to fix this directly in the tables. Since every situation is different, I would advise to get your GP partner or GP Support to help with this, as it can get pretty involved and it’s easy to get undesired results.

      -Victoria

      Like

      • Wow! Thanks for the quick follow-up. I thought our Controller had already run Check Links, but after just speaking with him I found he hadn’t. We’re going to try that tonight.

        I consider myself to be pretty savvy, but I’m concerned with being directly involved with this issue due to my lack of knowledge of the Purchasing tables. I feel that if I had a little more intimate knowledge I would be able to clear this up if Check Links doesn’t work, but I believe you’re right and we will be calling our GP Partner for assistance with this.

        Thanks again!

        Like

  9. Amir,

    I am not quite sure what you’re asking for here…we have not done a customization like this, so I don’t know what other information I can give you for it.

    -Victoria

    Like

  10. Hey Victoria,

    Thanks much for this post.

    We are tying to automate reading back the check cut process data from GP purchasing module. We are on version 9 and are not considering updating it.
    We are sending 4 DOCTYPEs of transactions to GP through taUpdateCreateVendorRcd, http://msdn.microsoft.com/en-us/library/bb648406(v=MSDN.9).aspx: 1=Invoice, 3=Misc. Chrg, 4=Return, 5=Credit Memo.

    During the check cut/post query there is a report titled: “Checks With Stub on Top” which has exactly the data that we are looking for.
    – seller id and name.
    – GP check id and check total.
    – A list having exactly one line per transaction we sent over. The transactions have a few columns but only 2 matter for us the voucher number (column 1) and the amounts (column 4). For instance on some test data on with respective DOCTYPE 1, 4, 5 and 3 it looks like that (last two columns dropped for brevity):

    ((our company name)), Inc.                 00000000000000000322
    
    ((vendor id))  ((vendor name))    00000000000000573     9/30/2010
    
    VCH-28824  VMD-100110-28824  10/1/2010  $1,033.08   $48.85  $0.00
    VCH-28825  VMD-100110-28825  10/1/2010  ($619.70)    $0.00  $0.00
    VCH-28826  VMD-100110-28826  10/1/2010  ($364.53)    $0.00  $0.00
    VCH-28827  VMD-100110-28827  10/1/2010    $210.28  $210.28  $0.00
    
         $259.13    $259.13    $0.00     $0.00     $259.13
    

    1. Our first preference would have been to read that data back.
    Is any GP history preserving that exact output from the GP check cut process?
    a. Is there a flag / config to flip for enabling it? (otherwise I see that some of the history and/or reprint tables in http://vstoolsforum.com/blogs/dynamicsgp/archive/2007/04/28/dynamics-gp-payables-management-rm-tables.aspx are empty)
    b. Is there a GP reports for that data _after_ the check was cut?
    c. Is there an api or GP stored procedure for reading it?

    2. If option 1 in not available the next best option would be to use your posted query.
    Your query does filter on P.DOCTYPE = 6 in the end. That makes the query show only check types. I have dropped that condition so now it shows both check and transaction data. I am also reporting P.DOCTYPE back as a column so the difference could be tracked by the reading code.

    Once we use your query, the data shows how one transaction was applied to another per the vouchers in Payment_Voucher_Number and Apply_To_Voucher_Number. They would show voucher numbers for P.DOCTYPE 6. Then for P.DOCTYPE = 6 Payment_Document_Number would show the check id and Apply_To_Voucher_Number would show the voucher number of on of the invoice transactions.
    Now the tricky part which seems to help solve our requirements – we draw a logical “linking” tree of all the voucher numbers (Apply_To_Voucher_Number for checks [=6] and both Apply_To_Voucher_Number and Payment_Voucher_Number for transactions [6]). Then all the transactions on each check’s tree are the ones applied towards that check. And the amounts in Payment_Functional_Amount seem correct and matching our expectations and seems that functionality is similar to what we had in option 1.

    Have questions about using this:
    i. Is this a reasonable solution, or is there a better way to do it?
    ii. What happens if one invoice (doctype=1) is _exactly_ consumed by one or more return (doctype=4). Would those transactions not get connected to the logical tree of the check?

    Thanks much,

    Amir

    Like

    • Hi Amir,

      Unfortunately, GP does not store the data in the way you want to use it. Even though you can apply a credit memo or a return at the time of the check creation process (or between the last check and the current check) and these transactions will show up on the check stub, the exact data that was on the check stub is not stored by GP. Since credit memos and returns are applied to invoices or misc. charges, not checks, there is no relationship created or stored in GP between the checks and the credit memos or returns that appear on that check stub. And, as you correctly point out, if a return or credit memo is the exact amount of an invoice, the two will be applied together and may or may not ever appear on the check stub, depending on other settings.

      If you absolutely need to have the same exact data as what is on the check stub, you may need to create a customization to store the data required for this. If it exists at the time of printing the check, you should be able to capture it at that point in custom tables. A less complicated option may be to store physical copies of all the check stubs. If these are used infrequently, this approach may be fine. If this is needed constantly, then a customization may be the better approach.

      -Victoria

      Like

      • Hi Victoria,

        Out of the options I listed it seems you recommend only looking at no 1. and not 2. Since if some data is lost then there is no way option 2 will cover it.

        Then we do need the exact check data and we do need to automate it. Yes I thought about having our financial folks store all the check cuts as files then parsing them back. This is not reliable or solid as you also pointed.

        So it appears capturing the data in custom tables at time of check generation is the best way to go.

        Would you kindly point where to implement such integration?
        Adding a table and insert statements sound simple.

        Not clear how come they have not yet added that to the product. Than as long as it’s customisable, that will be ok for us.

        Thanks for the answer,
        Amir

        Like

        • Amir,

          I thought I addressed option 2 by saying it’s not possible to get that data, since it’s not stored. You’ll get the check apply details and the separate credit memo and return apply detail, but you will not be able to duplicate what exactly what was on the check stub.

          As far as creating this customization, that’s not something I can help with on a blog comment. In my experience, it’s usually not as simple as it sounds. I would recommend working with your Dynamics GP partner to create this for you.

          -Victoria

          Like

          • Hey Victoria,

            About creating the customization, would you be able to point us to where such integration applies? Yes I understand your recommendation and won’t expect a full solution on the blog per your point. Would still want to get a good idea of the type of work it requires first, then we can evaluate internally and decide if we want it passed to our Dynamics GP partner.

            Thanks for the answers,

            Amir

            Like

          • Hey Victoria,

            Status update and a quick question.

            So we’ve gone with option 2 for now for 2 reasons – first to avoid the GP customization needed. Second since we were already comfortable reading that data. We know it’s not perfect, but also believe it would be rare, then we’ll throw in the fact that we’ll be closely monitoring it (send alerts if it happens) + make it simple to manually fix the data – then it’s a non-perfect but pretty practical solution. (in fact all amounts are being read back, even if amounts exactly consume others. Just that when they exactly consume the explicit association to check id is lost. In case one can guarantee a single check per day per seller we could have been deducting the association based on date+seller)

            Then another good news is that we are moving to the latest GP code soon.
            In which case – since we know this is a missing the option 1 feature in GP – do you have any recommendation or knowledge how to check / where to look up if it’s planned for an upcoming release?
            If not yet planned, I would want to file them a feature request for adding it.

            Thanks,
            Amir

            Like

  11. Victoria, as usual, this was EXTREMELY helpful.

    Like

  12. Victoria –

    What does it mean when you have rows in PM30300 which have values for VCHRNMBR that don’t appear anywhere else? In particular there is no join to PM30200 or PM20000.

    I think it may correspond to payments in an unposted batch that Great Plains allowed us to apply anyway – which has left something of a mess I’m trying to come to grips with!

    Tony

    Like

    • Tony,

      Another possibility could be that history tracking was not turned on or history has been purged for the vouchers you are seeing in PM30300 but not anywhere else. If you suspect a data issue, I would recommend working with your GP Partner or GP Support to clear it up. Most likely it’s going to keep causing issues for you on a regular basis. :-(

      -Victoria

      Like

  13. Victoria…thanks so much for this script. I had this request from our payables department a few weeks ago. I sat down to start writing this and thought I might had already seen it here. Sure enough, I did and it works perfectly.

    Thanks!

    Like

  14. Victoria,

    Extremely useful collection of information!

    I really appreciate for this and effort you’ve put into sharing information.

    Regards,
    Santosh

    Like

  15. How can I connect GL20000 (or GL30000) to any of the PM and/or POP tables?

    Like

    • Lukas,

      Unfortunately, there is no one answer for this, as each module will be different. It also may not be possible for every subledger transaction depending on GP setup, how transactions are entered and a number of other variables.

      A lot of times when faced with a request like this, I like to ask the users why exactly they need a report like this. Perhaps the actual need or issue can be solved in a different way…

      -Victoria

      Like

      • Victoria,

        I understand that it will not always be possible. The majority of our transactions start in Workplace. Eventually they become invoices that are paid with checks.

        As long as I can get the relevant fields together for those entries and don’t exclude the GL20000 entries that do not the users will be happy.

        Right now they have an SSRS report relying on a stored procedure that returns an incorrect check# and date for the majority of the transactions. The stored procedure has over 500 lines of sql attempting to backfill the invoice# invoice date, check# and check Date into a table that began with GL20000 (and GL30000 even though it is empty) data.

        Thank you for taking the time to reply,
        Lukas

        Like

  16. Dear Victoria

    Thanks a lot for your reply. I will post this requirement to Microsoft

    Like

  17. Dear Vitoria

    First of all I want to congratulate you on the latest MVP award. Wish you that you will be awarded this and more in the coming years.

    Regarding GP 10 Security I have 2 concerns. Hope in your busy schedules you will be able to look in to this and give me some answer.

    One is that I want to restrict the users from voiding bank transaction. I tried many ways, but I could not. How I can achieve this?

    Number 2 is that I created and assigned a user the security roll for Professional Services Tools. But still when he click on any tool like combine accounts, he gets the message that “you must be logged in as ‘sa’ to utilize this utility”. How I can solve this?

    Thanks for your time

    Like

    • Abdul,

      For the Professional Tools question – there are a number of them that are hard-coded to only work for ‘sa’. No matter what permissions you use, they will still require ‘sa’ to run them. These is no way around this until Microsoft changes this. If this is important to you, I would recommend contacting them about this, as the more people that request a particular change, the more likely it is to get addressed.

      For restricting the ability to void bank transactions, since this is done from the same window as entering bank transactions, I don’t see how you would be able to restrict this unless you took away access to the Bank Transaction Entry window entirely. I don’t see a way around this without a customization.

      -Victoria

      Like

  18. Victoria,

    This is great stuff! Your site is on my Favorites bar!

    Thanks for all you do!

    Leslie Vail

    Like

  19. Victoria, this information is so helpful. I really appreciate the time and effort you’ve put into sharing information that is so relevant to helping businesses succeed with the applicable information. Have you considered publishing a SQL view for AR Applied transactions?
    Sandy

    Like

  20. Thanks for an extremely useful collection of information!

    Like

  21. Just want to say you thanks heaps for sharing your valuable knowledge with everyone.
    I was looking for this for some time.

    Like

  22. Hi Victoria,

    Do views work in GP 9.00.0281 for the Smartlist Builder? If so, what is needed? I keep getting the error message

    ” GPS Error: 58
    SQL Error: 7405 [Microsoft][ODBC SQL Server Driver][SQL Server]Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. This ensures consistent query semantics. Enable these options and then reissue your query.
    ODBC Error: 37000″

    when trying to add a SQL view from the company database.

    I tried corrected the problem by setting the ANSI_NULLS and ANSI_WARNINGS but still no luck.

    Like

    • Doug,

      SQL views absolutely work in all versions of GP 8.0, 9.0 and 10.0 that I have worked with. The only time I recall seeing an error similar to yours is when using linked servers. Are you doing that by any chance? If so, that will not work in a view with SLB (it’s a Dexterity limitation) and you will need to find a different way to get the data into your GP SQL server first.

      -Victoria

      Like

      • Victoria,

        I am not using linked serves. Should my ANSI NULL default box be selected in the database properties on the options tab?

        Like

        • Doug,

          The general rule for GP is that anywhere in settings where you see ANSI options, they should unchecked or set to False.

          The only time I have ever seen that error is when trying to access data on a different SQL Server instance than where GP is installed. If that’s not the case here, something else is going on and I would recommend posting your question on one of the Dynamics GP newsgroups or forums to see if you can get some other opinions.

          In the meantime, here is a similar question asked on Tek-Tips: http://www.tek-tips.com/viewthread.cfm?qid=1493496&page=10

          -Victoria

          Like

  23. Just wanted to say thank you again, Victoria! This is exactly what I need right now. I’m very grateful to you for sharing your knowledge with everyone :-)

    Like

Trackbacks/Pingbacks

  1. Concatenating strings in SQL Server | Interesting Findings & Knowledge Sharing - May 21, 2012

    […] 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: […]

    Like

  2. Concatenating strings in SQL Server – 5/21, Victoria Yudin | Partner Compete - May 21, 2012

    […] 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: […]

    Like

  3. Concatenating strings in SQL Server - Victoria Yudin - GP Technical Blogs - Microsoft Dynamics Community - May 21, 2012

    […] 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: […]

    Like

  4. Concatenating strings in SQL Server | Victoria Yudin - May 21, 2012

    […] 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: […]

    Like

  5. Victoria Yudin - September 27, 2010

    SQL view for Payables apply detail and GL distributions in Dynamics GP…

    Who doesn’t need yet another view for Payables transactions in Dynamics GP? The view below is a…

    Like

  6. SQL view for Payables apply detail and GL distributions in Dynamics GP « Victoria Yudin - September 23, 2010

    […] another view for Payables transactions in Dynamics GP?   The view below is a combination of my Payment Apply Detail and GL Distributions for AP Transactions views. It lists all Payments, then shows the […]

    Like

  7. SQL View for All Posted Payables Documents and Apply Info - DynamicAccounting.net - October 26, 2009

    […] Posted Payables Documents and Apply Info Victoria Yudin is back with a SQL View to provide all posted payables documents and related apply information. Thanks Victoria. We've got a lot of folks always looking for more SQL info for Dynamics GP. […]

    Like

  8. uberVU - social comments - October 24, 2009

    Social comments and analytics for this post…

    This post was mentioned on Twitter by dynamicsblogger: #dyngp SQL view for Payables payment apply detail in Dynamics GP http://bit.ly/1zB4df

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 1,640 other followers

%d bloggers like this: