Running the adjust cost – item entries routine

What is it?

It’s a routine that checks that the inventory cost of a transaction going out of the system matches the inventory cost that went in.

For example –if you purchased an item in January, Sold it in February and then posted a purchase invoice for it in March (with a different cost), it would adjust the cost of sale to match the newly posted invoice cost.

When should I run it?

Firstly you should run the routine away from normal transactional hours, as it is quite a complex process and can cause record locking if you try to run during the day.

How often should I run it?

This really depends upon how accurate you need to keep your cost of sale information during the accounting period. As a minimum you should run it once per month, we generally recommend running it weekly.

Do I need to run it if I am using Standard Costing?

Yes – this is because you may still have stock with a different standard cost to current, especially if you have not re-valued your stock to match the standard cost.

How do I need to set up my posting dates?

You need to pay attention to getting your posting dates correct before you run this routine, as it will attempt to post into a prior period unless you set your posting date ranges correctly.

User Setup   

You need the allowable date range set for the person running the routine to be as wide as any potential adjustments. If you set this too narrow, you will receive an error saying to don’t have permission to post in that date range.

General Ledger Setup

This is the important one! The “Allow Posting From” field needs to be the first date you want any prior period changes to get posted to, so typically this is the first day of your current period. Anything after this date will get posted on the actual date of the change. If you are running the routine say in the first week of a month, but using it to finish off the previous accounting month, then you would set this field to the first day of the previous month, allowing it to adjust cost of sales for the previous month before you close it.

Remember to change the dates in your user setup back to the current period!

Pegasus reasserts itself in the SME accounting market

The last decade has witnessed one the most tumultuous periods for business software in the UK mid-market.  Unprecedented levels of merger and acquisition activity combined with the rise of global mid-market providers has re-defined the software landscape, challenging the way that software is delivered and transforming many systems in the SME space from mere bookkeeping systems into fully fledged business information systems.

It’s a situation very familiar to Pegasus Software, the Northamptonshire headquartered software house that has been one of the mainstays of the British software scene for almost three decades.  In recent years the business has changed hands as the market consolidated and although widely used (more than 100,000 users log onto Pegasus products every day), temporarily disappeared off the radar screen.  Now established as an autonomous trading unit of the Infor group, the fiercely independent business solutions vendor is mustering its partner resources, developing leading edge product…read rest of article

Gartner Research Suggest Firms Miss Social Site Success

The BBC today report on the productivity gains businesses can and are making with similar tools used in social networking sites such as Facebook and MySpace.

Increasingly, Microsoft’s business products are incorporating these tools, too.

MSN Messenger is an easy way to communicate quickly with colleagues on and off-site that is free to use, requiring only a web browser.

July NAV Knowledge Workshop

I’m delighted to say that our building refurbishment is finished and we can now continue to run the NAV knowledge workshops.

As a one-off we’re running it on a Friday this month – Friday 18th July (9.30am – 12.00 noon) at our offices in Wolverhampton.

Topics covered will be around using the Word and Excel export function within NAV version 5. With some added functionality, version 4 users can do the same too and we’ll be showing users this as well.

Matthew Woodhouse will be showing you how you can design your own MS Word-based letters and forms using style sheets and how to populate it with data from your NAV system.

It’s completely free to attend, but we always appreciated being told if you can’t make it after signing up so we don’t waste refreshments.

To book your place email Mark Britton

Speedy SQL Server SIFTs in Dynamics NAV 5.0 SP1

The way Dynamics NAV manages SIFTs in version 5.0 SP1 is a radical step forward from previous versions. Dynamics NAV is now leveraging the power of native SQL Server functionality for this important feature.

Prior to SP1, ever since Dynamics NAV was first ported to SQL Server, each SIFT index was implemented as a separate SQL Server table which had to be updated by a standard SQL Server trigger every time the base data table was changed. Building just a few SIFT indexes could slow certain Dynamics NAV operations significantly and many partners have had to become quite adept at SIFT performance tweaking.

All of this is considerably simplified in Dynamics NAV 5.0 SP1. SIFT tables are a thing of the past, SIFT triggers are no more. SIFT indexes are now implemented as "Indexed Views" which are a powerful feature of the SQL Server database engine.

When you update a Dynamics NAV table which includes one or more SIFT indexes, the SQL Server’s Indexed View(s) will automatically take care of maintaining the SIFT totals. A SQL Indexed View is a materialised view which is most often used to keep aggregated totals based on a related SQL Server table.

As Indexed Views are an integral part of the database engine they can maintain SIFT totals more efficiently than a structure involving custom TSQL triggers and separate tables. As a bonus, we will never have to worry about "zero SIFT records" ever again!

Part of this change means that you can no longer specify SIFT levels as all key columns are now included in each SIFT index. The "SIFTLevels" column (i.e. SIFTLevelsToMaintain property) has been removed from the Key maintenance window in Dynamics NAV 5.0 SP1. This change, along with other performance enhancements in Dynamics NAV 5.0 SP1 (e.g. batching repeated inserts into the database into a single "Bulk Insert" operation), have delivered very significant improvements in the speed of certain typical Dynamics NAV operations.