Skip to main content

Hi,

 

We are trying to drive materials in MRP based on revision dates on the product structures.  We’re able to see MRP no longer planning replenishment for the material that would be phasing out beyond the phase out date of the product structure, but do not see it picking up the planning for the new raw material item based on the phase in date of the new product structure.  Is this not possible in IFS?  

 

Thanks,

Curtis Carpenter

Hi!

I have some questions back to you.

***

Let me first quickly describe how MRP explosion works in IFS for manufactured parts: When there is a net requirement system does the lot sizing and creates an internal supply. MRP is then calculating a start date based on the required date, lot size and the lead time information that is available in Routing Alternate (typically for the *-alternate). This start date is then used to get the revision number (eng chg level). System checks if there is a Plannable or Buildable structure for that start date otherwise you will get an MRP Action Message.

If it finds a revision number it creates a shop order requisition. From MRP Part Information screen, the Gross Requirement tab, you can drill down to THE Shop Order Requisition and check the Stucture Revision number.

This revision number will be used when MRP continue to explode the structure to calculate MRP component demand

***

Checking your data with the description above - can you see any setup issues at your side?

Do you run Selective MRP? We have found a problem in Selective MRP considering future revisions and “as we speak” we are actually correcting that problem. So there will be a patch for this problem very soon.

***

Please also note that from the MRP Part Information screen, you have the Action Proposals tab. In this tab you see all MRP Action Messages for the part in the header portion of the screen.

 

Hope we can hunt down this problem soon

Cheers,

Mats


Hi Mats,

The steps we took are below along with what we are seeing post running both selective MRP and also waiting for full MRP to run.

  • Created a revision to the * alternate product structure with a phase in date of 1/3/2022; this created a phase out date/revision to this inventory part and the existing active product structure to be 1/2/2022.
  • The original * alternate has a raw material (ABC123) that we are trying to phase out and the new revision consisted of the same ingredients in the BOM with the exception of substituting the phased out item (ABC123) with a new part (DEF123)
  • Ran selective MRP for the FG item as well as the two raw materials in question.
  • Shop order requisitions were generated based on forecast loaded for the FG.  This drove purchase requisitions for ABC123 through 1/2/2022 to align with the phase out date on the * alternate.
  • No purchase requisitions created for DEF123 starting on 1/3.  

Expected/Wanted Result:

Everything we saw happen for the FG and the ABC123 item acted as we expected and wanted.  What we are hoping to see in MRP is starting on 1/3, the shop order requisitions for the FG would see the alternate revision and drive DEF123.  The FG just stops driving shop order requisitions at the day we phased out the * alternate.  We are needing it to continue to drive, but drive on the new revision.  Any thoughts?

Thanks in advance.

Curtis


Hi Curtis,

We are about patching a bug correction for Selective MRP not considering future reivisions. If you get this fix applied to your system, then I believe your problem should be solved.

Just want to double check…. the *-alternate for the revision starting on 1/3, is it ‘Plannable’ or ‘Buildable’? Because if it is ‘Tentative’, MRP will not consider it..

-Mats


Hello Mats, 

When you stated: “Do you run Selective MRP? We have found a problem in Selective MRP considering future revisions and “as we speak” we are actually correcting that problem. So there will be a patch for this problem very soon.”  

Can you let us know what update the patch to solve this issue will be, please?  

 

Thanks

Chris 


Hi Chris,

This patch is included in the IFSAPP10 UPD14. The patch id is 161421 -   http://lcs.corpnet.ifsworld.com/login/secured/buglnw/BlBug.page?__ID=165492&BUG_ID=161421

-Mangala.