Flowchart of SOP and Inventory

I always wanted to train the users using the flowchart for easy and better understanding.  So wanted to store this from the community for future use.  The following collection of flowchart of SOP / POP / Inventory / Manufacturing.  Thanks to Leslie and Mahmoud and Waqas.

Manufacturing Labor Code Definition

On GP 2013 radio button for fixed overhead and variable overhead in the Labor Code Definition window is not visible.  This is a bug of 2013  4 radio button groups in total for this window which got invisible because of improper Tab sequence order. This can modified on this Window to set the tab sequence for all the radio groups which you are not able to see.   This has been shared by Naga in the community which is useful information.

Thanks,

Babu Baskaran

Problem with Print Purchase Documents GP 2013

We had a problem with Printing purchase order documents after the migration of GP 10 to GP 2013.  The GP installed in Terminal server and none of the users were able to print  PO using Print Purchasing documents.  I was the only user were able to print it one of the terminal server.  I debugged this for so many days with no clue.  Finally I compared the 2 servers on my login  and checked the difference between the two of them.  The terminal which I was able to print had setting of English(United States) with MM/DD/YYYY date format under Region and Language.  And the 2nd terminal had English(United Kingdom) with DD/MM/YYYY date format.  I checked the 2nd server by changing the date format to English(United States) with MM/DD/YYYY format and luckily the PO got printed.  So this look like the print purchasing documents only work if the date format is MM/DD/YYYY so its a bug with GP 2013 with Europe date format.

Its my pleasure to serve anyone better,
Thanks & Regards,
Babu

Interesting Information by Frank Hamelly

Dynamics GP Tools that you may not know about . . .

Here's a list of tools available from your Microsoft Partner that are not a standard part of the
Professional Services Tools Library toolset, along with the GP versions that they apply to.
 Most, if not all, of these are installed by dropping a file into the GP folder on your application
 server and restarting GP.  Talk to your partner for more information.

SQL Server xact abort setting breaks Microsoft Dynamics GP by David Musgrave

RATE THIS

David Musgrave 

16 Jan 2014 9:00 PM 

• 0

Happy New Year. Wishing everyone a very successful 2014.
I have been back from leave for two weeks, but have been really busy with support cases.
One recent case highlighted a SQL Server setting that I have never used before and the negative consequences of changing the setting from its default value of "off".

Background
The customer reported that when Payables Management transactions were fully applied and should be moved to history, that what was happening was the transaction was being removed from the Open tables, but was failing to be added to the History tables. The end result was that the transactions would just disappear from the system.
We used the Support Debugging Tool (http://aka.ms/SDT) to capture logs. From the Dexterity side nothing looked unusual, but from the DEXSQL.LOG the system showed a couple of unusual behaviours.

1. We were seeing many more of the Invalid column name 'desSPRkmhBBCreh' errors than would be expected. These errors are not a problem in themselves (see blog post), but the frequency that they occurred at was unusually high.
    
2. We were also seeing many commands in the DEXSQL.LOG repeated. Calls to stored procedures and select statements being issued multiple times when they would normally only occur once.

Reviewing the case notes, I found that it was mentioned in passing that the problem started occurring AFTER the Microsoft Dynamics GP system was migrated to a new server.
So we needed to look at the Database configuration and Server Configuration to see what differences could be responsible for this behaviour

The Problems
Further investigation using the sp_helpdb command did highlight that the Dynamics GP system and company databases were set to compatibility 900 (SQL Server 2005) and the database owner was not set to DYNSA.  These settings were easily fixed using the Options page on the Database Properties to change the Compatibility Level and the T-SQL command sp_changedbowner 'DYNSA' to change the owner for each of the databases.  While these settings were wrong, I doubt they were responsible for the issues we were seeing.
I then received an email which explained that the customer's IT Administrator had been comparing settings on the SQL Server between the old and new servers and noticed some differences on the Server Properties on the Connections page.

 

The differences notices was that on the old server: the Remote Query Timeout value was set to 1200 seconds instead of the default 600 seconds, and on the new server: the option xact abort was checked (the default value is unchecked).
The Remote Query Timeout being 1200 would not cause any problems for normal operation. I suggested they move that setting to the new server. There may have been a reason it was increased.
The xact abort setting however was once that I have never come across before, so I did some research to understand what it means and how it can affect the behaviour.

The Solution
Looking at SQL Books online for the Server Properties Connection Page it explains the xact abort settings as "Rolls back a transaction if a Transact-SQL statement raises a run-time error."
I also found an interesting article about the option: Use Caution with Explicit Transactions in Stored Procedures.
While the blog article suggests that it would be safe to leave the option on, the author does not know the Dynamics GP application.  Dynamics GP does generate a number of expected runtime errors (such as the column desSPRkmhBBCreh one) and ignores them or handles them as appropriate.
However, if the xact abort option is enabled, it will cause transactions to be rolled back for the slightest error.... even ones that Dynamics GP expects.
After unchecking the option and restarting the SQL Server, the problems stopped occurring.

Analytics for Microsoft Dynamics GP by Mark Polino

Change has been proved to be an inevitable part of organizations lives, no organization can survive without facing it and managing strategies to respond in an efficient and effective way. In this essence, the importance of decision making emerges as a key function for managers.

In Dynamics GP, decision making has been absolutely enhanced with the new plug and playAnalytics for Microsoft Dynamics GP by MVP Mark Polino. Data has been there in your system, but now well presented in a simple and meaningful way through elegant dashboards which overall provides the the capability to analyze, manipulate and correlate your business data efficiently and effectively.

Here’s the Sales, Starter Edition Dashboard:

The dashboard includes:

• Top Customers with corresponding costs
• Top Items with corresponding costs
• Top Salespeople, Territories and Sites
• Sales over time with forward looking projection
• Sales mix over time by item class
• A full range of data filters to control information

Interesting Blog by Vaidy

#MSDYNGP Extender View Involving Extender Window/Form – Strange “Add Link” Issue & Reason.

Posted on January 14, 2014 by Vaidhyanathan Mohan

 

 

 

 

 

 

Rate This

Firstly, I am not sure whether I should categorise this as an issue. Let me explain this with an example.

For illustrative purpose, my requirement is to assign an additional information to customers. In addition to Country Code, I would like to assign from which continent a customer is from.

First step; to create an Extender Form named Continent Maintenance in which I will maintain list of continents. I do not need anything information other than an ID (Continent ID) and a name (Name); as shown below:

Note that there are no fields apart from ID and Description.

Second step; I am going to create an Extender Window for Customer Maintenance (Cards -> Sales -> Customer -> Additional -> Continent) to assign a continent to a customer. Extender Window definition is as follows:

Third step; is to check whether things are properly done and confirm. Let me open Customer Maintenance and see if I can access this new Extender information:

Perfect. Let’s now get into the actual issue.

I would like to create a view to retrieve customer continent information. To achieve this, I would like to link Assign Continent (Extender Window) with Continent Maintenance (Extender Form) to get the continent name. Ideally, my view should retrieve following:

Customer ID, Continent ID, Continent Name

Now, when I try to create an Extender View linking my Extender Window and Form, I end up facing below issue:

Did you see that? I do not have my Extender Form fields shown here. I have two fields; Continent ID and Name. Where are they? Why are they not shown here? Shouldn’t it be available for me to link with my Extender Window’s Continent ID?

REASON: If your Extender Form DOES NOT have any other field than an ID and a Description (in my case, Continent ID and Name), ADD LINK To Field will not list out the ID and Description fields.

Is that the actual reason? Let’s confirm by adding another field to Extender Form as follows:

After adding above field, Additional Info., look at my Extender View Add Link now:

Did you see that? They are available now. AFTER adding a field in addition to default ID and Description fields.