2/08/2011

The selected position is default and cannot be deleted

The title of the post “The selected position is default and cannot be deleted” is actually an error message that is encountered in Microsoft Dynamics GP Business Portal Requisition Management module.

This message will pop up when we try to delete a user in Approval hierarchy who is appearing multiple times in the hierarchy and is assigned the default status.

When the settings are such that users can be added multiple times in the hierarchy, the approval hierarchy of the requisition management allows the user to be added multiple times. For example, User A Assigned under User B and the same User A assigned under User C.

The question is which level this user will be assigned default status? Default User status is assigned when the user is first defined in the approval hierarchy. Typically, it is called the first level. In the above example, User A is assigned under User B and then to User C. In this case, User A assigned to User B will be assigned default status.

Assume a scenario, You realize User A under User B is no longer required, and you quickly navigate to the hierarchy proceeding to delete this user. Immediately system throws the error message in the post title.

Solution to this problem is to first change the default status of User A under User B to User A under User C. In other words, Assign the default to a level other than the first level in which User A is assigned. This can be done by right-clicking the User and click Assign Default.

Once this is done, You can now proceed to delete the user which was earlier a default user and you no longer see this message.

2/06/2011

GP Basics: Historical Inventory Trail Balance in Excel

Historical Inventory Trial Balance is available in Inventory  > Reports > Activity > Historical IV Trial Balance Report. This report will run into several hundred pages most times based on the size of Inventory.

To have this report in excel is always a good choice and easy to work on the report for reconciliation purposes if you have it nice formatted excel worksheet. Smartlist by making use of smartlist builder makes it an easy task. All you have to do is build a custom smartlist builder report using SEE30303 Table (Termed as Inventory Transaction History Detail Table in GP).

I am providing a link to download the smartlist that gives the Inventory Historical Trial balance. Please note that I’ve used Item Master table also along with Inventory Transaction History Detail table in order to pull Item description from the former because Item description is not stored in the latter.

Download the smartlist and import it into Smartlist Builder using smartlist builder Import functionality. As and when needed, You can just get the smartlist results and export it into excel.

Click the link below to get this smartlist.

Inventory Historical Trial Balance report File

2/05/2011

Transaction Reference for Cost Variance Journals

Sometimes A Finance Controller wonder where from this document originated?. This happens with the cost variance journals that posts to GL automatically. Here is the list of transaction reference prefixes for these journals. Please note that the credits to this information goes to Tristan Thor from Microsoft who has provided this in response to a forum question on Dynamics GP Forum.

1. BOM – assembly transaction
2. INV – invoice from the Invoicing module
3. IVT – inventory transfer
4. IVA – inventory adjustment
5. IVV – inventory variance
6. SALES – sales invoice from Sales Order Processing
7. PRTN – purchase return
8. MCTE – for a transaction that originated in Manufacturing Component Transaction Entry
9. MRCT – manufacturing receipt
10. MCLS – manufacturing close, including regular close and Quick MO
11. STCK – stock count variance
12. FSSC – field service Service Call
13. FSRMA – field service RMA
14. FSRTV – field service RTV
15. FSWO – field service Work Order
16. PA – project accounting
17. POP – close a PO line in Edit PO Status
18. RECON – created by Inventory Reconcile
19. CONV - created by an upgrade conversion
20. MCTERCT - If the items were issued in the Component Transaction Entry window and then the invoice is completed the adjustment will have a prefix of MCTERCT
21. MRCTRCV - If the items were issued in Mo Receipt Entry (they are "back flushed") and then the invoice is complete the adjustment will have a prefix of MRCTRCV.
22. MCLSRCV - If the items were issued in the MO Close process (the MO was partially received and more "back flushed" items were issued during the close) and then the invoice is completed the adjustment will have a prefix of MCLSRCV.

GP Basics: Inventory BOM And Manufacturing BOM

There are two Bill of Materials available in Dynamics GP where Manufacturing module is installed. One Bill of Materials (BOM) is available in the Inventory module, Which I’d call it as Inventory BOM or Core BOM. The other BOM is from Manufacturing module where it is more detailed and extensive functionality.

The Inventory BOM works best with companies having a very simple production process so as to just assemble materials into a finished product. Here production is recorded after the fact.

The Manufacturing BOM makes use of both Inventory and Manufacturing order processing modules where the production of finished goods is recorded. In addition to Material costs, Labor costs are also tracked.

INVENTORY BOM

MANUFACTURING BOM

WIP is not tracked Tracks WIP for Materials, Labor and Machine Time
Enter standard and Design QTY Enter Fixed and variable QTY
Link to associate Lot and serial numbered items with Lot and serial numbers of FG Link with the BOM item to a particular Routing sequence
Only one BOM type Multiple BOM Types and Categories (Manufacturing, Engineering, Archived, Configured and Super)
Each Component on BOM can have effective and obsolete date Each component on BOM can have effective in date and out date
No Lead Time Lead time by BOM Date
No integration with SOP and POP Integrates with SOP and POP
Visual Indicators for serial/lot tracked items and overrides Visual indicators for BOM Items such as Alternates, Serial/Lot tracked, Phantom
User defined fields for the assembly document User defined fields for the BOM components
BOM Copy BOM Copy
No Revision levels Track revision numbers for all changes to BOm
Quantities can be entered only in base UOM Quantities can be entered in UOM Schedule and not necessarily base UOM
No Mass update Automatically update BOM changes using BOM Mass update
No Floor Stock ability Mark Items as Floor stock

For more information, Refer to this post from Mariano Gomez on the same subject.

Inventory BOM vs Manufacturing BOM

2/04/2011

GP Basics: Manual payment Distribution

Do you know how distributions in Manual Payment entry of Payables management are defaulted? In this example post we will see how the distributions are defaulted in Manual Payment entry.

Example: Vendor ABC is mapped to Accounts Payable Account 000-2100-00 and Purchases Account 000-1300-00 in vendor Accounts under Vendor Maintenance.

I. When you create a manual payment entry for this vendor, the default distributions should be as follows

ACCOUNT DIST TYPE DEBIT CREDIT
000-1100-00 CASH - $1000
000-2100-00 PAY $1000 -

Note that in this scenario the payment is created without applying an invoice.

II. In this second scenario, We will first create a vendor Invoice with the following distributions. Instead of the default Accounts Payable, let us select a different account 000-2100-01 under the distribution type PAY.

ACCOUNT DIST TYPE DEBIT CREDIT
000-1300-00 PURCH $1000 -
000-2100-01 PAY - $1000

Now Let us create a manual payment entry for the above invoice and simultaneously apply the invoice. See how the distributions are affected when the payment is applied to invoice above on the fly.

ACCOUNT DIST TYPE DEBIT CREDIT
000-1100-00 CASH - $1000
000-2100-01 PAY $1000 -

The point here is that when a Payment is created without applying the same to an open invoice, the distribution is governed by the default posting accounts mapped to the vendor. Instead, When you create a payment entry, apply it to an open invoice, then the distribution for the type PAY (Which is Accounts Payable) is defaulted from the Invoice distribution entry and not the default vendor posting accounts.

2/03/2011

GP Basics: Allow Account Entry

Allow Account Entry is an option in Account Maintenance screen. Account Maintenance is used to maintain (create) the Posting account. Allow Account entry is marked by default in the Account Maintenance screen.

image

When it is unmarked, It prevents an user from manually entering or choosing this account in transaction or distribution entry windows irrespective of the module. However, this account can be used as the default posting account.

This feature works well with accounts like Inventory, Accounts Payable, Accounts Receivable which minimize balances mismatch between subsidiary ledgers and General ledger as it does not allow direct posting into GL.

There is an exception to this feature. This functionality fails to work in Purchase order entry. In Purchasing Item detail entry, this account can be selected manually despite the selection in Account Maintenance. This might be a possible bug.

image

Ran out of values in format symbols list

We encounter this error in Microsoft Dynamics GP Report Writer. I experienced the same recently and here is the cause and resolution for the error.

Cause

If we have fields dragged to the far right of the report layout or presence of any unusual characters like #,*,+ in text fields of the layout, we may get this error.

Resolution

Quite simple that drag the fields back to the left or remove them if this is due to dragging issue. If it is due to the special characters, remove them from those text fields and add the text back to the report.

Requisition Management–Roadmap

I’d say this is a million dollar question when some one asks me when Requisition Management module for Dynamics GP gets a feature pack. Unlike Dynamics GP which gets frequent upgrades through various feature and service packs, this specific module within Business Portal looks to be completely kept in the dark. Microsoft is also tight lipped when I queried on the same in several forums on various feature requirements in this one module.

In one of his articles, Mariano presented a nice graphic of Dynamics GP roadmap, if my memory is good enough. I tried my level best searching one for Requisition Management or Business portal, I had a hard luck in getting it. Probably it doesn’t exist either or not available on the public internet.

So, What is this module lacking in terms of features? I highlighted certain requirements in my earlier post titled Requisition Management – Enhancements When?. Adding to these requirements, there comes several other requests from various clients lined up  for many partners, if I’m not wrong.

I do not go into each one of those requirements and rather restrict this post with one critical requirement which is integration with project accounting module of Dynamics GP. So What’s the issue with this? Let’s look at it.

Issue

Requisition Management module does not support Dynamics GP Project Accounting module. Period. When Project Accounting module is installed within Dynamics GP, Purchase order entry screen uses Project Number and Cost category fields in PO Line item fields. We all know that we can easily convert the requisitions to purchase orders with a single click of a button. However, when a requisition is converted to a PO where PA is installed, immediately Project number and cost category fields are greyed out. System doesn’t even allow you to enter these fields manually also.

Question

How is it justified when PA is a module within Dynamics GP, Yet, the Requisition Management module doesn’t support creation of POs’ when PA is activated? Just for the sake of two additional fields, Should we forgo the entire Requisition management module or for the sake of requisitions, should we forgo PA module itself?

Requisition Management is a smart development where you see several features available within the module and the flexibility in terms of implementation and ease of use. However, limitations like these pose a threat which has to be addressed by Microsoft.

For those looking to have these features, don’t forget we have a some third party ISV developed products available in the market addressing these issues and that comes with added functionality.

To conclude this post, It’d be highly appreciated if Microsoft Product development team comes out with a specific roadmap on this module in specific. This module is long due for enhancement of its features.

BP 5.1 for 64-Bit–Errors

In this post, I’d highlight a series of errors you’d receive while installing Business portal 5.1 on a 64-bit machine. Just to give a quick background, BP 5.0 works with 32-bit editions while BP 5.1 was supposed to work for 64-bit environments. This release happened in the mid of 2010. However, the installation itself has a series of bugs which forced Microsoft to pull back the file download link from Customer source.

I tried installing the same on my 64-bit machine as soon as it was released and experienced the following errors. The only update that we have currently is that the development team is engaged on fixing the issues on installation and no date has been specified yet for this updated release.

While installing the same, We see the following errors and when we hit close, we get the message saying the installation is ended prematurely. (I’d guess the correct message that it should give is that the developers have released the version prematurely –Smile)

-------------------------------------------------------------------
Feature Id: 93dfb004-5724-4a4b-850b-6e0cb99c83c0
Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPWcfConnectorModel
Action: Install
Exception: Method not found: 'Void Microsoft.BusinessData.Infrastructure.AccessDeniedException..ctor(Microsoft.BusinessData.Infrastructure.IAccessControlList, System.Type, System.String, Microsoft.BusinessData.Infrastructure.IExceptionHelper)'.
Error was encountered at or just before Line: '0' and Position: '0'.
Stack Trace: at Microsoft.SharePoint.BusinessData.SharedService.BdcServiceApplicationProxy.Execute[T](String operationName, UInt32 maxRunningTime, ExecuteDelegate`1 operation, Boolean performCanaryCheck)
at Microsoft.SharePoint.BusinessData.SharedService.BdcServiceApplicationProxy.ImportPackage(String xml, String[]& errors, PackageContents packageContents, AdministrationMetadataCatalogStruct adminStruct, String settingId, Boolean updateModel, Guid jobId)
at Microsoft.SharePoint.BusinessData.Administration.AdministrationMetadataCatalog.ImportPackage(String xml, String[]& errors, PackageContents packageContents, String settingId, Boolean updateModel, Guid jobId)
at Microsoft.Dynamics.GP.BusinessPortal.ImportModelReceiver.ImportModel(String fileContents, PackageContents packageContents, Boolean incrementalUpdate)
at Microsoft.Dynamics.GP.BusinessPortal.ImportModelReceiver.ImportModelFromFile(String filePath, PackageContents packageContents, Boolean incrementalUpdate)
at Microsoft.Dynamics.GP.BusinessPortal.ImportModelReceiver.ImportBdcArtifacts(String featureFolder, String modelFilePath, String[] resourceFilesPaths, Dictionary`2 lobSystemAssemblies, Boolean incrementalUpdate)
at Microsoft.Dynamics.GP.BusinessPortal.ImportModelReceiver.FeatureActivated(SPFeatureReceiverProperties properties)
at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPAdminFeatureCollection.Add(Guid featid, Version version, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.AddInternal(SPFeatureDefinition featdef, SPSite site, String solutionHash, Boolean fForce, Boolean fDoValidation)
at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.Add(String relativePathToFeatureManifest, Guid solutionId, Boolean force)
at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Install(String manifest, Boolean force)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointInstallFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)
-----------------------------------------------------------------------

-----------------------------------------------------------------------
Feature Id: f9297852-e1f9-445e-a1ba-5f8fdc2f6bc1
Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPSalesExternalLists
Action: Activate
Exception: Entity (External Content Type) cannot be found with Namespace = 'Microsoft.Dynamics.GP.WcfConnectorModel', Name = 'Customer'.
Stack Trace: at Microsoft.SharePoint.SPListDataSource.InitializeByEntityNameAndNamespace(SPWeb webContext)
at Microsoft.SharePoint.SPListDataSource.ValidateViewGroup(SPWeb web)
at Microsoft.SharePoint.SPExternalList.CreateExternalDataList(SPWeb web, String sTitle, String sDescription, String urlList, SPListDataSource datasrc, String sxmlCustomSchema, QuickLaunchOptions qlopts, String& srurlDefaultView)
at Microsoft.SharePoint.SPListCollection.Add(String strTitle, String strDescription, String strUrl, SPListDataSource datasrc, String sxmlCustomSchema, QuickLaunchOptions qlopts, String& srurlDefaultView)
at Microsoft.SharePoint.SPListCollection.CreateList(String strTitle, String strDescription, String strListUrl, String strFeatureId, Int32 templateID, String strDocTemplateType, String strDataSource, String customSchemaXml, SPFeatureDefinition listInstanceFeatureDefintion, QuickLaunchOptions qlOpt)
at Microsoft.SharePoint.SPListInstanceElement.EnsureListExists(SPWeb web)
at Microsoft.SharePoint.SPListInstanceElement.ElementActivated(SPFeaturePropertyCollection props, SPSqlCommand sqlcmdAppendOnly, SPWebApplication webApp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionListInstances(SPFeaturePropertyCollection props, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.SPFeature.ProvisionElements(SPElementDefinitionCollection elemdefcoll, SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Activate(Guid id, FeatureScope scope, String siteCollection, String relativeUrl)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointActivateFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)
-----------------------------------------------------------------------

-----------------------------------------------------------------------
Feature Id: ad393042-be84-47bd-ae04-fd9aaae1e52d
Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPSalesExternalListPages
Action: Activate
Exception: Object reference not set to an instance of an object.
Stack Trace: at Microsoft.Dynamics.GP.BusinessPortal.ExternalListPages.ModifyListView(XmlNode listNode, SPLimitedWebPartManager webPartManager)
at Microsoft.Dynamics.GP.BusinessPortal.ExternalListPages.SetUpExternalLists(SPFeatureReceiverProperties properties)
at Microsoft.Dynamics.GP.BusinessPortal.SalesExternalListPages.FeatureActivated(SPFeatureReceiverProperties properties)
at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Activate(Guid id, FeatureScope scope, String siteCollection, String relativeUrl)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointActivateFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)
-----------------------------------------------------------------------

-----------------------------------------------------------------------
Feature Id: 6166dbce-44b9-4117-88d2-26048b0433ae
Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPPurchasingExternalLists
Action: Activate
Exception: Entity (External Content Type) cannot be found with Namespace = 'Microsoft.Dynamics.GP.WcfConnectorModel', Name = 'Vendor'.
Stack Trace: at Microsoft.SharePoint.SPListDataSource.InitializeByEntityNameAndNamespace(SPWeb webContext)
at Microsoft.SharePoint.SPListDataSource.ValidateViewGroup(SPWeb web)
at Microsoft.SharePoint.SPExternalList.CreateExternalDataList(SPWeb web, String sTitle, String sDescription, String urlList, SPListDataSource datasrc, String sxmlCustomSchema, QuickLaunchOptions qlopts, String& srurlDefaultView)
at Microsoft.SharePoint.SPListCollection.Add(String strTitle, String strDescription, String strUrl, SPListDataSource datasrc, String sxmlCustomSchema, QuickLaunchOptions qlopts, String& srurlDefaultView)
at Microsoft.SharePoint.SPListCollection.CreateList(String strTitle, String strDescription, String strListUrl, String strFeatureId, Int32 templateID, String strDocTemplateType, String strDataSource, String customSchemaXml, SPFeatureDefinition listInstanceFeatureDefintion, QuickLaunchOptions qlOpt)
at Microsoft.SharePoint.SPListInstanceElement.EnsureListExists(SPWeb web)
at Microsoft.SharePoint.SPListInstanceElement.ElementActivated(SPFeaturePropertyCollection props, SPSqlCommand sqlcmdAppendOnly, SPWebApplication webApp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionListInstances(SPFeaturePropertyCollection props, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.SPFeature.ProvisionElements(SPElementDefinitionCollection elemdefcoll, SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Activate(Guid id, FeatureScope scope, String siteCollection, String relativeUrl)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointActivateFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)
-----------------------------------------------------------------------

-----------------------------------------------------------------------
Feature Id: 6b42a62d-b3a0-4ec4-a2df-1c33e9244234
Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPPurchasingExternalListPages
Action: Activate
Exception: Object reference not set to an instance of an object.
Stack Trace: at Microsoft.Dynamics.GP.BusinessPortal.ExternalListPages.ModifyListView(XmlNode listNode, SPLimitedWebPartManager webPartManager)
at Microsoft.Dynamics.GP.BusinessPortal.ExternalListPages.SetUpExternalLists(SPFeatureReceiverProperties properties)
at Microsoft.Dynamics.GP.BusinessPortal.PurchasingExternalListPages.FeatureActivated(SPFeatureReceiverProperties properties)
at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Activate(Guid id, FeatureScope scope, String siteCollection, String relativeUrl)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointActivateFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)
-----------------------------------------------------------------------

-----------------------------------------------------------------------
Feature Id: 86283466-6086-43d1-8a80-7c3da9bcacb4
Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPInventoryExternalLists
Action: Activate
Exception: Entity (External Content Type) cannot be found with Namespace = 'Microsoft.Dynamics.GP.WcfConnectorModel', Name = 'SalesItem'.
Stack Trace: at Microsoft.SharePoint.SPListDataSource.InitializeByEntityNameAndNamespace(SPWeb webContext)
at Microsoft.SharePoint.SPListDataSource.ValidateViewGroup(SPWeb web)
at Microsoft.SharePoint.SPExternalList.CreateExternalDataList(SPWeb web, String sTitle, String sDescription, String urlList, SPListDataSource datasrc, String sxmlCustomSchema, QuickLaunchOptions qlopts, String& srurlDefaultView)
at Microsoft.SharePoint.SPListCollection.Add(String strTitle, String strDescription, String strUrl, SPListDataSource datasrc, String sxmlCustomSchema, QuickLaunchOptions qlopts, String& srurlDefaultView)
at Microsoft.SharePoint.SPListCollection.CreateList(String strTitle, String strDescription, String strListUrl, String strFeatureId, Int32 templateID, String strDocTemplateType, String strDataSource, String customSchemaXml, SPFeatureDefinition listInstanceFeatureDefintion, QuickLaunchOptions qlOpt)
at Microsoft.SharePoint.SPListInstanceElement.EnsureListExists(SPWeb web)
at Microsoft.SharePoint.SPListInstanceElement.ElementActivated(SPFeaturePropertyCollection props, SPSqlCommand sqlcmdAppendOnly, SPWebApplication webApp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionListInstances(SPFeaturePropertyCollection props, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.SPFeature.ProvisionElements(SPElementDefinitionCollection elemdefcoll, SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Activate(Guid id, FeatureScope scope, String siteCollection, String relativeUrl)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointActivateFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)
-----------------------------------------------------------------------

-----------------------------------------------------------------------
Feature Id: 1d8cee6d-e5ce-40bf-9d79-6ded79e31463
Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPInventoryExternalListPages
Action: Activate
Exception: Object reference not set to an instance of an object.
Stack Trace: at Microsoft.Dynamics.GP.BusinessPortal.ExternalListPages.ModifyListView(XmlNode listNode, SPLimitedWebPartManager webPartManager)
at Microsoft.Dynamics.GP.BusinessPortal.ExternalListPages.SetUpExternalLists(SPFeatureReceiverProperties properties)
at Microsoft.Dynamics.GP.BusinessPortal.InventoryExternalListPages.FeatureActivated(SPFeatureReceiverProperties properties)
at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Activate(Guid id, FeatureScope scope, String siteCollection, String relativeUrl)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointActivateFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)
at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)
-------------------------------------------------------------------

This error more likely seems to be the result of permissions issue.


It is suggested to wait for the fix before installing it on your production environments. Atleast the Development team was proactive enough to pull it out before it affects many installations.