Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

SmartList field bug - Purchasing>Payables Transaction> Payment Entry Type field

Posted on by Microsoft Employee

IN GP 2013, SmartList Purchasing, Payables Transaction, I believe there is a bug in the Payment Entry Type field logic.

There are 4 Payment Entry Types, and the field is defined as a dropdown type. However, the Search dropdown only lists Check, Cash, and Credit Card. It does not include the new EFT type.

 Further, if I search for Payment Entry Type = Check, nothing is returned. If I search for Payment Entry Type = Credit Card, I get back nothing back. If I search for Payment Entry Type = Cash, I get back all the Credit Card type entries.

Is anyone else experiencing problems with this field? If so, what is the best way to report this bug to Microsoft?

We are beginning to implement EFT processing, so need some way to review and report on all my EFT entries. I thought this would be the easiest way, but apparently not!

Thanks!

*This post is locked for comments

  • Redbeard Profile Picture
    Redbeard 12,931 on at
    RE: SmartList field bug - Purchasing>Payables Transaction> Payment Entry Type field

    You're welcome!

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: SmartList field bug - Purchasing>Payables Transaction> Payment Entry Type field

    Thanks Harry, for delving into the issue, and providing a SQL solution!

    Thomas, I will report it to Microsoft and get a fix submitted.

  • Suggested answer
    Thomas Newcomb Profile Picture
    Thomas Newcomb 1,810 on at
    RE: SmartList field bug - Purchasing>Payables Transaction> Payment Entry Type field

    Hi Robert!

    Thank you for the question on this issue, I would recommend creating a Support incident with Microsoft Dynamics GP Support to look at this issue closer. I have performed some research into this in which I had found an old quality report from 8.0 with a similar issue to this. If you do create a Support incident and it is found to be a known issue the case should be changed to a non-chargeable incident.

    ~Thomas Newcomb

    --------------------------------------

    Dynamics GP Support Engineer

    --------------------------------------

    This posting is provided "AS IS" with no warranties, and confers no rights

  • Verified answer
    Redbeard Profile Picture
    Redbeard 12,931 on at
    RE: SmartList field bug - Purchasing>Payables Transaction> Payment Entry Type field

    Robert,

    I have noted similar issues in Dynamics GP 2013 SP2 (build 1570) - the EFT Transaction type come up with no text (as blanks), and the filters do not work as they are supposed to.

    In order to report a bug to Microsoft, you have to log a technical support issue and be up on the most recent service pack.  If the issue is a bug, and this one looks like it is, Microsoft should credit back the technical support incident.  Your partner should be able to help you facilitate this.

    Being more of a problem solver than reporter, here is a SQL Query which does the basic work of the SmartList in question, though it is very raw - you will not the field value that corresponds to EFT = 3:

    select 'HIST' as 'Status',

    Case PYENTTYP when 0 then 'Check'

    when 1 then 'Cash'

    when 2 then 'Credit Card'

    when 3 then 'EFT'

    else 'ERROR'

    end PMT_TYPE,

    * from PM30200 PMH

    where DOCTYPE = 6

    Union all

    select 'OPEN' as 'Status',

    Case PYENTTYP when 0 then 'Check'

    when 1 then 'Cash'

    when 2 then 'Credit Card'

    when 3 then 'EFT'

    else 'ERROR'

    end PMT_TYPE,

    * from PM20000 PMO

    where DOCTYPE = 6

    --where PYENTTYP != 0

    order by 'Status' desc,DOCNUMBR

    Victoria Yudin has a better version, which creates a View in SQL, which can be used as the foundation for an SSRS report.

    victoriayudin.com/.../sql-view-for-all-posted-payables-transactions-in-dynamics-gp

  • DinB Profile Picture
    DinB 3,812 on at
    RE: SmartList field bug - Purchasing>Payables Transaction> Payment Entry Type field

    Yes, It seems like a bug. You could try submitting product suggestion in the following website.
    https://connect.microsoft.com/dynamicssuggestions

    Here are few more findings after my testing in GP 2013 R2.

    First of all, the SDK document shows the "Payment Entry Type" field in the PM tables can hold only following 3 values:
    0 for Check
    1 for Cash
    2 for Credit Card

    There is no value for EFT for this field in database. So I don't think this column can be used to search for EFT.

    I checked the background SQL Scripts using Profiler and there are certainly some strange things happening.

    When I search that SmartList by "Payment Entry Type", it is only searching for records in the History table PM30200 and ignores the records in Work (PM10000) and Open (PM20000) tables . This does not happen when searching by other columns such as "Document Type".

    Also, When I search for "Payment Entry Type = Cash" in SmartList, the background SQL script is selecting the records from the History table PM30200 using the following clause:
    WHERE ((TWO.dbo.PM30200.PYENTTYP IN (2)))
    The value "2" in database is "Credit Card". So it is returning the "Credit Card" types instead of "Cash"

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans