Posts

Showing posts from February, 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,

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 functi

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 ac

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

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 invo

GP Basics: Allow Account Entry

Image
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. 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.

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  f

BP 5.1 for 64-Bit–Errors

Image
I n 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 – ) -------------------------