Mark Polino's Blog, page 213
July 23, 2012
Weekly Dynamic: Tracing Purchase Price Variance
Purchase Pice Variances can occur when the purchase invoice cost is different from the cost recognized on the receipt (usually the same as the P.O.).
GP properly adjusts for these cost difference but they can be a real bear to trace. When you find the GL side of one of these transactions they don't link back to the source except with a reference. You have to go to SmartLists or the tables to figure out that they started in Inventory.
However, there is a Dex.ini switch that can make this easier. Adding:
REVALJEINDETAIL=TRUE
to the Dex.ini file populates the ORCTRNUM, ORMSTRID, ORMSTRNM and ORDOCNUM fields in the GL10001 (GL Transaction Amounts Work) and GL20000 (GL Year-to-Date Transaction Open) tables making it much easier to trace these transactions back in SmartLists.
There is also a set of downloadable reports that improve on the default posting reports. However, neither the default reports nor the downloadable reports can be reprinted so if you want that detail you'll have to print or save the posting reports.
More on this next week.[image error]
GP properly adjusts for these cost difference but they can be a real bear to trace. When you find the GL side of one of these transactions they don't link back to the source except with a reference. You have to go to SmartLists or the tables to figure out that they started in Inventory.
However, there is a Dex.ini switch that can make this easier. Adding:
REVALJEINDETAIL=TRUE
to the Dex.ini file populates the ORCTRNUM, ORMSTRID, ORMSTRNM and ORDOCNUM fields in the GL10001 (GL Transaction Amounts Work) and GL20000 (GL Year-to-Date Transaction Open) tables making it much easier to trace these transactions back in SmartLists.
There is also a set of downloadable reports that improve on the default posting reports. However, neither the default reports nor the downloadable reports can be reprinted so if you want that detail you'll have to print or save the posting reports.
More on this next week.[image error]
July 20, 2012
July 19, 2012
Weekly Review: PowerPivot and Multiple Cubes
Last week we looked at PowerPivot for analyzing Dynamics GP data. This week someone
asked if you can connect to multiple cubes with PowerPivot. Yes you can. For
testing I connected to the GP Financial Cube and Sales Cube and then was able to
join them in PowerPivot. These cubes were both on the same server but given the
way that PowerPivot connects that there is no reason that you couldn’t join
cubes across servers assuming that the you have the right access.
Originally Posted by Mark Polino
at 10/25/2010
09:00:00 AM
asked if you can connect to multiple cubes with PowerPivot. Yes you can. For
testing I connected to the GP Financial Cube and Sales Cube and then was able to
join them in PowerPivot. These cubes were both on the same server but given the
way that PowerPivot connects that there is no reason that you couldn’t join
cubes across servers assuming that the you have the right access.
Originally Posted by Mark Polino
at 10/25/2010
09:00:00 AM
July 18, 2012
Adding Window Size and Position Memory using the Support Debugging Tool - Developing for Dynamics GP
David Musgrave adds to his SDT Non-Logging Triggers post with Adding Window Size and Position Memory using the Support Debugging Tool [image error]
