Dynamics GP

Posts tagged with Dynamics GP

GP 2013 and 2015 GP Web Services "Exception message: The security object does not exist"

After moving the GPWEBSECURITY database for GP Web Services and running a repair we received the following error opening the Security Console:

"Exception message: The security object does not exist. Missing Key: 25cc1a21-2cc4-4b13-a1c8-eea186fb688a"

Turns out we ran the wrong repair.  DO NOT run the repair from the GP Web Services Configuration Console.  Instead, launch the GP Setup.exe from the GP installation media.  This will detect the existing install and give you the option to repair.I used information from the following link and updated it for the new web services that does not run in IIS:

https://support.microsoft.com/en-us/kb/943949

To determine the scopes in the ADAM database, use the Authorization Manager (Azman.msc) Microsoft Management Console (MMC) snap-in to browse the database. To do this, follow these steps:

  1. Click Start, click Run, type azman.msc, and then click OK.
  2. On the Action menu, click Open Authorization Store.
  3. Click Active Directory.
  4. In Windows Explorer, open the following folder:
    C:\Program Files\Microsoft Dynamics\GPWebServices\WebServices
  5. Use Notepad to open the DynamicsSecurity.config file.
  6. Copy the following value for the AzManConnectionString setting:
    mssql://Driver={SQL Server};Server={MySqlServer\MyInstance};/GPWEBSECURITY/DynamicsGPWebServices
  7. Paste the value into the Store Name field in the Open Authorization Store window, and then click OK.
  8. Expand the DynamicsSecurityService store.
  9. Expand 25cc1a21-2cc4-4b13-a1c8-eea186fb688a to view the scopes. A folder graphic designates the scopes that are installed and that have an assigned integer value.

I was able to verify that the database in the new GPWEBSECURITY database did not contain the data from the original database.  I restored from backup.  Reran the repair.


NOTE: I also had to search all .config files in the install folders for the original MyOldSqlServer\MyOldInstance and replace it with the MyNewSqlServer\MyNewInstance.

I used FNR.exe from codeplex.

SSRS Report Builder "Application cannot be started, contact application vendor."

When trying to launch Report Builder you receive the error "Application cannot be started, contact application vendor."

I did two things that seemed to of helpled.

1. Open SSMS and connect Server type "Reporting Services", Server name. Right Click the Server Name in Object Explorer and pick Properties. Under Advanced setting in the Reports section set the ReportBuilderLaunchURL to https://serverurl/ReportServer/Report/BuilderReportBuilder_3_0_0_0.appli....

2. Create a Web.config file in the C:\Program Files\Microsoft SQL Server\MSRS11.instancename\Reporting Services\ReportServer\ReportBuilder folder containing the following

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<compilation tempDirectory="C:\Program Files\Microsoft SQL Server\MSRS11.instancename\Reporting Services\RSTempFiles\"/>
</system.web>
</configuration>

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

 

Syndicate content