I don’t have many details right now but just wondering if any one is using Multi-pegging and if you have run into issues?
Our doesn’t seem to be pegging correcting but still testing.
What version are you on? There was a known issue when we were on 10.1.600.6 that was not fixed until I think maybe .28. We upgraded to 10.2.200.7 and the issue was resolved. Issue was mostly around if there was stock on hand for the part it was not considered when calculating against open PO’s and Jobs.
Kimberly,
Look up this SCR and see if it is similar to what you are experiencing.
SCR 202366 Fixed 10.2.100.
Here is the response from Epicor.
Your Multi Level Pegging issue is related to the Problem PRB0184780 enclose below, at the end it notes being fixed by SCR 202366 that was not available until version 10.2.100. If you can upgrade soon to that release you will see this problem fixed. For your version, the latest available release is 10.1.600.27 on the Epicor website, upgrading to this release may also help with this pegging – quantity problem.
Philip Berglund, Epicor Support
I am getting inconsistent results with the Projected Sales order shortages Dashboard. Specifically with the demand links for supply pegging to a purchase order when there is sufficient stock on hand to cover the order. The below order is for a purchase item shipped from stock but is getting pegged to the next arriving PO. Currently we have (14) pcs of that item in stock and should not show as a potential over due order.
Based on all the documentation I have seen Multi level pegging should be using stock on hand first if there is enough to fulfill the order then peg to Open PO’s / Jobs.
Is there a conversion that needs to be run somewhere to fix the issue?
Is this a feature that needs additional modules to run correctly?
Problem PRB0184780
Multi Level Pegging pegs incorrect part Onhand Qty in Warehouse partial from Purchase Order. It should use the full Onhand Quantity first, then use a PO quantity.
PROBLEM DESCRIPTION:
Multi Level Pegging process pegged quantity ignore the warehouse available balance quantity, the system will pegged from the warehouse quantity (Partial), PO supply quantity and suggestion quantity.
EXPECTED BEHAVIOR:
Pegging quantity should come from the warehouse(Quantity that to fulfill the demand should look at the warehouse balance) and the remaining demand quantity should come from the PO Suggestion.
Reproduction Steps:
In Epicor Education \ Main Plant
Step 1: New part
Navigate to Material management \ Inventory management \ Setup \ Part
Ø File – New part
Ø Part = any part
Ø Description = any description
Ø Type = purchased
Save
Go to Sites | Detail tab | purchasing panel
Ø Buyer = Howard Low
Ø Min Order qty = 380
Ø Generate PO suggestions = TRUE
Save [Image 1]
Go to Sites | Planning tab | MRP Planning panel
Ø Process MRP = TRUE [Image 2]
Stay on same module
Step 2: Part quantity adjustment
Inventory management \ General operation \ Quantity adjustment
Ø Part = part number created in step 1
Ø Date = 13 Apr 17
Ø Warehouse = default
Ø Bin = choose any from the search list
Ø Quantity = 100
Ø Reason = choose any from the drop down list
Save [Image 3]
Stay on same module
Step 3: New PO
Purchase management \ General operation \ Purchase order entry
File – new PO
Ø Supplier = any supplier from the search list
At Header | Detail tab
Ø PO date = 15 May 17
Ø Due date = 15 May 17
Save [Image 4]
File – new line
At Lines | Detail tab
Ø Part = part number created on step 1
Ø Our Qty = 200
Ø Unit price = any price [Image 4]
Approved PO and Save
Step 4: New Sale Order x 2
Navigate to Sale management \ Order management \ general operation \ Order entry
New order – at Header | Detail tab
Ø Customer = any customer from the search list
Ø Order date = 26 May 17
Ø Need by date = 26 May 17
Ø Ship by date = 26 May 17
File – new line – at Line | Detail tab
Ø Part = part created on step 1
Ø Order qty = 150
Ø Unit price = any price
Save [Image 5]
Repeat the Step above by create second Sale Order – use the below value for second Sale order
Header | Detail tab
Ø Order date = 28 May 17
Ø Need by date = 28 May 17
Ø Ship by date = 28 May 17
Line | Detail tab
Ø Order qty = 400
Save [Image 6]
Step 5: Run Multi Level pegging process
Navigate to Production management \ Material requirements planning \ General operation \ Multi level pegging process
Now = today date (13 Apr 17)
Submit [Image 7]
Check system monitor for the process status = completed
Step 6: Verify Data by using SQL query
Using below scripts to pull out the data:
Select * from erp.PegDmdMst where Company =‘epic06’ and PartNum=‘part number’ order by DemandSeq
Select * from erp.PegSupMst where Company =‘epic06’ and PartNum=‘Part number’ order by SupplySeq
Select * from erp.PegLink where Company =‘epic06’ and PartNum=‘part number’ order by DemandSeq
Result = refer Image 8
The system is pegged from the warehouse quantity first
Step 7: Repeat Step 4
Repeat the Step above by create third Sale Order – use the below value for second Sale order
Header | Detail tab
Ø Order date = 29 May 17
Ø Need by date = 29 May 17
Ø Ship by date = 29 May 17
Line | Detail tab
Ø Order qty = 100 [Image 9]
Step 8: Run MRP process
Cut Off date = 31 May 17
Schedule start date = 31 May 17
Run multi level pegging process check box marked
Go to filter tab > filter by part number created on step 1
Submit [Image 10]
Step 9: Verify Data by using SQL query
Using below scripts to pull out the data:
Select * from erp.PegDmdMst where Company =‘epic06’ and PartNum=‘part number’ order by DemandSeq
Select * from erp.PegSupMst where Company =‘epic06’ and PartNum=‘Part number’ order by SupplySeq
Select * from erp.PegLink where Company =‘epic06’ and PartNum=‘part number’ order by DemandSeq
Result: Image 11
Problem:
The Supply quantity from warehouse 100 does not fully peg to the demand for SO 1 (qty 150).
It is either the next demand qty of 400 or last demand qty of 100.
The balance quantity of 30 (refer to Image 12 – Time Phase Inquiry) does not linked to any Sale order demand sequence.
VERSION 10.1.500.14
RESPONSE FROM DEVELOPMENT:
SCR 202366 created. Fixed in the 10.2.100 release.
Xxxxxx (04/28/2017)
Able To Duplicate On Epicor Current Code 10.2(04/28/2017)
Ref:MSG13068965
1 Like
Sorry we are on Version 10.2.300.10