At Eureka Solutions we regularly get requests from clients to make amendments to the way that Sage 200 works for them.  Our latest blog entry outlines some changes that were requested by a client to some previous Sage 200 development that we had carried out for them.  The development previously delivered was as follows:

• An additional field had been added to the customer record to store Number of Shipping Days.
• An additional field was added to the Sales Order Header that calculates a shipping date by subtracting the number of Shipping days (held on the Customer Record) from the Promised Date input on the Sales Order Header.

Amendments

The amendments requested that our development team carried out were:

• Shipping Date needed at Order Line Level
  • Development was carried out to make the Shipping Date field exist at order line level. This is populated with the order header values by default.
  • The user is then able to change the Promised Date at line level and the Shipping Date is automatically recalculated for that line.
  • The calculation was programmed in such a way that when working out the Shipping date, it excluded weekends.
• Shipping date should be Promised Date Field
  • In Sage 200 the Promised Date on the Sales Order drives MRP recommendations.  The client required the existing Promised Date field to act as the calculated Shipping Date.  Therefore this allowed the field currently used in the bespoke as Shipping Date to be what the user enters as the Promised Date, and the existing promised date field to act as the calculated Shipping Date. This is the same on both the Order Header and Order Lines.

About Eureka Solutions

Eureka Solutions is a leading Sage Business Partner and Sage Developer.  To find our more about our Sage Development or to discuss your specific requirements, please call our head office on 01355 581 960 or email development@eurekasolutions.co.uk.

A client has a bespoke addon which allows them to link a price band to a warehouse.  When a warehouse is selected on an order the addon assigns the price band related to that stock item to the customer, so that all prices for that customer are specific to that warehouse’s price band.

The customer required Sage 200 to have additional functionality to allow users to have item specific pricing per item, per customer and per warehouse.

Solution

• An additional tab on the Amend Sales Ledger Account form was added.  At the top of this tab is a warehouse selector and below this, a grid. The grid was designed to have the columns, “Stock Item Code”, “Stock Item Name” and “Price”.  The user must first select the warehouse they wish to set the customer specific pricing for, thereafter they can add additional stock items and pricing related to that warehouse. The user can add/delete stock item entries from here if required.
• A CSV import and export routine was also provided with the following fields “SL Account Reference”, “Warehouse”,” Stock Item Code” and “Price”.
• On the sales order itself the existing bespoke addon functions as before:
  A SL Account will be selected -> A Warehouse will be selected -> SL Price Band will be changed to the price band associated with that account.
• However at the point of adding an additional Sales Order Standard Item Line onto the sales order, the development carried out checks this customer specific price.  This will be in the order as follows:
  A Stock Item is selected -> A Warehouse is selected -> this looks up a custom table programmed by our team. This will then look at the Sales Ledger Account on the order, Warehouse on the line and stock item.
• This in turn overrides the unit selling price if one exists in their list.  It overrides the value regardless of it being greater or less than the price band value.

About Eureka Solutions

Eureka Solutions is a leading Sage Business Partner and Sage Developer.  To find out more about our Sage Development and how we can help your business please call our head office on 01355 581960 or email development@eurekasolutions.co.uk.

When creating/amending a supplier account, Sage 200 allows the user to enter the supplier’s bank details.  However as standard, Sage 200 2009 does not display these details when using the Supplier Enquiry Form.

As requested by a client we created an additional tab on the Supplier Enquiry Form to allow users to view the supplier’s bank details.

About Eureka Solutions

Eureka Solutions is a leading Sage Business Partner and Sage Developer.  To find out more about our Sage Development and how we can help your business please call our head office on 01355 581960 or email development@eurekasolutions.co.uk.