Hi,I think you need to check and confirm that you have the correct version of Demand Planning installed for your 23R2 environment. You will need to raise an IFS support ticket to get this checked.Good luck!
Hi,This is a screen shot from IFS Cloud but basically it will be the same in IFS Apps10.You need to check how the ‘Inspection Type’ and ‘Inspection Percentage/Qty’ is set up for your Inspection Code ‘C’Is it ‘Percentage’ or ‘Quantity’? Also, check the settings in your Control Plan - Inventory data points
Hi Christèle,Apologies for the delay. My understanding is that we used Configurations to achieve this.Unfortunately I don’t have any of the technical details, but the process flow was something like this:Create a new CRO Header and CRO Line. Receive the part for repair against the CRO Line. Create a return Customer Order to deliver the part back to the Customer once it has been repaired. Create a Repair Shop Order Add a new Custom RMB or new Custom Command Button to allow the user to choose a Project Activity to connect the Repair Shop Order to. Custom code then connects the CRO to the Project Activity. Process the Repair Shop Order. Custom code is also triggered at various points in the process to ensure that the Project Activity is recorded against the transactions.I hope that this helps.
Hi Stephen,Looking at the various error messages, here are a few things to check …‘The period version for the server not valid’Use the RMB button to validate the dates ‘ORA00918: column ambiguously defined’Sometimes (when the SQL is more advanced or non-standard database views are used) you may need to add “IFSAPP.” as a prefix to the field names as shown below Once these things have been checked, I suspect that the ‘Error in Inheritance Aggregation Process’ may then go away the next time you run the Demand Server jobs.If not, we would then need to take a look for Forecast Parts which are using Inheritance and check the settings.I hope this helps and good luck!
Hi,This value has probably been updated to allow you to run the ‘Create Forecast’ job more than once per Forecast Period (maybe for testing?)This can be edited here (simply remove the date ‘2023-09-26’ in your example)I hope that this helps.
Hi,I think that we need a little more information about the way in which you plan the replenishment of your inventory parts, but essentially, for any parts that are currently planned by MRP, you will no longer receive any supply proposals or action messages which means that the production planners and procurement buyers won’t know which orders to place, reschedule, expedite, etc.I hope this helps.
Make sure the Phase Out Date is a date in the past (e.g., NOT today) 🙂
My apologies, I was multitasking when I replied!You should of course add the ROUTING Phase Out Date hereI hope this helps.
Hi,Try entering a Phase Out Date in this fieldI hope this helps.
So, in other words, you can use this screen to remove or restrict user access to base flows in the old legacy client (the Demand Client) which is the same as it always worked in the older versions of IFS too.However, if you want to restrict access to the base flows within the ‘Demand Forecast’ screen in IFS Cloud, you need to control this using the ‘Publish Forecast’ screen where user access can be granted or removed at different levels.
Hi,You cannot delete the Resource as it is used in other objects.However, you can Phase Out the Resource here.I hope this helps.
Hi,The IFS Help explains it like this …“Enable this option to plan safety stock receipts with the MRP run date by considering the lead time of the part. If the option is disabled, safety stock receipts will be planned in conjunction with the first event for the part.”So, in other words, if you enable the option, it will plan to the replenish the safety stock if the qty on hand is less than the safety stock qty. If you disable the option, it will plan to the replenish the safety stock on the date of the next demand. I hope this helps.
Hi Yash,Thanks for the feedback which will help others in the Community who may encounter the same problem.I’m pleased to hear that you’ve got it working. Good luck with the testing!Best Regards,Richard.
Hi,I think you are on the right lines here and essentially you need to do the following things for the complete solution.Make sure you enter Supplier Manufacturing Lead Time against the Supplier for Purchase Part records for each of the shop order components.You can also include Inspection Time Add External Delivery Time and Internal Transport Time in Supply Chain Matrix for Site Run the Calculate Purchase Lead Time jobThis calculates the Purchase Lead Time for all of the component parts. Create a Routing for your manufactured part and add operations. The Work Centre, Machine Set Up, Machine Run Factor and Factor Unit can be used to specify where the operation takes place and how long the operation takes to perform. Run the Manufacturing Lead Time CalculationThis calculates the Manufacturing Lead Time for the manufactured part. Run the Cumulative Lead Time CalculationThis calculates the Cumulative Lead Time for the parts. Look at the Product Structure for the manufactured part. It is
These values are automatically computed by the system when you run the following jobs: Calculate Cumulative and Unprotected Lead TimeExplanationThis activity is used to calculate a part’s cumulative and unprotected lead times. The cumulative lead time of a part is the total turnaround time for all parts in the structure. You can calculate the cumulative lead time for a single part or all parts for the specified site.Use the Cumulative Lead Time Calculation page to calculate the cumulative lead time of a specific part or all parts in a site.When calculating the cumulative lead time for asingle part, it looks just one level down and accumulates the lead time tothe top.It does not consider the entire BOM structure. When calculating the cumulative lead time for all parts in a site, itstarts with calculating low level code, then it calculates the cumulative leadtime for the parts on the lowest level and then it continues with parts on(lowest level - 1) etc. This always gives accurate result
Is the part that you are trying to move lot / batch tracked? I guess that it doesn’t really matter, but the thing is that the system wants the expiration dates to match unless you distinguish the stock using WDR as previously explained.An alternative solution could be a configuration (a new scheduled task) that looks at all of the stock and automatically sets the part expiration dates (or part lot /batch expiration dates) to same value no matter what location the stock is in. Then you should have no problem moving the stock.If you didn’t want that sort of configuration, perhaps this could be a manual housekeeping task where the user is shown a list of parts (or part lot / batches) where the expiration dates don’t match. This could be a saved search, Lobby Element, report, etc. The user would then manually update the expiration dates as required. The Inventory Part in Stock screen would be a candidate for this.
Hi,Check this previous post > Move same Parts to same Location with different expiration date | IFS CommunityI hope this helps.
Hi Yash,Thanks for confirming the Master Flow (always good to check, just in case) 😉I can’t see the Scenario ID in your DP Client screen shot (it will be in the ‘Detail View’ section), but by default this should be Scenario ‘0’ (which you see in Exported Forecast and in the Import Demand Planning Forecasts dialog).It is possible to create different Scenarios in the DP Client (it’s available from one of these, but I can’t remember which one and it’s Friday afternoon!) 😅 The idea is that you can have different versions (or Scenarios) of the forecast such as ‘Best Case’, ‘Worst Case’, ‘Budget’, etc. which you can then import into different MS Sets (or ‘Scenario Sets’) for analysis, comparison reporting and such like.So …. can you check that it is Scenario ‘0’ in the DP Client?Also, when you make a change to the Adjusted Forecast for Part ‘XXX’, have you tried moving to the next part (Part ‘YYY’) and then moving back again?The Adjusted Forecast should be automatically updated (you may ne
Hi Yash,Just checking here, but is the Base Flow flagged as the Master Flow or does the Base Flow belong to a Combined Flow that is flagged as a Master Flow? Either way, it is there a Master Flow?The problem for me is that the Adjusted Forecast should show in the Exported Forecast screen to start with. This is the data that is then imported into MS 😊
Try switching the Status = ‘Released’ in the DP Client and then refresh the Exported Forecast screen
Hi Yash,Check the Exported Forecasts screen - this shows the data that will be importedRegards,Richard
Hi,In this scenario I would suggest the following (but it may depend on how many base flows the new forecast part appears in):Essentially you could copy the current forecast for the predecessor part and copy it into the Adjusted Forecast for the new forecast part (the Forecast Table allows ‘copy & paste’ possibilities for this). This means that you would have a forecast for this period and then you could run the Create Forecast job again next period. You may need to set the Adjusted Forecast back to the System Forecast (System to Adjusted) next period depending if it’s vastly different (but it probably won’t be).I hope this helps.
Hi Yash,That’s great news!In IFS Cloud 23R2 you can set the decimal precision per user hereI can’t quite remember the old DP Client functionality, but have you tried the RMB option in the ‘Detail’ section or Forecast Table? Perhaps there are some possibilities to change the decimal precision there.
Hi Yash,Take another look at the Base Flow SQL … I think you need to express it like this.This is because you have ‘Ship Date’ and ‘Shipped Qty’ in your historic transactions which matches to ‘Issue Date’ and ‘Issue Qty’ in the SQL 😀Good luck!
Hi,Thanks for the feedback and for confirming that the Phantom Part Product Structures are ‘Buildable’.Next step: Is it possible to create the Shop Order anyway and are any components then included?Not sure how big and deep the Product Structure is, but are you then able to identify any missing component parts which should be on the Shop Order but aren’t? If so, we should then try to focus on the ‘Phantom’ or ‘Blow-through’ parent part for those missing components to see what’s going on.
Already have an account? Login
No account yet? Create an account
Enter your 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.
