Dynamics GP

Posts tagged with Dynamics GP

Management Reporter 2012 on GP 2015 Couldn't retrieve the list of available databases: The connection attempt failed.

While trying to configure Management Reporter 2012 on a brand new install of GP 2015 I received the following error:

"Couldn't retrieve the list of available databases: The connection attempt failed."

Configuration is SQL 2012 on Server 2012 R2, GP 2015 on Server 2012 R2.

Solution: Install Dexterity Shared Components 12 from the install disc for GP2013 R2.

I found the answer here:
https://community.dynamics.com/gp/f/32/t/146554.aspx

Thank you to Richard Markham.

Grant Permissions for Manufacturing SmartLists

When using Manufacturing in Microsoft Dynamics GP (both GP 2010 and GP 2013), people not assigned to the POWERUSER role are unable to see Manufacturing SmartLists by default - even users who are assigned MFG ADMIN and MFG_INQUIRY roles.

To grant permissions for these, you need to include them with a task. You can assign the permissions to whichever task you choose. I choose to assign different SmartLists to their matching inquiry task (INQ_MFG_XXX), in case custom roles are added for which there should be limited manufacturing permissions.

To add SmartLists to a Security Task:

1. Open the Security Task Setup window (Administration >> Setup >> Security >> Security Tasks)
2. Choose the Task ID for which you would like to add SmartList permissions
3. Select Product: Smartlist, Type: SmartList Object, Series: SmartList Objects
4. Check the boxes next to the SmartLists you would like to include
5. Click Save

The tasks to which I assign Manufacturing SmartLists:

INQ_MFG_BOM*
-- Bill of Materials

INQ_MFG_MO*
-- Manufacturing Orders
-- Picklists
-- Recorded Outsourcing Shipments
-- Sales Documents Not Linked to Manufacturing
-- SO/MO Link
-- Suggested Outsourcing Purchase Orders
-- Suggested Outsourcing Shipments

INQ_MFG_WIP*
-- Work in Process

GP Manufacturing Accounting Flow: Component Transactions and MO Receipts

In GP Manufacturing, the accounting flow for inventory transactions involved in a Manufacturing Order can be tricky, because they don't all follow the same logic. Below is a summary of the accounting flow for some of the basic inventory transactions that take place during the Manufacturing process.

Component Transaction Entry (Issue)
Issues raw materials to production/WIP:
-- Credits (decreases) the Inventory account
-- Debits (increases) the WIP account
 
To determine which inventory account to use, GP checks the Inventory account assigned to the Raw Material item.
-- If this is present, it will use the account
-- If it is blank, it will use the default posting inventory account
 
To determine which WIP account to use, GP checks the WIP account assigned to the Finished Good item that is being produced:
-- If the WIP account is present, it will use that account
-- If the WIP account is left blank, it will use the account assigned as the Inventory Offset account for the Raw Material item
 
IMPORTANT NOTE: If you perform a REVERSE ISSUE, which brings Raw Materials from WIP back into inventory, GP will put the Raw Materials cost out of WIP and back into inventory. However, if the WIP account of the Finished Good item is blank, it does not use the Inventory Offset account from the Raw Material item. Instead, it allows the transaction to post, leaving the WIP account blank. The resulting GL does not balance so it does not post, it has to be completed and posted manually.
 
MO Receipt
Completes production, consumes Raw Materials from WIP and issues Finished Goods to inventory:
-- Credits (decreases) the WIP account
-- Debits (increases) the Inventory account
 
To determine which inventory account to use, GP checks the Inventory account assigned to the Finished Good item.
-- If this is present, it will use the account
-- If it is blank, it will use the default posting inventory account
 
To determine which WIP account to use, GP checks the WIP account assigned to the Finished Good item that is being produced:
-- If the WIP account is present, it will use that account
-- If the WIP account is left blank, it will post the transaction without a WIP account and not give an error to the person posting the transaction. When it posts:
     - Inventory quantities are increased
     - An incomplete GL transaction is created, but does not post all the way through because it does not balance
     - The GL transaction needs to be completed and posted manually

 

GP 2013 Crash on Navigation Lists

Some of our clients have been experiencing a Dynamics GP application crash when selecting a Navigation List.

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: Dynamics.exe
Problem Signature 02: 12.0.270.0
Problem Signature 03: 5217d52e
Problem Signature 04: WindowsBase
Problem Signature 05: 4.0.30319.34004
Problem Signature 06: 5246811c
Problem Signature 07: 1432
Problem Signature 08: 17
Problem Signature 09: System.InvalidOperationException
OS Version: 6.3.9600.2.0.0.16.7
Locale ID: 1033
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: d1d9
Additional Information 4: d1d94a13d3609d6b740644c12508f581

I found this post from Donna Krizik that solved the problem:
http://www.crestwood.com/blog/view/dynamics-gp-2013-crashes-every-time-y...

Quick fix:
The Business Analyzer Fact Box was the culprit. I used the following script to turn it off and make sure it stayed turned off.

Use Dynamics
go

update DYNAMICS..SY07225 set FactBoxVisible = 0
go

CREATE TRIGGER
dbo.Update_SY07225_FactBoxVisible ON dbo.SY07225 AFTER INSERT
AS
Update SY07225 SET FactBoxVisible = 0
go

Error logging in to GP2013 "An error occurred while loading or initializing an addin."

Working with GP2013, I encountered this error logging in:

"An error occurred while loading or initializing an addin. Ask your administrator to check the Windows event log for more details. Dynamics will now close."

Checking the Event Viewer provided a bit more information:

"Microsoft Dexterity error:

The description for Event ID 0 from source Microsoft Dexterity cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

An exception occurred while trying to load or initialize the addin located at VAT100ElectronicSubmission.

Exception Details:
System.IO.FileNotFoundException: Could not load file or assembly 'VAT100ElectronicSubmission, Version=12.0.0.0, Culture=neutral, PublicKeyToken=5eca28f6788f0a91' or one of its dependencies. The system cannot find the file specified.
File name: 'VAT100ElectronicSubmission, Version=12.0.0.0, Culture=neutral, PublicKeyToken=5eca28f6788f0a91'
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName)
at System.RuntimeType.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
at System.Type.GetType(String typeName, Boolean throwOnError)
at Microsoft.Dexterity.Bridge.AddinManager.LoadAddinsFromConfig(String configPath, String sectionName)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

the message resource is present but the message is not found in the string/message table"

When I first installed 2013 I included most available modules, but later removed the VAT Daybook feature. I was unable to get back into GP after this change.

I checked for stray .dll or dictionary files in the GP2013 folder, but there were none. On an impulse, I checked the Dynamics.exe.config file and found two references to VAT100ElectronicSubmission. I made a backup copy of the config file and removed

< addin name="VAT100ElectronicSubmission" type="VAT100ElectronicSubmission.GPAddIn,VAT100ElectronicSubmission,Version=12.0.0.0,Culture=neutral,PublicKeyToken=5eca28f6788f0a91" / >

from the addins/Dynamcs and addins/DynUtils nodes. With this change, I was able to get back into GP without any further errors.

Syndicate content