Archive for June, 2012


tsgnews

We’re excited to announce that TSG has recently become the first Sage Business Partner to be awarded the title of Sage CRM Accredited Developer on the new Sage Developers Programme.

The Developer Accreditation scheme was launched by Sage in January of this year with the objective of giving developers with a Professional Level subscription a chance to demonstrate their knowledge and proficiency in Sage CRM development.

With a wide range of experience in delivering CRM solutions, the TSG CRM team develops powerful and highly customised CRM implementations using a variety of CRM packages.  Sage CRM is a highly innovative product and we have a real diversity of customers using this software.  As well as deploying it as a ‘traditional’ CRM solution, we’ve developed some powerful and highly customised implementations based on the product. These include membership management for clubs, societies and institutions, plus a combined CRM and claims management system for…

View original post 266 more words

Establishing Landed Costs for Stock Items can be difficult. All companies that import or export need to know what the total cost of an item is.

Calculating Landed Cost is critical in understanding what a stock item costs and so what price it can be sold for.

In order to calculate the Landed Cost, all factors beyond the original price should be considered (shipping costs, custom duties, taxes, insurance, crate costs, handling fees etc.).

The Sage 200 Landed Costs option makes it possible to calculate the costs incurred in shipping costs, duties, etc.  separately from the cost of the stock item it isself.

The Landed Cost values can also be posted to a specific Landed Cost Nominal account.

The Landed costs are added to the cost price of the stock item in order to represent the full cost of purchasing the item in your stock valuation.

Landed Costs are entered during Purchase Order entry. This can be either a percentage or a value. They affect the Stock Control when the purchase order is processed. The Nominal Ledger is affected when the Purchase Order Line has a Purchase Invoice raised against it.

The folloing document explains how to set up and use Landed Costs in Sage 200:

Talking Sage 200 – Landed Costs

The most important part of any business is getting paid. It’s important for any business to make sales, however this is all a waste of time if it does not then collect payment. Having good Credit Control functionality that allows you to collect more debts, more quickly, will vastly improve cashflow.

Sage 200 has its own basic functions to help with Credit Control: Debtors Reports, Statements, Letters and the Credit Control workspace (which is often missed). For a lot of companies these functions are too basic and time-consuming.

Credit Hound, by Draycir, is a Sage 200 add-on that makes debt chasing easier, faster, and therefore more efficient.

It has a separate user interface from Sage 200, but links directly to it, synchronizing your Debtors information.

Dashboards give Credit controllers better debtor visibility, with graphical views of ‘who owes the most money over the longest period’, visibility of ‘who they are scheduled to chase’ as well as ‘who has paid recently’ or ‘promised to pay’.

There is an interactive Debtors Listing, easily filtered as required.

Chasing can be automated, or manual. The chase screen is easy to use with visibility of contacts, transactions etc. There is an area to enter notes. You can also create prompts which will allow the chaser to ask the correct questions based on the Debtors answers or excuses.

i.e. Prompt: Your Invoice X for £Y is outstanding, when will you be sending payment?

Debtor Answers: We did a payment run this morning, I am waiting for the cheque to be signed.

Prompt: What is the Cheque number and Value?

Debtor Answers: 000001111, £Y

Prompt: When will the cheque be posted?

You can flag transactions when a commitment to payment has been made, or if a dispute has been made. Then as part of completing a chase, internal/external letters can be created and sent as required.

e.g. Send a letter to the customer about the agreed expected payment.

or

Send a Dispute report to the required internal contact, to advise them payment is being withheld until they resolve the detailed issue.

Any follow ups that are required after a chase are automatically entered into the Credit Hound calendar so the Credit Controller knows what they need to follow-up and when. The calendar is fully linked to Sage 200, which means if a payment is made before the scheduled follow-up, Credit Hound will automatically complete it.

Rules & Actions can be created so you can tell Credit Hound, if a Customer or Transaction meets a certain Rule then perform a particular Action.

Credit Hound also has its own built-in Report Designer that allows the ability for Creating and or Amending reports and Letters as required. An added advantage is that as a Draycir product, Credit Hound also integrates with Spindle allowing you to distribute documents as required.

When it comes to installing Sage 200 service packs there are a few ways that it can be done, browse to the share from each client machine, copy and run on each machine, or set it up to deploy and run at the next login.

Deploying the service pack is quick, easy, it insures all services packs are installed on all client machines and makes it easier to install remotely.

  1. Copy the service pack to the Updates directory within the Sage share
  2. Go to Program Files/Sage/Sage 200
  3. Double click SageMMSUpdateAdmin.exe
  4. Enter the full Service Pack file name (including extension) into the File Name field i.e. Sage200v2011SP2.msp not Sage200v2011SP2
  5. Type a Version number 1.00.00.00 etc.
  6. Click Save.
  7. This will Generate a file called DEPLOYMENT.DAT within C:\Program Files\Sage\Sage 200
  8. Put DEPLOYMENT.DAT into the Updates directory within the Sage share.
  9. Now Login to Sage 200 on each machine
  10. Download the update(s), as prompted
  11. Install the update(s), as prompted

NB. If other files have been deployed previously (i.e. there is something already in updates), and these need to continue deploying where required, there will already be a DEPLOYMENT.DAT file in the Updates directory. This should be copied to Program Files > Sage > Sage 200 before step 3 above. This way you will be amending the deployment already set up.

NB. If the SP has already been installed on to a machine before setting up the Deployment, it will still try to download and Install when you login to Sage 200 for the first time after setting up the deployment. In this instance allow the file to download. Then go to Program Files > Sage > Sage 200 > Updates. In here there should be a file called Deployment.xml.

  • Right click and “Open With” ‘Notepad’
  • There will be a line for each Deployment starting: <File Name =”Sage2002011SP2.msp”…..
  • On the line for your File Change the Status to = “2”  (It should be showing as “1”)  (Status 1 = Downloaded, Status 2 = Installed)
  • Close & Save.

This happens for me on the server(s) as I tend to manually install service packs here. I install the server(s) like this because once a service pack is installed to the server(s), you have to login to System Administration and update companies.

An issue has been found within the Estimating module for Sage 200 2011 SP3.

The issue occurs when a user amends an estimate by adding a new stage or amending an existing stage on the estimate. If this is done, some stages will then have duplications of Stock items that were already added.

A hotfix has now been released.

An issue has been found within both SOP and POP, where by an exception error is given when a user tries to amend an order that contains multiple lines and the user has re-sorted the lines by the ‘Complete’ column.

A hotfix has been released. This is only relevent to Sage 200 SP3.

A great feature of Sage Report Designer is the ability to format objects in a certain way, depending on certain conditions.

You can configure the fields, sections, items etc. within a report to display in different ways, depending on different conditions.

For example, you might want to highlight Stock items on a report that are below their re-order level. Using conditional formatting you can specify to make the text colour of the Item Name red, if the item is below its re-order level.

The following document uses an example to show how to apply conditional formatting to a particular variable.

Talking Sage 200 – Using Conditional Formatting