SOP SQL Views

Dynamics GP Sales Order Processing SQL Views

8 Responses to “SOP SQL Views”

  1. Hi Victoria…you site has been most helpful. Thanks. I’m a financial guy for a company that was acquired….parent company uses GP10 and I’ converting to that now. My solution provider is giving me advice that I must upgrade to GP2010 to use invoices because the SOP Blank Invoice is already being used by the parent company….and that I can’t simply copy the existing invoice, change the logo, reference it as an another invoice format and use it, I don’t get it……how can such a comprehensive program be so restrictive re invoice formats?
    Thanks
    Ben

    • Hi Ben,

      It is true that GP is pretty restrictive with what you can do with invoice formatting out-of-the-box. This is mostly a result of limitations of the Report Writer inside GP and while there is now Word Template functionality to somewhat help with this, past very basic stuff I do not believe Word Templates are an answer either.

      To answer your ‘how’ question…what is restrictive for one company, may be absolutely fine for another. Many of our customers either do not use invoicing in GP or have very basic needs that are satisfied out-of-the-box with no issues. One of the benefits of a system like Dynamics GP is that it offers you the opportunity to (a) customize as needed and/or (b) choose from many available add-ons for specific functionality that you might need that’s not in the box. Once you get past the plain vanilla invoice, you either have a lot of modification/customization needed, or you may decide to get an add-on that makes invoicing easier. My company has a GP add-on called GP Reports Viewer that may help mitigate some out-of-the-box limitations surrounding invoicing.

      -Victoria

  2. Victoria

    Help, I am trying to develop sales reports for management and I am getting two different data set depending on the joins I use. I am joining a view (a union of SOP10100 and SOP30200) with the RM00101 table (for the Sales territory) using left outer joins. When I join only on custnmbr I get one set of data and when I join on custnmbr and custname I get a much small set of data. Since as far as I know the and tested both the custnmbr and custname are distinct can you give me a clue as to why two links are not better than one.

    • Hi Patrick,

      There may be more, but below are at least 2 reasons I can think of to never link on the customer name:

      1. The customer name that defaults onto new SOP transactions is taken from RM00101. However, as soon as it is defaulted, the users can change it to anything they want. The changed customer name will be saved with the SOP transaction and will now be different from what is in RM00101.
      2. Periodically customers change their name. Let’s say you have 500 SOP transactions for a customer with the name of ABC Carpets. Today you receive a letter from them saying their new name is ABC Home Furnishings. You change this on the Customer Maintenance window (which updates RM00101), however this new name will only be defaulted onto future new transactions, your existing 500 SOP transactions will not be changed unless you proactively do something about that (and GP out of the box cannot do this, you would need to use the PSTL Customer Name modifier tool or do this directly in SQL, however most companies choose not to do either).

      So, as you’re seeing in your results, linking on customer name is returning only a subset of the data you are looking for. Here is a query that will give you a list of all customers in SOP30200 with more than one name for the same customer ID:
      select CUSTNMBR, COUNT(*) Unique_Names from
      (select distinct CUSTNMBR, CUSTNAME from SOP30200) a
      group by CUSTNMBR having COUNT(*) > 1

      Here is another that will show you the customer names in SOP30200 that do not match what’s in RM00101 for the same customer ID:
      select distinct
      s.CUSTNMBR, s.CUSTNAME Name_in_SOP,
      r.CUSTNAME Name_in_RM
      from SOP30200 s
      left outer join RM00101 r
      on s.CUSTNMBR = r.CUSTNMBR
      where s.CUSTNAME < > r.CUSTNAME
      order by s.CUSTNMBR

      Hope that helps.
      -Victoria

Trackbacks/Pingbacks

  1. Interesting Findings & Knowledge Sharing » SQL view for sales quantities by item by year - January 26, 2012

    [...] see additional Dynamics GP SOP code please take look at this page. For additional GP reporting information and links, check out my GP Reports [...]

  2. SQL view for sales quantities by item by year - Victoria Yudin - GP Technical Blogs - Microsoft Dynamics Community - January 23, 2012

    [...] see additional Dynamics GP SOP code please take look at this page. For additional GP reporting information and links, check out my GP Reports [...]

  3. SQL view for sales quantities by item by year | Victoria Yudin - January 23, 2012

    [...] see additional Dynamics GP SOP code please take look at this page. For additional GP reporting information and links, check out my GP Reports [...]

  4. SQL view for sales quantities by item by year | Victoria Yudin - January 23, 2012

    [...] SOP SQL Views [...]

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 )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 422 other followers