Friday, June 28, 2013

Dynamics GP - How to use the Landed Cost Module in Trinidad


  • Landed Cost Process
    • Setup Cards>Inventory>Landed Costs
    • Setup Card>Inventory>Landed Cost Groups
    • Setup Default Landed Cost Groups for each Item (and for each location if applicable)
      • Cards>Inventory>Quantities/Sites>Select a site
      • Enter Landed Cost in field at the bottom of the page
    • When the item is used on a PO, it will use the default landed cost group
      • You can modify this on the PO Line Detail if necessary
    • When the PO is received, Item-Specific Landed Costs are visible in the Unit Cost blue arrow
      • The Landed Cost Functional Total blue arrow shows a summary of all landed costs
    • Overall transaction landed costs can be additionally added using the Landed Cost button at the bottom of the screen
    • Post Receipt as Shipment/Invoice, or as Shipment only
    • To generate the invoice to the landed cost vendor
      • Go to Enter/Match Invoices
      • Enter Landed Cost Vendor
      • Tick the LC box on the line to indicate this is a Landed Cost Invoice Line
      • Use the Item Lookup to select an outstanding Landed Cost to be paid to this vendor
      • Enter the Landed Cost amount to be invoiced
      • Click on the blue arrow next to "Matched to Shipment" to match the values to the total amount to be invoiced
        • Any variances here will revalue the cost of received inventory if the revalue inventory box is ticked
      • Post the Landed Cost Invoice

  • Trinidad Duty Calculations
    • Import Duty - % of Item Cost
    • Insurance - 8% of (Item Cost + Import Duty)
    • Freight Charge - based on weight
    • Fuel Surcharge - based on weight
    • VAT - 15% of (Item Cost + Import Duty + Freight Charge)

  • The landed costs do not calculate properly for Trinidad & Tobago because we have compound charges that GP cannot automatically calculate (Vat on Duty) 
  • Method 1 - Total Shipment Value Apportion
    • To handle this properly in GP, all charges have to be manually calculated on a spreadsheet first for the entire shipment, then applied to the entire shipment as afixed amount, apportioned by Value
      • Setup each item with it's own Import Duty Landed Cost as a % of value - This gives you the correct duty per line item
      • The total Insurance, Freight, Fuel and VAT are added using the Landed cost button, and are applied over the entire shipment as a fixed amount, apportioned by Value
      • Print and Attach your excel costing sheet to the receipt printout to keep a detailed record of how the costs were calculated
      • This method is relatively quick, but higher value goods will always attract higher costs due to the apportionment method
      • This method may or may not make sense depending on the weight and value of the goods you are importing


  • Method 2 - Manual Line Item Values

    • To handle this properly in GP, all charges have to be manually calculated on a spreadsheet first for the entire shipment. A Factor is calculated for each line item, which is then used to distribute the other costs to that line item.
      • Setup each item with it's own Import Duty Landed Cost as a % of value - This gives you the correct duty per line item
      • Your excel sheet will calculate the Insurance, Freight, Fuel and VAT for each line item separately
      • Enter each one of these as a fixed value cost on each line item using the blue cost arrow in the line item detail
      • Print and Attach your excel costing sheet to the receipt printout to keep a detailed record of how the costs were calculated
      • This method is much more time consuming, but will capture accurate apportionment of landed costs

    Tuesday, June 25, 2013

    Thursday, June 20, 2013

    Dynamics GP - dex.dic version 12.00.0196.000 is not compatible with executable version 12.00.0232.000

    This error occurs when trying to install GP 2013 SP 1


    • Go to program files>GP 2013
    • rename the dex.dic to dex_old.dic
    • copy the dex_us.dic
    • rename the copy to dex.dic
    • rerun the service pack

    Tuesday, June 18, 2013

    How to dismantle Hamilton Beach 10 speed wave action blender


    1. First of all, Hamilton Beach Blenders are GARBAGE. Do not ever buy one. Ever.
    2. There are 2 hidden screws underneath the 2 read rubber legs. Poke something into the holes an side of the legs and pull them out to get to the screws.
    3. Fail horribly at trying to repair it, throw it away, and buy a food processor.

    Dynamics GP Manufacturing - Automatic GL Journals for small inventory cost adjustments

    The system will automatically generate small adjusting entries to correct rounding errors that occur in costing.

    This can be seen by going to
    MO activity > Double click on Raw Material Relief for your MO>Click Receipt Costs

    For example,

    • I Receive 900 units with a total raw material cost of $4,000
    •  The finished good unit cost will be rounded
      • 4000 / 900 = 4.44444 rounded down to 4.44
      • The rounding error = 0.00444 * 900 = 3.996
    • This rounding error should go to a rounding account for overs and unders for inventory rounding errors.
    • The account should be setup in the Manufacturing>Setup>System Defaults>Costing>Rounding Difference Account
    • See this article for full information on all manufacturing accounts setup
    • http://waqasb.blogspot.com/2009/12/microsoft-dynamics-gp-manufacturing.html

    Thursday, June 13, 2013

    Dynamics GP - Security Permission View - UserAccess Which user has access to what Roles, Tasks, and Windows?

    Original Post
    https://victoriayudin.com/2009/03/12/sql-view-to-show-security-roles-and-tasks-in-dynamics-gp-10/

    Modified View
    ----------------------------------------------------------------------------------------------------------------
    /****** Object:  View [dbo].[BI_UserAccess]    Script Date: 08/28/2017 01:52:39 PM ******/
    SET ANSI_NULLS ON
    GO

    SET QUOTED_IDENTIFIER ON
    GO

    CREATE VIEW [dbo].[BI_UserAccess]
    AS
    SELECT DISTINCT
                             S.USERID AS User_ID, S.CMPANYID AS Company_ID, C.CMPNYNAM AS Company_Name, S.SECURITYROLEID AS Security_Role_ID, COALESCE (T.SECURITYTASKID, '') AS Security_Task_ID,
                             COALESCE (TM.SECURITYTASKNAME, '') AS Security_Task_Name, COALESCE (TM.SECURITYTASKDESC, '') AS Security_Task_Description, COALESCE (R.DICTID, SO.ASI_DICTID, '') AS Dictionary_ID,
                             COALESCE (R.PRODNAME, '') AS Product_Name, COALESCE (R.TYPESTR, SO.ResType, '') AS Resource_Type, COALESCE (R.DSPLNAME, SO.SmartlistObject, '') AS Resource_Display_Name,
                             COALESCE (R.RESTECHNAME, '') AS Resource_Technical_Name, COALESCE (R.Series_Name, '') AS Resource_Series
    FROM            DYNAMICS.dbo.SY10500 AS S LEFT OUTER JOIN
                             DYNAMICS.dbo.SY01500 AS C ON S.CMPANYID = C.CMPANYID LEFT OUTER JOIN
                             DYNAMICS.dbo.SY10600 AS T ON S.SECURITYROLEID = T.SECURITYROLEID LEFT OUTER JOIN
                             DYNAMICS.dbo.SY09000 AS TM ON T.SECURITYTASKID = TM.SECURITYTASKID LEFT OUTER JOIN
                             DYNAMICS.dbo.SY10700 AS O ON T.SECURITYTASKID = O.SECURITYTASKID LEFT OUTER JOIN
                             DYNAMICS.dbo.SY09400 AS R ON R.DICTID = O.DICTID AND O.SECRESTYPE = R.SECRESTYPE AND O.SECURITYID = R.SECURITYID LEFT OUTER JOIN
                                 (SELECT        ST.SECURITYTASKID, ST.SECURITYID, ST.DICTID, ST.SECRESTYPE, ST.ASI_DICTID, ST.SL_OBJID, SM.SmartlistObject, 'Smartlist' AS ResType
                                   FROM            (SELECT        SECURITYTASKID, SECURITYID, DICTID, SECRESTYPE, SECURITYID / 65536 AS ASI_DICTID, SECURITYID % 65536 AS SL_OBJID
                                                             FROM            DYNAMICS.dbo.SY10700
                                                             WHERE        (SECRESTYPE = 1000) AND (DICTID = 1493)) AS ST INNER JOIN
                                                                 (SELECT        COALESCE (A.TRANSVAL, F.ASI_Favorite_Name) AS SmartlistObject, F.ASI_Favorite_Dict_ID, F.ASI_Favorite_Type
                                                                   FROM            DYNAMICS.dbo.ASIEXP81 AS F LEFT OUTER JOIN
                                                                                             DYNAMICS.dbo.ASITAB30 AS A ON F.ASI_Favorite_Name = A.UNTRSVAL AND A.Language_ID = 0
                                                                   WHERE        (F.ASI_Favorite_Save_Level = 0)) AS SM ON ST.ASI_DICTID = SM.ASI_Favorite_Dict_ID AND ST.SL_OBJID = SM.ASI_Favorite_Type) AS SO ON SO.DICTID = O.DICTID AND
                             O.SECRESTYPE = SO.SECRESTYPE AND O.SECURITYID = SO.SECURITYID

    GO


    -------------------------------------------------------------------------------

    Thursday, June 6, 2013

    Dynamics GP Manufacturing - Non-Inventory Items

    You can use Non-inventory items on a Manufacturing BOM
    Manufacturing Boms can use Non-inventory items if they are Misc. charges, or Services.
    Flat Fee will not allocate itself automatically as a component on a receipt.

    The items will show up in the picklist as normal, and will affect your finished goods.
    When you post a receipt though, a General GL transaction is created for the non-inventory items.
    These items do not print on any reports, but the costing of your finished good is correct.

    Smartlist>Account transactions>Enable Reference Column
    • Journal Credit RM Non-Inventory costs Debit WIP
    • Journal Credit RM Inventory Costs Debit WIP
    • Journal Debit FG Credit WIP

    Dynamics GP 2013 - Smartlist does not export dollar values or quantities properly

    This article explains what changed.
    http://dynamicsgpblogster.blogspot.com/2013/05/gp-2013-why-are-my-smartlists-not.html


    1. To fix it, Go to Program Files>Microsoft Dynamics>GP 2013>Data>Edit dex.ini
    2. Add this line
    3. SmartlistEnhancedExcelExport=TRUE
    4. Your smartlists will be back to normal

    Saturday, June 1, 2013

    Dynamics GP Manufacturing - SCRAP FAQ

    Methods for tracking scrap in Dynamics GP

    First, we will define the different types of scrap, and the best ways to track each type in Dynamics GP Manufacturing.
    RM-Raw Materials
    FG-Finished Goods
    We will use Bread as a simple example.
    Flour, Salt, Yeast, Water = Bread


    • Manufacturing Constants
      • Once RM is issued to an MO, it will be included in the cost of the FG, even if it is scrapped
      • Component Transaction - Scrap Transaction
        • Adds the cost of the item to the MO, but does not add the quantity.
        • You cannot create a scrap transaction unless you have posted an issue transaction (The stock is not there to be scrapped)
        • You cannot create a scrap transaction if you have used all of the raw materials issued to an MO via FG receipts
      • Entering a value in the "Backflush Qty to Scrap" in the component detail of the MFG Receipt window does not affect anything. 
        • This field is for informational purposes only.
        • If you had to issue more material to replace the scrap to complete production, you must do this manually
      • By Products - The cost of the by-product item is whatever the current cost is of the item on the item master
        • The cost is COMPLETELY UNRELATED to the costs of production
        • However, the Cost of the By-Products will consume cost away from the original FG
          • Example - Bread usually costs $10. However, we can make Breadsticks as a by-product, with a current cost of $1. 
            • If I do an MO for 1 bread and receive 1 bread with no by product, it will have a current cost of $10
            • If i do an MO for 1 bread and receive 1 bread AND 5 Breadsticks, the bread will go in at a cost of $5 and each breadstick goes in at $1 (based on the current cost in the item master)
            • Cost of FG = Cost of Raw Materials and other inputs - Cost of By Products
    • Raw Material Scrap (RM Scrap)
      • This is Raw Material that is spilled or scrapped after it has been issued to the MO, but before it actually gets turned into anything
      • Example-A Worker starts measuring out ingredients to put into the mixer, and he drops a bag of flour and it spills all over the floor.
      • Generally at this point, RM is still in separate components, and the scrap can be measured
      • If you want to Include these costs in your FG, and just track scrap quantities - 
        • Create a Scrap Component Transaction OR Enter the quantity in the backflush quantitiy to scrap field if backflushing
        • Issue more raw material to compensate for what was scrapped if additional material was used, OR increase the backflush component qty used to compensate for the qty scrapped if backflushing
      • If you do not want to include these costs in your FG, but still want to track the scrap -
        • Create a Reverse Issue Transaction to return RM back to the original location, then do an inventory adjustment to remove it from stock, and change the distributions to send it to a scrap account. Enter the MO number in the Batch field to tie the inventory adjustment to the MO. A Manual report will have to be created to link the transactions.
        • If you are backflushing, do not change the default qty to backflush, and simply do an inventory adjustment for the raw materials that should be scrapped and change the distributions to send it to a scrap account. Enter the MO number in the Batch field to tie the inventory adjustment to the MO. A Manual report will have to be created to link the transactions.
    • Work In Process Scrap (WIP Scrap)
      • This is Raw Materials that have already begun processing, and are in a state where they cannot be separated or measured separately, but are also not completed 
      • Example - After the components have been mixed into dough, and then a piece falls on the floor
      • If the components can be easily separated, and adjusted out, treat this the same way as RM Scrap. However, and costs for labor and machines that went into the WIP will not be included, or accounted for.
      • If the components cannot be easily identified and separated, and it is important to you to calculate the true cost of any labor and machine time that went into the WIP, then it should be treated as though it was completed as a finished product, but instead, received into a SCRAP site.
        • Example - We issue Raw Materials to Produce 10 bread. We produce 6, and the other dough falls off the line. 
          • We Receive 4 bread into our SCRAP site - Then adjust this out of stock, changing the distributions to hit the scrap account. Enter the MO number in the Batch to tie this back to the MO.
          • A manual report can be done on all transactions to the SCRAP site
          • We Issue more raw materials to produce an additional 4
          • We receive our final 10 bread into our FG site
    • Finished Goods Scrap (FG Scrap)
      • This is finished goods that do not meet standards to be considered acceptable
      • Example - Bread comes out misshapen, miscolored, or falls on the floor
      • At this point, all costs have been put into the product, and it is a complete product that has to be dumped
      • It should just be adjusted out of stock, with the distributions changed to point to a scrap account, and the MO in the Batch field.
    Conclusion
    • I want to measure scrap, but do not want it included in the cost of my finished goods
      • The only way to do this is to reverse issue raw material from the MO, and then adjust it out, change the distributions and send the cost to a scrap account, enter the MO number in the Batch field, create a customized report.
      • If backflushing, accept all default components, and adjust RM scrap out manually, or receive Scrapped FG directly into a scrap site, then adjust it out, change the distributions and send the cost to a scrap account, enter the MO number in the Batch field, create a customized report.
      • Use standard costing - set the standard cost of the item, and measure cost variances against the standard cost