REP - MRP Summary / Trial Kit / PFS - HELP Troubleshooting Guide
Types of Order in MRP Summary and PFS
PO : Purchase Order.
WO- : Works Order Demand - required to be issued on the date required.
WO+ : Works Order Supply - expected to be completed into warehouse on the due date.
SO : Sales Order.
FC : Sales Forecast.
MRP Recommendations
When showing MRP Recommendations, the types are:
C-R : Cancel or Raise New.
F-B : Bring Forward (expedite) or Put Back (delay).
I-D : Increase or Decrease the quantity.
BAL : Balance excluding MRP recos.
BAM : Balance including MRP recos.
1UP : MRP WO Recommendations for products 1 level up the BOM. These are included in both BAL & BAM on the assumption that they will be actioned.
Therefore BAL shows what the predicted stock would be if firm orders AND the 1UP actions were followed, hence there will be some hotspots.
Eg. where BAL goes below zero.
And BAM shows what would then happen if you actioned the MRP recommendations for this product.
PFS Tips
Hover over the Reference field and the tooltip will show various extra information:
WO: shows any F3 / F7 comments.
FC: shows the customer code, forecast description and the qty that has been consumed by SO.
SO: shows the customer code and the amount of forecast that this line has consumed (only if nett Forecasts showing).
MRP Summary Tips
Hover over the "............Product........Supplier..." section for a tooltip showing the date that MRP last ran.
Hover over the Product code for a tooltip showing the product description.
Document Map
From version 4-30, if the primary sort is Supplier, and "Populate Doc Map" = "n - For 1 tab in Excel"
then the Supplier sections are shown as contracted, with a + box to expand as required to see the product detail.
Key to the background colours on the Quantity field
Hotspots : balance < 0 Warmspots : balance < ROL
Order is inside today + lead time Order is beyond today + lead time
Selecting Weeks with Day Numbers
| | Backward Horizon | Forward Horizon | Results in Day No.s for: |
| A | 0 | 0 | No day numbers |
| B | 0 | 6 | Today and the next 6 days |
| C | 6 | 0 | Today and the last 6 days |
| D | 3 | 10 | Last 3 days, today and next 10 days |
System Keys
Key | Value | Description |
SLECTPREFX | 77 | sl-ect Prefix for other system keys |
77CUST | SL-ECT | Used to add customer specific functions |
77PFSWH** | ** | List of WH to exclude |
77PFSWHRJ | RJ | WH to exclude from PFS |
77PFSMRPIN | YES | Include MRP recos? |
77PFSFWDH | 42 | MRP/PFS Pivots - FWD Horizon if beyond Today + this |
77PFSBKDH | 7 | MRP/PFS Pivots - BKWD Horizon if beyond Today - this |
77PFSWODOF | -14 | MRP/PFS/TrialKit WO detail date offset |
How to affect the "Xsort" field and the Make Or Buy definition:
The SQL View called scheme.slectrepX_stock_multiwh can be changed to suit each site.
So it will never be overwritten by a version upgrade, but it MUST:
a) Contain exactly 1 record for every product that you wish to show in the MRP Summary and Trial Kit screens
b) Have certain mandatory fields:
product (string)
morb_combo (string) - used when selecting the Make Or Buy prompt
Xsort (string) - used for site specific sorting and the Document Map setting
If the same product could exist in multiple warehouses then the above View must deal with this situation.
For example if product ABC1 exists in 3 warehouses and you want to use AnalysisA as Xsort then you need to consider what happens if one of the warehouses has a blank value in AnalysisA, but the other 2 don't.
In that case you would probably put Xsort = MAX(scheme.stockm.analysis_a).
The same considerations must be made with regard to the Make Or Buy field. By default the system uses a lookup to another view called scheme.slectrep_morb_combo2. Note that this view may be overwritten on future upgrades.
And remember that you can use your own Views instead and join them into scheme.slectrepX_stock_multiwh, which is under your control!