Hi Guys,You have sorted it out without my help.It is working like Matt says.And by the way - Copy Entire Master Schedule was implemented on request by some customers who wanted to save the April situation in another MS set and then, as time goes by, compare June situation with what we thought and knew in April.-Mats
Hi @MuzYashoN Sorry for late reply…I can’t see any workaround really in Apps9 and earlier releases.-Mats
Hi,On top of what Athulya writes, I can also mention a small thing that could be interesting for some of you out there…If you have huge number of purchased parts AND you never ever going to use purchase structure for them AND you use MRP AND MRP creates a lot of PO Req Lines, THEN you save some execution time if you set them to Purchased (raw). Why? Well then MRP does not even try to explode the PO Req Line supply into component demand.-Mats
Hi, I think you should add a small idea in IFS Community to add the Calc Variance column to Shop Orders Costs overview page.I think Matt’s proposal will work fine in a pure standard cost business environment where you maintain your Part Cost, cost set 1 amounts. For other valuation methods it will not work so good - well it (Total Std Accum Cost - (Actual Accumulated Cost Total + Total Std-Operation Scrapped) will not be the same amount as the Calc Variance field in the WIP status tab.Best Regards,Mats
Well, there will be a quite big integration, and then a nice thing with MRP and IPAP is as you might know...Typical scenarioWe have a parent demand that generates a shop order reqAnd then we get exploded demand for components and if there is a net requirement, system “responds” by creating SO/PO Reqs for the components.In IPAP we see the exploded demand nicely.Then when we convert the parent SO Req, system hides the exploded demand in IPAP and replaces them with Shop Order Component demand. And under the hood is more than that … it considers P- and K-phantoms in a good way. We avoid showing double demand in IPAP.This could be a challenge for an integration like this.Also if your planners works with Action Messages from MRP, like for example Late- and Early Order messages, this might be a challenge.Then of course you will have the challenge to incorporate new developments in “the other MRP engine”. (if you want) Like for example in 24r1 we have modified logic quite a bit for more advan
Hi,Or do you want to run the MRP job less frequently?-Mats
Yeah, in my examples I don’t have the leadtimes that you have.Anyway - It is the Planned Due Date that are used by the planning engines as well as IPAP and MS-ATP. And it must be like that!The “Forecast Date” column - the only date column in the MS grid - is very oriented towards “the date when the goods needs to be available for picking from stock”. Even if some describes Master Scheduling as a handshake between Sales and Operations (procurement), much of date handling in MS are about when the “stuff” is available in inventory and less about delivery dates. And remember Master Scheduling is close to manufacturing, at the manufacturing side “we” want to see dates that makes sense to “us”.-Mats
Hi Yashodha,I want to get some things clarified first…. So when I test with a master scheduled part in 24r1 (early version) I have following CO and CO Line:I have been moving this in time earlier today when playing with this, from mid march to 1st of April. (And I don’t think I have any picking leadtime on site level)In IPAP the planned due date shows up as 1st of AprilNow I will change this row’s Planned Delivery Date to 1st of May…If I copy some of the data I have in IPAP - All tab. I see my customer order line demand at the 1st of May as expected :-)Do you get correct dates in IPAP? For the CO Line demands?Have you re-executed MS Level 1 calculation?I could type in more questions, but I think it is good to sort out the CO Line dates first and check if it looks okay in the famous IPAP page.Thanks,Mats
Follow up - These corrections are fixing problems with PMRP, MTRs and planning method G, so it seems that they are the ones you need. If you have a test database you can try out PMRP, using planning method A. -Mats
Hi Steph,In October and November 2023 we corrected two bugs in this area in Apps10. So I hope and I think your problem is solved in update 22 of Apps10.Best Regards,Mats at RnD
Hi Yashodha, I am doing fine thanks :-) But I would feel even greater if customers upgrades to later versions ;-)Okay good old Apps9 behavior at my end when testing. Same setup up as you, 1-day backward consumption window, which in Apps9 mean, go backwards infinite number of days, but only if there are records with unconsumed forecast. When 1-day backward consumption passes, then write a level 1 message.There is a remaining forecast of 1, but since forward consumption is 0 then it will not find future forecast to consume. It writes “Insufficient unconsumed Forecast to satisfy Actual Demand”Okay…Next stepMoved the Customer Order Line demand to 25th. And rerun the MS Level 1 calculation.The actual demand has NOT been consumed in forward direction as expected. And there was no forecast earlier or equal to 25th.Hope this helps-Mats
Hi Carlo,A sort of sidekick…Did you know that you can change date and quantity for a shop order direct from master scheduling grid?For some companies where there is a close collaboration between “MS” and Shop Floor this could be useful.So display the Firm Supply Created toggle switch. For the lines with a Yes - system has a connection between the MPS and the Shop Order. As long as the shop order is in state Planned or Released and is backward scheduled, you can modify the MS date and/or the Master Production Schedule Qty and press SAVE. Then the shop order will be updated.Similar with Purchase Order… I mean if you have a purchased Master Scheduled part.Cheers-Mats
Hi @matt.watters Unfortunately we have found a defect here, this worked fine earlier in Apps10, but because of another fix related to MRP and Supplier Scheduling, “things” happened in the MS - Supplier Scheduling generation and the “unknown” bug slipped through. We will fix it.-Mats
Hi,When the parts are shipped out through the door, forecasts and consumed forecast gets reduced. It actually happens when you deliver the customer order line - same transaction. So if you stopped just after:"I then created a new Customer Order for QTY 2 with a planned delivery date of 20/02/24, but then immediately released, picked & delivered it today (14/02/24)."...And then refreshed your “Master Schedule Grid” you would have seen that the forecast and unconsumed forecast would have been been updated. System needs to do this - the forecast is indeed materialized.It reduces the forecast and consumed forecast based on the due date of the customer order line. First it goes backward from due date. So here it does not use the actual delivery date. If it can’t find enough forecast and consumed forecast to reduce, while going backward, then it changes direction IF YOU HAVE FORWARD Consumption window. ***When you run the level 1 calculation, it will always consume forward in your case (
Hello,Are you interested in the exploded demand quantities for the purchased parts? And/or are you interested in the MRP lot sized supply quantities that is sort of result of the exploded demand quantities.And do really really need to start with the SO Req numbers or is it fine to use a “start date” date interval or a “required date” date interval?Anyway the Shop Order Req release screen does not have this featureBut perhaps you can try out the MRP Open Supply Demand Orders page.If you for example provide a semicolon separeted list for you Shop Order Req’s numbers in the Order Ref search column OR use a date intervall search, you could hopefully filter out the demand- and/or supply plan for your required purchase components.And, remember you can query on Part Type here as well, and there are some other interesting columns to filter on/sort by here... Hope it helps-Mats
Hi,Safety Stock has no impact on forecast consumption qty columns.The Cumulative Unconsumed Forecast is carried forward in time. So 3 is correct that day and following dates.Let us just assume that the forecast the 1st of July was not fully consumed. Let say 2 was consumed of 3, then the Cumulative Unconsumed Forecast that day would be 4. Then on the following dates, the CUMULATIVE Unconsumed Forecast will be 4.Cheers,Mats
Hi,In Apps9 and earlier the (Backward) Forecast Consumption Window only works as a triggering point for MS Action Proposals. So system continues to consume forecast prior Forecast Consumption Window. When this boundary is crossed system writes an MS Action Proposal Message: Forecast consumed outside Forecast Consumption WindowIn Apps10 and IFS Cloud this is much stricter, when boundary is crossed, then it does not continue backward. Instead, if Forward Forecast Consumption Window > 0, then it consumes forward until it reaches the forward consumption window boundary.Hope this information helps.-Mats
Hi again,If I quote you:"When I performed the Disassembly Cost Calculation for MW-M-103 in Cost Set 2, no material costs from bucket 110 were distributed to the components..."Now when I read and think a little bit more, I assume you mean from your top manufactured part, you got material cost distributed for you machine- and labor cost buckets, but not for cost bucket 110.I can see a potential problem in RnD code here :-(Perhaps it is not the most common use case, but it should work.Please log a ticket and we will try to fix it.Thanks for testing-Mats
Hi Matt,Answering late from Sweden…First, when cost are exploded down in the structure, it uses the Disassembly Structure only, so the components (if any) that you use (issue) to tear down the part you are going to disassemble, are the ones that you specify in your disassembly structure. And when I have played around with this, my top top part that I am going to disassemble is typically purchased. But I have created a Disassembly Structure for the purchased part, and entered some components like “sandpaper” and “polishing material”. For this purchased part I have connected a “Make and Buy Cost Template (essentially I have combined M-110 and P-110 into a new one).I create a disassembly routing for the purchased part that I am going to disassemble.Okay...I also enter an estimated material cost for my top part that I am going to disassemble (the core)Then I perform a normal cost calculation, and check that my core, sandpaper and my polish material gets the correct cost.Then for my disasse
WOW - I digged deeper into this, and in my first reply I focused sooo much on how MS drives component demand in MRP using the Sub MS receipt.NOW I realize we have a bug in MS how we generate the alternative no:s in the Shop Order Requisitions created when we have lot sized based structures.Report a ticket!Sorry for the confusion @Guto Future glory ahead-Mats
Hello,When Master Scheduling (MS Level 1 calculation) creates master schedule receipt, it actually creates the MS receipts into the tab Sub MS Receipts (and the main reason for this is max order lot size rule => system might need to generate more than one MS receipt per day)Anyway, when doing this we capture structure revision, structure alternate, routing revision and and routing alternate (using for example lot sized based structure rules). This is then used when MRP explodes Master Schedule receipts, to save valuable execution time for MRP engine.When MS Level 1 calculation runs, Structure Revisions and Structure Alternates etc, are refreshed outside Planning Time Fence (PTF). Look at my two yellow marked lines outside PTF. Here I have the same setting as you have. (Ignore values inside PTF, I was playing around here).As times goes by, my proposed MS receipts will roll inside PTF and become fixed MS receipts… and then, when they are inside PTF, we don’t refresh Structure Revision
Hello,The Order Cover Time should be defined in manufacturing calendar days. When it comes to internal processing MRP is working with the manufacturing calendar. You could argue that for purchased parts it should use the distribution calendar when adding the order cover time. That could be a possible future enhancement.So if you have a order cover time of 10, MRP will summarize the demands during 10 manufacturing calendar days and create a PO/SO Req that covers the summarized demand.Regarding your third question… I am not 100% sure what you are asking for, but could Safety Lead Time be something for you to look into. It gives some extra time window, so that we are receiving material a few days earlier than the required date.Cheers-Mats
Hi,Here is the Qty Calc Rounding field on the level 1part, but that one is today only used to get rid of decimals when dis-aggregating forecasts on MS Level 0 (Product family forecast) to MS Level 1. I mean that you can enter an Idea for future improvements so that we can consider this when improving the solution. You will not benify from it now, but perhaps in one year from now.Regards,Mats at RnD
Hi Carlo,I can see that you have some customizations in the header portion of the screen…Anyway, that starting balance with lots of decimals values creates a problem for you. Perhaps we in Core can improve situation here by using Inventory Part Calc Rounding field or the rounding field in the Master Schedule Level 1 Part page itself.If possible, it would be great if you can create an Idea here in IFS Community.Cheers
Hi,As soon as system finds a primary supplier for the purchase part then it will use that record information even it it is 0 supplier manuf lead time or/and if there is 0 inspection lead time.If MRP does not find any primary supplier - when generating the PO Req Line - then the purchase lead time on inventory part will be used to calculate Latest Order Date.Best Regards,Mats
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
