Consider MRP is running for particular Job on every day basis . MRP is running for same job…
what is the content of SugPOdtl table?
Our team is seeing rows are getting deleted in sugPOdtl table?
my assumption that, PO suggestion are getting deleted for every run of MRP? is that right ? please us here. what is the real beaviour of SugPODtl table?
Is there any simple flow?
Inputs for MRP are BOM, SO and FO entries
Output PO suggestions from suppliers to complete job , assigns resource to that job based on resource and product calendar. Any additional information?
I don’t have any experience in Kinetic yet but my understanding of the SugPODtl table is that it’s the PO suggestions.
So if MRP is running a full regen it makes sense (at least to me) that the SugPODtl table would be rebuild (deleted and then re-created). I’d also point out that buyers can delete suggestions as well. I know for our business we will occasionally have a couple of buyer who will delete the suggestions they don’t want to order just yet.
If you’re trying to determine what’s going on you could always place a BPM on the table and send an email with the information when someone is trying to delete a record. At least then you may be able to tell if it’s the system (and MRP) or a buyer.
@Schae235 Thanks for replying in this thread. Nobody is deleting in POSug table, I mean buyers. It is happening by itself, MRP is recreating PO suggestions, I believe.
Any idea?
If MRP is recreating PO suggestions, when we can send POs to our suppliers? If MRP runs on job for three days, third day we will get latest PO suggestions?
Actually what is the process? When MRP is done with job creation. When is the best time to consider correct and better PO suggestions?
It’ll recreate the PO suggestions until you convert them to actual POs. Once they’re out there, they won’t regenerate. Simplest example is a dropship sales order…suggestions generated, converted to PO, more or less locks down that sales order demand and won’t suggest it again.
MRP looks at the supply (POs and Jobs) and demand (orders and jobs) and will create the PO Suggestions, which is the POSuggDtl table. That table will be changed as PO’s are created from those suggestions, and MRP we re-evaluate and add or remove records into the table whenever it runs.
After you create a PO. (Whether using suggestions or making one manually).
@JMPCONJ Thanks for your reply? How Epicor MRP will come to know whether PO is generated or not and then which leads to stopping regeneration of PO Suggestions?. I will read tech ref MRP guide. Soon I will also add my understanding here. Let us align!!
@Banderson Thanks for you reply. When MRP will come to know, did we create PO or not? Based on that information, it should stop regenerating PO Suggs. Same Question asked to @JMPCONJ too.
If a dropship PO suggestion has already been converted to an actual PO, the sales order is no longer considered an “open requirement” that would require a new suggestion. Hope that clarifies.
If you run MRP with the Regenerative option selected, the very first thing it does is delete ALL unconverted PO Suggestions (as well as all unfirm jobs). The MRP process looks at the Ship By date on a Sales Order Release, then checks what the inventory level will be at that date for that part (which will include any POs due to be received on or before that date). If there is not enough inventory to satisfy the requirement, it will generate a PO Suggestion.
There are LOTS of other variables in the mix (explained in the MRP Tech Ref manual), but that is the basic process.
MRP analyzes demand (orders/jobs) and supply (POs/Jobs) and matches them up to decide if it needs more or not. If you have say 10 orders for 10 each, it will look for supply, (either already in inventory, or coming on an existing PO) and if it doesn’t have enough, will suggest a PO. Of course there are all kinds of knobs that you can adjust to decide how PO’s get suggested (buy to order, drop ship, minimum on hand etc.) so that’s a lot simpler than it actually is, but it’s not looking at an order and recording whether or not you have a PO for it (unless it’s buy to order… lot of caveats here)
It always looks at what’s there and calculates the requirements. Does that make sense?