Skip to content

MRP Recommendation Fields in the mrmrprm table

March 12, 2014

This is frequently asked by folks running MRP and trying to write their own reports.
The question is what do the various single character codes in various fields really mean?

Field = “kind”:

  • P = The recommendation is to raise or change a Purchase Order (PO)
  • W = The recommendation is to raise or change a Works Order (WO)
  • R = Represents the BoM for a “Raise New WO”.

So for each Raise New WO there will be 10 R records if there are 10 lines on the made product’s BoM.
If you are doing an MRP Analysis type reports you will always ignore the Rs.
But they are very useful for other types of reports.
For instance the slect REP pack has PFS and MRPSummary reports which both use the R records to show the demand qty and date that would affect the PFS balance if the suggested WO had been raised.
Hence an interesting thing to consider:  You don’t always need to raise WO too far out because MRP can generate the same info for reporting on what to buy. If you don’t raise too many actual WO you get fewer recommendations to alter them and more to Raise New on the next MRP run. These just follow changes to the forecast or sales orders, rather than having to change WO dates and quantities if the top level demand changes.

Field = “acted”:

  • B = Put Back / Delay
  • U = Uplift / Increase
  • N = Raise New
  • C = Cancel
  • D = Decrease
  • F = Bring Forward

Field = “tag_type”:

  • G = The cause of this reco is a tag to a GRP record, so a sales forecast.
  • M = The cause of this reco is a tag to a MPS record used as demand when running “Generate MRP from MPS”
  • S = The cause is a sales order
  • C = The cause is a works order BoM line
  • R = The cause is a kind=R record because a WO is recommended for a product on the level above
  • P = Product based, the cause is a reorder / safety level
  • N = None, the order has no tags so all these recommendations are to cancel the mentioned order number
  • Blank = These are just associated with the kind=R lines, exclude those and you never see a blank tag_type

What’s new with Preactor and Sage?

September 24, 2013

Preactor V12 is now available, the main features being:

  • Improved UI – more responsive drag and drop, new zoom and pan features
  • All tabs are now able to float, perfect for multiple monitors with, for example, a plot of people on one screen and the main Gantt chart on the other.
  • Faster performance for automatic scheduling of jobs .
  • Support for SQL SSRS 2008 report features, for example gauges.
  • Shift calendars can now be saved with datasets.
  • Security module.
  • Improved import / export wizard.

Additionally V12 saw the release of a significant new product in the Preactor range. P400 GMPS is a Master Production Schedule that can suggest production quantities for top level SKUs in order to keep future stock at an acceptable level. The level can be a simple minimum stock or can be expressed in terms of days of cover. The calculation takes into account the sales forecast and EOQ batch sizes. In the background the traditional focus of Preactor comes into play with capacity management based on the suggested make quantities. So it is also a rough cut capacity planner. The suggested plan will typically then be fed into a MRP process for lower BoM level requirements, which can then be fed into a standard Preactor APS system for finite capacity scheduling. Perfect for FMCG companies!

slect PRO System:

New from 2013 is the ability to create “Preactor Orders” (PRO) to represent production that you want to make.

Previously you had to create Works Orders in Sage and import to Preactor to get a schedule for a new order. The idea behind PRO is that when you have new customer demand we’ll let you quickly create PRO orders directly in Preactor, fetching the BoM and Routing on the fly from Sage.

So that you can speed up the time it takes to get back to the customer with an accurate promise date.

A great new feature is that PRO will look down all levels of BoM for the product entered. When it finds “Make” items with shortages it will generate PRO at this level, continuing down until all BoM items have been dealt with.

“Buy” items that can’t be satisfied from stock or due in purchase orders will generate “PSUG” purchase suggestions on today + supplier lead time, in order to dynamically calculate the earliest start date for the PRO orders.

Then you can convert the PRO to WO as part of an export back to Sage (requires the Defacto UI module). Or just discard them if you were dealing with a speculative enquiry. The choice is yours.

The system is available for Preactor 400 and 500 APS against Sage 1000 or Line 500.

We are working on doing the same for Sage X3 ERP. A joint development would be great – get in touch if you are an end user interested in this.

Free SQL SSRS Reports for Sage 1000 / Line 500

September 24, 2013

Everyone gives stuff away for free on the internet now, right?

We were feeling left out, so we’ve made some SQL SSRS reports from the “REP” pack available for download here:

Format is .RDL files, ready for use in your report server.

Make To Order – how to get a fast, accurate promise date for your customer.

April 2, 2013

It’s a common problem …. you are a manufacturer taking in sales orders from customers. The order may have 5 different products with the same or different required dates.

Even better (worse!) your products are complex and there are many levels of Bill Of Materials (BoM) to look through to work out which items you need to make or buy in order to satisfy this new customer demand.

With some ERP systems you may have to manually check all supply and demand, perhaps for dozens of part numbers.

The customer wants an answer quickly “when can we expect delivery?”.

So you don’t want to keeep them waiting. But you don’t want to give a quick answer that is not accurate. Either way you could lose this and / or future business.

The answer is to have a production scheduling system that can read your ERP system to fetch BoM and process routes and effectively run an MRP calculation down all levels, suggesting new Works Orders (WO) or Purchase Orders (PO) along the way. If it finds spare stock on hand or due in at any level then that quantity is reserved and no new requirements suggested.

The PO suggestions then tell you the ealiest date that each WO could start, based on the supplier purchasing lead time.

The WO can then be “forward scheduled” into the existing factory plan to find the earliest finish date for each line on the sales order or quotation.

That production scheduling system could be from Preactor International. A Preactor APS system has the ability to do all of the above in a much shorter time than it will take you to trawl through the ERP data manually.

And the answer will be more accurate beacause it will be based on your existing achievable factory plan. Customer delivery performance will improve, as will your reputation at the customer!

More info? Check out some of the screenshots on this PDF:




Work Order allocations prevent Sales Order allocation

May 12, 2011

Problem: Maybe you have a product that is used to make a finished goods item, but which may also be sold for spares? If so then the stock may sometimes get allocations at the same time from both WO and SO. Even if the WO dates are 2 months away, you can’t allocate a Sales Order due out tomorrow. So you end up deleting the WO to despatch the SO and then re-create the WO. Crazy!

Solution: Change the BMSPALLOCS system key to YES. Then WO allocations no longer count when trying to allocate a Sales Order. And you’ll see the WO allocations in a seperate field stockm.worder_allocations.

So remember to run a “Stock Recalc” just after you change the system key!

Some things you can do with the Sage system

August 5, 2010

14 Things You Can Do With Sage ERP 1000 / Line 500

1. View all the main Full Stock Details and Stock Statusfieldson one page

2. Show the TIME of a transaction in Stock History. 

3. Find all the products that are expected to have stock below zero (or the ROL) at some point in the future.  

4. Use an MRP recommendations report that can be edited in Excel, with a drill down to Predict Future Stock. 

5. View what you have spent with a supplier by year / period.

6. List which data tables were added to by doing a transaction – to know where to look for the data.

7. Track who has changed a standard cost, when they did it, and the before and after values to find the change in stock value. 

8. Report on all changes and additions to Sales Order lines.  

9. Report on all changes and additions to Purchase Order lines. 

10. Explode a BOM to all levels and view this in Excel. 

11. Enter a top level (sales) product and quantity, then explode the BOM to find the longest cumulative lead time  and check stock availability. From which you can estimate a promise date for a new sales order. 

12. Force WO Completions to take component stock ONLY from specified “backflush bins“.  

13. Automate the entry of timesheets to get real time labour hours and WIP Tracking data. 

14. Stop all those “Bring PO forward” MRP recommendations by driving the MRP from an achievable production plan

For full details click here 


Preactor Version 11 is now available!

June 23, 2010
Including the all new Material Explorer.
Watch the video here: